Basically, you should create a script to install/uninstall Creo Parametric (preferably silently). That script is then used in the SCCM application development.
Here are some items that will help in the creation of a script that can be used in a SCCM deployment application:
1. Avoid any user specific setup in the install script. The SCCM deployment will typically run as the client PC local "SYSTEM" account, not under the user's account. If you use %USERNAME% in any scripts, the variable will resolve to the SYSTEM account, not the user account. Additionally, the SYSTEM account doesn't have a C:\users area like a normal user account.
2. Avoid any queries for logged in users in the install script. With SCCM, you can push the software to the client PC whether there are any users logged into the PC or not. If you must have a user logged in, make the SCCM application a "pull" only.
3. Avoid any dialogs requiring user response to continue in the install script. With SCCM, you can push the software to the client PC whether there are any users logged into the PC or not. Any dialogs requiring user response when there is no user to respond will cause the installation to hang. If you must have a user logged in, make the SCCM application a "pull" only.
4. Consider separating the installation of the pre-requisite programs. One of the pre-requisite programs is .NET framework. The installation of .NET framework often requires a system reboot. The pre-requisite programs can be installed via a separate SCCM package that is defined as a requirement for the Creo Parametric SCCM package.
5. Use exit codes in your script. The SCCM program will evaluate the exit code of the script.
6. Try to incorporate an uninstall option in the script. SCCM can uninstall the software as well. It's easier to use a single script with command line options vs. creating two individual scripts.
7. If your SCCM package is setup to copy the source files to the user's PC and run the install locally (this is very typically), separate the install and uninstall folders in SCCM. The uninstall does not require the source files, only the install/uninstall script, so uninstalls will be faster because multiple gigs of data doesn't need to be copied to the SCCM cache area.
8. Use a log file to record script activities to help with debugging installation failures.
9. With newer installs of Creo Parametric (from 8.0 and higher I believe), a separate Java installation may be (or will be) required. Your company likely has specific Java requirements to meet security requirements. You should work with the SCCM application/package development folks regarding java installations.
10. PTC has instructions for creating an automated installation that can be used as part of your install/uninstall script. If you're comfortable with that method, use it. You can always create your own automated installation using CMD, powershell, AutoIT, perl, etc.
11. Create the installation for multiple business areas, geographical locations, etc. that have separate configurations like license servers etc. incorporating those into your installation script using command line options to control the installation. You can use features within SCCM to determine who the user is, what machine they are using, etc. That information is used within SCCM to determine which deployment type to use for installing the software.
