

Creating a new deployment from the web, this seems relatively painless, until I try to edit it to use a custom .ini file and not install the library files, family templates, etc on each machine. We generally keep the imperial library on the network, as well as the templates, and all of that.
I have pointed it to a custom ini file and removed the install paths for those items. When I do that the install runs fine but it doesn't want to recognize the custom .ini and then even when i try to put the .ini in the right location I continuously get the "Path specified for Family templates is invalid" even after correcting it. It just won't honor the updates.
trying to figure out my best path forward to get this deployed
I'm running into the same problem after creating a deployment for 2021.1.2. I set everything manually on one machine installation, then closed out of the program, launched it again, and found that all the settings were gone once again! So apparently it's not writing/updating the .INI file at all?
So, the changes should technically be done there AND in the one thats in Program Data. If they arent, there is a chance something triggered Program Data to overwrite the Roaming AppData one. Been that way forever.
but how does one do that, and make it part of the Deployment?
I ran the deployment on another machine with the INI file in the "Deployment/Image" folder this time, and it appears to have worked.
You put it in the Deployment the same as you always have. All im saying is, the way Profiles are meant to work, the INI file in Program Data will (in some cases) write over the one in AppData Roaming. If your current status made it think it had to seed the User Appdata, the changes you made are gone. None of that is new.