The remote installation methods include the background installation mode, which involves copying of files only, and the GUI installation mode, which involves use of the graphical user interface (GUI). Most distributed programs, including Hitachi program products and other companies' software, use the GUI installation mode.

However, in a Windows NT client, GUI installation mode packages can be installed only when the user who installed the client is logged on, and no dialog boxes are displayed during processing.

In JP1/Software Distribution Client, you can display dialogs during processing in the GUI installation mode while you are logged on as a non-Administrator user or an Administrator user who is different from the user who installed the client. You must specify use of the facility for installation with non-Administrator user permissions in the client setup. You must also set the access permissions for the following registry in such a manner that ordinary users cannot change the registry:

• In a 32-bit OS
  HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\NETM/DM/P
  
• In a 64-bit OS
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\NETM/DM/P
  

To enable the facility for installation with non-Administrator user permissions, select the Run the client with non-Administrator user permissions check box on the Security page of the Client Setup dialog box.

Figure 11-7 Security page

Note that background installation mode packages are installed regardless of the permissions of the user who is logged on.

When you are using the facility for installation with non-Administrator user permissions, the client is subject to the following restrictions:

(a) Moving startup programs

If you use the facility for installation with non-Administrator user permissions, the following limitations apply to the startup programs.

• Changing the Software Distribution Client Startup folder
  When the Create Software Distribution Client Startup folder check box is selected on the Startup page in Setup, the location in which the Software Distribution Client Startup folder is created depends on whether or not the facility for installation with non-Administrator user permissions is used.
  When the facility for installation with non-Administrator user permissions is not used, the Software Distribution Client Startup group folder is created in a personal program folder. If you specify use of the facility for installation with non-Administrator user permissions during setup, the group folder is created in the common program folder.
  If the Move programs in the Startup group to the Software Distribution Client Startup folder option is specified during setup and shortcuts are registered in both the common program folder and the personal program folder, the Software Distribution Client Startup folder is created in both the common program folder and the personal program folder, regardless of whether the facility for installation with non-Administrator user permissions is used.
  If the client is to be shared by users with non-Administrator user permissions and users with Administrator permissions, you should specify shortcuts created in the Software Distribution Client Startup folder to be accessible using either of the permissions.
  
• Scope of the setting for automatically moving startup programs
  If you select the Move programs in the Startup group to the Software Distribution Client Startup folder option on the Startup page, the startup programs of all users are moved automatically.
  All of a non-Administrator user's startup programs are moved to the Software Distribution Client Startup folder regardless of the Select the shortcuts to move setting. If you want to move a non-Administrator user's startup programs back to the individual user's Startup group, clear the Move programs in the Startup group to the Software Distribution Client Startup folder check box on the Startup page in the setup, and then move the startup programs manually.
  
• Scope of uninstallation when startup programs are moved automatically
  If you select the Move programs in the Startup group to the Software Distribution Client Startup folder option on the Startup page in the setup and you then uninstall JP1/Software Distribution Client, the operations listed below will be performed automatically for the users who are logged on currently, but not for users who are not logged on:
  
  • Startup programs will be moved to the Startup group
  • The Software Distribution Client Startup folder will be deleted
  These operations must be performed manually for the users who are not logged on.
  

(b) Changing program folders for programs to be installed

As a general rule, a package installed using non-Administrator user permissions creates a program folder different from when the same package is installed using the Administrators permissions. Table 11-1 shows the permissions of the logged-on user and the types of program folders that are created by Installer.

If you installed a package using non-Administrator user permissions, move the program folder manually, if required.

Table 11-1 User permissions and program folders

Type of program folders created by Installer	Permissions of logged-on user
	Administrator	Users
Individual	Individual	Default User#1
Common	Common	Common or Individual#2
None (16-bit applications)	Common	Individual

#1

The user permissions are created in the Default User personal program folder. If the Windows NT installation path is C:\Winnt, the personal program folder is in the following location:

C:\Winnt\Profiles\Default User\start menu\program

#2

Program folders that are created can vary depending on the specifications for the program being installed.

(c) Installing packages when the client is shut down

If you log on using non-Administrator user permissions, the following restrictions apply if the client has been shut down by Client Manager, or if both the Client starts automatically at system boot check box on the Default Running Status/Polling page and the Use the Package Setup Manager or Execute Job Backlog command when a client is not resident check box on the Security page are deselected.

• The following packages cannot be installed even if installation is executed from the client using either the Package Setup Manager or the Execute Job Backlog icon.
  
  • Packages that require registration, startup, or termination of services
  • Packages that create new registry keys
  • Packages in which read, write, or delete is not set for the installation destination directory or the file access permissions
• Even if installation is executed from the client using either the Package Setup Manager or the Execute Job Backlog icon, the access permission to and owner of the installation directory and files do not change.

(d) Installation using an AIT file

To remotely install a package using an AIT file that is set to operate the HKEY_CURRENT_USER registry, you must log on as an Administrator user.

If you log on as a non-Administrator user, you do not have access permissions for HKEY_CURRENT_USER, and therefore the registry operated by the AIT file is automatically changed to HKEY_USERS\.DEFAULT. Consequently, installation may not be executed correctly.

(e) Starting an external program during background installation

When you are installing a package that specifies a program that uses a command prompt or a batch file as an external program into a client for which use of the facility for installation with non-Administrator user permissions is specified, the command prompt window is displayed during the startup of the external program, even if you specified background installation.