And moving to the “wrapping up phase” of this installation we have just one final step to cover, which is getting a Gateway Server in place. There are two dependencies you need to get in place before you can start the install however.

The multi-instance feature requires the Gateway Server to have knowledge of the specific instance it belongs to. The Gateway Server is not a member of Active Directory, and thus cannot learn anything from the instance information there. You will need to supply this information in an xml-file, which you can either create yourself, or more preferably create on the Device Management Server and transfer to the GW Server.
—
Part 3 of 3

We’ll run quickly through the process of installing the server roles, as this has been covered previously and hasn’t changed all that much.

Remember to install the following components on your server before proceeding:
- WSUS 3.0 SP1
- PowerShell
- MBCA
- Report Viewer Redistributable

(…)

Part 2 of 3

System Center Mobile Device Manager 2008 (SCMDM 2008) has recently seen the release of Service Pack 1, so I felt it was time for another multi-post series on how to perform an installation of this little MDM product from Redmond.

(…)

One of the new features in System Center Mobile Device Manager 2008 Service Pack 1 is the ability to deploy multiple SCMDM instances in a single forest. Although my lab was working nicely with just one SCMDM deployment it was a feature I couldn’t resist testing, and documenting

Another new feature of SP1 is support for Windows Server 2008 Domain Functional Level, and Certificate Authority running on Windows Server 2008. I had to include this in my new lab as well.

So before installing SCMDM I have setup a new forest with a root domain, and two sub-domains. I installed this using three Virtual Machines all running Windows Server 2008 SP2 (Beta) Enterprise Edition.
—
Part 1 of 3