[anyweb]

Please note that this guide is designed to get you up and running with SCCM in a LAB Environment as quickly as possible. This guide is provided as is, if you find any errors please report them in the forums.

In a production environment please consult Technet for best practise, see below links:

Configuration:

System Center Configuration Manager 2007

Best Practices:

Configuring Configuration Manager Sites for Best Performance
Checklist for Security Best Practices
Best Practices for Central and Primary Site Hardware and Software Configuration


This guide assumes you have installed SCCM 2007 SP1 and then configured it as outlined here in Part 1 you must then do the additional configuration outlined in Part 2, and you must have completed the final configuration tasks in Part 3. Lastly you must be able to deploy an application using SCCM 2007



Step 1.

Configure MDT

Note: MDT is optional, if you want to avail of it's many features then use it, otherwise skip to Step 2.


Download and then install Microsoft Deployment Toolkit (particularly if you want the MDT integration within Task Sequencer for Windows Server 2008), download details for MDT 2008 SP1 are here.


Note: If you plan on using MDT 2010 which supports Server 2008 R2 and Windows 7, then you should be aware that the PXE filter for Unknown support has been removed from that version and therefore you do not need to configure that anymore however having MDT 2010 installed is certaintly helpful as you'll find out sooner or later, so go ahead and install it.

Once MDT is installed, click on Start and expand the Microsoft Deployment toolkit menu in All Programs, you'll see some options including the one we want to use

Highlight Configure ConfigMgr integration, right click and choose Run As Administrator



select your SCCM server and SCCM site code and click finish to install the files and tools necessary for MDT integration within SCCM 2007, we'll look at where this can be used later in this guide.





Step 2.

Add the PXE Service Point (PSP) role to SCCM

Recommended Reading on Technet:
Planning for PXE Initiated Operating System Deployments



Start up SCCM ConfigMgr and expand Site Database/Site Management/Site Code/Site Settings/Site Systems and highlight your server

right click on it and choose New Roles



when the New Site Role Wizard appears, click next



highlight the PXE role and select it, click next



when you get a pxe service point confirmation click yes




on the PXE - General options page, remove the password requirement and set the PXE server response to 3 seconds (this value should be less than the value listed in your Windows Deployment Services PXE delay), you can verify the WDS pxe delay by right clicking the WDS server and choose properties/PXE response Settings. What we want to happen here is that SCCM answers the first PXE boot request(s) from a client and if they are not associated with a Task Sequence then let WDS take over with the PXE boot routine.

So here are two screenshots, the first is the PXE delay within the PXE role for SCCM



and below are the settings for PXE within WDS



Trouble Shooting Note:-

Installing the PXE Service point adds a service to the machine and a registry entry for WDS so WDS knows what to do with a boot request.

If you open regedit and browse to HKLM\System\CurrentControlSet\WDSServer\Providers\WDSPXE there is a "ProvidersOrder" key with some values in it. These values represent the boot order of WDS.

- SMS.PXE.Filter - The PXE filter script added by MDT.

- SMSPXE - Configuration manager PXE service point.

- BINLSVC - WDS and RIS legacy menus.

If you change the order of the ProvidersOrder key you should be able to switch between which device answers the PXE call first..

Now let's continue with configuring SCCM's PXE role,

accept the PXE-database settings and click next

Tip: set the PXE Certificate expiration date to 10 years from todays date, that way you'll not have to renew it for quite some time...



review the summary and click next and then click close to finish.



Now we should see the PXE service point role is added to ConfigMgr.



If you have any problems with getting WDS to start once the PSP role is installed then please take a look at this post

[anyweb]

Step 3.

Configure WDS PXE Filter


Note: If you plan on using MDT 2010 which supports Server 2008 R2 and Windows 7, then you should be aware that the PXE filter for Unknown support has been removed from that version and therefore you can skip this step, in addition if you are NOT going to use MDT integration then you can skip this step.

Next we click on Start and expand Microsoft Deployment Toolkit once more, this time select Configure WDS PXE filter , right click and choose Run As Administrator.



Note: The PXEFilter.vbs file should be edited to allow unknown computers to be registered into the SCCM database.







click on the Edit PXEFilter.vbs button and find the following six lines

sProviderServer = ""
sSiteCode = "CEN"
sNamespace = "root\sms\site_" & sSiteCode
sUsername = ""
sPassword = ""
sCollection = "CEN0000D"   ' This must be a collection ID, not a collection name

change them to match your setup (for example below)

sProviderServer = "WIN-AE2V1IRN067"
sSiteCode = "WIN"
sNamespace = "root\sms\site_" & sSiteCode
sUsername = "SMSadmin"
sPassword = "************"
sCollection = "SMS00001"   ' This must be a collection ID, not a collection name

the Collection ID can be found in Configuration Manager\computer management\collections in the right pane under collection ID for the selected collection, once done, save your file and click
.

The collection ID SMS00001 in the example above is the collection ID for All Systems. You will want to change that to the collection ID for your Deploy Vista collection. This means that the PXEFilter is being used for unknown computers to add them to the collection you specify.

[anyweb]

Step 4.

Create a New Collection

In SCCM ConfigMgr, highlight collections, right click and choose New Collection,



when the wizard appears, give the collection the name Build And Capture (Vista)



do not specify any memership rules and click Ok to the warning after you click next,





accept the defaults for Advertisements and Security settings





and click Close at the confirmation screen.

[anyweb]

Step 5.

Create a Package From Definition

In SCCM ConfigMgr, expand Computer Management and select the software distributions node, right click on packages and choose New Package from Definition.



when the Create package from Definition wizard appears, click next



Select the package called Configuration Manager Client Ugrade,



click next and choose the second option, Always obtain files from a source directory



and then select Network Path (UNC name) as the type and click on browse, browse to your sites SMS directory (SMS_xxx where xxx=the SMS site code)

eg: \\Win-ae2v1irn067\sms_win\Client



review the summary and click Finish.

Right-click on the new package you've just created and review it's properties, and while you are at it rename it from Upgrade to Installation

[anyweb]

Step 6.

Create and Update Distribution Points

Select the Package we have just created (Configuration Manager Client Installation) and expand it, Right-Click on Distribution Points and choose new distribution points



Select the standard distribution point only and click next



when it's done copying, click close



Now that you have created the distribution point, right click on Distribution points again, and choose Update Distribution points, answer Yes when prompted





Continue to Part 2 >>



digg it !