This task explains an alternative to the previous scenario: how to use the
RCMD command, which is part of the Resource Kit for your Windows platform,
for distributing the software from a source computer to a client computer
inside the same domain.
Note that the default installation path can be:
|The Resource Kit must be installed on both the source
computer ("ravel" in our example) and the client computer ("chopin" in our
Furthermore, for the RCMD command to operate, the RCMDSVC service must be started beforehand on the client computer. This involves installing a Remote Command server on each client computer, then starting the Remote Command server. For more information, refer to the following Windows online help topic: RCMD.EXE: Remote Command Service.
|When setting up the server you can:
|With Windows XP Professional 32-bit operating systems, if LUM is already installed on your machine, and the LUM license server has been started, you will be prompted to stop the LUM server before proceeding. If you choose not to stop the LUM server, the installation will be stopped.|
|The software supplied by Microsoft in the Windows Workstation Resource Kit is not officially supported. Microsoft (and Dassault Systemes) do not guarantee the performance of the Windows Workstation Resource Kit tools, response times for answering questions, or bug fixes to the tools. The software (including instructions for its use and printed and online documentation) is provided "AS IS" without warranty of any kind.|
|1. Log onto the source computer using an account with Domain Administrator privileges.|
|2. Copy the Version 5 software into a folder on the source
computer, and share the folder.
For example, the folder name could be
|4. Double-click the
A Command Prompt window is opened and you are now located in the directory, for example on 32-bit Windows XP:
|5. Connect to the remote client computer using the command:
where "remote_computer" is the name of the remote computer.
In our example, the command would be:
|6. Once you are connected to the remote computer, map a drive on
the remote computer to the shared folder on the source computer.
In our example, the command would be for example:
This command maps the M: device (the device must be available) on the remote computer "chopin" to the shared folder "CATIA" on the source computer "ravel", using the domain administrator password "admin". Note that the domain name is "MyDomain" and the domain administrator username is "root".
To check that the map has been successfully performed, enter the command:
which will list the mapped resources like this:
|For more information about the net use command, refer to the Windows online help system.|
|7. To check that the installation folder and the
to access the command help, or:
to list the configurations/products you can install.
Note: Replace INTEL by WIN64 on Windows XP Professional x64 Edition.
|8. Install the Version 5 software.
For example, running the following command will install the DP2 and MD2 configurations (and the corresponding nodelock licenses) for the CATIA product line into the following location, for example on 32-bit Windows XP Pro:
into the following location on the remote computer:
|9. Unmap the drive on the remote computer by running the
|For detailed information about the
Note that appending the "-exe" option to the StartB command does not launch a session at the end of the installation on the remote computer.
|You can also use the System Management Server (SMS), part of the Windows BackOffice suite. SMS includes desktop management and software distribution that significantly automates the task of upgrading software on client computers.|