Hi,
I'm not sure I'm posting in the right forum, but anyway, here goes...
Our IT department was tasked with creating a deployment of Civil3d 20xx. The deployment was supposed to include specific support paths. The deployment however doesn't seem to work as intended. The support paths are only available in the "as autocad" version of the installment. This leads me to believe, that the supportpaths are written in the wrong "profile" when creating the deployment. I'm currently not able to test how a deployment is made so I'm asking you guys wether you know what went wrong... Maybe some checkbox was left unchecked or something?
Any help is always appreciated!
- F
Solved! Go to Solution.
Solved by m_latz. Go to Solution.
Hello @Buzz0m,
I have listed some information you should review. When the Autodesk deployment was created in the Deployment Wizard a direct network path needed to be specified for example,\\server\share\folder.
Please review the "Best Practices for creating a deployment".
Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.
Natasha
Community Product Support Specialist
Helpful Links:
AutoCAD Videos | AutoCAD Crashes or Freezes | AutoCAD Customer Council | AutoCAD System Requirements | Prepare your computer for download | Autodesk Virtual Agent | Clean Uninstall | Steps for Setting-Up Student Software
Hi @natasha.l !
Thanks for your tips! I'll look into them and pass them on...
Our IT guy pointed out that the problem seems to be in the profiles (?). The text strings below are from the icons that appear on the users win desktop after installment. The "Civil 3D 2020" doesn't work but the "as autocad" alternative works... just to be sure I'd like to know that into which profiles the support paths are written? If our IT guy is correct, the support paths is only written to a specific profile and nowhere else? What is the point of that?
Does this mean that for the installment to have a predefined civil3d profile we would have to run somekind of overwrite on the "<<C3D_Metric>>"-named profile? I don't want to go down the road of creating shortcuts for different profiles but use the OOTB profile that is linked to the shortcuts that come with the standard installation...
Civil 3D 2020 = "C:\Program Files\Autodesk\AutoCAD 2020\acad.exe" /ld "C:\Program Files\Autodesk\AutoCAD 2020\\AecBase.dbx" /p "<<C3D_Metric>>" /product "C3D" /language "en-US"
Civil 3D As a AutoCAD 2020 = "C:\Program Files\Autodesk\AutoCAD 2020\acad.exe" /P AutoCAD /Product "C3D" /Language "en-US"
- F
Hello @Buzz0m,
Sure. The software needs Administrator rights during installation & at first launch after installation.
Users must have Full Control permissions you will read/write to the folder locations:
Additionally, users must have Full Control permissions to all registry keys and values:
You should also set a program to run as administrator.
Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.
Natasha
Community Product Support Specialist
Helpful Links:
AutoCAD Videos | AutoCAD Crashes or Freezes | AutoCAD Customer Council | AutoCAD System Requirements | Prepare your computer for download | Autodesk Virtual Agent | Clean Uninstall | Steps for Setting-Up Student Software
Hello @Buzz0m ,
sorry for the delay, but I did not read your post.
It is quite easy to modify the settings you need, if you know where ...
Just go to your deployment folder to ".\Img\Content\en" (I suppose you have an English version)
There you have the following configuration files:
For example in the "cp_C3D_Metric_Base.xml" you can modify things like shortcut parameter, etc.
In the "cp_C3D_Profiles.xml" you can modify the profile settings for the C3D specific profiles:
I hope this solves your problem. If not let me know.
regards
Markus
After looking into this it seems that @m_latz suggested solution works [I haven't tried it yet]... I also found this thread, which goes a bit deeper into instructions on setting up the deployment image:
I can confirm, that the marked solution works. Only thing that need tweaking is the support paths and dwt-template filepaths. That means editing TWO xml files in the deployment folder structure as pointed out in the thread.
Can't find what you're looking for? Ask the community or share your knowledge.