System Requirements for MDM Servers and Managed Devices

Configuring Infrastructure for MDM Deployment

You must set the forest in which you install MDM to Windows Server 2003 forest functional level. MDM does not support Windows 2000 mixed, Windows 2000 native, or Windows Server 2008 domain and forest functional levels.

Software Requirements for MDM Servers

Each server role in MDM has specific software prerequisites for the installation. Make sure that you update all Windows® Server® 2003 operating systems to include the most recent service packs, and that you configure the Windows-based operating system correctly before you start deployment.

Note:
To view administrator options to update Windows-based operating system servers to include the most recent updates, see the Microsoft Web page: http://go.microsoft.com/fwlink/?LinkId=106611. For more information about Microsoft security, see the Microsoft Security Web page: http://go.microsoft.com/fwlink/?LinkId=62649.

MDM infrastructure described in this section assumes that all servers are using a clean installation of the Windows-based operating systems, applications, and services listed. All software versions listed show the minimum version required.

Note:
MDM Best Practices Analyzer PreReq Tool helps you analyze a group of servers to determine if prerequisites for deploying MDM are met. The tool also lets you analyze servers post-deployment to verify port settings, etc. To download MDM Best Practices Analyzer PreReq Tool, see MDM Client Tools at this Microsoft Web page: http://go.microsoft.com/fwlink/?LinkID=108953.

MDM Core Components

Role	Operating system	Applications and services
SQL database server	Windows Server 2003 with SP2	Member of the Active Directory® domain Microsoft® SQL Server® 2005 Standard Edition SP2 or a later version Full product version of SQL Server must be installed; Express Edition is not supported Microsoft SQL Server 2008 is not supported Install the English or local language version of SQL Server For better performance in a production environment, do not install SQL Server on a server that is running MDM
MDM Device Management Server	Windows Server 2003 Standard x64 Edition with SP2	Member of the Active Directory domain Internet Information Services (IIS) 6.0 and World Wide Web Publishing Service .NET Framework 2.0 Windows Software Update Server (WSUS) 3.0 SP1 Microsoft Report Viewer Redistributable 2005 (optional)
MDM Enrollment Server	Windows Server 2003 Standard x64 Edition with SP2	Member of the Active Directory domain Internet Information Services (IIS) 6.0 and World Wide Web Publishing Service .NET Framework 2.0
MDM Gateway Server	Windows Server 2003 Standard x64 Edition with SP2	Stand-alone server Internet Information Services (IIS) 6.0 and World Wide Web Publishing Service .NET Framework 2.0

Review the following additional requirements before you install the MDM system:

MDM services might not start correctly if you do not install the .NET Framework language in the same language as MDM. You can download and install the .NET Framework Version 2.0 Language Pack from the Microsoft Download Center at this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=105268. Make sure that you select the correct language and then choose Update to refresh the page before you choose Download.
Report Viewer is not required for Windows Server Update Services (WSUS) software distribution. However, if you do not install Report Viewer, you cannot view result information about WSUS deployments.
If you install MDM Enrollment Server in a language that differs from that of the Microsoft SQL Server installation, and you connect to the server that is running SQL Server remotely, you must install MDM Enrollment Server at a command prompt. During the installation, you must specify the name of the Anonymous account on the server that is running SQL Server by using the ENWEB_SVC_ACC property. For more information, see "Required Language Version for SQL Server" in Install and Configure SQL Server for MDM.

Administration Components

Administrator Tools	Applications and Services
MDM Software Distribution Console	WSUS 3.0 SP1 Console .NET Framework 2.0 Windows PowerShell 1.0 MMC 3.0
Group Policy extensions	Group Policy Management Console Windows Server x32 editions or Windows Vista® x64 editions .NET Framework 2.0
MDM Console	MMC 3.0 Windows PowerShell 1.0 .NET Framework 2.0

MDM Administrator Tools provides management support over the MDM infrastructure together with the following three consoles:

MDM Console
MDM Software Distribution Console
Group Policy Management Console (GPMC) with MDM Group Policy extensions

Only 32-bit software platforms and 64-bit platforms running Windows Vista support GPMC. During MDM deployment, install the GPMC on a server or desktop that meets this requirement so that you can configure MDM Group Policy settings.

Infrastructure Components

Role	Operating System	Applications and Services
Domain controller	Windows Server 2003 Standard or Enterprise Edition with SP1	Active Directory Access to Domain Name System (DNS)
Microsoft Enterprise Certification Authority	Windows Server 2003 Enterprise Edition with SP2	Internet Information Services (IIS) 6.0 and World Wide Web Publishing Service Windows Server 2003 Standard Edition is not supported

Note:
If you install an MDM component on a domain controller, the domain controller operating system must be Windows Server 2003 Standard or Enterprise Edition with SP2.

If your environment does not use WINS, you can enable the Windows Mobile powered device to concatenate the Value you provide to the Shortname and send that host name to DNS. To enable this functionality, distribute a Group Policy setting to the device that contains the following registry key. Without this key, the device sends only the Shortname and assumes that DNS can resolve it.

The following table shows the properties of the registry key.

Location	New Key	Type	Value
HKLM\Comm\MSEC\IPSECVPNNIC1\Parms\TCPIP	Domain	String	Example: dns.corp.contoso.com

If your environment uses WINS, you should set the registry key above and meet the following additional requirements. You must have a WINS server in the perimeter network, or allow NetBIOS names to cross the firewall inbound. Additionally, set the following registry key for Name Resolution search order.

Location	New Key	Type	Value
HKLM\Comm\AFD	NameResolutionOrdering	Dword	4

Hardware Requirements for all MDM Servers

The following requirements apply to all MDM servers: MDM Enrollment Server, MDM Device Management Server, and MDM Gateway Server.

Hardware	Requirement
Processor	x64-bit architecture-based server with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T) AMD processor that supports the AMD64 platform Recommended: Dual processors at 2700 MHz or faster
Memory	4 GB of RAM. You may have to increase this amount for servers that are running SQL Server. Refer to SQL Server documentation for more information.
Disk Space	100 GB of free disk space for installation and data storage
Network	One network adapter for each server that is running SQL Server, MDM Enrollment Server, and MDM Device Management Server. Must be 100 Mb/s or faster Two network adapters for each MDM Gateway Server. Must be 100 Mb/s or faster.

Requirements for Managed Devices

Windows Mobile powered devices that you manage by using MDM must be running Windows Mobile 6.1. For more information about support for Windows Mobile powered devices in MDM, see this Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=107520.