Configuring Fabrication Configurations
When you manually add a Fabrication Configuration to your system yourself, it only works for the currently logged in user. In fact, you may have noticed this with your own configurations compared to the default ones Autodesk adds during installation. You can see the difference by the presence of a little Yellow Lock icon in the lower left of the Configuration’s image.
So when you use the Add Link option to add a configuration, it’ll only exist for you. If someone else logs into the computer, the configuration won’t be displayed for the new user. Autodesk’s on the other hand…will still be there.
The difference between these two ways Configurations work is based on how the configurations are “configured” in the Windows Registry. So let’s take a look by starting the Registry Editor.
The first thing to know, is that there’s two ways to start the Registry. Just running the REGEDIT command opens the editor and displays everything. The other way is to Run as Administrator. When just run, you’ll have read/write access to the HKEY_CURRENT_USER branch (‘Hive’ is the proper term) often abbreviated as HKCU. This is the branch where the User configurations are stored.
The Computer based Configurations (like Autodesk’s) are stored in the HKEY_LOCAL_MACHINE branch often abbreviated as HKLM. When you run REGEDIT normally, you’ll see the HKLM branch but it’s Read-Only. To write to the HKLM branch, you’ll need to launch REGEDIT with the Run as Administrator option. Your IT Department may restrict this from you so you may need to involve them if you want to implement Computer based Fabrication Configurations.
The other thing to note, is that when you Run as Administrator, the HKCU branch is there but the settings may be missing or different. This is because, the Registry Editor is technically running as another user and that branch is User specific. You can see the two branches I’ve referenced in the following image.
Converting Configurations to ‘Computer’ Based
While you can edit the Registry manually, the easiest way to convert your Fabrication Configurations to be Computer based (not User) is to run the Registry Editor normally (not as Administrator) and export the HKEY_CURRENT_USER settings. The settings are in the key…
HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Fabrication <year>\ConfigurationThe <year> represents the version year of Autodesk Fabrication (CADmep, ESTmep, CAMduct, Remote Entry, etc.) or Revit. You can see that in the following image. If the Configuration key isn’t there, that means there’s no configurations “configured” for that version year. If a specific “year” isn’t listed, it means that version wasn’t installed.
Once you get to the Configuration Key, you can export it using the File -> Export option as shown here…
While you can Export a single configuration, I like to pick the Configuration Key and do them all. We can get rid of what we don’t want later. The main point to note when exporting is to change the Save as type: to the Win9x/NT4 Registration Files (*.reg) option. This will save the export in ASCII text which you can edit in Notepad.
Once you export to a file, you can right click on the file and select Edit to open in Notepad. The following image shows how it looks and is marked up what I’ve removed vs added/edited. Note I also edited the Registry Hive from HKEY_CURRENT_USER to HKEY_LOCAL_MACHINE.
Once you’ve edited the file and saved it, you’re almost ready to import it. It’s generally not advisable to have the same configuration with the same name and same path in both the HKCU and HKLM branches.
So first, you can run REGEDIT normally and rename the Configuration folder…or just delete it (if you’re comfortable doing so). Then close the Registry Editor and run it again but Run as Administrator. You can now Import the file you just edited to import those new Registry settings. The following image shows what both branches might look like…
Now, when you launch Fabrication (CADmep, CAMduct, ESTmep, etc.) you’ll see the little Yellow Lock icon on your configurations. Revit won’t show that little icon but it does honor the ‘User’ vs ‘Computer’ configurations.
A Word About Fabrication ‘Profiles’
One side effect of ‘Computer’ or machine based Fabrication Configurations shows up if you use Profiles in your Fabrication Configuration. It doesn’t apply to Revit but does CADmep, CAMduct and ESTmep. When you use Profiles with ‘User’ based Configurations, the last active profile will be the default when you launch the program again. With ‘Computer’ or machine based profiles, you’ll always default back to the Global profile.
However this is easily fixed. To start, let’s look at the ‘User’ based configurations under HKCU when a profile was used…
You’ll see there’s now an ActiveProfile value in the configuration that wasn’t there before. That’s how Fabrication knows which profile to load by default. But also remember, the HKLM branch of the registry is normally Read-Only. So this means those programs can’t create this value when you change profiles.
The solution to this, is making those registry keys Read-Write in the HKLM registry branch. You can do that by running REGEDIT as an administrator like before and navigating to the proper registry keys. From here, you can Right-Click on the Key’s name and select Permissions….
You can do this on a specific configuration or at the root Configuration key and the permissions will be inherited by the downstream keys. Once the Permissions dialog shows up, select the User permission group and select the Allow toggle for Full Control. Again, you may need your IT’s help if you don’t have permissions to do this.
This will now allow CADmep, CAMduct and ESTmep to save the last Fabrication Profile to the Registry in the HKLM branch so when you start the software the next time, it’ll be able to use the last Profile used.
One good side effect of changing these permissions…you’ll now also be able to import or create more Fabrication Configurations in HKLM in the future WITHOUT having to Run as Administrator as you’ll now have Read-Write permissions to those keys by default.
Make sure if you do these steps, to do them for all versions of Fabrication. You can even make entries for versions you don’t have installed so they work later if you install that version. So if you want to prepare for 2025 versions, you can copy/paste/edit those registry settings in the file you exported and rename them as 2025 (or older versions) all in the same file, Being proactive in this way will minimize future support downtime.
