We build into our profile (for each version) custom folders stored on the user's personal network space (that only they can read/write) using their LOGINNAME, so that no matter what computer they log into, _their_ customized settings are loaded by default (i.e., Main CUIx, PGP, etc.).
This makes it easy for any user to log into the laptop in a conference room for meetings, etc. and still have their settings, menus, keyboard shortcuts, etc. available immediately.
We store all Enterprise customizations on the network where user's are not allowed to write, but can also read from any work station. I use offline files for Laptop users (like myself).
Could you please Give more explain how to do that?
Building on @rkmcswain's & @dgorsman's apt comments....
This is initially setup on the IT side, where the user's Active Directory account is assigned a 'home folder' which resides on the network, and is assigned a drive letter, for which only that user (and Admins) have write-access to.
From Active Directory, this is done by opening the user's Properties, Profile tab, Home folder section (at bottom), check the 'Connect' radio button, specify a drive letter from the dropdown, and then paste the UNC path in the textbox. For these changes to take affect, have the user log off, and back onto their workstation.
With that in place - this 'personal network space' - now I begin to create version-specific folders for each deployment (i.e., I:\CAD\2014, I:\CAD\2015, I:\CAD\2016, I:\CAD\Common, etc.), usually created via .BAT as part of our initial deployment, or updates, but it can be done in several different ways (i.e., PowerShell, etc.).
The ..\Common\ folder might store anything that should be available to all versions, such as Apps/plugins, Fonts, Linetypes, LISP, Hatch Patters, Scripts, or Tool Palettes, etc.
The version-specific folders, might hold the user's custom CUI, LISP, Scripts, Tool Palettes, etc., so that they can customize each as they wish, without affecting the Enterprise files (stored on the network where user does not have write-access).
All of these file paths are mapped into that version's SFSP, etc. so that the user just launches AutoCAD, and has all of their (as well as the Enterprise's) customizations on first run, or after an update.
The point is, that by having your script use the user's personal network space location, these user-specific files, folders, and settings, are always stored in a location that is both consistent for each user, and available to each user no matter what machine they log into.
As example:
You have a client meeting in the conference room; you just log into the conference room laptop (provided it too, has a valid AutoCAD license, etc.).
A workstation crashes, and requires IT support? Simply log into any other workstation, provided you have an available workstation as CYA, and a valid license, etc.
This scenario also allows for all user-specific settings to be backed up, so if they accidentally delete something critical, CUI becomes corrupt, etc. it's usually a simple task to restore from last good backup copy, regardless of using Windows' File History availability.
HTH
