This section provides notes related to using a client.

If the client's OS is Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista, also see A.6. Notes on using the Windows 8/2012/7/2008/Vista Edition of JP1/Software Distribution Client in the manual Administrator's Guide Volume 2.

• Notes on using a client in the terminal service environment
  To use a client in the terminal service environment of Windows Server 2003 or Windows 2000, use it on a local console. The terminal service is not supported. For limitations on using a client at a local console and how to perform remote installation, see B. Using JP1/Software Distribution Client (Client) on a Terminal Server in the Setup Guide.
  
• Notes on using other companies' software
  While other companies' software is being installed in a remote installation, you must not perform window operations on the active installer. If you do perform such an operation, the installer might freeze.
  
• Notes about password locking of clients
  If the client PC is locked by means of a logon password (a dialog box requesting entry of Ctrl + Alt + Delete keys is displayed), software that requires the user's intervention in the GUI installation mode is not installed remotely because no response can be made. Hitachi program products supporting remote installation are installed because they do not require user intervention during remote installation.
  
• Client cannot be started or takes too long to start
  In the following cases, the client (or relay system) might not be able to start or will take too long to start:
  
  1. The higher system to which the client is to be connected has not started.
  2. The client is transmitting the results of a job that it was unable to process during the previous startup.
  3. On the Default Running Status/Polling page in Setup, the Start polling when the client program starts option is selected and the system start polling frequency is specified as Before the client starts.
  In case 1, the client starts when the higher system to which it is to be connected starts.
  In case 2 or 3, the client starts when transmission of job results or polling of the higher system is completed.
  
• What to do when the installation process hangs
  If a user program that was started during remote installation processing freezes, or the user program termination code notification interface is incorrect in the GUI installation mode, the remote installation process also hangs. If this happens, restart the client PC.
  
• Notes on split distribution
  

  Split distribution in an environment where the client is nonresident and does not conduct polling:

  If no client is resident, a job waiting for split distribution is run when you start Execute Job Backlog. After a split distribution job has been executed, if you choose Execute Job Backlog after the specified distribution interval, the next split distribution job is executed.

  If the client does not conduct polling, split distribution is only started by the server. If startup fails, you must use Execute Job Backlog to execute any waiting split distribution job as if no client were resident.

  In an environment where the client is nonresident and does not conduct polling, split distribution starts at the same time as Execute Job Backlog. Therefore, you should avoid split distribution in such an environment.

  Hold cancellation and split distribution:

  In the case of split distribution, after all split jobs have been transferred, the Hold or Cancel Software Distribution Job dialog box is displayed asking the user whether to perform installation. Choosing Execute starts installation and choosing Hold delays installation. Installation is not performed until the user responds. Clicking Cancel deletes jobs without installation. When you retry canceled jobs, jobs are re-executed from the beginning of split distribution.

  Split distribution specified with an installation date/time:

  If an installation date/time is specified for a split distribution and the installation time comes during a split distribution, installation will begin after all the split jobs for the split distribution have been transferred.

  Split distribution installation at startup time:

  In the case of split distribution with installation specified at the time of system startup, installation begins when the system starts after all split jobs have been transferred.

• Limitations on using JP1/Software Distribution Client in a virtual environment
  Some limitations apply when you install or operate JP1/Software Distribution Client (client) in a virtual environment. Note also that depending on the OS type, JP1/Software Distribution Client (client) might not support a virtual environment. For more details about OS types, see 1.1.1 Supported OSs in the Setup Guide.
  

  Limitations related to Remote Desktop

  • When you connect using Remote Desktop to install JP1/Software Distribution Client (client), you cannot use the installation set.
  • When you connect using Remote Desktop to install a package, you cannot use offline installation.
  • To connect using Remote Desktop to install or operate JP1/Software Distribution Client (client) when the OS is Windows Server 2003, connect to a console session.
    To connect to a console session, specify the /console or /admin parameter as described below and execute Remote Desktop Connection Client.
    /console parameter
    

    mstsc.exe /console

    /admin parameter
    

    mstsc.exe /admin

    The parameter required for connecting to the console session differs depending on the version of Remote Desktop Connection Client being used.
    
  • When Remote Desktop is used to connect to and operate JP1/Software Distribution Client (client) when the OS is Windows Server 2012 or Windows Server 2008, multiple users cannot concurrently execute JP1/Software Distribution applications.

  Limitations on the Quick User Switching Feature

  • When the Quick User Switching Feature is used to connect to and operate JP1/Software Distribution Client (client) when the OS is Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista, multiple users cannot concurrently execute JP1/Software Distribution applications.

  Limitations related to terminal servers

  • For the limitations applicable to using JP1/Software Distribution Client (client) on a terminal server, see B. Using JP1/Software Distribution Client (Client) on a Terminal Server in the Setup Guide. This appendix also explains limitations related to Citrix XenApp.

  Limitations related to Windows XP Mode

  • For the limitations applicable to using JP1/Software Distribution Client (client) in the Windows XP Mode environment, see C. Using JP1/Software Distribution Client (Client) in a Windows XP Mode Environment in the Setup Guide.

  Limitations on Modern UI applications

  • Software information cannot be collected for Modern UI applications.
  • All the facilities for software operation monitoring do not support Modern UI applications.