Job Management Partner 1 Version 10 Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager Description, User's Guide, Reference and Operator's Guide

3021-3-379(E)

Notices

Relevant program products

For details about the applicable OS versions, and the service packs and patches required for Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager, see the Release Notes.

P-2642-7EAL Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager 10-50

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager consists of the following components:

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Smart Device Manager) (For Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 and 64-bit edition of Windows Server 2008)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Communication Server) (For Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 and 64-bit edition of Windows Server 2008)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Messaging Server) (For Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 and 64-bit edition of Windows Server 2008)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Smart Device Android Agent) (For Android 4.1 or later)

JP1/IT Desktop Management 2 - Smart Device Manager (Smart Device iOS Agent) (For iOS 7.0 or later)

Trademarks

HITACHI, JP1, Job Management Partner 1, uCosminexus are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.

Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.

Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Microsoft Exchange server is a product name of Microsoft Corporation in the U.S. and other countries.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

RSA and BSAFE are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Other company and product names mentioned in this document may be the trademarks of their respective owners.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.

This product includes software developed by IAIK of Graz University of Technology.

Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This product includes software developed by the University of California, Berkeley and its contributors.

This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).

Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/).

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by Andy Clark.

This product includes RSA BSAFE Cryptographic software of EMC Corporation.

Microsoft product screen shots

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

Exchange

Microsoft(R) Exchange Server

IE

Internet Explorer

Windows(R) Internet Explorer(R)

Windows

Windows Server 2008

Windows Server 2008

Microsoft(R) Windows Server(R) 2008 Enterprise

Microsoft(R) Windows Server(R) 2008 Standard

Windows Server 2008 R2

Microsoft(R) Windows Server(R) 2008 R2 Datacenter

Microsoft(R) Windows Server(R) 2008 R2 Enterprise

Microsoft(R) Windows Server(R) 2008 R2 Standard

Windows Server 2012

Windows Server 2012

Microsoft(R) Windows Server(R) 2012 Datacenter

Microsoft(R) Windows Server(R) 2012 Standard

Windows Server 2012 R2

Microsoft(R) Windows Server(R) 2012 R2 Datacenter

Microsoft(R) Windows Server(R) 2012 R2 Standard

Restrictions

Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.

Material contained in this document may describe Hitachi products not available or features not available in your country.

No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.

Issued

Oct. 2015: 3021-3-379(E)

Copyright

Copyright (C) 2015, Hitachi, Ltd.

Copyright (C) 2015, Hitachi Solutions, Ltd.

Preface

This manual provides an overview of Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (abbreviated hereafter to JP1/ITDM2 - SDM) and describes its features. This manual also explains how to design and build a system, how to use JP1/ITDM2 - SDM, and provides operation examples.

Job Management Partner 1 is abbreviated in this manual as JP1.

Intended readers

This manual is intended for:

Those who are considering installing JP1/ITDM2 - SDM or who want to design JP1/ITDM2 - SDM systems.

Those who want to gain an overview of JP1/ITDM2 - SDM products and function details.

Those who want to build a JP1/ITDM2 - SDM system.

Those who want to learn how to build JP1/ITDM2 - SDM.

Those who want to use JP1/ITDM2 - SDM to manage smart devices in the organization.

Those who want to know how to use and operate JP1/ITDM2 - SDM.

Organization of the manual

This manual is organized into the following chapters.

1. Product Overview

This chapter provides an overview of JP1/ITDM2 - SDM, and describes its system components.

2. Features of JP1/ITDM2 - SDM

This chapter explains JP1/ITDM2 - SDM functions.

3. System Configuration

This chapter describes how to build a system.

4. Managing Smart Devices by Using JP1/ITDM2 - SDM

This chapter explains how to operate and utilize JP1/ITDM2 - SDM.

5. Starting and Ending Operations

This chapter explains how to start and end operations in JP1/ITDM2 - SDM.

6. Managing User Accounts

This chapter explains how to manage user accounts.

7. Managing the Security Status

This chapter explains how to manage security of the smart devices in an organization and how to understand the security status.

8. Smart Device Management

This chapter explains how to collect information from smart devices and how to grasp the current status in an organization.

9. Managing Applications

This chapter explains how to manage applications to be distributed to smart devices in an organization.

10. Event Reference

This chapter explains how to reference events that are output by JP1/ITDM2 - SDM.

11. Customizing Settings

This chapter describes the items that can be customized in the Settings module and during setup.

12. Database Management

This chapter explains how to manage a database by using the JP1/ITDM2 - SDM commands.

13. Troubleshooting

This chapter describes the actions to be taken when a problem occurs during operation of JP1/ITDM2 - SDM.

14. GUI Reference

This chapter describes the GUI of JP1/ITDM2 - SDM.

15. Commands

This chapter describes the JP1/ITDM2 - SDM commands.

16. Definition Files

This chapter describes the definition file of JP1/ITDM2-SDM.

17. Messages

This chapter lists the JP1/ITDM2 - SDM messages.

1 Product Overview

This chapter provides an overview of JP1/ITDM2 - SDM and its system components.

1.1 Product overview

The JP1/ITDM2 - SDM product manages smart device operations and provides security measures.

An increasing number of businesses use smart devices (such as smart phones and tablet PCs) as IT devices, requiring management of such devices in the same way as other IT devices.

JP1/ITDM2 - SDM supports management of smart device operation and security in an organization, and enables unified management of PCs, server devices, and smart devices from JP1/IT Desktop Management 2.

1.1.1 Product benefits

With JP1/ITDM2 - SDM, you can understand the current status of smart devices, ensure compliance with smart device usage guidelines, prevent information leakage if a device is stolen or lost, and distribute applications. JP1/ITDM2 - SDM also provides integrated management of IT assets.

The smart device administrator must manage all smart devices in a manner appropriate for the business goals of the organization. The administrator must also prevent users from using smart devices for non-business purposes, and take preventive measures against leakage of business information from smart devices.

JP1/ITDM2 - SDM supports unified management of smart devices based on the following points:

Understanding the current status of smart devices

Ensuring compliance with smart device usage guidelines

Preventing information leakage if a smart device is stolen or lost

Distributing applications to smart devices

Integrated management of IT assets

Understanding the current status of smart devices

Increasing use of smart devices in the organization makes it difficult to know where (and by whom) devices are being used. JP1/ITDM2 - SDM displays a list of smart devices owned by the organization, enabling the administrator to easily understand smart device information. For example, the administrator can easily identify available devices and quickly distribute them as required.

Ensuring compliance with smart device usage guidelines

The smart device administrator must discourage use of smart devices for non-business purposes. JP1/ITDM2 - SDM applies security rules to smart devices in order to notify the administrator of a violation of rules, and to restrict a specific smart device function. For example, allowed phone numbers, Web sites, and applications can be defined in a security policy. If that security policy is applied to smart devices, any use of a disallowed phone number, Web site, or application will be reported to the administrator. In addition, use of smart device cameras can be prohibited if such functionality is not necessary for business purposes.

Preventing information leakage if a smart device is stolen or lost

JP1/ITDM2 - SDM can remotely lock or initialize a lost or stolen device to prevent unauthorized use or information leakage by a third party.

Distributing applications to smart devices

JP1/ITDM2 - SDM provides unified management of applications used for in-company business, and allows for simultaneous distribution of business applications to smart devices. This allows users in the organization to use the same applications, and simplifies the distribution process.

Integrated management of IT assets

Smart device information in JP1/ITDM2 - SDM can be viewed and manipulated from JP1/IT Desktop Management 2. This allows the administrator to manage smart devices in the same way as other IT assets (such as PCs and server devices), by simply using JP1/IT Desktop Management 2.

1.1.2 Flow of smart device management

JP1/ITDM2 - SDM manages smart devices from their initial purchase to final disposal, within an organization.

The following figure shows the flow from purchase to disposal of a smart device.

When you purchase a smart device, register information about the device in JP1/ITDM2 - SDM. Install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device, and then distribute the smart device to a user.

For distributed smart devices, manage the security status and applications. If a user loses a smart device or if it is stolen, take action such as remotely locking or initializing the device.

If the smart device is currently not being used, change the setting to Unmanaged, and then store the smart device. If there is no plan to use the smart device later, delete the registration information from JP1/ITDM2 - SDM, and then dispose of the device.

1.2 System components

In this manual, when referring to a system managed by JP1/ITDM2 - SDM, defined names are used for system components such as smart devices and the servers on which JP1/ITDM2 - SDM is installed.

The following table gives definitions used in JP1/ITDM2 - SDM for basic system components.

No.

Component name

Definition

1

Smart device manager

The server on which JP1/ITDM2 - SDM (Smart Device Manager) is installed as a relay system. A database for storing the various information managed by JP1/ITDM2 - SDM is created on the management server.

One smart device manager can manage up to 2,000 smart devices.

2

ITDM2 management server

A component that manages IT assets (such as PCs and server devices) and smart devices, in a unified manner

3

Administrator's computer

A computer used by the administrator for on-screen operation of JP1/ITDM2 - SDM. The administrator displays JP1/ITDM2 - SDM program modules from a Web browser. Therefore, JP1/ITDM2 - SDM can be operated on any computer that can access the smart device manager. The smart device manager itself can be used as the administrator's computer.

4

Communication server

A server on which JP1/ITDM2 - SDM (Communication Server) is installed for data communication with smart devices.

This server collects inventory information from smart devices and stores it in the database. If an inventory acquisition request, lock or initialization request, or policy application request is sent from the administrator, the communication server requests the smart device to perform processing.

5

Messaging server

A server on which JP1/ITDM2 - SDM (Messaging Server) is installed. This server provides synchronization between an Android device and JP1/ITDM2 - SDM.

If an inventory acquisition request or lock or initialization request is sent from the administrator, this server requests the Android device to connect to the communication server.

6

Android device

An Android device on which JP1/ITDM2 - SDM (Smart Device Android Agent), which monitors and controls the Android device, is installed.

The Android device sends smart device information (such as inventory and location information) to JP1/ITDM2 - SDM, and performs processing in response to a lock or initialization request from the administrator.

7

iOS device

An iOS device on which JP1/ITDM2 - SDM (Smart Device iOS Agent), which monitors and controls the iOS device, is installed.

The iOS device sends smart device information such as inventory information to JP1/ITDM2 - SDM.

8

APNs server

An Apple server that controls iOS devices. Inventory acquisition requests and lock or initialization requests from JP1/ITDM2 - SDM to the iOS device are sent via the APNs server.

The following figure shows an example of a basic system configuration consisting of these components and managed by JP1/ITDM2 - SDM.

Related Topics

3.4 Components of JP1/ITDM2 - SDM

1.3 Program modules

In JP1/ITDM2 - SDM you can access functions by clicking the buttons at the top and opening a different module.

The operations you can perform in each module are described next.

Home module

In the Home module, you can get an overview of the information managed by JP1/ITDM2 - SDM, presented in panels. From each panel you can navigate to another module to perform a management operation.

Security module

In the Security module, you can view the list of security rules defined for your organization. You can also understand which security rules apply to smart devices.

Smart Device module

In the Smart Device module, you can view the list of smart devices managed by your organization. You can also check hardware information and installed applications for managed smart devices, and perform remote operation on smart devices. This allows you to take action for smart devices that have security problems.

Distribution module

In the Distribution module, you can view the list of applications to be distributed to Android devices. You can also distribute to or remove applications from managed Android devices, and instruct the Android devices to install or uninstall applications.

Events module

In the Events module, you can check events that occurred during JP1/ITDM2 - SDM operation.

Settings module

In the Settings module, you can customize a variety of JP1/ITDM2 - SDM information, such as user accounts and email notifications.

1.3.1 Basic module layout

The following describes the basic layout of the JP1/ITDM2 - SDM modules and the terminology used for the module components.

Menu area

Menus are specific to the selected module. When you select an item here, corresponding information appears in the information area.

Information area

Displays information according to the item selected in the menu area.

Tabs

The tabs in the lower part of the information area show detailed information about any item selected in the upper part of the information area.

Menu bar

The menus at the top of screen are common to all modules.

System

Logs the user out of JP1/ITDM2 - SDM.

Go

Edits the user account of the logged-in user.

Help

Displays the Help for JP1/ITDM2 - SDM and version information of the product.

Log Out button

Logs the user out of JP1/ITDM2 - SDM. The user ID, permissions, and login date/time for the user account of the logged-in user are displayed on the left of the Log Out button. Click the user ID to edit your account information or change your password.

Buttons at the top of the window

These buttons allow you to access functions by switching to another module.

1.3.2 Working with the Home module

The Home module appears immediately after the user logs in. This module works as the base point of JP1/ITDM2 - SDM operations.

In the Home module, each of the panels presents an overview of information managed by JP1/ITDM2 - SDM. These panels allow you to quickly check the status of information managed by each module.

After checking the status, click a button in a module (or a link in a panel) to navigate to another module, and then start management operation.

1.3.3 Working with the Security module

In the Security module, you can create security rules. By applying security rules to smart devices, you can manage the security status and take actions for smart devices that have security problems.

The Security module provides the following views:

Security Policy List view

Android Policy List view

iOS Profile List view

Each view is described next.

Security Policy List view

You can create security policies, which can then be applied to smart devices.

Android Policy List view

You can create Android policies, which can then be applied to Android devices.

iOS Profile List view

You can register iOS profiles, which can then be applied to iOS devices.

1.3.4 Working with the Smart Device module

In the Smart Device module, you can check or register smart device information, and apply security rules created in the Security module to smart devices. You can also perform remote operations such as locking and initializing smart devices.

The Smart Device module provides the following views:

Managed Smart Device List view

Unmanaged Smart Device List view

Each view is described next.

Managed Smart Device List view

You can check information about managed smart devices.

In the menu area, select Android Smart Device to display a list of Android devices, or select iOSsmart Device to display a list of iOS devices.

When you select an item in the upper part of the information area, detailed information about that item is displayed on the tabs in the lower part of the information area. You can check events that have occurred, call history, Web browsing history, software (applications), hardware, running applications, running services, system information, security, and Bluetooth connection information.

Unmanaged Smart Device List view

You can check information about unmanaged smart devices.

Detailed information about the smart device selected in the upper part of the information area is displayed on the tabs in the lower part of the information area. You can check events and system information.

Note that you can set an unmanaged smart device to Managed by applying a security policy and an Android policy, or a security policy and an iOS profile, to that smart device.

1.3.5 Working with the Distribution module

In the Distribution module, you can manage applications to be distributed to smart devices. You can also distribute applications to smart devices, and then instruct the smart devices to install the applications. You can also instruct the smart devices to uninstall the distributed applications, and then remove the applications.

Note that you can manage Android applications only.

The Distribution module provides the following views:

Distributed Application List view

Android Application view

Each view is described next.

Distributed Application List view

You can view a list of applications to be distributed to smart devices, and a summary of the distributed applications.

Android Application view

You can view a list of Android applications registered in JP1/ITDM2 - SDM.

When you select an Android application in the upper part of the information area, a list of smart devices is displayed by distribution status in each tab in the lower part. Three types of distribution status are displayed: Not Distributed, Distributed, and Installed. You can also distribute to and remove applications from smart devices, and instruct smart devices to install and uninstall the applications.

1.3.6 Working with the Events module

In the Events module, you can check events that occurred during JP1/ITDM2 - SDM operation. For example, whether a security judgment operation terminated normally is displayed as an event.

You can view an event in detail by clicking the link in Description.

Some events require a quick response. Attend to Critical events first, followed by Warning events. Identify the cause of the event from the event details, and take the appropriate action.

When you have finished dealing with an event, change its status to Ack. By changing the event status, you can easily identify whether an event has been resolved.

1.3.7 Working with the Settings module

In the Settings module, you can specify settings required for operating JP1/ITDM2 - SDM, such as user account management and email notification when an event occurs.

The Settings module provides the following views:

User Management

Account Management view

Events

Event Notifications view

General

SMTP server view

Each view is described next.

Account Management view

You can add, edit, and delete JP1/ITDM2 - SDM user accounts.

Event Notifications view

You can specify the severity and type of events for which email notifications will be sent, event notifications to be ignored, and users to which email notification will be sent if a certain event occurs.

SMTP server view

You can specify connection information for the mail server when sending an event notification email.

2 Features of JP1/ITDM2 - SDM

This chapter provides details about JP1/ITDM2 - SDM features, such as security management, smart device management, application management, and the event viewer.

2.1 List of features

The following lists and describes JP1/ITDM2 - SDM features.

List of features

No.

Feature

Description

1

System summary

You can check the system summary that contains the following:

Smart device status

Event status

Database status and hard disk usage

Status of certificates for MDM

2

User account management

You can create user accounts appropriate for the role of the JP1/ITDM2 - SDM user.

3

Security management

You can create a security policy for smart devices. You can also create an Android policy or register an iOS profile appropriate for smart devices. You can determine the security status by applying these policies (or profiles) to smart devices.

4

Smart device management

You can check the list of smart devices registered in JP1/ITDM2 - SDM. You can also check detailed device information such as hardware and software information for each smart device. In addition, you can perform remote operation such as locking and initializing smart devices that have security problems.

5

Application management

You can perform unified management of applications to be distributed to smart devices. You can also distribute to, and remove applications from, managed smart devices, and instruct smart devices to install or uninstall the applications.

6

Event viewer

You can check events that occurred. Execution results of JP1/ITDM2 - SDM functions can also be displayed as events.

Related Topics

2.2 Displaying a system summary

2.3 Managing user accounts

2.4 Managing security

2.5 Managing smart devices

2.6 Managing applications

2.7 Displaying events

2.2 Displaying a system summary

You can check the status of smart devices registered in JP1/ITDM2 - SDM and the event status. You can also check whether the database is backed up on the smart device manager, check the hard disk usage and free space, and check the status of certificates for MDM.

System Summary panel

Displays summary information for the smart devices registered in JP1/ITDM2 - SDM.

You can check the following information displayed below Smart Device Status:

Total number of registered smart devices, and the difference from the previous day's number of smart devices

Number of managed smart devices, and the difference from the previous day's number of smart devices

Number of unmanaged smart devices, and the difference from the previous day's number of smart devices

Click the link on the number of managed or unmanaged smart devices to display the Smart Device module, which allows you to check details about the smart devices.

Event Summary panel

Displays the total number of events that occurred in one week, and the number of events by event type.

If an event whose severity is Critical occurred, the icon is displayed at the left of the event type. At this time, click the link on the number of events to display the Events module, which allows you to check the contents of events.

You can also change the display period to check the number of events that occur over either a single day, or a three-day period.

Database and Disk Usage panel

You can check the following:

Whether the database is backed up

Hard disk usage and free space

Hard disk usage for the database, and free space

Tip

You can move the database backup folder from a nearly full disk to one with enough free space, or free up disk space by removing data that is no longer needed.

Status of Certificate for MDM panel

You can check the following:

Validity of the MDM certificate

Expiration date of the MDM certificate

Related Topics

2.5 Managing smart devices

2.7 Displaying events

14.3 Home module

14.5 Smart Device module

14.7 Events module

2.3 Managing user accounts

If several administrators will be using JP1/ITDM2 - SDM, you can create a user account for each administrator.

You can set the following parameters for user accounts that define the range of operations the user can perform.

Permission

You can set permissions according to the range of operations allowed for a user: for example, a manager who only needs to view information can have permissions different from a system administrator who manages smart devices.

2.3.1 Locking user accounts

If a user fails to log in to JP1/ITDM2 - SDM three consecutive times, the user account is locked. That user cannot log in again until the user account is unlocked.

You can find out whether any accounts are locked by accessing the Account Management view in the Settings module from a user account with the system administrator permission. You can then use the same view to unlock the account.

Disabled appears as the Status of locked user accounts in the Account Management view.

Related Topics

2.3.2 User account permissions

6.7 Unlocking a user account

14.8.1 Account Management view

2.3.2 User account permissions

There are two permissions you can assign to user accounts in JP1/ITDM2 - SDM:

System administrator permission

A user with this permission has full access to the features of JP1/ITDM2 - SDM.

View permission

A user with this permission is able to view the information managed by JP1/ITDM2 - SDM. Users are assigned view permission by default.

Related Topics

2.3.1 Locking user accounts

2.3.3 List of operations that cannot be performed with the view permission

2.3.3 List of operations that cannot be performed with the view permission

The following describes the operations that cannot be performed by a user account that has been assigned the view permission.

Operations that cannot be performed with the view permission

Operation window

Operation

Security module

Security Policy List view

Operations on security policies (adding, editing, and deleting)

Updating notes about a security policy

Android Policy List view

Operations on Android policies (adding, editing, and deleting)

Updating notes about an Android policy

iOS Profile List view

Operations on iOS profiles (adding and deleting)

Updating notes about an iOS profile

Smart Device module

Managed Smart Device List view

The following operations selected from Action:

Update Device Details

Initialize Smart Device

Lock Smart Device

Reset Smart Device Passcode

Send Notification

Set to Unmanaged

Apply Security Policy

Apply Android Policy

Apply iOS Profile

Add Smart Device

Import Smart Device List

Events tab of Managed Smart Device List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Call History tab of Managed Smart Device List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Allow

Web Browsing History tab of Managed Smart Device List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Allow

Prohibit

Software tab of Managed Smart Device List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Allow

Prohibit

Bluetooth Connection Information tab of Managed Smart Device List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Unmanaged Smart Device List view

The following operations selected from Action:

Apply Security Policy

Apply Android Policy

Apply iOS Profile

Deleting smart devices

Events tab of Unmanaged Smart Device List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Distribution module

Distributed Application List view

Operations on distributed applications (adding, editing, and deleting)

Updating notes about a distributed application

Android Application view

Operations on Android applications (adding, editing, and deleting)

List of Smart Devices Not Distributed To tab of Android Application view

The following operations selected from Action:

Application Distribution

Application Installation

List of Smart Devices Distributed To tab of Android Application view

The following operations selected from Action:

Application Installation

Application Deletion

List of Smart Devices Installed To tab of Android Application view

The following operations selected from Action:

Application Deletion

Events module

Event List view

The following operations selected from Action:

Set to Confirmed

Set to Not Confirmed

Settings module

Account Management view

User account management

Event Notifications view

Setting up event notifications

SMTP Server view

Setting up the mail server

Related Topics

2.3.2 User account permissions

2.4 Managing security

You can manage smart devices by creating security rules and then applying them to the smart devices.

2.4.1 Types of security rules

There are three types of security rules: Security policy, Android policy, and iOS profile.

Security policy

This is a policy used to monitor the usage of smart devices. Phone numbers, Web sites, and applications can be set for a security policy. JP1/ITDM2 - SDM checks this policy and smart device usage history, and then issues an event if any use that does not comply with the policy is found. The administrator can detect unauthorized use of a smart device by checking the issued event.

Android policy

This is an operation policy that is set for Android devices. An Android policy can specify password rules and restrict use of the camera function.

iOS profile

This is an operation policy that is set for iOS devices. A configuration profile created by using the iPhone Configuration Utility (provided by Apple) can be registered as an iOS profile. An iOS policy can specify passcode rules and restrict use of the camera function.

The following lists the typical functions that can be disabled or monitored by using security rules:

Function

Android device

iOS device

Camera

Can be disabled

Can be disabled

Application installation (using App Store)

Cannot be disabled

Can be disabled

Call history

Can be monitored

Cannot be monitored

Web browsing history

Can be monitored

Cannot be monitored

Application use history

Can be monitored

Cannot be monitored

Legend:

Disable: Specified in an Android policy or iOS profile

Monitor: Specified in a security policy

Related Topics

2.4.2 Managing a security policy

2.4.3 Items that can be set for a security policy

2.4.4 Managing an Android policy

2.4.5 Items that can be set for an Android policy

2.4.6 Managing an iOS profile

2.4.7 Items that can be set in an iOS profile

2.4.2 Managing a security policy

In the Security Policy List view of the Security module, create and manage a security policy.

Create a security policy.

Create a security policy based on your organization's security principles. You can create multiple security policies.

Edit a security policy.

If the security trends change or your organization's security principles are changed, edit a security policy.

Security trends change together with changes to smart devices and the network environment. By always incorporating security trends into your organization, you will be able to robustly manage the security status.

Delete a security policy.

Delete security policies that are no longer needed because, for example, the management structure changed or multiple security policies were combined.

Related Topics

2.4.3 Items that can be set for a security policy

7.1 Using security policies

2.4.3 Items that can be set for a security policy

For a security policy, you can set the following items whose use is monitored: phone numbers, Web sites, and applications.

Items that can be set for a security policy

No.

Configuration item

Description

1

Phone Number

Set phone numbers to be monitored. If a phone number that is not registered in this list is used, an event is issued to notify the administrator.

2

Web Site

Set Web sites to be monitored.

If a Web site that is not specified in Whitelist or a Web site specified in Blacklist is browsed, an event is issued to notify the administrator.

3

Application

Set applications to be monitored. If an application that is not specified in Whitelist or an application specified in Blacklist is installed, an event is issued to notify the administrator.

For applications specified in Whitelist, you can also specify whether installation is required. If an application that must be installed is not installed, an event is issued to notify the administrator.

Related Topics

2.4.2 Managing a security policy

14.4.1 Security Policy List view

2.4.4 Managing an Android policy

In the Android Policy List view of the Security module, create and manage an Android policy.

Create an Android policy.

Create an Android policy based on your organization's security principles. You can create multiple Android policies.

Edit an Android policy.

If your organization's security principles are changed, edit an Android policy.

Delete an Android policy.

Delete Android policies that are no longer needed because, for example, the management structure changed or multiple Android policies were combined.

Related Topics

2.4.5 Items that can be set for an Android policy

7.2 Using Android policies

2.4.5 Items that can be set for an Android policy

For an Android policy, you can set password rules, the time that can elapse before the Android device is automatically locked, and whether the camera can be used.

Items that can be set for an Android policy

No.

Configuration item

Description

1

Password Complexity

Set the password complexity as one of the following types:

1 (Alphabetic password)

2 (The password requires alphabetic letters and numbers.)

3 (The password requires alphabetic letters, numbers, and special symbols.)

4 (Password made of any string)

5 (Biometrics)

The initial value is 1 (Alphabetic password)

2

Min. Password Length

Set the number of characters required for the password.

This item is valid if Password Complexity is not set to 5 (Biometrics).

The initial value is 4. The specifiable values are 4 to 16.

3

Minimum Number of Alphabetic Characters Required in the Password

Set the minimum number of alphabetic characters required in the password.

This item is valid if Password Complexity is set to 3 (The password requires alphabetic letters, numbers, and special symbols.).

The initial value is - (not limited). The specifiable values are - (not limited) and 1 to 4.

4

Minimum Number of Lowercase Characters Required in the Password

Set the minimum number of lowercase characters required in the password.

This item is valid if Password Complexity is set to 3 (The password requires alphabetic letters, numbers, and special symbols.).

The initial value is - (not limited). The specifiable values are - (not limited) and 1 to 4.

5

Minimum Number of Uppercase Characters Required in the Password

Set the minimum number of uppercase characters required in the password.

This item is valid if Password Complexity is set to 3 (The password requires alphabetic letters, numbers, and special symbols.).

The initial value is - (not limited). The specifiable values are - (not limited) and 1 to 4.

6

Minimum Number of Non-Alphabetic Characters Required in the Password

Specify the minimum number of non-alphabetic characters required in the password.

This item is valid if Password Complexity is set to 3 (The password requires alphabetic letters, numbers, and special symbols.).

The initial value is - (not limited). The specifiable values are - (not limited) and 1 to 4.

7

Minimum Number of Numerals Required in the Password

Specify the minimum number of numeric characters required in the password.

This item is valid if Password Complexity is set to 3 (The password requires alphabetic letters, numbers, and special symbols.).

The initial value is - (not limited). The specifiable values are - (not limited) and 1 to 4.

8

Minimum Number of Special Characters Required in the Password

Specify the minimum number of special characters required in the password.

This item is valid if Password Complexity is set to 3 (The password requires alphabetic letters, numbers, and special symbols.).

The initial value is - (not limited). The specifiable values are - (not limited) and 1 to 4.

9

Timeout Value Until Password Expires

Specify the number of days that can elapse before the password must be changed. Specify 0 to disable the function.

The initial value is 0 (Disabled). The specifiable values are 0 to 730 (days).

10

Password History Limit

This function prevents reuse of the password more than the specified number of times. Specify 0 to disable the function.

The initial value is 0 (Disabled). The specifiable values are 0 to 50.

11

Maximum Number of Retries for Password Failure

Set the maximum number of retries allowed when the user fails to enter the password. Specify 0 to disable the function.

The initial value is 0 (Disabled). The specifiable values are 0 and 4 to 10.

12

Maximum Value for Inactive Time Lock

Set the time allowed for idling before the Android device is automatically locked. Specify 0 to disable the function.

The initial value is 0 (Disabled). The specifiable values are 0, 1 to 5, 10, and 15 (minutes).

13

Request for Storage Encryption

Specify whether to perform encryption for internal storage.

If the Android device supports storage encryption, this function is enabled by selecting the check box.

This check box is cleared (the function is disabled) by default. You can select the check box to enable the function or clear the check box to disable the function.

14

Timeout Value for Failed Server Connection

Specify the maximum amount of time that can elapse before the Android device is initialized if the Android device cannot connect with JP1/ITDM2 - SDM. Select OFF to disable the function.

The initial setting is OFF. You can select OFF or ON. When ON is selected, the specifiable values are 1 to 60 (minutes).

15

Camera Use Prohibited

Prohibit use of the camera.

This check box is cleared (camera can be used) by default. You can select the check box to prohibit use of the camera, or clear the check box to permit use of the camera.

Important note

After a password rule is applied, the rule takes effect the next time the password is changed.

Related Topics

2.4.4 Managing an Android policy

14.4.11 Android Policy List view

2.4.6 Managing an iOS profile

In the iOS Profile List view of the Security module, you can manage iOS profiles.

Register an iOS profile.

Use the iPhone Configuration Utility (provided by Apple) to create a configuration profile based on your organization's security principles, and then register that profile as an iOS profile. You can register multiple iOS profiles.

Export an iOS profile.

If your organization's security principles are changed or a new environment must be created, export the iOS profile as an XML file. You can import the exported file to the iPhone Configuration Utility (provided by Apple) by changing the extension to .mobileconfig. If necessary, edit the configuration profile, and then register it again as an iOS profile.

Delete an iOS profiles.

Delete iOS profiles that are no longer needed because, for example, the management structure changed or multiple iOS profiles were combined.

Related Topics

2.4.7 Items that can be set in an iOS profile

7.3 Using iOS profiles

2.4.7 Items that can be set in an iOS profile

In an iOS profile, you can set items of a configuration profile that can be created by using the iPhone Configuration Utility.

To find these items, please visit Apple's website.

Related Topics

2.4.6 Managing an iOS profile

2.5 Managing smart devices

You can register information about smart devices and check the latest information in a list. You can also apply security rules to smart devices and perform remote operations such as locking and initializing smart devices.

2.5.1 Managing managed smart devices

The Managed Smart Device List view of the Smart Device module displays a list of managed smart devices. In this view, you can register a smart device, apply security rules, and perform remote operation such as locking or initializing smart devices.

Checking smart device information

In the menu area, select Android Smart Device or iOS Smart Device to view the list of smart devices for each OS.

When you select a smart device in the list, detailed information is displayed on the tabs in the lower part of the information area. The following describes the information you can check on each tab:

Tab name

Description

Events tab

You can check the list of events that occurred on the smart device. You can set the status of an event to Ack or Not Ack.

Call History tab

You can check the call history list for the smart device. You can set the status of an entry of the history to Ack or Not Ack. You can add a phone number in the history to the security policy as an allowed phone number.

Web Browsing History tab

You can check the Web browsing history listing for the smart device. You can set the status of a history entry to Ack or Not Ack. You can add a Web site in the history to the security policy as an allowed or prohibited Web site.

Software tab

You can check the list of software products (applications) distributed or installed on the smart device. You can set the status of a software product in the list to Ack or Not Ack. You can also add a software product in the list to the security policy as an allowed or prohibited application.

Hardware tab

You can check hardware information such as the serial number and internal storage capacity of the smart device.

Running Applications tab

You can check the list of applications running on the smart device.

Running Services tab

You can check the list of services running on the smart device.

System Information tab

You can check system information such as the OS information and phone number of the smart device.

Security tab

You can check information including the security policy and Android policy (or iOS profile) applied to the smart device, GPS power status, and the date and time when the smart device was locked last.

Bluetooth Connection Information tab

You can check the smart device connection history using Bluetooth communications. You can set the status of a history entry to Ack or Not Ack.

Registering smart device information

You can register smart device information including the name, OS type, and security rules. If you create a CSV file containing the smart device information you want to register, you can register the information in a batch by importing that CSV file. You can also export the registered smart device information in a CSV file.

Operations for smart devices

You can perform the following operations for smart devices:

Acquire the latest information (acquire the latest inventory information from the smart device)

Initialize the smart device (reset to the factory default settings)

Lock the smart device

Change the Android device password

Resets the iOS device passcode

Sends messages to an Android device

Set the smart device to Unmanaged

Apply a security policy

Apply an Android policy

Apply an iOS profile

Related Topics

2.5.2 Managing unmanaged smart devices

8. Managing Smart Devices

14.5.1 Managed Smart Device List view

2.5.2 Managing unmanaged smart devices

The Unmanaged Smart Device List view of the Smart Device module displays a list of unmanaged smart devices. In this view, you can apply security rules.

Checking smart device information

When you select a smart device in the list, detailed information is displayed on the tabs in the lower part of the information area. The following describes the information you can check on each tab:

Tab name

Description

Events tab

You can check the list of events that occurred on the smart device. You can set the status of an event to Ack or Not Ack.

System Information tab

You can check system information such as the OS information and phone number of the smart device.

Operations for smart devices

You can perform the following operations on the smart devices:

Apply a security policy

Apply an Android policy

Apply an iOS profile

Related Topics

2.5.1 Managing managed smart devices

8. Managing Smart Devices

14.5.3 Unmanaged Smart Device List view

2.6 Managing applications

You can manage the applications to be distributed to smart devices.

2.6.1 Managing distributed applications

You can check the registered applications in a list, and register or remove applications.

In the Distributed Application List view of the Distribution module, you can check the list of applications registered by the administrator and check a summary of the status of distribution to smart devices. You can also add, edit, and remove applications.

When you select an application in the list, you can enter the description of the application as a note in the lower part of the information area.

Note that you can manage Android applications only.

Related Topics

9. Managing Applications

14.6.1 Distributed Application List view

2.6.2 Managing Android applications

You can check the list of registered Android applications, and register, edit, or remove them. You can also distribute applications and send instructions to install or uninstall the applications.

The Android Application view of the Distribution module shows a list of Android applications and a summary of distribution to Android devices. In this view, you can register Android applications, and edit or delete registered information. You can distribute registered Android applications, remove the distributed applications, and send instructions to install or remove Android applications.

When you select an Android application in the list, a list of smart devices by distribution status is displayed on each tab in the lower part of the information area. The following describes the information you can check on each tab:

Tab name

Description

List of Smart Devices Not Distributed To tab

You can check the list of smart devices to which Android applications have not been distributed. You can distribute Android applications to the displayed smart devices, and instruct those smart devices to install applications.

List of Smart Devices Distributed To tab

You can check the list of smart devices to which Android application have been distributed. You can instruct the displayed smart devices to install Android applications. You can also remove Android applications from those smart devices.

List of Smart Devices Installed To tab

You can check the list of smart devices on which Android applications are installed. You can instruct the displayed smart devices to uninstall Android applications, and then remove the Android applications.

Related Topics

9. Managing Applications

14.6.2 Android Application view

2.7 Displaying events

An event is output when something that requires a quick response occurs during JP1/ITDM2 - SDM operation. The processing results of each function are also output as events. By checking the displayed events, the administrator can understand what occurred during operation.

2.7.1 Events to be output

Events to be output are classified into three severity types. Periodically check the events, and take action if any problems are found.

Events are classified into three severities depending on the details.

(Critical)

Events that require immediate action. Check the details of the event, and take action immediately.

(Warning)

Events that require a response but not immediately. Check the details of the event, and take action as necessary.

(Information)

Events regarding the results of system processing. No actions are required.

Some events require immediate action. Check Critical events first and then Warning events. Determine the cause referring to the error message, and take appropriate actions.

Tip

You can specify settings so that the administrator is notified of events when they occur.

Related Topics

2.7.2 Event types

2.7.3 Event format

11.1 Specifying settings for event notification

11.2 Setting up mail servers

14.7 Events module

2.7.2 Event types

The following are types of events to be output:

Event types

No.

Event type

Description

1

Security

Events regarding security management, such as a change or application of a security policy, and results of security policy judgments

2

Smart Device

Events regarding smart device management, such as addition or deletion of smart device information

3

Distribution

Events regarding distribution, such as distribution of applications to a smart device, and installation of applications

4

Settings

Events regarding settings, such as user account management, and email notification of events

5

Suspicious Operations

Events regarding suspicious operations, such as use of applications prohibited by a security policy, and a call to a destination prohibited by a security policy

6

Error

Events regarding errors that occurred in various functions.

Related Topics

2.7.1 Events to be output

2.7.3 Event format

2.7.3 Event format

The following table describes the format of events to be output.

Event format

No.

Field

Description

1

Status

This field shows whether the event was checked. Clicking the field changes the status.

Not Ack

Ack

2

Severity

This field shows the severity of the event. One of the following is displayed:

Critical

Warning

Information

3

Registered Date/Time

This field shows the date and time the event was registered in the smart device manager.

4

Type

This field shows the event type. One of the following is displayed:

Security

Smart Device

Distribution

Settings

Suspicious Operations

Error

5

Event Number

This field displays the ID of the event message.

6

Source

This field shows information that identifies the target of an event, such as a smart device or security policy. Clicking a link in this field changes the display to the link destination. One of the following is displayed:

Smart Device Name (link destination: Managed Smart Device List view or Unmanaged Smart Device List view)

Security (link destination: Security Policy List view)

Distribution (link destination: Distributed Application List view)

Settings (link destination: Settings module)

7

Description

This field displays detailed information about the event.

Related Topics

2.7.1 Events to be output

2.7.2 Event types

3 System Configuration

This chapter describes how to install JP1/ITDM2 - SDM components, set up certificates for SSL communication, and install JP1/ITDM2 - SDM (Smart Device Agent) on a smart device.

3.1 Flow of building a system

To build a system, you set up JP1/ITDM2 - SDM, and then install JP1/ITDM2 - SDM (Smart Device Agent) on each smart device to be managed.

To use JP1/ITDM2 - SDM, set up the smart device manager, communication server, and messaging server, and then install JP1/ITDM2 - SDM (Smart Device Agent) on the smart devices. The following describes the flow of setting up the smart device manager in an intranet environment (basic configuration) and setting up the communication server and messaging server in a DMZ environment.

Install JP1/ITDM2 - SDM (Smart Device Manager) on a host in the intranet environment.

The host on which JP1/ITDM2 - SDM (Smart Device Manager) installed is the smart device manager.

Install JP1/ITDM2 - SDM (Communication Server).

The host on which JP1/ITDM2 - SDM (Communication Server) is installed is the communication server.

Install JP1/ITDM2 - SDM (Messaging Server).

The host on which JP1/ITDM2 - SDM (Messaging Server) is installed is the messaging server.

Open the ports on the router and setting up a firewall on each server.

Obtain certificates for SSL communication.

Set up certificates for SSL communication on the smart device manager.

Set up certificates for SSL communication on the communication server.

Log in to a program module and then set user account information.

Install JP1/ITDM2 - SDM (Smart Device Agent) on a smart device.

Important note

To manage iOS devices, the condition shown below must be satisfied. For details, see the information provided by Apple.

Obtain a license for the iOS Developer Enterprise Program.

Related Topics

3.5 Procedure for installing JP1/ITDM2 - SDM (Smart Device Manager)

3.6 Procedure for installing JP1/ITDM2 - SDM (Communication Server)

3.7 Procedure for installing JP1/ITDM2 - SDM (Messaging Server)

3.8 Opening ports on the router and setting up a firewall on each server

3.11 Obtaining certificates for SSL communication

3.12 Setting up certificates for SSL communication on the smart device manager

3.13 Setting up certificates for SSL communication on the communication server

3.14 Flow of installing JP1/ITDM2 - SDM (Smart Device Agent) on a smart device

5.1 Logging in

5.2 Setting user account information

3.2 Prerequisite OSs

The following lists the prerequisite OSs for JP1/ITDM2 - SDM:

Target

Prerequisite OS

Smart device manager (host on which JP1/ITDM2 - SDM (Smart Device Manager) is installed)

64-bit version of Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

Communication server (host on which JP1/ITDM2 - SDM (Communication Server) is installed)

64-bit version of Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

Messaging server (host on which JP1/ITDM2 - SDM (Messaging Server) is installed)

64-bit version of Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

Smart device on which JP1/ITDM2 - SDM (Smart Device Agent) is installed

Android 4.1

Android 4.3

iOS 7.1

iOS 8.1

3.3 Prerequisite programs

The prerequisite programs for JP1/ITDM2 - SDM are as follows:

Internet Explorer 8 or later

Firefox 24 or later

3.4 Components of JP1/ITDM2 - SDM

JP1/ITDM2 - SDM consists of the following components:

JP1/ITDM2 - SDM (Smart Device Manager)

Installed on a host in the intranet. The host on which JP1/ITDM2 - SDM (Smart Device Manager) is installed is referred to as the smart device manager.

JP1/ITDM2 - SDM (Communication Server)

Installed on a host having a global IP address in DMZ. The host on which JP1/ITDM2 - SDM (Communication Server) is installed is referred to as the communication server.

JP1/ITDM2 - SDM (Messaging Server)

Installed on a host having a global IP address in DMZ. This component can be installed on the same host as the communication server. The host on which JP1/ITDM2 - SDM (Messaging Server) is installed is referred to as the messaging server.

JP1/ITDM2 - SDM (Smart Device Android Agent)

A program installed on an Android device to provide the agent functionality

JP1/ITDM2 - SDM (Smart Device iOS Agent)

A program installed on an iOS device to provide the agent functionality

Related Topics

3.5 Procedure for installing JP1/ITDM2 - SDM (Smart Device Manager)

3.6 Procedure for installing JP1/ITDM2 - SDM (Communication Server)

3.7 Procedure for installing JP1/ITDM2 - SDM (Messaging Server)

3.14 Flow of installing JP1/ITDM2 - SDM (Smart Device Agent) on a smart device

3.5 Procedure for installing JP1/ITDM2 - SDM (Smart Device Manager)

Install JP1/ITDM2 - SDM (Smart Device Manager) on a host in the intranet environment. The host on which JP1/ITDM2 - SDM (Smart Device Manager) is installed is referred to as the smart device manager.

Prerequisites

You must log on to the OS as a user with administrator permissions.

Procedure

Insert the media supplied with the product in the CD/DVD drive.

In the Hitachi Integrated Installer dialog box that opens, select JP1/IT Desktop Management 2 - Smart Device Manager, and then click the Install button.

In the dialog box indicating the start of the installation, click the Next button.

In the Permission Agreement dialog box, check the displayed information, select I accept the terms in license agreement, and then click the Next button.

If you do not want to accept the terms in the license agreement, click Cancel. The dialog box asking whether you want to cancel the installation of JP1/ITDM2 - SDM appears.

Click the Yes button to cancel the installation.

Click the No button to continue the installation.

In the User Registration dialog box, enter the user name and company name, and then click the Next button.

In the Select Server dialog box, select Smart device manager, and then click the Next button.

In the Installation type dialog box, select the installation type, and then click the Next button.

If you choose quick installation, go to step 9.

In the Installation folder dialog box, specify the installation folder, and then click the Next button.

Important note

To specify the installation folder, use a string that begins with the drive letter and contains only the characters shown below. The path name length must be 42 or fewer characters (bytes), including the backslash (\) at the end.

Alphanumeric characters, underscore (_), period (.), space character, left parenthesis ((), right parenthesis ()), and path-delimiter backslash (\)

In the confirmation dialog box for the installation, make sure the information you selected for the installation is correct, and then click the Install button.

Installation starts. If you notice a problem during the installation, click the Back button and make the necessary correction.

When the installation finishes, click the Completed button.

Installation of JP1/ITDM2 - SDM (Smart Device Manager) is complete. When a message that prompts you to log off appears, log off from JP1/ITDM2 - SDM.

Specify the environment setting file for the smart device manager.

Restart the JP1/ITDM2 - Smart Device Manager Server Service on the smart device manager.

Related Topics

3.1 Flow of building a system

16.2 Smart device manager environment setting file (manager.properties)

3.6 Procedure for installing JP1/ITDM2 - SDM (Communication Server)

Install JP1/ITDM2 - SDM (Communication Server). The host on which JP1/ITDM2 - SDM (Communication Server) is installed is referred to as the communication server.

Prerequisites

The target host must have a global IP address and must be in DMZ.

You must log on to the OS as a user with administrator permissions.

Procedure

Insert the media supplied with the product in the CD/DVD drive.

In the Hitachi Integrated Installer dialog box that opens, select JP1/IT Desktop Management 2 - Smart Device Manager, and then click the Install button.

In the dialog box indicating the start of the installation, click the Next button.

In the Permission Agreement dialog box, check the displayed information, select I accept the terms in license agreement, and then click the Next button.

If you do not want to accept the terms in the license agreement, click Cancel. The dialog box asking whether you want to cancel the installation of JP1/ITDM2 - SDM appears.

Click the Yes button to cancel the installation.

Click the No button to continue the installation.

In the User Registration dialog box, enter the user name and company name, and then click the Next button.

In the Select Server dialog box, select Communication server, and then click the Next button.

In the Database connects to dialog box, specify the IP address or domain name, and then click the Next button.

Tip

You can use the sdmnetchange command to change the connection destination address for the database.

In the Installation type dialog box, select the installation type, and then click the Next button.

If you choose quick installation, go to step 10.

In the Installation folder dialog box, specify the installation folder, and then click the Next button.

Important note

To specify the installation folder, use a string that begins with the drive letter and that contains only the characters shown below. The path name length must be 42 or fewer characters (bytes), including the backslash (\) at the end

Alphanumeric characters, underscore (_), period (.), space character, left parenthesis ((), right parenthesis ()), and path-delimiter backslash (\)

In the confirmation dialog box for the installation, make sure the information you selected for the installation is correct, and then click the Install button.

Installation starts. If you notice a problem during the installation, click the Back button and make the necessary correction.

When the installation finishes, click the Completed button.

Installation of JP1/ITDM2 - SDM (Communication Server) is complete. When a message that prompts you to log off appears, log off from JP1/ITDM2 - SDM.

To change the operating environment for the communication server, change the communication server environment setting file.

If you changed the environment setting file, restart the JP1/ITDM2 - Smart Device Manager (Communication Server Service) on the communication server.

Related Topics

3.1 Flow of building a system

15. sdmnetchange (changing the network configuration for the smart device manager or communication server)

16.6 Communication server environment setting file (CommunicationServerEngine.properties)

3.7 Procedure for installing JP1/ITDM2 - SDM (Messaging Server)

Install JP1/ITDM2 - SDM (Messaging Server). The host on which JP1/ITDM2 - SDM (Messaging Server) is installed is referred to as the messaging server.

Prerequisites

The target host must have a global IP address and must be in DMZ.

You must log on to the OS as a user with administrator permissions.

Procedure

Insert the media supplied with the product in the CD/DVD drive.

In the Hitachi Integrated Installer dialog box that opens, select JP1/IT Desktop Management 2 - Smart Device Manager, and then click the Install button.

In the dialog box indicating the start of the installation, click the Next button.

In the Permission Agreement dialog box, check the displayed information, select I accept the terms in license agreement, and then click the Next button.

If you do not want to accept the terms in the license agreement, click Cancel. The dialog box asking whether you want to cancel the installation of JP1/ITDM2 - SDM appears.

Click the Yes button to cancel the installation.

Click the No button to continue the installation.

In the User Registration dialog box, enter the user name and company name, and then click the Next button.

In the Select Server dialog box, select Messaging server, and then click the Next button.

In the Installation type dialog box, select the installation type, and then click the Next button.

If you choose quick installation, go to step 9.

In the Installation folder dialog box, specify the installation folder, and then click the Next button.

Important note

To specify the installation folder, use a string that begins with the drive letter and that contains only the characters shown below. The path name length must be 42 or fewer characters (bytes), including the backslash (\) at the end.

Alphanumeric characters, underscore (_), period (.), space character, left parenthesis ((), right parenthesis ()), and path-delimiter backslash (\)

In the confirmation dialog box for the installation, make sure the information you selected for the installation is correct, and then click the Install button.

Installation starts. If you notice a problem during the installation, click the Back button and make the necessary correction.

When the installation finishes, click the Completed button.

Installation of JP1/ITDM2 - SDM (Messaging Server) is complete. When a message that prompts you to log off appears, log off from JP1/ITDM2 - SDM.

To change the operating environment for the messaging server, change the messaging server environment setting file.

If you changed the environment setting file, restart JP1/ITDM2 - Smart Device Manager (Messaging Server Service) on the messaging server.

Related Topics

3.1 Flow of building a system

16.7 Messaging server setting file (SdMessagingServer.ini)

3.8 Opening ports on the router and setting up a firewall on each server

You need to open the ports on the router and set up a firewall on each server.

The following shows the port numbers used and the connection direction:

Port number

Connection direction

Internet

->

DMZ

Internet

<-

DMZ

DMZ

->

Intranet

DMZ

<-

Intranet

Intranet

<-

Internet

26080/tcp

--

--

--

--

Y

26055/tcp

Y

--

Y

Y

--

2195/tcp

--

Y

--

--

--

2196/tcp

--

Y

--

--

--

80/tcp

--

Y

--

--

--

26079/tcp

Y

--

--

--

--

26067/tcp

--

--

Y

--

--

26068-26077/tcp

--

--

--

Y

--

Legend:

Y: Applicable connection direction

--: Inapplicable connection direction

The following describes the port numbers:

26080: Port for management modules

26055: HTTPS communication port

2195/2196: Port for communication with the APNs server. This port is required only for managing iOS devices.

80: HTTPS communication port. This port is required only for managing iOS devices.

26079: Port for HTTP communication between an Android device and the messaging server.

26067: Port for communication between the communication server and the database in the smart device manager (database receiving port)

26068-26077: Ports for communication between the communication server and the database in the smart device manager (communication server receiving port)

Related Topics

3.1 Flow of building a system

C. Port number list

3.9 Types of certificates for SSL communication

The following describes the types of certificates required for JP1/ITDM2 - SDM to perform SSL communication.

Certificates for SSL communication required for JP1/ITDM2 - SDM

Certificates for SSL communication for the communication server

Obtain the following certificates from a Certificate Authority:

Root certificate for SSL communication

Server certificate for SSL communication

Certificates for SSL communication for the smart device manager

Obtain the following certificates from a Certificate Authority:

Root certificate for SSL communication

Server certificate for SSL communication

Certificates for SSL communication for the APNs server (when managing iOS devices)

To manage iOS devices, the following certificates are required:

Root certificate for SSL communication

Client certificates for SSL communication (for MDM)

The file name is APNsMDMPushDev.p12 in PKCS#12 format

Important note

This certificate must be updated every year.

Related Topics

3.11 Obtaining certificates for SSL communication

3.12 Setting up certificates for SSL communication on the smart device manager

3.13 Setting up certificates for SSL communication on the communication server

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.10 Deployment of certificates for SSL communication

To perform SSL communication using JP1/ITDM2 - SDM, you need to deploy SSL communication certificates on the specified servers or smart devices.

The following figure shows the locations of the certificates for SSL communication:

3.11 Obtaining certificates for SSL communication

The required certificates for SSL communication are different depending on the OS of the smart device.

The following shows the operations for obtaining certificates for SSL communication and when each operation is required:

No.

Operation

Required?

1

Obtain certificates for SSL communication for the communication server.

Required

2

Obtain certificates for SSL communication for the smart device manager.

Required

3

Obtain a root certificate for SSL communication for the APNs server.

Required only for managing iOS devices

4

Obtain a client certificates for SSL communication for the APNs server (for MDM).

Download the MDM certificate request file.

Required only for managing iOS devices

Create an MDM signed-certificate request file.

Create MDM client certificates.

Related Topics

3.1 Flow of building a system

3.11.1 Flow of obtaining certificates for SSL communication for the communication server

3.11.2 Flow of obtaining certificates for SSL communication for the smart device manager

3.11.3 Procedure for obtaining a root certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.5 Procedure for downloading the MDM certificate request file (when managing iOS devices)

3.11.6 Procedure for creating an MDM signed-certificate request file (when managing iOS devices)

3.11.7 Procedure for creating MDM client certificates (when managing iOS devices)

3.11.1 Flow of obtaining certificates for SSL communication for the communication server

From a Certificate Authority, obtain certificates (root certificate and server certificate) for SSL communication for the communication server.

The flow of obtaining certificates for SSL communication for the communication server is as follows:

Create a private key for the Web server (keygen command).

Specify the file containing the created private key for the Web server in the SSLCertificateKeyFile directive.

Create a Certificate Signing Request (CSR) (certutil reqgen command).

Display the contents of a Certificate Signing Request (CSR) (certutil req command).

If necessary, check the contents of the Certificate Signing Request (CSR).

Send the CSR to the CA.

Acquire a certificate from the CA.

Create a pair of the obtained client certificate and client private key in PKCS#12 format.

The following shows how to create the pair:

openssl pkcs12 -export -inkey httpsdkey.pem -in client-certificate.pem -out user.p12 -certfile root-certificate.pem

Tip

You can use the certutil cert command to check the contents of the certificate you obtained.

Tip

In the certificate you obtained, save the part from -----BEGINCERTIFICATE----- to -----END CERTIFICATE---- in another file (httpsd.pem file defined in httpsd.conf provided as standard). Defining this file for the SSLCertificateFile directive enables use of SSL.

Related Topics

3.12.1 Procedure for setting up the root certificate for SSL communication for the communication server on the smart device manager

3.13.2 Procedure for setting up server certificates for SSL communication on the communication server

G.1 Creating a private key for the Web server (keygen command)

G.2 Creating a Certificate Signing Request (CSR) (certutil reqgen command)

G.3 Displaying the contents of a Certificate Signing Request (CSR) (certutil req command)

G.4 Displaying certificate contents (certutil cert command)

G.5 Converting the certificate format (certutil cert command)

3.11.2 Flow of obtaining certificates for SSL communication for the smart device manager

From a Certificate Authority, obtain certificates (root certificate and server certificate) for SSL communication for the smart device manager.

The flow of obtaining certificates for SSL communication for the smart device manager is as follows:

Create a private key for the Web server (keygen command).

Specify the file containing the created private key for the Web server in the SSLCertificateKeyFile directive.

Create a Certificate Signing Request (CSR) (certutil reqgen command).

Display the contents of a Certificate Signing Request (CSR) (certutil req command).

If necessary, check the contents of the Certificate Signing Request (CSR).

Send the CSR to the CA.

Acquire a certificate from the CA.

Tip

You can use the certutil cert command to check the contents of the certificate you obtained.

Tip

In the certificate you obtained, save the part from -----BEGINCERTIFICATE----- to -----END CERTIFICATE---- in another file (httpsd.pem file defined in httpsd.conf provided as standard). Defining this file for the SSLCertificateFile directive enables use of SSL.

Important note

The obtained certificates must also be set up on the JP1/IT Desktop Management 2 management server.

Related Topics

3.12.2 Procedure for setting up server certificates for SSL communication on the smart device manager

G.1 Creating a private key for the Web server (keygen command)

G.2 Creating a Certificate Signing Request (CSR) (certutil reqgen command)

G.3 Displaying the contents of a Certificate Signing Request (CSR) (certutil req command)

G.4 Displaying certificate contents (certutil cert command)

G.5 Converting the certificate format (certutil cert command)

3.11.3 Procedure for obtaining a root certificate for SSL communication for the APNs server (when managing iOS devices)

Because the APNs server uses Entrust server certificates, an Entrust root certificate is required. You need to obtain a root certificate for SSL communication for the APNs server from the Entrust website as described below only when managing iOS devices.

Procedure

Access the Entrust website.

Select Personal Use and Secure Server Installation, and then click the Download Certificates button.

Click Root Certificates to download entrust_2048_ca.cer.

Related Topics

3.13.1 Procedure for setting up the APNs server's root certificate for SSL communication on the communication server (when managing iOS devices)

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

Obtain the MDM client certificate (APNsMDMPushDev.p12 file) from the iOS Dev Center.

The following shows the flow of obtaining the MDM client certificate, which is required only when managing iOS devices.

Download the MDM certificate request file.

Create an MDM signed-certificate request file.

Create the MDM client certificate.

Related Topics

3.11.5 Procedure for downloading the MDM certificate request file (when managing iOS devices)

3.11.6 Procedure for creating an MDM signed-certificate request file (when managing iOS devices)

3.11.7 Procedure for creating MDM client certificates (when managing iOS devices)

3.13.3 Procedure for setting up the APNs server's client certificates for SSL communication on the communication server (when managing iOS devices)

3.13.4 Procedure for creating a configuration profile on the communication server (when managing iOS devices)

3.11.5 Procedure for downloading the MDM certificate request file (when managing iOS devices)

To create an MDM signed-certificate request file, download the MDM certificate request file (mdm.cer). This procedure is required only when managing iOS devices.

Prerequisites

You must purchase a license for the iOS Developer Enterprise Program.

You must perform the procedure on a Mac PC.

Procedure

Log in to the iOS Dev Center. From iOS Developer Program, click Certificates, Identifiers & Profiles.

Click Certificates.

Click the + (Add) button.

From Production, select MDM CSR, and then click the Continue button.

In the window that explains upload of a certificate request, click the Continue button.

Use Keychain Access to create a Certificate Signing Request (CSR).

Specify the following items as certificate information:

User Email Address

Enter the email address that was used to register your iOS development license.

Common Name

Set any name.

Tip

The name set here will be used when you create an MDM signed-certificate request file.

Request is

Select Saved to disk.

Let me specify key pair information

Select this check box.

Upload the created CSR (Certificate Signing Request).

Download the created MDM certificate request file (mdm.cer).

Postrequisites

Create an MDM signed-certificate request file.

Related Topics

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.6 Procedure for creating an MDM signed-certificate request file (when managing iOS devices)

3.11.7 Procedure for creating MDM client certificates (when managing iOS devices)

3.11.6 Procedure for creating an MDM signed-certificate request file (when managing iOS devices)

To create MDM client certificates, you need to change the format of the MDM certificate request file, and then create an MDM signed-certificate request file. You need to perform this procedure only when managing iOS devices.

Prerequisites

You must purchase a license for the iOS Developer Enterprise Program.

You must perform the procedure on a Mac PC.

You must download the MDM certificate request file (mdm.cer) in advance.

Procedure

Double-click the downloaded MDM certificate request file (mdm.cer) to import it to Keychain Access, and then export the file in PKCS#12 format.

Specify vendor.p12 as the export file name.

Tip

Set a password when exporting the file. The password set here will be registered in step 6.

Obtain the following root certificate and intermediate certificate from Apple:

Apple Root CA (AppleIncRootCertificate.cer)

Apple Worldwide Developer Relations CA (AppleWWDRCA.cer)

Execute the following commands from the terminal to convert the cer files to pem format:

openssl x509 -inform der -in mdm.cer -out mdm.pem
openssl x509 -inform der -in AppleWWDRCA.cer -out intermediate.pem
openssl x509 -inform der -in AppleIncRootCertificate.cer -out root.pem

Execute the following commands from the terminal to create a customer certificate request:

Create a private key:

openssl genrsa -des3 -out customerPrivateKey.pem 2048

Create the customer certificate request:

openssl req -new -key customerPrivateKey.pem -out customer.csr

Convert the customer certificate request to der file format:

openssl req -inform pem -outform der -in customer.csr -out customer.der

Copy the following five created files to the communication server:

customer.der

vendor.p12

mdm.pem

intermediate.pem

root.pem

Execute the following command from the command prompt to create an MDM signed-certificate request file:

sdmcreatemdmcertreq -f "folder-storing-files" -o "MDM-signed-certificate-request-file-output-folder" -a common-name-set-when-creating-the-certificate-request-file -p password-set-when-exporting-vendor.p12

Postrequisites

Create MDM client certificates.

Related Topics

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.5 Procedure for downloading the MDM certificate request file (when managing iOS devices)

3.11.7 Procedure for creating MDM client certificates (when managing iOS devices)

15. sdmcreatemdmcertreq (creating an MDM signed-certificate request file)

3.11.7 Procedure for creating MDM client certificates (when managing iOS devices)

Upload the MDM signed-certificate request file to create MDM client certificates. You need to perform this procedure only when managing iOS devices.

Prerequisites

You must purchase a license for the iOS Developer Enterprise Program.

You must perform the procedure on a Mac PC.

You must create the MDM signed-certificate request file in advance.

Procedure

Log in to Apple Push Certificates Portal.

Click the Create a Certificate button.

Select the check box for accepting the terms of the license agreement, and then click the Accept button.

Select the plist_encoded file to be uploaded, and then click the Upload button.

When the file is uploaded successfully, an MDM certificate file is created.

Click the Download button to obtain the certificate file (mdm_vendor.pem).

Click the information icon (Certificate Info), and then confirm the UID of the Subject DN.

Tip

You need the UID when creating a configuration profile communication server in order to distribute client certificates to iOS devices.

Execute the following command to create the APNsMDMPushDev.p12 file from the private key and pem file:

openssl pkcs12 -export -inkey customerPrivateKey.pem -in mdm_vendor.pem -out APNsMDMPushDev.p12

Related Topics

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.5 Procedure for downloading the MDM certificate request file (when managing iOS devices)

3.11.6 Procedure for creating an MDM signed-certificate request file (when managing iOS devices)

3.13.4 Procedure for creating a configuration profile on the communication server (when managing iOS devices)

3.12 Setting up certificates for SSL communication on the smart device manager

This section describes how to set up, on the smart device manager, certificates for SSL communication for the communication server and smart device manager.

3.12.1 Procedure for setting up the root certificate for SSL communication for the communication server on the smart device manager

On the smart device manager, set up the root certificate for SSL communication for the communication server.

Procedure

Execute the following command to install the root certificate:

"JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\bin\keytool.exe" -importcert -alias alias-name# -file certificate-path -keystore "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\jre\lib\security\cacerts" -storepass changeit

To check the installed root certificate, execute the following command:

"JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\bin\keytool.exe" -list -v -storepass changeit -keystore "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\jre\lib\security\cacerts"

To delete the certificate from the keystore, execute the following command:

"JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\bin\keytool.exe" -delete -alias alias-name# -keystore "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\jre\lib\security\cacerts" -storepass changeit

#: You can specify any alias name.

Important note

If the keytool.exe command ends abnormally, the keystore file might be set to read-only. In this case, cancel the read-only attribute of the keystore file, and then re-execute the command.

The following shows the path to the keystore file and how to cancel the read-only attribute.

Keystore file path: "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\jdk\jre\lib\security\cacerts"

Right-click the keystore file, and then select Properties.

On the General tab, clear the Attributes check box for Read-only.

Click OK.

Related Topics

3.1 Flow of building a system

3.11.1 Flow of obtaining certificates for SSL communication for the communication server

3.12.2 Procedure for setting up server certificates for SSL communication on the smart device manager

Set up the server certificate for SSL communication and private key on the smart device manager.

Procedure

Store the server certificate for SSL communication and private key in the following folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\httpsd\conf\ssl\server

Add the definitions to the httpsd.conf file.

The httpsd.conf file is stored in the following location:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\httpsd\conf

Add the following lines and comment out the lines described below.

ServerName localhost or host-name

#--Omitted--
Listen 26080
<VirtualHost localhost or host-name:26080>
<Location /jp1itdm2sdm>
     Allow from all
</Location>
</VirtualHost>

Listen 26056
<VirtualHost localhost:26056>
<Location /rest>
     Allow from command
</Location>
</VirtualHost>

#--Uncomment out the following lines--
Listen 26055
<VirtualHost host-name:26055>
    SSLEnable
    SSLProtocol TLSv1 TLSv11 TLSv12
    SSLCertificateFile "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder/mgr/uC/httpsd/conf/ssl/server/newcert.pem"
    SSLCertificateKeyFile "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder/mgr/uC/httpsd/conf/ssl/server/newkeyRSA.pem"
    #SSLCertificateKeyPassword "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder/mgr/uC/httpsd/conf/ssl/server/.keypasswd"
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    <Location /server01/api/v1.0>
        ProxyPass http://localhost:26057/rest/itdmsdapi
        Allow from all
    </Location>
    <Location /server01/api/version>
        ProxyPass http://localhost:26057/rest/itdmsdapi/version
        Allow from all
    </Location>
</VirtualHost>

Listen 26057
<VirtualHost localhost:26057>
<Location /rest>
     Allow from all
</Location>
</VirtualHost>
#--End of the change--

Include "JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder/mgr/uC/CC/web/redirector/mod_jk.conf"

Legend:

httpsd.pem: Server certificate file name (PEM format)

httpsdkey.pem: Private key file name (PEM format)

.keypasswd: Password file name

Important note

If you set a password when creating the private key for the Web server, you need to create a password file by using the sslpasswd command, and then set the SSLCertificateKeyPassword directive.

Related Topics

3.1 Flow of building a system

3.11.2 Flow of obtaining certificates for SSL communication for the smart device manager

G.6 Create a password file (sslpasswd command)

3.13 Setting up certificates for SSL communication on the communication server

This section describes how to set up, on the communication server, certificates for SSL communication for the communication server and APNs server. This section also describes how to create a configuration profile for distributing client certificates to iOS devices.

3.13.1 Procedure for setting up the APNs server's root certificate for SSL communication on the communication server (when managing iOS devices)

On the communication server, set up the root certificate for SSL communication for the APNs server. You need to perform this procedure only when managing iOS devices.

Procedure

Execute the following command to install the root certificate:

"JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\bin\keytool.exe" -importcert -alias alias-name# -file certificate-path -keystore "JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\jre\lib\security\cacerts" -storepass changeit

To check the installed root certificate, execute the following command:

"JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\bin\keytool.exe" -list -v -storepass changeit -keystore "JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\jre\lib\security\cacerts"

To delete the certificate from the keystore, execute the following command:

"JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\bin\keytool.exe" -delete -alias alias-name# -keystore "JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\jre\lib\security\cacerts" -storepass changeit

#: You can specify any alias name.

Important note

If the keytool.exe command ends abnormally, the keystore file might be set to read-only. In this case, cancel the read-only attribute of the keystore file, and then re-execute the command.

The following shows the path to the keystore file and how to cancel the read-only attribute.

Keystore file path:"JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\jdk\jre\lib\security\cacerts"

Right-click the keystore file, and then select Properties.

On the On the General tab, clear the Attributes check box for Read-only.

Click OK.

Related Topics

3.1 Flow of building a system

3.11.3 Procedure for obtaining a root certificate for SSL communication for the APNs server (when managing iOS devices)

3.13.2 Procedure for setting up server certificates for SSL communication on the communication server

On the communication server, set up the server certificate for SSL communication and private key for the communication server.

Procedure

Store the server certificate for SSL communication and private key in the following folder:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\httpsd\conf\ssl\server

Add the definitions to the httpsd.conf file.

The httpsd.conf file is stored in the following location:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\httpsd\conf

Add the following lines:

ServerName host-name

#--Omitted--
Listen 26055
<VirtualHost host-name:26055>
    SSLEnable
    SSLProtocol TLSv11 TLSv12
    SSLCertificateFile "JP1/ITDM2 - SDM (Communication Server)-installation-folder/cms/uC/httpsd/conf/ssl/server/newcert.pem"
    SSLCertificateKeyFile "JP1/ITDM2 - SDM (Communication Server)-installation-folder/cms/uC/httpsd/conf/ssl/server/newkeyRSA.pem"
</VirtualHost>
Include "JP1/ITDM2 - SDM (Communication Server)-installation-folder/cms/uC/CC/web/redirector/mod_jk.conf"

Legend:

httpsd.pem: Server certificate file name (PEM format)

httpsdkey.pem: Private key file name (PEM format)

.keypasswd: Password file name

Important note

If you set a password when creating the private key for the Web server, you need to create a password file by using the sslpasswd command, and then set the SSLCertificateKeyPassword directive.

Restart the JP1/ITDM2 - Smart Device Manager Web Server on the communication server.

Related Topics

3.1 Flow of building a system

3.11.1 Flow of obtaining certificates for SSL communication for the communication server

G.6 Create a password file (sslpasswd command)

3.13.3 Procedure for setting up the APNs server's client certificates for SSL communication on the communication server (when managing iOS devices)

On the communication server, store the MDM client certificate and the file containing the password for MDM client certificates. You need to perform this procedure only when managing iOS devices.

Procedure

In the following folder on the communication server, store the MDM client certificate (APNsMDMPushDev.p12 file in PKCS#12 format), and the password file containing the password of the MDM client certificate.

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\conf

Restart the JP1/ITDM2 - Smart Device Manager (Communication Server Service) on the communication server.

Related Topics

3.1 Flow of building a system

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.13.4 Procedure for creating a configuration profile on the communication server (when managing iOS devices)

Create a configuration profile on the communication server in order to distribute client certificates to iOS devices. You need to perform this procedure only when managing iOS devices.

Prerequisites

The following procedure is provided based on the iPhone Configuration Utility version 3.6.

Procedure

Install the Apple iPhone Configuration Utility.

In the left pane of the window, select Library, and then Configuration Profiles. Then, click the New button at the top of the window.

Specify the General settings as follows:

Item

Specifiable value

Name

Any

Identifier

Any

Organization

Any

Description

Any

Consent Message

Any

Security

Select With Authentication.

Automatically Remove Profile

Select Never.

In the Credentials settings, select the root certificate used for connecting iOS devices to the communication server. Then, enter the credential name, and then add the root certificate. (This step is required if the root certificate for the communication server is not installed on an iOS device.)

Tip

You can also set root certificates for individual iOS devices.

In the Credentials settings, select the client certificate used by iOS devices to connect to the communication server. Then, enter the credential name and the password for the certificate, and then add the client certificate.

In the Credentials settings, select the client certificate (APNsMDMPushDev.p12) used by iOS devices to connect to the APNs server. Then, enter the credential name and the password for the certificate, and then add the client certificate.

Specify the Mobile Device Management Settings information as follows:

Item

Specifiable value

Server URL

https://communication-server-host-name:26055/CommunicationServerWeb/ios/server

Check in URL

https://communication-server-host-name:26055/CommunicationServerWeb/ios/checkin

Topic

Set the UID in the Subject DN of the MDM certificate created by using the Apple Push Certificates Portal.

Identity

In the list, select the credential name specified in step 5, which is used for connecting to the communication server.

Sign messages

Select the check box.

Check Out When Removed

Select the check box.

Access Rights

Select all check boxes.

Apple Push Notification Server

Clear the check box.

Click the Export button at the top of the window, select Sign Configuration Profile, and then export the configuration profile.

For the file name, specify mdmprofile.mobileconfig.

Store the configuration profile in the following folder on the communication server:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\conf

Related Topics

3.1 Flow of building a system

3.11.1 Flow of obtaining certificates for SSL communication for the communication server

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.7 Procedure for creating MDM client certificates (when managing iOS devices)

3.14 Flow of installing JP1/ITDM2 - SDM (Smart Device Agent) on a smart device

The following describes the flow of installing JP1/ITDM2 - SDM (Smart Device Agent) on a smart device used in the organization, and starting the smart device management.

Define security principles.

Register security rules.

Understand the smart devices in your organization.

Create a smart device management ledger. Based on the ledger information, determine the smart devices to be managed by JP1/ITDM2 - SDM. In addition, obtain registration information of the smart devices.

Set up a provisioning.

Check the root certificates for SSL communication preinstalled on the smart device.

Set the root certificates for SSL communication on the smart device (only when necessary certificates are not preinstalled).

Register smart device information in JP1/ITDM2 - SDM.

Use JP1/ITDM2 - SDM to set the password for SSL communication with the APNs server.

Plan JP1/ITDM2 - SDM (Smart Device Agent) installation.

Install JP1/ITDM2 - SDM (Smart Device Agent) in either of the following ways:

The administrator installs JP1/ITDM2 - SDM (Smart Device Agent), and then distributes it to the user.

After distributing the smart device to the user, ask the user to install JP1/ITDM2 - SDM (Smart Device Agent).

Install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

The administrator or user installs JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

Confirm that JP1/ITDM2 - SDM (Smart Device Agent) is installed.

If JP1/ITDM2 - SDM (Smart Device Agent) is installed on the smart device, inventory information is periodically reported to JP1/ITDM2 - SDM. If inventory information has not been sent from the managed smart device for a specified period of time, an event is issued. Therefore, by checking whether an event was issued, you can understand whether JP1/ITDM2 - SDM (Smart Device Agent) is installed on smart device.

Send a notification email indicating that JP1/ITDM2 - SDM (Smart Device Agent) must be installed (only for users who have not installed JP1/ITDM2 - SDM (Smart Device Agent).

Related Topics

2.4.1 Types of security rules

3.14.1 Defining the organization's security principles

3.14.2 Provisioning settings

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.14.6 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (using the Android device only)

3.14.7 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (for a PC)

3.14.8 Procedure for installing JP1/ITDM2 - SDM (Smart Device iOS Agent) on an iOS device

7.1 Using security policies

7.2 Using Android policies

7.3 Using iOS profiles

8.1 Registering smart devices in JP1/ITDM2 - SDM

3.14.1 Defining the organization's security principles

Define the organization's security principles to manage smart device security.

The following are essential points of security principles to be defined:

To ensure that hard-to-guess unlock passwords are set for smart devices, create a password policy.

To restrict users to access phone numbers that are required for jobs, create a list of allowed phone numbers.

If some applications must be installed or if you want to prohibit use of applications, create a list of required or prohibited applications.

To permit or prohibit web browsing of some sites, create a list of allowed or prohibited sites.

To prohibit some smart device functions (such as cameras), create a list of prohibited functions.

These points will differ depending on the group in the organization and contents of work. Cooperate with the security administrators of each department to define security principles applicable to the contents of each job.

We recommend that you understand security trends, and periodically review security principles in order to maintain robust security management.

Related Topics

2.4 Managing security

3.14.2 Provisioning settings

Provisioning information means the configuration information for JP1/ITDM2 - SDM (Smart Device Agent) that runs on the smart device.

The configuration information includes the following:

URL of the connected communication server

URL of the connected messaging server

Inventory data collection interval

GPS information collection interval

Battery capacity for sending inventory data in the event of low voltage

The provisioning settings take effect by updating the provisioning information setting file (provisioning.properties), and then restarting the service.

Related Topics

16.3 Provisioning information setting file (provisioning.properties)

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

Confirm that the necessary root certificates for SSL communication are preinstalled on the smart device.

Procedure

On the smart device, do the following:

For an iOS device:

Tap Settings, General, About, and then Trust Store to access the Apple's website. In the Apple's website, check the list of root certificates preinstalled on the iOS device.

For an Android device:

Tap Settings, Personal, Security, Credential storage, and then Trusted credentials. Then, check the list of root certificates.

Postrequisites

If the necessary root certificate for SSL communication is preinstalled, you do not have to set up a root certificate on the smart device.

If the necessary root certificate for SSL communication is not preinstalled, obtain the certificate, and then set it up on the smart device.

Related Topics

3.11.1 Flow of obtaining certificates for SSL communication for the communication server

3.11.3 Procedure for obtaining a root certificate for SSL communication for the APNs server (when managing iOS devices)

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

On the Android device, install the root certificate for SSL communication for the communication server. You need to perform this procedure only when the root certificate for SSL communication is not installed.

Procedure

Save the root certificate file in the internal storage of the device or the root directory of an SD card.

The extension of the root certificate file is .cer or .crt.

Select whether to install the root certificate from the storage or SD card.

To install the root certificate from storage:

Select Settings, Personal, Security, Credential storage, and then Install from device memory.

To install the root certificate from an SD card:

Select Settings, Personal, Security, Credential storage, and then Install from SD card.

Select the root certificate to be installed.

Enter the certificate name, and then tap OK.

Installation is complete.

Confirm that the certificate has been installed.

Select Settings, Personal, Security, Credential storage, and then Trusted credentials. On the User tab, confirm that the certificate has been installed.

Related Topics

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

On the iOS device, install the communication server's root certificate for SSL communication and the Root certificate for SSL communication for the APNs server. You need to perform this procedure only when the necessary root certificates for SSL communication are not installed.

Procedure

Launch the iPhone Configuration Utility.

Tap Library, Configuration Profiles, and then tap New.

Tap Credentials, and then tap the Configuration button in the right pane.

Select the root certificate you obtained.

Tap General, and then enter any values in the Name and Identifier fields.

Under Devices, select the device name. Then, tap the Configuration Profiles tab, and then tap the Install button.

In the profile installation window that appears, tap the Install button.

In the confirmation message dialog box for the installation, tap the Install button.

In the installation completion window, tap the Completed button.

Related Topics

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.6 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (using the Android device only)

Install JP1/ITDM2 - SDM (Smart Device Android Agent) (application name: JP1ITDM2SDM) on the Android device, and then set up JP1/ITDM2 - SDM (Smart Device Android Agent). This procedure uses the Android device only.

Procedure

Launch the Google Play Store application.

Tap the Play Store icon, and then select My apps.

Select ALL as the category.

Select JP1/ITDM2 - SDM (Smart Device Android Agent) (application name: JP1ITDM2SDM), and then tap the Install button on the application detail page.

JP1/ITDM2 - SDM (Smart Device Android Agent) is installed.

On the Android device, start JP1/ITDM2 - SDM (Smart Device Android Agent).

In the Settings window, enter the host name of the connection destination communication server and smart device name, and then tap OK.

For the communication server, enter the host name in host-name:26055 format.

When the server is connected successfully, a dialog box indicating so appears.

Tap OK in the dialog box.

3.14.7 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (for a PC)

The following describes how to use a PC to install JP1/ITDM2 - SDM (Smart Device Android Agent) (application name: JP1ITDM2SDM) on the Android device, and then set up JP1/ITDM2 - SDM (Smart Device Android Agent).

Procedure

On the PC, access the My apps page of Google Play.

Select the application, and then display its detail page.

Click the Install or Installed button, and then select the device on which you want to install the application.

Click Install.

JP1/ITDM2 - SDM (Smart Device Android Agent) is installed.

On the Android device, start JP1/ITDM2 - SDM (Smart Device Android Agent).

In the Settings window, enter the host name of the connection destination communication server and smart device name, and then tap OK.

For the communication server, enter the host name in host-name:26055 format.

When the server is connected successfully, a dialog box indicating this fact appears.

Tap OK in the dialog box.

3.14.8 Procedure for installing JP1/ITDM2 - SDM (Smart Device iOS Agent) on an iOS device

Install JP1/ITDM2 - SDM (Smart Device iOS Agent) (application name: JP1ITDM2SDM) on the iOS device, and then set up JP1/ITDM2 - SDM (Smart Device iOS Agent).

Procedure

From the App Store, download and install JP1/ITDM2 - SDM (Smart Device iOS Agent) (application name: JP1ITDM2SDM).

On the iOS device, start JP1/ITDM2 - SDM (Smart Device iOS Agent).

In the Communication Server Settings window, enter the host name of the connection destination communication server and smart device name, and then tap OK.

For the communication server, enter the host name in host-name:26055 format.

When the server is connected successfully, a dialog box indicating so appears.

Tap OK in the dialog box.

3.15 Procedure for uninstalling JP1/ITDM2 - SDM from the server

If you want to re-install JP1/ITDM2 - SDM, you must first uninstall JP1/ITDM2 - SDM (Smart Device Manager), and JP1/ITDM2 - SDM (Communication Server) or JP1/ITDM2 - SDM (Messaging Server) from the server.

Prerequisites

You must log on to the server by using a user account with administrator permissions.

We recommend that you stop any running JP1/ITDM2 - SDM programs.

Procedure

In the Windows Control panel, select Programs and Features.

A dialog box listing programs that can be uninstalled appears.

Select the JP/ITDM2 - SDM programs to be uninstalled, and then click the Uninstall button.

In the dialog box indicating the start of the uninstallation, click the Next button.

In the Select Server dialog box, select the server components to be uninstalled, and then click the Next button.

In the Remove the Program dialog box, click the Remove button.

The selected programs are uninstalled.

Remove any files or folders that still exist in the installation folder.

Important note

Files and folders that were open during uninstallation are not removed. We recommend that you close the files and folders before starting uninstallation.

Related Topics

A. List of folders

3.16 Procedure for uninstalling JP1/ITDM2 - SDM (Smart Device Android Agent) from the Android device (using the Android device settings menu)

Use the Android device Settings menu to uninstall JP1/ITDM2 - SDM (Smart Device Android Agent) from the Android device.

Procedure

In the Settings menu, tap Apps or Application manager.

Tap the icon of the JP1/ITDM2 - SDM (Smart Device Android Agent) application (application name: JP1ITDM2SDM).

Tap Uninstall.

JP1/ITDM2 - SDM (Smart Device Android Agent) is uninstalled.

3.17 Procedure for uninstalling JP1/ITDM2 - SDM (Smart Device Android Agent) from the Android device (using the Google Play Store application)

Use the Google Play Store application to uninstall JP1/ITDM2 - SDM (Smart Device Android Agent) from the Android device.

Procedure

Launch the Google Play Store application.

In the Play Store menu, tap My apps.

Tap the JP1/ITDM2 - SDM (Smart Device Android Agent) application (application name: JP1ITDM2SDM) marked Installed, and then tap Uninstall on the application detail page.

JP1/ITDM2 - SDM (Smart Device Android Agent) is uninstalled.

3.18 Procedure for uninstalling JP1/ITDM2 - SDM (Smart Device iOS Agent) from the iOS device

Uninstall JP1/ITDM2 - SDM (Smart Device iOS Agent) from the iOS device.

Procedure

Long-press the icon of the JP1/ITDM2 - SDM (Smart Device iOS Agent) application (application name: JP1ITDM2SDM).

Tap the mark that appears at the upper left of the icon.

Tap Remove to remove the application.

JP1/ITDM2 - SDM (Smart Device iOS Agent) is uninstalled.

4 Managing Smart Devices by Using JP1/ITDM2 - SDM

This chapter describes how to use JP1/ITDM2 - SDM: for example, to manage smart devices and to take action if a smart device is lost.

4.1 What you can do while JP1/ITDM2 - SDM is running

The following describes what you can do while JP1/ITDM2 - SDM is running:

You can:

Overview

Prepare smart devices

Prepare smart devices to be managed by JP1/ITDM2 - SDM. The preparation procedure differs depending on whether the device is a newly purchased smart device or stored smart devices.

Distribute new smart devices

If you receive a new application to use a smart device, you can distribute the smart device to the user.

Replace smart devices

Replace smart devices in the organization.

Change smart device users

If a user is transferred, another user can inherit the smart device.

Store smart devices

Store a smart device that is not being used because the user was transferred, or smart devices were replaced.

Dispose of smart devices

Dispose of smart devices that are no longer used because of a hardware problem or some other reason.

Distribute applications to Android devices and give instructions on installation

Distribute applications to multiple Android devices at the same time.

Remove applications that are no longer needed

Uninstall and remove an application from an Android device when the application is no longer needed.

Manage security rules

Create security rules based on the organization's security principles to manage smart devices. If a user violates security rules, an event is issued so that the administrator can detect the unauthorized use of the smart device.

Take action if a smart device is lost

If a user loses a smart device, lock or initialize that smart device to prevent unauthorized use.

Take action if a user forgets the Android device password or iOS device passcode

If a user forgets an Android device password or iOS device passcode, change the Android device password or reset the iOS device passcode.

Send notifications of events by email

Use email to notify the administrator of events that occur in JP1/ITDM2 - SDM or smart device. The administrator can check JP1/ITDM2 - SDM errors and unauthorized use of the smart device without logging in to the JP1/ITDM2 - SDM program module.

Send messages to Android devices

If there is information that must be reported to Android device users, messages can be sent from JP1/ITDM2 - SDM to Android devices.

Related Topics

4.2 Preparing smart devices

4.3 Flow of distributing new smart devices

4.4 Flow of replacing a smart device

4.5 Flow of changing a smart device user

4.6 Flow of storing a smart device

4.7 Flow of disposing of smart devices

4.8 Flow of distributing applications to Android devices and instructing installation

4.9 Flow of removing an application that is no longer needed

4.10 Managing security rules

4.11 Taking action if a smart device is lost

4.12 Taking action if a user forgets the Android device password or iOS device passcode

4.13 Flow of notifying events by email

8.11 Sending messages to Android devices

4.2 Preparing smart devices

You need to prepare smart devices to be managed and used by JP1/ITDM2 - SDM.

The preparation procedure differs depending on whether you are going to distribute a newly purchased smart device or a smart device already registered in JP1/ITDM2 - SDM.

Related Topics

4.2.1 Flow of preparing a newly purchased smart device

4.2.2 Flow of preparing a smart device registered in JP1/ITDM2 - SDM

4.2.1 Flow of preparing a newly purchased smart device

To use a newly purchased smart device, register it in JP1/ITDM2 - SDM, and then install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

The following describes the flow of preparing a new smart device.

Check the root certificates for SSL communication preinstalled on the smart device.

Set the root certificates for SSL communication on the smart device (only when necessary certificates are not preinstalled).

Register the smart device in JP1/ITDM2 - SDM.

Set the security policy and Android policy (or the security policy and iOS profile) appropriate for the user, and then register the smart device as Managed.

Install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

Related Topics

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.14.6 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (using the Android device only)

3.14.7 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (for a PC)

3.14.8 Procedure for installing JP1/ITDM2 - SDM (Smart Device iOS Agent) on an iOS device

8.1 Registering smart devices in JP1/ITDM2 - SDM

4.2.2 Flow of preparing a smart device registered in JP1/ITDM2 - SDM

To use a stored smart device, check the smart device information such as specifications. If the smart device can be used without problems, change the setting from Unmanaged to Managed, and then install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

The following describes the flow of preparing an existing smart device.

Check the smart device.

Check the information such as specifications to make sure that the smart device can be used without problems. To view the information to be checked, in the Smart Device module, select Smart Device, and then Unmanaged Smart Device List.

Check the root certificates for SSL communication preinstalled on the smart device.

Set the root certificates for SSL communication on the smart device (only when necessary certificates are not preinstalled).

Set the smart device to Managed.

Install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

Related Topics

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.14.6 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (using the Android device only)

3.14.7 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (for a PC)

3.14.8 Procedure for installing JP1/ITDM2 - SDM (Smart Device iOS Agent) on an iOS device

8.3 Setting unmanaged smart devices to Managed

14.5.3 Unmanaged Smart Device List view

4.3 Flow of distributing new smart devices

If a user submits a new application to use a smart device after the operation, prepare the smart device, and then distribute it to the user.

The following describes the flow of distributing a new smart device.

Prepare the smart device.

Tip

You can create a list of smart devices to be distributed, and use it as a check list when distributing smart devices. Create the smart device list by exporting the smart device information to a CSV file.

Distribute the smart device to the user.

Confirm that the latest inventory information can be collected.

After distributing the smart device, confirm that the smart device inventory information can be collected to JP1/ITDM2 - SDM. If it cannot be collected, make sure that JP1/ITDM2 - SDM (Smart Device Agent) is installed correctly.

Related Topics

4.2 Preparing smart devices

8.2 Exporting a list of smart devices

8.6 Obtaining the latest inventory information from a smart device

4.4 Flow of replacing a smart device

To replace smart devices in your organization, use JP1/ITDM2 - SDM to find the smart devices to be replaced. Then, collect the smart devices and distribute new ones.

The following describes the flow of replacing smart devices.

Identify the smart devices to be replaced.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, check the smart devices that must be replaced. At this time, you can use a filter to narrow down the displayed information.

Prepare the smart devices.

Tip

You can create a list of smart devices to be replaced, and use it as a check list when replacing the devices. Create the list by exporting the smart device information to a CSV file.

Collect the smart devices.

Tip

Store the collected smart devices if they are to be reused later. Dispose of any that are not to be used.

Move the SIM cards of the collected smart devices to the new smart devices to be distributed.

This step is unnecessary if you replace smart devices including their SIM cards.

Distribute the smart devices to users.

Confirm that inventory information can be collected.

After distributing the smart devices, confirm that the smart device inventory information can be collected to JP1/ITDM2 - SDM. If it cannot be collected, make sure that JP1/ITDM2 - SDM (Smart Device Agent) is installed correctly.

Related Topics

4.2 Preparing smart devices

4.6 Flow of storing a smart device

4.7 Flow of disposing of smart devices

8.2 Exporting a list of smart devices

8.6 Obtaining the latest inventory information from a smart device

14.5.1 Managed Smart Device List view

4.5 Flow of changing a smart device user

For a smart device to be inherited by another user (for example, when the current user is transferred), initialize the smart device, and then re-register it in JP1/ITDM2 - SDM.

The following describes the flow of changing the smart device user.

Obtain the required information.

Obtain the following information required for changing the user:

Name

User name and department or group before the change

User name and department or group after the change

Identify the smart device whose user has changed.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, identify the smart device based on the information you obtained. At this time, you can use a filter to narrow down the displayed information.

Collect the smart device from the current user.

Initialize the collected smart device.

Change the smart device to Unmanaged.

Remove the smart device from JP1/ITDM2 - SDM.

Check the root certificates for SSL communication preinstalled on the smart device.

Set the root certificates for SSL communication on the smart device (only when necessary certificates are not preinstalled).

Register the smart device in JP1/ITDM2 - SDM.

Set the security policy and Android policy (or the security policy and iOS profile) appropriate for the user, and then register the smart device as Managed.

Install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

Distribute the smart device to a new user.

Confirm that inventory information can be collected.

After distributing the smart device, confirm that the smart device inventory information can be collected to JP1/ITDM2 - SDM. If the information cannot be collected, make sure that JP1/ITDM2 - SDM (Smart Device Agent) is installed correctly.

Related Topics

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.14.6 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (using the Android device only)

3.14.7 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (for a PC)

3.14.8 Procedure for installing JP1/ITDM2 - SDM (Smart Device iOS Agent) on an iOS device

8.1 Registering smart devices in JP1/ITDM2 - SDM

8.3 Setting unmanaged smart devices to Managed

8.4 Setting managed smart devices to Unmanaged

8.5 Removing smart devices from JP1/ITDM2 - SDM

8.7 Resetting a smart device

14.5.1 Managed Smart Device List view

4.6 Flow of storing a smart device

Initialize and store a smart device that is not being used (when, for example, the current user is transferred, or the smart device is replaced).

The following describes the flow of storing a smart device.

Collect the smart device that is not being used.

Initialize the collected smart device.

Important note

When the smart device is initialized, JP1/ITDM2 - SDM (Smart Device Agent) is removed and the security policy and Android policy (or security policy and iOS profile) settings are discarded.

Related Topics

8.7 Resetting a smart device

4.7 Flow of disposing of smart devices

Dispose of smart devices that are no longer used because of a hardware failure or other reason.

The following describes the flow of disposing of smart devices.

Determine the smart devices to be disposed of.

Tip

You can create a list of smart devices to be disposed of and use it as a check list when disposing of smart devices. Create the list by exporting the smart device information to a CSV file.

Initialize the smart devices to be disposed of.

This step is unnecessary if the smart devices have already been initialized.

Set the smart devices to Unmanaged.

Dispose of the smart devices.

Remove the smart devices from JP1/ITDM2 - SDM.

Related Topics

8.2 Exporting a list of smart devices

8.4 Setting managed smart devices to Unmanaged

8.5 Removing smart devices from JP1/ITDM2 - SDM

8.7 Resetting a smart device

4.8 Flow of distributing applications to Android devices and instructing installation

Register applications you want to distribute in JP1/ITDM2 - SDM, and then simultaneously distribute them to multiple Android devices. Users can install the distributed applications as required, and you can send instructions from JP1/ITDM2 - SDM to the users to install the applications.

The following describes the flow of distributing and installing applications.

Select applications in accordance with the organization's security principles.

Register the applications to be distributed in JP1/ITDM2 - SDM.

Distribute the applications to Android devices, or instruct users to install the applications.

Tip

Use the Android Application view to check the applications that have been distributed and those that are installed.

Related Topics

9.1 Registering applications to be distributed in JP1/ITDM2 - SDM

9.4 Distributing applications to Android devices

9.5 Instructing users to install applications

14.6.2 Android Application view

4.9 Flow of removing an application that is no longer needed

If a specific application is no longer needed, uninstall and remove it from the Android device, and then remove it from JP1/ITDM2 - SDM.

The following describes the flow of removing an unneeded application from JP1/ITDM2 - SDM.

Instruct the Android device to uninstall and remove the application.

Remove the distributed application from JP1/ITDM2 - SDM.

Related Topics

9.3 Removing applications from JP1/ITDM2 - SDM

9.6 Uninstalling distributed applications

4.10 Managing security rules

Create a security rule based on the organization's security principles and manage smart devices. If a user violates the security rule, a JP1/ITDM2 - SDM event is issued. The administrator can detect unauthorized use of smart devices by checking issued events.

The following describes how to manage security rules.

Register security rules.

Register a security rule based on the organization's security principles. You can register multiple security rules. You can register different security rules for each department or group and for smart devices that require special management.

Apply security rules to smart devices.

Security rules allow the administrator to understand the security status of smart devices, and to restrict the use of smart devices to functions that are for business purposes only.

Edit security rules.

If the organization's security principles are changed, edit the security rules.

Delete security rules.

Delete security rules that are no longer needed because, for example, the management structure changed or security rules were combined.

Related Topics

2.4 Managing security

7.1 Using security policies

7.2 Using Android policies

7.3 Using iOS profiles

4.11 Taking action if a smart device is lost

You can lock or initialize any lost smart devices. Loss of a smart device used by your organization might result in confidential information on that smart device being leaked. You need to take action if a smart device is lost.

If a smart device is lost, you can do the following:

Lock the lost smart device.

Lock the smart device so that it cannot be used. Apply this method to prevent unauthorized use of the smart device.

Information in the lost smart device is not deleted by simply locking the smart device. It remains possible for a third party to unlock the device and leak information.

Initialize the lost smart device.

Initialize the smart device to the factory default settings. When a smart device is initialized, information in the smart device is also deleted. Apply this method in the following cases:

The smart device has been lost for a certain period of time.

Prevention of information leakage has the highest priority.

Related Topics

4.11.1 Flow of locking a lost smart device

4.11.2 Flow of initializing a lost smart device

4.11.1 Flow of locking a lost smart device

If a smart device is lost, you can lock it so that it cannot be used.

The following describes the flow of locking a smart device.

Receive a report from a user that the smart device was lost.

When receiving the report, obtain information, such as the user's name or subscribed phone number, to identify the smart device.

Identify the lost smart device.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, identify the smart device based on the information you obtained. At this time, you can use a filter to narrow down the displayed information.

Lock the smart device.

Related Topics

8.8 Locking a smart device

14.5.1 Managed Smart Device List view

4.11.2 Flow of initializing a lost smart device

If a smart device is lost, you can initialize it to the factory default settings.

The following describes the flow of initializing a smart device.

Receive a report from the user that the smart device was lost.

When receiving the report, obtain information, such as the user's name or subscribed phone number, to identify the smart device.

Identify the lost smart device.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, identify the smart device based on the information you obtained. At this time, you can use a filter to narrow down the displayed information.

Initialize the smart device.

Related Topics

8.7 Resetting a smart device

14.5.1 Managed Smart Device List view

4.12 Taking action if a user forgets the Android device password or iOS device passcode

If a user forgets an Android device password or iOS device passcode, the action to be taken differs depending on whether the smart device has been initialized by JP1/ITDM2 - SDM (Smart Device Agent).

If the smart device has not been initialized:

If the user forgets an Android device password or iOS device passcode, the administrator changes the Android device password or resets the iOS device passcode. Then, the administrator instructs the user to set a new Android device password or iOS device passcode.

If the smart device has been initialized:

If the user consecutively enters an incorrect passcode to a smart device, JP1/ITDM2 - SDM (Smart Device Agent) might initialize the smart device. To use the initialized smart device, JP1/ITDM2 - SDM (Smart Device Agent) must be installed again.

Related Topics

4.12.1 Flow of changing the Android device password

4.12.2 Flow of resetting the iOS device passcode

4.12.3 Flow of setting the smart device initialized by JP1/ITDM2 - SDM (Smart Device Agent) to Managed

4.12.1 Flow of changing the Android device password

If a user forgets an Android device password, the administrator changes the Android device password, and then instructs the user to set the Android device password again.

The following describes the flow of changing an Android device password.

Receive a report from the user that they forgot the Android device password.

When receiving the report, obtain information, such as the user's name or subscribed phone number, to identify the Android device.

Identify the Android device.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, identify the Android device based on the information you obtained. At this time, you can use a filter to narrow down the displayed information.

Change the Android device password.

Send the new password to the user whose Android device password was changed, and instruct the user to set the password again.

Related Topics

8.9 Changing an Android device password

14.5.1 Managed Smart Device List view

4.12.2 Flow of resetting the iOS device passcode

If a user forgets an iOS device passcode, the administrator resets the iOS device passcode, and then instructs the user to set the iOS device passcode again.

The following describes the flow of resetting an iOS device passcode.

Receive a report from the user that they forgot the iOS device passcode.

When receiving the report, obtain information, such as the user's name or subscribed phone number, to identify the iOS device.

Identify the iOS device.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, identify the iOS device based on the information you obtained. At this time, you can use a filter to narrow down the displayed information.

Reset the iOS device passcode.

Instruct the user (whose iOS device passcode was reset) to set the passcode again.

Related Topics

8.10 Resetting an iOS device passcode

14.5.1 Managed Smart Device List view

4.12.3 Flow of setting the smart device initialized by JP1/ITDM2 - SDM (Smart Device Agent) to Managed

If a user consecutively enters an incorrect passcode to a smart device, JP1/ITDM2 - SDM (Smart Device Agent) might initialize the smart device. To manage the initialized smart device in JP1/ITDM2 - SDM, the smart device must be set to Managed in JP1/ITDM2 - SDM.

The following describes the flow of setting the initialized smart device to Managed.

Receive a report from the user that the smart device was initialized.

When receiving the report, obtain information, such as the user's name or subscribed phone number, to identify the smart device.

Identify the smart device.

In the Smart Device module, select Smart Device, and then Managed Smart Device List. In the list that appears, identify the smart device based on the information you obtained. At this time, you can use a filter to narrow down the displayed information.

Check information for the identified smart device.

Check the user's name and contact address in the smart device information, and then verify the identity of the user.

Collect the smart device from the user.

Check the root certificates for SSL communication preinstalled on the smart device.

Set the root certificates for SSL communication on the smart device (only when necessary certificates are not preinstalled).

Install JP1/ITDM2 - SDM (Smart Device Agent) on the smart device.

Distribute the smart device to the new user.

Confirm that inventory information can be collected.

After distributing the smart device, confirm that the smart device inventory information can be collected to JP1/ITDM2 - SDM. If it cannot be collected, make sure that JP1/ITDM2 - SDM (Smart Device Agent) is installed correctly.

Related Topics

3.14.3 Procedure for checking the root certificates for SSL communication preinstalled on the smart device

3.14.4 Procedure for setting up the root certificate for SSL communication on the Android device

3.14.5 Procedure for setting root certificates for SSL communication on the iOS device

3.14.6 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (using the Android device only)

3.14.7 Procedure for installing JP1/ITDM2 - SDM (Smart Device Android Agent) on an Android device (for a PC)

3.14.8 Procedure for installing JP1/ITDM2 - SDM (Smart Device iOS Agent) on an iOS device

8.6 Obtaining the latest inventory information from a smart device

14.5.1 Managed Smart Device List view

4.13 Flow of notifying events by email

You can use email to notify the administrator of events that occurred in JP1/ITDM2 - SDM or a smart device.

The following describes the flow of sending notification of an event by email.

Specify settings for event notification.

Set up the mail server.

Define the event mail format in the event mail format information file.

Related Topics

11.1 Specifying settings for event notification

11.2 Setting up mail servers

16.4 Event mail format information file (eventmail.properties)

5 Starting and Ending Operations

This chapter explains how to start and end operations in JP1/ITDM2 - SDM.

5.1 Logging in

In the Login module, you can log in to JP1/ITDM2 - SDM when your user account is successfully authenticated.

Procedure

Enter the following URL into the address bar of your Web browser:

http://smart-device-manager-IP-address-or-host-name:port-number-for-connection-from-administrator-computer#/jp1itdm2sdm/

#: The default port number is 26080.

The Login module appears.

Enter the user ID and password.

The default user ID is system. The default password is manager.

Click the Log In button.

If you use the default password of the built-in account to log in, the Change Password dialog box is displayed. Change the password. Note that the Change Password dialog box is also displayed when you use a newly created user account to log in for the first time.

Result

The Home module is displayed if the user account is successfully authenticated.

Tip

A password is valid for 180 days from the setup date. Beginning seven days prior to expiration, when the user logs in, he or she will be prompted to change the password. If you are prompted to do so, change the password. If 180 days have elapsed since the setup date, the Change Password dialog box is displayed when you log in.

Important note

If a user fails to log in to JP1/ITDM2 - SDM three consecutive times, the user account is locked. The user cannot log in with the locked user account until the user account is unlocked.

Related topics

2.3.1 Locking user accounts

5.2 Setting user account information

5.3 Changing the default password

6.7 Unlocking a user account

14.2 Login window

14.2.1 Change Password dialog box

C. Port number list

5.2 Setting user account information

When you use the built-in account or a newly created user account to log in to JP1/ITDM2 - SDM for the first time, you need to set user account information.

Procedure

Click the user ID link on the left of the Log Out button.

In the dialog box that appears, set information about the logged-in user account, and then click OK.

Tip

You can also set user account information by selecting User Management and then Account Management in the Settings module. In the Account Management view, you can also add a new user account.

Tip

After you specify an email address for a user account, notifications of event occurrences can be sent to that email address. We recommend that you specify an email address so that the appropriate person can be made aware of the operating status without having to frequently check the operation window. Note that to receive such notifications, you also need to specify the event notification settings, in addition to the email address.

Related topics

6.1 Adding a user account

11.1 Specifying settings for event notification

14.8.1 Account Management view

14.8.3 Edit User Account dialog box

5.3 Changing the default password

When you use the built-in account or a newly created user account to log in to JP1/ITDM2 - SDM for the first time, you are prompted to change the default password.

Procedure

Log in with the built-in account or a new user account.

In the dialog box that appears, change the password, and then click OK.

Important note

Make sure to change the default password to enhance security. After the password is changed, you must use the new password from the next login.

Tip

The password is valid for 180 days from the setup date. Beginning seven days prior to expiration, you will be prompted to change the password when logging in. If you are prompted to do so, change the password. If 180 days have elapsed since the setup date, the Change Password dialog box is displayed when you log in.

Related topics

5.1 Logging in

14.2.1 Change Password dialog box

5.4 Logging out

After you have finished performing operations in JP1/ITDM2 - SDM, log out from the operation window.

Procedure

Click the Log Out button.

In the displayed dialog box, click OK.

Tip

You can also log out by selecting Log Out from the System menu at the top of the window.

Related topics

5.1 Logging in

6 Managing User Accounts

This chapter describes how to manage user accounts.

6.1 Adding a user account

When multiple persons use JP1/ITDM2 - SDM to manage smart devices, you can add an administrator's user account.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Settings module.

In the menu area, select User Management, and then Account Management.

In the information area, click the Add button.

In the dialog box that appears, enter the user account information, and then click OK.

Tip

The functions a user can use vary depending on his or her permissions, so assign adequate permissions to users.

Result

A user account is added and displayed in the Account Management view.

Related topics

2.3.2 User account permissions

2.3.3 List of operations that cannot be performed with the view permission

14.8.1 Account Management view

14.8.2 Add User Account dialog box

6.2 Editing your own user account

If you want to change the password or permissions of your user account, you can edit the user account information.

Procedure

From the Go menu at the top of the window, select Edit Your Account.

Alternatively, click the user ID link on the left of the Log Out button.

In the dialog box that appears, edit the user account information, and then click OK.

Related topics

2.3.2 User account permissions

2.3.3 List of operations that cannot be performed with the view permission

6.3 Editing another administrator's user account

14.8.3 Edit User Account dialog box

6.3 Editing another administrator's user account

You can edit another administrator's user account information such as the password and permissions.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Settings module.

In the menu area, select User Management, and then Account Management.

In the information area, click the Edit button for the account you want to edit.

In the dialog box that appears, enter the user account information, and then click OK.

Related topics

2.3.2 User account permissions

2.3.3 List of operations that cannot be performed with the view permission

6.2 Editing your own user account

14.8.1 Account Management view

14.8.3 Edit User Account dialog box

6.4 Removing a user account

You can remove a user account that is no longer used. However, you cannot remove the built-in account or the account of a user who is logged in.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Settings module.

In the menu area, select User Management, and then Account Management.

In the information area, select the user account you want to remove, and then click the Remove button.

You can select multiple user accounts.

In the dialog box that appears, click OK.

Related topics

14.8.1 Account Management view

6.5 Changing your own password

In addition to cases when the Change Password dialog box is displayed, you can change the password of your user account if necessary.

Procedure

From the Go menu at the top of the window, select Edit Your Account.

Alternatively, click the user ID link on the left of the Log Out button.

In the dialog box that appears, select the Changes the password check box.

Enter the password in Password and Re-enter Password, and then click OK.

Tip

The password is valid for 180 days from the setup date. Beginning seven days prior to expiration, you will be prompted to change the password when logging in. If you are prompted to do so, change the password. If 180 days have elapsed since the setup date, the Change Password dialog box is displayed when you log in.

Related topics

6.6 Resetting another administrator's password

14.8.1 Account Management view

14.8.3 Edit User Account dialog box

6.6 Resetting another administrator's password

If an administrator forgets his or her password, another administrator can reset the password to the default.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Settings module.

In the menu area, select User Management, and then Account Management.

In the information area, click the Edit button for the user account whose password you want to reset.

In the dialog box that appears, select the Changes the password check box.

Enter the password in Password and Re-enter Password, and then click OK.

The password is set for the selected user account.

Inform the administrator whose password has been reset, of the new password.

Also inform the administrator that the password needs to be changed after the administrator logs in JP1/ITDM2 - SDM using the reset password.

Related topics

6.5 Changing your own password

14.8.1 Account Management view

14.8.3 Edit User Account dialog box

6.7 Unlocking a user account

A user account is locked if the user fails to log in three consecutive times. You must unlock the account before it can be used.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Settings module.

In the menu area, select User Management, and then Account Management.

Click the Edit button of the locked user account.

In the dialog box that appears, select Enabled from Status, and then click OK.

Tip

If no other administrator has the system administrator permission, restart the JP1/ITDM2 - SDM. The user account is unlocked.

Related topics

2.3.1 Locking user accounts

14.8.1 Account Management view

14.8.3 Edit User Account dialog box

7 Managing the Security Status

This chapter explains how to manage the security of the smart devices in your organization and how to understand the security status.

7.1 Using security policies

Security policies are required to manage the security status of smart devices. For a security policy, you can specify settings to monitor usage of the following: phone numbers, Web sites, and applications. This section describes how to use security policies.

7.1.1 Adding security policies

In the Security Policy List view of the Security module, you can add a security policy. By applying the added security policy to smart devices, you can monitor usage of those smart devices.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Security module.

In the menu area, select Security and then Security Policy List.

In the information area, click the Add button.

At the top of the Add Security Policy dialog box, enter data in the Security Policy Name text box.

Under Security Configuration Items on the left pane of the Add Security Policy dialog box, select Phone Number, Web Site, or Application.

Click the Add button.

In the displayed dialog box, configure the rules settings and then click OK.

Tip

You can specify an asterisk (*) for Phone Number and URL. For example, if you enter 1111111* for Phone Number, phone numbers whose first seven digits are 1111111 are monitored. You can also specify an abbreviated dialing number beginning with a sharp sign (#) for Phone Number.

Repeat steps 5 to 7 for each item you want to set.

In the Add Security Policy dialog box, click OK.

Result

The security policy is added and displayed in the Security Policy List view.

Related topics

2.4.3 Items that can be set for a security policy

7.1.2 Editing security policies

7.1.3 Removing security policies

7.1.4 Applying security policies

14.4.1 Security Policy List view

14.4.2 Add Security Policy dialog box

7.1.2 Editing security policies

You can edit security policies if a change occurs with the security policies of your organization or if you want to keep your security policies up to date.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Security module.

In the menu area, select Security and then Security Policy List.

In the information area, click the Edit button for the security policy that you want to edit.

Under Security Configuration Items on the left pane of the Edit Security Policy dialog box, select Phone Number, Web Site, or Application.

In the dialog box that appears, edit the rule.

To add a new rule:

Click the Add button. In the dialog box that appears, add a rule, and then click OK.

To edit an existing rule:

Click the Edit button for the rule you want to edit. In the dialog box that appears, edit the rule, and then click OK.

To remove an existing rule:

Select the rule you want to remove, and then click the Remove button. In the dialog box that appears, click OK. You can select multiple rules.

Tip

You can specify an asterisk (*) for Phone Number and URL. For example, if you enter 1111111* for Phone Number, phone numbers whose first seven digits are 1111111 are monitored. You can also specify an abbreviated dialing number beginning with a sharp sign (#) for Phone Number.

Tip

You can also add a rule to security policies from Action on the Call History, Web Browsing History, or Software tab.

Repeat steps 4 and 5 for each item you want to edit.

In the Edit Security Policy dialog box, click OK.

Related topics

2.4.3 Items that can be set for a security policy

7.1.1 Adding security policies

7.1.3 Removing security policies

7.1.4 Applying security policies

14.4.1 Security Policy List view

14.4.3 Edit Security Policy dialog box

7.1.3 Removing security policies

You can remove unneeded security policies if the security policies of your organization are changed or if the number of managed smart devices is reduced.

Prerequisites

You must log in by using a user account with the system administrator permission.

You must apply another security policy to smart devices before removing a policy already applied to those devices.

Display the Security module.

In the menu area, select Security and then Security Policy List.

In the information area, select the security policy you want to remove, and then click the Remove button.

You can select multiple security policies.

In the displayed dialog box, click OK.

Related topics

7.1.1 Adding security policies

7.1.2 Editing security policies

14.4.1 Security Policy List view

7.1.4 Applying security policies

If you want to monitor usage of smart devices, apply a security policy. The applied policy allows you to understand the status of smart devices, such as unauthorized use.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device.

In the information area, select the smart device to which you want to apply a security policy.

You can select multiple smart devices.

Tip

You can use a filter to narrow down the displayed information.

From Action, select Apply Security Policy.

In the displayed dialog box, select a security policy and then click OK.

Related topics

7.1.1 Adding security policies

7.1.2 Editing security policies

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.9 Apply Security Policy dialog box

7.2 Using Android policies

Android policies are required to manage the security status of Android devices. An Android policy can specify password rules and restrict use of a device's camera function. This section describes how to use Android policies.

7.2.1 Adding Android policies

In the Android Policy List view of the Security module, you can add an Android policy. By applying the added Android policy to Android devices, you can monitor usage of the target Android devices.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Security module.

In the menu area, select Security and then Android Policy List.

In the information area, click the Add button.

In the dialog box that appears, specify the rules, and then click OK.

Result

The Android policy is added and displayed in the Android Policy List view.

Related topics

2.4.5 Items that can be set for an Android policy

7.2.2 Editing Android policies

7.2.3 Removing Android policies

7.2.4 Applying Android policies

14.4.11 Android Policy List view

14.4.12 Add Android Policy dialog box

7.2.2 Editing Android policies

You can edit Android policies if the security policies of your organization are changed or if you want to keep your security policies up to date.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Security module.

In the menu area, select Security and then Android Policy List.

In the information area, click the Edit button for the Android policy that you want to edit.

In the dialog box that appears, edit the rules, and then click OK.

Related topics

2.4.5 Items that can be set for an Android policy

7.2.1 Adding Android policies

7.2.3 Removing Android policies

7.2.4 Applying Android policies

14.4.11 Android Policy List view

14.4.13 Edit Android Policy dialog box

7.2.3 Removing Android policies

You can remove Android policies that are no longer required (for example, if the security policies of your organization are changed or the number of managed Android devices is reduced).

Prerequisites

You must log in by using a user account with the system administrator permission.

You must apply another Android policy beforehand to the Android devices to which the Android policy to be removed is applied.

Procedure

Display the Security module.

In the menu area, select Security and then Android Policy List.

In the information area, select the Android policy you want to remove, and then click the Remove button.

You can select multiple Android policies.

In the displayed dialog box, click OK.

Related topics

7.2.1 Adding Android policies

7.2.2 Editing Android policies

14.4.11 Android Policy List view

7.2.4 Applying Android policies

If you want to monitor usage of Android devices, apply an Android policy. The applied policy allows you to understand the status of Android devices, such as unauthorized use.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device.

In the information area, select the Android device to which you want to apply an Android policy.

You can select multiple Android devices.

Tip

You can use a filter to narrow down the displayed information.

From Action, select Apply Android Policy.

In the displayed dialog box, select an Android policy and then click OK.

Related topics

7.2.1 Adding Android policies

7.2.2 Editing Android policies

14.4.11 Android Policy List view

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.10 Apply Android Policy dialog box

7.3 Using iOS profiles

iOS profiles are required to manage the security status of iOS devices. An iOS policy can specify passcode rules and restrict use of the camera function. This section describes how to use iOS profiles.

7.3.1 Adding iOS profiles

In the iOS Profile List view of the Security module, you can add an iOS profile. By applying the added iOS profile to iOS devices, you can monitor usage of the target iOS devices.

Prerequisites

You must log in by using a user account with the system administrator permission.

You must create a profile by using the iPhone Configuration Utility (provided by Apple) in advance.

Procedure

Display the Security module.

In the menu area, select Security and then iOS Profile List.

In the information area, click the Add button.

In the dialog box that appears, specify the profile name and the path to the import file.

Click OK.

Result

The iOS profile is added and displayed in the iOS Profile List view.

Related topics

2.4.7 Items that can be set in an iOS profile

7.3.2 Exporting iOS profiles

7.3.3 Removing iOS profiles

7.3.4 Applying iOS profiles

14.4.15 iOS Profile List view

14.4.16 Add iOS Profile dialog box

7.3.2 Exporting iOS profiles

You can export an iOS profile in XML format.

Procedure

Display the Security module.

In the menu area, select Security and then iOS Profile List.

In the information area, click the Export button for the iOS profile you want to export.

In the window that appears, specify the file name and the location to save the file, and then click the Save button.

Result

The iOS profile with the specified file name is saved in XML format in the specified location.

Tip

You can import the exported file to the Apple iPhone Configuration Utility by changing the extension to .mobileconfig. If necessary, you can edit the configuration profile, and then register it again as an iOS profile.

Related topics

7.3.1 Adding iOS profiles

7.3.3 Removing iOS profiles

7.3.4 Applying iOS profiles

14.4.15 iOS Profile List view

7.3.3 Removing iOS profiles

You can remove iOS profiles that are no longer required (for example, if the security policies of your organization are changed or if the number of managed iOS devices is reduced).

Prerequisites

You must log in by using a user account with the system administrator permission.

You must apply another security policy to iOS devices before removing a policy already applied to those devices.

Procedure

Display the Security module.

In the menu area, select Security and then iOS Profile List.

In the information area, select the iOS profile you want to remove, and then click the Remove button.

You can select multiple iOS profiles.

In the displayed dialog box, click OK.

Related topics

7.3.1 Adding iOS profiles

7.3.2 Exporting iOS profiles

14.4.15 iOS Profile List view

7.3.4 Applying iOS profiles

If you want to monitor the usage of iOS devices, apply an iOS profile. The applied profile allows you to understand the status of iOS devices, such as unauthorized use.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device.

In the information area, select the iOS device to which you want to apply an iOS profile.

You can select multiple iOS devices.

Tip

You can use a filter to narrow down the displayed information.

From Action, select Apply iOS Profile.

In the dialog box that appears, specify the iOS profile, and then click OK.

Important note

If you apply an iOS profile to an iOS device to which another iOS profile has already been applied, the old iOS profile remains on the iOS device. Therefore, we recommend that you change the contents of the applied iOS profile rather than apply another one.

Related topics

7.3.1 Adding iOS profiles

7.3.2 Exporting iOS profiles

7.3.3 Removing iOS profiles

14.4.15 iOS Profile List view

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.11 Apply iOS Profile dialog box

8 Managing Smart Devices

This chapter describes how to understand the current smart device status by collecting information from internal smart devices.

8.1 Registering smart devices in JP1/ITDM2 - SDM

Register smart devices you want to manage in JP1/ITDM2 - SDM.

You can register smart devices in the following two ways:

Manually register smart devices

Register information about a smart device one by one.

Register smart devices in a CSV file

Import a CSV file containing information about multiple smart devices to register them as a batch.

Related topics

2.5 Managing smart devices

8.1.1 Manually registering smart devices

8.1.2 Registering smart devices in a CSV file

8.1.1 Manually registering smart devices

You can manually register information about smart devices, one by one, in JP1/ITDM2 - SDM.

Prerequisites

You must log in by using a user account with the system administrator permission.

To register a smart device as a managed device, in advance you must create a security policy and Android policy, or a security policy and iOS profile.

You must obtain the following information:

User name

Department to which the user belongs

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

From Action, select Add Smart Device.

In the Add Smart Device dialog box, enter information about the smart device to be registered.

Click the Add button at the top of the dialog box to add a line in which you can enter smart device information. You can register information about multiple smart devices.

Important note

For Name, use the following characters only:

0 to 9 (ASCII code 0x30 to 0x39)

A to Z (ASCII code 0x41 to 0x5a)

a to z (ASCII code 0x61 to 0x7a)

_ (underscore) (ASCII code 0x5f)

- (hyphen) (ASCII code 0x2d)

. (period) (ASCII code 0x2e)

Important note

If a name that is already registered in JP1/ITDM2 - SDM is entered for Name, information about the registered smart device is overwritten.

Tip

In the Add Smart Device dialog box, click the Export button to output the entered information to a CSV file.

Click OK.

Result

The smart device is registered in JP1/ITDM2 - SDM. Note that the management status of the smart device varies depending on whether security rules were applied.

If the smart device is registered with entry of a security policy and Android policy, or with entry of a security policy and iOS profile:

The smart device is managed, and is displayed in the Managed Smart Device List view.

If the smart device is registered without entry of a security policy and Android policy, or without entry of a security policy and iOS profile:

The smart device is unmanaged, and is displayed in the Unmanaged Smart Device List view.

Related topics

8.1.2 Registering smart devices in a CSV file

8.2 Exporting a list of smart devices

8.3 Setting unmanaged smart devices to Managed

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.12 Add Smart Device dialog box

8.1.2 Registering smart devices in a CSV file

You can import a CSV file containing information about multiple smart devices to register them in a batch.

Prerequisites

You must log in by using a user account with the system administrator permission.

You must create a CSV file.

To register a smart device as a managed device, in advance you must create a security policy and Android policy, or a security policy and iOS profile.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

From Action, select Import Smart Device List.

In the dialog box that appears, select the CSV file containing information about the smart devices, and then click OK.

Important note

For Name to be specified for the CSV file, use the following characters only:

0 to 9 (ASCII code 0x30 to 0x39)

A to Z (ASCII code 0x41 to 0x5a)

a to z (ASCII code 0x61 to 0x7a)

_ (underscore) (ASCII code 0x5f)

- (hyphen) (ASCII code 0x2d)

. (period) (ASCII code 0x2e)

Important note

If a name that is already registered in JP1/ITDM2 - SDM is entered for Name to be specified for the CSV file, information about the registered smart device is overwritten.

Result

The smart devices are registered in JP1/ITDM2 - SDM. Note that the management status of the smart devices varies depending on whether security rules were applied.

If the smart devices are registered with an entered security policy and Android policy, or an entered security policy and iOS profile:

The smart devices are managed, and are displayed in the Managed Smart Device List view.

If the smart devices are registered without a security policy and Android policy, or without a security policy and iOS profile:

The smart devices are unmanaged, and are displayed in the Unmanaged Smart Device List view.

Related topics

8.1.1 Manually registering smart devices

8.2 Exporting a list of smart devices

8.3 Setting unmanaged smart devices to Managed

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.12 Add Smart Device dialog box

E. Output Format of Imported and Exported Files

8.2 Exporting a list of smart devices

In the Smart Device module, you can export the list of smart devices displayed in the information area, to a CSV file. You can use the CSV file as a check list when, for example, disposing of smart devices.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

In the information area, display the smart device list to be exported.

Tip

You can use a filter to narrow down the displayed information.

From Action, select Export Smart Device List.

In the window that appears, specify the file name and the location to save the file, and then click the Save button.

Result

The CSV file is saved with the specified file name in the specified location.

Tip

You can edit and import the exported CSV file.

Related topics

8.1.2 Registering smart devices in a CSV file

14.5.1 Managed Smart Device List view

E. Output Format of Imported and Exported Files

8.3 Setting unmanaged smart devices to Managed

Apply security rules to smart devices registered as unmanaged devices to set them to Managed. For the managed smart devices, you can collect device information and check the security status.

Prerequisites

You must log in by using a user account with the system administrator permission.

You must add, in advance, a security policy and Android policy, or a security policy and iOS profile.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Unmanaged Smart Device List.

Select the smart device to be managed.

You can select multiple smart devices.

From Action, select Apply Security Policy.

In the dialog box that appears, select the security policy to be applied, and then click the OK button.

From Action, select Apply Android Policy or Apply iOS Profile.

Depending on the OS type specified when the smart device was registered, you can select Apply Android Policy or Apply iOS Profile.

In the dialog box that appears, select the Android policy or iOS profile to be applied, and then click the OK button.

Result

The selected smart devices are now managed, and are displayed in the Managed Smart Device List view.

Related topics

2.5.1 Managing managed smart devices

8.4 Setting managed smart devices to Unmanaged

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.9 Apply Security Policy dialog box

14.5.10 Apply Android Policy dialog box

14.5.11 Apply iOS Profile dialog box

8.4 Setting managed smart devices to Unmanaged

For smart devices you no longer need to manage, you can cancel security rules and set those smart devices to Unmanaged.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

Select the smart device to be unmanaged.

You can select multiple smart devices.

From Action, select Set to Unmanaged.

In the displayed dialog box, click OK.

Tip

If you select the Forcibly set as unmanaged check box, sets the selected smart device as unmanaged, even if the device cannot be connected with.

Result

The selected smart devices are now unmanaged, and are displayed in the Unmanaged Smart Device List view.

Related topics

2.5.2 Managing unmanaged smart devices

8.3 Setting unmanaged smart devices to Managed

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.8 Set to Unmanaged dialog box

8.5 Removing smart devices from JP1/ITDM2 - SDM

You can remove unmanaged smart devices from JP1/ITDM2 - SDM if they are no longer needed (for example, due to a hardware failure or replacement).

Prerequisites

You must log in by using a user account with the system administrator permission.

The smart device must be set to Unmanaged.

If necessary, the smart device must be initialized before being removed from JP1/ITDM2 - SDM. A smart device is not initialized by simply removing it from JP1/ITDM2 - SDM.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Unmanaged Smart Device List.

Select the smart device to be removed.

You can select multiple smart devices.

Click the Remove button.

In the displayed dialog box, click OK.

Related topics

8.7 Resetting a smart device

14.5.3 Unmanaged Smart Device List view

8.6 Obtaining the latest inventory information from a smart device

You can obtain the latest inventory information from a smart device.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

In the information area, select the smart device from which you want to obtain information.

From Action, select Update Device Details.

In the displayed dialog box, click OK.

Result

In the Managed Smart Device List view, information displayed on the tabs for the selected smart device is updated.

Related topics

2.5.1 Managing managed smart devices

14.5.1 Managed Smart Device List view

14.5.2 Tabs displayed in the Managed Smart Device List view

8.7 Resetting a smart device

When disposing of smart devices, you can initialize them to the factory default settings.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

In the information area, select the smart device to be initialized.

You can select multiple smart devices.

From Action, select Initialize Smart Device.

In the displayed dialog box, click OK.

Important note

When the smart device is initialized, the installed JP1/ITDM2 - SDM (Smart Device Agent) is removed, and the security policy and Android policy settings, or the security policy and iOS profile settings, are discarded.

Related topics

14.5.1 Managed Smart Device List view

14.5.5 Initialize Smart Device dialog box

8.8 Locking a smart device

You can lock a smart device if, for example, it was lost.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, and then Managed Smart Device List.

In the information area, select the smart device to be locked.

You can select multiple smart devices.

From Action, select Lock Smart Device.

In the displayed dialog box, click OK.

Tip

For Android devices, you can use the Lock Smart Device dialog box to lock the device and change the password at the same time.

Related topics

8.9 Changing an Android device password

14.5.1 Managed Smart Device List view

14.5.6 Lock Smart Device dialog box

8.9 Changing an Android device password

If a user forgets an Android device password, you can lock the Android device and change the password.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, Managed Smart Device List, and then Android Smart Device.

In the information area, select the Android device to be locked.

You can select multiple Android devices.

From Action, select Lock Smart Device.

In the Lock Smart Device dialog box, select the check box Change the password used for the lock.

Enter the new password, and then enter it again for confirmation.

Click OK.

The Android device is locked and the password is changed.

Notify the user to set the password again.

Important note

If you select multiple Android devices and change the password, the same password is set for all the selected Android devices. If you want to set different passwords, change the password for each Android device.

Related topics

8.10 Resetting an iOS device passcode

14.5.1 Managed Smart Device List view

14.5.6 Lock Smart Device dialog box

8.10 Resetting an iOS device passcode

If an iOS device user forgets a passcode, you can reset the iOS device passcode.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, Managed Smart Device List, and then iOS Smart Device.

In the information area, select the iOS device of which you want to reset the passcode.

You can select multiple iOS devices.

From Action, select Reset Smart Device Passcode.

In the displayed dialog box, click OK.

Notify the user to set the passcode again.

Related topics

8.9 Changing an Android device password

14.5.1 Managed Smart Device List view

14.5.7 Reset Smart Device Passcode dialog box

8.11 Sending messages to Android devices

If there is information that must be reported to Android device users, you can send messages from JP1/ITDM2 - SDM to Android devices.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Smart Device module.

In the menu area, select Smart Device, Managed Smart Device List, and then Android Smart Device.

In the information area, select the Android device to which you want send messages.

You can select multiple Android devices.

From Action, select Send Notification.

In the dialog box that appears, enter the message to be sent.

Click OK.

Related topics

14.5.1 Managed Smart Device List view

14.5.14 Smart Device Message Notification dialog box

8.12 Collecting smart device log data

You can collect log data output by JP1/ITDM2 - SDM (Smart Device Agent) installed on a smart device.

Procedure

On the smart device, start JP1/ITDM2 - SDM (Smart Device Agent) (application name: JP1ITDM2SDM).

Tap Send Log.

Result

Log data of the smart device is stored in the following file:

JP1/ITDM2 - SDM (Communiation-Server)-installation-folder\cms\log\agent\name#1_yyyyMMdd_hhmmss#2.log

#1: Name of the selected smart device

#2: yyyy: year, MM: month, dd: day, hh: hour, mm: minute, ss: second

Related topics

14.5.1 Managed Smart Device List view

F. Storage locations of (and how to obtain) information required for support

9 Managing Applications

This chapter explains how to manage applications by using JP1/ITDM2 - SDM. Only Android applications can be managed.

9.1 Registering applications to be distributed in JP1/ITDM2 - SDM

In JP1/ITDM2 - SDM, you can register the applications you want to distribute to smart devices.

Prerequisites

You can register Android applications only.

You must log in by using a user account with the system administrator permission.

Procedure

Display the Distribution module.

In the menu area, select Distributed Application List or Android Application.

In the information area, click the Add button.

In the displayed dialog box, type the application information, and then click OK.

Result

The applications to be distributed are registered in JP1/ITDM2 - SDM, and information for the registered applications is displayed in the Distributed Application List view or Android Application view.

Related topics

9.2 Editing registered application information

9.3 Removing applications from JP1/ITDM2 - SDM

9.4 Distributing applications to Android devices

14.6.1 Distributed Application List view

14.6.2 Android Application view

14.6.4 Add Android Application dialog box

9.2 Editing registered application information

You can edit information about a registered application.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Distribution module.

In the menu area, select Distributed Application List or Android Application.

In the information area, click the Edit button of the application that you want to edit.

In the displayed dialog box, edit the application information, and then click OK.

Related topics

9.1 Registering applications to be distributed in JP1/ITDM2 - SDM

9.3 Removing applications from JP1/ITDM2 - SDM

9.4 Distributing applications to Android devices

14.6.1 Distributed Application List view

14.6.2 Android Application view

14.6.5 Edit Android Application dialog box

9.3 Removing applications from JP1/ITDM2 - SDM

If an application is no longer needed, remove it from JP1/ITDM2 - SDM.

Prerequisites

You must log in by using a user account with the system administrator permission.

Instruct the smart device (on which the application to be removed has been distributed or installed) to uninstall the application.

Procedure

Display the Distribution module.

In the menu area, select Distributed Application List or Android Application.

In the information area, select the application you want to remove.

Click the Remove button at the top of the information area.

In the displayed dialog box, click OK.

Related topics

9.1 Registering applications to be distributed in JP1/ITDM2 - SDM

9.2 Editing registered application information

9.6 Uninstalling distributed applications

14.6.1 Distributed Application List view

14.6.2 Android Application view

9.4 Distributing applications to Android devices

If you want users to install applications as required, distribute the applications to managed Android devices.

Prerequisites

You must log in by using a user account with the system administrator permission.

The applications to be distributed must be registered in JP1/ITDM2 - SDM in advance.

Procedure

Display the Distribution module.

In the menu area, select Android Application.

In the information area, select the application to be distributed.

On the List of Smart Devices Not Distributed To tab in the lower part of the information area, select the Android device to which you want to distribute the application.

You can select multiple Android devices.

In the lower part of the information area, select Action, and then Application Distribution.

In the displayed dialog box, click OK.

Result

The application is distributed to the selected Android devices. Each user can install the application from the list of distributed applications that are not installed.

After the application is distributed, Android device information is displayed on the List of Smart Devices Distributed To tab in the lower part of the information area of the Android Application view.

Related topics

9.1 Registering applications to be distributed in JP1/ITDM2 - SDM

9.2 Editing registered application information

9.5 Instructing users to install applications

14.6.2 Android Application view

9.5 Instructing users to install applications

You can instruct users to install applications on Android devices. If you instruct a user to install an application that has not been distributed, the instructions for distribution and installation of the application are executed at the same time.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Distribution module.

In the menu area, select Android Application.

In the information area, select the application to be installed.

Select the Android device on which the application is to be installed.

To instruct a user to install a distributed application:

On the List of Smart Devices Distributed To tab in the lower part of the information area, select the Android device on which the application is to be installed. You can select multiple Android devices.

To instruct a user to install an application that has not been distributed:

On the List of Smart Devices Not Distributed To tab in the lower part of the information area, select the Android device on which the application is to be installed. You can select multiple Android devices.

In the lower part of the information area, select Action, and then Application Installation.

In the displayed dialog box, click OK.

Result

The instruction to install the distributed application is displayed on the Android device.

After the user installs the application, the Android device information appears on the List of Smart Devices Installed To tab in the lower part of the information area of the Android Application view.

Related topics

9.1 Registering applications to be distributed in JP1/ITDM2 - SDM

9.2 Editing registered application information

9.4 Distributing applications to Android devices

14.6.2 Android Application view

9.6 Uninstalling distributed applications

You can instruct Android devices to uninstall distributed or installed applications, and then delete application data.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Distribution module.

In the menu area, select Android Application.

In the information area, select the application to be uninstalled.

In the lower part of the information area, click the List of Smart Devices Distributed To or List of Smart Devices Installed To tab. Then, select the Android device to which you want to send the instruction to uninstall the application.

You can select multiple Android devices.

In the lower part of the information area, select Action, and then Application Deletion.

In the displayed dialog box, click OK.

Result

If the distributed application is not installed:

Application data is deleted.

If the distributed application is installed:

The instruction to uninstall the application is displayed on the Android device. When the user uninstalls the application, application data is also deleted.

When the application is uninstalled and application data is deleted from the Android device, Android device information appears on the List of Smart Devices Not Distributed To tab in the lower part of the information area (Android Application view).

Related topics

9.4 Distributing applications to Android devices

9.5 Instructing users to install applications

14.6.2 Android Application view

10 Event Reference

This chapter describes how to reference events that are output by JP1/ITDM2 - SDM.

10.1 Viewing event details

You can view details about events output by JP1/ITDM2 - SDM.

Procedure

Display the Events module.

In the menu area, select Events, and then select the severity of the events you want to display.

In the information area, click the link in the Description column for the event for which you want to display details.

Alternatively, select the event for which you want to display details, and then select Action and Show Details, to open the Event Detail dialog box.

Result

Details of the events you have selected are displayed in the Event Detail dialog box.

Related topics

2.7 Displaying events

14.7.1 Event List view

14.7.2 Event Detail dialog box

10.2 Exporting event information

You can export the event information displayed in the information area of the Events module to a CSV file.

Procedure

Display the Events module.

Display the event information to be exported in the information area.

From Action, select Export Event List.

In the window that appears, specify the file name and the location to save the file, and then click the Save button

Result

The CSV file is saved with the specified file name in the specified location.

Related topics

2.7 Displaying events

14.7.1 Event List view

11 Customizing Settings

This chapter describes items that can be customized in the Settings module.

11.1 Specifying settings for event notification

You can specify settings for mail notification so that when a specific event occurs, you can be notified of the event occurrence via email.

Prerequisites

You must log in by using a user account with the system administrator permission.

You must set up the mail server.

Procedure

Display the Settings module.

In the menu area, select Events, and then Event Notifications.

In the window that appears, select the check boxes for the severity and types of events about which you want to be notified by email, and user IDs of email recipients.

Postrequisites

Use the event mail format information file to define the event email format.

Related topics

2.7 Displaying events

11.2 Setting up mail servers

14.8.4 Event Notifications view

16.4 Event mail format information file (eventmail.properties)

11.2 Setting up mail servers

To receive notification emails about the occurrence of an event, you must specify information about the mail server used by JP1/ITDM2 - SDM to send the email notifications.

Prerequisites

You must log in by using a user account with the system administrator permission.

Procedure

Display the Settings module.

In the menu area, select General and then SMTP Server.

In the information area, specify the mail server information.

Click the Send a Test Email button to send a test email to the email address set for the user account of a logged-in user. Check if the test mail is sent properly.

Click the Apply button.

Result

Emails can be sent by using the specified user.

Related topics

11.1 Specifying settings for event notification

14.8.5 SMTP Server view

12 Database Management

This chapter describes how to manage a database.

12.1 Backing up the database

Back up the database before replacing the smart device manager and for restoration in case of a hard disk failure.

Procedure

On the communication server, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

On the smart device manager, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager Server Service

On the smart device manager, start the command prompt, and then change the current directory to the command storage location.

On the smart device manager, execute the sdmexportdb command.

On the smart device manager, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager Server Service

On the communication server, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

Result

The backup data (that is, the backup of the data) is saved. By default, the backup data is stored in the following folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\backup

Related topics

15. Executing commands

15. sdmexportdb (acquiring backup data)

B.1 List of services

12.2 Restoring the database

You can restore the database to the status when it was backed up. To restore the database, you need backup data acquired by using the sdmexportdb command.

Procedure

On the communication server, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

On the smart device manager, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager Server Service

Copy the backup data acquired by the sdmexportdb command to the smart device manager.

On the smart device manager, start the command prompt, and then change the current directory to the command storage location.

On the smart device manager, execute the sdmimportdb command.

On the smart device manager, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager Server Service

On the communication server, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

Result

The database of JP1/ITDM2 - SDM (Smart Device Manager) is restored to the status when the backup data was acquired.

Related topics

15. Executing commands

15. sdmimportdb (restoring backup data)

B.1 List of services

12.3 Changing the connection destination port number for the database

You can change the connection destination port number for the database on the smart device manager.

Prerequisites

You must stop all the JP1/ITDM2 - SDM program modules and all commands.

Procedure

On the communication server, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

On the smart device manager, start the command prompt, and then change the current directory to the command storage location.

On the smart device manager, execute the sdmnetchange command.

On the smart device manager, use a text editor to open the following file:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\db\conf\pdsys

Change the value of pd_name_port.

Example: Change the underlined part:

set pd_name_port = 26066

On the smart device manager, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager Server Service

On the smart device manager, stop the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (DB Service)

On the smart device manager, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (DB Service)

On the smart device manager, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager Server Service

On the communication server, start the following service from the Windows Services window:

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

Result

The connection destination port number for the database is changed.

Related topics

15. Executing commands

15. sdmnetchange (changing the network configuration for the smart device manager or communication server)

B.1 List of services

13 Troubleshooting

This chapter describes the actions to be taken when a problem occurs in JP1/ITDM2 - SDM.

13.1 Troubleshooting procedure on the smart device manager

This section describes the actions to take if a problem occurs during operation of the smart device manager.

Procedure

Check the error message.

Check the error message as follows:

Check the error information in the dialog box that was displayed when the error occurred.

Check the error information in the output log files.

Check the event message in the Home module or in the Events module.

Using the error message, check the cause of and workaround for the trouble, and then take action to resolve the problem.

If necessary, collect log data (troubleshooting information) for the smart device manager.

Related topics

10.1 Viewing event details

15. sdmgetlogs (collecting log information)

17. Messages

F. Storage locations of (and how to obtain) information required for support

13.2 Troubleshooting procedure on a smart device

This section describes the actions to take if a problem occurs during operation of a smart device.

Procedure

Check the error message.

Check the event message in the Home module or in the Events module.

Using the error message, check the cause of and workaround for the trouble, and then take action to resolve the problem.

If necessary, collect smart device log data (troubleshooting information).

Related topics

8.12 Collecting smart device log data

10.1 Viewing event details

14.3 Home module

14.7 Events module

17. Messages

13.3 Actions to be taken when a disk is low on free space

If the amount of free space on the disk that contains the database for JP1/ITDM2 - SDM (Smart Device Manager) is insufficient, new data cannot be added and management with correct information is disabled. To avoid such problems, it is necessary to monitor the free space available on the disk that JP1/ITDM2 - SDM (Smart Device Manager) uses, and to take action when this space runs low.

You can check the free space on the disk that JP1/ITDM2 - SDM (Smart Device Manager) uses from the Database and Disk Usage panel in the Home module. If the free space on the disk is becoming low, take action to increase free space.

For example, you can perform the following:

Delete unnecessary data from the disk.

If you are using a logical drive, increase its storage capacity by expanding the disk.

If you cannot provide free disk space, replace the smart device manager. You need to back up the database before replacing the smart device manager. After replacing the smart device manager, install JP1/ITDM2 - SDM (Smart Device Manager), and then restore the database from the backup file.

Related topics

3.5 Procedure for installing JP1/ITDM2 - SDM (Smart Device Manager)

12.1 Backing up the database

12.2 Restoring the database

14.3.3 Database and Disk Usage panel

13.4 Troubleshooting for a communication error between servers

This section describes the actions to take if a communication error occurs between servers.

13.4.1 Actions to take if a communication error occurs between the smart device manager and the communication server

The following describes the possible causes and actions to take if a communication error occurs between the smart device manager and the communication server:

Cause

Action

The service of the smart device manager or communication server is stopped.

Start the service of the relevant server from the Windows Services window.

The connection-destination address and port number settings between the smart device manager and communication server are not correct.

Revise the network settings.

The Web server's SSL communication settings on the communication server contain an error.

Revise the SSL communication settings on the communication server.

Other than the above (disconnected cable or hardware failure)

Contact the system administrator.

Related topics

3.1 Flow of building a system

3.8 Opening ports on the router and setting up a firewall on each server

3.11 Obtaining certificates for SSL communication

13.4.2 Actions to take if a communication error occurs between the communication server and the messaging server

The following describes the possible causes and actions to take if a communication error occurs between the communication server and the messaging server:

Cause

Action

The service of the communication server or messaging server is stopped.

Start the service of the relevant server from the Windows Services window.

The connection-destination address and port number settings between the communication server and messaging server are not correct.

Revise the network settings.

Other than the above (disconnected cable or hardware failure)

Contact the system administrator.

Related topics

3.8 Opening ports on the router and setting up a firewall on each server

13.5 Troubleshooting during window operation

The following describes the possible cause and action to take if downloading of the export file does not start when you try to export a list of smart devices or a list of events:

Cause

Action

The Enable Protected Mode check box for Trusted Sites is cleared in the Internet Explorer settings.

For Internet Explorer 8, specify as follows:

Add the smart device manager to Trusted sites.

Change the security level for Trusted sites.

Select the Enable Protected Mode check box.

For details, see the information provided by Microsoft.

13.6 Troubleshooting problems with the database

This section describes the actions to take if a database problem occurs.

13.6.1 Actions to take if a database connection error occurs

The following describes the possible cause and action to take if a database connection error occurs:

Cause

Action

JP1/ITDM2 - Smart Device Manager (DB Service) has stopped or is starting.

If JP1/ITDM2 - Smart Device Manager (DB Service) has stopped, from the Windows Services window, start JP1/ITDM2 - Smart Device Manager (DB Service).

If JP1/ITDM2 - Smart Device Manager (DB Service) is starting, wait until it has started.

13.6.2 Actions to take if a database access error occurs

The following describes the possible cause and actions to take if a database connection error occurs:

Cause

Action

An access error is caused by database corruption.

Try to restore the database by using the database restore command.

13.6.3 Actions to take if database backup or restoration fails

The following describes the possible causes and actions to take if database backup or restoration fails:

Cause

Action

You do not have permission to access the database storage folder.

Make sure that you have permissions to access the database storage folder.

If you do not have the required access permission for the folder, obtain it, and then try to back up or restore the database again.

An I/O error occurred.

Make sure that no disk error occurred.

If a disk error occurred, set up the environment again, such as replacing the hard disk.

If the problem cannot be corrected by taking the above actions, collect the backup data of the database and troubleshooting information.

Related topics

15. sdmgetlogs (collecting log information)

A.1 Folders created on the smart device manager

14 GUI Reference

This chapter describes the windows of JP1/ITDM2 - SDM, buttons, operation menus, and items displayed in windows.

14.1 Window transition diagrams

This section describes window transitions in JP1/ITDM2 - SDM.

14.1.1 Window transitions from the Login window to immediately after the login

The following shows the window transitions from the Login window to immediately after the login.

Window transitions

Related Topics

14.2 Login window

14.3 Home module

14.4 Security module

14.5 Smart Device module

14.6 Distribution module

14.7 Events module

14.8 Settings module

14.1.2 Window transitions from the Security module

The following shows the window transitions from the Security module used to manage security rules.

Window transitions

Related Topics

14.4 Security module

14.4.1 Security Policy List view

14.4.11 Android Policy List view

14.4.15 iOS Profile List view

14.1.3 Window transitions from the Smart Device module

The following shows the window transitions from the Smart Device module used to manage smart device information.

Window transitions

Related Topics

14.5 Smart Device module

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.1.4 Window transitions from the Distribution module

The following shows the window transitions from the Distribution module used to manage applications to be distributed.

Window transitions

Related Topics

14.6 Distribution module

14.6.1 Distributed Application List view

14.6.2 Android Application view

14.1.5 Window transitions from the Events module

The following shows the window transitions from the Events module used to check events that occurred during JP1/ITDM2 - SDM operation.

Window transitions

Related Topics

14.7 Events module

14.7.1 Event List view

14.1.6 Window transitions from the Settings module

The following shows the window transitions from the Settings module used to specify settings required for operating JP1/ITDM2 - SDM.

Window transitions

Related Topics

14.8 Settings module

14.8.1 Account Management view

14.8.4 Event Notifications view

14.8.5 SMTP Server view

14.2 Login window

Any user who logs in through the Login window must be authenticated. When authentication is successful, the user can log in to JP1/ITDM2 - SDM. If the built-in account or a newly created user account is used to log in, or if the password has expired, the Change Password dialog box is displayed.

Window

Items

The following describes the items displayed in the window.

User ID

Enter the user ID used to log in to JP1/ITDM2 - SDM (Smart Device Manager).

Password

Enter the password for the user name.

Related Topics

14.2.1 Change Password dialog box

14.2.1 Change Password dialog box

You can use the Change Password dialog box to change the password. If the built-in account or a newly created user account is used to log in, or if the password has expired, the Change Password dialog box is displayed.

Window

Items

The following describes the items displayed in the window.

New Password

Enter a new password.

Re-enter Password

Re-enter the password for confirmation.

14.3 Home module

The Home module is the initial module displayed to a user who logs in to JP1/ITDM2 - SDM. This module displays panels that provide an overview of information managed by JP1/ITDM2 - SDM.

Window

Related Topics

14.3.1 System Summary panel

14.3.2 Event Summary panel

14.3.3 Database and Disk Usage panel

14.3.4 Status of Certificate for MDM panel

14.3.1 System Summary panel

The System Summary panel displays an overview of the statuses of the managed smart devices.

Window

Items

The following describes the items displayed in the window.

Total Number of Registered Smart Devices

Displays the total number of smart devices registered in JP1/ITDM2 - SDM, and the difference from the previous day's number of smart devices.

Managed Smart Devices

Displays the number of managed smart devices, and the difference from the previous day's number of smart devices. If the current number of smart devices is one or more, clicking the link on the number displays the Smart Device module, in which you can check detailed information about managed smart devices.

Unmanaged Smart Devices

Displays the number of unmanaged smart devices, and the difference from the previous day's number of smart devices. If the current number of smart devices is one or more, clicking the link on the number displays the Smart Device module, in which you can check detailed information about unmanaged smart devices.

Related Topics

14.5 Smart Device module

14.3.2 Event Summary panel

The Event Summary panel displays the total number of events that occurred in the specified display period, and the number of events by event type.

Window

Clicking the link on the number of events displays the Events module, in which you can check the contents of events.

Items

The following describes the items displayed in the window.

Display Period

Changes the event display period.

Related Topics

14.7 Events module

14.3.3 Database and Disk Usage panel

In the Database and Disk Usage panel, you can check database-related information, including the database backup status and free space on the hard disk.

Window

Items

The following describes the items displayed in the window.

Database Backup

Displays the date when the database was backed up, and the backup status.

Data

Displays the hard disk usage and free space.

Database

Displays the hard disk usage for the database, and free space.

14.3.4 Status of Certificate for MDM panel

In the Status of Certificate for MDM panel, you can check information about the expiration dates of certificates and the validity of a certificate.

Window

Items

The following describes the items displayed in the window.

Validity of Certificate for MDM

Displays the validity of the certificate for MDM.

The following describes the displayed information:

Information

Description

Not Used

The certificate is not set.

Normal

The certificate is set (normal).

Invalid

The certificate is set (invalid).

Expiration date of Certificate for MDM

Displays the expiration date of the certificate for MDM.

The following describes the displayed information:

Information

Description

hyphen (-)

The certificate for MDM is not set.

yyyy/MM/dd hh:mm:ss# (Date/Time)

The certificate for MDM is set.

(Critical)

Expired

(Warning)

One month before expiration

(Information)

Within the valid period, or the certificate for MDM is not set.

# yyyy: year, MM: month, dd: day, hh: hour, mm: minute, ss: second

14.4 Security module

In the Security module, you can manage security rules provided in JP1/ITDM2 - SDM.

Window

Related Topics

14.4.1 Security Policy List view

14.4.11 Android Policy List view

14.4.15 iOS Profile List view

14.4.1 Security Policy List view

The Security Policy List view displays a list of created security policies. This view can also be used to add, edit, or remove security policies.

Window

Items

The following describes the items displayed in the window.

Add button

Adds a new security policy.

Remove button

Removes the selected security policy.

Edit button (Browse button)

Edits the selected security policy.

If you have logged in by using an account with the view permission, the Browse button is displayed, which allows you to check the contents of the selected security policy.

Notes tab

The description of the selected security policy is displayed in the lower part of the information area. If you have logged in by using an account with the system administrator permission, you can edit this description.

Related Topics

14.4.2 Add Security Policy dialog box

14.4.3 Edit Security Policy dialog box

14.4.4 View Security Policy dialog box

14.4.2 Add Security Policy dialog box

The Add Security Policy dialog box allows you to add a new security policy.

Window

Items

The following describes the security configuration items.

Phone Number

Sets the phone numbers allowed for use. If a phone number not registered in the phone number list is used for a smart device, an event is issued to notify the administrator.

Web Site

Sets the Web sites for which browsing is allowed or prohibited. If a Web site for which browsing is prohibited is viewed on a smart device, an event is issued to notify the administrator.

Application

Allows or prohibits the use of applications. If an application for which use is prohibited is used on a smart device, an event is issued to notify the administrator.

You can specify whether installing applications for which use is allowed is required or optional. If an application that must be installed is not, an event is issued to notify the administrator.

The following describes the item and buttons displayed in the window.

Security Policy Name

Enter the name of a security policy.

Add button

Adds a security configuration item, such as a phone number.

Remove button

Removes the selected item, such as a phone number.

Edit button

Edits the selected item, such as a phone number.

Related Topics

14.4.5 Add Phone Number dialog box

14.4.6 Edit Phone Number dialog box

14.4.7 Add Web Site dialog box

14.4.8 Edit Web Site dialog box

14.4.9 Add Application dialog box

14.4.10 Edit Application dialog box

14.4.3 Edit Security Policy dialog box

The Edit Security Policy dialog box allows you to edit a created security policy.

Window

Items

The following describes the security configuration items.

Phone Number

Sets the phone numbers allowed for use. If a phone number not registered in the phone number list is used for a smart device, an event is issued to notify the administrator.

Web Site

Sets the Web sites for which browsing is allowed or prohibited. If a Web site for which browsing is prohibited is viewed on a smart device, an event is issued to notify the administrator.

Application

Allows or prohibits the use of applications. If an application for which use is prohibited is used on a smart device, an event is issued to notify the administrator.

You can specify whether installing applications for which use is allowed is required or optional. If an application that must be installed is not, an event is issued to notify the administrator.

The following describes the item and buttons displayed in the window.

Security Policy Name

Enter the name of a security policy.

Add button

Adds a security configuration item, such as a phone number.

Remove button

Removes the selected item, such as a phone number.

Edit button

Edits the selected item, such as a phone number.

Related Topics

14.4.5 Add Phone Number dialog box

14.4.6 Edit Phone Number dialog box

14.4.7 Add Web Site dialog box

14.4.8 Edit Web Site dialog box

14.4.9 Add Application dialog box

14.4.10 Edit Application dialog box

14.4.4 View Security Policy dialog box

The View Security Policy dialog box allows you to check the contents of a security policy.

Window

Items

The following describes the security configuration items.

Phone Number

Displays a list of the phone numbers allowed for use. If a phone number not registered in the phone number list is used for a smart device, an event is issued to notify the administrator.

Web Site

Displays a list of the Web sites for which browsing is allowed or prohibited. If a Web site for which browsing is prohibited is viewed on a smart device, an event is issued to notify the administrator.

Application

Displays a list of the applications allowed or prohibited for use. If an application for which use is prohibited is used on a smart device, an event is issued to notify the administrator.

You can specify whether installing applications for which use is allowed is required or optional. If an application that must be installed is not, an event is issued to notify the administrator.

14.4.5 Add Phone Number dialog box

The Add Phone Number dialog box allows you to add a phone number to which calls are allowed.

Window

Items

The following describes the items displayed in the window.

Phone Number

Enter the phone number to which calls are allowed for smart devices.

Description

Enter a description about the phone number. Enter information, such as the user name and purpose of the phone number, to make policy management easier.

14.4.6 Edit Phone Number dialog box

The Edit Phone Number dialog box allows you to edit a phone number to which calls are allowed.

Window

Items

The following describes the items displayed in the window.

Phone Number

Edits a registered phone number.

Description

Edit the description about the phone number. Enter information, such as the user name and purpose of the phone number, to make policy management easier.

14.4.7 Add Web Site dialog box

The Add Web Site dialog box allows you to add a Web site for which browsing is allowed or prohibited.

Window

Items

The following describes the items displayed in the window.

Registration Type

Select whether to allow or prohibit browsing of the Web site to be registered. Select Whitelist to allow browsing. Select Blacklist to prohibit browsing.

URL

Enter the URL of the Web site for which browsing is to be allowed or prohibited.

Description

Enter a description about the Web site to be registered. Enter information, such as the site name and purpose, to make policy management easier.

14.4.8 Edit Web Site dialog box

The Edit Web Site dialog box allows you to edit a Web site for which browsing is to be allowed or prohibited.

Window

Items

The following describes the items displayed in the window.

Registration Type

Select whether to allow or prohibit browsing of the Web site to be registered. Select Whitelist to allow browsing. Select Blacklist to prohibit browsing.

URL

Edit the URL of the Web site for which you want to allow or prohibit browsing.

Description

Edit the description about the Web site to be registered. Enter information, such as the site name and purpose, to make policy management easier.

14.4.9 Add Application dialog box

The Add Application dialog box allows you to add an application for which usage is to be allowed or prohibited. You can also specify whether installation of an allowed application is required.

Window

Items

The following describes the items displayed in the window.

Registration Type

Select whether to allow or prohibit use of the application to be registered. Select Whitelist to allow use of the application. Select Blacklist to prohibit use of the application.

Application Name

Enter the name of the application for which usage is to be allowed or prohibited.

Version

Enter the version of the application for which usage is to be allowed or prohibited.

Required

Specify whether installation of the allowed application is required or optional. To specify that installation is required, select the Required check box.

OS

Specify the OS for the application for which usage is to be allowed or prohibited. Select either Android or iOS.

Description

Enter a description about the application to be registered. Enter information, such as the purpose of the application, to make application management easier.

14.4.10 Edit Application dialog box

The Edit Application dialog box allows you to edit an application for which usage is to be allowed or prohibited. You can also specify whether installation of the allowed application is required.

Window

Items

The following describes the items displayed in the window.

Registration Type

Select whether to allow or prohibit use of the application to be registered. Select Whitelist to allow use of the application. Select Blacklist to prohibit use of the application.

Application Name

Edit the name of the application for which usage is to be allowed or prohibited.

Version

Edit the version of the application for which usage is to be allowed or prohibited.

Required

Specify whether installation of the allowed application is required or optional. To specify that installation is required, select the Required check box.

OS

Specify the OS for the application for which usage is to be allowed or prohibited. Select either Android or iOS.

Description

Edit the description about the application to be registered. Enter information, such as the purpose of the application, to make application management easier.

14.4.11 Android Policy List view

The Android Policy List view displays a list of created Android policies. This view can also be used to add, edit, or remove Android policies.

Window

Items

The following describes the buttons and tab displayed in the window.

Add button

Adds a new Android policy.

Remove button

Removes the selected Android policy.

Edit button (Browse button)

Edits the selected Android policy.

If you have logged in by using an account with the view permission, the Browse button is displayed, which allows you to check the contents of the selected Android policy.

Notes tab

The description of the selected Android policy is displayed in the lower part of the information area. If you have logged in by using an account with the system administrator permission, you can edit this description.

Related Topics

14.4.12 Add Android Policy dialog box

14.4.13 Edit Android Policy dialog box

14.4.14 View Android Policy dialog box

14.4.12 Add Android Policy dialog box

The Add Android Policy dialog box allows you to add a new Android policy.

Window

If you select an item, the description of the selected item appears in the Description field.

14.4.13 Edit Android Policy dialog box

The Edit Android Policy dialog box allows you to change a created Android policy.

Window

If you select an item, the description of the selected item appears in the Description field.

14.4.14 View Android Policy dialog box

The View Android Policy dialog box allows you to check the contents of an Android policy.

Window

If you select an item, the description of the selected item appears in the Description field.

14.4.15 iOS Profile List view

The iOS Profile List view displays a list of created iOS profiles. This view can also be used to add, remove, or export iOS profiles.

Window

Items

The following describes the buttons and tab displayed in the window.

Add button

Adds a new iOS profile.

Remove button

Removes the selected iOS profile.

Export button

Exports the contents of the selected iOS profile.

Notes tab

The description of the selected iOS profile is displayed in the lower part of the information area. If you have logged in by using an account with the system administrator permission, you can edit this description.

Related Topics

14.4.16 Add iOS Profile dialog box

14.4.16 Add iOS Profile dialog box

The Add iOS Profile dialog box allows you to load a configuration profile created by using the iPhone Configuration Utility, and then add it as an iOS profile.

Window

Items

The following describes the security configuration items.

iOS Profile Name

Enter the iOS profile name.

Import File

Click the Browse button, and then specify the configuration profile created by using the iPhone Configuration Utility.

Description

Enter supplementary information for the iOS profile to be added. Enter information, such as the purpose of the iOS profile, to make iOS profile management easier.

14.5 Smart Device module

In the Smart Device module, you can manage smart device information. You can also apply security rules to smart devices, and lock or initialize smart devices.

Window

Related Topics

14.5.1 Managed Smart Device List view

14.5.3 Unmanaged Smart Device List view

14.5.1 Managed Smart Device List view

The Managed Smart Device List view displays a list of managed smart devices. You can register and remove smart devices, and apply security rules. In the menu area, you can also select Android Smart Device or iOS Smart Device to check a list of smart devices by OS.

Window

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

Items

The following describes the Action menu items.

Update Device Details

Obtains the latest inventory information from the selected smart device. You can select multiple smart devices.

Initialize Smart Device

Initializes the selected smart device. You can select multiple smart devices.

Lock Smart Device

Locks the selected smart device. You can select multiple smart devices.

Reset Smart Device Passcode

Resets the passcode of the selected iOS device. You can select multiple iOS devices.

Send Notification

Sends messages to the selected Android device. You can select multiple Android devices.

Set to Unmanaged

Sets the selected smart device to Unmanaged. You can select multiple smart devices.

Apply Security Policy

Applies a security policy to the selected smart device. You can select multiple smart devices.

Apply Android Policy

Applies an Android policy to the selected Android device. You can select multiple Android devices.

Apply iOS Profile

Applies an iOS profile to the selected iOS device. You can select multiple iOS devices.

Add Smart Device

Registers new smart device information.

Import Smart Device List

Imports smart device information from a CSV file.

Export Smart Device List

Exports a list of smart devices displayed in the Managed Smart Device List view to a CSV file.

Related Topics

14.5.2 Tabs displayed in the Managed Smart Device List view

14.5.5 Initialize Smart Device dialog box

14.5.6 Lock Smart Device dialog box

14.5.7 Reset Smart Device Passcode dialog box

14.5.8 Set to Unmanaged dialog box

14.5.9 Apply Security Policy dialog box

14.5.10 Apply Android Policy dialog box

14.5.11 Apply iOS Profile dialog box

14.5.12 Add Smart Device dialog box

14.5.13 Import Smart Device List dialog box

14.5.14 Smart Device Message Notification dialog box

H. Inventory information list

14.5.2 Tabs displayed in the Managed Smart Device List view

On the tabs displayed in the Managed Smart Device List view, you can check the event list and call history for a smart device selected in the information area.

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

The following describes the tabs displayed in the window.

Events tab

Displays a list of events that occurred on the selected smart device. You can change the status of an event by clicking the link displayed in the Status column.

The following describes the Action menu items.

Set to Confirmed

Sets the status of the selected event to Ack.

Set to Not Confirmed

Sets the status of the selected event to Not Ack.

Call History tab

Displays the call history for the selected smart device. You can change the status of an entry in the history by clicking the link displayed in the Status column. You can also register phone numbers displayed in the history as allowed phone numbers in the security policy applied to the smart device.

The following describes the Action menu items.

Set to Confirmed

Sets the status of the selected entry to Ack.

Set to Not Confirmed

Sets the status of the selected entry to Not Ack.

Allow

Registers the selected phone number as an allowed phone number in the security policy applied to the smart device.

Web Browsing History tab

Displays the Web browsing history for the selected smart device. You can change the status of an entry in the history by clicking the link displayed in the Status column. You can also register URLs displayed in the history (as Whitelist or Blacklist) in the security policy applied to the smart device.

The following describes the Action menu items.

Set to Confirmed

Sets the status of the selected entry to Ack.

Set to Not Confirmed

Sets the status of the selected entry to Not Ack.

Allow

Registers the URL selected in the Web browsing history as Whitelist in the security policy applied to the smart device.

Prohibit

Registers the URL selected in the Web browsing history as Blacklist in the security policy applied to the smart device.

Software tab

Displays the applications distributed to or installed on the selected smart device. You can change the status of an application by clicking the link displayed in the Status column. You can also register applications displayed in the list (as Whitelist or Blacklist) to the security policy applied to the smart device.

The following describes the Action menu items.

Set to Confirmed

Sets the status of the selected application to Ack.

Set to Not Confirmed

Sets the status of the selected application to Not Ack.

Allow

Registers the selected application as Whitelist in the security policy applied to the smart device.

Prohibit

Registers the selected application as Blacklist in the security policy applied to the smart device.

Hardware tab

Displays hardware-related information, such as the serial number and internal storage capacity, of the selected smart device.

Running Applications tab

Displays a list of applications running on the selected smart device.

Running Services tab

Displays a list of services running on the selected smart device.

System Information tab

Displays system-related information, such as the OS information and phone number, of the selected smart device.

You can click the link for GPS Information to check the location of the smart device on a map site.

Security tab

Displays security-related information, such as the security rules applied to the selected smart device, GPS power status, and the date and time when the smart device was locked last.

Bluetooth Connection Information tab

Displays the Bluetooth connection history of the selected smart device. You can change the status of an entry in the connection history by clicking the link displayed in the Status column.

The following describes the Action menu items.

Set to Confirmed

Sets the status of the selected entry of the Bluetooth connection information to Ack.

Set to Not Confirmed

Sets the status of the selected entry of the Bluetooth connection information to Not Ack.

Related Topics

H. Inventory information list

14.5.3 Unmanaged Smart Device List view

The Unmanaged Smart Device List view displays a list of unmanaged smart devices. You can remove smart devices or apply security rules to manage smart devices.

Window

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

Items

The following describes the button displayed in the window.

Remove button

Removes the selected smart device from JP1/ITDM2 - SDM.

The following describes the Action menu items.

Apply Security Policy

Applies a security policy to the selected smart device. You can select multiple smart devices.

Apply Android Policy

Applies an Android policy to the selected Android device. You can select multiple Android devices.

Apply iOS Profile

Applies an iOS profile to the selected iOS device. You can select multiple iOS devices.

Related Topics

14.5.4 Tabs displayed in the Unmanaged Smart Device List view

14.5.9 Apply Security Policy dialog box

14.5.10 Apply Android Policy dialog box

14.5.11 Apply iOS Profile dialog box

H. Inventory information list

14.5.4 Tabs displayed in the Unmanaged Smart Device List view

On the tabs displayed in the Unmanaged Smart Device List view, you can check the event list and system information for the smart device selected in the information area.

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

The following describes the tabs displayed in the window.

Events tab

Displays a list of events that occurred on the selected smart device. You can change the status of an event by clicking the link displayed in the Status column.

The following describes the Action menu items.

Set to Confirmed

Sets the status of the selected event to Ack.

Set to Not Confirmed

Sets the status of the selected event to Not Ack.

System Information tab

Displays system-related information, such as the OS information and phone number, of the selected smart device.

You can click the link for GPS Information to check the location of the smart device on a map site.

Related Topics

H. Inventory information list

14.5.5 Initialize Smart Device dialog box

The Initialize Smart Device dialog box allows you to initialize the displayed smart device to the factory default settings.

Window

14.5.6 Lock Smart Device dialog box

The Lock Smart Device dialog box allows you to lock the displayed smart device. For Android devices, you can also change the password.

Window

Items

The following describes the items displayed in the window.

Change the password used for the lock.

Select this check box if you want to change the password when locking an Android device. If this check box is selected, data can be entered for New Password and Re-enter Password.

Important note

For iOS devices, the password does not change, even if you select the check box Change the password used for the lock., and then enter a password.

New Password

Enter a new password.

Re-enter Password

Re-enter the password for confirmation.

14.5.7 Reset Smart Device Passcode dialog box

The Reset Smart Device Passcode dialog box allows you to reset the passcode of the displayed iOS device.

Window

14.5.8 Set to Unmanaged dialog box

The Set to Unmanaged dialog box allows you to cancel the security rules applied to the displayed smart device, and set the device to Unmanaged.

Window

Items

The following describes the items displayed in the window.

Forcibly set as unmanaged

Select this check box if you want to forcibly set the smart device to Unmanaged, even if it cannot be connected.

14.5.9 Apply Security Policy dialog box

The Apply Security Policy dialog box allows you to apply a security policy to smart devices.

Window

14.5.10 Apply Android Policy dialog box

The Apply Android Policy dialog box allows you to apply an Android policy to Android devices.

Window

14.5.11 Apply iOS Profile dialog box

The Apply iOS Profile dialog box allows you to apply an iOS profile to iOS devices.

Window

14.5.12 Add Smart Device dialog box

The Add Smart Device dialog box allows you to add smart devices to be managed in JP1/ITDM2 - SDM.

Window

Items

The following describes the buttons displayed in the window.

Add button

Adds a line in which you can enter smart device information.

Remove button

Removes the selected line. You can select multiple lines.

Export button

Outputs the entered information to a CSV file.

The following describes the items for smart device information.

Name

Enter a name, such as an asset management number.

User Name

Enter the user name.

Department

Enter the department to which the user belongs.

Account

Enter information, such as an employee ID and email address.

OS Type

Select the OS type.

Security Policy

Select the security policy to be applied.

Android Policy

Select the Android policy to be applied.

iOS Profile

Select the iOS profile to be applied.

14.5.13 Import Smart Device List dialog box

The Import Smart Device List dialog box allows you to import a CSV file containing information about multiple smart devices to register them as a batch in JP1/ITDM2 - SDM.

Window

Items

The following describes the items displayed in the window.

Import File

Click the Browse button, and then specify a CSV file containing smart device information.

Related Topics

E. Output Format of Imported and Exported Files

14.5.14 Smart Device Message Notification dialog box

The Smart Device Message Notification dialog box allows you to send a message to the displayed Android device.

Window

Items

The following describes the items displayed in the window.

Input the notification message within 100 characters.

Enter the message you want to send to the Android device.

14.6 Distribution module

In the Distribution module, you can manage applications to be distributed by JP1/ITDM2 - SDM. You can also add applications to be distributed, and instruct installation.

Window

Related Topics

14.6.1 Distributed Application List view

14.6.2 Android Application view

14.6.1 Distributed Application List view

The Distributed Application List view displays a list of registered applications. This view can also be used to add, edit, or remove applications.

Window

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

Items

The following describes the buttons and tab displayed in the window.

Add button

Adds a new application.

Remove button

Removes the selected application.

Edit button (Browse button)

Edits the selected application.

If you have logged in by using an account with the view permission, the Browse button is displayed, which allows you to check the contents of the selected application.

Notes tab

The description of the selected application is displayed in the lower part of the information area. If you have logged in by using an account with the system administrator permission, you can edit this description.

Related Topics

14.6.4 Add Android Application dialog box

14.6.5 Edit Android Application dialog box

14.6.6 View Android Application dialog box

14.6.2 Android Application view

The Android Application view displays a list of registered Android applications. This view can also be used to add, edit, or remove applications.

Window

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

Items

The following describes the buttons displayed in the window.

Add button

Adds a new Android application.

Remove button

Removes the selected Android application.

Edit button (Browse button)

Edits the selected Android application.

If you have logged in by using an account with the view permission, the Browse button is displayed, which allows you to check the contents of the selected Android application.

Related Topics

14.6.3 Tabs displayed in the Android Application view

14.6.4 Add Android Application dialog box

14.6.5 Edit Android Application dialog box

14.6.6 View Android Application dialog box

14.6.3 Tabs displayed in the Android Application view

On the tabs displayed in the Android Application view, you can check the distribution and installation status of the Android application selected in the information area.

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

The following describes the tabs displayed in the window.

List of Smart Devices Not Distributed To tab

Displays information for the smart devices to which the selected Android application is not distributed.

The following describes the Action menu items.

Application Distribution

Distributes the Android application to the selected Android devices.

Application Installation

Distributes the Android application to the selected Android devices, and then instructs the installation.

List of Smart Devices Distributed To tab

Displays information for the smart devices to which the selected Android application is distributed.

The following describes the Action menu items.

Application Installation

Instructs the selected smart devices to install the Android application.

Application Deletion

Instructs the selected smart devices to uninstall the Android application, and then removes the distributed Android application.

List of Smart Devices Installed To tab

Displays information about the smart devices on which the selected Android application is installed.

The following describes the Action menu items.

Application Deletion

Instructs the selected smart devices to uninstall the Android application, and then removes the distributed Android application.

14.6.4 Add Android Application dialog box

The Add Android Application dialog box allows you to register an Android application to be distributed in JP1/ITDM2 - SDM.

Window

Items

The following describes the items displayed in the window.

Distributed File

Click the Browse button, and then specify the Android application to be registered.

Installation Parameter

Enter the parameters used for installation.

Application Package Name

Enter the Android application name.

Description

Enter a description about the Android application to be registered. Enter information, such as the purpose of the Android application, to make Android application management easier.

14.6.5 Edit Android Application dialog box

The Edit Android Application dialog box allows you to edit a registered Android application.

Window

Items

The following describes the items displayed in the window.

Installation Parameter

Enter the parameters used for installation.

Application Package Name

Enter the Android application name.

Description

Enter a description about the Android application. Enter information, such as the purpose of the Android application, to make Android application management easier.

14.6.6 View Android Application dialog box

The View Android Application dialog box allows you to check the contents of a registered Android application.

Window

14.7 Events module

In the Event module, you can check events that occurred during JP1/ITDM2 - SDM operation. You can also check event details and export an event list to a CSV file.

Window

Related Topics

14.7.1 Event List view

14.7.1 Event List view

The Event List view displays events that occurred during JP1/ITDM2 - SDM operation. You can check details about the events that occurred, and export an event list to a CSV file.

Window

Tip

You can use a filter to narrow down the displayed information. The data entered in the filter text box is used for prefix filtering.

You can perform the following operations for events that occurred:

Click a link displayed in the Status column to change the status of an event.

Click a link displayed in the Description column to check details of an event.

Click a link displayed in the Source column to display the window in which an event occurred.

Export an event list to a CSV file.

Items

The following describes the Action menu items.

Show Details

Displays details about the selected event.

Display Source Information

Displays the window, such as the Smart Device module or Settings module, in which the selected event occurred.

Set to Confirmed

Sets the status of the selected event to Ack.

Set to Not Confirmed

Sets the status of the selected event to Not Ack.

Export Event List

Exports the displayed event list to a CSV file.

Related Topics

14.7.2 Event Detail dialog box

14.7.2 Event Detail dialog box

The Event Detail dialog box can be used to check details of an event.

Window

If a high-severity event occurs, use this dialog box to check the details of the event, and take appropriate measures.

You can also click or to switch to the previous or next event without closing the dialog box.

14.8 Settings module

In the Settings module, you can specify settings required for operating JP1/ITDM2 - SDM, such as settings for user account management and for email notifications.

Window

Related Topics

14.8.1 Account Management view

14.8.4 Event Notifications view

14.8.5 SMTP Server view

14.8.1 Account Management view

The Account Management view displays a list of registered user accounts. This view can also be used to add, edit, or remove user accounts.

Window

Items

The following describes the buttons displayed in the window.

Add button

Adds a new user account.

Remove button

Removes the selected user account. The built-in account or logged-in user account cannot be removed, even if selected.

Edit button

Edits the selected user account.

Related Topics

14.8.2 Add User Account dialog box

14.8.3 Edit User Account dialog box

14.8.2 Add User Account dialog box

The Add User Account dialog box allows you to register a user account in JP1/ITDM2 - SDM.

Window

Items

The following describes the items displayed in the window.

User ID

Enter the user ID used to log in to JP1/ITDM2 - SDM.

Password

Enter the password for the user ID to be added for login.

Re-enter Password

Re-enter the password for confirmation.

User Name

Enter the user name.

Email

Enter the email address of the user to be added.

Event notification emails are sent to the email address specified here.

Description

Enter a description about the user account to be added. Enter information, such as the purpose of the user account, to make account management easier.

Permission

Select this check box to assign the system administrator permission to the user account. If this check box is not selected, only the view permission is assigned.

14.8.3 Edit User Account dialog box

The Edit User Account dialog box allows you to edit registered user account information.

Window

Items

The following describes the items displayed in the window.

User ID

Displays the user ID used to log in to JP1/ITDM2 - SDM. This item cannot be edited.

Password

Enter the password for login by using the added user ID.

Re-enter Password

Re-enter the password for confirmation.

User Name

Enter the user name.

Email

Enter the email address.

Event notification emails are sent to the email address specified here.

Description

Enter a description about the user account. Enter information, such as the purpose of the user account, to make account management easier.

Permission

Select this check box to assign the system administrator permission to the user account. If this check box is not selected, only the view permission is assigned.

Status

This item is displayed if the user account being edited is locked.

If you have logged in by using an account with the system administrator permission, you can unlock the user account. After the user account is unlocked, the user can use that user account to log in.

14.8.4 Event Notifications view

The Event Notifications can be used to specify which events are automatically notified via email.

Window

Items

The following describes the items displayed in the window.

Select the category and severity of events about which you want to be notified by email:

Select the check boxes for the severity and types of events for which you want to send notification emails. Selecting a severity check box selects all check boxes for types under that severity.

Specify event notifications to be ignored:

Select the check boxes for the events for which you do not want to send notification emails. To select all events, select the check box at the left end of the title line.

Select recipients:

Select the check boxes for the user accounts to which you want to send event notification emails. To select all user accounts, select the check box at the left end of the title line.

Interval of notification

Set the interval for event notifications.

Related Topics

2.7.2 Event types

14.8.5 SMTP Server view

The SMTP Server view can be used to set up the mail server (SMTP server) used to send event notifications by email, and send a test email.

Window

Items

The following describes the items and buttons displayed in the window.

Host name

Enter the host name of the SMTP server.

Secure connection

Select the security protection used for communication with the SMTP server.

Important note

To use SSL or TLS, you need to import the CA root certificate to the environment in which the smart device manager is running.

Port

Enter the port number of the SMTP server.

Source email

Specify the source email address of event notification emails.

Use Authentication

Select this check box if you use SMTP authentication.

User ID

Enter a user ID if you use SMTP authentication.

Password

Enter the password for the user ID if you use SMTP authentication.

Re-enter Password

Re-enter the password for confirmation.

Send a Test Email button

Sends a test email to the email address of the logged-in user.

Apply button

Applies the specified settings.

Related Topics

3.12 Setting up certificates for SSL communication on the smart device manager

14.8.4 Event Notifications view

15 Commands

This chapter describes JP1/ITDM2 - SDM commands.

Command description format

The description of each command consists of eight items, including the functionality, format (syntax), and arguments. The following table shows how the commands are described.

Command description format

No.

Item

Description

1

Functionality

This subsection describes the command functionality.

2

Format

This subsection describes the format of the command.

3

Arguments

This subsection describes the arguments for the command.

4

Storage location

This subsection describes the storage location for the command.

5

Execution permissions

This subsection describes the permissions required to execute the command.

6

Notes

This subsection provides notes on execution of the command.

7

Return values

This subsection describes the return values of the command.

8

Example

This subsection provides an example of usage of the command.

Executing commands

To execute JP1/ITDM2 - SDM commands, you can use the Windows command prompt. The following describes how to execute a command.

Executing commands

Open the Windows command prompt.

Change the current directory to the command storage location.

The command is stored in the following locations:

Server type

Storage location

Smart device manager

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Communication server

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\bin

Messaging server

JP1/ITDM2 - SDM (Messaging Server)-installation-folder\mss\bin

Enter the command that you want to execute.

Command List

The following table shows the list of available commands in JP1/ITDM2 - SDM.

Command List

No.

Command name

Functionality

Server where the command is executed

1

sdmexportdb

Acquires data owned by the smart device manager for backup purposes.

Smart device manager

2

sdmimportdb

Restores data owned by the smart device manager to the state at the last backup point.

Smart device manager

3

sdmioutils exportdevice

Exports smart device information.

Smart device manager

4

sdmioutils importdevice

Imports smart device information.

Smart device manager

5

sdmioutils exportpolicy

Exports security policy settings.

Smart device manager

6

sdmioutils importpolicy

Imports security policy settings.

Smart device manager

7

sdmioutils exportsdpolicy

Exports Android policy or iOS profile information.

Smart device manager

8

sdmioutils importsdpolicy

Imports Android policy or iOS profile information.

Smart device manager

9

sdmioutils exportdeliveryapp

Exports application distribution information.

Smart device manager

10

sdmioutils importdeliveryapp

Imports application distribution information.

Smart device manager

11

sdmnetchange

Changes the network configuration for the smart device manager or communication server.

Smart device manager

Communication server

12

sdmcreatemdmcertreq

Creates an MDM signed-certificate request file when iOS devices are managed.

Smart device manager

Communication server

13

sdmgetlogs

Collects log information on the smart device manager, communication server, JP1/ITDM2 - SDM (Smart Device Agent), or messaging server.

Smart device manager

Communication server

Messaging server

Related Topics

15. sdmexportdb (acquiring backup data)

15. sdmimportdb (restoring backup data)

15. sdmioutils exportdevice (exporting smart device information)

15. sdmioutils importdevice (importing smart device information)

15. sdmioutils exportpolicy (exporting security policy settings)

15. sdmioutils importpolicy (importing security policy settings)

15. sdmioutils exportsdpolicy (exporting Android policy information or iOS profile information)

15. sdmioutils importsdpolicy (importing Android policy information or iOS profile information)

15. sdmioutils exportdeliveryapp (exporting distributed application information)

15. sdmioutils importdeliveryapp (importing distributed application information)

15. sdmnetchange (changing the network configuration for the smart device manager or communication server)

15. sdmcreatemdmcertreq (creating an MDM signed-certificate request file)

15. sdmgetlogs (collecting log information)

sdmexportdb (acquiring backup data)

This command is used to export data on the smart device manager for backup purposes.

Functionality

This command exports data on the smart device manager for backup purposes. The acquired backup can be used for data restoration in the event of a failure.

When you execute this command, a new backup storage folder is created with the name of yyyyMMddhhmmss# under the backup folder you specify in the argument. The backup file will be created in this folder.

# yyyy: year, MM: month, dd: day, hh: hours, mm: minutes, ss: seconds

Format

sdmexportdb[ -f backup-folder]

Arguments

-f backup-folder

Specify the absolute path to the backup storage folder. Only the folders in local drive can be specified. The size of the backup file varies depending on the operational environment and how long JP1/ITDM2 - SDM has been used. Make sure to keep enough free space for the disk drive in which the backup folder resides. The amount of space required is greater than the sum of the size of the database folder and the data folders that are already taking up capacity.

To specify a path containing a space, enclose the strings with double quotation marks (").

Make sure that the path length of the backup folder is 165 or fewer characters (bytes), including the backup file name.

You can use half-width alphanumeric characters, white space, and the following special characters:

#, (, ), hyphen (-), period (.), @, underscore (_), and path-delimiter backslash (\)

If this argument is specified, the following backup folder is used:

folder-specified-in-argument\yyyyMMddhhmmss

If this argument is omitted, backup files are stored in the following default backup folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\backup\yyyyMMddhhmmss

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager and communication server must be stopped.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmimportdb

Commands beginning with sdmioutils

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the folder name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

16

The specified folder does not exist.

17

An access error for the specified folder occurred.

18

Another command is being executed.

24

An attempt to create a backup file failed.

30

The database cannot be accessed.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to acquire backup data to C:\tmp\backup.

sdmexportdb -f C:\tmp\backup

Related Topics

15. Executing commands

15. sdmimportdb (restoring backup data)

sdmimportdb (restoring backup data)

This command restores data owned by the smart device manager to the state at the last backup point.

Functionality

This command restores data owned by the smart device manager to the state of the last backup point in case a disk failure occurs. To restore data, a backup file acquired with the sdmexportdb command is used.

Execute this command on the smart device manager.

Format

sdmimportdb[ -f backup-folder]

Arguments

-f backup-folder

Specify the absolute path to the folder in which the backup file of the target restore point resides. The path must contain the folder name yyyyMMddhhmmss that is created in the backup folder by the sdmexportdb command. Only a folder in a local drive can be specified.

To specify a path containing a space, enclose the strings with double quotation marks (").

Make sure that the path length of the backup folder is 165 or fewer characters (bytes), including the backup file name.

Half-width alphanumeric characters, white space, and the following special characters are allowed:

#, (, ), -(hyphen),.(period), @, _, and path-delimiter backslash (\)

When this argument is specified, the backup folder specified in the argument is used.

When this argument is omitted, the most up-to-date backup folder available under the path below is chosen by name.

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\backup

Example:

If the following backup folders are under the path, the \20140101060000 folder is used to restore data:

\20140101000000

\20140101060000

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager and communication server must be stopped.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

Commands beginning with sdmioutils

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the folder name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

16

The specified folder does not exist.

17

An access error for the specified folder occurred.

18

Another command is being executed.

25

An attempt to restore the database failed.

30

The database cannot be accessed.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to restore data from a backup acquired at 2:30:00 on January 1, 2014 (backup folder: C:\tmp\backup\20140101023000).

sdmimportdb -f C:\tmp\backup\20140101023000

Related Topics

15. Executing commands

15. sdmexportdb (acquiring backup data)

sdmioutils exportdevice (exporting smart device information)

This command exports smart device information in CSV format.

Functionality

This command exports smart device information to the specified file in CSV format.

Execute this command on the smart device manager.

Format

sdmioutils exportdevice -export export-file-name[ -encoding character-encoding][ -s]

Arguments

-export export-file-name

Specify the absolute path (within 259 bytes) of the CSV file to export.

-encoding character-encoding

Specify the character encoding of the file to be exported. If you do not specify this argument, the character encoding is set to UTF-8.

The following types of character encoding can be specified.

ISO-8859-1

UTF-8

UTF-16

-s

Overwrites the file even if a file with the same file name already exists at the export destination. If you do not specify this argument and a file with the same file name already exists, an overwrite confirmation message appears. In this case, the system cancels the output or overwrites the file according to the administrator's reply.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to export smart device information to C:\temp\smartdevice.csv.

sdmioutils exportdevice -export C:\temp\smartdevice.csv -encoding UTF-8 -s

Related Topics

15. Executing commands

15. sdmioutils importdevice (importing smart device information)

E.1 Format of exported or imported smart device list CSV file

sdmioutils importdevice (importing smart device information)

This command imports smart device information using a CSV file.

Functionality

This command imports smart device information using a CSV file.

Execute this command on the smart device manager.

Format

sdmioutils importdevice -import import-file-name[ -encoding character-encoding]

Arguments

-import import-file-name

Specify the absolute path (within 259 bytes) of the CSV file to import.

-encoding character-encoding

Specify the character encoding of the file to be imported. If you do not specify this argument, the character encoding is set to UTF-8.

The following types of character encoding can be specified.

ISO-8859-1

UTF-8

UTF-16

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to import the smart device information defined in the CSV file C:\temp\smartdevice.csv.

sdmioutils importdevice -import C:\temp\smartdevice.csv -encoding UTF-8

Related Topics

15. Executing commands

15. sdmioutils exportdevice (exporting smart device information)

E.1 Format of exported or imported smart device list CSV file

sdmioutils exportpolicy (exporting security policy settings)

This command exports security policy settings in XML format.

Functionality

This command exports security policy settings to the specified file in XML format.

For an environment with multiple JP1/ITDM2 - SDM systems configured, this command enables security policy settings created on one smart device manager to be reused on another smart device manager.

Execute this command on the smart device manager.

Format

sdmioutils exportpolicy -export export-file-name -name security-policy-name[ -s]

Arguments

-export export-file-name

Specify the absolute path (within 259 bytes) of the XML file to export.

-name security-policy-name

Specify a security policy name to export.

-s

Overwrites the file even if a file with the same file name already exists at the export destination. If this argument is not specified and a file with the same file name already exists, an overwrite confirmation message appears. In this case, the system cancels the output or overwrites the file according to the administrator's reply.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

20

The specified security policy does not exist.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to export the security policy settings Development Department policy to C:\temp\exportpolicy.xml.

sdmioutils exportpolicy -export C:\temp\exportpolicy.xml -name Development Department policy -s

Related Topics

15. Executing commands

15. sdmioutils importpolicy (importing security policy settings)

E.3 Format of an exported security policy list XML file

sdmioutils importpolicy (importing security policy settings)

This command imports previously exported security policy settings.

Functionality

This command imports previously exported security policy settings.

For an environment with multiple JP1/ITDM2 - SDM systems configured, this command enables security policy settings created on one smart device manager to be reused on another smart device manager.

Execute this command on the smart device manager.

Format

sdmioutils importpolicy -import import-file-name[ -name security-policy-name]

Arguments

-import import-file-name

Specify the absolute path (within 259 bytes) of the XML file to import.

-name security-policy-name

Specify a security policy name to import. If this argument is omitted, the security policy name defined in XML is registered. If the specified security policy name already exists, registration fails.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

22

The specified security policy already exists.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to import the security policy settings in exportpolicy.xml (security policy name: Development Department policy) that was exported to C:\temp\.

sdmioutils importpolicy -import C:\temp\exportpolicy.xml -name Development Department policy

Related Topics

15. Executing commands

15. sdmioutils exportpolicy (exporting security policy settings)

E.3 Format of an exported security policy list XML file

sdmioutils exportsdpolicy (exporting Android policy information or iOS profile information)

This command exports Android policy or iOS profile information in XML format.

Functionality

This command exports Android policy or iOS profile information to the specified file in XML format.

For an environment with multiple JP1/ITDM2 - SDM systems configured, this command enables Android policy or iOS profile created on one smart device manager to be reused on another smart device manager.

Execute this command on the smart device manager.

Format

sdmioutils exportsdpolicy -export export-file-name -name Android-policy-name-or-iOS-profile-name -policytype policy-type[ -s]

Arguments

-export export-file-name

Specify the absolute path (within 259 bytes) of the XML file to export.

-name Android-policy-name-or-iOS-profile-name

Specify an Android policy name or iOS profile name to export.

-policytype policy-type

Specify the type of policy to export.

The following policy types can be specified:

0: iOS profile

1: Android policy

-s

Overwrites the file even if a security policy with the same file name already exists. If this argument is not specified and a security policy with the same file name already exists, an overwrite confirmation message appears. In this case, the system cancels the input or overwrites the file according to the administrator's reply.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

20

The specified Android policy or iOS profile does not exist.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to export Development Department policy to C:\temp\exportsdpolicy.xml.

sdmioutils exportsdpolicy -export C:\temp\exportsdpolicy.xml -name Development Department policy -policytype 0 -s

Related Topics

15. Executing commands

15. sdmioutils importsdpolicy (importing Android policy information or iOS profile information)

E.4 Format of an exported smart device security policy (Android policy or iOS profile) XML file

sdmioutils importsdpolicy (importing Android policy information or iOS profile information)

This command imports previously exported Android policy or iOS profile.

Functionality

This command imports previously exported Android policy or iOS profile.

For an environment with multiple JP1/ITDM2 - SDM systems configured, this command enables Android policy or iOS profile created on one smart device manager to be reused on another smart device manager.

Execute this command on the smart device manager.

Format

sdmioutils importsdpolicy -import import-file-name[ -name Android-policy-name-or-iOS-profile-name]

Arguments

-import import-file-name

Specify the absolute path (within 259 bytes) of the XML file to import.

-name Android-policy-name-or-iOS-profile-name

Specify an Android policy name or iOS profile name to import. If this argument is omitted, the Android policy or iOS profile name defined in XML is registered. If the specified name already exists, registration fails.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

22

The specified Android policy or iOS profile already exists.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to import Development Department policy exported to C:\temp\exportsdpolicy.xml.

sdmioutils importsdpolicy -import C:\temp\exportsdpolicy.xml -name Development Department policy

Related Topics

15. Executing commands

15. sdmioutils exportsdpolicy (exporting Android policy information or iOS profile information)

E.4 Format of an exported smart device security policy (Android policy or iOS profile) XML file

sdmioutils exportdeliveryapp (exporting distributed application information)

This command exports application distribution information in XML format.

Functionality

This command exports application distribution information to the specified file in CSV format.

If multiple JP1/ITDM2 - SDM systems are configured, this command allows application distribution information created on a smart device manager to be reused on another smart device manager.

Execute this command on the smart device manager.

Format

sdmioutils exportdeliveryapp -export export-file-name -name application-name[ -s]

Arguments

-export export-file-name

Specify the absolute path (within 259 bytes) of the XML file to export.

-name application-name

Specify the name of the application to be exported.

-s

Overwrites the file even if a security policy with the same file name already exists. If this argument is not specified and a security policy with the same file name already exists, an overwrite confirmation message appears. In this case, the system cancels the input or overwrites the file according to the administrator's reply.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

21

The specified application does not exist.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to export the application distribution information Security applications to C:\temp\exportdeliveryapp.xml.

sdmioutils exportdeliveryapp -export C:\temp\exportdeliveryapp.xml -name Security applications -s

Related Topics

15. Executing commands

15. sdmioutils importdeliveryapp (importing distributed application information)

E.5 Format of an exported distributed-application XML file

sdmioutils importdeliveryapp (importing distributed application information)

This command imports previously exported application distribution information.

Functionality

This command imports previously exported application distribution information.

If multiple JP1/ITDM2 - SDM systems are configured, this command allows application distribution information created on a smart device manager to be reused on another smart device manager.

Execute this command on the smart device manager.

Format

sdmioutils importdeliveryapp -import import-file-name[ -name application-name]

Arguments

-import import-file-name

Specify the absolute path (within 259 bytes) of the XML file to import.

-name application-name

Specify an application name to import. If this argument is omitted, the application name defined in XML is registered. If the specified application name already exists, registration fails.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To execute this command, the smart device manager must be running.

To execute this command, the database service on the smart device manager must be running.

Multiple instances of this command cannot be executed simultaneously.

This command cannot be executed simultaneously with any of the following commands:

sdmexportdb

sdmimportdb

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the file name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

23

The specified application already exists.

30

The database cannot be accessed.

40

Command execution was interrupted.

150

Other error occurred.

253

The service has not started.

Example

The following shows an example of using the command to import the application distribution information (application name: Security applications) exported to C:\temp\exportdeliveryapp.xml.

sdmioutils importdeliveryapp -import C:\temp\exportdeliveryapp.xml -name Security applications

Related Topics

15. Executing commands

15. sdmioutils exportdeliveryapp (exporting distributed application information)

E.5 Format of an exported distributed-application XML file

sdmnetchange (changing the network configuration for the smart device manager or communication server)

This command changes the connection destination address and port number set on the smart device manager or communication server.

Functionality

This command changes the connection destination address and port number set on the smart device manager or communication server.

Execute this command on the target smart device manager or communication server.

Format

sdmnetchange -target server-name[ -db database-address][ -port port-number]

Arguments

-target server-name

Specify the target server name as follows:

Manager: For the smart device manager

Comsrv: For the communication server

-db database-address

Specify this argument to change the database address (connection destination IP address). You can specify this argument only when the target server is the communication server.

-port port-number

Specify this argument to change the connection destination port number for the database. You must specify this argument if the target server is the smart device manager.

Storage location

In JP1/ITDM2 - SDM (Smart Device Manager):

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

In JP1/ITDM2 - SDM (Communication Server):

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

After executing the command, you must restart the target server.

Multiple instances of this command cannot be executed simultaneously.

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The file does not exist, or you do not have permission to access it.

18

Another command is being executed.

64

Failed to open the XML file.

65

Failed to open the hosts file.

66

Failed to stop the JP1/ITDM2 - Smart Device Manager Server Service.

67

Failed to start the JP1/ITDM2 - Smart Device Manager Server Service.

68

Failed to stop the JP1/ITDM2 - Smart Device Manager (Communication Server Service).

69

Failed to start the JP1/ITDM2 - Smart Device Manager (Communication Server Service).

70

The alias name is not correct.

71

The password is not correct.

150

Other error occurred.

Example

The following shows an example of using the command to change the connection destination port number for the database on the smart device manager.

sdmnetchange -target Manager -port 32000

The following shows an example of using the command to change the connection destination address and port number for the database on the communication server.

sdmnetchange -target Comsrv -db 192.168.1.13 -port 32001

Related Topics

15. Executing commands

sdmcreatemdmcertreq (creating an MDM signed-certificate request file)

This command creates an MDM signed-certificate request file when managing iOS devices.

Functionality

This command creates an MDM signed-certificate request file. Use this command when managing iOS devices. The name of the file created by this command is plist_encoded (or plist.xml if -x is specified).

Execute this command on the smart device manager or the communication server.

Format

sdmcreatemdmcertreq -a alias-name -p password -f name-of-folder-for-storing-signature-files[ -o file-destination][ -x]

Arguments

-a alias-name

Specify the alias name (within 260 bytes) that was specified when the MDM certificate request file was created.

-p password

Specify the password (within 260 bytes) that was specified when the MDM certificate request file was created.

-f name-of-folder-for-storing-signature-files

Specify the absolute path (within 260 bytes) to the folder that stores a file used to sign the MDM certificate request file.

-o file-destination

Specify the absolute path (within 260 bytes) to the output destination of the MDM signed-certificate request file.

-x

Specify this argument to output the MDM signed-certificate request file in XML (non-encoded) format.

Storage location

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

Multiple instances of this command cannot be executed simultaneously.

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid.

14

The file does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

70

The alias name is not correct.

71

The password is not correct.

150

Other error occurred.

Example

The following shows an example of using the command to create the MDM signed-certificate request file (plist_encoded).

sdmcreatemdmcertreq -a mdmalias -p mdmpass -f C:\work -o C:\temp

The following shows an example of using the command to output the created MDM signed-certificate request file in XML format (plist.xml).

sdmcreatemdmcertreq -a mdmalias -p mdmpass -f C:\work -o C:\temp -x

Related Topics

3.11.4 Flow of obtaining the MDM client certificate for SSL communication for the APNs server (when managing iOS devices)

3.11.5 Procedure for downloading the MDM certificate request file (when managing iOS devices)

3.11.6 Procedure for creating an MDM signed-certificate request file (when managing iOS devices)

15. Executing commands

sdmgetlogs (collecting log information)

This command collects log information compressed in zip format for the smart device manager, communication server, JP1/ITDM2 - SDM (Smart Device Agent), or messaging server.

Functionality

This command collects log information compressed in zip format for the smart device manager, communication server, JP1/ITDM2 - SDM (Smart Device Agent), or messaging server.

Execute this command on the server for which you want to collect log information. To collect log data for JP1/ITDM2 - SDM (Smart Device Agent), execute the command on the communication server.

The following table lists the output file names:

Collection target

file name

Smart device manager

tsinfo_manager.zip

Communication server

tsinfo_comsrv.zip

JP1/ITDM2 - SDM (Smart Device Agent)

tsinfo_agent.zip

Messaging server

tsinfo_msgsrv.zip

Format

sdmgetlogs -target log-collection-target[ -f output-folder]

Arguments

-target log-collection-target

Specify the log collection target as follows:

Collection target

Specification

Smart device manager

Manager

Communication server

Comsrv

JP1/ITDM2 - SDM (Smart Device Agent)

Agent

Messaging server

Msgsrv

-f output-folder

Specify the absolute path (within 161 bytes) to the output destination of the collected log information.

If this argument is omitted, log information will be output to one of the following folders created by the command:

Collection target

Output folder if this argument is omitted

Smart device manager

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\troubleshoot

Communication server

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\troubleshoot

JP1/ITDM2 - SDM (Smart Device Agent)

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\troubleshoot

Messaging server

JP1/ITDM2 - SDM (Messaging Server)-installation-folder\mss\troubleshoot

Storage location

The command is stored in the following locations:

Collection target

Storage location

Smart device manager

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin

Communication server

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\bin

JP1/ITDM2 - SDM (Smart Device Agent)

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\bin

Messaging server

JP1/ITDM2 - SDM (Messaging Server)-installation-folder\mss\bin

Execution permissions

Administrator permissions (this command is executed from the administrator's console if the Windows UAC function is enabled)

Notes

To collect log information for JP1/ITDM2 - SDM (Smart Device Agent), you must send log information from JP1/ITDM2 - SDM (Smart Device Agent) to the communication server before executing the command.

Multiple instances of this command cannot be executed simultaneously.

Return values

Return value

Description

0

The command finished normally.

11

The format for specifying the command arguments is invalid. Alternatively, the length of the folder name specified for the command argument exceeds the upper limit.

12

You do not have the permissions to execute this command.

13

The specified server is not correct, or the operating environment of JP1/ITDM2 - SDM (Smart Device Manager) is invalid.

14

The folder does not exist, or you do not have permission to access it.

15

A file access error occurred, or the disk does not have sufficient capacity.

18

Another command is being executed.

150

Other error occurred.

Example

The following shows an example of using the command to output log information for the smart device manager to the C:\work folder.

sdmgetlogs -target Manager -f C:\work

The following shows an example of using the command to output log information for the communication server to the C:\work folder.

sdmgetlogs -target Comsrv -f C:\work

The following shows an example of using the command to output log information for JP1/ITDM2 - SDM (Smart Device Agent) to the C:\work folder on the communication server.

sdmgetlogs -target Agent -f C:\work

The following shows an example of using the command to output log information for the messaging server to the C:\work folder.

sdmgetlogs -target Msgsrv -f C:\work

Related Topics

8.12 Collecting smart device log data

15. Executing commands

16 Definition Files

This chapter describes the JP1/ITDM2 - SDM definition files.

16.1 Definition file list

The following table lists the JP1/ITDM2 - SDM definition files.

Definition file list

Server

Definition file

File name

Description

Smart device manager

Smart device manager environment setting file

manager.properties

Environment settings file for the smart device manager

Provisioning information setting file

provisioning.properties

Provisioning information settings file for the smart device

Event mail format information file

eventmail.properties

Format information file for event emails

Test mail format information file

testmail.properties

Format information file for test emails

Communication server

Communication server environment setting file

CommunicationServerEngine.properties

Environment settings file for the communication server

Messaging server

Messaging server setting file

SdMessagingServer.ini

Environment settings file for the messaging server

Important note

To change a definition file and apply settings, you must restart the server on which the definition server is stored.

Related Topics

16.2 Smart device manager environment setting file (manager.properties)

16.3 Provisioning information setting file (provisioning.properties)

16.4 Event mail format information file (eventmail.properties)

16.5 Test mail format information file (testmail.properties)

16.6 Communication server environment setting file (CommunicationServerEngine.properties)

16.7 Messaging server setting file (SdMessagingServer.ini)

16.2 Smart device manager environment setting file (manager.properties)

This file specifies the operating environment for the smart device manager.

Format

callhistory=call-history-storage-period
webhistory=Web-browsing-history-storage-period
apphistory=application-use-history-storage-period
gpsevent=whether-to-issue-GPS-power-off-event
gpsmapview=map-site-linkage-for-GPS-information-display
sdcardevent=whether-to-issue-SD-card-use-event
bluetoothevent=whether-to-issue-Bluetooth-connection-event
bluetoothalertlevel=alert-level-of-Bluetooth-connection-event
simevent=whether-to-issue-SIM-card-change-event
unlockevent=number-of-days-until-event-is-issued-before-next-unlock
unconectedevent=event-issuing-period-if-inventory-data-collection-is-incomplete
callhistory.securityinterval=call-history-security-check-interval
webhistory.securityinterval=Web-browsing-history-security-check-interval
application.securityinterval=application-security-check-interval
bluetooth.securityinterval=Bluetooth-history-security-check-interval
baseinfo.securityinterval=basic-information-security-check-interval
communicationserverurl=communication-server-address
detail.debug.log.mode=detailed-trace-log-output-mode

Setting items

The following describes the setting items and specifiable values for the smart device manager environment setting file:

Setting item

Description

Specifiable value

Initial value

callhistory

Specify the call history storage period.

1 to 365 (in days)

120

webhistory

Specify the period to store the Web browsing history.

1 to 365 (in days)

120

apphistory

Specify the period to store the application use history.

1 to 365 (in days)

120

gpsevent

Specify whether to issue an event when GPS power is turned off.

true

Issues an event.

false

Does not issue an event.

true

gpsmapview

Specify whether to link the map site when GPS information is displayed.

true

Links the map site.

false

Does not link the map site.

true

sdcardevent

Specify whether to issue an event when an SD card is used.

true

Issues an event.

false

Does not issue an event.

true

bluetoothevent

Specify whether to issue an event when a Bluetooth connection is established.

true

Issues an event.

false

Does not issue an event.

true

bluetoothalertlevel

Set the alert level of an event that is issued when a Bluetooth connection is established.

0

Critical

1

Warning

2

Information

0

simevent

Specify whether to issue an event when a SIM card is changed.

true

Issues an event.

false

Does not issue an event.

true

unlockevent

Specify whether to issue an event before the lock is released the next time. If an event is to be issued, specify the number of days until the event is issued.

0

Does not issue an event.

1 to 7

Number of days until the event is issued

1

unconectedevent

Specify the period during which an event is issued if inventory data collection is incomplete.

1 to 7 (in days)

1

callhistory.securityinterval

Specify the security check interval for the call history.

1 to 86400 (in minutes)

1440

webhistory.securityinterval

Specify the security check interval for the Web browsing history.

1 to 86400 (in minutes)

1440

application.securityinterval

Specify the security check interval for applications.

1 to 86400 (in minutes)

1440

bluetooth.securityinterval

Specify the security check interval for the Bluetooth history.

1 to 86400 (in minutes)

1440

baseinfo.securityinterval

Specify the security check interval for basic information.

1 to 86400 (in minutes)

1440

communicationserverurl

Specify the address of the communication server to which the smart device manager is connected.

This item must be specified.

host-name:port-number

host-name

Host name of the communication server (FQDN format)

port-number#

The communication server HTTPS port number for SSL communication (default: 26055)

None

detail.debug.log.mode

Set the detailed trace log output mode.

0

Disabled

1

Enabled

0

#

This port number must be the same as the port number specified in the httpsd.conf file for the communication server.

Example

callhistory=120
webhistory=120
apphistory=120
gpsevent=true
gpsmapview=true
sdcardevent=true
bluetoothevent=true
bluetoothalertlevel=1
simevent=true
unlockevent=1
unconectedevent=1
callhistory.securityinterval=30
webhistory.securityinterval=30
application.securityinterval=30
bluetooth.securityinterval=30
baseinfo.securityinterval=30
communicationserverurl=xxxxxxx.xxxxxxx.co.jp:26055
detail.debug.log.mode = 1

16.3 Provisioning information setting file (provisioning.properties)

This file specifies the provisioning information for JP1/ITDM2 - SDM (Smart Device Agent) that runs on a smart device.

Format

communicationserveraddress=connection-destination-communication-server-address
messagingseverurl=connection-destination-message-server-address
inventoryinterval=inventory-data-collection-interval
gpsinterval=GPS-information-collection-interval
lowbattery=battery-capacity-to-send-inventory-data-at-low-voltage

Setting items

The following describes the setting items and specifiable values for the provisioning information setting file:

Setting item

Description

Specifiable value

Initial value

communicationserveraddress

Specify the address of the connection destination communication server.

This item must be specified.

host-name:port-number

host-name

Host name of the communication server (FQDN format)

port-number#1

The communication server HTTPS port number for SSL communication (default: 26055)

None

messagingseverurl

Specify the address of the connection destination messaging server (for Android only).

This item must be specified.

host-name:port-number

host-name

Host name of the messaging server (FQDN format)

port-number#2

The messaging server HTTP port number for communication (default: 26079)

None

inventoryinterval

Specify the inventory data collection interval.

1 to 24 (in hours)

24

gpsinterval

Specify the GPS information collection interval.

1 to 24 (in hours)

24

lowbattery

Specify the battery level for sending inventory data in the event of low voltage.

You can specify multiple values separated by commas.

Example: 15,10,5

1 to 100 (%)

5

#1

This port number must be the same as the port number specified in the httpsd.conf file for the communication server.

#2

This port number must be the same as the port number to be set for HttpPort in the messaging server setting file (SdMessagingServer.ini).

Example

communicationserveraddress=xxxxxxx.xxxxxxx.co.jp:26055
messagingseverurl=xxxxxxx.xxxxxxx.co.jp:26079
inventoryinterval=24
gpsinterval=24
lowbattery=10,5

Related Topics

16.7 Messaging server setting file (SdMessagingServer.ini)

16.4 Event mail format information file (eventmail.properties)

This file specifies the event email format.

Format

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<comment>Event mail properties</comment>

<!-- Mail subject -->
<entry key="mail_subject">mail-subject</entry>

<!-- Mail header -->
<!--
Create data by replacing the following parameter characters enclosed in curly brackets { } with the corresponding data:

{EVENT_COUNT}           : Number of events
 -->
<entry key="mailheader">mail-header</entry>

<!-- Mail footer -->
<entry key="mailfooter">mail-footer</entry>

<!-- Mail format -->
<!--
Create data by replacing the following parameter characters enclosed in curly brackets { } with the corresponding data:

{STATUS}                : Whether the event is checked
{ALERT_LEVEL}           : Severity
{MESSAGE_ID}            : Event number
{MESSAGE_CONTENT}       : Event description
{NOTE}                  : Detailed information for the event
{EVENT_DATE}            : Date and time when the event was registered
{MESSAGE_TYPE}          : Event type
{EVENT_ORIGIN}          : Source of the event
 -->
<entry key="mailformat">mail-format</entry>
</properties>

Setting items

The following describes the setting items of the event email format information file:

Setting item

Description

mail_subject

Specify the email subject name.

mailheader

Specify the email header.

mailfooter

Specify the email footer.

mailformat

Specify the email text.

The table below lists the parameter characters you can use to specify event email. The parameter characters used in the file are replaced with the corresponding data when an email is sent.

Parameter character

Description

{EVENT_COUNT}

Number of events

{STATUS}

Whether the event is checked

{ALERT_LEVEL}

Severity

{MESSAGE_ID}

Event number

{MESSAGE_CONTENT}

Event description

{NOTE}

Detailed information for the event

{EVENT_DATE}

Date and time when the event was registered

{MESSAGE_TYPE}

Event type

{EVENT_ORIGIN}

Source of the event

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<comment>Event mail properties</comment>

<!-- Mail subject -->
<entry key="mail_subject">Event Mail Information</entry>

<!-- Mail header -->
<!--
Create data by replacing the following parameter characters enclosed in curly brackets { } with the corresponding data.

{EVENT_COUNT}           : Number of events
 -->
<entry key="mailheader"><![CDATA[Number of events: {EVENT_COUNT}]]></entry>

<!-- Mail footer -->
<entry key="mailfooter"><![CDATA[
////////////////////////////////////
* Company: XXXXXXX
* Address: XXXXXXXXX X-X-X
* MAIL: XXXXXX@XXX.XX.XX
* TEL: XXX-XXXX-XXXX
////////////////////////////////////
]]></entry>

<!-- Mail format -->
<!--
Create data by replacing the following parameter characters enclosed in curly brackets { } with the corresponding data.

{STATUS}                : Whether the event is checked
{ALERT_LEVEL}           : Severity
{MESSAGE_ID}            : Event number
{MESSAGE_CONTENT}       : Event description
{NOTE}                  : Detailed information for the event
{EVENT_DATE}            : Date and time when the event was registered
{MESSAGE_TYPE}          : Event type
{EVENT_ORIGIN}          : Source of the event
 -->
<entry key="mailformat"><![CDATA[
Whether the event is checked                : {STATUS}
Severity                                    : {ALERT_LEVEL}
Event number                                : {MESSAGE_ID}
Event description                           : {MESSAGE_CONTENT}
Detailed information for the event          : {NOTE}
Date and time when the event was registered : {EVENT_DATE}
Event type                                  : {MESSAGE_TYPE}
Source of the event                         : {EVENT_ORIGIN}
]]></entry>
</properties>

16.5 Test mail format information file (testmail.properties)

This file specifies the test email format.

Format

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<comment>Event mail properties</comment>

<!-- Mail subject -->
<entry key="mail_subject">mail-subject</entry>

<!-- Mail header -->
<entry key="mailheader">mail-header</entry>

<!-- Mail footer -->
<entry key="mailfooter">mail-footer</entry>

</properties>

Setting items

The following describes the setting items of the test mail format information file:

Setting item

Description

mail_subject

Specify the email subject name.

mailheader

Specify the email header.

mailfooter

Specify the email footer.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<comment>Event mail properties</comment>

<!-- Mail subject -->
<entry key="mail_subject">JP1/ITDM2 - SDM Test mail</entry>

<!-- Mail header -->
<entry key="mailheader"><![CDATA[Confirm email transmission]]></entry>

<!-- Mail footer -->
<entry key="mailfooter"><![CDATA[--message end--]]></entry>

</properties>

16.6 Communication server environment setting file (CommunicationServerEngine.properties)

This file specifies the operating environment for the communication server.

Format

messaging.server.address = messaging-server-connection-destination-address
messaging.server.port = messaging-server-connection-destination-port-number
request.timeout.time = request-timeout-time
semaphore.wait.timeout.time = semaphore-allocation-timeout-time
ios.battery.inventory.timeout.time = iOS-device-battery-information-collection-interval
detail.debug.log.mode = detailed-trace-log-output-mode

Setting items

The following describes the setting items and specifiable values for the communication server environment setting file:

Setting item

Description

Specifiable value

Initial value

messaging.server.address

Specify the connection destination address for the messaging server.

This item must be specified.

IPv4 address

localhost

messaging.server.port

Specify the connection destination port number for the messaging server.

This item must be specified.

1 to 65535

26078

request.timeout.time

Specify the request timeout time.

0 to 60 (in minutes)

5

semaphore.wait.timeout.time

Specify the semaphore allocation timeout time.

0 to 60 (in minutes)

5

ios.battery.inventory.timeout.time

Specify the interval for collecting iOS device battery information.

1 to 60 (in minutes)

60

detail.debug.log.mode

Specify the detailed trace log output mode.

0

Disabled

1

Enabled

0

Example

messaging.server.address = localhost
messaging.server.port = 9000
request.timeout.time = 5
semaphore.wait.timeout.time = 5
ios.battery.inventory.timeout.time = 60
detail.debug.log.mode = 0

16.7 Messaging server setting file (SdMessagingServer.ini)

This file specifies the operating environment for the messaging server.

Format

[MessagingServer]
HttpPort=Android-device-listen-port-number
HttpAddress=Android-device-listen-IP-address
HttpKeepConnectTime=Android-device-Comet-connection-keep-time
HttpClosePendingTime=Android-device-reconnection-wait-time
HttpMaxConnection=maximum-number-of-Comet-connections-with-Android-devices
ManagePort=communication-server-listen-port-number
ManageAddress=communication-server-listen-IP-address

Setting items

The following describes the setting items and specifiable values for the messaging server setting file:

Setting item

Description

Specifiable value

Initial value

HttpPort

Specify the listen port number used for establishing TCP connections with Android devices.

To change the initial value, if you omit the specification or specify a null string, listen port number 80 is used. Therefore, you must specify this item.

1 to 65535

26079

HttpAddress

Specify the listen IP address used for establishing TCP connections with Android devices.

If you omit the specification or specify a null string, all IP addresses on the local computer are listened.

IPv4 address

None

HttpKeepConnectTime

Specify the time (in seconds) to maintain a Comet connection with an Android device.

A connection that exceeds the specified time is disconnected, and then is reconnected with JP1/ITDM2 - SDM (Smart Device Android Agent).

1 or more (no upper limit; in seconds)

86400

HttpClosePendingTime

Specify the time to wait for a reconnection from the Android device from which a Comet connection was disconnected.

0 to 3600 (in minutes)

60

HttpMaxConnection

Specify the maximum number of simultaneous Comet connections with Android devices.

If a connection request exceeding the specified value is issued, a connection is disconnected immediately after being established.

1 to 30000

10000

ManagePort

Specify the listen port number used for establishing TCP connections with the communication server.

To change the initial value, if you omit the specification or specify a null string, listen port number 9000 is used. Therefore, you must specify this item.

1 to 65535

26078

ManageAddress

Specify the listen IP address used for establishing TCP connections with the communication server. If you omit the specification or specify a null string, all IP addresses on the local computer are listened.

IPv4 address

None

Example

[MessagingServer]
HttpPort=26079
HttpAddress=xxx.xxx.xxx.xxx
HttpKeepConnectTime=86400
HttpClosePendingTime=60
HttpMaxConnection=10000
ManagePort=26078
ManageAddress=xxx.xxx.xxx.xxx

17 Messages

This chapter lists and describes messages output by JP1/ITDM2 - SDM.

17.1 Message format

JP1/ITDM2 - SDM messages consist of a message ID, message type, and message text.

The following shows the format of message IDs and message types, and the meanings of the constituent parts of a message.

Format: KNAFpnnnnn-m

KNAF

Indicate a message output from JP1/ITDM2 - SDM.

p

Indicates the component that output the message. The following table shows the correspondence between the numbers and the components:

Number

Component

0

Installer

1

Smart device manager

2

Communication server

3

Messaging server

4

JP1/ITDM2 - SDM (Smart Device Android Agent)

5

JP1/ITDM2 - SDM (Smart Device iOS Agent)

6

Command

nnnnn

Indicates the message number.

m

Indicates the message type. The following are the message types:

Message code

Type

Description

E

Error

Processing could not continue because an error occurred.

W

Warning

A warning was output, and processing continued. See the warning message to determine whether there is a problem.

I

Information

Processing ended successfully.

17.2 JP1/ITDM2 - SDM (Smart Device Manager) messages output as events

Some JP1/ITDM2 - SDM (Smart Device Manager) messages are output as events, and others are not.

JP1/ITDM2 - SDM (Smart Device Manager) messages output as events

Message ID

Output as event

KNAF100003-E

Y

KNAF100004-W

Y

KNAF100005-W

Y

KNAF120000-I

Y

KNAF120001-W

Y

KNAF120002-W

Y

KNAF120100-I

Y

KNAF120101-E

Y

KNAF120102-I

Y

KNAF120103-E

Y

KNAF120105-E

Y

KNAF120107-E

Y

KNAF120108-I

Y

KNAF120109-W

Y

KNAF120111-E

Y

KNAF120113-E

Y

KNAF120114-W

Y

KNAF120115-W

Y

KNAF120116-I

Y

KNAF120117-E

Y

KNAF120118-I

Y

KNAF120119-I

Y

KNAF120200-I

Y

KNAF120201-E

Y

KNAF120203-E

Y

KNAF120204-I

Y

KNAF120205-E

Y

KNAF120207-E

Y

KNAF120209-E

Y

KNAF120211-E

Y

KNAF120212-I

Y

KNAF120213-W

Y

KNAF120214-I

Y

KNAF120215-W

Y

KNAF120216-I

Y

KNAF120217-W

Y

KNAF120218-I

Y

KNAF120219-W

Y

KNAF120220-I

Y

KNAF120221-W

Y

KNAF120222-I

Y

KNAF120223-W

Y

KNAF120224-I

Y

KNAF120225-I

Y

KNAF120226-W

Y

KNAF120227-I

Y

KNAF120228-W

Y

KNAF120229-I

Y

KNAF120230-W

Y

KNAF120231-I

Y

KNAF120232-W

Y

KNAF120233-I

Y

KNAF120234-W

Y

KNAF120300-I

Y

KNAF120301-E

Y

KNAF120302-I

Y

KNAF120303-E

Y

KNAF120305-E

Y

KNAF120307-E

Y

KNAF120309-E

Y

KNAF120310-I

Y

KNAF120311-E

Y

KNAF120312-I

Y

KNAF120313-E

Y

KNAF120315-E

Y

KNAF120317-E

Y

KNAF120318-I

Y

KNAF120319-E

Y

KNAF120320-I

Y

KNAF120321-E

Y

KNAF120323-E

Y

KNAF120325-E

Y

KNAF120326-I

Y

KNAF120327-E

Y

KNAF120328-I

Y

KNAF120329-E

Y

KNAF120331-E

Y

KNAF120332-I

Y

KNAF120333-E

Y

KNAF120401-E

Y

KNAF120403-E

Y

KNAF120405-E

Y

KNAF120407-E

Y

KNAF120409-E

Y

KNAF120411-E

Y

KNAF120501-E

Y

KNAF120503-E

Y

KNAF120505-E

Y

KNAF120507-E

Y

KNAF120509-E

Y

KNAF120511-E

Y

KNAF120513-E

Y

KNAF120515-E

Y

KNAF120517-E

Y

KNAF120519-E

Y

KNAF120521-E

Y

KNAF120523-E

Y

KNAF120524-E

Y

KNAF120526-E

Y

KNAF120528-E

Y

KNAF120530-E

Y

KNAF120531-E

Y

KNAF120533-E

Y

KNAF120535-E

Y

KNAF120537-E

Y

KNAF120539-E

Y

KNAF120541-E

Y

KNAF120543-E

Y

KNAF120545-E

Y

KNAF120547-E

Y

KNAF120600-I

Y

KNAF120601-E

Y

KNAF120602-I

Y

KNAF120603-E

Y

KNAF120607-E

Y

KNAF120700-I

Y

KNAF120701-E

Y

KNAF120702-I

Y

KNAF120703-E

Y

KNAF120707-E

Y

KNAF120900-I

Y

KNAF120901-E

Y

KNAF120902-I

Y

KNAF120903-E

Y

KNAF120907-E

Y

KNAF120908-I

Y

KNAF120909-E

Y

KNAF121000-I

Y

KNAF121001-E

Y

KNAF121003-E

Y

KNAF121005-E

Y

KNAF121006-I

Y

KNAF121007-E

Y

KNAF121009-E

Y

KNAF121011-E

Y

KNAF121013-E

Y

KNAF121015-E

Y

KNAF121017-E

Y

KNAF121019-E

Y

KNAF121021-E

Y

KNAF121023-E

Y

KNAF121024-I

Y

KNAF121025-E

Y

KNAF121026-I

Y

KNAF121027-E

Y

KNAF121028-I

Y

KNAF121029-E

Y

KNAF121030-I

Y

KNAF121031-E

Y

KNAF121033-E

Y

KNAF130000-I

Y

KNAF130001-E

Y

KNAF130002-I

Y

KNAF130003-E

Y

KNAF130004-I

Y

KNAF130005-E

Y

KNAF130008-I

Y

KNAF130009-E

Y

KNAF130012-I

Y

KNAF130013-E

Y

KNAF130016-I

Y

KNAF130017-E

Y

KNAF130018-I

Y

KNAF130019-W

Y

KNAF130024-I

Y

KNAF130025-E

Y

KNAF130026-I

Y

KNAF130027-W

Y

KNAF130028-I

Y

KNAF130029-W

Y

KNAF130030-W

Y

KNAF130031-I

Y

KNAF130032-W

Y

KNAF130033-W

Y

KNAF130037-I

Y

KNAF130038-I

Y

KNAF130039-W

Y

KNAF130040-I

Y

KNAF130041-I

Y

KNAF130043-W

Y

KNAF130044-W

Y

KNAF130045-W

Y

KNAF130046-W

Y

KNAF130047-W

Y

KNAF130048-W

Y

KNAF130051-W

Y

KNAF130056-I

Y

KNAF130057-E

Y

KNAF130060-I

Y

KNAF130061-W

Y

KNAF130062-I

Y

KNAF130063-W

Y

KNAF130064-W

Y

KNAF130065-I

Y

KNAF130066-W

Y

KNAF130067-I

Y

KNAF130068-W

Y

KNAF130069-I

Y

KNAF130070-W

Y

KNAF130071-I

Y

KNAF130072-W

Y

KNAF130073-I

Y

KNAF130074-W

Y

KNAF130075-I

Y

KNAF130076-W

Y

KNAF190001-I

--

KNAF190002-I

--

KNAF190003-I

--

KNAF190004-E

--

KNAF190005-E

--

KNAF190006-I

--

KNAF190007-I

--

KNAF190008-E

--

KNAF190009-E

--

Legend:

Y: Output

---: Not output

17.3 List of JP1/ITDM2 - SDM (Smart Device Manager) messages

The following lists and describes JP1/ITDM2 - SDM (Smart Device Manager) messages.

KNAF100003-E

Failed to generate an instance. error-description (instance-name)

[Cause] The system failed to generate an instance.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF100004-W

Failed to connect to the communication server.

[Cause] The system failed to connect to the communication server.

[Action] Cancels the connection.

[Workaround] Verify that the communication server is running.

Verify that the communicationserverurl value in the file manager.properties is configured properly.

Verify that the root certificate required for connection is specified.

KNAF100005-W

Failed to send a test email message.

[Cause] The system failed to send a test email message.

[Action] Cancels email notification.

[Workaround] Check and, if necessary, revise the settings in the file testmail.properties, or verify that the destination SMTP server is specified properly.

KNAF120000-I

A change in manager.properties was detected. key-of-the-changed-value:[value-before-the-change]->[value-after-the-change]

KNAF120001-W

Some items in manager.properties are not defined.

item-name

[Cause] Some required definition items in manager.properties are not defined.

[Action] Cancels the execution.

[Workaround] Add necessary definitions, and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

KNAF120002-W

The definition file contains incorrect settings. file-name: item-name

[Cause] Items in the definition file have incorrect values.

[Action] Discards the settings in the definition file and continues the processing.

[Workaround] Check and, if necessary, revise the settings in the definition file, and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

KNAF120100-I

A user account was created. User ID = user-ID

KNAF120101-E

Failed to create a user account. User ID = user-ID

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120102-I

A user account was deleted. User ID = user-ID

KNAF120103-E

Failed to delete a user account. User ID = user-ID

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120105-E

Failed to obtain the number of user accounts.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120107-E

Failed to obtain user account information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120108-I

The login was successful. User ID = user-ID

KNAF120109-W

The login failed. User ID = user-ID

[Cause]

- The user ID or password is not correct.

- The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround]

- Enter the correct user ID and password, and then try logging in again.

- Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120111-E

Failed to obtain role information. User ID = user-ID

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120113-E

Failed to obtain the list of user accounts.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120114-W

Multiple attempts to log in failed.

[Cause] The specified maximum number of login attempts was exceeded.

[Action] Cancels the execution.

[Workaround] Enter the correct user ID and password, or contact and ask the administrator to create a user.

KNAF120115-W

A user account was locked. User ID = user-ID

[Cause] The user account was locked.

[Action] Cancels the execution.

[Workaround] Contact and ask a user with administrator privileges to unlock the locked user account.

If all users with administrator privileges are locked, restart the service (JP1/ITDM2 - Smart Device Manager Server Service) to unlock the users.

KNAF120116-I

A user account was changed. User ID = user-ID

KNAF120117-E

Failed to change a user account. User ID = user-ID

[Cause]

- The password is not correct, or the same password as the current password was entered for the new password.

- The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround]

- Specify the correct password, or provide a new password different from the current one.

- Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120118-I

A user account was unlocked. User ID = user-ID

KNAF120119-I

You have logged out. User ID = user-ID

KNAF120200-I

A smart device was imported.

KNAF120201-E

Failed to import a smart device. Error line number: line-number

[Cause] The system failed to import smart device information.

[Action] Cancels the execution.

[Workaround] Remove the error that occurred at the line for the specified number in the file, and then retry the import.

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120203-E

Failed to export smart device information. error-description

[Cause] The system failed to export smart device information.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120204-I

A smart device was deleted. name

KNAF120205-E

Failed to delete a smart device. name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120207-E

Failed to obtain the number of smart devices.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120209-E

Failed to obtain the differences from the previous day.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120211-E

Failed to obtain smart device information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120212-I

The latest information was requested.

KNAF120213-W

Failed to request the latest information.

[Cause] The system failed to collect the latest information.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120214-I

An initialization request was made.

KNAF120215-W

An initialization request failed.

[Cause] An initialization request failed.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120216-I

A device was instructed to lock itself.

KNAF120217-W

Failed to instruct a device to lock itself.

[Cause] Lock instructions failed.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120218-I

A device was instructed to lock itself and to update its password.

KNAF120219-W

Failed to instruct a device to lock itself and to update its password.

[Cause] The system failed to instruct a device to lock itself and to update its password.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120220-I

A device was instructed to reset its passcode.

KNAF120221-W

Failed to instruct a device to reset its passcode.

[Cause] The system failed to instruct a device to reset its passcode.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120222-I

Logs were requested.

KNAF120223-W

Failed to request logs.

[Cause] The system failed to request logs.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120224-I

A device was set as an unmanaged device.

KNAF120225-I

A device was forcibly set as an unmanaged device.

KNAF120226-W

Failed to set a device as an unmanaged device.

[Cause] The system failed to set a device as an unmanaged device.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of service range or is not connected via Wi-Fi, the system cannot access the device. If the system cannot access the smart device because it failed or was lost, select the "Forcibly set to unmanaged" check box.

KNAF120227-I

A security policy was applied. Policy name: policy-name

KNAF120228-W

Failed to apply a security policy. Policy name: policy-name

[Cause] The system failed to apply a security policy.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120229-I

A request to apply an Android policy was made. Policy name: policy-name

KNAF120230-W

A request to apply an Android policy failed. Policy name: policy-name

[Cause] The system failed to apply an Android policy.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120231-I

A request to apply an iOS profile was made. Profile name: profile-name

KNAF120232-W

A request to apply an iOS profile failed. Profile name: profile-name

[Cause] The system failed to apply an iOS profile.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120233-I

A message was sent.

KNAF120234-W

Failed to send a message.

[Cause] A message transfer failed.

[Action] Cancels the execution.

[Workaround] Make sure that the target smart device is connected to the network. If the smart device is out of the service range or is not connected via Wi-Fi, the system cannot access the device.

KNAF120300-I

A security policy was created. Policy name: policy-name

KNAF120301-E

Failed to create a security policy. Policy name: policy-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120302-I

A security policy was removed. Policy name: policy-name

KNAF120303-E

Failed to remove a security policy. Policy name: policy-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120305-E

Failed to obtain security policy information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120307-E

Failed to obtain the number of security policies.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120309-E

Failed to obtain the phone number list in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120310-I

A phone number was added to a security policy or changed in a security policy.

KNAF120311-E

Failed to add a phone number to a security policy or change it in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120312-I

A phone number was removed from a security policy.

KNAF120313-E

Failed to remove a phone number from a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120315-E

Failed to obtain the number of registered phone numbers in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120317-E

Failed to obtain the URL list in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120318-I

A URL was added to, or changed in, a security policy.

KNAF120319-E

Failed to add a URL to a security policy, or failed to change it in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120320-I

A URL was removed from a security policy.

KNAF120321-E

Failed to remove a URL from a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120323-E

Failed to obtain the number of registered URLs in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120325-E

Failed to obtain the application list in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120326-I

An application was added to, or changed in, a security policy.

KNAF120327-E

Failed to add an application to, or failed to change an application in, a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120328-I

An application was removed from a security policy.

KNAF120329-E

Failed to remove an application from a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120331-E

Failed to obtain the number of registered applications in a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120332-I

A security policy was changed.

KNAF120333-E

Failed to change a security policy.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120401-E

An event was deleted.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120403-E

Failed to export a list of events.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120405-E

Failed to obtain the number of events.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120407-E

Failed to obtain a list of event information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120409-E

Failed to add or change event information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120411-E

Failed to obtain an alert level.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120501-E

Failed to update inventory information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120503-E

Failed to delete inventory information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120505-E

Failed to update call history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120507-E

Failed to obtain call history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120509-E

Failed to obtain the number of records of call history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120511-E

Failed to update URL browsing history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120513-E

Failed to obtain URL browsing history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120515-E

Failed to obtain the number of records of URL browsing history.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120517-E

Failed to create information about installed applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120519-E

Failed to obtain the number of records of information about installed applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120521-E

Failed to obtain a list of information about installed applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120523-E

Failed to create information about running applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120524-E

Failed to delete information about running applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120526-E

Failed to obtain the number of records of information about running applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120528-E

Failed to obtain a list of information about running applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120530-E

Failed to create information about running services.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120531-E

Failed to delete information about running services.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120533-E

Failed to obtain the number of records of information about running services.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120535-E

Failed to obtain a list of information about running services.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120537-E

Failed to create GPS history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120539-E

Failed to obtain the number of records of GPS history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120541-E

Failed to obtain a list of GPS history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120543-E

Failed to create Bluetooth history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120545-E

Failed to obtain the number of records of Bluetooth history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120547-E

Failed to obtain a list of Bluetooth history information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120600-I

Provisioning information for Android was created.

KNAF120601-E

Failed to create provisioning information for Android.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120602-I

Provisioning information for Android was deleted.

KNAF120603-E

Failed to delete provisioning information for Android.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120607-E

Failed to obtain a list of provisioning information for Android.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120700-I

Provisioning information for iOS was created.

KNAF120701-E

Failed to create provisioning information for iOS.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120702-I

Provisioning information for iOS was deleted.

KNAF120703-E

Failed to delete provisioning information for iOS.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120707-E

Failed to obtain a list of provisioning information for iOS.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120900-I

Policy profile information was created.

KNAF120901-E

Failed to create policy profile information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120902-I

Policy profile information was deleted.

KNAF120903-E

Failed to delete policy profile information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120907-E

Failed to obtain a list of policy profile information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF120908-I

Policy profile information was changed.

KNAF120909-E

Failed to change policy profile information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121000-I

A distributed application was removed. Application name: application-name

KNAF121001-E

Failed to remove a distributed application. Application name: application-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121003-E

Failed to obtain the number of distributed applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121005-E

Failed to obtain distributed application information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121006-I

A distributed application was added. Application name: application-name

KNAF121007-E

Failed to add a distributed application. Application name: application-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121009-E

Failed to delete the state of a distributed application. application-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121011-E

Failed to obtain the number of states of distributed applications.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121013-E

Failed to obtain state information about a distributed application.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121015-E

Failed to add the state information about a distributed application. application-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121017-E

Failed to delete application data. Application name: application-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121019-E

Failed to obtain the number of application data records.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121021-E

Failed to obtain application data information.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121023-E

Failed to register application data information. Application name: application-name

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121024-I

An application was distributed.

KNAF121025-E

Failed to distribute an application.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121026-I

A request to install an application was made.

KNAF121027-E

A request to install an application failed.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121028-I

A request to remove an application was made.

KNAF121029-E

A request to remove an application failed.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121030-I

A distributed application was changed.

KNAF121031-E

Failed to register a distributed application.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF121033-E

Failed to change the state information about a distributed application.

[Cause] The database service (JP1/ITDM2 - Smart Device Manager (DB Service)) is not running.

[Action] Cancels the execution.

[Workaround] Start the database service (JP1/ITDM2 - Smart Device Manager (DB Service)), and then restart the service (JP1/ITDM2 - Smart Device Manager Server Service).

If the problem persists, collect troubleshooting information, and then contact customer support.

KNAF130000-I

Detailed information was updated.

KNAF130001-E

Failed to update detailed information.

[Cause] The system failed to update detailed information.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130002-I

Bluetooth connection information was updated.

KNAF130003-E

Failed to update Bluetooth connection information.

[Cause] The system failed to update Bluetooth connection information.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130004-I

Security of the call history was validated.

KNAF130005-E

Failed to validate the security of the call history.

[Cause] The system failed to validate the security of the call history.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130008-I

Security of application information was validated.

KNAF130009-E

Failed to validate the security of application information.

[Cause] The system failed to validate the security of application information.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130012-I

Security of the Web browsing history was validated.

KNAF130013-E

Failed to validate the security of the Web browsing history.

[Cause] The system failed to validate the security of the Web browsing history.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130016-I

Information for which the retention period expired was deleted.

KNAF130017-E

Failed to delete information for which the retention period expired.

[Cause] The system failed to delete information for which the retention period expired.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130018-I

The severity management table was updated.

KNAF130019-W

Failed to update the severity management table.

[Cause] The system failed to update the severity management table.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130024-I

The security policy of detailed information was validated.

KNAF130025-E

Failed to validate the security policy of detailed information.

[Cause] The system failed to validate the security policy of detailed information.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130026-I

A call was made to an authorized phone number. Phone number: phone-number

KNAF130027-W

A call was made to an unauthorized phone number. Phone number: phone-number

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130028-I

Installation is allowed. Application name: application-name

KNAF130029-W

Installation is prohibited. Application name: application-name

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130030-W

An application which is not in the security list has been installed. Application name: application-name

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130031-I

Site browsing is allowed. URL: URL

KNAF130032-W

Site browsing is prohibited. URL: URL

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130033-W

You are browsing a website which is not in the security list.

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130037-I

An application was installed.

KNAF130038-I

An application was uninstalled.

KNAF130039-W

A connection to a new Bluetooth device was established. Device name: device-name

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130040-I

A connection to a Bluetooth device was removed. Device name: device-name

KNAF130041-I

Detailed information was updated.

KNAF130043-W

IMEI/MEID information was changed. Changed from: changed-from Changed to: changed-to

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130044-W

OS version information was changed. Changed from: changed-from Changed to: changed-to

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130045-W

ICCID information was changed. Changed from: changed-from Changed to: changed-to

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130046-W

An SD card is being used.

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130047-W

GPS power is off.

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130048-W

The device remains locked for a certain period of time.

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130051-W

A required application is not installed. Application name: application-name

[Cause] A violation was found during the validation of the security policy.

[Action] Continues the process.

[Workaround] Take action according to the applicable security policy.

KNAF130056-I

The number of managed smart devices was updated.

KNAF130057-E

Failed to update the number of managed smart devices.

[Cause] The system failed to update the number of managed smart devices.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130060-I

An email notification of event information was sent.

KNAF130061-W

Failed to send an email notification of event information.

[Cause] The system failed to send an email notification of event information.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF130062-I

The latest information was obtained.

KNAF130063-W

Failed to obtain the latest information.

[Cause] The system failed to obtain the latest information.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130064-W

Initialization failed.

[Cause] Initialization processing failed.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130065-I

The device was locked.

KNAF130066-W

Failed to lock a device.

[Cause] The system failed to lock a device.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130067-I

A passcode was reset.

KNAF130068-W

Failed to reset a passcode.

[Cause] The system failed to reset a passcode.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130069-I

The log was obtained.

KNAF130070-W

Failed to obtain the log.

[Cause] The system failed to obtain the log.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130071-I

A device was set as an unmanaged device.

KNAF130072-W

Failed to set a device as an unmanaged device.

[Cause] The system failed to set a device as an unmanaged device.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130073-I

An Android policy was applied.

KNAF130074-W

Failed to apply an Android policy.

[Cause] The system failed to apply an Android policy.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF130075-I

An iOS profile was applied.

KNAF130076-W

Failed to apply an iOS profile.

[Cause] The system failed to apply an iOS profile.

[Action] Continues the process.

[Workaround] The request might have failed because the smart device was out of service range or has no Wi-Fi connection. Wait a while, and then try again.

KNAF190001-I

The JP1/ITDM2 - Smart Device Manager Server Service service will now start.

KNAF190002-I

The JP1/ITDM2 - Smart Device Manager Server Service service will now stop.

KNAF190003-I

The system will now stop.

KNAF190004-E

A system error occurred. (message-description)

[Cause] A system error occurred.

[Action] Stops the service.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF190005-E

Failed to start the JP1/ITDM2 - Smart Device Manager Server Service service.

[Cause] Service startup failed.

[Action] Stops the service.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF190006-I

The JP1/ITDM2 - Smart Device Manager Server Service service was registered.

KNAF190007-I

The JP1/ITDM2 - Smart Device Manager Server Service service was removed.

KNAF190008-E

Failed to register the JP1/ITDM2 - Smart Device Manager Server Service service.

[Cause] Registration of the service to Windows services failed.

[Action] Cancels installation.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF190009-E

Failed to remove the JP1/ITDM2 - Smart Device Manager Server Service service.

[Cause] Removal of the service from Windows services failed.

[Action] Cancels uninstallation.

[Workaround] Collect troubleshooting information, and then contact customer support.

17.4 List of JP1/ITDM2 - SDM (Messaging Server) messages

The following lists and describes JP1/ITDM2 - SDM (Messaging Server) messages.

KNAF300001-I

The JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service will now start.

KNAF300002-I

The JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service will now stop.

KNAF300003-I

The system will now stop.

KNAF300004-E

A system error occurred. (message-description)

[Cause] A system error occurred.

[Action] Stops the service.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF300005-E

Failed to start the JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service.

[Cause] Service startup failed.

[Action] Stops the service.

[Workaround] Collect the troubleshooting information, and then contact customer support.

KNAF300006-I

The JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service was registered.

KNAF300007-I

The JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service was removed.

KNAF300008-E

Failed to register the JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service.

[Cause] Registration of the service to Windows services failed.

[Action] Cancels installation.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF300009-E

Failed to remove the JP1/ITDM2 - Smart Device Manager (Messaging Server Service) service.

[Cause] Removal of the service from Windows services failed.

[Action] Cancels uninstallation.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF300201-E

The server address is invalid.

[Cause] Either the communication server defined in the configuration file or the address on standby for connection from the agent is invalid.

[Action] Stops the service.

[Workaround] Make sure the values defined in the configuration file are correct. If the problem persists, collect the troubleshooting information, and then contact customer support.

KNAF300202-E

An error occurred in the communication with the smart device agent. (WinSock-error-code)

[Cause] An error occurred in the communication with the smart device agent.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF300203-I

Standby for the server port started. (IP address = IP-address, port number: port-number)

KNAF300204-I

Standby for the server port ended. (IP address = IP-address, port number: port-number)

KNAF300205-I

Connection with the smart device agent will now start. (IP address = IP-address, port number: port-number)

KNAF300206-I

Connection with the smart device agent is freed (device-ID).

KNAF300207-E

The length of the received data exceeded the maximum size. (socket-ID)

[Cause] The length of the received data exceeded the maximum size.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF300208-E

The maximum number of simultaneous connections was exceeded.

[Cause] The number of simultaneous connections with the smart device agent was exceeded.

[Action] Continues the process.

[Workaround] Make sure the values defined in the configuration file are correct. If the problem persists, collect the troubleshooting information, and then contact customer support.

KNAF300209-E

An error occurred in the communication with the communication server. (WinSock-error-code)

[Cause] An error occurred in the communication with the communication server.

[Action] Continues the process.

[Workaround] Collect troubleshooting information, and then contact customer support.

KNAF300210-E

An error occurred in the server socket. (WinSock-error-code)

[Cause] A communication error occurred.

[Action] Stops the service when an error occurred in the starting process, but in other case continues process.

[Workaround] Make sure the values defined in the configuration file are correct. If the problem persists, collect the troubleshooting information, and then contact customer support.

KNAF300211-W

The smart device agent to which data was to be sent (device-ID) has already been disconnected.

[Cause] The smart device agent is not connected.

[Action] Continues the process.

[Workaround] Check the boot status and communication status of the smart device agent.

KNAF300212-I

Connection to the smart device agent (device-ID) was established.

KNAF300213-E

Failed to read the configuration file (file-name).

[Cause] Failed to get a path of the configuration file.

[Action] Continues the process.

[Workaround] Collect the troubleshooting information, and then contact customer support.

KNAF300214-W

The smart device agent for which processing was requested (device-ID) is not connected.

[Cause] The smart device agent is not connected.

[Action] Continues the process.

[Workaround] Check the boot status and communication status of the smart device agent.

KNAF300215-I

A request for connection with the smart device agent (device-ID) will now be sent.

KNAF300216-I

A request for log transmission from the smart device agent (device-ID) will now be sent.

KNAF300217-E

Failed to request processing from the smart device agent.

[Cause] An error occurred in the communication with the smart device agent.

[Action] Continues the process.

[Workaround] Check the boot status and communication status of the smart device agent.

KNAF300218-I

A message notification will now be sent to the smart device agent (device-ID).

17.5 List of command messages

The following lists and describes command messages.

KNAF600001-I

The command ended normally. (command = command-name)

KNAF600002-E

The command ended abnormally. (command = command-name, return value = return-value)

[Cause] The command ended abnormally.

[Action] Cancels the execution.

[Workaround] Check the return value of the command and take appropriate action, and then re-execute the command.

Appendixes

A. List of folders

This appendix describes the folders that are created during installation of components.

A.1 Folders created on the smart device manager

The following tables list and describe the folders that are created on the smart device manager during installation of JP1/ITDM2 - SDM (Smart Device Manager).

Folders created during installation of JP1/ITDM2 - SDM (Smart Device Manager)

Folder name

Description

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder

JP1/ITDM2 - SDM (Smart Device Manager) data folder

Default: %Program Files%\Hitachi\jp1itdm2sdm

%WINDIR%\Temp\SDMINST

Folder for log files which are output during installation

Folders created under the installation folder

Folder name

Description

log\

Folder for log files which are output during installation

mgr\

Root folder for the smart device manager

mgr\bin

Executable file folder

mgr\backup

Default backup folder

mgr\conf\

Environment definition file folder

mgr\db\

Database installation folder

mgr\log\

Trace log folder

mgr\temp

Temporary data folder

mgr\troubleshoot\

Default troubleshooting information folder

mgr\uC\

Application server installation folder

Folders created during installation of JP1/ITDM2 - SDM (Smart Device Manager) (other than the installation folder)

Folder name

Description

%Program Files%\Hitachi\HNTRLib2\

Trace library installation folder

All-User-profile-application-data-folder\Hitachi\jp1itdm2sdm\Database\#

JP1/ITDM2 - SDM (Smart Device Manager) data folder

program-menu-of-the-system\JP1_IT Desktop Management2 - Smart Device Manager

Program folder

#: This folder name is set by default when the product is provided. The folder is created during setup.

A.2 Folders created on the communication server

The following tables list and describe the folders that are created on the communication server during installation of JP1/ITDM2 - SDM (Communication Server).

Folders created during installation of JP1/ITDM2 - SDM (Communication Server)

Folder name

Description

JP1/ITDM2 - SDM (Communication Server)-installation-folder

JP1/ITDM2 - SDM (Communication Server) data folder.

Default: %Program Files%\Hitachi\jp1itdm2sdm

%WINDIR%\Temp\SDMINST

Folder for log files which are output during installation

Folders created under the installation folder

Folder name

Description

log\

Folder for log files which are output during installation

cms\

Root folder for the communication server

cms\bin

Executable file folder

cms\conf\

Environment definition file folder

cms\log\

Trace log folder

cms\troubleshoot\

Default troubleshooting information folder

cms\uC\

Application server installation folder

A.3 Folders created on the messaging server

The following tables list and describe the folders that are created on the messaging server during installation of JP1/ITDM2 - SDM (Messaging Server).

Folders created during installation of JP1/ITDM2 - SDM (Messaging Server)

Folder name

Description

JP1/ITDM2 - SDM (Messaging Server)-installation-folder

JP1/ITDM2 - SDM (Messaging Server) data folder.

Default: %Program Files%\Hitachi\jp1itdm2sdm

%WINDIR%\Temp\SDMINST

Folder for log files which are output during installation

Folders created under the installation folder

Folder name

Description

log\

Folder for log files which are output during installation

mss\

Root folder for the messaging server

mss\bin\

Executable file folder

mss\conf\

Environment definition file folder

mss\log\

Trace log folder

mss\troubleshoot\

Default troubleshooting information folder

B. List of services and processes

This appendix describes the services and processes of JP1/ITDM2 - SDM.

B.1 List of services

For each server, this section shows JP1/ITDM2 - SDM service names, corresponding service process names, and service descriptions, and indicates whether a service starts automatically.

Smart device manager

Service name

Service display name

Service process name

Description

Automatic startup of the service

JP1_ITDM2_SDM_MGRSVR

JP1/ITDM2 - Smart Device Manager Server Service

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\bin\SdManagerServer.exe

Smart device manager service

Yes

HiRDBEmbeddedEdition_IS1

JP1/ITDM2 - Smart Device Manager (DB Service)

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\db\BIN\pdservice.exe

Smart device manager database service

Yes

JP1_ITDM2_SDM_WEBSVR

JP1/ITDM2 - Smart Device Manager Web Server

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC\httpsd\httpsd.exe

Web server service

Yes

Legend:

Yes: The service starts automatically

Communication server

Service name

Service display name

Service process name

Description

Automatic startup of the service

JP1_ITDM2_SDM_COMSVR

JP1/ITDM2 - Smart Device Manager (Communication Server Service)

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\bin\SdCommunicationServer.exe

Communication server service

Yes

JP1_ITDM2_SDM_WEBSVR

JP1/ITDM2 - Smart Device Manager Web Server

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC\httpsd\httpsd.exe

Web server service

No

Legend:

Yes: The service starts automatically

No: Does not start automatically

Messaging server

Service name

Service display name

Service process name

Description

Automatic startup of the service

JP1_ITDM2_SDM_MSGSVR

JP1/ITDM2 - Smart Device Manager (Messaging Server Service)

JP1/ITDM2 - SDM (Messaging Server)-installation-folder\mss\bin\SdMessagingServer.exe

Messaging server service

Yes

Legend:

Yes: The service starts automatically

B.2 List of processes

This section lists and describes the functions of JP1/ITDM2 - SDM processes for each server.

Smart device manager

Process name

Function

Whether the process is resident

cjstartsv.exe

Application server process

Yes

SdManagerServer.exe

Service process

Yes

pdxxx.exe#

Database processes

Yes

httpsd.exe

Web server function process

No

Legend:

Yes: The process is resident.

No: The process is not resident.

#: xxx is a character string that contains 3 to 8 characters.

Communication server

Process name

Function

Whether the process is resident

cjstartsv.exe

Application server process

Yes

SdCommunicationServer.exe

Service process

Yes

httpsd.exe

Web server function process

Yes

Legend:

Yes: The process is resident.

Messaging server

Process name

Function

Whether the process is resident

SdMessagingServer.exe

Service process

Yes

Legend:

Yes: The process is resident.

C. Port number list

This appendix lists and describes the port numbers used in JP1/ITDM2 - SDM for each server.

Smart device manager

Port number

Connection direction

Connected to

[port number]

Protocol

Use

26080

<-

Administrator's computer

[ephemeral]

TCP

Used for communication from the administrator's computer to the smart device manager for operating and viewing program modules

26055

<-

ITDM2 management server

TCP

Hitachi Web Server HTTPS port used for SSL communication with the ITDM2 management server

26056

<-

Smart device manager

[ephemeral]

TCP

Used to receive requests for internal communication when the sdmioutils command is executed

26057

<-

ITDM2 management server

TCP

Used for HTTP communication with the ITDM2 management server

26065

<-

Smart device manager

[ephemeral]

TCP

Used by J2EE applications in the smart device manager to receive RMI registry requests

26053

<-

Smart device manager

[ephemeral]

TCP

Used by J2EE applications in the smart device manager to receive requests from the in-process HTTP server

26052

<-

Smart device manager

[ephemeral]

TCP

Used for management communication by J2EE applications in the smart device manager

26066

<-

Smart device manager

[ephemeral]

TCP

Used for communication with the database configured in the smart device manager

26067

<-

Communication server

[26068-26077]

TCP

Used for communication with the database configured in the smart device manager

Communication server

Port number

Connection direction

Connected to

[port number]

Protocol

Use

26055

<-

Smart device manager

[ephemeral]

TCP

Hitachi Web Server HTTPS port number for SSL communication

<-

JP1/ITDM2 - SDM (Smart Device Android Agent)

[ephemeral]

TCP

<-

JP1/ITDM2 - SDM (Smart Device iOS Agent)

[ephemeral]

TCP

26065

<-

Communication server

[ephemeral]

TCP

Used by J2EE applications in the communication server to receive RMI registry requests

26053

<-

Communication server

[ephemeral]

TCP

Used by J2EE applications in the communication server to receive requests from the Web server (redirector)

26052

<-

Communication server

[ephemeral]

TCP

Used for management communication by J2EE applications in the communication server

26068-26077

<-

Smart device manager

[26067]

TCP

Used for communication with the database configured in the smart device manager

Messaging server

Port number

Connection direction

Connected to

[port number]

Protocol

Use

26078

<-

Communication server

[ephemeral]

TCP

Used to send requests from the communication server to the messaging server

26079

<-

JP1/ITDM2 - SDM (Smart Device Android Agent)

[ephemeral]

TCP

Used for Comet connection with JP1/ITDM2 - SDM (Smart Device Android Agent)

D. Lists of parameters

This appendix describes the parameters for each setting.

D.1 User account parameters

The following table lists and describes the parameters in the Account Management view.

User account parameters

Item

Description

Specifiable values

Default

User ID

Specify the user ID of the user account used to log in to JP1/ITDM2 - SDM (Smart Device Manager)

Character string of 8-50 half-width characters#1

(Blank)

Password

Specify the password for the user ID.

Character string of 8-20 half-width characters#1 #2

(Blank)

Re-enter Password

Enter the password again.

Character string of 8-20 half-width characters#1 #2

(Blank)

User Name

Specify the user account name.

Character string of 20 or fewer full- or half-width characters

(Blank)

Email

Specify the email address of the user account user.

Email character string of 100 or fewer characters

(Blank)

Description

Enter a description of the user account.

Character string of 1,000 or fewer half-width characters

(Blank)

Permission

Specify whether to assign the system administrator permission to the user account.

Selected

The system administrator permission is assigned.

Not selected

The system administrator permission is not assigned.

Not selected

Status

The user account can be unlocked if it has been locked.

Enabled

Disabled

Disabled#3

#1: You can use ASCII characters other than ASCII control characters.

#2: To change the password, specify a character string that is different from the current password.

#3: Displayed only when the user account has been locked.

D.2 Event notification parameters

The following tables list and describe the parameters in the Event Notifications view.

Select the category and severity of events about which you want to be notified by email:

Item

Description

Specifiable values

Default

Critical

Select the check box to send notification emails for all types of events whose severity is Critical.

Selected

Event notification emails are sent.

Not selected

Event notification emails are not sent.

Not selected

Warning

Select the check box to send notification emails for all types of events whose severity is Warning.

Information

Select the check box to send notification emails for all types of events whose severity is Information.

Security

Select the check box to send notification emails for events related to security management, such as a change or allocation of a security policy, and results of security policy judgment.

Selected

Notification emails for the selected events.

Not selected

Event notification emails are not sent.

Not selected

Suspicious Operations

Select the check box to send notification emails for events related to suspicious operations, such as the detection of a call to a disallowed phone number, or browsing of a disallowed Web site.

Smart Device

Select the check box to send notification emails for events related to smart devices, such as addition and removal of smart devices.

Distribution

Select the check box to send notification emails for events related to distribution, such as addition and removal of distributed applications, and distribution of applications.

Settings

Select the check box to send notification emails for events related to settings, such as user account management and event notification settings.

Error

Set events related to errors that occur in functions.

Specify event notifications to be ignored:

Item

Description

Specifiable values

Default

Event Number

Select the check box for the event number for which you do not want to send notification email.

Selected

The event is not notified.

Not selected

The event is notified.

Not selected

Select recipients:

Item

Description

Specifiable values

Default

User ID

Select the check box for the user ID to which you want to send event notification emails. If an email address is not set, use the Edit User Account dialog box to set the email address.

Selected

Event notification emails are sent to the user.

Not selected

Event notification emails are not sent to the user.

Not selected

Interval of notification

Item

Description

Specifiable values

Default

Interval of notification (minutes)

Specify the interval (minutes) at which notification emails are sent.

1 to 1440

30

Related Topics

6.3 Editing another administrator's user account

D.3 Mail server parameters

The following table lists and describes the parameters in the SMTP Server view.

Mail server parameters

Item

Description

Specifiable values

Default

Host name

Enter the host name of the SMTP server.

The host name of the SMTP server

(Blank)

Secure connection

Select the security protection used for communication with the SMTP server.

Plain

SSL

TLS

Plain

Port

Specify the port number of the SMTP sever.

1 to 65535

25

Source email

Specify the source email address of notification emails.

Email character string

(Blank)

Use Authentication

Select to use the user authentication function (SMTP Authentication) on the SMTP server.

Selected

SMTP authentication is used.

Not selected

SMTP authentication is not used.

Not selected

User ID

Enter the user ID used for user authentication.

User ID used for user authentication

(Blank)

Password

Specify the password for the user ID.

Password for the user ID

(Blank)

Re-enter Password

Enter the password again for confirmation.

Password for confirmation

(Blank)

E. Output Format of Imported and Exported Files

This appendix describes the output format of imported or exported files.

E.1 Format of exported or imported smart device list CSV file

The following table describes the format of an exported or imported smart device list CSV file.

Format of an exported or imported smart device list CSV file

Item#1

Description

Specifiable values

Maximum number of bytes#2

Imported?

Name

Name such as an asset management number

--

128

Y

OS type

OS information acquired from the smart device

0: iOS

1: Android

1

Y

IMEI/MEID

IMEI/MEID acquired from the smart device

15 digits

15

N

Phone number

Phone number of the smart device from which the information is acquired

Maximum of 20 characters

Only numbers can be specified, excluding a hyphen (-).

20

N

Status

Management status in the product

0: Unmanaged

1: Managed

1

N

Current security policy

Name of the security policy applied to the smart device

--

36

Y#3

Current Android policy/iOS profile

Android policy or iOS profile applied to the smart device

--

36

Y#3

Department

Department to which the user belongs

--

128

Y#4

Account

Account of the user

--

128

Y#4

User name

Name of the user

--

128

Y#4

Last modified date/Time

Date and time that the information was last modified due to registration of a smart device or import of smart device information

yyyy/MM/dd hh:mm:ss#5

19

N

Manufacturer

Manufacturer name acquired from the smart device

--

256

N

Model number

Model number acquired from the smart device

--

256

N

Protocol version

Protocol version of the product

--

64

N

Language

Language setting acquired from the smart device

Maximum of 20 characters

80

N

Product name

Product name acquired from the smart device

Maximum of 10 characters

Android

iOS

40

N

Model name

Model name acquired from the smart device

--

256

N

Serial number

Serial number acquired from the smart device

--

256

N

OS version

OS version acquired from the smart device

--

32

N

OEM name

OEM name acquired from the smart device

--

64

N

Firmware version

Firmware version acquired from the smart device

--

64

N

Software version

Software version acquired from the smart device

--

64

N

Mobile network country code

Mobile network country code acquired from the smart device

Maximum of 10 characters

40

N

Mobile network operator code

Mobile network operator code acquired from the smart device

Maximum of 20 characters

80

N

Mobile network operator name

Mobile network operator name acquired from the smart device

Maximum of 20 characters

80

N

Mobile network type

Mobile network type acquired from the smart device

Maximum of 20 characters

80

N

SIM card country code

SIM card country code acquired from the smart device

Maximum of 10 characters

40

N

SIM card operator code

SIM card operator code acquired from the smart device

Maximum of 20 characters

80

N

SIM card operator name

SIM card operator name acquired from the smart device

--

256

N

ICCID

ICCID acquired from the smart device

19 digits

19

N

SIM status code

SIM status code acquired from the smart device

--

64

N

IMSI

IMSI acquired from the smart device

15 digits

15

N

User name

User name acquired from the smart device

Maximum of 20 characters

80

N

Roaming

Roaming information acquired from the smart device

0: Normal

1: Roaming

1

N

Android ID/Apple ID

Android ID or Apple ID acquired from the smart device

--

256

N

Email

Email address acquired from the smart device

--

256

N

Password (set or not set)

Password (set or not set) acquired from the smart device

0: Not set

1: Set

1

N

Internal storage (Total / Free [B])

Internal storage information acquired from the smart device

--

64

N

SD Card (Total / Free [B])

SD card information acquired from the smart device

--

64

N

RAM (Total / Free [B])

RAM information acquired from the smart device

--

64

N

Date/Time of Android policy/iOS profile application

Date and time that the Android policy or iOS profile was applied to the smart device

yyyy/MM/dd hh:mm:ss#5

19

N

Android policy/iOS profile version

Version of the Android policy or iOS profile applied to the smart device

Maximum of 5 characters

5

N

Date/time of device details update

Last date and time that the inventory information was collected

yyyy/MM/dd hh:mm:ss#5

19

N

Legend:

Y: Imported

N: Not imported

--: Any value

#1: The first line of the CSV file does not contain item information.

#2: The maximum number of bytes if UTF-8 or UTF-16 is specified for the character encoding. For half-width alphanumeric characters and symbols, one character is counted as one byte. For other characters, one character is counted as four bytes.

#3: If this item is not specified, the smart device is registered as an unmanaged device.

#4: Although this is an optional item, we recommend that you specify a value.

#5: yyyy: year, MM: month, dd: day, hh: hour, mm: minute, ss: second

Related Topics

15. sdmioutils exportdevice (exporting smart device information)

15. sdmioutils importdevice (importing smart device information)

E.2 Format of an exported event list CSV file

The following table describes the format of an exported event list CSV file.

Format of an exported event list CSV file

Item#1

Description

Output format

Maximum number of bytes#2

Severity

The severity is output.

0: Information

1: Warning

2: Critical

1

Registered Date/Time

The registration date and time is output.

yyyy/MM/dd hh:mm:ss#3

19

Source

The source of the event is output.

Smart Device

smart-device-name

Security

Distribution

Settings

128

Description

The event description is output.

A character string of 1,024 characters plus the number of embedded characters is output.

4,096 characters + number-of-embedded characters x 4

Event Number

The event number is output.

The message for event output is displayed.

10

Type

The event type is output.

0: Security

1: Suspicious Operations

2: Smart Device

3: Distribution

4: Settings

5: Error

1

Details

Event details are output.

A character string of 1,024 characters plus the number of embedded characters is output.

4,096 characters + number-of-embedded characters x 4

Status

The check status is output.

0: Not Ack

1: Ack

1

#1: The first line of the CSV file does not contain item information.

#2: The maximum number of bytes if UTF-8 or UTF-16 is specified for the character encoding. For half-width alphanumeric characters and symbols, one character is counted as one byte. For other characters, one character is counted as four bytes.

#3: yyyy: year, MM: month, dd: day, hh: hour, mm: minute, ss: second

Related Topics

10.2 Exporting event information

17.2 JP1/ITDM2 - SDM (Smart Device Manager) messages output as events

E.3 Format of an exported security policy list XML file

The following describes the format of an exported security policy list XML file.

Example of an exported security policy list XML file

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<policy name="General">
    <note>Description in the note</note>
    <phones number="09000010001">
        <note>Customer A</note>
    </phones>
    <apps name="In-house application">
        <version>1.0</version>
        <alerttype>0</alerttype>
        <installtype>1</installtype>
        <os>1</os>
        <note>For in-house information access</note>
    </apps>
    <urls name="http://www.xyz.co.jp">
        <alerttype>0</alerttype>
        <note>Search site</note>
    </urls>
</policy>

Important note

Do not edit the exported file.

Format of an exported security policy list XML file

Element name

Description

Type

Value output format

Maximum number of bytes#

policy

Security policy root element

!

N

0

name

Security policy name

@

A maximum of 20 characters

80

note

Description of the security policy

!

A maximum of 1,000 characters

4000

phones

Phone number list root element

-

N

0

phone

Phone number information root element

+

N

0

number

Phone number

@

A maximum of 20 characters

A hyphen (-) is not included.

Only numbers are output.

20

note

Description of the phone number

!

A maximum of 1,000 characters

4000

apps

Application list root element

-

N

0

app

Application information

+

N

0

name

Application name

@

A maximum of 100 characters

400

version

Application version

!

A maximum of 100 characters

400

alerttype

Alert type

!

0: Allowed

1: Prohibited

1

installtype

Installation type

!

0: Installation allowed

1: Installation required

1

os

OS type

!

0: iOS

1: Android

1

note

Application description

!

A maximum of 1000 characters

4000

urls

Web site list root element

-

N

0

url

Web site information

+

N

0

name

URL

@

A maximum of 200 characters

800

alerttype

Alert type

!

0: Allowed

1: Prohibited

1

note

URL description

!

A maximum of 1000 characters

4000

Legend:

N: No value is output.

@: Attribute value of the element

!: Required

-: Optional

+: One or more repetitions

#: The maximum number of bytes if UTF-8 or UTF-16 is specified for the character encoding. For half-width alphanumeric characters and symbols, one character is counted as one byte. For other characters, one character is counted as four bytes.

Related Topics

15. sdmioutils exportpolicy (exporting security policy settings)

15. sdmioutils importpolicy (importing security policy settings)

E.4 Format of an exported smart device security policy (Android policy or iOS profile) XML file

The following describes the format of an exported smart device security policy (Android policy or iOS profile) XML file.

Example of an exported smart device security policy (Android policy or iOS profile) XML file

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<sdmpolicy name="General">
    <os>0</os>
    <policy>Android-policy-or-iOS-profile</policy>
    <note>Description</note>
</sdmpolicy>

Important note

Do not edit the exported file.

Format of an exported smart device security policy (Android policy or iOS profile) XML file

Element name

Description

Type

Value output format

Maximum number of bytes#

sdmpolicy

Root element of the Android policy or iOS profile

!

N

0

name

Android policy name or iOS profile name

@

A maximum of 20 characters

80

os

OS type

!

0: iOS

1: Android

1

policy

Android policy or iOS profile

!

<![CDATA[

XML-data-for-Android-policy-or-iOS profile

]]>

32000

note

Description of the Android policy or iOS profile

!

A maximum of 1,000 characters

4000

Legend:

N: No value is output.

@: Attribute value of the element

!: Required

#: The maximum number of bytes if UTF-8 or UTF-16 is specified for the character encoding. For half-width alphanumeric characters and symbols, one character is counted as one byte. For other characters, one character is counted as four bytes.

Related Topics

15. sdmioutils exportsdpolicy (exporting Android policy information or iOS profile information)

15. sdmioutils importsdpolicy (importing Android policy information or iOS profile information)

E.5 Format of an exported distributed-application XML file

The following describes the format of an exported distributed-application XML file.

Example of an exported distributed-application XML file

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<delivery name="Sample application">
    <description>Description</description>
    <binary>distributed-application-package</binary>
    <installparam>installParam</installparam>
    <mime>package-type</mime>
    <pkg_no>package-No.</pkg_no>
    <pkg_id>package-ID</pkg_id>
</delivery>

Important note

Do not edit the exported file.

Format of an exported distributed-application XML file

Element name

Description

Type

Value output format

Maximum number of bytes#

delivery

Distributed application root element

!

N

0

name

Distributed application name

@

A maximum of 100 characters

400

description

Description

!

A maximum of 1000 characters

4000

binary

Distributed application package

!

Binary value

Package size

installparam

Install Parameters

!

A maximum of 256 characters

1024

mime

Package type

!

A maximum of 256 characters

1024

pkg_no

Package No.

!

UUID value

36

pkg_id

Package ID

!

UUID value

36

Legend:

N: No value is output.

@: Attribute value of the element

!: Required

#: The maximum number of bytes if UTF-8 or UTF-16 is specified for the character encoding. For half-width alphanumeric characters and symbols, one character is counted as one byte. For other characters, one character is counted as four bytes.

Related Topics

15. sdmioutils exportdeliveryapp (exporting distributed application information)

15. sdmioutils importdeliveryapp (importing distributed application information)

F. Storage locations of (and how to obtain) information required for support

The table below shows the storage locations of information required for support if the sdmgetlogs command cannot be used in a user environment, and how to obtain such information. Notify users of the storage locations and how to collect the information.

Storage locations or how to collect information required for support

Information

Description

Storage location or how to obtain information

Smart device manager information

JP1/ITDM2 - SDM (Smart Device Manager) log

File stored in the following folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\log

JP1/ITDM2 - SDM (Smart Device Manager) environment setting file

File stored in the following folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\conf

Files in the uC folder for JP1/ITDM2 - SDM (Smart Device Manager)

Files stored in the following folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\uC

Files in the db folder for JP1/ITDM2 - SDM (Smart Device Manager)

Files stored in the following folder:

JP1/ITDM2 - SDM (Smart Device Manager)-installation-folder\mgr\db

Communication server information

JP1/ITDM2 - SDM (Communication Server) log

File stored in the following folder:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\log

JP1/ITDM2 - SDM (Communication Server) environment setting file

File stored in the following folder:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\conf

Files in the uC folder for JP1/ITDM2 - SDM (Communication Server)

Files stored in the following folder:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\uC

Messaging server information

JP1/ITDM2 - SDM (Messaging Server) log

File stored in the following folder:

JP1/ITDM2 - SDM (Messaging Server)-installation-folder\mss\log

JP1/ITDM2 - SDM (Messaging Server) environment setting file

Following file:

JP1/ITDM2 - SDM (Messaging Server)-installation-folder\mss\conf\SdMessagingServer.ini

JP1/ITDM2 - SDM (Smart Device Android Agent) information

JP1/ITDM2 - SDM (Smart Device Android Agent) log

Collect log data from the smart device, and then obtain the file stored in the following folder:

JP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\log\agent\name_yyyyMMdd_hhmmss#.log

JP1/ITDM2 - SDM (Smart Device iOS Agent) information

JP1/ITDM2 - SDM (Smart Device iOS Agent) log

Collect log data from the smart device, and then obtain the file stored in the following folder:

JJP1/ITDM2 - SDM (Communication Server)-installation-folder\cms\log\agent\name_yyyyMMdd_hhmmss#.log

#: yyyy: year, MM: month, dd: day, hh: hour, mm: minute, ss: second

Tip

Information might not be obtainable, depending on the user's environment. In such cases, collect information as much as possible.

G. Commands used to acquire certificates for SSL communication

The following describes the commands used to acquire certificates for SSL communication.

G.1 Creating a private key for the Web server (keygen command)

This section describes how to use the keygen command to create a private key for the Web server. The created Web server private key file is specified in the SSLCertificateKeyFile directive.

Format

keygen -rand file-name [encryption-type] -out key-file [-bits bit-length]

Arguments

-rand file-name

Specify any file to be used for random number generation. You must specify an appropriate file whose size is large enough for the random number generation (for example, C:\WINNT\NOTEPAD.EXE).

encryption-type

Specify the encryption type when encrypting the private key. If you specify this parameter, you will be requested to enter a password when creating the private key. The password must be no more than 64 characters long.

When creating the Certificate Signing Request (CSR) and starting the Web server, you will also be requested to enter the password. Note that you can skip the password entry for Web server startup. The following encryption types can be specified:

-des

The Data Encryption Standard (DES) is selected as the encryption type.

-des3

Triple DES is selected as the encryption type. This parameter does not affect the encryption type used in the communication between the Web server and the Web browser.

-out key-file

Specify the file to which the Web server private key is output.

-bits bit-length

Specify the bit length of the Web server private key. The following bit length can be specified:

512

1024

2048

4096

If this argument is omitted, 1024 is assumed.

Example

To create the httpsdkey.pem Web server private key:

keygen -rand C:\WINNT\NOTEPAD.EXE -out httpsdkey.pem -bits 1024

Related Topics

G.2 Creating a Certificate Signing Request (CSR) (certutil reqgen command)

G.6 Create a password file (sslpasswd command)

G.2 Creating a Certificate Signing Request (CSR) (certutil reqgen command)

This section describes how to use the certutil reqgen command to create a Certificate Signing Request (CSR). The created CSR file is submitted to the CA, which then issues the signed certificate. The CSR is created in the format conforming to PKCS #10.

Format

certutil reqgen [-sign signature-algorithm] -key key-file -out CSR-file

Arguments

-sign signature-algorithm

Specify the signature algorithm used when the CSR is created. The following signature algorithms can be specified:

MD5

md5WithRSAEncryption is used.

SHA1

sha1WithRSAEncryption is used.

SHA224

sha224WithRSAEncryption is used.

SHA256

sha256WithRSAEncryption is used.

SHA384

sha384WithRSAEncryption is used.

SHA512

sha512WithRSAEncryption is used.

If this argument is omitted, SHA1 is assumed.

-key key-file

Specify the Web server private key file. Specify the private key file created by using the keygen command.

-out CSR-file

Specify the file to which the created CSR is output.

Example

To create a Certificate Signing Request (CSR) by using the Web server private key file httpsdkey.pem, specify as follows:

certutil reqgen -sign SHA1 -key httpsdkey.pem -out httpsd.csr

If you have set a password when creating the private key for the Web server, you are prompted to enter the password. For the items to be set, follow the instructions from the CA to which you submit the Certificate Signing Request (CSR).

G.3 Displaying the contents of a Certificate Signing Request (CSR) (certutil req command)

This section explains how to display the contents of a Certificate Signing Request (CSR).

Format

certutil req -in CSR-file -text

Arguments

-in CSR-file

Specify the CSR file to be displayed.

Example

To display the CSR file httpsd.csr, specify as follows:

certutil req -in httpsd.csr -text

G.4 Displaying certificate contents (certutil cert command)

This subsection explains how to display the contents of a certificate file. The following command displays the part of the certificate file that begins with -----BEGIN CERTIFICATE----- and ends with -----END CERTIFICATE----.

Format

certutil cert -in certificate-file -text

Arguments

-in certificate-file

Specify the certificate file to be displayed.

Example

To display the certificate file httpsd.pem, specify as follows:

certutil cert -in httpsd.pem -text

G.5 Converting the certificate format (certutil cert command)

This section explains how to convert the certificate format. Use this functionality as necessary.

Format

certutil cert -inform input-format -outform output-format -in input-file -out output-file

Arguments

-inform input-format

Specify the input format of the certificate file before conversion. The following input formats can be specified:

DER

PEM

If this argument is omitted, PEM is assumed.

-outform output-format

Specify the input format of the certificate file after conversion. The following input formats can be specified:

DER

PEM

If this argument is omitted, PEM is assumed.

-in input-file

Specify the certificate file before conversion.

-out output-file

Specify the certificate file after conversion.

G.6 Create a password file (sslpasswd command)

If you want to omit the password input when starting the Web server, create a password file.

When you use the server private key protected by a password, you can save the password in advance in a file and set the directive to omit the password input when restarting the server. This procedure is described below. Note that the following procedure is required when you use the server private key protected by password:

Create a server private key with a password by using the keygen command.

Create a password file by the sslpasswd command.

Set the SSLCertificateKeyPassword directive that specifies the created password file together with the SSLCertificateKeyFile directive that specifies the server private key file in the httpsd.conf.

Start or restart the server.

Important note

You need to take care when protecting the password file items. Set the directory permissions and the file permissions to prevent other users from accessing the storage directory of the server private key, and also prevent them from accessing the storage directory of the password file.

Format

sslpasswd server-private-key-file-name password-file-name

Arguments

server-private-key-file-name

Specify the password protected server private key. Specify the private key file created by using the keygen command.

password-file-name

Specify the name of the file that outputs password.

Important note

You cannot specify an existing file name as the password file name.

Example

To create a password file keypasswd, specify as follows:

sslpasswd httpsdkey.pem .keypasswd

Related Topics

G.1 Creating a private key for the Web server (keygen command)

H. Inventory information list

The following table describes inventory information that can be collected in JP1/ITDM2 - SDM.

Inventory information list

Category

Item

Description

iOS

Android

Smart Device List view

Severity

The highest severity of events for the smart device

Y

Y

Name

Name such as an asset management number

Y

Y

IMEI/MEID

IMEI/MEID acquired from the smart device

Y

Y

ICCID

ICCID acquired from the smart device

Y

Y

Phone Number

Phone number of the smart device from which the information is acquired

Y

Y

Department

Department to which the user belongs

Y

Y

User Name

Name of the user

Y

Y

Last Modified Date/Time

Date and time that the information was last modified due to registration of a smart device or import of smart device information

Y

Y

Events tab

Status

Check status of the event

Y

Y

Severity

Severity of the event

Y

Y

Event Number

Event number

Y

Y

Description

Event description

Y

Y

Registered Date/Time

Date and time that the event was registered

Y

Y

Type

Event type

Y

Y

Call History tab

Status

Check status of the call history

N

Y

Severity

Severity of the call history

N

Y

Other Party's Phone Number

Other party's phone number acquired from the smart device

N

Y

Category

Call category (Made, Received, Missed, Unidentified, or Blocked) acquired from the smart device

N

Y

Call Start Time

Call start time acquired from the smart device

N

Y

Call Time

Call time acquired from the smart device

N

Y

Web Browsing History tab

Status

Check status of the Web browsing history

N

Y

Severity

Severity of the Web browsing history

N

Y

URL

Browsed URL acquired from the smart device

N

Y

Browsed Date/Time

Browsed date and time acquired from the smart device

N

Y

Software tab

Status

Software check status

Y

Y

Severity

Severity of the software

Y

Y

Application name

Name of the application installed on the smart device

Y

Y

Version

Application version

Y

Y

Manufacturer

Application manufacturer

Y

Y

Hardware tab

IMEI/MEID

IMEI/MEID acquired from the smart device

Y

Y

ICCID

ICCID acquired from the smart device

Y

Y

Serial Number

Serial number acquired from the smart device

Y

Y

Model Number

Model number acquired from the smart device

Y

Y

Model Name

Model name acquired from the smart device

Y

Y

Manufacturer

Manufacturer name acquired from the smart device

Y

Y

Battery Level

Battery level acquired from the smart device

Y

Y

Internal storage (Total / Free [B])

Internal storage information acquired from the smart device

Y

Y

SD Card (Total / Free [B])

SD card information acquired from the smart device

N

Y

RAM (Total / Free [B])

RAM information acquired from the smart device

N

Y

3G MAC Address

3G MAC address acquired from the smart device

N

Y

WiFi MAC Address

WiFi MAC address acquired from the smart device

Y

Y

Bluetooth MAC Address

Bluetooth MAC address acquired from the smart device

Y

Y

UDID

UDID acquired from the smart device

Y

N

Running Applications tab

Application name

Name of the running application acquired from the smart device

N

Y

Version

Application version

N

Y

Manufacturer

Application manufacturer

N

Y

Running Services tab

Service Name

Name of the running service acquired from the smart device

N

Y

Version

Service version

N

Y

Manufacturer

Service manufacturer

N

Y

System Information tab

OS

OS information acquired from the smart device

Y

Y

OS Version

OS version acquired from the smart device

Y

Y

Phone Number

Phone number acquired from the smart device

Y

Y

Mobile Network

Mobile network information acquired from the smart device

Y

Y

SIM Card

SIM card information acquired from the smart device

Y

Y

Roaming

Roaming information acquired from the smart device

Y

Y

Android ID/Apple ID

Android ID or Apple ID acquired from the smart device

Y

Y

Email

Email address acquired from the smart device

Y

Y

IP Address

IP address acquired from the smart device

Y

Y

Proxy Server

Proxy server acquired from the smart device

Y

Y

GPS Information

GPS information acquired from the smart device

N

Y

Lock Release Password Changed During Last Lock

Unlock password that was changed the last time the lock was set

N

Y

Department

Department to which the user belongs

Y

Y

Account

Account of the user

Y

Y

User Name

Name of the user

Y

Y

Security tab

Current Security Policy

Name of the security policy applied to the smart device

Y

Y

Current Android Policy/iOS Profile

Android policy or iOS profile applied to the smart device

Y

Y

Date/Time of Android Policy/iOS Profile Application

Date and time that the Android policy or iOS profile was applied to the smart device

Y

Y

Android Policy/iOS Profile Version

Version of the Android policy or iOS profile applied to the smart device

Y

Y

GPS Power Status

GPS power status acquired from the smart device

Y

Y

Last Date/Time of Successful Lock Release

Date and time that the last unlock was successful

N

Y

Last Date/Time of Failed Lock Release

Date and time that the last unlock failed

N

Y

Agent Ver.

Agent version of this product

Y

Y

Bluetooth Connection Information tab

Status

Check status of Bluetooth connection information

N

Y

Severity

Severity of Bluetooth connection information

N

Y

Connection Name

Bluetooth connection name acquired from the smart device

N

Y

Connection Address

Bluetooth connection address acquired from the smart device

N

Y

Legend:

Y: Can be acquired

N: Cannot be acquired

I. Reference Material for This Manual

This appendix provides reference information, including various conventions, for this manual.

I.1 Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

Job Management Partner 1/IT Desktop Management 2 Getting Started (3021-3-367(E))

Job Management Partner 1/IT Desktop Management 2 Overview and System Design Guide (3021-3-368(E))

Job Management Partner 1/IT Desktop Management 2 Configuration Guide (3021-3-369(E))

Job Management Partner 1/IT Desktop Management 2 Administration Guide (3021-3-370(E))

Job Management Partner 1/IT Desktop Management 2 Distribution Function Administration Guide (3021-3-373(E))

Job Management Partner 1/IT Desktop Management 2 Automatic Installation Tool Administration Guide (3021-3-374(E))

Job Management Partner 1/IT Desktop Management 2 - Asset Console Description (3021-3-375(E))

Job Management Partner 1/IT Desktop Management 2 - Asset Console Planning and Configuration Guide (3021-3-376(E))

Job Management Partner 1/IT Desktop Management 2 - Asset Console Administration Guide (3021-3-377(E))

Job Management Partner 1/IT Desktop Management 2 Messages (3021-3-378(E))

I.2 Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Abbreviation

Full name or meaning

Firefox

Firefox(R)

JP1/ITDM2 - SDM

JP1/ITDM2 - SDM (Smart Device Agent)

JP1/ITDM2 - SDM (Smart Device Android Agent)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Smart Device Android Agent)

JP1/ITDM2 - SDM (Smart Device iOS Agent)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Smart Device iOS Agent)

JP1/ITDM2 - SDM (Smart Device Manager)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Smart Device Manager)

JP1/ITDM2 - SDM (Communication Server)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Communication Server)

JP1/ITDM2 - SDM (Messaging Server)

Job Management Partner 1/IT Desktop Management 2 - Smart Device Manager (Messaging Server)

I.3 Conventions: Acronyms

This manual uses the following acronyms:

Acronym

Full name or meaning

APNs

Apple Push Notification Service

CD

Compact Disc

CPU

Central Processing Unit

CSV

Comma Separated Values

DB

Database

DMZ

DeMilitarized Zone

DVD

Digital Versatile Disk

HTTP

Hyper Text Transfer Protocol

HTTPS

Hyper Text Transfer Protocol Secure

ICCID

Integrated Circuit Card ID

IMEI

International Mobile Equipment Identity

IMSI

International Mobile Subscriber Identity

ID

IDentification

IP

Internet Protocol

IT

Information Technology

LAN

Local Area Network

MAC

Media Access Control

MDM

Mobile Device Management

OEM

Original Equipment Manufacturer

OMA-DM

Open Mobile Alliance Device Management

OS

Operating System

PC

Personal Computer

RAM

Random Access Memory

SD

Secure Digital

SIM

Subscriber Identity Module

SSL

Secure Socket Layer

Subject DN

Subject Distinguished Name

TCP

Transmission Control Protocol

TLS

Transport Layer Security

UAC

User Account Control

UDID

Unique Device IDentifier

URL

Uniform Resource Locator

USB

Universal Serial Bus

UUID

Universally Unique IDentifier

VPN

Virtual Private Network

WWW

World Wide Web

XML

Extensible Markup Language

I.4 Conventions: Fonts

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.

I.5 Conventions: Symbols

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

I.6 About Help

JP1/ITDM2 - SDM comes with an HTML manual that you can read in a Web browser.

You can view the help by selecting Help and then IT Desktop Management2 - Smart Device Manager Help in the JP1/ITDM2 - SDM operation window.

I.7 Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,024² bytes.

1 GB (gigabyte) is 1,024³ bytes.

1 TB (terabyte) is 1,024⁴ bytes.

J. Glossary

administrator's computer

The computer a JP1/ITDM2 - SDM administrator uses to log in to JP1/ITDM2 - SDM.

Android policy

A policy used in JP1/ITDM2 - SDM to batch specify Android device functionality and usage guidelines. This policy is set on the smart device manager, and then applied to managed smart devices.

APNs

Abbreviation of Apple Push Notification Service, which is provided by Apple.

Comet

A technology used when making Web applications. Comet technology allows a server to hold a request from a client, without giving an immediate response, and then send a response when an event occurs on the server.

Comet connection

In JP1/ITDM2 - SDM, Comet technology is used as a means of implementing requests to Android terminals. A Comet connection indicates an HTTP connection that uses Comet technology for the connection between an Android device and JP1/ITDM2 - SDM.

communication server

A computer on which JP1/ITDM2 - SDM (Communication Server) is installed.

configuration profile

An XML file containing device and security policies, VPN configuration information, Wi-Fi settings, APN settings, Exchange account settings, email settings, and certificates that allow enterprise system operations from iPhones and iPads. You can create a configuration profile by using the iPhone Configuration Utility provided by Apple.

initialize

The act of initializing (wiping) a smart device to the factory default settings. This operation is used to prevent unauthorized use by third parties if a smart device is lost or stolen.

iOS profile

A policy used in JP1/ITDM2 - SDM to batch specify iOS device functionality and usage guidelines. This policy is set on the smart device manager, and then applied to managed smart devices. A configuration profile that is created in advance by using the iPhone Configuration Utility configuration is used as an iOS profile in JP1/ITDM2 - SDM.

iPhone Configuration Utility

A tool, provided by Apple, for creating configuration profiles. In addition to creating configuration profiles, you can use this tool to install a configuration profile on a smart device.

JP1/IT Desktop Management 2

A system that manages IT assets from device management, security management, and asset management perspectives.

JP1/ITDM2 - SDM (Communication Server)

A JP1/ITDM2 - SDM program that provides communication server functionality

JP1/ITDM2 - SDM (Messaging Server)

A program that provides the Comet function with Android devices

JP1/ITDM2 - SDM (Smart Device Agent)

The generic name for JP1/ITDM2 - SDM (Smart Device Android Agent) and JP1/ITDM2 - SDM (Smart Device iOS Agent)

JP1/ITDM2 - SDM (Smart Device Android Agent)

A JP1/ITDM2 - SDM program that provides agent functionality for Android devices

JP1/ITDM2 - SDM (Smart Device iOS Agent)

A JP1/ITDM2 - SDM program that provides agent functionality for iOS devices

JP1/ITDM2 - SDM (Smart Device Manager)

A JP1/ITDM2 - SDM program that provides server functionality

lock

The act of remotely disabling a smart device. This operation is used to prevent unauthorized third parties from using a smart device that was lost or stolen.

menu area

An area that appears in the left side of the operation window. The menu displayed in this area depends on the selected module. Select a menu item to display the corresponding information in the information area on the right side of the operation window.

messaging server

A computer on which JP1/ITDM2 - SDM (Messaging Server) is installed.

OMA-DM

An abbreviation of Open Mobile Alliance (OMA) Device Management (DM), which is a device management protocol defined by the Open Mobile Alliance, which promotes standardization of mobile-related applications. OMA-DM provides functionality such as provisioning, device setup, and software upgrading.

OMA-DM Client

An OMA-DM client program that is deployed on an Android device

passcode

A password used to unlock an iOS device

provisioning

A function that automatically changes settings such as the connection destination URL and inventory data collection interval for JP1/ITDM2 - SDM (Smart Device Agent) running on a smart device managed by JP1/ITDM2 - SDM

security policy

A policy used to monitor the usage of smart devices in JP1/ITDM2 - SDM. Phone numbers, Web sites, and applications to be monitored can be set as criteria for evaluating the risk level of smart devices. A security policy is set on the smart device manager and then applied to managed smart devices.

security rule

The generic name of the following three rules for managing smart devices:

Security policy

Android policy

iOS profile

severity

Three types of severity (Critical, Warning, and Information) are displayed for events output during JP1/ITDM2 - SDM operation by an administrator, and for events output as a result of security policy verification.

smart device

A small, portable terminal device such as a smartphone, tablet PC, or PDA.

smart device manager

A computer on which JP1/ITDM2 - SDM (Smart Device Manager) is installed.

system administrator permission

One of the permissions assignable when a user account is created in JP1/ITDM2 - SDM. A user with this permission has full access to the management features of JP1/ITDM2 - SDM.

view permission

One of the permissions assignable when a user account is created in JP1/ITDM2 - SDM. A user with this permission can view modules other than the Settings module, but cannot add new information or change existing settings.

Index

A

abbreviations for products[1]

Account Management view[1]

acquiring backup, sdmexportdb command[1]

acronyms[1]

actions to be taken for problems with database[1]

actions to be taken when a disk is low on free space[1]

Add Android Application dialog box[1]

Add Android Policy dialog box[1]

Add Application dialog box[1]

adding Android policies[1]

adding iOS profiles[1]

adding security policies[1]

adding user account[1]

Add iOS Profile dialog box[1]

Add Phone Number dialog box[1]

Add Security Policy dialog box[1]

Add Smart Device dialog box[1]

Add User Account dialog box[1]

Add Web Site dialog box[1]

administrator's computer[1], [2]

Android applications

managing[1]

Android Application view[1]

Android Application view, tabs[1]

Android device[1]

sending messages to[1]

Android device password

changing[1], [2]

Android policies

applying[1]

Android policy[1], [2]

items[1]

managing[1]

Android policy, adding[1]

Android policy, editing[1]

Android policy, removing[1]

Android Policy List view[1]

APNs[1]

APNs server[1]

applications

distributing to Android devices[1], [2]

instructing installation[1], [2]

managing[1], [2]

removing from JP1/ITDM2 - SDM[1]

applications to Android devices

flow of distributing[1]

application that is no longer needed

removing[1]

application to be distributed

registering in JP1/ITDM2 - SDM[1]

Apply Android Policy dialog box[1]

applying

Android policies[1]

applying iOS profiles[1]

applying security policies[1]

Apply iOS Profile dialog box[1]

Apply Security Policy dialog box[1]

B

backing up database[1]

basic module layout[1]

basic system configuration[1]

Bluetooth Connection Information tab (Managed Smart Device List view)[1]

C

Call History tab (Managed Smart Device List view)[1]

certificates for SSL communication[1]

deployment[1]

obtaining[1]

setting up on communication server[1]

setting up on smart device manager[1]

certificates for SSL communication for APNs server [1]

certificates for SSL communication for communication server[1]

obtaining[1]

certificates for SSL communication for smart device manager[1]

obtaining[1]

certutil cert command[1], [2]

certutil req command[1]

certutil reqgen command[1]

Change Password dialog box[1]

changing

Android device password[1]

connection destination port number for database[1]

changing network configuration for smart device manager or communication server, sdmnetchange command[1]

changing the default password[1]

changing your own password[1]

checking

root certificates for SSL communication preinstalled on smart device[1]

client certificate for SSL communication for APNs server

setting up on communication server[1]

collecting

smart device log[1]

collecting log information, sdmgetlogs command[1]

Comet[1]

Comet connection[1]

command description format[1]

command list[1]

commands[1]

commands used to acquire certificates for SSL communication[1]

communication server[1], [2]

CommunicationServerEngine.properties (communication server environment setting file)[1]

communication server environment setting file (CommunicationServerEngine.properties)[1]

components of JP1/ITDM2 - SDM[1]

configuration profile[1]

configuration profile on communication server

creating[1]

connection destination port number for database

changing[1]

convention

symbol[1]

conventions

abbreviations for products[1]

acronyms[1]

font[1]

fonts[1]

KB, MB, GB, and TB[1]

symbols[1]

converting the certificate format[1]

create a password file[1]

creating a Certificate Signing Request (CSR)[1]

creating a private key for the Web server[1]

creating MDM signed-certificate request file, sdmcreatemdmcertreq command[1]

customizing settings[1]

D

database, changing port number[1]

Database and Disk Usage panel[1]

database backup[1]

database management[1]

database restoration[1]

defining organization's security principles[1]

definition file list[1]

definition files[1]

displaying

events[1]

system summary[1]

displaying certificate contents[1]

displaying the contents of a Certificate Signing Request (CSR)[1]

Distributed Application List view[1]

distributed applications

managing[1]

uninstalling[1]

distributing

applications to Android device[1]

Distribution module[1]

window transitions[1]

Distribution module operation[1]

E

Edit Android Application dialog box[1]

Edit Android Policy dialog box[1]

Edit Application dialog box[1]

editing

registered application information[1]

editing Android policies[1]

editing another administrator's user account[1]

editing security policies[1]

editing your own user account[1]

Edit Phone Number dialog box[1]

Edit Security Policy dialog box[1]

Edit User Account dialog box[1]

Edit Web Site dialog box[1]

event

notifying by email[1]

Event Detail dialog box[1]

Event List view[1]

eventmail.properties (event mail format information file)[1]

event mail format information file (eventmail.properties)[1]

event notification parameters[1]

Event Notifications view[1]

event reference[1]

events

displaying[1]

format[1]

output[1]

types[1]

Events module[1]

window transitions[1]

Events module operation[1]

Events tab (Managed Smart Device List view)[1]

Events tab (Unmanaged Smart Device List view)[1]

Event Summary panel[1]

executing commands[1]

exported distributed-application XML file

format[1]

exported event list CSV file

format[1]

exported security policy list XML file

format[1]

exported smart device list CSV file

format[1]

exported smart device security policy (Android policy or iOS profile) XML file

format[1]

exporting

list of smart devices[1]

exporting Android policy information, sdmioutils exportsdpolicy command[1]

exporting distributed application information, sdmioutils exportdeliveryapp command[1]

exporting event information[1]

exporting iOS profile information, sdmioutils exportsdpolicy command[1]

exporting iOS profiles[1]

exporting security policy settings, sdmioutils exportpolicy command[1]

exporting smart device information, sdmioutils exportdevice command[1]

F

features

list of[1]

firewall

setting up on server[1]

flow of building system[1]

flow of changing

Android device password[1]

smart device user[1]

flow of disposing of

smart devices[1]

flow of distributing

new smart device[1]

flow of initializing

lost smart device[1]

flow of installing

JP1/ITDM2 - SDM (Smart Device Agent) on smart device[1]

flow of locking

lost smart device[1]

flow of notifying

event by email[1]

flow of obtaining

certificates for SSL communication for communication server[1]

certificates for SSL communication for smart device manager[1]

MDM client certificate for SSL communication for APNs server[1]

flow of preparing

newly purchased smart device[1]

smart device registered in JP1/ITDM2 - SDM[1]

flow of removing

application that is no longer needed[1]

Flow of replacing

smart devices[1]

flow of resetting

iOS device passcode[1]

flow of setting

initialized smart device to Managed[1]

flow of storing

smart devices[1]

folders

created on the communication server[1]

created on the messaging server[1]

created on the smart device manager[1]

list of[1]

format

events[1]

exported distributed-application XML file[1]

exported event list CSV file[1]

exported or imported smart device list CSV file[1]

exported security policy list XML file[1]

exported smart device security policy (Android policy or iOS profile) XML file[1]

G

GB meaning[1]

GUI Reference[1]

H

Hardware tab (Managed Smart Device List view)[1]

Home module[1]

Home module operation[1]

I

imported and exported files

format of[1]

imported smart device list CSV file

format[1]

importing Android policy information, sdmioutils importsdpolicy command[1]

importing distributed application information, sdmioutils importdeliveryapp command[1]

importing iOS profile information, sdmioutils importsdpolicy command[1]

importing security policy settings, sdmioutils importpolicy command[1]

importing smart device information, sdmioutils importdevice command[1]

Import Smart Device List dialog box[1]

information area[1]

initialize[1]

initialized smart device

setting to Managed[1]

Initialize Smart Device dialog box[1]

installing

JP1/ITDM2 - SDM (Communication Server)[1]

JP1/ITDM2 - SDM (Messaging Server)[1]

JP1/ITDM2 - SDM (Smart Device Manager)[1]

instructing

application installation[1], [2]

inventory information list[1]

iOS device[1]

iOS device passcode

resetting[1], [2]

iOS profile[1], [2]

items[1]

managing[1]

iOS profile, adding[1]

iOS profile, applying[1]

iOS profile, exporting[1]

iOS profile, removing[1]

iOS Profile List view[1]

iPhone Configuration Utility[1]

ITDM2 management server[1]

items that can be set

Android policy[1]

iOS profile[1]

security policy[1]

J

JP1/IT Desktop Management 2[1]

JP1/ITDM2 - SDM

managing smart devices[1]

uninstalling[1]

JP1/ITDM2 - SDM, what you can do while it is running[1]

JP1/ITDM2 - SDM (Communication Server)[1]

JP1/ITDM2 - SDM (Messaging Server)[1]

JP1/ITDM2 - SDM (Smart Device agent)[1]

JP1/ITDM2 - SDM (Smart Device Agent) on smart device

installing[1]

JP1/ITDM2 - SDM (Smart Device Android Agent)[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) (for Android device)

installing[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) (for PC)

installing[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) from Android device (using Android device Settings menu)

uninstalling[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) from Android device (using Google Play Store application)

uninstalling[1]

JP1/ITDM2 - SDM (Smart Device iOS Agent)[1]

installing[1]

JP1/ITDM2 - SDM (Smart Device iOS Agent) from iOS device

uninstalling[1]

JP1/ITDM2 - SDM (Smart Device Manager)[1]

K

KB meaning[1]

keygen command[1]

L

latest inventory information from smart device

obtaining[1]

list of folders[1]

list of operations that cannot be performed

view permissions[1]

list of processes[1]

list of services[1]

list of smart devices

exporting[1]

List of Smart Devices Distributed To tab (Android Application view)[1]

List of Smart Devices Installed To tab (Android Application view)[1]

List of Smart Devices Not Distributed To tab (Android Application view)[1]

lists of parameters[1]

lock[1]

locking

user accounts[1]

locking smart device[1]

Lock Smart Device dialog box[1]

logging in[1]

logging out[1]

Login window[1]

window transitions from, to immediately after login[1]

lost smart device

initializing[1]

locking[1]

M

mail notification, event[1]

mail server parameters[1]

Managed Smart Device List view[1]

Managed Smart Device List view, tabs[1]

managed smart devices

managing[1]

managed smart device to Unmanaged

setting[1]

manager.properties (smart device manager environment setting file)[1]

managing

Android applications[1]

Android policy[1]

applications[1], [2]

distributed applications[1]

iOS profile[1]

managed smart devices[1]

security[1]

security policy[1]

security rules[1]

smart device[1]

smart devices[1]

unmanaged smart devices[1]

user accounts[1]

managing the security status[1]

managing User Accounts[1]

manually registering

smart device[1]

MB meaning[1]

MDM certificate request file

downloading[1]

MDM client certificate for SSL communication for APNs server

obtaining[1]

MDM client certificates

creating[1]

MDM signed-certificate request file

creating[1]

menu area[1], [2]

message format[1]

messages[1]

JP1/ITDM2 - SDM (Smart Device Manager) messages output as events[1]

list of command messages[1]

list of JP1/ITDM2 - SDM (Messaging Server) messages[1]

list of JP1/ITDM2 - SDM (Smart Device Manager) messages[1]

messaging server[1], [2]

messaging server setting file (SdMessagingServer.ini)[1]

module layout[1]

module operation (Distribution module)[1]

module operation (Events module)[1]

module operation (Home module)[1]

module operation (Security module)[1]

module operation (Settings module)[1]

module operation (Smart Device module)[1]

N

new smart device

distributing[1]

O

obtaining

certificates for SSL communication[1]

latest inventory information from smart device[1]

OMA-DM[1]

OMA-DM Client[1]

opening ports on router[1]

output

events[1]

output format

imported and exported files[1]

overview

product[1]

P

parameters

event notification[1]

list of[1]

mail server[1]

user account[1]

passcode[1]

permissions

user account[1]

port number list[1]

preparing

smart devices[1]

prerequisite OSs[1]

prerequisite programs[1]

procedure for creating

configuration profile (communication server)[1]

MDM client certificates[1]

MDM signed-certificate request file[1]

procedure for downloading

MDM certificate request file[1]

procedure for installing

JP1/ITDM2 - SDM (Communication Server)[1]

JP1/ITDM2 - SDM (Messaging Server)[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) (for Android agent)[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) (for PC)[1]

JP1/ITDM2 - SDM (Smart Device iOS Agent)[1]

JP1/ITDM2 - SDM (Smart Device Manager)[1]

procedure for obtaining

root certificate for SSL communication for APNs server[1]

procedure for setting

root certificate for SSL communication (Android device)[1]

root certificate for SSL communication on iOS device[1]

procedure for setting up

client certificate for SSL communication for APSs server (communication server)[1]

root certificate for SSL communication for APSs server (communication server)[1]

root certificate for SSL communication for communication server (smart device server)[1]

server certificates for SSL communication (on communication server)[1]

server certificates for SSL communication (on smart device manager)[1]

procedure for uninstalling

JP1/ITDM2 - SDM[1]

JP1/ITDM2 - SDM (Smart Device Android Agent) from Android device (using Android device Settings menu)[1]

JP1/ITDM2 - SDM (Smart Device iOS Agent) from OS device[1]

JP1/ITDM - SDM (Smart Device Android Agent) from Android device (using Google Play Store application)[1]

processes

list of[1]

product

benefits[1]

product benefits[1]

product overview[1]

program modules[1]

provisioning[1]

provisioning.properties (provisioning information setting file)[1]

provisioning information setting file (provisioning.properties)[1]

provisioning settings[1]

R

registered application information

editing[1]

registering

application to be distributed in JP1/ITDM2 - SDM[1]

smart device in JP1/ITDM2 - SDM[1]

smart devices in CSV file[1]

removing

application from JP1/ITDM2 -SDM[1]

smart device from JP1/ITDM2 -SDM[1]

removing Android policies[1]

removing iOS profiles[1]

removing security policies[1]

removing user account[1]

Reset Smart Device Passcode dialog box[1]

resetting

iOS device passcode[1]

resetting another administrator's password[1]

resetting smart device[1]

restoring database[1]

restoring data using a backup, sdmimportdb command[1]

root certificate for SSL communication for APNs server

obtaining[1]

setting up on communication server[1]

root certificate for SSL communication for communication server

setting up on smart device manager[1]

root certificate for SSL communication on Android device

setting[1]

root certificate for SSL communication on iOS device

setting[1]

root certificates for SSL communication preinstalled on smart device

procedure for checking[1]

Running Applications tab (Managed Smart Device List view)[1]

Running Services tab (Managed Smart Device List view)[1]

S

sdmcreatemdmcertreq command[1]

SdMessagingServer.ini (messaging server setting file)[1]

sdmexportdb command[1]

sdmgetlogs command[1]

sdmimportdb command[1]

sdmioutils exportdeliveryapp command[1]

sdmioutils exportdevice command[1]

sdmioutils exportpolicy command[1]

sdmioutils exportsdpolicy command[1]

sdmioutils importdeliveryapp command[1]

sdmioutils importdevice command[1]

sdmioutils importpolicy command[1]

sdmioutils importsdpolicy command[1]

sdmnetchange command[1]

security

managing[1]

Security module[1]

window transitions[1]

Security module operation[1]

security policy[1], [2]

items[1]

managing[1]

security policy, adding[1]

security policy, applying[1]

security policy, editing[1]

security policy, removing[1]

Security Policy List view[1]

security rule[1]

security rules

managing[1]

types of[1]

security status, managing[1]

Security tab (Managed Smart Device List view)[1]

sending

messages to Android device[1]

server

setting up firewall[1]

server certificates for SSL communication

setting up on communication server[1]

server certificates for SSL communication on smart device manager

setting up on smart device manager[1]

services

list of[1]

setting

managed smart device to Unmanaged[1]

unmanaged smart devices to Managed[1]

Settings module[1]

window transitions[1]

Settings module operation[1]

setting up

certificates for SSL communication (communication server)[1]

certificates for SSL communication (smart device manager)[1]

setting up mail servers[1]

setting user account information[1]

Set to Unmanaged dialog box[1]

severity[1]

smart device[1]

collecting log[1]

flow of management[1]

managing[1]

manually registering[1]

registering in JP1/ITDM2 - SDM[1]

removing from JP1/ITDM2 - SDM[1]

smart device, locking[1]

smart device, newly purchased

preparing[1]

smart device, resetting[1]

smart device manager[1], [2]

smart device manager environment setting file (manager.properties)[1]

Smart Device Message Notification dialog box[1]

Smart Device module[1]

window transitions[1]

Smart Device module operation[1]

smart device registered in JP1/ITDM2 - SDM

preparing[1]

smart devices

disposing of[1]

managing[1]

preparing[1]

registering in CSV file[1]

replacing[1]

storing[1]

taking action if lost[1]

smart device user

changing[1]

SMTP Server view[1]

Software tab (Managed Smart Device List view)[1]

specifying settings for event notification[1]

sslpasswd command[1]

Status of Certificate for MDM panel[1]

storage location of (and how to obtain) information required for support[1]

system administrator permission[1], [2]

system components[1]

system configuration[1]

System Information tab (Managed Smart Device List view)[1]

System Information tab (Unmanaged Smart Device List view)[1]

system summary

displaying[1]

System Summary panel[1]

T

tabs[1]

taking action if smart device is lost[1]

taking action if user forgets Android device password[1]

taking action if user forgets iOS device passcode[1]

TB meaning[1]

testmail.properties (test mail format information file)[1]

test mail format information file (testmail.properties)[1]

troubleshooting[1]

actions to take if communication error occurs between communication server and messaging server[1]

actions to take if communication error occurs between smart device manager and communication server[1]

actions to take if database access error occurs[1]

actions to take if database backup or restoration fails[1]

actions to take if database connection error occurs[1]

communication error between servers[1]

window operation[1]

troubleshooting, database problems[1]

troubleshooting, disk is low on free space[1]

troubleshooting procedure on smart device[1]

troubleshooting procedure on smart device manager[1]

types

events[1]

U

uninstalling

distributed application[1]

unlocking user account[1]

unmanaged smart device

managing[1]

Unmanaged Smart Device List view[1]

Unmanaged Smart Device List view, tabs[1]

unmanaged smart devices to Managed

setting[1]

user account

locking[1]

managing[1]

permissions[1]

user account, adding[1]

user account, managing[1]

user account, removing[1]

user account, unlocking[1]

user account parameters[1]

using Android policies[1]

using iOS profiles[1]

using security policies[1]

V

View Android Application dialog box[1]

View Android Policy dialog box[1]

viewing event details[1]

view permission[1], [2]

list of operations that cannot be performed by[1]

View Security Policy dialog box[1]

W

Web Browsing History tab (Managed Smart Device List view)[1]

window transition diagrams[1]

window transitions

Distribution module[1]

Events module[1]

from Login window to immediately after login[1]

Security module[1]

Settings module[1]

Smart Device module[1]