Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

rmitchellFGQ5Z
en respuesta a: rmitchellFGQ5Z

Posting to follow up for any future IT Admins looking for some guidance/help that are new to ACA24. I was able to solve my own problem/questions and my findings were that pretty much everything you should need (except for more advanced lisp, etc. customizations) should come over in either the .ARG profile/file which is really just a registry file with a different file extension/formatting, and the CUI/X files. Custom workspaces (toolbars, etc.) are contained and stored within the CUI file from what I can tell, just make sure the CUI file has been saved correctly post modifications/customizations.

The issue I was chasing was a correctly configured CUIX file on the local user's C drive location, that was working, but had not been saved/overwritten to capture all the latest changes. Not sure if this is 100% the correct explanation but by going into the workspace/CUIX editor and just hitting save on the CUIX file, it overwrote the C drive location file for the local user CUI and upon export/deployment to test endpoints solved the issue. 

I'm not saying it's all encompassing, but I have found as an IT admin new to ACA24 customization, that most of what you should need lies in ARG and CUI files assuming they are saved correctly. This greatly reduces workload and allows saving those two file types to a corporate location like on a network share drive, and just using the desktop shortcut /p parameter to pick the correct ARG file to start ACA24 with. Then, if the ARG file correctly points to the specific corporate (network share) and local C drive CUI files, ACA24 should open and load correctly per your customer's needs. 

 

I found these methods combined solved the majority of my problems, which I did not find intuitive from the ACA24 admin deployment instructions or suggestions. Hopefully Autodesk continues in the future to make their software easier to manage and deploy for IT admins that have to handle numerous endpoints and don't know the ins and outs of the software suites.