Video Screencast Help

Mobile Management for Configuration Manager POC

Created: 11 Dec 2012 • Updated: 11 Dec 2012 | 1 comment

Hi all,

I'm completly new to this product and MDM sw at all. I have to setup POC of SMM for CM in environment with one primary and 3 secondary SCCM sites. All SCCM servers are part of one domain. I installed one non domain server and put it in DMZ. My idea is to install Push component of SMM on DMZ server, and Console and Services components on Primary SCCM server. I have created all required certificates. Now, my problem is...

Now, web application that is used for enrollment (https://..../athena/enrollment/athenaiosenroll.aspx) is installed as part of instalation of Services component. Should I publish this application which is in interrnal network, or shuld I install Services component on server in DMZ too and publish that web app?

Another question, how user authentication works on this system.. What I meen.. Why SMM agent asks me for user name and password and what SMM do with this credentials?

PS. My current topology is provided as attachment.

Comments 1 CommentJump to latest comment

rscovel's picture


At this time SMM for SCCM is supported on SCCM 2007 only. An upcoming release will add support for SCCM 2012.

You can find the correct installation order in the Installation guide located here:

The following is the proper order of installation in a Configuration Manager environment.

1. Internet-Facing Server

a. Push Services

2. Central Server

a. Console

b. ISV Proxy (first time only)

c. Services

d. Reporting Services

e. Feature Packs (optional)

f. Replication Services

3. Primary Server

a. Console

b. Services

c. Feature Packs (optional)

4. Secondary Server

a. Console (optional)

b. Services

Don't install anything on any servers other than what is specified in the instructions.

I am attaching a LAB Guide as a reference. The guide will have information about setting up a test environment and can be used as a reference but should be adapted for your environment.

Authentication is used to enroll the devices into the system. When AD is used the credentials are pushed to the devices when configuring the email setup and potentially for any other configurations that require authentication.

The Authentication also associates the devices to those users. If a user has multiple devices you will then be able to see all of the associated devices for that person.

SMM-SCCM72_Installation_and_Configuration_Lab.pdf 1.06 MB

Russ Scovel
Inside Systems Engineer

Altiris SOS – Endpoint Management and Mobility
Symantec Corporation