Deploying Creo View and Customizing the Installation > Creating and Deploying a Customized Installer
  
Creating and Deploying a Customized Installer
You can add and remove applications from the Creo View installation. For instance, the users in your organization have the following needs:
Required
Not Required
Using Creo View client
Microsoft Visual Studio C++ 2017 Runtime Redistributable
Working with JT (*.jt) files
Viewing ECAD designs
In this case, you may want to customize the installer in these ways:
• Bundle the JT Import Filter with the Creo View installation
• Remove Microsoft Visual Studio C++ 2017 Runtime Redistributable because you have already deployed it. We will still deploy 2012 Runtime.
Accomplish the customization by performing two basic tasks:
1. Prepare the directory structure by adding and removing installer files.
2. Modify CreoSetup.ini to run the installers correctly.
After you complete these tasks, you can deploy the software. The procedures in the next sections contain instructions for completing the tasks above, and for and the deployment.
Preparing the Directory Structure
Follow the steps below to customize the installation directory.
1. Create an empty directory (<directory>).
2. Copy CreoView_64.exe into <directory>, and then right-click the file and choose 7–Zip > Extract Here. The setup files are extracted from the wrapper.
3. Delete CreoView_64.exe. These subdirectories and files remain:
◦ \prereqs subdirectory
◦ \pview subdirectory
◦ CreoSetup.exe
◦ CreoSetup.ini
4. Create a new subdirectory called \jtimport.
5. Navigate to the installation subdirectory on the JT DVD image:
cdimages/jtadapter/installers/
Copy CreoView_JT_Import_64.msi, and then paste them into the \jtimport subdirectory you created in step 4.
6. Under the \prereqs subdirectory, remove the two Microsoft Visual Studio 2017 C++ Redistributable x86 and Microsoft Visual Studio 2017 C++ Redistributable x64. They are called vcredist_x64_VS2017.5u8exe and vcredist_x64_VS2015u3.exe.
The directory is now ready. Continue to the next section to customize the INI file.
Modifying CreoSetup.ini
You have added an installer file to bundle the JT Import Filter with the Creo View installation. You must now modify CreoSetup.ini to make these changes to the default installation directives. You can delete unnecessary lines and sections from the file, or you can modify them. In this example, they are modified.
• Add new directives to run the JT installer
• Remove or disable the vcredist_x64_VS2017u8.exe directives.
Follow the next steps to update the INI file accordingly.
1. Open CreoSetup.ini in a text editor.
2. In the [Other Applications] section, find the line VC2017_X86=YES and replace it with VC2017_X86=NO, or VC2017_X64=YES and replace it with VC2017_X64=NO.
3. At the end of the [Other Applications] section, find these lines:
ECADADAPTERS_X64=YES
Modify them to call the JT installer instead of the Creo View ECAD Adapters installer:
JTIMPORT_X64=YES
4. At the end of the file, find the sections for the Creo View ECAD Adapters, such as the example below:
[ECADADAPTERS_X64]
PROGRAM=CreoView_ECAD_Adapters_64.exe
COMMANDLINE=/f /vADDLOCAL="ALL" REBOOT="ReallySuppress" /l*v
TempFolder]pvinstecadadapters.log" /qb!
LOCATION=..\ecad_adapters
; PRODUCTCODE=
PLATFORM=X64
Change the heading and information in the [ECADADAPTERS_X64] sections to information for the JT Import Filter, as shown in these example:
[JTIMPORT_X64]
PROGRAM=CreoView_JT_Import_Filter_64.msi
COMMANDLINE=ADDLOCAL="ALL" REBOOT="ReallySuppress" /l*v "[TempFolder]pvinstjt.log" /qb!
LOCATION=jtimport
PRODUCTCODE={E6438BA9-7C4D-4D54-A87D-65272F3169A6}
PLATFORM=X64
5. Save CreoSetup.ini and close the text editor.
You have now defined the installation in the INI file:
• For more information on locating the code for an application, continue to the next section, Finding the Product Code.
• For more information on the INI file, skip to the section Understanding the CreoSetup.ini File.
• To begin deployment, skip to the section Deploying with the Customized Installer below.
Finding the Product Code
This example uses the JT ProductCode for Creo 2.0 M020. Each release has a unique ProductCode. An application also has a permanent UpgradeCode. The UpgradeCode is not used by CreoSetup.exe because it does not identify the version of the application. You can find the product code for the applications to install by using the Registry Editor. On a computer where the application is already installed, navigate to the registry key.
* 
Do not modify the registry. Doing so can severely damage your computer.
1. Open a command prompt, and then type regedit.
2. Press ENTER. The Registry Editor opens.
3. On the left, navigate to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
4. Find the application to install, and copy the key, including the curly brackets. These are examples of the registry keys for Creo View 2.0 M020 JT Import Filters:
◦ 64–bit—{E6438BA9-7C4D-4D54-A87D-65272F3169A6}
Understanding the CreoSetup.ini File
Each application in the file’s [Other Applications] section has a YES or NO value. A YES value does not necessarily mean the application’s installer will always be executed. Instead, each application with a YES value is a potential installation. If your system has an installation that matches the product code line, then nothing is done. If your system does not have a matching installation, the application is installed.
The PRODUCTCODE line for each application is optional. In all cases, the application is installed automatically when your system does not have the same version installed. Providing a product code minimizes the time the installation takes to complete.
The value for the PROGRAM line must be a *.exe file or a *.msi file.
Deploying Creo View with the Customized Installer
You have now prepared the directory and modified the INI file. In this example, deploy the applications with a passive installation. You may use one or both of these strategies:
• Run CreoSetup.exe directly from the network location.
• Create a new, self-extracting archive from the modified directory. Make sure the self-extractor calls CreoSetup.exe to chain all the installations to deploy.
The call to CreoSetup.exe must include, in the command line, all MSI arguments for the base Creo View installer. At this time, you cannot embed the Creo View MSI arguments directly in CreoSetup.ini.
To perform the passive installation, open a command shell and enter the following command:
CreoSetup.exe /vADDLOCAL="ALL" APPLICATIONFOLDER="C:\ptc\Creo View" LICENSESERVER=”7788@licsrv.example.com” /qb!
* 
Make sure there is no space between /v and the next character in the command.
Creo View and the JT Import Filter are installed with a progress bar, but no Cancel button. For more information on common examples of options for a silent installation, see Deploying Creo View Using a Silent Installation.