A.6 Version changes

Maximum of 300,000 devices can be managed.

Operation Date/Time (UTC) was added to the information items to be collected in the operation log.

A procedure for setting API usage was added.

The explanation for using operation windows with 10-20 concurrent users was changed.

Windows Server 2019 was added as an applicable operating system for the following products:

• JP1/IT Desktop Management 2 - Manager

• JP1/IT Desktop Management 2 - Agent

• JP1/IT Desktop Management 2 - Network Monitor

• JP1/IT Desktop Management 2 - Asset Console

• JP1/IT Desktop Management 2 - Internet Gateway

• Remote Install Manager

Devices can now be managed from an external system via the API.

Shared VDI-based virtual computers can now be managed.

Windows Server 2008 R2 was removed from applicable OSs for the following products:

• JP1/IT Desktop Management 2 - Manager

• JP1/IT Desktop Management 2 - Network Monitor

• JP1/IT Desktop Management 2 - Asset Console

• Remote Install Manager

The connection destination of a higher system can now be automatically switched for distribution of files.

Computers can now be managed via the Internet.

A security policy can now be set for offline-managed devices.

You can now install an agent on the server on which Citrix XenApp and Microsoft RDS have been installed and manage it with JP1/IT Desktop Management 2.

For agents for Mac, the distribution of software and files (remote installation) is now enabled. Additionally, these agents are judged for security status based on security policies.

Windows Server 2016 was added as an applicable operating system for the following products:

• JP1/IT Desktop Management 2 - Manager

• JP1/IT Desktop Management 2 - Agent

• JP1/IT Desktop Management 2 - Network Monitor

• JP1/IT Desktop Management 2 - Asset Console

• Remote Install Manager

By linking with JP1/Base, you can now log in to JP1/IT Desktop Management 2 by using JP1 authentication.

An agent can now be managed after being installed on a computer running Mac OS.

Provided functionality

• Acquisition of system information and software information

• Remote control via RFB connections (already provided for agentless management)

• Network control (enabling or disabling network access on demand)

Unavailable functionality (including functionality in development)

• Software and file distribution (remote installation)

• Collection of files (remote collection)

• Agent settings and agent deployment

• Security management (security judgments, automated countermeasures)

• Operation logs

• Device control

As files that are to be executed automatically during installation, ZIP files for installers of related products, such as Hibun, can now be set.

A maximum of 50,000 devices can now be managed.

JP1/IT Desktop Management 2 - Operations Director was added as a relevant program product.

Windows 10 was added as an applicable operating system for JP1/IT Desktop Management 2 - Network Monitor.

You can now use the file for connection destinations (itdmhost.conf) to specify the connection destination of an agent.

In the description of the Procedure for installing Remote Install Manager only, the following information was amended:

• The description of the dialog box where you select a component to install

• The description of the information needed when starting Remote Install Manager after installation

To perform distribution by using Remote Install Manager, you can now select whether to enable flow control (by specifying the maximum transfer rate for sending packages).

You can now perform device maintenance in which you can specify judgement conditions for duplicate or idle devices in order to detect devices suggested for deletion, and then delete them automatically or manually.

You can now select which menu items are to be displayed in the start menu of an agent.

The procedure for switching the higher connection destination of a management relay server now mentions that device information needs to be manually reported all the way from the lower management relay server to the primary management server.

A description of the port numbers used on the administrator's computer (Remote Install Manager) and relay systems was added.

Operating JP1/IT Desktop Management 2 in a multi-server configuration enables both location-by-location management and integrated management.

The procedure for installing JP1/IT Desktop Management 2 - Manager was changed.

The procedure for setting up a management server was changed.

The procedure for overwrite-installing JP1/IT Desktop Management 2 - Manager was changed.

You can now import and export network connection information.

The following products now support Windows 10:

• JP1/IT Desktop Management 2 - Agent

• JP1/IT Desktop Management 2 - RC Manager

• Remote Install Manager

Windows Server 2003 and Windows Server 2008 (excluding Windows Server 2008 R2) were excluded from the applicable OSs for the following products:

• JP1/IT Desktop Management 2 - Manager

• JP1/IT Desktop Management 2 - Agent

• JP1/IT Desktop Management 2 - Network Monitor

• JP1/IT Desktop Management 2 - RC Manager

Anti-virus product information can now be acquired from the support service site.

You can now install and manage an agent on a computer whose OS is UNIX.

As an argument for the resetnid.vbs (resetting host identifiers) command, /s was added.

(Changes from only this manual (3021-3-369(E))) The software, purchasing status, product ID, GUID, and software type for some software can now be managed.

A description of a method of displaying the return code of the resetnid.vbs (reset a host ID) command was added, and the accompanying usage example was amended.

Systems can no longer be deployed in a site server configuration, and a host called a relay system was added as an essential component of distribution using Remote Installation Manager.

When distributing software using Remote Installation Manager, the conditions for managed computers and the installation behavior can now be specified in more detail.

Hardware information (including networking equipment), software information, and contract information can now be centrally managed in the database.

Files stored on managed computers can now be collected as a batch.

In the Getting Started wizard, you can now manage devices by installing the agent software.

Systems can no longer be deployed in a multi-server configuration, and a single management server can now manage a maximum of 30,000 devices.

You can now specify how many times the user can enter the wrong password before his or her account is locked, and set a valid period for passwords.

The settings associated with installation, setup, and agent setup were changed to reflect the new product structure.

Windows 8.1 and Windows Server 2012 R2 were added as supported OSs for the following products:

• JP1/IT Desktop Management 2 - Manager

• JP1/IT Desktop Management 2 - Agent

• JP1/IT Desktop Management 2 - Network Monitor

Windows 8 and Windows 7 are no longer supported OSs of the following product:

• JP1/IT Desktop Management 2 - Manager

The following product no longer supports Windows 2000:

• JP1/IT Desktop Management 2 - Agent

The supported versions of Internet Explorer were changed.

Microsoft Cluster Service was removed from the list of supported cluster software.

Some port numbers were changed.

The folder structure created under JP1/IT Desktop Management 2 - Manager was changed to reflect the new product structure.

Cautionary notes regarding installation, overwrite installation, and uninstallation were added.

A description was added stating that if the discovery of network-connected devices is concentrated within a specified time period, the discovery range must be set so that the number of IP addresses does not exceed 50,000.

By linking with JP1/NM - Manager, network connections that are monitored by the appliance products on which JP1/NM is installed can now be monitored from JP1/IT Desktop Management.

A description was added about changing the server certificate of the MDM system after the server certificate is imported to the management server. The description of the versions of Internet Explorer that can be used to obtain the server certificate was deleted. A description of the settings to use when linking with the JP1 smart device management service was also added.

You can now specify whether to enable automatic updates for all items in the network control list or only for additional items.

The description of performing an overwrite installation of the product and updating the components was amended.

A description of the procedure for upgrading the entire JP1/IT Desktop Management system and the procedure for upgrading JP1/IT Desktop Management -Manager was added.

The procedure for changing the site server's connection destination was added to the procedure for replacing the management server in a single-server configuration system.

All descriptions relating to command execution permissions were consolidated under the description of the procedure for executing commands. A description was also added regarding situations in which UAC is enabled in the OS when executing commands other than getinv.vbs.

Cautionary notes regarding command execution were added.

The /i option was added to the resetnid.vbs command, and dialog boxes in which the user can select whether to execute the command and display the execution result now appear on the user's computer.

The description of port number settings was amended. A description of the network between JP1/IT Desktop Management - Remote Site Server and agentless computers was also added.

The following products now support Windows 8 and Windows Server 2012:

• Job Management Partner 1/IT Desktop Management - Manager

• Job Management Partner 1/IT Desktop Management - Remote Site Server

• Job Management Partner 1/IT Desktop Management - Network Monitor

Notes on installation, overwrite installation, and uninstallation were added.

You can now obtain the revision history of device information.

The following note was added: If you want to specify a period of time to intensively search for devices connected to the network, you must specify settings so that the number of IP addresses contained in the IP address range is 50,000 or lower.

You can now link with JP1/NM - Manager to allow JP1/IT Desktop Management to control network connections monitored by appliance products with JP1/NM installed.

Descriptions of how to import a server certificate to the management server, and then change the server certificate of the MDM system, were added. In addition, the descriptions of the Internet Explorer version available for obtaining a server certificate were deleted.

For automatic update of the network control list, you can now specify whether to enable all automatic updates or automatic updates only for add operations.

Descriptions of overwrite-installing the product and updating components were corrected.

Descriptions were added to the procedures for updating the version of the entire JP1/IT Desktop Management system and JP1/IT Desktop Management - Manager.

The procedure for changing the connection destination of a site server was added to the procedure for replacing a management server in a single-server system.

Descriptions about permissions required to execute commands were collected in 8.1 Executing commands. In addition, a description about what to do if User Account Control (UAC) for the OS is enabled when executing a command other than the getinv.vbs command was added.

A procedure of executing commands on a computer with an agent installed was added. In addition, notes on command execution were added.

You can now export and import definitions of shared management items and added management items in CSV format.

A description was added about the characters that can be used for folder names specified in the following commands:

• exportdb command

• getlogs command

• getinstlogs command

• importdb command

The /i option was added to the resetnid.vbs command so that a dialog box to select whether to let the user's computer execute the command and a dialog box to show execution results are displayed. In addition, the following topics were added:

• A procedure of resetting a host ID on a computer on which a site server is installed

• Notes on executing the resetnid.vbs command on a device on which the network monitor is installed

The description about ports was corrected. Also, a description about the network between JP1/IT Desktop Management - Remote Site Server and agentless computers was added.

The following products now support Windows 8 and Windows Server 2012:

• JP1/IT Desktop Management - Manager

• JP1/IT Desktop Management - Remote Site Server

• JP1/IT Desktop Management - Network Monitor

You can now obtain the revision history of device information.

A procedure of executing commands on a computer with an agent installed was added.

You can now export and import definitions of shared management items and added management items in CSV format.

A description was added about the characters that can be used for folder names specified in the following commands:

• exportdb command

• getlogs command

• getinstlogs command

• importdb command

A procedure of resetting a host ID on a computer on which a site server is installed.

Notes on executing the resetnid.vbs command on a device on which the network monitor is installed.

A description stating that the default file name of the installation set is ITDMAgt.exe was added.

A description about using Autorun.inf to enable an installation to start automatically when a CD-R is used as the media for installing the agent was added.

Computers that are not connected to the management server via a network can now be managed by using the offline management functionality.

JP1/IT Desktop Management information can now be updated by obtaining the support service information, including information about anti-virus software.

The notes that apply when JP1/IM and JP1/Base are not connected in a JP1/IM linkage system were improved.

The notes on deleting the search range or authentication information of devices managed without using agents, or on unregistering the devices from the Active Directory settings, were collected in the JP1/IT Desktop Management 2 Overview and System Design Guide.

You can now update the JP1/IT Desktop Management information by obtaining anti-virus product information from the support service site.

The procedure for setting the information required to link with the MDM system was corrected.

A general procedure for updating the version of the entire JP1/IT Desktop Management system was added.

The procedure for updating the version of JP1/IT Desktop Management - Manager was corrected.

The description of how to update components was corrected.

A general procedure for overwrite-installing JP1/IT Desktop Management - Manager in a multi-server system was added.

A general procedure for updating the version of JP1/IT Desktop Management - Manager in a multi-server system was added.

The procedure for replacing a site server and the notes on the recreatelogdb command used to replace a site server were corrected.

A procedure for replacing a computer on which the network monitor is enabled was added.

You can now update the JP1/IT Desktop Management information by obtaining the SAMAC software dictionary file for offline updates from the support service site.

The note on the recreatelogdb command executed with an argument other than -node was corrected.

A description of the stopservice (stopping services) command as a configuration-related command was added.

A description stating that the getlogs command uses the folder set in the TEMP user environment variable as a temporary folder was added.

The description of the case in which an agent is installed by copying a disk without executing the resetnid.vbs command in the reference material section was improved.

The port numbers used by JP1/IT Desktop Management - Manager were described separately for a single-server configuration and for a multi-server configuration.

The following information was combined into the Job Management Partner 1 Version 10 Job Management Partner 1/IT Desktop Management Overview and System Design Guide:

• A description of Microsoft products

• Icons and formats used in the manual

• Online Help

• Related manuals

• Related documents

• Notations used in the manual

• Abbreviations used in the manual

• Conventions, for example, kilobyte (KB)

• Glossary

A description stating that the default file name of the installation set is ITDMAgt.exe was added.

A description about using Autorun.inf to enable an installation to start automatically when a CD-R is used as the media for installing the agent was added.

Computers that are not connected to the management server via a network can now be managed by using the offline management functionality

You can now update the JP1/IT Desktop Management information by obtaining information from the support service.

The notes applying if JP1/IM and JP1/Base are not connected in a JP1/IM linkage system were improved.

The procedure for setting the information required to link with the MDM system was corrected.

A general procedure for updating the version of the entire JP1/IT Desktop Management system was added.

The procedure for updating the version of JP1/IT Desktop Management - Manager was corrected.

The description of how to update components was corrected.

A general procedure for overwrite-installing JP1/IT Desktop Management - Manager in a multi-server system was added.

A general procedure for updating the version of JP1/IT Desktop Management - Manager in a multi-server system was added.

The procedure for replacing a site server and the notes on the recreatelogdb command used to replace a site server were corrected.

A procedure for replacing a computer on which the network monitor is enabled was added.

The note on the recreatelogdb command executed with an argument other than -node was corrected.

A description of the stopservice (stopping services) command as a configuration-related command was added.

A description stating that the getlogs command uses the folder set in the TEMP user environment variable as a temporary folder was added.

A description of the case in which an agent is installed by copying a disk without executing the resetnid.vbs command in the reference material section was improved.

The port numbers used by JP1/IT Desktop Management - Manager were described separately for a single-server configuration and for a multi-server configuration.

You can now manage a maximum of 50,000 devices when operating a system in a multi-server configuration.

You can now link with JP1/IM to send notifications concerning JP1 events.

The URL of the login window for JP1/IT Desktop Management was added.

The following description was added: The Set the account to install Agent setting in the Create Agent Installer dialog box takes effect only if you install an agent in Windows 2000, Windows XP, or Windows Server 2003.

The following description was added: You can schedule the time to obtain the latest updated program information from the support service site by using Edit Import Schedule, which is displayed by selecting General, and then Product Update in the Settings module.

A solution for the following was added: When installing an agent by copying a disk, multiple devices are recognized as a single device.

The following was added: The time required to generate a new host name after the resetnid.vbs is executed.

The port numbers of the controller and remote control agent were modified.

The timing at which the host ID is regenerated was added.

The timing at which you are asked to change your password at login was added. In addition, the following description was added: You must change your password at login within 180 days of setting it.

A procedure for releasing a user account lock was added.

You can now link with an MDM product to manage smart devices.

The following description was added: A user ID used in authentication for Windows administrative share must be specified in the following format if the ID is to be authenticated as a domain user: user-ID@FQDN (fully qualified domain name), or domain-name\user-ID.

A detailed procedure for replacing a management server was added.

The action to be taken in the following case was added: The file for recording the execution status (deletelog_lasttime.txt) exists in the work folder when the deletelog command that deletes the site server operation log data is executed.

Port number 31000 was added to the list of port numbers for site servers.

You can now manage a maximum of 50,000 devices when operating a system in a multi-server configuration.

You can now link with JP1/IM to send notifications concerning JP1 events.

The URL of the login window for JP1/IT Desktop Management was added.

The following description was added: The Set the account to install Agent setting in the Create Agent Installer dialog box takes effect only if you install an agent in Windows 2000, Windows XP, or Windows Server 2003.

The following description was added: You can schedule the time to obtain the latest updated program information from the support service site by using Edit Import Schedule that is displayed by selecting General, and then Product Update in the Settings module.

A solution for the following was added: When installing an agent by copying a disk, multiple devices are recognized as a single device.

The following was added: The time required to generate a new host name after the resetnid.vbs is executed.

The port numbers of the controller and remote control agent were modified.

The timing at which the host ID is regenerated was added.

The following information was combined into the JP1 Version 10 JP1/IT Desktop Management Overview and System Design Guide:

• A description of Microsoft products

• Icons and formats used in the manual

• Online Help

• Related manuals

• Related documents

• Notations used in the manual

• Abbreviations used in the manual

• Conventions, for example, kilobyte (KB)

• Glossary

The timing at which you are asked to change your password at login was added. In addition, the following description was added: You must change your password at login within 180 days of setting it.

A procedure for releasing a user account lock was added.

You can now link with an MDM product to manage smart devices.

The following description was added: A user ID used in authentication for Windows administrative share must be specified in the following format if the ID is to be authenticated as a domain user: user-ID@FQDN (fully qualified domain name), or domain-name\user-ID.

A detailed procedure for replacing a management server was added.

The action to be taken in the following case was added: The file for recording the execution status (deletelog_lasttime.txt) exists in the work folder when the deletelog command that deletes site server operation log data is executed.

Port number 31000 was added to the list of port numbers for site servers.