Open Active Directory Users and Computers and create two new Domain Users

SMSadmin and SMSread.

Attached Image: monthly_08_2008/post-1-1219746034.jpg

The SMSAdmin account should have Full Administrative priveledges on the SCCM server. To do this you can add the SMSadmin account to the Local Administrators Group on the SCCM Server.

Go back to SCCM ConfigMgr, expand Site Settings and Site Systems, and click on your Server name. You should see that several Roles are already installed (Component Server, distribution point, management point, site server, site system, site database server).

Attached Image: monthly_08_2008/post-1-1219745485.jpg

Right click your server name and choose New Roles. This will bring up the New Site Role Wizard.

Attached Image: monthly_08_2008/post-1-1219746118.jpg

Accept the defaults and click next.

Select Server Locator point, State Migration point, Reporting point and Software update point from the list.

Attached Image: monthly_08_2008/post-1-1219746557.jpg

Note: If you are not using the Configuration Manager AD schema *ie, if you have not extended the AD schema for SCCM as outlined here* , then you do need an SLP.For Server Locator point, however, if you plan on doing Build and Capture, then read below.

Select the Server Locator Point even though the AD schema has been extended for SCCM. This is because when doing Build and Capture of an Operating System, best practise means the computer is not domain joined, therefore it cannot get the information it needs (to install windows updates) from AD, it therfore retrieves the information from the SLP. Read this post for more info.

Attached Image: monthly_08_2008/post-1-1219746743.jpg

For State Migration point, click on the red exclamation mark to input a path to store the SMP data for example d:\smp this is where data will be stored during the OSD process if it has to be stored on the network.

Attached Image: monthly_08_2008/post-1-1219747017.jpg

Next up is the reporting point, leave it as it is

Attached Image: monthly_08_2008/post-1-1219747210.jpg

Then we will have the Software Update point, WSUS 3.0 sp1 or later must be installed to use this feature, but if you’ve followed my guide from start to finish you’ll already have it (WSUS 3.1) installed.

Attached Image: monthly_08_2008/post-1-1219747430.jpg

Put a checkmark in Use this server as the active software update point, and click next, then leave the Sync source settings as they are.

Attached Image: monthly_08_2008/post-1-1219747878.jpg

Accept the Sync Schedule defaults

Attached Image: monthly_08_2008/post-1-1219748218.jpg

click next to see the classifications, choose the following Critical Updates, Definition Updates, Security Updates, Service Packs, Update Rollups, and Updates, then click the next button.

Attached Image: monthly_08_2008/post-1-1219748244.jpg

For Products to update, choose Office, SQL and Windows (Windows and Office will already be selected)

Attached Image: monthly_08_2008/post-1-1219748336.jpg

Set your language preferences, mine had Chinese, Korean, French and German pre-selected (odd…) I changed it to only English

Attached Image: monthly_08_2008/post-1-1219748463.jpg

finally you can review the summary…. click Finish

Attached Image: monthly_08_2008/post-1-1219748531.jpg

once done click close.

Attached Image: monthly_08_2008/post-1-1219748644.jpg

We can now see our roles in ConfigMgr.

Attached Image: monthly_08_2008/post-1-1219748898.jpg

Next step > SCCM 2007 SP1 configuration guide – Part 2

The guide covers:-

Configuring the Distribution Point (DP) and the Management Point (MP), adding Authoring rules in WebDav and changing WebDav settings, making sure the System Management container in Active Directory has the correct permissions for SCCM, checking and fixing errors in SCCM System Status.

Advertisements