![]() ![]() Workstations all have "P:\" drives mapped back to the fileserver. Maybe explain the methodology used in your opening of the files, & how Everything plays into that methodology? Thanks for the help, I am mainly just trying to rule things out at this point. Is the way I configured Everything causing the corruption? Is this even a possibility? I am just learning about using an ETP server to provide a central index for multiple users. I did a brief search on this forum for similar events, but didn't find anything matching Autodesk software issues. No Windows updates have been installed recently, and Everything was the most recent change on each machine. The machines are all running Windows OS Build 17134.706. This same scenario occurred for 3 other users throughout the day. The strange thing is we recovered the file in question from the last save that occurred 10 minutes prior to the corruption, and it worked fine. This is a Civil Engineer office, so in the morning I got reports from several users that their drawing files were corrupted upon opening. I configured Everything to index these drives every 6 hours. ![]() I then configured each user workstation to index "A:\" and "P:\" drives which are mapped back to the file server. Last night, I deployed Everything on a domain network from the domain controller for about 15 users. I have been using Everything on a basic level for a few years now. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |