anyweb

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.

the System Status node is just below the Computer Management node in ConfigMgr do you see it ?

personally i would fix all the problems one by one in site status before attempting any service pack upgrade or anything else for that matter, it will teach you lots about configuring sccm, that said, are you using windows 2008 server Sp1 or SP2 or r2 ???

how weird, is your system status in sccm reporting ok ? i'd like to find out why the package from definition is missing, hence my questions if there's anything you think would shed some light on this let me know cheers niall

hi Kevin i'm very aware of why the red exclamation mark is there i'm just trying to understand why you are seeing (or rather not seeing) this package from definition problem how did you install SCCM and is there anything you did that may have contributed to this ? what user are you logged on as ? is MDT installed and configured ?

interesting tip Peter thanks ! now back to the problem, which i'd really like to understand, i looked at the screenshot some more and there is the red exclamation mark there to the right of where the package from definition SHOULD be so can you try clicking there in the whitespace and click next, what happens ?

in addition to the above you can look at System Status, package status and it will reveal.... the package and its ID

how odd, i'm in the process of re-doing the Deploy 7 guide and i see that package from definition listed, are you using SCCM 2007 SP1 or another version ???

welcome to the forums kevin, ok can you post a screenshot of what you see please ? also, you need sp2 to deploy windows 7 and its available (beta) on microsoft connect

Microsoft Deployment Toolkit (MDT) 2010 RC - now available ws2008 r2 blog logoWe are pleased to announce the immediate availability of the release candidate of MDT 2010. This release contains numerous bug fixes since MDT 2010 Beta 2. MDT 2010 RC has been tested and will work with Windows 7 RTM and Windows Server 2008 R2 RTM as well as all previously supported operating systems. Improvements to MDT 2010 RC allow you to: * Access deployment shares from anywhere on the network and replicate files and settings across organizational boundaries or sites. * Organize and manage drivers, operating systems, applications, packages and task sequences with an improved UI. * Automate all UI functionality utilizing the new Windows PowerShellTM. For more information, see http://blogs.technet.com/msdeployment/archive/2009/08/19/mdt-2010-release-candidate-is-now-available-for-download.aspx. To grab the bits, head to https://connect.microsoft.com/site/sitehome.aspx?SiteID=14. via > http://209.34.241.68/keithcombs/archive/2009/08/19/microsoft-deployment-toolkit-2010-rc-now-available.aspx

what makes you think it doesn't support an in-place migration ? To get an In-place migration, simply advertise your OSD Task Sequence to a computer while Windows is running, ie: do not PXE boot the computer, it will start the Task Sequence and automagically and your USMT status will be registered as In-place.

you could always disable uac via gpo

how long did you wait ? what do your site status logs tell you ?

take a look at the list of SCCM log files here the ones that we'd like to see are any with obvious errors about your problem, seeing as your server logs are ok then we need to see what's happening on your clients..

have you added any network drivers to boot.wim ? you need to add windows vista network drivers for the nic to both your X86 and X64 boot.wim files then redistribute those boot.wim files to the distribution points cheers