A.3 Summary of amendments

Changes in 10-50

• 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.

Changes in 10-10

• 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.

Changes in 10-01

• The following information items are now collectively described in the Job Management Partner 1 Version 10 Job Management Partner 1/IT Desktop Management Overview and System Design Guide:

  • Abbreviated Microsoft product names

  • Conventions: Fonts and symbols

  • About help

  • Related manuals

  • Related documentation

  • Abbreviated product names (other than Microsoft product names)

  • Acronyms

  • Conversions: KB, MB, GB, and TB

  • Glossary

• A default file name (ITDMAgt.exe) for the installation set has been added.

• Information about automatic startup of agent installation has been added. When a CD-R is used as the agent installation media, agent installation can be started automatically by using Autorun.inf.

• The offline management functionality can now be used to manage computers that are not connected to the management server via a network.

• Information about JP1/IT Desktop Management can now be updated by acquiring support service information, including anti-virus product information.

• Notes on JP1/IM linkage systems when JP1/IM and JP1/Base are not connected have been improved.

• The procedure for setting information used to link with an MDM system has been corrected.

• An overview of upgrading the entire JP1/IT Desktop Management system has been added.

• The procedure for upgrading JP1/IT Desktop Management - Manager has been corrected.

• The explanation about how to update components has been corrected.

• An overview of the overwrite installation of JP1/IT Desktop Management - Manager in a multi-server configuration system has been added.

• An overview of upgrading JP1/IT Desktop Management - Manager in a multi-server configuration system has been added.

• A procedure for replacing site servers and notes on the recreatelogdb command used to replace site servers have been corrected.

• The procedure for replacing computers with network access control enabled has been added.

• Notes on executing the recreatelogdb command with an argument other than -node specified have been corrected.

• A description of the stopservice command that stops services has been added. This command can be used for building-related operations.

• For the getlogs command, information about using the folder set for the TEMP user environment variable as a general folder has been added.

• The description related to reference information when an agent is installed from a disk copy without executing the resetnid.vbs command has been improved.

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

• A maximum of 50,000 devices can now be managed by using a multi-server configuration system.

• JP1 events can now be reported by linkage with JP1/IM.

• The URL of the Login window for JP1/IT Desktop Management was included.

• Information about settings for Set the account to install Agent in the Create Agent Installer dialog box that apply only when an agent is installed on a computer whose OS is Windows 2000, Windows XP, or Windows Server 2003, was added.

• Information about setting a schedule for obtaining the latest update program information from the support service site by selecting General, Customer Support configuration, and Edit Import Schedule of the Settings module was added.

• Corrective action for multiple devices treated as a single device when the agent is installed from a disk copy were added.

• The time it takes after execution of the resetnid.vbs command for a new host name to be generated was added.

• The Controller and Remote Control Agent port numbers were been corrected.

• The timing for regeneration of a host identifier was added.

• A description of when users are prompted to change their passwords at login was added. Also, a description stating that any login password must be changed every 180 or fewer days was added.

• The procedure for unlocking a user account was added.

• Smart devices can now be managed by linkage with the MDM products.

• A description stating the following was added: If a domain user is authenticated by a Windows administrative share, the user ID must be in user-ID@FQDN (FQDN: fully qualified domain name) or in domain-name\user-ID format.

• Detailed procedures for replacing management servers were added.

• Corrective action for executing the deletelog command that deletes site server operation log data, when the file for recording the execution status (deletelog_lasttime.txt) is in the work folder was added.

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

To Page Top