SCCM scripts don't include custom support paths?

[Anonymous]

I've created a deployment with the settings we need for our environment.  There are a lot of custom support paths built into the deployment.  When running the shortcut in the root directory of the deployment that goes to the setup.exe, everything works great.

I'm attempting to make a better installation script for use with SCCM and I'm using the script under the "SMS_SCCM scripts" folder, but I notice that when all of those installs run (which they do all run successfully), none of the custom support paths I built into the deployment are added.

Do I need to add an additional parameter to use the deployment's INI file in order for those custom support paths to get loaded?  I don't want to have to export settings from the registry, because each time the deployment is changed I'll also have to update the SCCM install, which causes more work...

Currently working with AutoCAD 2015, but will need to reproduce this with some older versions of AutoCAD.

Thanks!

[dgorsman]

Do you mean the support file search paths (SFSP) in each AutoCAD profile?  Or are you referring to the actual folders and contents?

[Anonymous]

The support file search paths.  The actual folders and contents are on network shares in our environment.

I'll explain in more detail:

When creating the deployment, you get to the screen where you select which components you want to install.  Under Autodesk AutoCAD 2015, I hit the down arrow.  Scrolling down on that page, I can see the Search Paths and File Locations.  I have added several network folders into these sections (some under Support File Search Path, some under Printer Support File Path, and some in various other areas.  Then I finished creating the deployment.

When running the setup.exe with the flag specifying the INI file:

\\domain.com\Deployments\AutoCAD_2015\Img\Setup.exe /qb /I \\domain.com\Deployments\AutoCAD_2015\Img\AutoCAD_2015.ini /language en-us

Those paths are set correctly when opening AutoCAD 2015.

When installing each of the components separately, as specified in the SCCM text file under the "SMS_SCCM scripts" folder, these support paths do not appear to be set.

[dgorsman]

Double check that the correct profile is being started with AutoCAD.  But I wouldn't worry too much about doing that through SCCM, leave it for software distribution and basic set-up.  \You can use ARG files to specify initial profile settings, although you can also merge REG files after the secondary installer runs.  Use those initial settings to point to automation inside AutoCAD for managing the paths (ie. stored as data on your network), so that once the user is running you can make any changes you need and there is no need for anyone to do anything extra.

[Anonymous]

Can you explain that part about ARG files to specify initial profile settings in a little more detail?  Is there a way to dynamically build this based on the deployment?  i.e. if I update the deployment and add more SFSP, will this SCCM install automatically update the initial profile for new installs to match those, or will I have to re-generate ARG files and registry settings each time I update that?

I'm trying to not have to double the amount of work to manage these...

[Anonymous]

Well, from everything I've tried, I'm unable to have our custom search support paths in this install.  I guess I'll just have a batch script that launches the setup.exe with the INI file as a configuration to make this work.  It's not how I'd prefer, and it causes an issue with our configuration system, but if it's the only way to have those then so be it!  Thanks for your help.

[m_latz]

The SCCM batch script files you mentioned earlier are only samples for your installation.

That you have the same result as your created deployment you have to call the msi packages with the transformations (.mst files) that are generated during the creation of your deployment.

regards

Markus