1.6.2 Notes on installing software manually

This section provides cautionary notes that apply when installing software manually.

If the managed computer is running Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista, also see A. Notes on using JP1/IT Desktop Management 2 - Agent in Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, and Windows Vista.

• Notes on installing other companies' software

  When remotely installing other companies' software, do not perform operations in the user interface of the installer while the software is installing. Doing so might cause the installer to stop responding.

• Notes on password-protected computers

  If a managed computer is password-protected (it displays a dialog box asking the operator to press Ctrl + Alt + Delete), software that requires user intervention in GUI installation mode cannot be installed remotely. This is because the password protection prevents the required responses from being provided. This issue does not affect Hitachi program products that are compatible with remote installation, because such programs do not require user intervention during remote installation.

• A managed computer cannot start or takes too long to start

  In the following circumstances, a managed computer might be unable to start, or might take a long time to start.

  1. The higher connection destination of the managed computer is not running.

  2. The managed computer is busy transmitting the results of a job that could not be processed the last time the computer was running.

  3. On the Basic Settings page during agent setup, the Perform polling based on the system startup check box was selected in the Timing of communication with the higher system area, and Before the system starts is selected for Polling timing.

  In the first scenario above, the managed computer starts when the higher system has started.

  In the second and third scenarios, the managed computer starts when the transmission of job results and the polling of the higher system has completed.

• What to do if the installation process stops responding

  If a user program that was started during remote installation stops responding, or the user program termination code notification interface is configured incorrectly in GUI installation mode, the remote installation process also stops responding. If this happens, restart the managed computer.

• Notes on split distribution

  Split distribution in environments where the managed computer does not conduct polling:

  If the managed computer does not conduct polling, split distribution can be initiated by an instruction from the server. We recommend that you avoid using split distribution in environments where the server might fail to start the split distribution process.

  Held jobs and split distribution:

  When using split distribution, when all split packages have been transferred, the JP1/IT Desktop Management 2 Job Suspended dialog box appears asking the user whether to install the packages. If the user chooses to install the packages, the installation process begins. If the user chooses to hold the packages, installation is put on hold and the packages are not installed until requested by the user.

  Split distribution with an installation date and time specified:

  When using split distribution with an installation date and time specified, the installation date and time might elapse while split distribution is still in progress. In this case, installation begins as soon as all the split packages for the split distribution process have been transferred.

  Installation of split packages at startup

  If you perform split distribution with installation at system startup, installation will begin when the system next starts after all the split packages have been transferred.

• Limitations when using JP1/IT Desktop Management 2 - Agent in virtual environments

  Certain limitations apply when using JP1/IT Desktop Management 2 - Agent (agent) in a virtual environment. JP1/IT Desktop Management 2 - Agent (agent) does not support some operating systems in virtual environments.

  Limitations related to Remote Desktop

  • You cannot use offline installation when you use Remote Desktop to install a package.

  • In Windows Server 2003, when using Remote Desktop to install or operate JP1/IT Desktop Management 2 - Agent (agent), connect to a console session.

    To connect to a console session, establish the Remote Desktop connection with the /console or /admin parameter specified as shown below.

    /console parameter

    mstsc.exe /console

    /admin parameter

    mstsc.exe /admin

    The parameters for connecting to the console session differ depending on the version of Remote Desktop you are using.

  • When you operate JP1/IT Desktop Management 2 - Agent (agent) via a Remote Desktop connection in Windows Server 2012 or Windows Server 2008, multiple users cannot concurrently run the JP1/IT Desktop Management 2 application.

  Limitations related to Fast User Switching

  • When you use Fast User Switching to run JP1/IT Desktop Management 2 - Agent (agent) in Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista, multiple users cannot concurrently run the JP1/IT Desktop Management 2 application.

To Page Top