B.6 Deploying the Windows MSI or EXE Files

B.6.1 Deployment Specifics

For MSI and EXE deployments, the DeployAgents tool performs the following actions:

  • Employs wrapper scripts that work with both the Novell Storage Manager MSI agents and Event Monitors and the Novell File Reporter EXE agents.

  • Utilizes scripts that rely on the C$ admin share being available on the servers where the agent is to be installed, and that the C:\temp directory exists or can be created, and can be written to over the network by a domain administrator.

  • Uses the installer name without path information.

  • Uses the latest version by time and date in the software folder, regardless of the command line designation.

B.6.2 Setting an Alternate Installation Path

By default, DeployAgents installs the agent and Event Monitor software to the following locations:

Table B-3 Default Installation Paths

Software

File Path

NSM Agent

C:\Program Files\Novell\Storage Manager\Agent

NSM Event Monitor

C:\Program Files\Novell\Storage Manager\Event

NFR Agent

C:\Program Files\Novell\File Reporter\Agent

For MSI and EXE files, you can change the default installation path for the agent or Event Monitor software through the AlternateInstallPath.txt file.

  1. In the root of the DeployEXE or DeployMSI file, locate the _AlternateInstallPath.txt file.

  2. Rename the file to AlternateInstallPath.txt by removing the underscore.

    After it is renamed, the file can be edited via Notepad or another text editor.

    The AlternateInstallPath.txt file uses a combination of text and variables so it can be used over and over.

  3. Use Notepad or another text editor to edit the installation path.

    You can change the drive letter, add additional path text, or change the text altogether to make the component best fit your environment.

    MSI Example:

    Default path: c:\%brand%\%product%\%component%

    Modified path example: e:\%brand%\%product%\%component%

    EXE Example:

    Default path: c:\%brand%\%product%\

    Modified path example: e:\%brand%\%product%\

  4. Save the AlternateInstallPath.txt file.

B.6.3 Using DeployAgentsMSI.cmd

  1. Launch the DOS Command Prompt utility.

  2. Change to the DeployMSI directory.

  3. Do one of the following:

    • Enter: deployAgentsMSI.exe servernames.txt domain\administrator NSMAgent-3.1.0-x64-xx.msi

    • Enter: deployAgentsMSI.exe agents.dat domain\administrator NSMAgent-3.1.0-x64-xx.msi

      When you deploy MSIs through an agents.dat file, if a servernames.txt file already exists, you are asked if you want to use the servernames.txt file that already exists.

      If you choose No, the servernames.txt file is deleted and a new one is created, based on the contents of the agent.dat file.

B.6.4 Using DeployAgentsEXE.cmd

  1. Launch the DOS Command Prompt utility.

  2. Change to the DeployEXE directory.

  3. Do one of the following:

    • Enter: deployAgentsEXE.exe servernames.txt domain\administrator NSMAgent-3.1.0-x64-xx.exe

    • Enter: deployAgentsEXE.exe agents.dat domain\administrator NSMAgent-3.1.0-x64-xx.exe

      When you deploy EXEs through an agents.dat file, if a servernames.txt file already exists, you are asked if you want to use the servernames.txt file that already exists.

      If you choose No, the servernames.txt file is deleted and a new one is created, based on the contents of the agent.dat file.