Symantec Mobile Management for System Center...

Symantec™ Mobile Management for System

Center Configuration Manager

Installation Guide

7.2

SymantecTM Mobile Management for

Configuration Manager: Installation Guide

The software described in this book is furnished under a license agreement and may be used

only in accordance with the terms of the agreement.

Last updated: 2012-06-22.

Legal Notice

Copyright © 2012 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and Athena are trademarks or registered trademarks of

Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be

trademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is required to

provide attribution to the third party (“Third Party Programs”). Some of the Third Party

Programs are available under open source or free software licenses. The License Agreement

accompanying the Software does not alter any rights or obligations you may have under those

open source or free software licenses. Please see the Third Party Software file accompanying

this Symantec product for more information on the Third Party Programs.

See "Symantec Mobile Management for Configuration Manager Third-Party Legal

Notices" on page 105

The product described in this document is distributed under licenses restricting its use,

copying, distribution, and decompilation/reverse engineering. No part of this document may

be reproduced in any form by any means without prior written authorization of Symantec

Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY

IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE

EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR

CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,

PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION

CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT

NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as

defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19

"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in

Commercial Computer Software or Commercial Computer Software Documentation", as

applicable, and any successor regulations. Any use, modification, reproduction release,

performance, display or disclosure of the Licensed Software and Documentation by the U.S.

Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation, 350 Ellis Street, Mountain View, CA 94043

http://www.symantec.com

http://www.symantec.com/

Technical Support Symantec Technical Support maintains support centers globally. Technical

Support’s primary role is to respond to specific queries about product features and

functionality. The Technical Support group also creates content for our online

Knowledge Base. The Technical Support group works collaboratively with the other

functional areas within Symantec to answer your questions in a timely fashion. For

example, the Technical Support group works with Product Engineering and

Symantec Security Response to provide alerting services and virus definition

updates.

Symantec’s support offerings include the following:

A range of support options that give you the flexibility to select the right

amount of service for any size organization

Telephone and/or Web-based support that provides rapid response and

up-to-the-minute information

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7

days a week basis

Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web site at

the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreement

and the then-current enterprise technical support policy.

Contacting Technical Support Customers with a current support agreement may access Technical Support

information at the following URL:


Before contacting Technical Support, make sure you have satisfied the system

requirements that are listed in your product documentation. Also, you should be at

the computer on which the problem occurred, in case it is necessary to replicate the

problem.

When you contact Technical Support, please have the following information

available:

Product release level

Hardware information

Available memory, disk space, and NIC information

www.symantec.com/business/support


Operating system

Version and patch level

Network topology

Router, gateway, and IP address information

Problem description:

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration If your Symantec product requires registration or a license key, access our technical

support Web page at the following URL:


Customer service Customer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as the

following types of issues:

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs or manuals

Support agreement resources If you want to contact Symantec regarding an existing support agreement, please

contact the support agreement administration team for your region as follows:

Asia-Pacific and Japan [email protected]

Europe, Middle-East, and Africa [email protected]

North America and Latin America [email protected]


mailto:[email protected]


http://entsupport.symantec.com/docs/276547


Contents

Chapter 1 About this guide ................................................................................. 7

Introducing this guide ................................................................................................................. 7 Comment on the documentation ............................................................................................... 7

Chapter 2 Server Requirements .......................................................................... 9

Central and Primary Servers ..................................................................................................... 9 Secondary Servers or Management Points.......................................................................... 10 Administrator Console Workstation PCs ............................................................................ 11 Required Ports/Protocols ........................................................................................................ 12 Security Group Configuration ................................................................................................. 13 Apple Enterprise Membership Requirements .................................................................... 13 SYMC Agent for iOS Requirements ..................................................................................... 14 iOS Profile Security Requirements ........................................................................................ 14 Supported Mobile Devices ........................................................................................................ 15

Mobile Device Network ................................................................................................... 15

Chapter 3 Installation ........................................................................................ 17

Installation Components ........................................................................................................... 17 Symantec Mobile Management Components Installation Order ................................. 18 Push Services Installation Procedure .................................................................................... 20 Console and Services Installation Procedures .................................................................... 26

Part 1 Console Installation ............................................................................................. 27 Part 2 Add ISV Proxy Certificate ................................................................................. 32 Part 3 Services Installation ............................................................................................. 35

Chapter 4 Set Up Profiles for iOS Devices ......................................................... 51

View Profiles ................................................................................................................................ 51 Configure iOS Signing and Encryption Profile .................................................................. 52 Create Security Credentials ...................................................................................................... 54

Root or Signing with Public Key .................................................................................. 54 Encryption ........................................................................................................................... 57

Configure MDM Enrollment Profile .................................................................................... 58

Chapter 5 Enrolling Devices .............................................................................. 61

6 Contents

Authentication for Agent Enrollment .................................................................................. 61 iOS Device .................................................................................................................................... 62

Install Symantec Mobile MGMT Agent ................................................................... 62 Enroll iOS device .............................................................................................................. 63

Android Device ........................................................................................................................... 68 Authorizing the Symantec Mobile MGMT Agent for Device Administrator

Privileges ............................................................................................................................. 72

Chapter 6 Registering Devices .......................................................................... 73

Windows Mobile and Windows CE Devices ..................................................................... 74 BlackBerry Smartphones .......................................................................................................... 77

Chapter 7 Device Licenses ................................................................................ 79

View License Information ........................................................................................................ 79 License Warning Dialog .......................................................................................................... 80

Chapter 8 View Devices in Collections .............................................................. 81

iOS Device (iPhone, iPad, iPod Touch) ............................................................................... 81 Android Device ........................................................................................................................... 82 Windows Mobile or Windows CE Device .......................................................................... 83 BlackBerry Smartphone ........................................................................................................... 84

Chapter 9 Configuring Device Ownership ........................................................ 85

Set Ownership ............................................................................................................................. 85 Windows Mobile/Windows CE ................................................................................... 85 BlackBerry Smartphone .................................................................................................. 86

Chapter 10 Additional Procedures ..................................................................... 87

Using a Non-Domain Admin Account for Installation ................................................... 88 Enabling ASP.Net in IIS .......................................................................................................... 89 Query for All Windows Mobile Devices Collection ........................................................ 90 DNS Text Record Setup for Android and iOS Services ................................................. 99

Chapter 1

About this guide

Introducing this guide This guide contains the installation prerequisites and installation procedures for

Symantec Mobile Management for Microsoft® System Center Configuration

Manager.

This guide is intended for administrators who are familiar with Configuration

Manager and its operation and who are authorized to install software.

Comment on the documentation Let us know what you like and dislike about the documentation. Were you able to

find the information you needed quickly? Was the information clearly presented?

Report errors and omissions, or tell us what you would find useful in future versions

of our guides and online help.

Please include the following information with your comment:

The title and product version of the guide on which you want to comment.

The topic (if relevant) on which you want to comment.

Your name.

Email your comment to [email protected]. Please only use this address to

comment on product documentation.

We appreciate your feedback.

https://symdocs.symad.symantec.com/sites/EVWeb/eng/documentation/Templates/Word%20and%20Release%20Note%20Templates%20for%20Third%20Parties/www.symantec.com/business/support?subject=Comment%20on%20the%20Enterprise%20Vault%20documentation

8 About this guide

Comment on the documentation

Chapter 2

Server Requirements This chapter lists the software requirements for servers in the System Center

Configuration Manager environment. It also includes required domain group and

port/protocol configuration information. For more information about the

Configuration Manager requirements, visit the Microsoft web site

(www.microsoft.com).

Notes: All site servers must be members of the same or trusted Active Directory

domain.

Replication Services is required for multi-server environments. Contact support for

assistance and see the Replication Services Installation Guide for more information.

Central and Primary Servers Windows Server® 2003 with Service Pack 1 or higher (32-Bit Edition),

Windows Server 2008 (32 or 64-Bit Edition)

SQL Server® 2005 with Service Pack 2 or higher or SQL Server 2008

Windows Server 2000, 2003, 2008 Active Directory Domain

Microsoft System Center Configuration Manager 2007 R2 Service Pack 1 or

Service Pack 2

Microsoft Internet Information Server (IIS) version 6.0 (Server 2003)

Microsoft Internet Information Services (IIS) version 7.5 (Server 2008)

ASP .Net 2.0 enabled in IIS. See Enabling ASP.Net in IIS on page 89 for more

information.

Microsoft .NET Framework 2.0 or higher

Microsoft Message Queuing (MSMQ)- Microsoft Message Queuing Service,

Message Queuing, Message Queuing Server, and Directory Service Integration

(installed on the server where APNS is running, which is typically the Central

server).

10 Server Requirements

Secondary Servers or Management Points

Windows® Communication Foundation (WCF) service activated.

(Microsoft .NET 2.2 Framework or higher)

Microsoft Silverlight 4.0 for 32 bit systems


The following are also required on the Configuration Manager server if the console

is used on this server:

Microsoft Management Console (MMC) 3.0 or higher

Sun® Microsystems J2SE Runtime Environment Version 6 (Update 5) or

higher

The following are required for supporting iOS devices in Symantec Mobile

Management for System Center Configuration Manager:

MDM (Apple® Mobile Device Management) Services configured on any server

that can access the internet or any server for WiFi.

Microsoft Simple Certificate Enrollment Protocol (SCEP)/

Network Device Enrollment Service (NDES):

Note: SCEP/NDES is optional if a single Identity Certificate is not used for all

iOS devices.

Windows Server 2003- SCEP Add-On for Certificate Services installed on a

Certificate Authority (CA). For more information, visit the following Microsoft

website:

http://www.microsoft.com/downloads/en/details.aspx?familyid=9f306763-d

036-41d8-8860-1636411b2d01&displaylang=en

Windows Server 2008- Certification Authority Role (CertServ) configured on

a domain managed server. For more information, visit the following Microsoft

website:

http://www.microsoft.com/downloads/en/details.aspx?familyid=E11780DE-

819F-40D7-8B8E-10845BC8D446&displaylang=en

Note: iOS devices will access the SCEP server using a URL that the devices can

reach.

Secondary Servers or Management Points Windows Server 2003 Standard Edition with Service Pack 1 or higher (32-Bit

Edition), Windows Server 2008 (32 or 64-Bit Edition)

Microsoft System Center Configuration Manager 2007 R2 Service Pack 1 or

Service Pack 2 (Secondary Servers)

Server Requirements

Administrator Console Workstation PCs

11

Microsoft Internet Information Server (IIS) version 6.0 (Server 2003)

Microsoft Internet Information Services (IIS) version 7.5 (Server 2008)

ASP.Net 2.0 enabled in IIS. See Enabling ASP.Net in IIS on page 89 for more

information.

Microsoft .NET Framework 2.0 or higher

Microsoft Message Queuing (MSMQ)- Microsoft Message Queuing Service,

Message Queuing, Message Queuing Server, and Directory Service Integration

Administrator Console Workstation PCs Windows XP Professional, Windows Vista®, Windows 7, Windows Server

2003, or Windows Server 2008

Microsoft ActiveSync 4.2 or higher

Microsoft Management Console 3.0 or higher

Sun Microsystems J2SE Runtime Environment Version 6 (Update 5) or higher



Typical implementation with the processing/data flow between Configuration Manager components and supported devices


Required Ports/Protocols

Required Ports/Protocols The following are the required ports for communication to devices:

Port 80- for Symantec Mobile Management Device Client communication with

the Athena™ Web Services. Agents use either port 80 or 443 inbound to the

Web Server for inventory.

Port 389- LDAP Service. From the Enrollment Server to an LDAP Server

(internal network) for authentication.

Port 443- for Symantec Mobile Management Device Client communication

with the Athena Web Services with SSL Encryption. Agents use either port 80

or 443 inbound to the Web Server for inventory.

Port 444- for iOS enrollment with MDM (default).

Port 7778- for communication between the console and the Tunnel Server.

Port 7780- for communication between devices and the Tunnel Server.

Port 1433- for Symantec Mobile Management Replication Services SQL

server connection.

To communicate with Apple services, the following outbound ports must be open for

outbound connections over TCP:

Port 2195- must be open, outbound, on the server hosting the Athena APNS

NT Service for communication with the Apple Push Notification Service

(APNS).

Port 2196- must be open, outbound, on the server hosting the Athena APNS

NT Service for communication with the Apple Push Notification Feedback

Service (APNS).

Port 5223- must be open, outbound, on any network on which iOS devices will

be confined to a WLAN and unable to access cellular data networks. For a

higher level of security, firewall rules can limit this port to the 17.0.0.0/8

address block which is assigned to Apple. 5223 can be left closed if all iOS

devices being managed have access to a cellular data network.

Port 5228- Android C2DM (using WIFI, VPN, etc.). Outbound from the

device hosting the C2DM application (Internet) to android.apis.google.com.

Note: If your site security policy dictates using different ports, please consult

Symantec for assistance.

Server Requirements

Security Group Configuration

13

Security Group Configuration Membership of the domain groups determine access to interactive Live Support

Sessions from Symantec Mobile Management Device Explorer, and security groups

for Tunnel Server. After installation, members of security groups will have Athena

Database read access. The Active Directory account of the Configuration Manger

Console user must be added to the groups.

The following is the preferred security group configuration that should be defined

before performing the installation.

Tier1 (Level 1 group for Tunnel Server)



The number determines access level - the higher the number, the more access the

group will have. Three different security groups must be created for use and can use

any name or site naming convention.

Apple Enterprise Membership Requirements If you are only using MDM (features), an APNS certificate is required and Apple

memberships are not required.

If you are developing in-house apps, the following memberships are required:

iOS Developer Enterprise Program membership- visit the following

website to become a member:

http://developer.apple.com/programs/ios/enterprise/.

This program provides the certificate that allows the use of APNS for the

Symantec Mobile MGMT agent for iOS and is the certificate used within the

Symantec Mobile Management server-side solution. The program also

provides the certificate for developing and testing an in-house developed MDM

agent.

Developer Program- visit the following website to become a member:

http://developer.apple.com/programs/ios/. This program will provide the

certificate used to sign a site-developed branded version of the Symantec

Mobile MGMT agent for submission to the Apple App Store.


SYMC Agent for iOS Requirements

SYMC Agent for iOS Requirements For Symantec Mobile MGMT agent functionality, the following certificates and

Provisioning Profile are required before installation occurs:

MDM push certificate (com.apple.mgmt). See the Certificate Signing Request

(CSR) Guide for more information.

Developer certificate. See the Prerequisites Guide for more information.

APNS Provisioning Profile for the Symantec Mobile MGMT Agent. See

the MDM Agent for iOS Development Guide for more information.

iOS Profile Security Requirements To configure server settings for iOS Profile security, the following is required:

Profile Signing Certificate- certificate used for signing on the Management

Point server (local computer) personal store. This cert is created automatically

during installation.

Profile Encryption Certificate- certificate used for encryption on the

Management Point server (local computer) personal store. This cert is created

automatically during installation.

Device Encryption Credential- credential payload containing a certificate to

be placed on devices for encryption/decryption.

Device Signing Credential- credential payload containing a certificate to be

placed on devices to validate signing.

Device Signing/Encryption Root Credential- credential payload containing

a server root certificate to be placed on devices to complete the certificate chain

for the decryption and signing validation certificates. Used only for

non-commercial CAs.

Note: See Create Security Credentials on page 54 for more information on

credential payload creation.

Server Requirements

Supported Mobile Devices

15

Supported Mobile Devices The following devices can be managed using Symantec Mobile Management for

Configuration Manager:

Android 2.1 and above.

Apple iPhone

iOS 4.1 and above

3G, 3GS, 4, 4S models

Apple iPad

iOS 4.2 and above

all models

Apple iPod Touch

iOS 4.1 and above

2nd generation, 3rd generation, 4th generation models

BlackBerry 4.3 and above

Windows Mobile 2003 for Pocket PC Phone Edition/Smartphone

Windows Mobile 5 and above for Pocket PC Phone Edition/Smartphone

206 MHz ARM or higher processor recommended

16 MB Program Memory (approximately 1.5 MB utilized by Symantec

Mobile Management)

16 MB Storage Memory (approximately 1.2 MB utilized by Symantec

Mobile Management)

Mobile Device Network Any reachable IP-based device connection including Ethernet cradle (Windows CE

devices), 802.11/WiFi, or WWAN (e.g. GSM/GPRS or EDGE, CDMA 1xRTT or

EVDO).

Note: Some WWAN providers do not pre-configure their device network settings

for reachable network IP addresses. This must be requested from the carrier or the

device network settings must be modified prior to deployment. Other WWAN

providers configure reachable IP addresses as the default for their WWAN settings.


Supported Mobile Devices

Chapter 3

Installation The Symantec Mobile Management for System Center Configuration Manager

components, which include Push Services, Console, Services, Reporting Services,

Replication Services, and optional Windows Mobile/CE Feature Packs, must be

installed in a specific order on the servers in the site environment. For multiple

server sites, the installation should be done following the site hierarchy starting

with the highest level server and then proceeding to the lower level servers.

Installation Components The Symantec Mobile Management for Configuration Manager installation

includes the following components:

Push Services- includes the APNS Web Service, Google Cloud to Device

Messaging (C2DM) Service, and Feedback Web Service. These Windows and

Web services are required for iOS and Android device management.

Console- administrator console integration components for device

management, which includes Symantec Mobile Management utilities for

interactive troubleshooting and live support, device data inventory/history

(Device Explorer), package creation (Device Software Package Wizard), and

package distribution (Software Distribution Wizard). See the Device Explorer

User Guide, Device Software Package Wizard User Guide, iOS and Android Features

User Guide, Remote Management for BlackBerry User Guide, and Package

Assignment and Distribution Guide for more information.

Services- management point integration for mobile device communication.

Includes servers and database configuration, iOS/Android setup, and the

Athena Tunnel Server installation. The Athena Tunnel Server is a secure

HTTPS tunnel which uses two-way SSL certificate-based authentication to

provide a custom connection gateway from a site to Windows Mobile,

Windows CE, BlackBerry smartphones, and Android devices.

18 Installation

Symantec Mobile Management Components Installation Order

Replication Services- creates a copy of the Athena database for recovery

purposes and provides synchronization of data across multiple database

environments. See the Replication Services Installation Guide for more

information.

Reporting Services (optional)- standard set of reports for Symantec Mobile

Management Windows Mobile/CE and BlackBerry devices and/or collections.

Additional report packs are also available for creating custom reports. See the

Reporting Services Installation Guide for more information.

Windows Mobile/CE Feature Packs (optional)- feature packs for Windows

Mobile and Windows CE devices. Includes Positioning (GPS), Phone, and

Security Essentials (Lock and Wipe) device functionality. See the Windows

Mobile/Windows CE Feature Pack Installation Guide for more information.

Symantec Mobile Management Components

Installation Order The following outline shows the server, installation order, and Symantec Mobile

Management component for installation:

Internet-facing Server

1. Push Services

Central Server

1. Console

2. ISV Proxy (first time only)

3. Services

4. Reporting Services (optional)

5. Feature Packs (Windows Mobile/CE optional)

6. Replication Services

Primary Server

1. Console

2. Services

3. Feature Packs (Windows Mobile/CE optional)

4. Replication Services

Secondary Server

1. Console (optional)

2. Services

Installation

Symantec Mobile Management Components Installation Order

19

Feature Device Support

Configuration

Manager Feature

Android BlackBerry iOS

(iPhone, iPad,

iPod Touch)

Windows

Mobile/Windows

CE

Remote Management X X X X

Inventory Reporting X X X X

Device Explorer X X X X

Device profile

distribution

(Profile Editor/

Configuration Editor)

X X

Provisioning/

Software Distribution

(Package Wizard,

Distribution Wizard)

X

Remote Control X X

Mobile Library

including content

notification to device

X X

Lock X X X

Wipe X X X

20 Installation

Push Services Installation Procedure

Push Services Installation Procedure The Push Services Installation consists of the APNS Web Service, C2DM Web

Service, and the Feedback Service.

The network topology of the site environment will determine where Push Services

are installed. Push Services must be installed on a server that has access to the

internet. Typically, this is a server that is not running Configuration Manager.

To perform the Push Services installation:

1. Locate the executable and start the installation wizard by double-clicking the

Symantec Mobile Management Push Services icon.

2. The Welcome screen appears. Click Next to run the installation wizard.

Installation


21

3. Accept the end user software license agreement and click Next to continue.

Optionally, click Print to print a hard copy of the license agreement before

continuing with the installation (only appears for first time installations).

4. Accept the default installation folder or click Change to browse and select a

different folder. When finished, click Next to continue.

22 Installation


5. Both the Feedback and Push services are selected for installation by default.

Click the components to change the installation option. When finished, click

Next to continue.

APNS Web Service Configuration

6. Click Browse and locate the APNS certificate. Then, enter the password for the

certificate. When finished, click Next to continue.

Installation


23

C2DM Web Service Configuration

An authentication token is required which will be sent to the Android Cloud to

Device Messaging (C2DM) service and then routed to the Android device. The

token is generated by the installation using the Gmail account name and password

that was created during the Android C2DM setup. See the Android Cloud to Device

Messaging (C2DM) Service Setup Guide for more information.

7. Enter the Gmail account name and password that was created during the

Android C2DM setup.

If an authentication token already exists, click No thanks, I already have one.

Note: This option only appears if a token is available.

When finished, click Next to continue.

24 Installation


Feedback Service Configuration

The iOS Feedback Service communicates with the Central server database and the

APNS Web Service to obtain a list of iOS devices that are no longer communicating

with the server.

8. Enter the names for the Central or Primary database server and the Central

database server where the APNS and C2DM Push Services reside.

If the Feedback Service is located on a different server than the Push Services,

enter the Fully Qualified Domain Name (FQDN) of the server in Server where device Push services are running.

Note: The Server where device Push services are running entry only

appears if the Push Services are installed on a different server.


Installation


25

9. Click Install to start the installation using the settings specified in the previous

steps.

10. Click Finish to exit the wizard and complete the installation. Optionally, click

Show the Windows Installer log to view the log upon exiting the wizard. The

Installer Log shows any errors or other events that occurred during the

installation.

26 Installation

Console and Services Installation Procedures


Notes: To ensure success, all requirements should be met before beginning the

installation procedure.

Configuration Manager should be installed in Mixed mode, not Native mode.

Contact Symantec support and see the Native Mode Setup Guide for more information

about Symantec Mobile Management for Configuration Manager in Native mode

environments.

The Symantec Mobile Management for Configuration Manager Console and

Services Installation consists of three parts that must be done in the following order:

1. Part 1 Console Installation on page 27.

2. Part 2 Add ISV Proxy Certificate on page 32.

3. Part 3 Services Installation on page 35.

A Configuration Manager administrator is recommended to perform the installation

as the appropriate rights and permission are required to administer the

Configuration Manager server(s). On Central/Primary servers, the installer should

also be a member of the SMS Admins security group.

Note: The installation procedures generate log files that may contain sensitive

information. To protect this information, purge the log files after the installation is

successfully completed.

Installation


27

Part 1 Console Installation The Console installation must be done for each console residing in the site

environment.

If the console is being installed on a 64bit OS (Server 2008/Server 2003/Windows

7) and the console will be used to access Live Support Session for Remote Control,

the 64bit version of the Java JRE (Java Runtime Environment) must be installed on

the desktop/server.

If the 64bit version of the Java JRE has not been installed, an error message will

appear on the Remote Control page even though Java has been installed on the

desktop/server.

If the file “JRE-{latest version}-windows-x64.exe” is not available on the

desktop/server, use the 64bit version of Internet Explorer® to browse to

www.java.com and obtain the latest 64bit version of the JRE installation.

Note: During the Console Installation, the Console should not be accessed from the

location where it is being installed.

To install the Administrator Console:

1. Locate the executable and start the installation wizard by double-clicking the

Symantec Mobile Management Console icon.

Note: For Windows Vista and Windows 7 systems, right-click on the icon and

select Run as administrator.

28 Installation


2. The Welcome screen appears. Click Next to run the installation wizard for the

Console portion of the installation.



continuing with the installation (This screen only appears for first time

installations).



Installation


29

5. Enter the fully qualified domain name of the Central server. The Symantec Mobile Management Database Name field contains the recommended name of

Athena. This entry is the database name of the Central server as the console

will pull data from the Central server.


30 Installation


6. Locate and select the Central server database by clicking Browse or type the

Central server database name.

If the current user is a Configuration Manager administrator, use the default

Windows authentication credentials of current user.

If using SQL server logins, select Server authentication using the Login ID and password below to create the SQL server login.


Installation


31

7. Click Install to start the installation of the Console using the settings specified

in the previous steps.

8. Click Finish to exit the wizard and complete the Console Installation.

Optionally, click Show the Windows Installer log to view the log upon exiting

the wizard. The Installer Log shows any errors or other events that occurred

during the installation.

32 Installation


Part 2 Add ISV Proxy Certificate The second part of the installation provides instructions for manually adding the

Symantec ISV proxy certificate (provided by Symantec) to the Configuration

Manager Console.

Note: This procedure should be performed on all Central and Primary servers in the

site hierarchy.

For messages sent from Athena Web Services to be authenticated by Configuration

Manager, an ISV (Independent Software Vendor) proxy certificate is required. The

certificate (odyssey-athena-sccm.cer) enables devices running Symantec Mobile

Management to communicate securely with the Management Point by validating

that they are Symantec devices.

To add the certificate to the Configuration Manager Console:

1. Access the Configuration Manager Console.

2. Expand Site Database > Site Management > yoursitename > Site Settings > Certificates.

3. Right-click ISV Proxy and select Register or Renew ISV Proxy.

Installation


33

4. On the certificate registration or renewal screen, select Register certificate for a new ISV proxy.

34 Installation


5. Click Browse to locate and select the ISV proxy certificate that is provided by

Symantec. The Administrator Console Installation automatically places the

certificate in the C:\Program Files (x86)\Odyssey Software\Athena\SCCM

folder by default. If you have installed the console to another location, the

certificate will be located in that installation folder.

6. Click Apply.

7. Click OK to exit the screen. The certificate is added and can be viewed in the

ISV proxy pane. This completes part 2 of the installation.

Installation


35

Part 3 Services Installation The Services Installation is done on all (one or multiple) Management Point servers

to which the devices are reporting. For multiple server sites, the Services

installation should be done following the site hierarchy. For example, starting with

the highest level server and then proceeding to the lower level servers. See

Symantec Mobile Management Components Installation Order on page 18 for more

information.

Note: The computer account must have system administrator access to the database

server for creation of the Athena database and permissions assignment.

The following steps must be done on each Configuration Manager server:

1. Log in as a Configuration Manager administrator.

2. On each Configuration Manager server, locate the executable and start the

installation wizard by double-clicking the Symantec Mobile Management Services icon.

3. The Welcome screen appears. Click Next to run the installation wizard for the

Services portion of the Symantec Mobile Management for Configuration

Manager installation.

36 Installation


4. Both the Tunnel Server and Symantec Mobile Management Services are

selected for installation by default. Click the Tunnel Server and/or Symantec Mobile Management Services components to change the installation options.

Note: The Tunnel Server is required. If not installing the Tunnel Server at this

point or server location, it must be installed on another server located in the

Configuration Manager site environment.

Optionally, click Change to browse and select a different folder.

Optionally, click Space to view the disk space that is required for the

selected option(s).


Installation


37



continuing with the installation (This screen only appears for first time

installations).



38 Installation


7. For Tunnel Sever component installation, enter the names of the three security

groups that were created for use with Tunnel Server. A different group must be

used for each level. The entries must be WINS names in the format

domain\group name. For example, e3qa\atier1.

Note: Level 1 has the least rights, while Level 3 has the most rights. See

Security Group Configuration on page 13 for more information.


Installation


39

8. Depending on the topology of the site, select the server type:

Central server (default)- Root Primary server.

Secondary server- does not have a database. This is the server where the

Athena Web Services are installed.


40 Installation


9. The Site Code field is populated with the three character alphanumeric code of

the Management Point server. Enter the following:

SCCM Database- name of the SCCM database.

SCCM Database Server- name of the server where the SCCM database

resides.


Installation


41

10. Review the default values for the following options. Make any changes as

required for the site:

Management Point Address- IP address of server. Typically this entry is

the address of the Central server or the Primary server (when installing on

a Primary server).

Note: The http:// prefix is not automatically pre-pended to the IP address, so

it must be entered with the IP address when a server is running DHCP. For

example, a valid entry is http://192.168.1.101. If http:// is not entered, the

correct Management Point address will not be written to the Athena

web.config file and DCOM will be used to communicate, which is problematic.

Management Point Port- port of the server that is specified in the

Management Point Address field. Typically, the entry is port 80.

EndPoint Server Name- name of the Management Point server.

DNS Suffix– specifies the DNS suffix that managed devices use to connect

to the server. This setting is not required for WINS.

Note: Run the ipconfig /all command in a command window to view the DNS

suffix of the server.

Log to EventLog– when selected, specifies when the Athena Device

Tracker (Tracker) service logs run time errors to the server Event Log

under the Athena application group. Used by Athena Tracker and Web

Services.

Log to DeviceLog Table- when selected, specifies when Tracker service

writes run time errors and run time status messages to the Athena

database DEVICELOG table. Used by Athena Tracker and Web Services.

42 Installation


Derive Device Name From Host Name– determines whether the custom

parsing logic within the Athena Tracker service is used to derive the

Device Name property from the DNS Host Name attribute passed to the

device from a DHCP server.

Derive Device Name From Phone Number– (Phone devices only)

determines whether the custom parsing logic within the Athena Tracker

service is used to derive the Device Name property from the device(s)

Phone Number attribute.


Installation


43

11. The Device Agent Server Configuration screen is used to configure secure

server connections (SSL) for iOS and Android device communication.

The Agent (iOS and Android) entries configure the Symantec Mobile MGMT

agent:

Using SSL protocol- select to enable SSL.

Server Name- name of the server where devices communicate. This entry

can be an IP address, machine name, or FQDN. The default is the server

where the installation is being performed.

Port Override- port to use for SSL connections. The default is 443.

The iOS MDM (SSL) entries configure a separate port for the native Apple iOS

agent:

Server Name- name of the server where devices communicate. This entry

can be an IP address, machine name, or FQDN. The default is the server

where the installation is being performed.

SSL Port Override- port to use for SSL connections. The default is 444. If

this entry is left blank, the default SSL port 443 is used.

Certificate- select the server SSL certificate from the drop-down list.


44 Installation


12. Enter the server name where Push Services reside.

The C2DM email field is the Gmail address that was set up in the Android

C2DM setup procedure and also entered in the C2DM Web Services

installation. See the C2DM Web Service Configuration on page 23 for more

information.


Installation


45

13. Devices typically communicate with the Mobile Library proxy on a Secondary

server. The proxy communicates with the actual Mobile Library via web

services. Enter the server name where the Mobile Library proxy resides.


46 Installation


14. The Symantec Mobile Management Database Name entry is populated with

the recommended name Athena. This entry must match the Symantec Mobile

Management Database Server that will be entered on the next screen of the

installation wizard.

Select Use existing database for Central or Primary server installations

if planning to create the database manually or preserve existing device

information when performing an upgrade or re-installation.

Note: This option is not available when installing Secondary servers.

Update packages from central database server- selected by default

when installing a Primary server. When selected, this setting will get

package updates from the Central database server. For example, when

installing a new Primary server in an existing site hierarchy, this option

will copy all packages (system and user-defined) from the existing Central

server.

Note: This option is not available when installing Central or Secondary

servers.

Installation


47

Enter the Central Database Server name when installing a Primary

server. This entry should be a fully qualified domain name.

Note: This option is not available when installing Central or Secondary

servers.


15. A list of servers is populated by default in the Symantec Mobile Management

Database Server drop-down list. Select the database server where the Athena

Database is located or will reside.

When using a Secondary server, the database server must be the database of the

Primary (parent) server of this Secondary server.

Note: If the drop-down list does not contain any entries, locate and select the

SQL server on this domain by clicking Browse or type the server name.

If the current user is a Configuration Manager administrator, accept the default

of Windows authentication credentials of current user. If not, select Server authentication using the Login ID and password below and see Using a

Non-Domain Admin Account for Installation procedure on page 88.


48 Installation


16. On the Product License screen, select You have purchased a license and want to install it if you have purchased a license for the software. Leave this

option unchecked if you are using a trial license.

Perform one of the following steps:

If the SLF resides on the server, select Browse to your SLF and click

Browse to locate the file.

OR

If the server has access to the internet, click Provide information for the Licensing Server and enter all information.


Installation


49

17. Click Install to start the installation of the Services using the settings specified

in the previous steps.

18. Click Finish to complete the installation and exit the wizard. The Services

installation portion of the Symantec Mobile Management for Configuration

Manager is now complete.

19. Perform the procedures in the Set Up Profiles for iOS Devices chapter

beginning on page 51.

20. Optionally, perform the DNS Text Record Setup for Android and iOS Services

procedure on page 99. This allows users to enroll iOS or Android devices using

their individual e-mail addresses.

Note: The installation procedures generate log files that may contain sensitive

information. To protect this information, purge the log files after the

installation is successfully completed.

50 Installation


Chapter 4

Set Up Profiles for iOS Devices

The Signing and Encryption and Enrollment MDM Profiles are created during the

Services installation. These system-created profiles are required for securing iOS

devices and automatically display in the Profiles list for configuration with your

site-specific credentials information. Once configured, the profiles will be

automatically distributed to iOS devices.

View Profiles

To view profiles:

1. Access the Configuration Manager Console, and expand Site Database > Computer Management > Mobile Device Management > Symantec Mobile Management.

2. Select Profiles. The Profiles list displays. Profiles are managed from the

Profiles list. For more information, see the iOS and Android Features User Guide.

The following default iOS Profiles display in the list:

iOS Signing and Encryption Profile- used to sign configuration profiles

(which prevents third-party tampering) and for iOS devices to recognize

signed profiles. This profile is automatically assigned to devices when

Signed and/or Encrypt is selected for an iOS profile.

The iOS Signing and Encryption Profile also contains the root certificate

to complete the certificate chain for the decryption and signing validation

certificates.

52 Set Up Profiles for iOS Devices

Configure iOS Signing and Encryption Profile

Enrollment MDM Profile- used to identify an iOS device and allow the

device to enroll in Configuration Manager. A credential payload that

contains signing and encryption keys must be created and added to this

iOS Profile. See Create Security Credentials on page 54 for more

information.

Configure iOS Signing and Encryption Profile The iOS Signing and Encryption Profile is assigned to devices when Sign and/or

Encrypt profile is specified for an iOS profile and is distributed with the new profile

automatically.

To edit the profile:

1. Right-click the profile and click Edit. The Profile Editor displays.


Configure iOS Signing and Encryption Profile

53

2. Select the following certificates for the site:

Root Certificate- self-signed. This server certificate is associated with the

Signing and Encryption Certificates if using a site-created certificate and

not a commercial CA, such as VeriSign.

Signing Certificate Public- complementary Signing Certificate with

Public Key. This certificate allows devices to recognize and accept profiles

signed using the Signing Cert with Private and Public Keys.

Encryption Certificate Public-Private- allows devices to decrypt and

install profiles that were encrypted using the Encryption Certificate with

Public Key.


Create Security Credentials

Create Security Credentials Private keys, and an Encryption Certificate with Public key are required to sign and

encrypt profiles sent to iOS devices. For this reason, security credentials or payloads

for devices with the complementary Signing Certificate with Public Key, and

Encryption Certificate with Public and Private keys must be created and distributed

to devices.

After creating the security credentials, they can be added to the Enrollment MDM

Profile. The Enrollment MDM Profile will be automatically assigned to iOS devices

during the enrollment process.

Configuring security credentials and distributing with the Enrollment MDM

Profile is typically the method used for sites using SSL for communication or for

sites that are using more than one root certificate.

Root or Signing with Public Key A credential payload with the Root Certificate associated with the Signing and

Encryption Certificates must be created if not using a commercial CA.

To create the Root credential:

1. In Configuration Manager, expand Site Database > Computer Management > Mobile Device Management > Symantec Mobile Management.

2. Expand Profiles.



55

3. Select Configuration Editor. Payloads are defined for profiles using the

Configuration Editor. For more information, see the iOS and Android Features

User Guide.

4. When the Configuration Editor opens, select iOS Configuration.

5. Select Credentials.

6. Click to create a new credential.

7. Click Select cert file, browse to the location of the Root or Signing Certificate

with Public Key, and open the file.



8. Enter the Credential Name and Description. Make sure to use a descriptive

name to make it easy to identify.

9. Click Save Changes. The Root credential is created and displays in the iOS

Configuration pane.



57

Encryption A credential payload with the Encryption Certificate must be created if not using a

commercial CA.

To configure the Encryption credential:

1. In Configuration Manager, expand Site Database > Computer Management > Mobile Device Management > Symantec Mobile Management.

2. Expand Profiles.

3. Select Configuration Editor.

4. When the Configuration Editor opens, select iOS Configuration.

5. Click Credentials.

6. Click to create a new credential.

7. Click Select cert file, browse to the location of the Encryption Certificate and

open the file.

8. Enter the Credential Name and Description.

9. Enter a Password for the certificate. This is an optional entry.

10. Click Save Changes. The Encryption credential is created and displays in the

iOS Configuration pane.

11. Close the Configuration Editor.


Configure MDM Enrollment Profile

Configure MDM Enrollment Profile The Enrollment MDM Profile identifies iOS devices and allows enrollment in

Configuration Manager. The Security Credentials that were configured in the

Create Security Credentials procedure on page 54 will be added to this profile.

To configure the MDM Enrollment Profile:

1. Expand Site Database > Computer Management > Mobile Device Management > Symantec Mobile Management.

2. Select Profiles. The Profiles list displays.

3. Right-click the Enrollment MDM Profile and click Edit.



59

The following information displays:

Profile Name, Description, and Organization.

Push Certificate Subject- App ID Bundle Identifier or Topic which

allows the use of MDM commands. This entry is not editable.

4. Select the configured SCEP Server credential or VPN for the Cryptographic credential used for authentication.

5. Select the Security Credentials payloads from Profile Content Items.

6. Click Save. The profile is now configured and will be assigned to iOS devices

during enrollment.



Chapter 5

Enrolling Devices The Enrollment Process registers iOS (iPhone, iPad, iPod Touch) or Android

devices in Configuration Manager. Once a device is enrolled, it can be viewed and

managed using the Configuration Manager Console. See the iOS and Android

Features User Guide for more information about using these devices in Configuration

Manager.

Authentication for Agent Enrollment For agent authentication to occur, the Enrollment Web Configuration file must be

edited to enable authentication (ON).

To turn on Agent Enrollment authentication:

1. Locate and open the C:\Program Files (x86)\Odyssey

Software\Athena\SCCM\Web\Enrollment\web.config file in a text editor.

2. Make the following changes to the values in the file:

<add key="SCCM-iOSAuthenticate" value="true" />

<add key="SCCM-ActiveDirectoryServer" value="servername" />

<add key="SCCM-DomainName" value="domainname" />

<add key="SCCM-DomainExtension" value="local" />

<add key="SCCM-RequireDomain" value="false" />

<add key="SCCM-AndroidAuthenticate" value="true" />

62 Enrolling Devices

iOS Device

iOS Device Before enrollment can be done, the Symantec Mobile MGMT agent must be

installed on devices.

Install Symantec Mobile MGMT Agent

To install the Mobile MGMT agent on a device:

1. Open Safari from the device Home screen.

2. Enter the URL to download the Mobile MGMT agent (iOS agent).

3. Touch the Install Symantec Mobile MGMT link. After the Symantec Mobile

MGMT agent installation is completed successfully, the Mobile MGMT icon

appears on the iPhone, iPad or iPod Touch Home screen.

Enrolling Devices

iOS Device

63

Enroll iOS device

To enroll an iOS device:

1. Touch the Symantec Mobile MGMT agent icon to begin enrollment of the

device.

2. Enter following information on the Symantec Mobile MGMT agent screen:

URL for initiating enrollment-

http://<servername>/Athena/Enrollment/athenaiosenroll.html

OR

Email Address- if DNS text records have been defined for iOS enrollment,

enter a company email address, for example [email protected]. See

DNS Text Record Setup on page 99 for more information.

When finished, touch Enroll.


iOS Device

3. Enter your username and password.

Note: You may also be prompted to enter a domain.

4. Touch Yes if the device is company owned or No if it is a personal device.

5. When finished, touch Enroll.

Enrolling Devices

iOS Device

65

6. If prompted, touch OK on the Current Location screen to enable tracking on

the device. This allows the agent to send location data with inventory to the

server.

Note: After the device is enrolled, tracking can be disabled by accessing

Settings > Location Services on the device.

7. Touch Accept to accept the End-User License Agreement (EULA).


iOS Device

8. Touch Install to install the MDM Enrollment Profile or before installing, touch

More Details to view more information about the MDM Enrollment Profile.

9. Touch Install on the warning screen to continue with the installation.

Enrolling Devices

iOS Device

67

10. On the Profile Installed screen, click Done.

After successful completion of MDM Enrollment and SCEP Profile installation on

the device, the iOS device checks in to the server. Additional profiles may be sent to

the device such as VPN settings, restrictions, or Exchange server settings.

The server also sends the schedule for when the Mobile MGMT agent will report

device inventory to the server, the URL to which the Mobile MGMT agent reports,

and a URL for the Mobile Library. When all of these steps are complete, the device is

successfully enrolled.

To view the Enrollment and Agent Provisioning Profiles, access Settings > Profiles on the iOS device.


Android Device

Android Device

To enroll an Android device:

1. On the device, access a browser.

2. Enter the URL to download and install the Symantec Mobile MGMT agent to

the Android device.

3. Once installed, locate and touch the Mobile MGMT icon on the Android device

screen to access the Symantec Mobile MGMT agent.

Enrolling Devices

Android Device

69

4. Enter and select the following information on the initial Mobile

MGMT-Enroll Screen:

URL for initiating enrollment-

http://<servername>/Athena/Enrollment/AthenaAndroidEnroll.aspx

OR

Email Address- if DNS text records have been defined for Android

enrollment, enter a company email address, for example

[email protected].

Require SSL- select this option.

Accept all SSL certificates- select this option.

When finished, touch Submit.


Android Device

5. Enter Domain (if prompted), Username, and Password credentials.

When finished, touch OK.

6. Touch Corporate Device? to select this option if the device is company owned.

7. Click Submit.

Enrolling Devices

Android Device

71

8. At the prompt for accepting the End-User License Agreement (EULA), touch

OK.

9. Touch Agree to EULA to select this option and touch Submit. Once the

enrollment processing finishes successfully, the Android device is enrolled.


Android Device

Authorizing the Symantec Mobile MGMT Agent for Device Administrator Privileges

After Enrollment, a Security Action Required notification will display for activation.

This occurs because administrator privileges are required for the Mobile MGMT

agent to lock, wipe, reset password or set password policies on the Android device.

Note: This screen only appears the first time the device is enrolled.

To view the application notification and activate administrator privileges:

1. Select the icon in the upper right and drag down.

2. Select Security Action Required.

3. Select Activate. This will activate device administrator privileges for the

Symantec Mobile MGMT agent.

Chapter 6

Registering Devices Windows Mobile, Windows CE, and BlackBerry smartphone devices are registered

to the server by accessing the Locate Site Server web page via Internet Explorer on

the device. The registration process is automatic. iOS and Android are registered

during the enrollment process. See Enrolling Devices on page 61 for more

information.

Note: The screens and prompts for Locate Site Server and will vary between devices

and operating systems.

The following prerequisites are required for registering devices:

Device connected to the network.

Device communicating with a reachable Management Point that has

Athena Services.

Resolve the server by name with WINS and DNS.

Note: Referencing the server by IP is not sufficient.

74 Registering Devices

Windows Mobile and Windows CE Devices


To register a Windows Mobile or Windows CE device:

1. On the device, access Internet Explorer.

2. Enter http://<Central Server name>/deviceupdates to access the Locate

Site Server web page.

3. Tap Continue.

Note: For devices running Windows CE .Net, Windows Mobile .Net Compact

Framework 2.0 (.NETCF) must be installed.

Registering Devices


75

4. Tap Yes to download the LocateSiteServer.CAB file and install Symantec

Mobile Management.



5. Select the location for the installation, then tap Install. In most cases, select the

default location. The installation is finished and the device is registered when

the device returns to the desktop screen.

Note: This screen may vary depending on the device and available storage

areas.

Registering Devices

BlackBerry Smartphones

77


To register a BlackBerry smartphone:

1. On the device, access a browser.

2. Enter http://<Central Server name>/deviceupdates to access the Locate

Site Server web page.

3. Tap Download to download and install the Athena client.

4. Click OK to complete the registration procedure.



Chapter 7

Device Licenses Device Licenses provides a graphic and chart that illustrates the site environment's

deployed devices and indicates if the number of device licenses has exceeded the

maximum number of available device licenses.

View License Information To view device license information:

1. Select Site Database > Computer Management > Mobile Device Management > Symantec Mobile Management.

2. Select Device Licenses. The current license information displays in the

console.

80 Device Licenses

License Warning Dialog

License Warning Dialog If device licenses are not valid or have expired (non-compliant), a warning message

will display in the console when certain actions are done. For example when creating

a new software package for Windows Mobile/CE devices.

To dismiss the warning dialog, click OK.

Chapter 8

View Devices in Collections After registration or enrollment, devices are automatically populated in the built-in

collections available in the Configuration Manager Console.

iOS Device (iPhone, iPad, iPod Touch)

To view an iOS device in the Configuration Manager Console:

1. Access the Configuration Manager Console and expand Site Database > Computer Management > Collections > All Apple Mobile Devices.

2. Click Update Collection Membership in the Actions pane.

3. On the dialog that displays, select Update subcollection membership, then

click OK. The collection is updated and shows the newly registered iOS devices.

82 View Devices in Collections

Android Device

Android Device

To view an Android device in the Configuration Manager Console:

1. Access the Configuration Manager Console and expand Site Database > Computer Management > Collections > All Android Mobile Devices.



click OK. The collection is updated and shows the newly registered Android

devices.

View Devices in Collections

Windows Mobile or Windows CE Device

83

Windows Mobile or Windows CE Device

To view a Windows Mobile or CE device in the Configuration Manager Console:

1. Access the Configuration Manager Console and expand Site Database > Computer Management > Collections > All Windows Mobile Devices.

Note: The All Windows Mobile collection is a built-in collection which

automatically contains all types of devices (i.e. BlackBerry smartphone,

Windows Mobile, iPad, etc.) by default. See Query for All Windows Mobile

Devices Collection on page 90 for more information.



click OK. The collection is updated and shows the newly registered Windows

devices.

84 View Devices in Collections

BlackBerry Smartphone

BlackBerry Smartphone

To view a BlackBerry smartphone in the Configuration Manager Console:

1. Access the Configuration Manager Console and expand Site Database > Computer Management > Collections > All BlackBerry Mobile Devices.



click OK. The collection is updated and shows the newly registered Blackberry

smartphones.

Chapter 9

Configuring Device Ownership You can specify if a registered Windows Mobile/Windows CE or BlackBerry

smartphone is company owned (Corporate) or employee owned (Personal). This

allows devices in the enterprise to be managed differently according to ownership.

Set Ownership

Windows Mobile/Windows CE To set ownership for a Windows Mobile or Windows CE device:

1. Access the Configuration Manager Console and expand Site Database > Computer Management > Collections > All Windows Mobile Devices.

2. Right-click a device in the collection and select Symantec Mobile Management > Set Ownership.

3. Depending on the device owner, select either Corporate for company owned

device or Personal for an employee owned device.

4. Click OK.

86 Configuring Device Ownership

Set Ownership

BlackBerry Smartphone To set ownership for a BlackBerry smartphone:

1. Access the Configuration Manager Console and expand Site Database > Computer Management > Collections > All BlackBerry Mobile Devices.

2. Right-click a smartphone in the collection and select Symantec Mobile Management > Set Ownership.

3. Depending on the smartphone owner, select either Corporate for company

owned smartphone or Personal for an employee owned smartphone.

4. Click OK.

Chapter 10

Additional Procedures The procedures in this chapter include optional procedures that are used to

configure the site environment after Symantec Mobile Management for

Configuration has been successfully completed. The sections in this chapter discuss

the following topics:

Using a Non-Domain Admin Account for Installation

Enabling ASP.Net in IIS

Query for All Windows Mobile Devices Collection

DNS Text Record Setup for Android and iOS Services

88 Additional Procedures

Using a Non-Domain Admin Account for Installation

Using a Non-Domain Admin Account for

Installation This procedure is done at step 15 during the Services Installation. If the current user

performing the installation is not a domain or Configuration Manager administrator,

have a domain or Configuration Manager administrator perform a re-installation or

perform the following SQL server authentication steps on each Configuration

Manager server.

Note: This procedure is not recommended, as the best practice is to have a domain

or Configuration Manager administrator perform the installation.

When using SQL Server Logins, you must create a blank Athena database to

properly assign the Athena SQL server.

1. Log in with the appropriate authority to perform these database administration

tasks.

2. Create the Athena database using all of the default settings.

3. Modify the Athena SQL Server Login on the Configuration Manager server:

On the General tab (node), the Default Database should be Athena.

On the Server Roles tab (node), select the Public and sysadmin role check

boxes. The sysadmin role is needed by the installation to create the

Athena_Purge job in the SQL Server agent.

On the User Mappings tab (node), select the check box for Athena in the

top section and check box for the role db_owner in the lower section.

Note: Public should be selected.

4. Click OK.

5. Return to step 15 on page 47 of the Services installation procedure and finish

the installation.

Additional Procedures

Enabling ASP.Net in IIS

89

Enabling ASP.Net in IIS This procedure enables ASP.Net 2.0 in IIS.

To enable ASP.Net in IIS:

1. Access the Windows command prompt.

2. Enter the following command:

Windows\Microsoft.Net\Framework\V2.0.50727\aspnet_regiis.exe –i

3. Access the IIS Console by selecting Start > Administrative Tools > Internet Information Services (IIS) Manager.

4. Expand the site and select Web Service Extensions.

5. Ensure that ASP.Net v2.0 is set to Allowed.



Query for All Windows Mobile Devices Collection This procedure adds the query string for the All Windows Mobile Devices

collection so that only Windows Mobile devices appear in the collection. The All

Windows Mobile collection is a built-in collection which automatically contains all

types of devices (i.e. BlackBerry smartphone, iPhone, iPad, etc.) by default.

To add the query string:

1. Access the Configuration Manager Console.

2. Expand Site Database > Computer Management > Collections.

3. Right-click the All Windows Mobile Devices collection and select Properties.



91

4. Click the Membership Rules tab.

5. Double click the All Windows Mobile Devices membership rule.

OR

Click .



6. Click Edit Query Statement.



93

7. Click the Criteria tab.



8. Click Show Query Language to display the current query.



95

9. Select or delete the displayed query.



10. Enter the following query:

select

SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,

SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,

SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client

from SMS_R_System where SMS_R_System.ResourceType = 5 and

SMS_R_System.ClientType = 3 and

SMS_R_System.OperatingSystemNameandVersion like "Windows%"

11. When finished, click OK.



97

12. Click OK to exit the Query Rule Properties dialog.



13. Click OK to exit the collection properties dialog and return to the

Configuration Manager Console.

To verify that the new query is working correctly:

1. In the Configuration Manager Console, click Update Collection Membership

in the Actions pane.

2. Right-click Collections and then select Refresh or click Refresh in the Actions

pane.

3. Open the Windows Mobile Devices collection. Only Windows Mobile devices

should now appear in the collection.



99

DNS Text Record Setup for Android and iOS

Services This procedure contains the steps for setting up the Text Tag (TXT record) in DNS

which maps the Mobile MGMT agent for iOS or Android enrollment URL. This

allows users to enroll iOS or Android devices using their individual e-mail

addresses.

To set up the Text record in DNS:

1. Log in to the Domain Controller.

2. Access Start > Administrative Tools > DNS to run the DNS utility.



3. From the DNS Window, navigate to the domain folder.



101

4. Right-click the domain folder and select Other New Records.



5. On the Resource Record Type dialog, select Text (TXT) from the list.

6. Click Create Record.



103

7. Leave the Record name field blank.

8. Enter the following entry in the Text field for either iOS (following) or

Android (next page).

For iOS:

OSIAGENTREGURL=http://<site server IP address or

FQDN servername>/Athena/Enrollment/AthenaIosEnroll.aspx

Note: The best practice is to use the FQDN of the server and use SSL (https)

for enrollment.

Example:

http://mscentral.ms1qa.local/Athena/Enrollment/AthenaIosEnroll.aspx



For Android:

android-mdm-enroll=http://<site server IP address or

FQDN servername>/Athena/Enrollment/AthenaAndroidEnroll.aspx

Note: The best practice is to use the FQDN of the server and use SSL (https)

for enrollment.

Example:

http://mscentral.ms1qa.local/Athena/Enrollment/

AthenaAndroidEnroll.aspx

9. Click OK to create the Text Record. The setup procedure is now complete.

Appendix

Symantec Mobile Management for Configuration Manager 7.2 Third-Party Legal Notices

Third-Party Legal Attributions This Symantec product contains third party software for which Symantec is

required to provide attribution (“Third Party Programs”). Some of the Third Party

Programs are available under open source or free software licenses. The License

Agreement accompanying the Software does not alter any rights or obligations you

may have under those open source or free software licenses. This appendix contains

proprietary notices for the Third Party Programs and the licenses for the Third

Party Programs, where applicable.

Microsoft Microsoft®, Windows®, Windows Mobile®, Active Directory®, Windows Vista®,

Windows Server®, ActiveX®, Internet Explorer®, SQL Server®, and ActiveSync®

are registered trademarks of Microsoft Corporation in the United States and other

countries.

Bing™ is a trademark of Microsoft Corporation in the United States and other

countries.

106 Appendix

Apple Apple®, Mac®, Mac OS®, iPhone®, iPad®, iPod Touch®, iPod®, FaceTime®, and

iTunes® are registered trademarks of Apple Inc., registered in the United States and

other countries.

Sun Microsystems Sun and Sun Microsystems are trademarks or registered trademarks of Sun

Microsystems, Inc. in the United States and other countries.

Research In Motion BlackBerry® is a registered trademark of Research In Motion Limited.

Google Google™, Android™, and YouTube™ are trademarks of Google Inc.

NitroDesk TouchDown™ is a trademark of NitroDesk, Inc.

Mozilla Firefox® is a registered trademark of Mozilla.

Expat 1.2 Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center, Ltd

Permission is hereby granted, free of charge, to any person obtaining a copy of this

software and associated documentation files (the "Software"), to deal in the Software

without restriction, including without limitation the rights to use, copy, modify,

merge, publish, distribute, sublicense, and/or sell copies of the Software, and to

permit persons to whom the Software is furnished to do so, subject to the following

conditions:

The above copyright notice and this permission notice shall be included in all copies

or substantial portions of the Software.

Appendix

107

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO

THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT

SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR

ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN

ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT

OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR

OTHER DEALINGS IN THE SOFTWARE

jQueryjs 1.4.1 Copyright (c) 2011 John Resig, http://jquery.com/

Permission is hereby granted, free of charge, to any person obtaining a copy

of this software and associated documentation files (the "Software"), to deal

in the Software without restriction, including without limitation the rights to

use, copy, modify, merge, publish,

distribute, sublicense, and/or sell copies of the Software, and to permit

persons to whom the Software is furnished to do so, subject to the following

conditions:

The above copyright notice and this permission notice shall be included in all

copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT

LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR

COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES

OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN

CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER

DEALINGS IN THE SOFTWARE.

108 Appendix

Libjpeg 6b This software is based in part on the work of the Independent JPEG Group. This

software is copyright (C) 1991-2012, Thomas G. Lane, Guido Vollbeding. All

Rights Reserved except as specified below.

Log4Net 1.2.10 Licensed under the Apache License, Version 2.0 (the "License"); you may not use

this file except in compliance with the License. You may obtain a copy of the License

at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under

the License is distributed on an "AS IS" BASIS. WITHOUT WARRANTIES OR

CONDITIONS OF ANY KIND, either expressed or implied. See the License for the

specific language governing permissions and limitations under the License.

Newlib 1.17.0 The newlib subdirectory is a collection of software from several sources.

Each file may have its own copyright/license that is embedded in the source file.

Unless otherwise noted in the body of the source file(s), the following copyright

notices will apply to the contents of the newlib subdirectory:

(1) Red Hat Incorporated

Copyright (c) 1994-2009 Red Hat, Inc. All rights reserved.

This copyrighted material is made available to anyone wishing to use, modify, copy,

or redistribute it subject to the terms and conditions of the BSD License. This

program is distributed in the hope that it will be useful, but WITHOUT ANY

WARRANTY expressed or implied, including the implied warranties of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. A copy

of this license is available at http://www.opensource.org/licenses. Any Red Hat

trademarks that are incorporated in the source code or documentation are not

subject to the BSD License and may only be used or replicated with the express

permission of Red Hat, Inc.

(2) University of California, Berkeley

Copyright (c) 1981-2000 The Regents of the University of California.

All rights reserved.

http://www.apache.org/licenses/LICENSE-2.0

http://www.opensource.org/licenses

Appendix

109

Redistribution and use in source and binary forms, with or without modification, are

permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list

of conditions and the following disclaimers.

Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/or

other materials provided with the distribution.

Neither the name of the University nor the names of its contributors may be

used to endorse or promote products derived from this software without

specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS "AS IS"

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY

AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO

EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE

USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

SUCH DAMAGE.

(3) David M. Gay (AT&T 1991, Lucent 1998)

The author of this software is David M. Gay.

Copyright (c) 1991 by AT&T.

Permission to use, copy, modify, and distribute this software for any purpose

without fee is hereby granted, provided that this entire notice is included in all

copies of any software which is or includes a copy or modification of this software

and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS

OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR

NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY

KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR

ITS FITNESS FOR ANY PARTICULAR PURPOSE.

-------------------------------------------------------------------

The author of this software is David M. Gay.

110 Appendix

Copyright (C) 1998-2001 by Lucent Technologies

All Rights Reserved

Permission to use, copy, modify, and distribute this software and its documentation

for any purpose and without fee is hereby granted, provided that the above copyright

notice appear in all copies and that both that the copyright notice and this

permission notice and warranty disclaimer appear in supporting documentation, and

that the name of Lucent or any of its entities not be used in advertising or publicity

pertaining to distribution of the software without specific, written prior permission.

LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS

SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL LUCENT OR

ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR

CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER

RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN

ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,

ARISING OUT OF OR IN CONNECTION WITH THE USE OR

PERFORMANCE OF THIS SOFTWARE.

(4) Advanced Micro Devices

Copyright 1989, 1990 Advanced Micro Devices, Inc.

This software is the property of Advanced Micro Devices, Inc (AMD) which

specifically grants the user the right to modify, use and distribute this software

provided this notice is not removed or altered. All other rights are reserved by

AMD.

AMD MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,

WITH REGARD TO THIS SOFTWARE. IN NO EVENT SHALL AMD BE

LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN

CONNECTION WITH OR ARISING FROM THE FURNISHING,

PERFORMANCE, OR USE OF THIS SOFTWARE.

So that all may benefit from your experience, please report any problems or

suggestions about this software to the 29K Technical Support Center at:

800-29-29-AMD (800-292-9263) in the USA, or 0800-89-1131 in the UK, or

0031-11-1129 in Japan, toll free. The direct dial number is 512-462-4118.

Advanced Micro Devices, Inc.

29K Support Products

Mail Stop 573

5900 E. Ben White Blvd.

Austin, TX 78741

800-292-9263

(5) C.W. Sandmann

Appendix

111

Copyright (C) 1993 C.W. Sandmann

This file may be freely distributed as long as the author's name remains.

(6) Eric Backus

(C) Copyright 1992 Eric Backus

This software may be used freely so long as this copyright notice is left intact.

There is no warrantee on this software.

(7) Sun Microsystems

Copyright (C) 1993 by Sun Microsystems, Inc. All rights reserved.

Developed at SunPro, a Sun Microsystems, Inc. business. Permission to use, copy,

modify, and distribute this software is freely granted, provided that this notice is

preserved.

(8) Hewlett Packard

(c) Copyright 1986 HEWLETT-PACKARD COMPANY

To anyone who acknowledges that this file is provided "AS IS” without any express

or implied warranty: permission to use, copy, modify, and distribute this file for any

purpose is hereby granted without fee, provided that the above copyright notice and

this notice appears in all copies, and that the name of Hewlett-Packard Company not

be used in advertising or publicity pertaining to distribution of the software without

specific, written prior permission. Hewlett-Packard Company makes no

representations about the suitability of this software for any purpose.

(9) Hans-Peter Nilsson

Copyright (C) 2001 Hans-Peter Nilsson

Permission to use, copy, modify, and distribute this software is freely granted,

provided that the above copyright notice, this notice and the following disclaimer

are preserved with no changes.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND WITHOUT ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE.

(10) Stephane Carrez (m68hc11-elf/m68hc12-elf targets only)

Copyright (C) 1999, 2000, 2001, 2002 Stephane Carrez ([email protected])

The authors hereby grant permission to use, copy, modify, distribute, and license

this software and its documentation for any purpose, provided that existing

copyright notices are retained in all copies and that this notice is included verbatim

in any distributions. No written agreement, license, or royalty fee is required for any

of the authorized uses. Modifications to this software may be copyrighted by their

authors and need not follow the licensing terms described here, provided that the

new terms are clearly indicated on the first page of each file where they apply.

112 Appendix

(11) Christopher G. Demetriou

Copyright (c) 2001 Christopher G. Demetriou




1. Redistributions of source code must retain the above copyright notice, this list

of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this



3. The name of the author may not be used to endorse or promote products

derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR `ÀS IS'' AND ANY

EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED

TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS

FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,

BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

(12) SuperH, Inc.

Copyright 2002 SuperH, Inc. All rights reserved

This software is the property of SuperH, Inc (SuperH) which specifically grants the

user the right to modify, use and distribute this software provided this notice is not

removed or altered. All other rights are reserved by SuperH.

SUPERH MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,

WITH REGARD TO THIS SOFTWARE. IN NO EVENT SHALL SUPERH BE

LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL

DAMAGES IN CONNECTION WITH OR ARISING FROM THE

FURNISHING, PERFORMANCE, OR USE OF THIS SOFTWARE.

So that all may benefit from your experience, please report any problems or

suggestions about this software to the SuperH Support Center via e-mail at

[email protected] .

Appendix

113

SuperH, Inc.

405 River Oaks Parkway

San Jose

CA 95134

USA

(13) Royal Institute of Technology

Copyright (c) 1999 Kungliga Tekniska HÃ¶gskolan

(Royal Institute of Technology, Stockholm, Sweden).









3. Neither the name of KTH nor the names of its contributors may be used to

endorse or promote products derived from this software without specific prior

written permission.

THIS SOFTWARE IS PROVIDED BY KTH AND ITS CONTRIBUTORS `ÀS

IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL KTH OR ITS CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,


LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,

OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY

WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE


(14) Alexey Zelkin

Copyright (c) 2000, 2001 Alexey Zelkin <[email protected]>


114 Appendix








THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS

`ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,

BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF


DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS

BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,








SUCH DAMAGE.

(15) Andrey A. Chernov

Copyright (C) 1997 by Andrey A. Chernov, Moscow, Russia.













THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF



Appendix

115





(16) FreeBSD

Copyright (c) 1997-2002 FreeBSD Project.






















SUCH DAMAGE.

(17) S. L. Moshier

Author: S. L. Moshier.

Copyright (c) 1984, 2000 S.L. Moshier

Permission to use, copy, modify, and distribute this software for any purpose

without fee is hereby granted, provided that this entire notice is included in all

copies of any software which is or includes a copy or modification of this software

and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS

OR IMPLIED WARRANTY. IN PARTICULAR, THE AUTHOR MAKES NO

REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE

MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY

PARTICULAR PURPOSE.

116 Appendix

(18) Citrus Project

Copyright (c) 1999 Citrus Project,






















SUCH DAMAGE.

(19) Todd C. Miller

Copyright (c) 1998 Todd C. Miller <[email protected]>









3. The name of the author may not be used to endorse or promote products


Appendix

117

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE

AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,









(20) DJ Delorie (i386)

Copyright (C) 1991 DJ Delorie


Redistribution and use in source and binary forms is permitted provided that the

above copyright notice and following paragraph are duplicated in all such forms.

This file is distributed WITHOUT ANY WARRANTY; without even the implied

warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR

PURPOSE.

(21) Free Software Foundation LGPL License (*-linux* targets only)

Copyright (C) 1990-1999, 2000, 2001 Free Software Foundation, Inc.

This file is part of the GNU C Library.

Contributed by Mark Kettenis <[email protected]>, 1997.

The GNU C Library is free software; you can redistribute it and/or modify it under

the terms of the GNU Lesser General Public License as published by the Free

Software Foundation; either version 2.1 of the License, or (at your option) any later

version.

The GNU C Library is distributed in the hope that it will be useful, but WITHOUT

ANY WARRANTY; without even the implied warranty of MERCHANTABILITY

or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General

Public License for more details.

You should have received a copy of the GNU Lesser General Public License along

with the GNU C Library; if not, write to the Free Software Foundation, Inc., 51

Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

(22) Xavier Leroy LGPL License (i[3456]86-*-linux* targets only)

Copyright (C) 1996 Xavier Leroy ([email protected])

118 Appendix

This program is free software; you can redistribute it and/or modify it under the

terms of the GNU Library General Public License as published by the Free Software

Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY

WARRANTY; without even the implied warranty of MERCHANTABILITY or

FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General

Public License for more details.

(23) Intel (i960)

Copyright (c) 1993 Intel Corporation

Intel hereby grants you permission to copy, modify, and distribute this software and

its documentation. Intel grants this permission provided that the above copyright

notice appears in all copies and that both the copyright notice and this permission

notice appear in supporting documentation. In addition, Intel grants this permission

provided that you prominently mark as "not part of the original" any modifications

made to this software or documentation, and that the name of Intel Corporation not

be used in advertising or publicity pertaining to distribution of the software or the

documentation without specific, written prior permission.

Intel Corporation provides this AS IS, WITHOUT ANY WARRANTY, EXPRESS

OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY

OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intel makes no guarantee or representations regarding the use of, or the results of

the use of, the software and documentation in terms of correctness, accuracy,

reliability, currentness, or otherwise; and you rely on the software, documentation

and results solely at your own risk.

IN NO EVENT SHALL INTEL BE LIABLE FOR ANY LOSS OF USE, LOSS OF

BUSINESS, LOSS OF PROFITS, INDIRECT, INCIDENTAL, SPECIAL OR

CONSEQUENTIAL DAMAGES OF ANY KIND. IN NO EVENT SHALL

INTEL'S TOTAL LIABILITY EXCEED THE SUM PAID TO INTEL FOR

THE PRODUCT LICENSED HEREUNDER.

(24) Hewlett-Packard (hppa targets only)

(c) Copyright 1986 HEWLETT-PACKARD COMPANY

To anyone who acknowledges that this file is provided "AS IS” without any express

or implied warranty:

permission to use, copy, modify, and distribute this file for any purpose is hereby

granted without fee, provided that the above copyright notice and this notice

appears in all copies, and that the name of Hewlett-Packard Company not be used in

advertising or publicity pertaining to distribution of the software without specific,

written prior permission. Hewlett-Packard Company makes no representations

about the suitability of this software for any purpose.

(25) Henry Spencer (only *-linux targets)

Appendix

119

Copyright 1992, 1993, 1994 Henry Spencer. All rights reserved.

This software is not subject to any license of the American Telephone and

Telegraph Company or of the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on any

computer system, and to alter it and redistribute it, subject to the following

restrictions:

1. The author is not responsible for the consequences of use of this software, no

matter how awful, even if they arise from flaws in it.

2. The origin of this software must not be misrepresented, either by explicit claim

or by omission. Since few users ever read sources, credits must appear in the

documentation.

3. Altered versions must be plainly marked as such, and must not be

misrepresented as being the original software. Since few users ever read

sources, credits must appear in the documentation.

4. This notice may not be removed or altered.

(26) Mike Barcroft

Copyright (c) 2001 Mike Barcroft <[email protected]>






















SUCH DAMAGE.

120 Appendix

(27) Konstantin Chuguev (--enable-newlib-iconv)

Copyright (c) 1999, 2000

Konstantin Chuguev. All rights reserved.





















SUCH DAMAGE.

iconv (Charset Conversion Library) v2.0

(28) Artem Bityuckiy (--enable-newlib-iconv)

Copyright (c) 2003, Artem B. Bityuckiy, SoftMine Corporation.

Rights transferred to Franklin Electronic Publishers.












Appendix

121










SUCH DAMAGE.

(29) IBM, Sony, Toshiba (only spu-* targets)

(C) Copyright 2001,2006, International Business Machines Corporation, Sony

Computer Entertainment, Incorporated, Toshiba Corporation,




Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list

of conditions and the following disclaimer in the documentation and/or other

materials provided with the distribution.

Neither the names of the copyright holders nor the names of their contributors may

be used to endorse or promote products derived from this software without specific

prior written permission.


CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF


DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,









(30) - Alex Tatmanjants (targets using libc/posix)

122 Appendix

Copyright (c) 1995 Alex Tatmanjants [email protected] at Electronni Visti IA,

Kiev, Ukraine.













THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,









(31) - M. Warner Losh (targets using libc/posix)

Copyright (c) 1998, M. Warner Losh <[email protected]>

















Appendix

123







SUCH DAMAGE.

(32) - Andrey A. Chernov (targets using libc/posix)

Copyright (C) 1996 by Andrey A. Chernov, Moscow, Russia.













THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,


DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF







(33) - Daniel Eischen (targets using libc/posix)

Copyright (c) 2001 Daniel Eischen <[email protected]>.






124 Appendix








DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS









SUCH DAMAGE.

(34) - Jon Beniston (only lm32-* targets)

Contributed by Jon Beniston <[email protected]>





















SUCH DAMAGE.

(35) - ARM Ltd (arm and thumb variant targets only)

Appendix

125

Copyright (c) 2009 ARM Ltd









3. The name of the company may not be used to endorse or promote products


THIS SOFTWARE IS PROVIDED BY ARM LTD `ÀS IS'' AND ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ARM

LTD BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,








SUCH DAMAGE.

(36) - Xilinx, Inc. (microblaze-* and powerpc-* targets)

Copyright (c) 2004, 2009 Xilinx, Inc. All rights reserved.



1. Redistributions source code must retain the above copyright notice, this list of

conditions and the following disclaimer.




Neither the name of Xilinx nor the names of its contributors may be used to endorse

or promote products derived from this software without specific prior written

permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND



126 Appendix


DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR










(37) Texas Instruments Incorporated (tic6x-* targets)

Copyright (c) 1996-2010 Texas Instruments Incorporated

http://www.ti.com/

Redistribution and use in source and binary forms, with or without modification,

are permitted provided that the following conditions are met:






Neither the name of Texas Instruments, Incorporated nor the names of its

contributors may be used to endorse or promote products derived from this

software without specific prior written permission.


CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE

COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,


DAMAGES (INCLUDING, BUT NO LIMITED TO, PROCUREMENT OF




OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF

THE POSSIBILITY OF SUCH DAMAGE.

(38) National Semiconductor (cr16-* and crx-* targets)

Copyright (c) 2004 National Semiconductor Corporation

Appendix

127

The authors hereby grant permission to use, copy, modify, distribute, and license

this software and its documentation for any purpose, provided that existing

copyright notices are retained in all copies and that this notice is included verbatim

in any distributions. No written agreement, license, or royalty fee is required for any

of the authorized uses. Modifications to this software may be copyrighted by their

authors and need not follow the licensing terms described here, provided that the

new terms are clearly indicated on the first page of each file where they apply.

NLog – Advanced .NET Logging 1.0

Copyright (c) 2004-2009, Jaroslaw Kowalski


Redistribution and use in source and binary forms, with or without modification,

are permitted provided that the following conditions are met:






Neither the name of Jaroslaw Kowalski nor the names of its contributors may

be used to endorse or promote products derived from this software without

specific prior written permission.





DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR










128 Appendix

QuickLZ 1. GRANT OF LICENSE

This commercial license lets you use QuickLZ version 1.0.0 to 1.9.9, both

inclusive, for development within the company for any amount of closed source

products and product titles with unlimited distribution/sales.

The license is persistent, non-exclusive and non-transferable. The license does

not cover derived or ported versions created by third parties under GPL. The

license does not need to be renewed if the amount of employees increases.

2. APPLICABLE LAW

This license shall be deemed to have been made in, and shall be construed

pursuant to, the laws of Denmark.

3. DISCLAIMER OF WARRANTIES AND LIMITATION ON LIABILITY

3.1. No warranties. To the maximum extent permitted by applicable law, the

software is provided “as is” without warranty, express or implied, of any kind or

nature, including, but not limited to, any warranties of performance or

merchantability or fitness for a particular purpose.

3.2. No Liability for Consequential Damages. To the maximum extent

permitted by applicable law, in no event shall licensor be liable for any special,

incidental, indirect or consequential damages whatsoever (including, without

limitation, damages for loss of business profits, business interruption, loss of

business information, or any pecuniary loss) arising out of the use or inability to

use the software, even if licensor has been advised of the possibility of such

damages.

4. LIMITED INTELLECTUAL PROPERTY INDEMNIFICATION

Licensor agrees that in the event of any actual or alleged infringement of any

patent, copyright, trade secret, trademark, or other proprietary right arising

out of licensee's use of the licensed software, licensor shall, at licensee's option

and at no charge to licensee, (a) obtain a license so licensee may continue use of

the software; (b) modify the software to avoid the infringement; (c) replace the

software with a compatible, functionally equivalent and non-infringing

product; or if these options are commercially unreasonable (d) refund to

licensee the amount paid for the software. The foregoing states the entire set of

obligations and remedies flowing between licensee and licensor arising from

any intellectual property claim by a third party.

Appendix

129

SharpZipLib 0.85.4 Copyright (C) 2002 Ben Lowery ([email protected])

This software is provided 'as-is', without any express or implied warranty. In no

event will the authors be held liable for any damages arising from the use of this

software.

Permission is granted to anyone to use this software for any purpose, including

commercial applications, and to alter it and redistribute it freely, subject to the

following restrictions:

1. The origin of this software must not be misrepresented; you must not claim

that you wrote the original software. If you use this software in a product, an

acknowledgment in the product documentation would be appreciated but is not

required.

2. Altered source versions must be plainly marked as such, and must not be

misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Silverlight.js 2.0 4. Microsoft Public License (Ms-PL)

This license governs use of the accompanying software. If you use the software,

you accept this license. If you do not accept the license, do not use the software.

1. Definitions

The terms "reproduce," "reproduction," "derivative works," and "distribution"

have the same meaning here as under U.S. copyright law.

A "contribution" is the original software, or any additions or changes to the

software.

A "contributor" is any person that distributes its contribution under this license.

"Licensed patents" are a contributor's patent claims that read directly on its

contribution.

2. Grant of Rights

(A) Copyright Grant- Subject to the terms of this license, including the license

conditions and limitations in section 3, each contributor grants you a

non-exclusive, worldwide, royalty-free copyright license to reproduce its

contribution, prepare derivative works of its contribution, and distribute its

contribution or any derivative works that you create.

(B) Patent Grant- Subject to the terms of this license, including the license

conditions and limitations in section 3, each contributor grants you a

non-exclusive, worldwide, royalty-free license under its licensed patents to

make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its

130 Appendix

contribution in the software or derivative works of the contribution in the

software.

3. Conditions and Limitations

(A) No Trademark License- This license does not grant you rights to use any

contributors' name, logo, or trademarks.

(B) If you bring a patent claim against any contributor over patents that you

claim are infringed by the software, your patent license from such contributor

to the software ends automatically.

(C) If you distribute any portion of the software, you must retain all copyright,

patent, trademark, and attribution notices that are present in the software.

(D) If you distribute any portion of the software in source code form, you may

do so only under this license by including a complete copy of this license with

your distribution. If you distribute any portion of the software in compiled or

object code form, you may only do so under a license that complies with this

license.

(E) The software is licensed "as-is." You bear the risk of using it. The

contributors give no express warranties, guarantees or conditions. You may

have additional consumer rights under your local laws which this license

cannot change. To the extent permitted under your local laws, the contributors

exclude the implied warranties of merchantability, fitness for a particular

purpose and non-infringement.

TBXML 1.4 Copyright 2012 71Squared. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this

software and associated documentation files (the "Software"), to deal in the Software

without restriction, including without limitation the rights to use, copy, modify,

merge, publish, distribute, sublicense, and/or sell copies of the Software, and to

permit persons to whom the Software is furnished to do so, subject to the following

conditions:

The above copyright notice and this permission notice shall be included in all copies

or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY

KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,

DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF

CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN

CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER

DEALINGS IN THE SOFTWARE.

Appendix

131

Windows CE C Library Extensions Copyright (c) 2006, Taxus SI Ltd., http://www.taxussi.com.pl













DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE

GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS






http://www.taxussi.com.pl/

132 Appendix

Zlib 1.2.2/1.2.3 Copyright (C) 1995-2012 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no

event will the authors be held liable for any damages arising from the use of this

software.

Permission is granted to anyone to use this software for any purpose, including

commercial applications, and to alter it and redistribute it freely, subject to the

following restrictions:

1. The origin of this software must not be misrepresented; you must not claim

that you wrote the original software. If you use this software in a product, an

acknowledgment in the product documentation would be appreciated but is not

required.

2. Altered source versions must be plainly marked as such, and must not be

misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Date post:	23-Apr-2018
Category:	Documents
Upload:	buidien
View:	215 times
Download:	1 times

Symantec Mobile Management for System Center...

Documents