anyweb

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

as you posted this here and on Technet, I answered it on technet first http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d38c66e7-fc2a-4430-aa16-207d19763591 cheers niall

Now that we have created our new Deployment Package lets deploy it ! Expand our Deployment Management node, and select our Windows Vista Service Pack 2 Standalone X86 X64 deployment management task Right click and choose properties, click on the Collection Tab and then click on Browse Pick a Test Collection (which you must create yourself, and which must have some test Vista computers that you want to test this Service pack deployment on) and Click ok click Apply then ok you are now ready with the Deployment. Monitor your Vista Test Clients to verify the Service Pack is deploying... At this point, you must monitor your Vista Test clients to verify the Service Pack is actually deploying you can do this by checking your WUAHANDLER.LOG file, it should show something like the following the (Missing) bit means that the update isn't installed yet, later in the log you'll see

In this guide I will show you one way of Deploying Service packs using your Software Update Point in SCCM. In this example, I will deploy Windows Vista SP2 to our Vista Clients (both 32 bit and 64 bit). In a production environment, always refer to Technet for Best Practise. Create a new deployment package Expand your Software Updates node in ConfigMgr and Run a Syncrhonizaation by right clicking and choose Run Synchronization.. Once it is done, expland your search folders and expand your Windows Vista All Updates search folder. The Windows Vista All Updates search folder criteria are * Product "Windows Vista Ultimate Language Packs" OR "Windows Vista" * Expired No * Superseded No In the Look For drop down menu, type in Service Pack 2 Standalone and click on Find Now, you should see results similar to below. Select all updates found in the search, right click and choose Deploy Software Updates Accept the License Terms give your deployment a name like Windows Vista Service Pack 2 Standalone x86 x64 select our default All Microsoft Updates Deployment Template which we created when we setup the SUP choose to create a new deployment Package give it a suitable name and description such as Windows Vista Service Pack 2 Standaloneand create a new folder for the service pack such as \\WIN-CILZXI45G1Q\patches\Service Packs\Vista\Vistax86x64Sp2 Tip: For package source, you can click on browse, then browse to your chosen server, right click on your patches share, create New Folder, give it a suitable name Select your Distribution Point(s) Select download software updates from the Internet and click next select your language and then set your schedule like this review the progress (might take a while to download the Service Packs) finally after a long wait, your 1.75GB of updates should be downloaded and provisioned

which boot image are you applying the drivers to and can you provide a link for me to the drivers you have tested

setup.exe -ms will install FireFox silently after you rename the firefox setup.exe file no need for any other package maker to do that.. but i see your point, having to update it regularly could be a pain, I would tend to only upgrade apps when a security problem requires it or for functionality reasons, I would suggest you contact the good folks at FireFox and ask them if they can assist with some SCUP implementation cheers

i do, and the forum is closed for now, sorry.

you must keep the blank for staging collection EMPTY at ALL TIMES never put systems in it and never link to other collections in it, ever. you do this because all of your Deployment Management Tasks will point to the 'blank for staging' collection by DEFAULT. That is the way you want it to be, the LAST thing you want to happen is for an untested patch or service pack to go out to all your servers or clients causing mayhem in your organisation keep blank for staging empty Always, and use the phase 1,phase 2, phase 3 and test subcollections to test patches, working your way from test > phase 1 > phase 2 > phase 3 by the time you've reached phase 3 ALL of your systems should be targetted and patched with your selected patches and you then point your Deployment Management tasks back to blank for staging cheers

what do the ccm logs on your client say ? any errors there ?

hi dezdog make sure you are using the windows Vista network drivers for boot.wim see the following post here to find out how to inject the drivers properly into a boot.wim file

nice, now all you have to do is add a © windows-noob.com at the beginning of the PDF cheers