Missing Civil Imperial Subassemblies

[Anonymous]

The Civil Imperial Subassembly is not showing up in our list of palettes. I've followed the instructions listed at

https://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticl....

Unfortunately, those steps do not work for me. After copying the files to the local user's appData we are still not seeing the Civil Imperial Palette. Thanks for any additional help the community can provide.

Additional notes

1. We are running Windows 10 x64 Educational version.
2. Software was deployed using SCCM.
3. Reinstall has helped, but seems impractical for the number of machines involved.
4. Software: Civil3D 2016

Thank you again.

[Darin.Green]

What workspace is currently being used? 

You may need to rebuild the Civil 3D Profile. To do this follow these steps:

1. Close Civil 3D
2. Delete the following directories:
   • C:\Users\<username>\AppData\Local\Autodesk\C3D 2017
   • C:\Users\<username>\AppData\Roaming\Autodesk\C3D 2017
3. Go into the registry editor and delete the following key:
   • HKEY_CURRENT_USER\SOFTWARE\Autodesk\AutoCAD\R21.0\ACAD-0000:409
4. Start Civil 3D again.

[Anonymous]

Thank you for the quick response. How do I check the current work space?

I haven't tested this yet, but it seems like it would be difficult to do this in our labs since it requires that someone login before we can apply the fix.

[Darin.Green]

Using the quick access bar at the top left:

[Anonymous]

The workspace is Civil 3D.

[natasha.l]

Hello @Anonymous,

Thank you for being a part of the community! :)  This is a product specific question that would best be answered on the Civil 3D forum.

I will move this message for you to the correct product forum, they may have some more useful information and provide a better solution.

Thank you. 

[cwr-pae]

You can recreate the assembly palettes. In the Corridor menu select the assembly catalog. In ACAD create a new blank palette named Assemblies, in the catalog window select the Imperial Catalog, then the Assemblies category, the common Assemblies subcategory, drag each Assembly to the new palette using the little circled I symbol (you will see a little eye-dropper symbol for the cursor tip when you have it).  Repeat for each catalog and palette.

[Anonymous]

I need a solution that we can deploy in mass and that will work in a lab environment. In other words, each computer will be used by multiple students.

[cwr-pae]

Set up the palettes as I said. Export the palettes to a central location (server) or movable drive (external) and Import them to each computer.

Or path tool palette folder locations to a central server on 1 computer with write permission to that folder. Then set up the palettes on that computer. Path all computers to that folder and the palettes become available to all computers pathed to that folder. Creating palettes will create a 'palettes' folder in the pathed folder. For speed that folder should be pathed and placed at top of the list. When creating palettes the root palette folder has to be the top folder. It is best to keep write permission to the tool palette folder restricted to one user.

Or the Assemblies catalog can be used to put assemblies and subs directly into drawings. Click the assembly or sub, drag to the drawing, then release and pick placement point.

[Anonymous]

Thank you. I will give this a try.

--
Kind Regards,

Lorenzo A. Watson

[Anonymous]

Thank you for the suggestions. This is close to working as needed. Does Civil 3D modify the ToolPalette folder during initial setup? The suggested process fails for individuals who are using the software for the first time.

[Darin.Green]

During the initial startup of the application is when the tool palettes are built. The location of these tool palettes is %appdata%\Autodesk\C3D 2017\enu\Support

To perform the steps outlined by @cwr-pae, you'll need to have the users launch the application atleast once before importing the palettes

[Anonymous]

Thanks. That's what I thought. Unfortunately, this doesn't work for us
since we have hundreds of users. I've decided to redirect the application
to a central location tool palettes. I can do this by editing the registry
key using group policy. Here again, the initial setup will break this, but
it does repair itself after the gpo runs again. I'm now looking for a way
to prevent the software from changing my registry edit during its initial
setup.

--
Kind Regards,

Lorenzo A. Watson

[Darin.Green]

A solution to this is to get a working machine with everything in-place for you palettes. Then, Export the profile to a network share for hosting across the network. 

Once that's complete, edit the shortcuts on everyones desktop to include the /P switch and point it to the profile on the server where it was exported. Now, this will only effect those machines where the profile doesn't already exists, so you don't need to worry about it wiping away any changes the user made.

Your shortcut Target field currently look like this:

"C:\Program Files\Autodesk\AutoCAD 2017\acad.exe" /ld "C:\Program Files\Autodesk\AutoCAD 2017\\AecBase.dbx" /p "<<C3D_Imperial>>" /product "C3D" /language "en-US"

Change it to:

"C:\Program Files\Autodesk\AutoCAD 2017\acad.exe" /ld "C:\Program Files\Autodesk\AutoCAD 2017\\AecBase.dbx" /p "\\server\share\ProfileName.arg" /product "C3D" /language "en-US"

[Anonymous]

Awesome, thanks!

--
Kind Regards,

Lorenzo A. Watson

[Darin.Green]

You're welcome!

I've also edited my previous response to include the target path changes...

[mattwhite6085]

We had a group of 'custom' tool palettes we had originally created in C3D2012. by copying the file structure of "%AppData%\Roaming\Autodesk\C3D 2012\enu\Support\ToolPalette\Palettes" to a shared location on the server, and setting one of the tool palette paths to that location and the exporting a 'default' .arg file that was imported as the default .arg on each new computer/user we were able to deal with a lot of pathing issues all the way through 2015.  However, starting with C3D2016 these palettes are no longer loaded.  If we load (import) them manually, they function for that session but disappear with each restart of C3D. 

Any suggestions on fixing this in C3D2016-C3D2017? 

Thank you for your time,

Matt

Infrastructure Design Suite (2016-2017)

i7-7820X @3.6^^4.2Ghz

Winderz10x64Pro

16GigawafflesRAM

nVidiaGTX1080