Read this first

Organization of this preface

What you can do with JP1/IT Desktop Management 2
What is explained in this manual
Navigating the manuals

■ What you can do with JP1/IT Desktop Management 2

Are you spending more time than is necessary on security management of your organization's computers? Are you aware that your currently-recognized computer information might be out of date?

By using JP1/IT Desktop Management 2, you can oversee all the latest information about the computers installed on your organization. With JP1/IT Desktop Management 2, you can centrally manage business-critical machines, such as printers, network devices, and smart phones, as well as computers. Deploy JP1/IT Desktop Management 2, and devote time currently spent on management to more productive business operations.

[Figure]

To Page Top

■ What is explained in this manual

The purpose of this manual (Asset and Distribution Management: Getting Started) is to explain how to perform basic operations for computer management in accordance with the rules set by the applicable organization. This section describes the computer management rules that are assumed as standard in this manual, and provides notes on using this manual.

Computer management rules assumed in this manual

[Figure]

Security management must be implemented following the management rules set by the organization. These management rules define the organization's computer configuration and operation (Security policy). JP1/IT Desktop Management 2 judges security status based on this security policy. This manual uses the default policy, which is the security policy provided by JP1/IT Desktop Management 2.

When JP1/IT Desktop Management 2 is deployed, the default policy is automatically applied to all devices managed by JP1/IT Desktop Management 2. The default policy does not affect execution of any currently-used applications.

Notes on using this manual

[Figure]

For JP1/IT Desktop Management 2 - Manager, the descriptions of operations assume that a maximum of 5,000 devices are to be managed in the system configuration shown in the above figure. A relay system can manage a maximum of 1,000 devices.

For JP1/IT Desktop Management 2 - Operations Director, the descriptions of operations assume a minimum configuration consisting of one management server and a maximum of 1,000 devices. Relay systems are not to be built.

Note:: Compared with JP1/IT Desktop Management 2 - Manager, some functions of JP1/IT Desktop Management 2 - Operations Director are restricted. For details about functional restrictions, see the description Functional restrictions in JP1/IT Desktop Management 2 - Operations Director in the JP1/IT Desktop Management 2 Overview and System Design Guide.

Therefore, the system configuration described in this manual uses five relay systems. If the number of devices to be managed exceeds 5,000, multiple system configurations must be prepared according to the number of devices. For details, see the description Examining the system configuration in the JP1/IT Desktop Management 2 Overview and System Design Guide.

Note that the descriptions in this manual assume that the user has subscribed to support services. Subscribers can receive maintenance and technical support services for JP1/IT Desktop Management 2.

Non-subscribers can also use this manual. Perform the procedures as described, and when you encounter 2.3.1 Downloading the latest security updates from the support service site, read If support services are not subscribed. To use the service for subscribing support services, you must connect to the Internet.

To Page Top

■ Navigating the manuals

The following figure shows the JP1/IT Desktop Management 2 manuals, and indicates for what purpose you need to read these manuals.

[Figure]

A reference in one manual to another manual is indicated in the following format: For details about something, see topic-title in the manual-name. Using topic-title as a keyword, search for the relevant section in the target manual.

Descriptions of operations on windows assume the following respective environments:

Operations on the management server: Environment running Windows Server 2012
Operations in the Remote Install Manager: Environment running Windows 7
Operations on the administrator's computer: Environment running Windows 7, Internet Explorer 11.0, and Microsoft Excel

As a result of product improvements and other changes, some of the windows in this manual might differ from the windows of the product you are using.

Conventions: Fonts and symbols

The following table explains the text formatting conventions used in this manual:

Text formatting	Convention
Bold	Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name.
Italic	Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example: Write the command as follows: `copy` `source-file` `target-file` The following message appears: `A file was not found. (file =` `file-name)` Italic characters are also used for emphasis. For example: Do not delete the configuration file.
`Monospace`	Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example: At the prompt, enter `dir`. Use the `send` command to send mail. The following message is displayed: `The password is incorrect.`

Text formatting

Convention

Bold

Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:

From the File menu, choose Open.
Click the Cancel button.
In the Enter name entry box, type your name.

Italic

Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:

Write the command as follows:

copy source-file target-file
The following message appears:

A file was not found. (file = file-name)

Italic characters are also used for emphasis. For example:

Do not delete the configuration file.

Monospace

Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:

At the prompt, enter dir.
Use the send command to send mail.
The following message is displayed:

The password is incorrect.

The following table explains the symbols used in this manual:

Symbol	Convention
`\|`	In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example: `A\|B\|C` means A, or B, or C.
`{ }`	In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example: `{A\|B\|C}` means only one of A, or B, or C.
`[ ]`	In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example: `[A]` means that you can specify `A` or nothing. `[B\|C]` means that you can specify `B`, or `C`, or nothing.
`...`	In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted. In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example: `A,` `B,` `B,` `...` means that, after you specify `A,` `B,` you can specify B as many times as necessary.

Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

Version 1.00 (or 1.0) is written as 01-00.
Version 2.05 is written as 02-05.
Version 2.50 (or 2.5) is written as 02-50.
Version 12.25 is written as 12-25.

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

To Page Top