SharePoint based Support Files - Lessons Learned
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
This is less of an inquiry and more a report of results. The company I work for has stored support files on our local servers so that all settings and standards can be accessed by all users without having to worry about versions. The secondary portion of this is that we have software that allows us to change the options prior to startup so that standards for client "A" don't have to be the same for client "B". This works well when working across 100GB ethernet, but as we all went to working from home with a variety of speeds it became problematic.
Typical issues:
- Excessive start-up times (as much as 6-9m for a blank drawing)
- Command lag (entering commands has to be done 1 keypress at a time, we were seeing a lag of up to 3s between typing the first letter and when you could type the next key)
- Tooltip lag (any instance when a tooltip would populate would generate lag of 3-30s)
In the past, to avoid these problems what we've done is copy the support files to the C drive, but without knowing how long we'd be working from home the question was how do we deal with updates to the support files.
The solution we came up with was to store the support files on SharePoint (SP) and use the OneDrive (OD) application to sync the files to the local computer. To do this we've replicated the general folder structure of the server at the top level with our support files in their relative positions below it. Such as below:
SERVER
└ ACAD-SUPPORT-FILES
├ APPS
├ CLIENTS
│ ├ CLIENT-A
│ │ └ [Client specific files]
│ └ CLIENT-B
├ FONTv22
└ LISPv22
The result is that the average time to open a file is well under a minute, generally around 40s, and there is a general improvement in response time for all commands and tooltips. The only lag we're experiencing is the lag of the working files that are located on the server.
We have found 1 problem with this method, and we do have a work-around, however the nature of the problem is such that we are unaware if it's happening it areas that simply aren't as visible. This method syncs the files from SP, OD has 3 basic states for file being synced.
- In Cloud
- On Device (Temporary)
- On Device (Always)
When a file is "In Cloud" AutoCAD does not necessarily recognize the file is available for use. This was found by way of CTB files being unavailable in the Plot window. The files were in the correct location in the SP folder but were not available in AutoCAD until we right clicked on our Plot Styles folder and selected "Always keep on this device" from the OD menu. This fixed the missing CTB issue.