anyweb 455 Report post Posted February 4, 2009 Please note that this guide is designed to get you Deploying Windows 7 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 that you've installed and configured SCCM 2007 already and that you have set it up to deploy operating system's such as Windows Vista SP1. In addition you must have installed SP2 for ConfigMgr. It is available for download here. The most up to date version of this Guide will always be found in the Deploy 7 section of the windows-noob.com forums. For best practise information about deployments using SCCM you should always consult with Microsoft Technet. Step 1. get the ISO I chose the 64bit Enterprise version which was en_windows_7_enterprise_x64_dvd_x15-70749.iso. Now that you have the ISO, mount it or burn it to DVD and copy the contents of it (all files and folders) to a network share on your SCCM server. Step 2. Add Operating System Install Package In System Center Configuration Manager 2007 expand the Operating System Deployment node and right click on Operating System Install Packages, choose add operating system install package. When the Add Operating System Install Package wizard appears, point it to the path where the Windows 7 operating system files can be found eg: \\SCCM\sources\os\7\rtm\x64\ent\ fill in the name, version and a comment about the image review the summary and verify the confirmation Step 3. Create Distribution Point for the Image Now that we have added the operating system files to our available operating system install packages, we need to create a new distribution point for it so let's do that. Expand the newly added Windows 7 image you just added in Operating System Install Image Packages and right click on Distribution Points, select New Distribution Points. Click next on the Welcome screen. As this is not a boot image (it's an Entire Operating System), select only the first distribution point (do not select the PXE one) click next and close. Step 4. Update Distribution Point now that we have created a distribution point, let's update it, so right click on distribution points and choose update distribution points, answer yes when prompted. Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted August 21, 2009 Step 5. Create the Build and Capture Task Sequence In the Operating System Deployment node of ConfigMgr, right click on Task Sequences and choose New Task Sequence. when the wizard appears choose the Build and Capture option fill in the Task Sequence Information press browse and choose your boot image, in this case pick X64 Windows PE boot environment for SCCM 6.1.7100.0 en-US on the Install Windows screen, for Package click on Browse and select our Windows 7 operating system install package Leave the product key BLANK and assign an Administrator Password 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. Install ConfigMgr click browse and pick your configmgr Client Installation Package (from definition) which we created before This step is configured with the following switches to locate the Fallback Status Point, Server Locator Point and Management Point. FSP=xxxxx SMSSLP=yyyyy SMSMP=zzzzz where xxxxx=Fallback Status Point server name yyyyy=Server Locator Point server name zzzzz=Management Point Server Name Install Software Updates for software updates, choose whether or not to install them during the build (only applicable if you have implemented a SUP), you should have your SLP in use and you need to install the client with the SMSSLP and SMSMP switches as listed above. if you want to install some software, add it now by clicking on the yellow star and selecting the package and program click next at the System Preparation screen add some descriptive properties for the image fill in your Capture Path (UNC share) and capture account details, you can create the capture folder after clicking browse review the summary and click next and then click close at the confirmation screen If you'd like to download a sample Build and Capture Task Sequence for Windows 7 then click here. Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted August 21, 2009 Step 6. Advertise the Build and Capture Task Sequence We will now advertise the Build and Capture Task Sequence to a collection called Build and Capture 7, this collection is empty and without any membership rules, we only use it for creating new images for Windows 7. In the screenshot below I've created some collections for deploying, capturing or build and capturing operating systems and this makes it easy and clear to advertise specific task sequences to the correct collections. Right click our newly created task sequence and choose Advertise. when the new advertisement wizard appears select the following option make this task sequence available to boot media and PXE and browse to and select the Build and Capture 7 collection shown above Schedule Set your schedule depending on whether you are in a Lab or Production Environment. For a Lab Environment Make the Task Sequence mandatory by clicking on the yellow star and select As soon as possible. Select ignore maintenance windows when runing program and allow system restart, set the program rerun behaviour to always rerun program so that we can rerun the task sequence over and over as we require for testing. For a Production Environment In a Production environment set the advertisement from Mandatory to Optional, this gives us less risk of an accidental deployment but also introduces the possibilty of choice. if you want to remove choice then keep the advertisement mandatory but change the program rerun behaviour to never rerun (see below screenshot). choose the following Distribution Point options show the task sequence progress click next through the security and summary and review the confirmation Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted August 21, 2009 Step 7. Add a system to the Build and Capture 7 collection In Operating System Deployment, right click on Computer Association and choose Import Computer Information choose Import Single Computer enter the computer name and mac address review the choices browse to the Build and Capture 7 collection Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted August 23, 2009 Step 8. PXE boot the newly added Windows 7 client PXE boot your Windows 7 client and it should start the process of PXE boot starting Windows PE Starting the Task Sequence (Windows is Starting up) and then formatting the hard disc after the format the Windows 7 installation begins files get copied and expanded until they reach 100% finally it continues with the next bits (software updates if chosen) and then reboots after the reboot it will attempt pxe boot again if pxe is the first boot device and correctly do an abortpxe followed by continuing with the installation and now we get to see the lovely Windows 7 boot screen animation back into the Task Sequence after a short delay it will reboot the computer again and preparing the computer for the first use setting up windows and the configmgr client and then it installs FireFox followed by the third Reboot then it runs Sysprep Note: if sysprep fails for you at this point with SMSTS.log file reporting verifycapturerequirements fail 8004001 then simply recreate the ConfigMgr client package from definition, and push it out to a DP then use that client package in your TS after sysprep it will reboot again and then start the actual capturing process scanning volume 1 of 1 then capturing the volume to your network share specified while creating the Task Sequence finally it will reboot again and start the computer with your sysprepped settings and the Build and Capture is now complete On your SCCM server, browse to your capture folder (I changed the path of this during this guide due to lack of server space) and you can see the newly captured Windows 7 Enterprise WIM file We will be using that file for part 2 of Deploy Windows 7 Quote Share this post Link to post Share on other sites
sweety_devil 0 Report post Posted September 17, 2009 HI, Thank you for your website, it is the best I've ever seen ! I used your guide "Deploy Windows 7 part1" and it doesn't work for me. When I boot my computer, I have an IP and the first screen "Windows is starting" loads but after that I have a black screen and my computer reboot. Do you know what is the problem? I should have the next screen about the formatting. Thank you. Quote Share this post Link to post Share on other sites
Peter van der Woude 143 Report post Posted September 17, 2009 You probably have to add a NIC driver to your bootimage Quote Share this post Link to post Share on other sites
sweety_devil 0 Report post Posted September 17, 2009 Could you explain me how to do it? I have an error when I click on the Drivers tabs (see doc1.pdf). I have SCCM v4.00.6221.1000 and SQL 2008 and Window server 2008 SP2. Thank you Doc1.pdf Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted September 17, 2009 you can't do this without installing SP2 RC for Sccm 2007, and your version doesnt match that secondly you need to install a hotfix or two for SQL 2008 to get it to work properly with SCCM ConfigMgr 2007 SP1 customers must apply hot fix KB955262 sql server 2008 sp1 might negate the need for that hotfix, Quote Share this post Link to post Share on other sites
sweety_devil 0 Report post Posted September 18, 2009 Thank you, I installed SCCM R2 and SQL SP1 + patch KB955262. Now the error next to drivers has disappeard. But I have the same problem: my computer reboot after it tried to do a netwotk connection. I added the driver vista x86 for the broadcom card and Intel card in the boot image but it is the same problem. My computers are HP DC7100,DC7600,DC7700,DC7800,DC7900. Thank you for your help. Quote Share this post Link to post Share on other sites
jhkappert 0 Report post Posted October 8, 2009 Little question where do i get the X64 Windows PE boot environment for SCCM 6.1.7100.0 en-US? I trying to deploy windows 7 and use the PE from the vista guide. Greetings Jan Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted October 8, 2009 its part of the new waik for windows 7 that is also part of the RC so if you install sp2 rc youäll have the new WAIK Quote Share this post Link to post Share on other sites
jhkappert 0 Report post Posted October 9, 2009 its part of the new waik for windows 7 that is also part of the RC so if you install sp2 rc youäll have the new WAIK Thnx for your fast answer. Ik get the following error when i build and Capture windows 7, the error is 0x00000008. When i look in logging i dont see the error. The only thing i can find in the logging is Failed to pause component system Health Agent. I get this error message in the last stage when sccm is trying to make the capture. Attempting to pause System Health Agent TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Checking if CCM component System Health Agent is paused TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) spIComponentController->IsPaused(ulPauseCookie, &ePauseState), HRESULT=80040200 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,3969) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Failed to pause component System Health Agent (80040200) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) IsPaused(ulPauseCookie, ePauseState), HRESULT=80040200 (e:\nts_sms_fre\sms\client\tasksequence\napcontrol\tsnapcontrol.cpp,53) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Unable to query SHA for pause state (0x80040200). Skipping SHA pause. TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) _SMSTSReturnToGINA variable set to true TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Remediating TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) pNAP->GetSystemIsolationInfo(&pNAPInfo, &bUnknownConnections), HRESULT=8027000c (e:\nts_sms_fre\sms\client\tasksequence\napcontrol\remediate.cpp,463) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) GetSystemIsolationInfo(spNapClientInfo, &IsoStat), HRESULT=8027000c (e:\nts_sms_fre\sms\client\tasksequence\napcontrol\remediate.cpp,633) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Error getting system isolation info. Code 8027000C TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) ComputeComplianceAndRemediate(&QState), HRESULT=8027000c (e:\nts_sms_fre\sms\client\tasksequence\napcontrol\tsnapcontrol.cpp,173) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Remediation failed. Code 8027000C TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) hr = m_oNapCtrl.Remediate(QState), HRESULT=8027000c (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,1765) TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Remediation failed with error code 8027000C TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) Initializing TS Engine TSManager 10/9/2009 10:43:07 AM 2168 (0x0878) smsts.log smsts-20091009-104519.log Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted October 9, 2009 unless you are using NAP you can ignore all the system health validator checks... Quote Share this post Link to post Share on other sites
jhkappert 0 Report post Posted October 12, 2009 unless you are using NAP you can ignore all the system health validator checks... How does that work? Can you tell me how to ignore all the system health? Quote Share this post Link to post Share on other sites
jhkappert 0 Report post Posted October 13, 2009 How does that work? Can you tell me how to ignore all the system health? I found the problem. The build and capture pc joint a domain. sysprep didnt like that. Quote Share this post Link to post Share on other sites
manjurainbow123 0 Report post Posted November 20, 2009 I am getting the following error while booting into pxe... PXE-T01:File not found PXE-E3B : TFTP Error -File not found PXE-M0F : Exiting intel PXE ROM Operating system not found Can anybody help... My Setup is....(WINDOWS 2003 Servers sp2) Windows DC is running on VMWare and DC is hosting DHCP SCCM SP2 R2 is running on another VM and it is having WDS role i have doubt in this setup IS IT CORRECT TO HOST wds ON sccm SERVER and DHCP on domain plz help One more query..... I dont have any image in WDS but i have it in SCCM Is it required to add image in WDS too I am confused here little bit (Adding images in WDS and SCCM both is required?) Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted November 20, 2009 are you trying to deploy windows 7 ? did you look at the troubleshooting section here ? Quote Share this post Link to post Share on other sites
manjurainbow123 0 Report post Posted November 20, 2009 Yes I am trying to deploy windows 7. I tried your DHCP options from http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/page__p__958entry958 Now I am getting error abortpxe.com as attached screenshot Also I now saw weird action of my SCCM server After importing the computer details the PC is not adding to the specified Collection. instead it is showing in the All Systems collection. Why this happens, I am really tired of this sccm behavior...... Quote Share this post Link to post Share on other sites
Jimm 0 Report post Posted December 10, 2009 Good day, The guide really simplified everything required to get SCCM up and running and able to capture & deploy Win 7. I had a few issues with SATA controller drivers but got that all ironed out. One issue that I have no clue what to do with is this. In my TS, I have the line where I specify the license key info. I have a volume key from MS. If I enter this into the TS, it fails every time. Also, I noticed that the only way for me to get past this is to leave the key blank and specify do not activate. I have an ISA device and PIX in place here. I am assuming that since this device is not on the domain, it cannot get logged into the ISA device and thus cannot get to the activation services on the net. I have a build / capture image saved from when I left the license key out of the TS. Can I somehow inject the key back into the image in a new TS? Also, I now have this device on the domain and it is activated. Can I instead capture this image as is and use this as my base for new metal builds? I'm certain all are possible, I guess I am erally asking which way is the best practice? Jimm Quote Share this post Link to post Share on other sites
ejon 0 Report post Posted December 13, 2009 Hi Guys I have confifured my reference Windows 7 image and have tried to capture it using the same TS. However....... 1. it reinstalls win 7 2. then it runs sysprep 3. then it captures it...... ????? does this mean to purely just capture the image is to Disable the Task Sequence of installing windows 7?? cheers EJ Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted December 14, 2009 if you just want to capture it then yes disable the entire BUILD section of the build and capture ts, here's a guide for Capturing Windows 7 cheers niall Quote Share this post Link to post Share on other sites
ChandanOmkar 0 Report post Posted February 6, 2010 I have started working with SCCM. I am facing a problem. After Starting the Task Sequence (Windows is Starting up) the screen shot is mentioned below, the system gets restarted. It is not moving to formatting disk, as per mentioned in this site. Hey Niall Please help. Quote Share this post Link to post Share on other sites
anyweb 455 Report post Posted February 6, 2010 then you probably need to load the network drivers for windows 7 into the windows pe boot image, or something else, we need to see your SMSTS.LOG file from the client to be sure.. Quote Share this post Link to post Share on other sites
ChandanOmkar 0 Report post Posted February 8, 2010 then you probably need to load the network drivers for windows 7 into the windows pe boot image, or something else, we need to see your SMSTS.LOG file from the client to be sure.. Thanks Niall for your reply. Please find the attached smsts.log file from the client. Thanks Chandan smsts.log Quote Share this post Link to post Share on other sites
