Chapter 3 - CATIA Local Installation
On This Page
Preparing for Local Installation
If you have chosen to install CATIA V5 software locally, you must set up the software on each workstation where design will take place. You have the advantage that CATIA will run quickly because all of its code is located on the local computer and CATIA will generate relatively little network traffic. However, many local installations may increase the administrative overhead of a CATIA system. See Chapter 2, Planning a CATIA UNIX to Windows Migration, for a detailed discussion of these issues.
There are a number of techniques to choose from that can speed and automate local installations, and each is described in this chapter. In addition to installation, the management of CATIA V5 software involves upgrades, rollbacks, and sometimes running more than one version of CATIA on the same workstation. These topics are also described.
The chapter is divided into two major sections. Use the first, Preparing for Local Installation, to select the techniques to use and to plan your approach. Then find step-by-step example procedures for the tool you have selected in the "Methodologies" section.
Preparing for Local Installation
Need for Packaging
If your organization is small, or CATIA is used by a small number of your workers, it is practical to install CATIA manually. Up to 10 computers can be reasonably managed this way, but the repetitive nature of the setup and subsequent administration may persuade you to use a packaging and distribution approach. If you decide on manual installation, see Single Workstation Installation in the "Methodologies" section for a walk-through of the process.
In a large organization, manually installing CATIA V5 on all workstations is not practical. Either users must perform their own installations at the risk of incorrectly configuring the system or the administrator has to install the product on each workstation.
A better solution is to automate installation of the product from a server, without any user intervention. To achieve this, the CATIA installation must be packaged to create a manageable unit for installing onto client computers. Such a package includes all CATIA files and instructions for installation and configuration. Tools for creating packages are described in the following section.
Once you have created a package it must be deployed to users workstations. The methods available are covered in the section titled A Comparison of Deployment Techniques.
A Comparison of Packaging Tools
Several tools for creating a CATIA package are described below. When making your choice, consider the following:
Budget. SYSDIFF, WinINSTALL LE, and MSITool are free, and Silent Installation, or Unattended installation, is a feature of CATIA itself. However, if you also require advanced management features or have large numbers of workstations, you will also need Symantec Ghost or Microsoft SMS.
Installation Time. Several of the tools described, such as Symantec Ghost, decrease the time that is needed for installation. Installation time will be important if you need to install CATIA on many workstations.
Server Disk Space. Any package that includes CATIA will require a large amount of disk space to store. If the package includes an operating system as well, the problem is compounded.
Convenience. Although SYSDIFF, for example, is free, it requires a fairly complex setup with many command line steps. The equivalent procedure in SMS or Ghost AutoInstall is less complicated and includes a GUI to help you.
Other Applications. You may wish to roll out other applications along with CATIA. Many of the tools allow you to create a package containing multiple applications, but Silent Installation, or Unattended installation, can be used only for CATIA.
Hardware. If an image includes a computers hardware drivers and configuration, the target computers must have the same hardware as the computer of which the image was created. A Ghost image, for example, can be deployed only to computers with identical hardware.
Silent Installation/Unattended Installation
CATIA V5 setup supports Silent Installation (based on Installshield) until R10, and it is replaced by use of the StartB batch installation command beginning with R11. In the Silent Installation approach, an installation of CATIA on a client computer is automated by providing an answer file that contains information on the desired configuration. Because this file answers the questions usually asked during installation, the process can proceed without being monitored by an administrator.
The process has two stages: In the first, the CATIA Setup program is run with r option. This runs the usual installation wizard but stores the users answers in a file called, by default, Setup.iss. In the second stage, performed on many computers around the network, Setup is invoked again with a switch to point to Setup.iss. This setup runs without requiring any input from an administrator.
With the Unattended installation approach using the StartB installation command, CATIA can be installed without the graphical user interface. In the first stage, the software is copied to a folder in the source computer, or the CDROM is simply made available in the network. In the second stage, setup is invoked in client computers using the StartB batch command with the required switches. This process installs the application without user intervention.
The package needs to be kept in a shared folder so that the files are available to many client computers.
SYSDIFF.exe is one of the deployment tools provided in the Windows Resource Kit and as a download from the Microsoft Web site. You can use it to include an application, such as CATIA, in the installation of a desktop operating system. It can be used with Microsoft Windows NT 4.0 and Windows 2000.
The process is as follows: The Windows installation files (the i386 directory from the Windows CD) are copied to a shared folder on a server, known as the Distribution Server. A desktop computer, known as the Master System, has Windows installed on it. SYSDIFF.exe is used to create a difference file that records the changes made to the Master System by the installation of desktop applications, which may include CATIA. SYSDIFF.exe is then used to apply these changes to the shared installation files on the Distribution Server. When unattended installations of Windows are later run from the Distribution Server, they will automatically include the applications originally installed on the Master System.
This tool is normally used to distribute CATIA only on to newly installed desktop computers and only if the installed operating system configuration matches the OS configuration of the Master System. However, it can automate the installation of all the applications to be installed on desktop computers in one operation.
A master system with Windows NT 4.0 or Windows 2000 installed.
A share on the Distribution Server for the Windows i386 installation directory, the difference file, and auxiliary files. This share must have sufficient space for all the applications to be installed.
Symantec Ghost Disk Imaging
Symantecs Ghost application clones a disk drive or partition on a master system. This can be stored in an image" that you can copy to other desktop computers known as target computers. The image includes the operating system, all installed applications, and configuration information. Imaging speeds the installation of the operating system and removes the need for separate application installations. By installing CATIA on the master system before the image is taken, you can distribute CATIA with the other applications.
Symantec also provides the Ghost Console administrative application, which is a tool that allows centralized control of image distribution. See the discussion of this tool in the Deployment Options section that follows.
One clean personal computer with a hardware configuration that is identical to the client's hardware configuration and that has CATIA V5 installed. This will be the master computer.
At least one server and one client computer
A Symantec Ghost Server Console on the server
Symantec Ghost AI Packaging
AutoInstall (AI) is a tool provided with Symantec Ghost, as described earlier. It allows you to create a package to distribute one or more applications, including CATIA, onto existing operating systems. This package can then be distributed with the Ghost Console just as images are distributed.
AI packaging can be used to distribute application updates. Once installed, these packages can be removed quickly using the Ghost Console application.
The process involves taking snapshots of the system before and after installing the application. The recorded differences constitute the package.
The AI packager needs Symantec Ghost Console for deployment across the network.
AI Builder and AI Snapshot must be installed on a model computer.
The model computer should have a configuration similar to those that will receive the finished AI package.
In Windows 2000 and later, the preferred method for installing applications is with .msi files and the Windows Installer Service. This service finds instructions for installation within the .msi files. Applications installed from .msi files can be automatically repaired and smoothly removed by the service.
The Windows Installer Service can be invoked by simply double-clicking on an .msi file, or Group Policy can be used (see Deployment Options later in this chapter).
Unfortunately, CATIA does not include an .msi file for installation. However WinINSTALL is an application that can create these using a snapshot procedure. Now owned by OnDemand Software, WinINSTALL was previously a VERITAS product. A free version, WinINSTALL LE, ships with the Windows 2000 Advanced Server CD. Fully featured versions are obtainable from OnDemand.
A server or workstation that contains the Discover program (part of WinINSTALL).
A minimum of 15 MB of free hard disk space on the server or workstation for the installation of WinINSTALL.
Additional hard disk space for the application that is repackaged.
A workstation to create the package. The ideal reference computer (where the package will be created) is a clean machine, that is, one with only the operating system installed.
These two computers must be part of the same network.
WinINSTALL cannot create .msi files for an installation of more than 32,767 files. Therefore, some options, like AL2 in CATIA, cannot be made into a package properly.
MSITool, provided by Microsoft, can be used to create Windows installer packages and is thus a similar approach to WinINSTALL.
This tool creates a Microsoft Windows Installer (MSI) database for a single feature install. By pointing this tool at a desired directory and following a few easy steps, you can produce an .msi file, which may then be used to perform installations. Having installed CATIA on one computer, you can then use the tool to create an .msi file from the CATIA directory.
MSITool supports a sophisticated system that allows environment variables, registry entries, and product properties to be set during an installation. MSITool provides an XML-based method for setting up these capabilities. With an ASCII editor such as Notepad, you can edit the example XML files provided with the tool to implement these capabilities.
A package created in this way can then be easily fine-tuned by using an MSI database editor such as Orca.exe. This editor, downloadable from the Microsoft Web site, displays and edits the instructions contained in an .msi file and can also validate the database.
To get the latest MSITool, contact the Application Development Service Line in the U.S. National Practices through your local Microsoft Consulting Services practice at http://www.microsoft.com/services/microsoftservices/default.mspx, or contact Infosys at email@example.com.
Systems Management Server
Microsoft Systems Management Server (SMS) was designed as Microsofts primary tool for software distribution. SMS can significantly reduce the time and complexity of maintaining and upgrading software for organizations with distributed networks. You can use SMS to install software and upgrade and configure each computer from either a central location or from multiple locations. Individual software files or software application suites can be scheduled and distributed to specific computers. SMS even enables initiation of automated, unattended software distribution to selected computers.
Systems Management Server 2.0 offers greater control and flexibility in software distribution than its previous versions. Built-in functionality includes the option to force a package to run using a specified account with administrative rights on the target computer. This is necessary when distributing to clients who either are not logged on or when the logged on user does not have local Administrator rights on the computer.
SMS includes its own packaging tools that can be used to package an entire operating system image, including applications such as CATIA. Alternatively, it can create packages containing just CATIA, similar to a Ghost AI package. If you use SMS to create a CATIA package, you must also use SMS as the deployment technique.
In addition to its software distribution features, SMS has advanced asset management that allows you to catalog and track software and hardware and troubleshoot remotely.
A Comparison of Deployment Techniques
After you have created a package, the next step is to deploy it onto desktop computers. Below are detailed descriptions of the distribution techniques. When selecting one, consider the following:
Packaging Tool. Some packages require the use of their associated deployment tools. For example, a Ghost AI package should be deployed with the Ghost Console.
Convenience. Rshmsisvc (described later in this chapter) requires several setup stages on the destination computers, knowledge of batch files, and knowledge of command line techniques. SMS, by contrast, has a simple client setup and a GUI for ease of use.
Versatility. Group Policy (described later in this chapter), for example, allows you to define a small number of computers out of your entire enterprise and to determine where CATIA will be installed, all from a centralized administrative interface.
Active Directory/Group Policy
Microsoft Active Directory is a part of the Windows 2000 network architecture. It provides a directory service designed for distributed networking environments. Active Directory provides efficient sharing and management of information about network resources and users. It also acts as the central authority for network security, letting the operating system readily verify a user's identity and control their access to network resources.
Windows 2000 (and later versions) and Active Directory provide a tool named Group Policy that can deploy applications. By using Group Policy, you can assign software to users and computers based on their location in the directory (for example, organizational units, sites, or domains). The requirements to deploy software with these components are:
Microsoft Windows 2000 or Windows XP clients. The Group Policy infrastructure is available only on these two operating systems from Microsoft. Earlier Microsoft operating systems cannot use software that uses this technology.
Active Directory. To assign software throughout the enterprise, Group Policy settings within Active Directory need to be configured.
Group Policy is highly flexible and can roll out software to closely controlled groups of users or computers. It is not suitable for deploying SYSDIFF installations, Ghost Images, or Ghost AI Packages.
Group Policy is easiest to use in conjunction with an .msi file. Because CATIA does not include an .msi file, you must create one using WinINSTALL. If this is not possible, you could create a batch file to perform a Silent Installation or Unattended installation of CATIA. Group Policy can be used to run such a batch file on users computers.
Remote Installation Services
The Remote Installation Service (RIS) is one of the new enhancements in Windows 2000 that provides a means to install pre-configured client workstations across the network. RIS distributes images of operating systems and installed applications, on to client computers and, thus, is a similar approach to the Symantec Ghost Console. It cannot be used to deploy .msi files, Ghost Images, or Ghost AI packages because it uses its own images. RIS can only be used to install Windows 2000 Professional or Windows XP images.
RIS requires several other services that are also shipped as part of the Windows 2000 Server. These services can be installed on individual servers or on a single server, depending on the network design:
Domain Name Service (DNS) Server. Remote installation relies on DNS for locating the directory service and client computer accounts. Any Windows 2000 Active Directory service-compliant DNS server or the DNS server provided with Windows 2000 Server can be used.
Dynamic Host Configuration Protocol (DHCP) Server. RIS requires a DHCP server to be present and active on the network. The remote boot-enabled client computers receive an IP address from the DHCP server before contacting RIS.
Active Directory. RIS relies on Windows 2000 Active Directory for locating existing client computers as well as existing RIS servers. RIS must be installed on a Windows 2000-based server that has access to Active Directory. This can be a domain controller or a server that is a member of a domain with access to the Active Directory.
Shared Folder Space. The drive on the server where RIS is installed must be formatted with the NTFS file system. RIS requires a significant amount of disk space and cannot be installed on the same drive or partition on which Windows 2000 Server is installed.
Symantec Ghost Console Server
Symantec Ghost Console is used principally to deploy Ghost Images and Ghost AI Packages, although it can also distribute files or run commands on remote computers.
The use of such images and packages makes it possible for companies to do remote management of all networked computers effectively. Using the Symantec Ghost Console, you can perform a number of tasks to manage computers. From the Console server, it is possible to:
Roll out software.
Upgrade operating systems.
Migrate user settings.
Execute commands remotely.
An administrator can efficiently manage the networked users by grouping them within Symantec Ghost Console.
If you have created a Ghost image or AI Package that includes CATIA, this is the preferred method of deployment to the desktop.
Systems Management Server
SMS includes advanced and versatile options for the deployment of packages. If you decide to use the SMS packaging tool for CATIA, it must also be used for deployment. It can, however, be used to deploy MSI packages, such as a CATIA package created with WinINSTALL.
The Rshmsisvc is a service developed by Microsoft that assists in the deployment of software and subsequent updates. The service resides on client computers and can be installed by using Active Directory. (The installation can be done during startup). The service possesses administrative privileges and executes commands based on a triggering event. The triggering event is generated by the update of a specified text file (trigger script) that resides locally on the clients.
Rshmsisvc can be used to distribute .msi packages or to run a silent CATIA installation.
To get the latest RshMSISvc, contact the Application Development Service Line in the U.S. National Practices through your local Microsoft Consulting Services practice at http://www.microsoft.com/services/microsoftservices/default.mspx, or contact Infosys at firstname.lastname@example.org.
Deployment of Service Packs, Hotfixes, and Rollbacks
When CATIA is installed locally on workstations, any Service Pack or hotfix must be applied to all those computers, much like the initial installation. Again, if you have a small number of computers, you can install the Service Pack or hotfix manually on each. In larger enterprises, you can roll out the update by using the same package and deployment method you used to install the application.
Note: The rollout of an entire operating system image to many computers just to apply a small incremental hotfix is impractical. A very large amount of network traffic would be created, and the process may take many hours to complete for all clients. Those solutions that can package just the update, such as WinINSTALL, Ghost AI, or SMS packaging, are much more appropriate.
Rollback is the removal of CATIA, perhaps because of a change in a users role, licensing requirements, or strategy. When CATIA is locally installed, the user must use the software management tool provided with CATIA V5 on the workstation, or Add/Remove Programs from the Control Panel. If the software has been installed with a Ghost AI package, however, the Ghost Console can be used to remove it.
Single Workstation Installation
The following step-by-step procedure describes the desktop computer installation of CATIA V5R10.
On each workstation:
Browse the CATIA CD-ROM.
Select the language in the drop-down list.
In the Welcome dialog box, click Next.
In the CATIA V5R10 License dialog box, click Next.
Select the destination directory in the Choose Destination Location dialog box and click Next.
Select the location for the environment file and click Next.
Select Complete or Custom setup and click Next.
Select the required languages and click Next.
If you chose to implement a custom configuration in the Setup Type dialog box, then select the desired configuration and click Next.
Retain the default configuration values presented in the Choose Orbix Configuration dialog box and click Next.
Retain the default configuration values presented in the Set Up Communication Ports dialog box and click Next.
Select Online Documentation if you need to install it, and then click Next.
Review the configuration parameters presented in the Start Copying Files dialog box and click Next.
Click Finish when the Setup Complete screen appears.
Note: If you are installing CATIA V5 for the first time, the system may need to be restarted.
Packaging options include Silent Installation/Unattended installation, Symantec Ghost and WinINSTALL. This section also includes a discussion of SYSDIFF as an option to capture "before" and "after" snapshots. The following sections describe the procedures for each.
Silent Installation/Unattended Installation
A silent installation package, which is supported until CATIA V5R10, creates a Setup.iss file along with the usual setup files provided by the application. This file can be used to automate later installations of CATIA.
The detailed steps to create the silent installation package are as follows:
Copy the CATIA V5R10 code to one workstation or server (for example, in c:\CATIA V5R10Code).
Run the installation with the r option:
The installation proceeds automatically and the results are the same as those achieved in a manual installation when the default options are chosen.
This automatically generates a silent installation file or a response file, which is a record of the installation inputs, located by default in the Windows folder (in Windows 2000 it is C:\Winnt). The default name of the file is: Setup.iss.
An alternate location can also be specified, for which the response file can be created using the following command:
Setup.exe -r -f1path_name\ResponseFile
where path_name is the pathname of the folder containing the response file, and ResponseFile is the name of the response file, which in this case is Setup.iss.
Copy the response file from the Windows folder to the folder where the Setup.exe file resides.
Locate the Setup.ini file in the setup folder, edit the file, and change the line
EnableLangDlg = Y
to <pre IsFakePre="true" xmlns="http://www.w3.org/1999/xhtml">
EnableLangDlg = N
This will ensure that the installation runs in silent mode without invoking the graphic user interface. This step completes the creation of the package.
To install the package, create a batch file in the same folder (for example, CATIA V5R10Install.bat), containing the following command:
Setup.exe -s -f2path_name\LogFile -f1path_name\ResponseFile
where path_name (after -f2) is the pathname of the folder and LogFile is the name of a file for logging the installation. The path_name and ResponseFile variables after f1 are the values determined earlier in this procedure. The default log file name is Setup.log. This file will be used by the Setup.exe program when distributing CATIA V5 to other computers. You can change the destination folder for installation by modifying the Setup.iss file.
In CATIA V5 R11, Silent Installation is replaced by the StartB batch installation command. Note that Online documentation cannot be installed using this approach. The detailed steps to create the StartB installation package are as follows:
Copy the software to the source computer and share it in the network, or simply make the CD-ROM available in the network
In the computer where you want to install CATIA, connect over the network to the source computer containing the software using Explorer and map a network drive to the shared folder.
At the command prompt, from the INTEL folder run the following batch command:
Use the appropriate arguments:
Specifies the unload directory; make sure the directory path is enclosed like this: "unload dir" if the directory name contains spaces; the default unload directory is:
C:\Program Files\Dassault Systemes\B11
Creates an identifier used for differentiating multiple versions of the same release installed in different locations on the same computer.
Creates the unload directory if it doesn't exist.
Specifies the environment directory; the default environment directory is:
C:\Documents and Settings\All Users\Application Data\DassaultSystemes\CATEnv
Specifies the path and name of the nodelock license certificate to import.
Runs a Version 5 session at the end of the installation.
Specifies the Orbix daemon port number.
Specifies the starting port number for daemon-run servers.
Specifies the range for daemon-run servers.
Adds required privileges for Orbix for current user if they are missing.
-backbonePorts port3 port4
Specifies the ports reserved for the communication backbone; default values are 6666 and 6667.
Specifies the port reserved for processing events when using peripheral devices (spaceball, spacemouse, joystick); the default port for the peripheral device broker is 6668.
Specifies you do not want to set up any communication ports.
-CatiaV5Info/-CatiaV5Path Path -CatiaV5EnvPath Path -CatiaV5EnvName EnvName
Options for CATIA V5 ENOVIA V5 LCA interoperability.
Used alone, setup takes default values for other parameters.
Specifies CATIA V5 Installation path.
Specifies CATIA V5 Environment path.
Specifies environment file for CATIA V5.
Lists the configurations and products on the CD-ROM.
Unloads all the configurations and the products on the CD-ROM
Specifies the list of configurations and/or products to unload. You have to type the list of configurations and/or products, which you can obtain by running the command using the list argument. In the list, configuration names look like this: ME2.slt, and product names look like this: KIN.prd. These are the names you must type. Separate the names using a space.
The arguments -list**,**
-all and -l "list_to_unload" are mutually exclusive.
-noLang "fr ge it jp ch"/-noLang all
Specifies user doesn't want to install language user interface files for French, German, Italian, Japanese, Simplified Chinese.
Specifies user does not want to install language-indexed fonts.
The system will not be restarted if needed.
Updates the system DLLs if needed; your computer will be rebooted if the system DLLs are updated.
If used without arguments, it updates the file
with the default communication port numbers, even if the lines already exist in the file; if used with arguments, it can also be used to specify other port numbers.
VBA is not installed automatically by using the **StartB** batch command. To install VBA, run the following command: msiexec /q /i *pathcdrom*\\VBA\\VBA6.msi where *pathcdrom* is the path of the shared folder in the source computer. **SYSDIFF** This tool can be used to include the installation of CATIA and other applications during the installation of the operating system on a desktop computer. **Follow this procedure to use SYSDIFF:** 1. Install Windows on the master system. Wait to install applications until step 5. 2. On the master system, map a drive letter to a share on the server (for example, map X:\\ to D:\\BIN). 3. At the server, copy the SYSDIFF.exe and SYSDIFF.inf files in the Support\\Deptools\\Platform directory on the CD-ROM to D:\\BIN. 4. At the master system, run the **SYSDIFF.exe** application: SYSDIFF /SNAP X:\\*before.img* where *before.img* is the snapshot file name (it can be any 32-bit valid filename). This command takes a snapshot of the system, files, and settings. After the snapshot is completed, **SYSDIFF.exe** displays the message "Snapshot complete." 5. Install CATIA V5 on the master system. 6. Configure the CATIA V5 application by, for example, setting default directories, toolbars, and preferences. **Note:** Before performing the next step to create the difference file, reboot the master system to ensure that all functions relating to the application installation are completed and all files are closed. 7. Run the following command on the master system: SYSDIFF /DIFF X:\\*before.img* X:\\*after.img* where *before.img* is the snapshot file, *after.img* is the name of the difference file to be created, and *X* is the shared drive. **SYSDIFF.exe** takes a snapshot of the entire system again, compares the new snapshot with the old one, and writes the difference file. The difference file includes the changes in directories, files, Registry, and .ini files. After the difference file has been written to the disk, **SYSDIFF.exe** displays the message "Diff complete." 8. On the target system, map the path of the snapshot difference file (D:\\BIN folder on the server) to, say, the U drive. 9. To apply the difference file to the target system, run the command: SYSDIFF/m/apply *U:\\after.img* where *U:\\after.img* is the difference path and file name. **SYSDIFF.exe** copies all the files to the target system and then makes the necessary changes in the Registry and .ini files. **Symantec Ghost Disk Imaging** **The following procedure explains the use of Ghost to create an image for subsequent distribution.** On the server computer: **Note:** The user should have administrative rights for the domain selected. 1. To open the Ghost Console on the server computer, click **Start**, point to **Programs**, point to **Symantec Ghost**, and then click **Ghost Console**. 2. Select **Remote Client Install** from the **Tools** menu. 3. In the **Remote Client Install** dialog box, select the client computer on which to install the remote client and click **Install**. The remote client needs to be installed on the source computer used for disk imaging. 4. An authentication window appears. Enter the required **User name and Password**. The remote client will be installed on the client computer. 5. From the **File** menu, point to **New** and select **Image Dump**. 6. Enter a name for the task in the **Properties for New Task** dialog box. 7. To enter the name of the client computer in the Properties for New Task dialog box, click **Browse** in the **Source machine** area. Browse for the folder where image file will be saved and enter the name of the image file. Keep the other default values presented in this dialog box and click **OK**. 8. A new task with the name you assigned it is created under **Tasks**. Right-click the name of the task you created and click **Execute task**. 9. A confirmation window appears. Click **Yes**. 10. A message box indicating the start of the task appears. Click **OK**. 1. The source computer will reboot and will enter into the Ghost Imaging mode. 2. The progress of this process is shown on the progress bar at the bottom of the window on the server. 3. When the task is finished, the image is stored in the location identified in Step 7. **Symantec Ghost AutoInstall Packager** Symantec Ghost AutoInstall (AI) has two components to help create and customize AI packages. AI Snapshot creates an installation script that records the changes to a model computer when the software is installed. AI Builder uses the installation script to create a package that duplicates the changes made by the software installation. It also customizes the package according to users' needs while packaging. Once created, packages can also be modified. **Follow these steps to create the package.** 1. Ensure that no programs are running. To select **AI Snapshot**, click **Start**, point to **Programs**, and then click **Symantec Ghost**. 2. In the Symantec Ghost AI Snapshot dialog box, click **Next**. 3. Select the drives to be scanned (in this case, the drive where CATIA will be installed and the Windows drive) and click **OK**. The AI Snapshot will proceed through the system checks. 4. After the system check, the wizard prompts for the setup program of the application that needs to be installed (in this case, CATIA). Assuming the installation is done from a CD-ROM, click **Next**. Insert the CD-ROM and go through the installation of CATIA. 5. After the installation is complete, enter a name for the CATIA package to be created. (In this example, it is CATIA V5R10.) Then click **Compare**, which starts the second system check. 6. After completing the system check, the tool indicates successful creation of the configuration file. This configuration file, if needed, can be changed later using AI Builder. Click **OK**. 7. Click **Build** in the **Ready to Build** dialog box. 8. The package will be built in the path specified. Click **Finish**. This package, if needed, can be customized using the AI Builder now. **WinINSTALL** The following procedure describes the process for creating an .msi file using WinINSTALL. **Note:** The procedure describes the VERITAS version of WinINSTALL. The VERITAS WinInstall tool was recently purchased by OnDemand Software. Install WinINSTALL LE. However, do *not* install the application on the *personal computer* that is going to act as the package creation computer in case the program itself affects the installation of the applications. **Perform the following procedure to create the 'Before' Snapshot prior to installing the application.** 1\. Log on as an Administrator to the reference computer. 2\. Run the **Discover** Wizard from the distribution server (do not map a drive and do not use the **Run** dialog or Network Neighborhood): \\\\WINSERVER\\Program Files\\Veritas\\Winstall\\DiscoZ.exe 3\. When the wizard starts, click **Next**. 4\. Enter a name for the package (the name of the software for which the package is being created), specify a path for the .msi file (make sure it is on a drive other than one that forms part of the package, and select a new empty directory), and click **Next**. 5\. Select a drive for the temporary files and click **Next**. 6\. Select and then add the drives that the Discover program should scan and then click **Next**. Several drives can be selected, but each drive is time-sensitive, and so it is better to select only those drives where changes are expected. For example, if CATIA V5 is installed in the D drive, select the D drive (where the application is installed) and the C Drive (where the operating system is loaded). 7\. Select the files and directories to be excluded from the scan and click **Next**. This has to be done for all drives selected for scanning. 8\. In the **WinINSTALL Discover** dialog box, check the **Enhanced Registry Scan** option and click **Next**. The WinINSTALL LE Discover program will then start. 9\. After the program is completed, the **Launch Application Setup Program** wizard appears. It prompts for a setup program to run. This is the legacy CATIA V5 application for which an .msi file must be created. Click **OK.** 10\. Browse through the Explorer window, select the setup program to run, and click **Open**. 11\. Continue the application setup as per the normal local installation procedure. **The following procedure describes taking the 'After' Snapshot (after the application is installed).** 1\. Log on to the reference computer as an Administrator. 2\. Run the **Discover** wizard from the distribution server (do not map a drive or use the **Run** dialog or Network Neighborhood): \\\\WINSERVER\\Program Files\\veritas\\Winstall\\DiscoZ.exe" 3\. The wizard detects that a 'Before' Snapshot exists and displays the application and path of the .msi file. Check the **Perform the After' snapshot now** option and click **Next**. The check will begin on both the registry and the file system. 4\. Potential problems, if any, will be displayed. Click **OK**. 5\. After the check is completed, a wizard displaying the message **The After snapshot is complete** will appear. Click **OK**. 6\. If the conversion of the .nai file to MSI package is not successful, follow steps 7-10 to convert the .nai file to MSI package. 7\. From the **Start** menu, point to **Programs**, point to **Veritas Software**, and then click **Veritas Software Console.** 8\. Right-click **Windows Installer Package Editor** and select **Convert NAI to MSI.** 9\. In the NAI to MSI Converter wizard, select the .nai file (a CATIA file) to be converted and enter the name for the .msi file to be created. 10\. It is possible to fine-tune the created package using the Seagate Software Console Microsoft Management Console (MMC) snap-in. From this application, select **Open** from the **File** menu to change and view the files and registry components. Click **Save** after any changes. 11\. After you have finished this process, place not only the .msi file but also all files and subdirectories in the directory chosen for the .msi file in the distribution server. **Systems Management Server** **Follow this procedure to create a package with SMS Installer, available with SMS.** 1. Set up a clean reference computer. 2. Install SMS Installer. 3. From the **Start** menu, point to **Programs**, and then click **SMS Installer.** 1. The SMS Installer dialog box opens to let you select installation attributes. The dialog box lists them on the left. Each installation attribute has several configuration options. The icons on the right side of the dialog box represent these options. Click **Repackage**. 2. In the **Repackage Installation** dialog box, specify the setup program you want to run. You can supply command-line options for the installation. Before the installation starts, SMS Installer takes a snapshot of the reference system's hard disk. The **Repackage Installation** dialog box lets you tell the program which disks to scan. Even if you plan to install the software on the D drive, make sure to also scan the drive that holds your OS files because many programs dump files into the OS directory. Scanning all the subdirectories is optional, but it's a good idea. You can exclude parts of the Registry from the scan. 3. Click **Next** to start the setup process. The scan process starts immediately. SMS Installer scans the directory structure, then the Registry, 4. After the scan is complete, SMS Installer automatically begins the setup process. 5. Install the application. When the installation finishes, the **Repackage Installation** dialog box reappears. 6. Complete the repackage. You might want to start the application and configure some of the user options. After you make your changes, click **Next** in the **Repackage Installation** dialog box to initiate rescanning of the directories and Registry. 7. To start building the installation file, click **Compile** in the **SMS Installer** dialog box. The file will be large because it contains all the differences between your before and after snapshots, including the .exe files, .dlls, runtime support, and Registry changes. SMS Installer compresses the file.
Active Directory Group Policy
The Active Directory Group Policy Object (GPO) can be used in two ways depending on the type of package used.
If you have an .msi file for CATIA (perhaps created with WinINSTALL), follow the first procedure. Otherwise, use the second procedure, which uses a batch file to run a Silent Installation or Unattended installation of CATIA:
Steps for Deployment of CATIA MSI Package
The following procedure assumes the CATIA MSI package is named CATIA V5R10.msi
In the Active Directory window, click on the Active Directory Users and Computers icon.
Open the Group Properties window.
Before a group policy can be applied, a group must be defined (for example, Sales, Admin, etc.). A group can consist of systems, users, and other groups. These groups are called Organizational Units (OU) within Active Directory.
Create a group if one does not exist. In this example, the OU name is assumed to be CATIADeploy.
Right-click the group name (CATIADeploy) and select Properties to open the groups properties window.
Create a Group Policy for an OU:
Select the Group Policy tab.
Click New to create a new (and empty) group policy. A name can be given at this point, or the default name can be kept.
Click Edit to open the Group Policy properties window.
Before creating a new package, ensure that CATIA V5R10.msi installation file is located on a shared network drive. This is important because the client's computer still needs to have access to the installation files. The Group Policy just gives the location.
Expand the folders by clicking User Configuration Settings and then Software Installation.
Right-click Software Installation and point to New and then click Package.
Locate the CATIA V5R10.msi file when prompted and click OK.
Select Assigned from the Deploy Software dialog box and click OK. The CATIA V5R10 MSI package comes under software installation pane.
Perform the following test. Log on to another personal computer as a user who belongs to the OU defined above. After logon, the CATIA icon should appear in the Start menu. The first time a user clicks on this icon, the CATIA program will automatically be installed without showing any user interface.
Steps for Deployment of CATIA Non-MSI Setup Packages
If you do not have an .msi file, use the following procedure for deploying other setups.
Create a batch file/script file and name it CATIA V5R10Install.bat, Use this file to run Setup.exe of CATIA V5 from a network share. Use a universal naming convention (UNC) name for the network share.
In the Active Directory window, click on the Active Directory Users and Computers icon.
Open the Group Properties window.
Right-click the group name and select Properties to open the Group Properties window.
Create a Group Policy for the OU:
Select the Group Policy tab.
Click New to create a new (and empty) Group Policy. A name can be given at this point or the default name can be kept.
Click Edit to open the Group Policy Properties window.
Create new logon script following the same procedures detailed in Step 1.
As mentioned in the script file, ensure that the executable and other necessary files are in the network share.
Expand the folder User Configuration Settings in the Tree window pane by clicking Windows Settings and then Scripts (Logon/Logoff).
Click Logon to enter logon properties. Click Add to add the script file. Ensure a UNC name for the script path.
Perform the following test. Log on to another computer as a user that belongs to the OU defined above. After logon, the CATIA application is automatically installed.
Remote Installation Services
Remote Installation Services (RIS) can be used to install the image of the operating system along with the required applications. RIS uses the Remote Installation Preparation wizard (RIPrep.exe) to create these images and copy them to the distribution server.
RIPrep.exe prepares a Windows 2000 Professional image, including locally installed applications and specific configuration settings, and replicates that image to an available RIS server on the network.
Follow this procedure to run RIPrep.exe:
Install the base Windows 2000 Professional OS from an available RIS server on to a supported client computer.
Install the CATIA V5 application locally on the client computer.
Connect to the RIS server where this image has to be replicated by following these steps:
From the Start menu, click Run and type the following command in the Open text box:
where RISservername is the computer name of the destination RIS server.
Reminst is the Remote Installation Share that is created when the RIS service is installed on the server. Admin\I386 is the directory that contains RIPrep.exe and that launches the remote installation.
At this point, the Remote Installation Preparation wizard starts and presents a welcome screen that describes its features and its functionality. Click Next.
Enter the name of the RIS server where the contents of the client hard disk have to be replicated. By default, the RIS server that the wizard (RIPrep.exe) is being run from is automatically filled in. Click Next.
Provide the name of the directory on the RIS server where this image will be copied. The image is created under the \RemoteInstall\setup\OS Language\Images directory. Click Next.
Provide a description and help text describing this image. The description and help text are displayed to users of the Client Installation wizard during OS image selection. Provide enough information for a user to distinguish between images. Click Next.
The wizard displays a summary screen of the selections. After review, click Next.
The image preparation and replication process begins. The system is prepared and files are copied to the specified RIS server. Once the replication of the image completes, any remote boot-enabled client computer can select the image for a local installation.
Installing the Image
Reboot the client computer from either the remote floppy or the PXE boot ROM. When prompted, press the F12 key to start downloading the Client Installation wizard.
Click Enter on the welcome screen.
Type the user name. Press the Tab key twice. For this instruction set, the password is left blank and the domain name should be entered as reskit.com. Click Enter to continue.
A warning message that "all data on the client computer hard drive will be deleted" is displayed. To continue, click Enter.
A computer account and a global unique ID for this workstation are displayed. Click Enter to begin setup. The Windows 2000 Setup program begins.
If prompted, type the Product Key (found on the back of the Windows 2000 Professional CD case) and click Next.
Note: This step can be avoided by specifying the product key in the .sif file.
After the installation is complete, the user is prompted to log on to the network with an existing user account, password, and logon domain.
Symantec Ghost Console Server
Deployment of CATIA V5 can be done in two ways:
Image deploymentdeploying an image of a computer that has CATIA V5 installed.
Package deploymentdeploying AI Package of CATIA V5.
Symantec Ghost Console Server can be used for either method. Both methods require the creation of tasks, which is done using the Ghost Console application.
These tasks can be used to:
Deploy a Symantec Ghost image of a computer.
Deploy a package created using Symantec Ghost AI.
Deploy a file.
Run a command.
Deploying an Image of a Computer that already has CATIA Installed
The steps to make an image of a computer that has CATIA V5 installed are detailed in the section devoted to packaging that appears earlier in this document.
Use the following procedure to deploy an image. Here, it is assumed that such an image has already been obtained.
To open Ghost Enterprise Console:
From the Start menu, point to Programs, point to Symantec Ghost, and then click Ghost Console.
Type the user ID and password for Symantec Ghost Console Server, and then click OK. This opens the Symantec Ghost Console Wizard.
To add an image definition for a previously created image file:
Click Add a previously created image to the console, and then click Next.
Type the title for this image definition.
Click Browse to locate the clone image that was created previously.
To create a new Machine Groups folder:
Double-click Machine Groups.
Click File, point to New, and click Folder.
Right-click the New Folder icon.
Select Rename and type a new name for the Machine Group. Any name can be used here.
Copy individual computers from the default folder or other folders under Machine Groups and paste them into the new folder.
To create a configuration template:
From the File menu, point to New and then click Configuration. This opens the Properties for New Configuration Set window.
Type a name for the new template in the Name box.
Check the Allow template settings option and click OK. This allows modification of this template so that it can be used for more than one computer.
Click User Name on the tree-listing and type the user name to use as the default. Click Ok.
Type a word followed by two asterisks in the Apply Computer Name box, such as Work**. The asterisks are wild cards that Ghost will replace with numbers on the client computers, for example, Work01, Work02. Click OK.
Click TCP/IP Settings. The default selection is DHCP. If the network that the client computers are on does not have a DHCP server, select Target computer has static IP address, and then fill out the rest of the TCP/IP settings that are indicated on the left pane.
Click OK. A new configuration is created.
To create a new task:
From the File menu, point to New and click Task. This opens the Properties for New Task window.
Configure the General tab:
Type a name for the new task in the Name box.
Check the Clone and the Configuration options.
Click Browse, select the client computers to be written over, and click OK.
Configure the Clone tab:
Select the drive to be written over on the client computers in the Destination Drive box.
Click Browse, double-click Images, click the image file of the model computer, and then click OK.
To write to a single partition instead of the entire drive, check Partition Load and fill out the Source Partition information.
To roll out a Windows NT image, click SID change.
For Windows 2000, click SID Change only if SysPrep has not been run on the source computer before creating the image file (SysPrep is useful in eliminating computer specific details like security identification [SID]).
Configure the Configuration tab:
Click Template, and then click Browse.
Double-click Configurations and then click the configuration template that this task needs to use.
Click OK. This saves the task.
To run the task:
Right-click the icon for the Task that has to be run.
Click Execute Task. This displays a confirmation message.
Click Yes. Ghost now executes all operations specified on the General tab of this task.
Deploying AI Package of CATIA
The steps to make an AI Package of CATIA V5 are given in detail in the packaging section.
Follow this procedure to deploy an AI package of CATIA. For this example, it is assumed that such a package has been already obtained and is named CATIA V5R10.exe.
Install Ghost at the computer to be used as a server. This is the Ghost server computer. During installation, choose the Console installation type.
Install the remote client on each computer where the package needs to be deployed.
On the Tools menu, select Remote Client Install.
Select the machine or the domain on which to install the remote client.
Fill out the domain administrator password and click OK. This will install the remote client on the specified computers.
Open Ghost Console at the Ghost server computer:
From the Start menu, point to Programs, point to Symantec Ghost, and then click Ghost Console.
Click Cancel. This closes the Console Wizard.
Create an AI Package:
From the File menu, point to New and then click AI Package. This opens the Properties for New AI Package window.
Type a name for this package in the Name box.
Locate and click the name of the application package and click Open. This copies the path and name of the application package to the Location box on the Properties for new AI Package window.
Create a new task:
From the File menu point to New and then click Task. This opens the Properties for New Task window to the General tab.
Type a name for this task in the Name box.
Uncheck all Task Steps except Deploy AI Package.
Click Browse and select one or more computers. These are the client computers where the CATIA application package will be installed.
Click the Deploy AI Package tab.
Then click Browse.
This window has two Browse buttons. Click the top Browse button, next to the Install packages box.
Select CatiaV5R10 under AI Packages. The application package is a file that uses the filename format CATIA V5R10.exe. This step adds the application package to the Install packages box described in Step g.
To distribute and run the application package, execute the following procedure:
Click the task name.
Click File and then click Execute task.
When Execute Task is clicked, this process copies the application package file to the incoming folder on each client computer and runs the file. Running the file installs the programs that are included in the application package.
Clients will restart after successful installation of the package.
Systems Management Server
Before creating an SMS package, you must set up the system by using the following procedure.
To specify the account for software distribution to use when clients are not logged on, perform these steps on the site server:
From the Start menu, point to Programs, point to System Management Server, and then double-click SMS Administrator Console. This starts Microsoft Management Console (MMC).
In the left pane, expand the Site Database tree and then expand the Site Hierarchy node under Site Database.
Right-click the Site and then click Properties.
On the Accounts tab, click the Set option next to the SMS Client Remote Installation Account box. Specify the account, to be used to perform the software installation. The account needs to have domain Administrator rights as well as local Administrator rights on the workstations. The Remote Client Installation component primarily uses this account, but software distribution also uses the account to run packages on computers that are not logged on to the network.
Create the Systems Management Server 2.0 package for deployment by using the following procedure. This is the actual package that Systems Management Server uses for distribution.
1. On the General tab, provide values for the following attributes:
Name. The name of the package, up to 50 characters (for example, "CatiaV5R10"). This field is required.
Version. The version number of the software package, up to 32 characters. (For example, "1.0")
Publisher. The name of the software publisher, up to 32 characters. (For example, Dassault Systemes")
Language. The language version of the software, up to 32 characters. ("English")
Comment. Optional text about the package, such as a description, up to 127 characters.
2. On the Data Source tab, click to select the This Package Contains Source Files check box, and then click Set.
3. Under Source Directory Location, click the type of connection to the set up files in the source directory, and then click OK.
4. On the Distribution Settings tab, in the Sending Priority box, click High, and then click OK. The package should now appear under the Packages node of the site tree within the console.
5. Expand the package under the Packages node.
6. Right-click Distribution points, click New/Distribution Points, and then click Next to begin choosing distribution points.
7. Click to select the check box by the server or servers that will be the distribution points for this package, and then click Finish. Return back to the Site tree.
8. Right-click Programs under this package, click New/Program, and then type a name for the program.
9. In the Command Line box, type the full path to CATIA executable file, or click Browse to locate the file. Add these switches:
-- s for silent mode
-- SMS or SMS (This switch is case sensitive.)
10. On the Environment tab, click to clear the User Input Required check box.
11. Click to select the Run with Administrative rights check box, and then click OK.
12. The Packages window now reappears and the newly created Systems Management Server package is displayed.
To distribute a package created in SMS, you must advertise it in order to offer it to clients.
The following procedure describes creating the Advertisement.
1. Create a collection of clients that are targeted to receive the distribution. The collection can be based on a query or direct membership rules.
2. Right-click the collection that will receive the package and then click All Tasks/Distribute Software.
3. The Distribute Software wizard starts. Click Next.
4. Click Distribute an existing package, click the Internet Explorer package, and then click Next.
5. Make sure the distribution point is selected, and then click Next.
6. Click the program to install, and then click Next.
7. Fill in the advertisement name if appropriate, and then click Next.
8. Specify any sub-collections that should also receive this advertisement, and then click Next.
9. Confirm or change the time the advertisement is offered and specify if the advertisement should expire and when.
10. On the Assign Program page, click Yes to assign the program.
11. Click Next, and then click Finish.
The installation process of the Rshmsisvc on the clients requires the sharing of the folder containing the trigger script to enable remote updates to the script. Appropriate security permissions are assigned to this folder to prevent updates from unauthorized users.
The following diagram shows that you use Rshmsisvc by writing batch commands into the trigger script file. These commands could, for example, install CATIA by referencing an .msi file created with WinINSTALL or by running a silent installation.
Figure 3.1: Schematic Representation of Rshmsisvc Execution
The following two descriptions of stages detail the deployment strategies using Rshmsisvc
Distribution of the Application software bundle and the unattended installation script to all the clients. During Stage I, the Application software bundle and the unattended installation script are remotely copied from a network location to all the clients. The remote copy process should be done in a staggered manner for optimal use of the network. The process can be automated using batch files.
The distribution process helps to initiate the simultaneous installation of the software at a later time, on all the clients, without affecting the network.
Installation of the Application software on all the clients. In Stage II, the installation of the Application software bundle (available locally in the clients after Stage I) is initiated in the clients by remotely copying the trigger script to all the clients from the server. The copy process could be carried out using the same batch files discussed in Stage I.
The trigger script refers to the unattended installation script that is available as a part of the software bundle in the clients. The Rshmsisvc service at the clients begins execution of the installation script as soon as the trigger script is updated.
Note: The batch files used for the distribution (Stage I) and installation (Stage II) can be scheduled for execution during off hours.
After CATIA V5 has been installed using the methods discussed above, it becomes imperative to check whether the installation was successful.
Follow this process for validating installation.
From the Start menu, point to Programs, point to CATIA, point to Tools, and click on Software Management B10. Or, from the Start menu, point to Find, and then click Files or Folders and search for CATSoftwareMgt.exe in the Local Hard drives.
Click the Check Integrity tab.
Select Level 3 and click Check.
The message Check Integrity Level 3 is OK confirms that there is no integrity problem. But if the message Check Integrity Level 3 is KO appears, then the installation has been corrupted (for example, some files are missing). This message will be followed by troubleshooting information to identify and solve the problem.
The packaging and deployment technique you choose will depend on many factors, including the size of your organization, the project budget, and whether an operating system is already in place on the desktop computers.
Having deployed CATIA, you will later have Service Packs and hotfixes to distribute, and these can frequently be rolled out with the same tool that you used for the installation.
Network traffic is intense during the installation of CATIA and later Service Packs and hotfixes, and the distribution server is heavily utilized. This load can be managed by rolling out to a limited number of computers at a time. This also allows you to test the installation method in a live environment, without impacting a large number of users in the event of problems.
Disclaimer and Copyright Information
CATIA is a registered trademark of Dassault Systemes SA. The names of other actual companies and products mentioned herein may be the trademarks of their respective owners.