anyweb

with XP deployments its normally ALWAYS the sata mode in bios, so change it from AHCI to ATA and reboot and try again

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: Determine Your Operating System Deployment Method 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 Step by Step 4 part guide to Deploying Windows 7 Enterprise. Deploy Windows 7 part 1. Build and Capture Part 1 is the longest part of the 4 part guide and covers the steps required to successfully Build and Capture Windows 7 RTM. It was tested successfully on both X86 and X64 Enterprise RTM releases. Step 1. get the ISO Step 2. Add Operating System Install Package Step 3. Create Distribution Point for the Image Step 4. Update Distribution Point Step 5. Create the Build and Capture Task Sequence Step 6. Advertise the Build and Capture Task Sequence Step 7. Add a system to the Build and Capture 7 collection Step 8. PXE boot the newly added Windows 7 client Deploy Windows 7 part 2. Add the captured WIM file Step 1. Add the Captured Wim file as an Operating System Image Step 2. Distribute the Captured WIM file Deploy Windows 7 part 3. Create a new Task Sequence Step 1. Create a new Task Sequence Deploy Windows 7 part 4. Advertise the Task Sequence Step 1. Advertise the Task Sequence Step 2. Last Actions enjoy ! cheers

look at my post above yours

hyperv works fine, my second lab runs exclusively on hyperv and that is one AD server (2008) one SCCM server (2008), one Server 2008 R2, 2 xp and 2 windows 7 clients curently and i too didn't have to add anything to the boot images, all the machines aside from AD and SCCM were deployed via the sccm server in hyperv so, we'll need to see your log files to understand what you problems really are, or are you forgetting to Add a Legacy Network card and adding it as first boot device ?

are you deploying XP or what ??? and on what type of hardware

indeed, and the guide actually points that out too i've now re-worded it to say 'local administrative' to make it clearer and included a link back to here so others can see what happens cheers niall

no, you need the full release version

i just did a quick test on a win7 virtual client here and using a user that is a member of local administrators on the windows 7 pc i could remote desktop client to it via SCCM, all systems collection, right click, choose Start, Remote Desktop Client and it worked just fine, no UAC prompts at all. And this is on a clean install of windows 7 with no gp's applied aside from 1. enable remote desktop 2. disable firewall the os was Windows 7 Enterprise X86 (32bit)

its on Technet and MSDN

don't use the UPGRADE dvd, use the FULL release version available from MSDN or TECHNET or your Volume License download page

ok then good verify that the ConfigMgr DVD that you are using is the correct one from Technet and not the Upgrade version.

is this server a member of an AD ?

ok then on one of the clients that is not showing up as approved, as Peter requested can you post thos two logs here

you say only 4 out of 20 are showing in the console, do you mean that they are all showing up in the console but only 4 show as 'approved' ? or `?

ok should be fixed now, time was wrong on the server

are you seeing the wrong time in posts or somewhere else ?

Step 1. Advertise the Task Sequence In the Operating System Deployment node, click on Task Sequences and right click on the Task Sequence we just created, choose Advertise when the General screen comes up, choose the settings as below in the screenshot, you can browse to a collection called Deploy 7 (you should have created this collection beforehand). 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). select the following Distribution Point options show the task sequence progress and click next, next, next and close. at this point you can right click on the Deploy 7 collection, choose properties and you'll see our new Task Sequence is advertised to that collection Step 2. Last Actions All you have to do now is Add systems to the Deploy 7 collection and pxe boot them, then they will get imaged with our pre-captured Deploy 7 Enterprise X64 RTM image. You can do this in many ways, either by Direct Membership, Computer Association, AD groups membership.... job done !

Step 2. Distribute the Captured WIM file Expand Operating System Images and then Expand our newly added Windows 7 Enterprise RTM Release node right click on Distribution Points and click on New Distribution Points as this is NOT a boot image only select the first DP for Copy Package click next and close Right click on Distribution Points again and this time choose Update Distribution Points, click Yes when prompted Next Step, Create a New Task Sequence

Step 1. Create a new Task Sequence We will now create a new Task Sequence to deploy the captured WIM file from part 1. In ConfigMgr, expand Operating System Deployment and right click on Task Sequences, choose New Task Sequence Choose the first option, Install an existing image package fill in your Task Sequence information and browse to the X64 boot.wim file when the Install Windows screen appears click on browse and select our recently added operating system image for the Image drop down menu select 1-1 and don't forget to enter your product key and administrator password option Add your Domain Join info select your configmgr client from definition package (make sure this package is made AFTER you install SCCM SP2) choose whether you want to capture users data or not *USMT* using your USMT4 package Note: you will have to create the USMT 4 package separatly, if you have not created the USMT4 package you can deselect all three options on this screen. as I am not using a SUP on this lab, I will not be installing any updates... click next at the install software (we won't install any software packages now) and close at the confirmation screen Next Step > Advertise the Task Sequence to a Deploy Windows 7 collection

This guide assumes that you have completed part 1. Build and Capture of Deploy Windows 7. Step 1. Add the Captured Wim file as an Operating System Image In ConfigManager, expand the Operating System Deployment node and right click on Operating System Images and choose Add Operating System Image use the Browse button to browse to the captured WIM file from part 1 and click next when done give the WIM file a good descriptive name such as Windows 7 Enterprise X64 RTM Release click next and close at the confirmation screen

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

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

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

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.