anyweb

Before starting this part, you should have completed all the steps in Part 1. Add 32 bit and 64 bit boot.wim files Note: In your installation of SCCM 2007 SP1 you may already have a x86 and x64 bit boot.wim images, however we want to create our own and then distribute them to both the standard share and the PXE share. In SCCM 2007 configMgr, select Operating System Deployment under Computer Management, expand the boot images node and right click, choose Add Boot Image. browse to the network share where SCCM stores it's boot.wim files, this time for the 32 bit one eg: \\servername\SMS_WIN\OSD\boot\i386\boot.wim fill in details for the boot.wim and call it x86 Windows PE boot environment for SCCM review the summary click next to apply the changes Now that you have done the 32 bit boot.wim repeat the above actions for the 64 bit (X64) boot.wim file by using the 64 bit path (\\servername\SMS_WIN\OSD\boot\x64\boot.wim). You should now have two new boot.wim files listed in your ConfigMgr. Customise the background Logo In explorer, browse to \\servername\sms_win\OSD\bin\i386 and locate a file called WINPE.BMP, open it in Microsoft Paint and paste in your own company Logo, save the file (after backing up the original) and repeat this action for the WINPE.BMP file stored in \\servername\sms_win\OSD\bin\x64, this background will appear during the Deployment of Windows Vista (or Windows Server 2008). Once done, right click your chosen Boot.wim file in SCCM ConfigMgr and choose properties and then the Windows PE tab, select the Specify the customer background bitmap (UNC Path) and browse to your newly created WINPE.BMP file, apply the changes and answer NO to the Distribution points update reminder as we'll be doing that shortly. here is a sample I made up in less than a minute, hence the quality ;-) Create new Distribution Points and Update them In SCCM ConfigMgr, select the x86 Windows PE boot environment for SCCM boot image and expand that node, right click on distribution points and select New Distribution Points when the New Distribution Points wizard appears click next, now when the Copy Package screen comes up, make sure to select BOTH of the distribution points listed, one being the normal one and the other is the PXE distribution point, both are required for this to work properly. select next to continue and close when done. Now you need to Update the distribution point, so right click on Distribution Points and choose Update.... click next and next again... and click close when done Don't forget to repeat the above actions (create new and then update distribution points) for the X64 bit version also (x64 Windows PE boot environment for SCCM ) Continue to the next part >

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.

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.

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: Planning: Planning for PXE Initiated Operating System Deployments Planning for Operating System Deployment Configuration: System Center Configuration Manager 2007 How to Configure the PXE Service Point How to Configure Windows Server 2008 for Site Systems A step by step for using OSD through 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 Troubleshooting Troubleshooting the PXE Service Point and WDS in Configuration Manager 2007 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

Step 4. Installing SCCM 2007 SP2 After completing the above steps insert the SCCM 2007 DVD again and choose 'Configuration Manager 2007\ under the Install heading. when the welcome wizard appears, click next As we are upgrading SMS 2003 to SCCM 2007 we are offered the Upgrade option click next to continue and agree to the license terms.... Tell Microsoft if you want to help or not in the customer experience program reivew/input your key the next option allows setup to check for newer options, so I stayed with the default setting you have the option to input a path to store or access updates, so enter it there setup then went and downloaded 88 files.... and once done it told me finally you are shown a summary at this point setup will re run the prerequiste checker and present you with the option to begin install once done now is a good time to take a coffee break... after a long time you can click on next to continue... and place a checkmark in the Launch the configuration manager console after closing option if all went ok you'll now see SCCM 2007 running happily !

Step 3. fix the prerequisite warnings/errors. As per the prerequisite check recommendation, I then upgraded my installation of SQL 2000 to SQL 2005 Sp2. Once done I ran the prerequisite check again, and this time it listed 4 warnings One of those warnings was to install the following hotfix. I downloaded and extracted the hotfix, then installed it. Once installed I ran my SCCM 2007 prerequiste checker again. Great, only 3 warnings left now. Taking them one at a time I was informed that I had to install a WSUS update so I downloaded WSUS 3.0 SP1 and proceeded to install it 80mb application and I went with all the default settings in the wizard). WSUS took quiet a while to install but finally it was done once done I ran my check again. Now only two warnings left the first is for Schema Extensions and after a bit of googling it seems I can install them before or after running SCCM 2007 setup. Looking at how to extend the schema is complex. Updating the schema requires you to be in the Schema admin security group, even an Enterprise Administrator is not a Schema admin. As Microsoft say I decided to use the extADSch.exe method and located it on the SCCM 2007 DVD (F:\SMSSETUP\BIN\I386), but before doing so I wanted to add my Domain Administrator (Enterprise Administrator) to the Schema Admins group. Adding the Domain administrator account to the Schema Admins group to do this, start up Active Directory Users and Computers and select the Enterprise Admins group double click the group and select the Security Tab, click on Add When the Select Users, Computers or Groups window appears, click on Advanced click on the Find now button and when the results appear scroll down until you see the Schema Admins group, select it. click on ok and notice that it (schema admins group) is now listed in the Select Users, Computers or Groups window. click on ok and leave the permissions as they are listed click ok when done and now we can try running the extadsch.exe tool, we will run it from a command prompt and redirect any output to a file to see if there were any problems during the process. extadsch.exe > c:\output.txt if everything went ok the log file will be pretty emtpy (see mine) otherwise it may contain errors. Once done, you can run the SCCM 2007 prerequisite checker again, and this time the 'extend active directory schema' is no longer listed ! success. the last warning in my prereequisite check is for Secure Key Exchange To set this up I started up my SMS 2003 mmc and expanded Site Database/Site Hierarchy and then right clicked on my site and chose Properties and then Advanced. In the advanced section I could see an option called Require Secure Key exchange between sites I then selected it and clicked on apply then ok. After that I then ran the SCCM 2007 prerequisite checker again and this time it told me that all required prerequisite tests have completed successfully, success !

as you may or may not know, Windows 2008 Server doesn't support Windows Live Messenger, in fact, when you try to install it you'll get the following error why ? I don't know, however after some searching I found the following download (MSI package) which DOES work in Windows 2008 Server. so here you go, download the MSI file of Windows Live Messenger v8.5.1302.1018 here, it's a silent install so once you run it, it will install Messenger Live silently (no questions asked during the install process). Please Digg this so others will know the fix cheers anyweb

This guide assumes that you have first configured and installed WDS in Windows Server 2008 as outlined here. you'll also need a copy of the Windows Vista SP1 ISO (or DVD) from MSDN , do not use a slipstreamed DVD/ISO as results may not be what you expect here. for details of the MSDN downloads available see here 6001.18000.080118-1840_x86fre_Client_de-de-FRMCFRE_DE_DVD.iso 2,927.88 MB 6001.18000.080118-1840_amd64fre_Client_en-us-FRMCXFRE_EN_DVD.iso 3,748.59 6001.18000.080118-1840_amd64fre_Client_de-de-FRMCXFRE_DE_DVD.iso 3,704.87 6001.18000.080118-1840_x86fre_Client_en-us-FRMCFRE_EN_DVD.iso 2,943.18 MB 6001.18000.080118-1840_x86fre_client_ja-jp-frmcfre_ja_dvd.iso 2,802.59 MB for this article I'm using the following ISO 6001.18000.080118-1840_x86fre_Client_en-us-FRMCFRE_EN_DVD.iso and mounting it via Daemon Tools. Start Windows Deployment Services mmc and expand Install Images in the left pane, right click on Install Images and choose Add Image Group When prompted for the name input Windows Vista Service Pack 1 WDS should now look like this Right click on Windows Vista Service Pack 1 and choose add install image point it to the sources folder (containing install.wim) on the Vista SP1 DVD (or mounted ISO) click next and choose which images from the DVD to include (I left it as default - all) review the summary and at this point it should copy the files over (takes some time) eventually they'll be added and you can see them listed in the WDS gui now all you need to do is to PXE boot a client computer to the WDS server, press F12 to login, choose keyboard layout, and then when prompted enter your domain user/pass and then you'll be presented with a list of images youve just added (plus any others that have been added previously such as Windows 2008 server) cheers anyweb

Step 4. install SQL 2005 Servvice pack 2 Burn the en_sql_server_2005_sp2_x86_cd.iso to CD or mount it using Daemon tools, run the file called SQLServer2005SP2-KB921896-x86-ENU.exe accept the aggreement leave the feature selection as it is and click next, leave the authentication as it is and continue leve the error reporting settings as they are and click next... we dont mind a reboot so lets click next (or if you want, close each process in task manager) now we are ready to install ! time to go and make coffee, as this takes time......... after a long time you'll be prompted to reboot... click ok and then Next, and you'll see the installation summary, finally, you'll be presented with some additional information about what you've achieved click finish and then you have the option to grant Windows Vista (and later) operating systems user rights to access SQL server (they are not automatically granted administrative privileges.) in the sample below, i've given the user administrator full access to the available privileges. obvioulsy change/add users that you feel need this access in your own environment please Digg this if you found it useful cheers anyweb

Step 2. Install the Server components, tools, Books online and samples accept the EULA After it has installed the prerequisites click next when you see the welcome to the Microsoft SQL server install wizard click next it will then carry out a series of 14 system configuration checks after this you will see your registration info clkicking next will allow you to decide what services to install I selected them all and clicked next leave the default instance at it's default settings as we have SQL server 2000 already installed you'll get a message stating that it already found SQL Server Database Services 8.00.2039 place a checkmark in the empty box beside it and then for details click on the details tab go with the default authentication settings on the next screen enter your administrator password for the SQL Server Service, for the remaining serivices use the local system account leave the collation settings for service SQL Server Analysis Services as default use default configuration settings for the Report Server for the next screen leave the 'automatically send error reports' unchecked review the summary and click Install After quite some time you should hopefully see that Sql Server 2005 Setup has completed successfully. Make sure to scroll up and down to verify that all products listed have a status of 'setup finished'. click next when ready, review the summary log for any errors reported during setup. Summary.txt Once done click on Finish and reboot the server Step 3. Run the SQL Native Client Installation Wizard Start the SQL 2005 client install program When the wizard appears click next

Step 3. Install ReportViewer and WSUS on the WSUS server Download and then Install the ReportViewer. Download WSUS and then Double click on the WSUS exe, choose next at the welcome screen choose the Full Server installation accept the license agreement Select your update source and make sure to select 'Store Updates Locally' Select to use an Exisiting Database on this server click next after it has successfully connected to the database for this LAB we will choose to Use an exisiting IIS website (however read the TIP below) Tip: The IIS default web site can be used when installing WSUS on the computer that will become the SUP however it is recommended that a WSUS web site be configured for WSUS running on the active software update point so that IIS hosts the WSUS 3 services on a dedicated web site instead of sharing the same web site used by the other configuration manager 2007 site systems or other applications. This recommendation is especially important when you are installing the software update point on the site server. When you are using a custom website for wsus 3.0 the default port numbers are 8530 for http protocol and port 8531 for https protocol (ssl). These port settings need to be specified when creating the active sup for the site. click Finish when done When the Wizard appears, click on Cancel

Step 2. Install SQL 2005 SP3 Do all the steps in This post If you get a warning about IIS features not being installed then read this post and add the other IIS Role Services for SQL reporting.

In this guide I assume that you have installed and configured SCCM and have it all working ok. This guide assumes that you have installed another Server running Windows Server 2008 and that it is joined to the same domain that SCCM is joined to. Note: The Remote SUP can handle connections from up to 25,000 client computers. If there are more client computers you can configure the active SUP to use an NLB cluster which can handle connections up to 100,000 computers. Step 1. install IIS 7.0 on your WSUS server Start the Server Manager (click Start, click Run, and then type CompMgmtLauncher). In the tree view, select Roles, then in the Roles pane click Add Roles. In the Add Roles Wizard, click Select Server Roles, select the Web Service (IIS) check box, click Next, and then click Next again. You may see a message box Add features required for Web Server (IIS)? Click Add Required Features. In the Select Role Services window, make sure that the following services are selected: * Common HTTP Features (including Static Content) * ASP.NET, ISAPI Extensions, and ISAPI Features (under Application Development) * Windows Authentication (under Security) * IIS Metabase Compatibility (under Management Tools, expand IIS 6 Management Compatibility) Click Next, and then review your selections. Click Install, and finally click Close when done. Note: you can also review Technets Page on configuring IIS for WSUS.

Choose a Deployment Template In the Deployment Management Node, Right click on the Deployment Template we created earlier (All Microsoft Approved Patches) and choose properties Click on the Collections Tab and browse to Test Group make sure Include Members of Sub Collections is selected and click apply to start the Patch deployment to your Test Group click on the Schedule tab and select As Soon as Possible, include the Set a Deadline option and Ignore Maintenance options as below Note: If you are using or have configured Maintenance Windows then do not select Ignore Maintenance Windows unless you really want to ignore those maintenance windows, this remember, is just a LAB. sit back and wait, the Servers listed in your Test Group will now be targetted with the selected patches

Create some Patch Deployment Collections How you want to deploy your patches is up to you and your organisation, below is only a suggestion, use at your own risk ! Create some new Blank collections with no membership rules with each collection having a new sub-collection so they are like this Deploy Patches/Phase 3/Phase 2/Phase 1/Test Group When Microsoft Release's it's Patches you'll want to get them deployed quickly to a Test Group, to do that do as follows Add some computers to the Test Group collection (or create a link to a collection as described below) If you want to link a collection , then pick a collection from the list *remember this howto is to show you HOW you can do this, you will obviously have to create your own test collections and add computers to them yourself before linking them here*

Optional: Create an Update List Note: Update lists are useful for us as they can be used (after the event) to Report on what patches are deployed to computers and to review their compliance using those reports. If you are not interested in reporting or the compliance status of your machines then Update Lists will probably not matter to you at all and you can deploy patches without using them. If you do decide to utilise SCCM's reporting capabilities in regards to patching, then it would be a good idea to create separate Update Lists on a monthly basis to see what patches go out, and to what computers. If you want to read a guide aimed at using Update Lists for Reporting purposes then please see here. Select a search folder for example Windows Server 2008 Patches and highlight the first Windows update contained and press Shift, scroll down to the last one and press again until all patches are selected. Right click within the selection and choose Update List choose Create New Update List from the options in the wizard When the Deployment Package window appears, click on Browse to select one, or choose to create a new one and give it a descriptive name like All Windows XP Updates or Windows Server 2008 Updates as this is just a lab, we will pick the one we made earlier.. The Deployment Package is selected... choose the Internet as the download location *even if the WSUS server is on another Site Server* choose a language *english* click next to Security and Summary, the updates will be provisioned review the Confirmation, if there are any errors at this point then verify that you have correctly specified the WSUS site server Hit refresh in the Configmgr console to see your Update List.

Create a Windows Update Share In Windows Explorer, create a share that Everyone can access called Windows Updates Create a Deployment Management Task select a Search Folder that contains the patches you want to apply eg: select Windows Server 2008 Patches in the right you'll see the list of patches available (if not, you need to Synchronise WSUS with Microsoft) to do that click on Update Repository and choose Run Synchronisation. Select all and right click and choose Deploy Software Updates Enter a name for the new deployment, be descriptive eg: Windows Server 2008 Patches, the screenshot below is generic so refers to all updates..and click next .. Select the Deployment Template you created earlier and click next.. choose to Create a Package, be descriptive eg: Windows Server 2008 Patches, the screenshot below is generic so refers to all updates (All Microsoft Approved patches), point it to the Windows Updates share you created and give it a description, select Binary Replication for distribution points, click browse and selct your distribution point Choose download software updates from the internet select your language choose As soon as possible and Do not set a deadline for software update installation (keeps the updates OPTIONAL)... Note: You can change this later to force the deployment of the updates but this is fine for our LAB, in other words if you do NOT set a deadline then the updates will not be forcefully installed (they are Optional), if you want them to install (mandatory/forced) then SET A DEADLINE clicking next will start the Provisioning update progress....... *can take time...* once done you should see this and you can browse the Windows Updates share and it should be full of packages

Create a Deployment Template In Computer Management, right click on Collections and choose New Collection, create a new collection called Blank For Staging with no membership rules or advertisements. right click on Deployment Templates and choose New Deployment Template give the template a name like All Microsoft Approved Patches for Collection, point it to the Blank For Staging one we created above, and make sure sub collections are selected. Set the Display/Time settings to suppress display notification on clients, client local time for deployment schedules and duration of 1 day for Restart Setttings set them accordingly leave Event Generation as it is unless you are using Operations Manager servers and want the reporting.,... for download Settings, make sure to select download in both choices leave SMS 2003 blank and next... and next to the summary and close. your finished Deployment Template will appear

This guide assumes you have SCCM 2007 setup as described here. This guide was based upon a document entitled Patch Management directions for SCCM by Christopher Stauffer which you can find here. Please note that this guide is designed to help you get a working SUP in 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: Superflow: Software Update Deployment SuperFlow About Software Update Point: About Software Update Point Planning: Planning for Software Updates Client Settings Configuration: Configuring Software Updates How to Configure the Software Updates Client Agent How to Create and Configure an Active Internet-Based Software Update Point 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 Best Practices for Operating System Deployment Software Update Point process Flowcharts: Software Updates Synchronization Process Flowchart Software Update Deployment Process Flowchart Deployment Package Process Flowchart Related: How to obtain the latest version of the Windows Update Agent 1. Install WSUS Install WSUS but do not configure it. Once done, make sure the Software Update Point Role is installed on the SCCM Server. Once you've added the Software Update Point role, verify that it is installed by checking the SUPSetup.log, it should have a line which reads Installation was successful 2. Create some Search Folders In the Software Updates section, right click on Search Folders and choose New Folder, give the new folder a name like Enterprise Searches (we willl store our yearly searches here) Right click on our new folder and choose New Search Folder, select the following options from step 1 (in the screenshot), BulletinID, Expired and Superseded in step 2, Set the BulleinID to MS plus the last two digits of the year eg: MS08 Set Expired to No Set Superseded to No Make sure that Search All folders under this feature is selected and give the search a name, eg: 2008 patches Now that you know how to make a Search Folder, let's make one for Monthly searches, so right click on Enterprise Patches and choose New Search Folder Fill it in as follows and now make one for Windows Server 2008, we do this by adding Product as a search criteria and typing in the search phrase to look for, naturally you can customise it to suit your needs.

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 In addition to the above you must have completed Part 1 of this guide Create the Task Sequence right click on Task Sequences and choose New Task Sequence choose the second option (Build and Capture a reference operating system image) fill in your Task Sequence Information click browse and select our X86 boot image Note: if you don't see the x86 windows PE boot enviroment for SCCM 1.0 EN-US image listed then follow these steps first. On the Install Windows screen click on Browse and select the XP SP3 operating system install package we created in Part 1. Input your product key and make sure to enable the local Administrator account, Configure Network Here we need to enter our network configuration and click next, choose Join Workgroup (recommended best practise). Although joining the domain will work just fine you may have GPO's in place, or startup scripts (login scripts) etc which may taint your master image, keeping it off the domain will keep it clean. on the Install ConfigMgr screen, browse to the Predefined ConfigMgr Client Package we created earlier for the Updates and Software screens choose don't install any (ie: next, next) for the System Preparation screen click on browse and choose the sysprep package we created earlier fill in the image properties On the Capture image screen, browse to a share on your network for copying the image to, and give the file a name eg: \\WIN-AE2V1IRN067\captures\xpsp3r.wim fill in your user account for capturing the image with, I use SMSadmin click next, next and close at the confirmation screen

Please note that this guide is designed to get you Deploying Windows XP 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: Operating System Deployment: Operating System Deployment in Configuration Manager Overview of Operating System Deployment 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 Best Practices for Operating System Deployment 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 and you should have reviewed part one and part two of Deploying Windows Vista, which covers setting up the PXE Service point. Note: In this guide I've used the en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso available on MSDN, this is the Retail version of XP, you should really use the VL (Volume License edition) in conjunction with your VL key to deploy XP. Note: This Deploy XP guide will create a build image of Windows XP using the XP cd mentioned above. Once the image is created we will Capture the image. This whole process is known as 'Build and Capture'. The captured image can then be used in a separate task sequence to Deploy XP. Import XP SP3 as an Operating System Install Package In the Operating System Deployment node of ConfigMgr, right click on Operating System Install Packages and choose Add Operating System Install Package. click on browse and browse to the network share where you have previously copied the XP SP3 CD contents to... (in my case that's \\WIN-AE2V1IRN067\iso\Xp sp3 retail) once you have the Data Source correctly specified, click next on the General Page fill in some details about this XP SP3 image... review the summary, click next and click close at the confirmation screen.

Please note that this guide is designed to get you up and running with SCCM in a LAB Environment as quickly as possible, so server roles are not going to be separated unless otherwise stated. This guide is provided as is, if you find any errors please report them in the forums. This guide refers to Service Pack 1 but you should use the latest version available currently which is Configuration Manager 2007 Service Pack 2. The latest version of this guide can always be found at http://www.windows-n...ws-server-2008/ In a production environment please consult Technet for best practise, see below links: Prerequisites: Prerequisites for Installing Configuration Manager Configuration: System Center Configuration Manager 2007 How to Configure Windows Server 2008 for Site Systems 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 Best Practices for Operating System Deployment Checklists: Example Configuration Manager Installation Checklist Example Configuration Manager Upgrade Checklist This guide assumes that you have first setup Windows Server 2008 and configured it for Active Directory, with DHCP (you only need steps 1 and 2 this guide). If you want to deploy operating systems within SCCM you will then also need the Windows Deployment Services installed, and that is covered in steps 3 and 4 of this guide). You must have installed and configured IIS (for SCCM) and installed SQL Server 2005 SP2 (or SQL Server 2008 with this hotfix) and WSUS (you can install WSUS later if you want, it's only required for the SUP role). Please note: WSUS SP2 is a role within Server 2008 R2 so if you are using Server 2008 R2 you can install WSUS Sp2 by adding the role. If you are thinking about hosting SQL Server on another server than the SCCM server then please read this post. You should also read the SCCM prerequisites on Technet. We will be using the MSDN version of SCCM 2007 Sp1 namely en_system_center_configuration_manager_2007_with_service_pack_1_x86_dvd_x14-66461.iso so burn it to DVD or mount it in Daemon tools (or similar). Part 1. Run the prerequisite checker and fix the warnings/errors. When the menu appears, click on Run the prerequisite checker, we'll do this to see if our Windows Server 2008 needs any additional tasks performed prior to installing SCCM 2007 sp1. enter your servername as below (leave OUT the instance name or you may get errors explained in the Final Note) this gave me two prerequisites which needed looking at, the AD Schema extensions, Microsoft Remote Differential compression. If you want to get more details of the problems identified, then check c:\ConfigMgrPrereq.log (and c:\ConfigMgrSetup.log) or double click each warning/error in turn to get a short description (scrollable) of the problem. My first problem was that I needed to extend the Active directory schema, to do so I followed this guide. Once I had extended the active directory schema, I ran the prerequisite checker again, That left me with the RDC error, That led me here and that in turn had this info To add Remote Differential Compression to site servers and branch distribution points In Server Manager, on the Features node, start the Add Features Wizard. On the Select Features page, select Remote Differential Compression, and then click Next. Complete the rest of the wizard by clicking install then close. Now run the prerequisite checker again and the RDC error should be gone Once you have no warnings or errors, please proceed to Part 2. Final Note: if you entered the instance name at the start of this guide, you may get an error which states The Technet page for Setup Prerequisite checks states:-

Before starting this, make sure to backup all your SQL databases, any problems arising from doing this are your own responsibility, always test this on a test lab computer scenario before doing it in your business environment. Download the following from Microsoft connect or your MSDN downloads area. en_sql_2005_std_x86_dvd.iso and en_sql_server_2005_sp2_x86_cd.iso burn them to DVD/CD or mount them using tools such as Daemon tools. Step 1. Run the upgrade advisor to see what issues may need to be resolved Start the SQL Server 2005 Standard edition DVD and select Install SQL upgrade Advisor from the list of options. When the wizard appears click next accept the license aggreement enter/verify your registration information click next when asked what features to install (go with the default) choose install to install the SQL Upgrade Advisor once done click on Finish Now that it's installed, let's run it, so click on Start, All Programs, Microsoft SQL Server 2005, SQL Server 2005 Upgrade Advisor When the Upgrade Advisor splashscreen opens, click on Launch Upgrade Advisor Analysis Wizard. This will launch another wizard click next to continue choose the components you want to analyze (i selected all) when asked how the Upgrade Advisor should connect go with the default settings unless you have changed them previously when installing SQL click next when prompted for what databases to analyze if you get an error about not finding the notification services hit the back button three times and remove the checkmark from 'notification services' and continue again. click next for the DTS parameters view the confirmation and click Run to start... once done you can click on Launch Reprt to see the details viewing the report will allow you to see what components to change before attempting the actual SQL upgrade.

Please note, this is for lab testing purposes, use it at your own risk, always backup your SMS database and site before attempting any radical changes such as an upgrade. If you break your production setup by doing anything here I am not responsible, use at your own risk. Test always in a LAB first. Before performing the steps below you should perform a test DB (database) upgrade as detailed below.WARNING: the following can corrupt the database if used on a production database. It cannot be used more than once on the same database copy. Step 1. Test the DataBase upgrade Note you should have backed up your SMS database using SMS database backup prior to running this. In addition, copy your SCCM 2007 SP2 media to a local folder for the DB upgrade process. On your SMS 2003 Server:- Open SQL Server Management Studio. Right click Databases select Restore Database. For Database (type in): CopyofServerName (replace ServerName with your SMS server name) Select From Device, use ellipses button to browse. Click the Add button. in Files of Type, use drop down to select all Files(*) Expand the location where your SMS database is backed up to, for example C:\SMS_BACKUP\SiteDBServer select the SMSbkSQLDBsite.dat file. Click Ok, and Ok again. Select Restore Box to check. Ok, and Ok to Restore was successful Open Command prompt and Browse to your SCCM Sources Media folder. SCCM 2007 with SP2\SMSSETUP\BIN\I386 setup.exe /testdbupgrade CopyofServerName Answer YES, Click Begin Upgrade Open log files: C:\ConfigMgrPrereq.log, C:\ConfigMgrSetup.log A window should appear and say successful If unsuccessful stop here, if successful, move forward. Clean up CopyofServerName Database. Right click CopyofServerName database, select Delete, leave defaults, click ok. Step 2. Start the Upgrade First of all download the iso from your MSDN account or Microsoft Connect. once done, burn it to DVD or mount the ISO using Daemon tools or similar. Before starting the process you'll need to know the prerequisites, and thankfully there is a prerequisite checker included on the DVD. Next you should run the prerequisite checker so let's run that and see what it says If like me you already have an SMS 2003 server setup then it will automatically choose the upgrade option, as this server is the only SMS site we will click ok to continue. After some scanning it will present you with a results page, double clicking on a result will tell you what you have to do to fix the problem. As I was running SQL 2000 sp4, it correctly flagged that I needed to upgrade that to SQL 2005, at this point I exited the SMS>SCCM process (click on cancel) and got my SQL 2005 iso (en_sql_2005_std_x86_dvd.iso).

Step 4. Configure the Windows Deployment Services gui (mmc snap in) Click on Start/All Programs/Administrative tools/Windows Deployment Services. at this point we can see that WDS is not configured yet, so let's do that now. right click on the server name in the left pane and choose Configure Server at the welcome page click next change the remoteinstall path from the default C:\RemoteInstall to D:\RemoteInstall I put a checkmark in each of the DHCP options then clicked next I then chose to respond to all known and unknown computers (by default it's set to Do not respond to any) Please note, if you want to set this option to only respond to known computers, then you can do so, but you will have to prestage your computers in Active Directory to do so clicking on Finish applies these settings when done, you'll be told that the configuration is complete and that you can now add images to the WDS server, click on Finish (again). Step 5. Adding boot.wim and install.wim Note: You should use only the boot.wim file from the Windows Server 2008 DVD. If you use the boot.wim file from the Windows Vista DVD, you will not be able to use the full functionality of Windows Deployment Services for example, multicasting. If you have the Windows Vista SP1 dvd, you can safely use that for the boot.wim. The Windows Deployment Add image wizard will appear, insert your Windows 2008 Server DVD and click Browse, select the sources folder on the Windows 2008 DVD and then click next you'll be prompted to create a new image group, lets call it ImageGroup1 (the default name, you can change it later to Windows Server 2008 or Windows Vista Sp1 or whatever...). review your settings and click next when ready After a long while, the selected images will be added to the WDS server click finish and review the WDS server as it is now in the Boot Images pane, you should see Microsoft Windows Longhorn Setup (x86) and this is the original boot.wim file from the Windows 2008 Server DVD, please note that this is the default description name of the image, you could change it when addint the boot.wim image to something more descriptive as in this example In the Install Images pane, we can see the six available images from the Windows 2008 Server DVD, these are based upon the install.wim file on the DVD. you can now PXE boot your client computers to the Windows 2008 WDS server. troubleshooting note: if you add a new image to WDS and attempt to pxe boot and then install the image but get an error saying something like 'could not display the list of' then make sure you have used BOOT.WIM from a Windows Server 2008 DVD or Windows Vista sp1.