I have an existing admin image and I want to change or add file locations for templates, etc. I understand that this is editable in one of the files in the admin image. Which one do I need to use? Thanks for any help in this.
Does this help?
The best solution that I have found for doing this is to push a registry file in your installation. You can either make a registry options file and make it part of the default settings to install in the Admin image or simply run a post install batch process to merge the registry file into the system. Depending on what areas you all want to map, there are different locations in the registry to set. For a list of them just post the list of things you want to deploy and I can provide you with registry locations.
I will be in touch with you soon to try and resolve this issue.
Unless this functionality was added in 2010, setting template locations (and similar, with the exception of toolbox) is not possible in the AdminDirector.xml.
The KB Solution ID S-015650 even specifies that this is to be done via a registry file (or .sldreg).
Question: Using an administrative image installation, can an end user specify that all templates be in a certain location?
Answer: Yes, it is possible to use the administrative image installation to have users accessing their templates from a uniform location. While creating the administrative image, use the option to capture the registry information, and then proceed to define the locations of the templates (and any other accessible sources) in the 'Tools > Options > System options > File locations'. This will save the location paths in the registry and everybody who installs using this administrative image will get this registry merged in his machine thereby having uniform location paths for templates. The key here is to define a UNC path while creating the administrative image.
Another way of achieving this, if the administrative image is already created, is to define all the locations for templates in one user’s machine, and then copy his registry settings to all the other machines.
A big advantage to using the registry file is that as a support AE for a VAR we see a lot of issues that are corrected by crashing (resetting) the users registry settings (HKEY_Current_User\Software\Solidworks\Solidworks ####). If you build a registry (or .sldreg) file for deployment with your image, you have a great starting point to reset every user. If you set options, if available, in the AdminDirector.xml, you would have to reinstall to redploy those settings.
Retrieving data ...