sp5 system requirements

7/21/2019 SP5 System Requirements

http://slidepdf.com/reader/full/sp5-system-requirements 1/34

CUSTOMER

SAP Afaria

Version: 7 SP05 - 2014-12-10

SAP Afaria System Requirements



Content

1 Afaria Access and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Installation Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Certificate Authority Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 SAP Afaria Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

6 SAP Afaria Administrator Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

7 Self-Service Portal Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

8 Package Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

9 Enrollment Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

10 Browser Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

11 Access Control Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

11.1 Access Control Remote Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

11.2 Access Control Filter Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

12 Network Access Control Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

13 Relay Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

14 Re verse Proxy Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

15 SMS Gateway Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

16 Connectivity Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

17 Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

17.1 SAP Afaria Server Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

17.2 SAP Afaria Client Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

18 Device Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

18.1 Android Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

18.2 iOS Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

18.3 Windows Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

18.4 Windows CE Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

18.5 Windows Mobile Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

18.6 Windows Phone Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2

C U S T O M E R© 2014 SAP SE or an SAP affiliate company. All rights reserved.


Content



18.7 Windows Devices with the MDM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


Content

C U S T O M E R© 2014 SAP SE or an SAP affiliate company. All rights reserved. 3



1 Afaria Access and Support

SAP provides industry-leading support and a variety of downloads to help you get the best out of your productsand solutions.

The sections below provide more information about getting access to Afaria, Afaria support, and Afaria

documentation.

Where to Get Afaria

In the SAP Support portal Software Downloads page (https://support.sap.com/software.html ), choose

Installations and Upgrades if you want to download a product that you currently do not have (but have a valid

contract for), or if you wish to download a new version of the product.

You will require the Download Software authorization, which you can request via your company's SAP System

Administrator.

Existing Sybase Customers

If you are an existing Sybase customer with an Afaria maintenance agreement, visit METS at http://

frontline.sybase.com/support .

Afaria Updates or Hotfixes

In the SAP Support portal Software Downloads page (https://support.sap.com/software.html ), choose

Support Packages and Patches if you want to download code-corrections or fixes for a specific version of a

product.

Afaria Support

Get access to Afaria Knowledge Base articles and report incidents using the SAP Support portal (https://

support.sap.com/kb-incidents.html ).

Registering for Notifications

Register for notifications and manage them at https://support.sap.com/kb-incidents/notifications.html . By

creating filters, you can manage the notifications for only the systems or products you are interested in.

4



Afaria Access and Support

http://help.sap.com/disclaimer?site=https://support.sap.com/kb-incidents.html


http://help.sap.com/disclaimer?site=https://support.sap.com/kb-incidents/notifications.html



http://help.sap.com/disclaimer?site=https://support.sap.com/software.html

http://help.sap.com/disclaimer?site=http://frontline.sybase.com/support

http://help.sap.com/disclaimer?site=http://frontline.sybase.com/support

http://help.sap.com/disclaimer?site=https://support.sap.com/software.html



Afaria Documentation

For module-wise documentation of Afaria, refer the SAP Mobile Secure section in the SAP Help portal (http://help.sap.com/mobile).

Contact Us

To know more about SAP Support portal, check the help topics at https://support.sap.com/support-programs-

services/about/help-index.html .

For any feedback or queries related to Afaria Technical Publications, contact us at [email protected].


Afaria Access and Support


http://help.sap.com/disclaimer?site=https://support.sap.com/support-programs-services/about/help-index.html

http://help.sap.com/disclaimer?site=https://support.sap.com/support-programs-services/about/help-index.html

http://help.sap.com/mobile

http://help.sap.com/mobile



2 Installation Image

The SAP Afaria product image includes several folders.

Folders marked by an asterisk (*) are reserved for setup program use. Do not access them directly.

Folder Contents Description

AdminUI* This folder contains installation files for the Afaria Administration

console.

AfariaServiceHost* This folder contains SAP Afaria API host service files.

Documents This folder contains some support documentation for SAP Afaria.

EUSSP* This folder contains installation files for the Self-Service Portal.

The Self-Service Portal allows users to enroll devices in SAP Afaria

management, view device information, and to remote lock or re

mote wipe devices.

iPhoneServer This folder contains installation files for the SAP Afaria Enrollment

Server.

ISAPI_x64* This folder contains installation files for the ISAPI filter that SAP

Afaria uses for access control filter.

NetworkAccessControlService* This folder contains installation files that SAP Afaria uses for net

work access control.

PackageServer* This folder contains installation files for the SAP Afaria Package

Server. The Package Server delivers enterprise application packages to devices.

Redistributables ● DotNet – contains a third-party file for installing Micro

soft .NET Framework Runtime on 32- and 64-bit environ

ments.

● VC_RunTime – Visual Studio 2012 runtime binaries for 32-bit

(x86) and 64-bit (x64).

● SQLAnywhereClient – contains the installer for the 64- and

32-bit client versions.

● Windows Installer – contains Microsoft's Windows Installer.

● XML – contains Microsoft XML Core Services (MSXML).

relay_server This folder contains installation files for the relay server. The relay

server is an optional component.

Server* This folder contains installation files for SAP Afaria Server.

Utility* This folder contains files for a utility program that checks for miss

ing prerequisites or network connectivity issues prior to installing

SAP Afaria components.

6



Installation Image



3 Database Requirements

The database stores procedures; configuration properties; device, group, and policy data; and all message andactivity logging.

Component Requirements

Database software ● SAP SQL Anywhere 12

● Microsoft SQL Server 2008 R2 Datacenter edition

● Microsoft SQL Server 2008 R2 Enterprise edition

● Microsoft SQL Server 2008 R2 Standard edition

● Microsoft SQL Server 2008 Enterprise edition

● Microsoft SQL Server 2008 Standard edition

Collation ● Case-insensitive collation

Time zone ● Configured for the same date, time, and time zone as the SAP

Afaria Server components it supports

Double byte environment ● UTF-8 character set for SAP SQL Anywhere 12


Database Requirements




4 Certificate Authority Requirements

The certificate authority issues certificates that SAP Afaria uses to help secure device communication andmanagement.

Component Supported Configurations

Certificate Authority ● SCEP:

○ Windows Server 2008 R2 Enterprise edition

○ IIS

○ Active Directory Certificate Services (ADCS) role

○ Network Device Enrollment Service (NDES) role

○ Windows Server 2008 Enterprise edition

○ IIS


○ Network Device Enrollment Service (NDES) role

● Native Certificate APIs:

○ Windows Server 2008 R2 Enterprise edition

○ IIS


Additional Requirements ● iOS devices require verification of the complete chain of trust

● The identity credentials used for the certificate authority IIS

SCEP application pool must match the credentials for the SAP

Afaria Enrollment Server

8



Certificate Authority Requirements



5 SAP Afaria Server Requirements

The SAP Afaria Server is central to Afaria operations. The server communicates with the Afaria database andadditional components or devices as necessary.

This recommended setup is for 50-300 concurrent device sessions.


Operating system ● Windows Server 2008 R2 Datacenter edition (64-bit)

● Windows Server 2008 R2 Enterprise edition (64-bit)

● Windows Server 2008 R2 Standard edition (64-bit)

Processor ● Minimum: 1.4 GHz (x64 processor)

● Recommended: 2 GHz or faster

Memory ● Minimum: 1.5 GB

● Recommended: 2.0 GB

Storage ● 20 GB

● Additional storage is required for user data

Database ● Configured for the same date, time, and time zone as the data

base server

Relay server ● Connections from devices

● Connections from Afaria Access Control for Email Compo

nents

Directory and authentication ● Microsoft Active Directory

● Windows NTLM

● Novell eDirectory via LDAP v3

● Netscape Directory Server via LDAP v3

Client communication ● SSL protocol v3 using x.509 certificate signed by a trusted or

custom signed certificate authority

● HTTP with T-Mobile

Windows account ● Log on as service

● Interactive logon


SAP Afaria Server Requirements





Additional requirements ● Installation path and virtual directory must contain ASCII char

acters only● Microsoft Visual C++ Runtime

○ 2012 x64

○ 2012 x86

● Internet Information Services (IIS) for Windows Server 7.5

● Windows Installer 3.1

● Microsoft .NET Framework Runtime 4.5

● Microsoft XML Core Services 6.0

10



SAP Afaria Server Requirements



6 SAP Afaria Administrator Requirements

The Afaria Administration console is the interface for administering the SAP Afaria server and components.


Operating system ● Windows Server 2008 R2 Datacenter edition

● Windows Server 2008 R2 Enterprise edition

● Windows Server 2008 R2 Standard edition

● Windows Web Server 2008 R2

Processor ● Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor)


Memory ● Minimum: 512 MB

● Recommended: 2 GB or greater

Storage ● Minimum: 10 GB



base server


acters only

● Microsoft Visual C++ Runtime

○ 2012 x64

○ 2012 x86





SAP Afaria Administrator Requirements




7 Self-Service Portal Requirements

The Self-Service Portal lets users enroll devices in Afaria management, view device information, and issuecommands, such as to remote lock or remote wipe a device.


Operating systems ● Windows Server 2008 R2 Datacenter edition



● Windows Web Server 2008 R2







Database ● Configured for the same time zone as the database server

Additional requirements ● Installation path and virtual directory must contain only ASCII

characters

● Microsoft Internet Information Server (IIS) 7.5


● Microsoft .NET Framework Runtime 4

12



Self-Service Portal Requirements



8 Package Server Requirements

The Package Server sends Afaria application packages to devices for application policies and serves certificatesand device provisioning data to third-party applications for onboarding.












base server

Additional requirements ● Installation path and virtual directory must contain only ASCII

characters

● Microsoft Internet Information Server (IIS) 7.5● Microsoft Windows Installer 3.1



○ 2012 x64

○ 2012 x86


Package Server Requirements




9 Enrollment Server Requirements

The enrollment server supports device enrollment for Android, iOS, Windows Phone, Windows DM (Windows 8.1),and Windows Mobile devices, and also delivers payloads for iOS devices.

Demand for Afaria resources can vary greatly by installation and are highly dependent on several factors. Afaria

enrollment server resource recommendations are based on concurrent device sessions and session duration. The

following factors can affect session duration:

● Device response time

● Number of device enrollment requests

● Number of iOS configuration policies

● Number of settings within iOS configuration policies

● Connection speed

● IIS server request processing capacity











Database ● Configured for the same time zone as the database server


acters only


○ 2012 x64

○ 2012 x86




● Must be able to retrieve valid CRL and Delta CRL files

14



Enrollment Server Requirements



10 Browser Requirements

The following table describes the browser requirements for using the Afaria Administration console and the Self-Service Portal.

Component Requirement

Browser ● Afaria Administration console

○ Google Chrome 35.0

○ Internet Explorer 9, 10, and 11

○ Mozilla Firefox 30.0

○ Safari 5.15 - Mac or iPad

● Self-Service Portal

○ Google Chrome 35.0

○ Internet Explorer 8, 9, 10, and 11

○ Mozilla Firefox 30.0

○ Safari 5.15 - iOS devices

Additional requirements ● On the domain controller in an Active Directory environment,

make sure that the Log On To list is either unrestricted or in

cludes the SAP Afaria Administrator server and the computers

that access the Afaria Administration console

● Enhanced security configuration setting in Internet Explorer 9

is not supported

● Compatibility view in Internet Explorer is not supported

● Due to session state sharing restrictions between tabs, sup

port is limited to using a single tab


Browser Requirements




11 Access Control Requirements

11.1 Access Control Remote Requirements

Access control remote uses PowerShell commands that are native to the Exchange environment. The Exchange

environment may be local or hosted.

Component Description

Local email server ● Microsoft Exchange Server 2013

● Microsoft Exchange Server 2010

Hosted email server ● Microsoft Office 365

PowerShell Host Server ● Microsoft PowerShell Version 2.0

● Enable the PowerShell remote command capability by ena

bling Basic or Kerberos authentication on the virtual directory

in IIS

11.2 Access Control Filter Requirements

The access control filter installs a filter into the email environment through which ActiveSync requests are routed.


Local Email Server ● Microsoft Exchange Server 2010

● Microsoft Exchange Server 2007

Microsoft Proxy Server ● Microsoft Forefront Threat Management Gateway 2010

Internet Information Services (IIS) for Mi

crosoft Exchange Server

● Server with a 64-bit operating system

● IIS on a server separate from the server that hosts the SAP

Afaria Administrator

● Administrator account for running the Afaria filter as a service

must be a member of the Exchange Organization Administra

tors group (2007, 2010).

● Administrator account for running the Afaria filter as a service

must be a member of the Administrator groups on both IIS

and Microsoft Exchange Server

16



Access Control Requirements




Datahandler Host Server (component of the

access control filter)

● Server with a 64-bit operating system

● Microsoft PowerShell 2.0● User account for running the filter's PowerShell component

must be in the same domain as the email server

● Microsoft Data Access Components (MDAC) 2.8


Access Control Requirements




12 Network Access Control Requirements

The Network Access Control Server manages the access of Android and iOS devices to corporate Wi-Fi networksby ensuring the devices are under SAP Afaria control before Wi-Fi access is granted. This ensures that devices are

kept in compliance with SAP Afaria MDM control, enforcing inventory collection and security policies on the

device before permitting access to enterprise networks.












base server

Additional requirements ● Installation path and virtual directory must contain ASCII characters only

● Microsoft Internet Information Services (IIS) 7.5




○ 2012 x64

○ 2012 x86

18



Network Access Control Requirements



13 Relay Server Requirements

The relay server is a secure, load-balanced proxy server that relays communication between mobile devices andservers.

The relay server is an optional component that is included with the SAP Afaria product on the product installation

image.


Relay server ● SAP Sybase SQL Anywhere 16 Relay Server component

● SAP Sybase SQL Anywhere 12.0.1 Relay Server component

Web server ● IIS 7.5 (Windows)

● IIS 6.0 (Windows)

● Apache (Linux)

Supported server components ● SAP Afaria Server

● SAP Afaria Enrollment Server

● SAP Afaria Package Server

● Certificate Authority

Additional requirements ● All Relay Server Outbound Enabler (rsoe.exe) instances must

be the same version. Afaria uses rsoe.exe in these locations:

○ SAP Afaria Server: <ServerInstallDirectory>\bin\RSOut

boundEnabler\○ SAP Afaria Enrollment Server: user-defined

○ SAP Afaria Package Server: user-defined

○ Certificate Authority: user-defined

● Relay Server on IIS may coexist with other IIS applications

● Relay Server may coexist with other virtual Web server under

the same IIS install

● Relay Server may coexist with other Web site (or directory)

under the same logical Web server

● Relay Server Web server extensions may coexist with other

Web server extensions sharing the same application pool

○ Application pool properties are limited to being Relay

Server compatible (in general, all worker recycling options

need to be turned off)


Relay Server Requirements




14 Reverse Proxy Requirements

SAP Afaria supports sessions (HTTP or HTTPS) through a reverse proxy server.


Apache HTTP Server ● 2.2.7 - 2.2.11

● 2.2.6 (patch 19954)

● 2.1

● 2.0.54

Internet Security and Acceleration (ISA)

Server

● 2006

● 2004

20



Reverse Proxy Requirements



15 SMS Gateway Requirements

SAP Afaria uses the SMS Gateway to deliver outbound notifications, remote wipe commands, and any othercommunication that is addressed for SMS routing to supported devices.


Third-party components ● Cygwin UNIX-emulating environment (manual installation)

Other requirements ● Short Message Peer-to-Peer (SMPP) 3.4 protocol support

● SMS gateway configuration settings must contain only ASCII

characters


SMS Gateway Requirements




16 Connectivity Requirements

Component Ports

SAP Afaria Server ● Port 80 inbound: HTTP without a relay server

● Port 80 outbound: HTTP with a relay server

● Port 135 inbound: DCOM communications with SAP Afaria

components. The DCOM port range is configurable. These

ports are reserved for, and managed by, DCOM services.

● Port 443 inbound: HTTPS without a Relay Server

● Port 443 outbound: HTTPS with a Relay Server

● Port 443 outbound: Google Cloud Messaging (https://

android.apis.google.com/gcm/send)

● Port 443 outbound: HTTPS with messaging servers for Access

Control Remote

● Port 2195 outbound: Apple Push Notification Service server

(gateway.push.apple.com)

● Port 2196 outbound: Apple Push Notification Service feedback

server (feedback.push.apple.com)

● Port 5223 outbound: Apple Push Notification Service server

(gateway.push.apple.com) for devices using Wi-Fi

● Port 8085 inbound: Requests from SAP Afaria components for

notifications to devices

● Port 8086 inbound: Requests from SAP Afaria components

for notifications to devices

● Port 8087 inbound: Requests from SAP Afaria components for


● Port 8089 inbound: Internal communication

● Outbound connectivity to the Afaria database. The port is con

figurable for each supported database type.

22



Connectivity Requirements



Component Ports

Package Server ● Port 80 inbound: HTTP communication with devices (without

a relay server)● Port 80 outbound: HTTP communication with a SAP Afaria Re

lay Server

● Port 135 outbound: DCOM communication with the SAP Afaria

Server. The DCOM port range is configurable. These ports are

reserved for, and managed by, DCOM services.

● Port 443 inbound: HTTPS communication with devices (with

out a relay server)

● Port 443 outbound: HTTPS communication with a Relay

Server

● Port 8085 outbound: Requests to the SAP Afaria Server for

notifications to devices● Port 8086 outbound: Requests to the SAP Afaria Server for




● Port 8080 – reserved for internal communication.

● Outbound connectivity to the Afaria database. The port is con

figurable for each supported database type.

Enrollment Server ● Port 80 inbound: HTTP communication with devices (without

a Relay Server)

● Port 80 outbound: HTTP communication with a relay server

● Port 135 outbound: DCOM communication with the SAP Afaria




out a relay server)


Server

● Port 7007: Reserved for internal communication












Component Ports

SAP Afaria Administrator and API ● Port 80 inbound: HTTP communication

● Port 80 outbound: HTTP communication● Port 135 outbound: DCOM communication with the SAP Afaria



● Port 443 inbound: HTTPS communication

● Port 443 outbound: HTTPS communication

● Port 7980/7982 inbound

Self-Service Portal ● Port 80/443 inbound to IIS server, where the self-service por

tal website is installed

● Port 7980/7982 outbound: Communication with Afaria API

Certificate Authority ● Port 80 inbound: HTTP communication with devices (without

a Relay Server)

● Port 80 outbound: HTTP communication with a Relay Server


out a Relay Server)


Server

Access Control Filter ● The server hosting the Datahandler component requires out

bound connectivity to the Afaria server or its optional relay

server proxy.● Outbound port 3012 - when the Afaria filter's components are

installed on separate servers, the Datahandler component

host requires outbound connectivity to the filter component

host.

Network Access Control ● Port 443 inbound

● Port 7980/7982 outbound: Communication with Afaria API

Directory ● Port 389/636: LDAP/LDAPS

● Port 3268/3269: Global Catalog/Global Catalog over SSL

24






17 Supported Languages

17.1 SAP Afaria Server Supported Languages

The SAP Afaria server supports the following languages.

Language Operating System Afaria Administration

console

Self Service Portal

Chinese (Simplified) ● ●

Chinese (Traditional) ● ●

English ● ● ●

French ● ●

French (Canadian) ●

German ● ●

Italian ●

Japanese ●

Korean ● ●

Portuguese (Brazilian) ●

Romanian ●

Russian ●

Spanish ●

Spanish (Colombian) ●

Thai ●

Turkish ●


Supported Languages




17.2 SAP Afaria Client Supported Languages

The SAP Afaria client supports the following languages.

Language Android iOS Windows Mobile Windows Phone

Chinese (Simplified) ● ● ● ●

Chinese (Traditional) ● ● ● ●

English ● ● ● ●

French ● ● ● ●

French (Canadian) ● ● ●

German ● ● ● ●

Italian ● ● ● ●

Japanese ● ● ● ●

Korean ● ● ● ●

Portuguese ● ● ●

Portuguese (Brazilian)

●

Romanian ● ● ●

Russian ● ● ●

Spanish ● ● ● ●

Spanish (American) ●

Spanish (Colom

bian)

● ●

Spanish (Mexican) ●

Thai ● ● ● ●

Turkish ● ● ●

26



Supported Languages



18 Device Requirements

The operating requirements for the different device types are summarized.

The device types supported by SAP Afaria in the 7.0 SP05 release are:

● Android devices

● iOS devices

● Windows devices

● Windows CE devices

● Windows Mobile devices

● Windows Phone devices

● Windows devices with the MDM client (Windows DM)

Note

BlackBerry devices are not supported in Afaria 7.0 SP05 release.

18.1 Android Devices

SAP Afaria supports Android devices that meet the following requirements.


Operating system ● Android 5.0

● Android 4.4

● Android 4.3.x

● Android 4.2.x

● Android 4.1.x

● Android 4.0.x

● Android 3.x

● Android 2.3.x


Device Requirements





Advanced Enterprise Security (AES) ● Samsung

○ Enterprise mobile device management (Android 2.3.3 and

later)

○ Some MDM features are dependent on the "MDM ver

sion", which is viewable through inventory, and may not

function without updating the OS version to a level that

supports the specific MDM functionality. Samsung cur

rently supports the following MDM versions:

○ 1.0

○ 2.0

○ 2.1

○ 2.2

○ 3.0

○ 4.0

○ 4.0.1

NitroDesk TouchDown features ● Configuration Manager and Inventory Manager licensing

● Android NitroDesk TouchDown client 6.4 or later

Samsung KNOX 1.2

Note

Afaria supports KNOX 1.2 functionality on Samsung deviceswith KNOX 2.0.

18.2 iOS Devices

SAP Afaria supports iOS devices that meet the following requirements.


Operating system ● iOS 8.1, 8.1.1, and 8.1.2

● iOS 8 and 8.0.2

● iOS 7.1, 7.1.1, and 7.1.2

● iOS 7.0

● iOS 6.1, 6.1.1 (iPhone 4S devices), and 6.1.3

● iOS 6.0.1 and 6.0.2

● iOS 5 and 5.1

NitroDesk TouchDown ● iOS 6.1 and later

● NitroDesk TouchDown application (March 2013 or later)

28



Device Requirements




Certificates ● Apple Inc. Root Certificate

● Application Integration Intermediate Certificate● Apple Push Notification Service Certificate

Supervised Mode ● iOS 8.1 and 8.1.1

● iOS 8 and 8.0.2

● iOS 7.0, 7.1, 7.1.1, and 7.1.2

● Apple Configurator 1.4.2

Apple Device Enrollment Program ● iOS 8.1 and 8.1.1

● iOS 8 and 8.0.2

● iOS 7.1, 7.1.1, and 7.1.2

18.3 Windows Devices

SAP Afaria supports Window devices that meet the following requirements.


Operating system ● 64-bit

○ Windows 8 and 8.1

○ Windows 7

○ Windows Server 2008 R2

● 32-bit

○ Windows 8 and 8.1

○ Windows 7

○ Windows Server 2008

○ Windows Vista

○ Windows XP

○ Windows Server 2003

Storage ● 12 MB (Installation)

● Additional space for channel data

Protocol support ● XNET

● XNETS

● HTTP

● HTTPS

Additional requirements ● Microsoft Windows Installer 3.1


Device Requirements




18.4 Windows CE Devices

SAP Afaria supports Windows CE devices that meet the following requirements.

Windows CE devices do not support NT LAN Manager (NTLM). The devices support LDAP authentication with a

companion computer to deploy.


Operating system ● Windows CE 5.0

● Windows CE 4.2

● Windows CE 4.1

Additional requirements ● TCP/IPV4 protocol support

● ActiveSync support

● Microsoft Windows Shell

18.5 Windows Mobile Devices

SAP Afaria supports Windows Mobile devices that meet the following requirements.

Windows Mobile devices do not support NT LAN Manager (NTLM). The devices support LDAP authentication witha companion computer to deploy.


Operating system ● Windows Mobile 6.5 (Professional, Classic, and Standard)

● Windows Mobile 6.1 (Professional, Classic, and Standard)



Client notification to connect ● Short Message Service (SMS)

● Data service

Remote wipe and device lock ● Short Message Service (SMS)

● Data service

18.6 Windows Phone Devices

SAP Afaria supports Windows Phone devices that meet the following requirements.

Windows Phone devices do not support LDAP authentication.

30



Device Requirements




Operating system ● Windows Phone 8 and 8.1

18.7 Windows Devices with the MDM Client

SAP Afaria supports Windows devices with the MDM client (Windows DM) that meet the following requirements.


Operating System ● Windows 8.1


Device Requirements




Important Disclaimers and Legal Information

Coding Samples

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system

environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of c ertain coding. SAP does not warrant the correctness and

completeness of the Code given herein, and SAP shall not be liable fo r errors or damages caused by the usage of the Code, unless damages were caused by SAP

intentionally or by SAP's gross negligence.

Accessibility

The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a

binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does

not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales

person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not

exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not

warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages

caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency

(see: http://help.sap.com/disclaimer).

32




http://help.sap.com/disclaimer/



www.sap.com/contactsap

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP SE

or an SAP affiliate company. The information contained herein may

be changed without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software

vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company

for informational purposes only, without representation or warranty

of any kind, and SAP or its affiliated companies shall not be liable for

errors or omissions with respect to the materials. The only

warranties for SAP or SAP affiliate company products and services

are those that are set forth in the express warranty statements

accompanying such products and services, if any. Nothing herein

should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks

http://www.sap.com/contactsap