Hi There,
Is an enterprise customization file necessary? I have created a partial customization file for my office. Currently, I maintain the customization file in a location on the server that is read only to all others but myself. From there, I have a deployment set that maps to to each user's local machine - which is where CAD options points.
In an experiment to better understand Enterprise CUIx I merged my partial customization with the Civil3D CUIx, then saved it as our Enterprise CUIx file. I understand why I am getting an error message that the default / main CUIx file is unable to be loaded because the customization group already exists (the file is loaded twice and that this occurs when an enterprise cuix loads a cuix as a partial customization file and then the main cuix tries to load the same one).
What is the best way to clean this up if I need to go the route of Enterprise CUIx?
1. Remove the Civil3D CUI and only map my partial customization as an Enterprise?
2. Maintain my current workflow - knowing that I have a write protected customization file in safe keeping?
For clarity, the reason for my exploration into Enterprise CUI is that a handful of users have been experiencing drag and slow performance since loading the partial customization CUI from our shared server. I have since created a deployment that essentially "robocopies" from the server to their local machine each night, making sure they have the most recent file. This also seems to help for folks working out of office.
Thank you in advance for any suggestions!