anyweb

screenshots describing the above process are here

to create the USMT 4 package point to the USMT 4 folder root and you are done, no need to create any program, make sure to distribute the package to your dp's. which task sequence did you look at ?

if you leave the Product key blank in the Task Sequence does it work then ?

power management (core parking) branchcache direct access just a few thoughts, cheers niall

yes download mdt2010 instead (needed for win7) and continue with the vista guide substitue any reference to mdt 2008 with mdt2010 cheers niall

The Solution Accelerator team has released an updated guide: Microsoft Application Virtualization 4.6. This free guide, now updated for App-V 4.6, provides actionable guidance for planning your application virtualization infrastructure. With App-V, your organization can respond to the complex challenge of managing applications. This guide simplifies your App-V planning process. Updates now include information on how App-V supports Windows 7 and Windows Server 2008 R2, including such features as BranchCache; support for 64-bit clients; and server-sizing data. Strategically planning your infrastructure can help you avoid problems before they begin, allowing you to serve your customers more accurately and reliably, as well as saving you time and money. more > http://blogs.technet.com/appv/archive/2010/02/24/infrastructure-planning-and-design-guide-for-microsoft-app-v-4-6-now-available.aspx

I've been testing scanstate in Offline mode while in Windows PE in the last few days for Windows XP to Windows 7 migrations and it's impressive and fast, so I thought this would be a good way of showing you how the process works using some screenshots and links to info. First of all we start with a Windows XP desktop, nothing fancy, I’ve just dumped 2.5GB of data onto the desktop for the Demo. All of this data will migrate via scanstate in offline MODE while in Windows PE. So let’s get started with that and reboot into PXE to start the process. I’m doing this in a hyperV environment which is great for testing and I highly recommend you have a virtual environment for testing/demoing. As the screenshot says press F12 for network service boot. The reason we are seeing this is because I have advertised Optional Task Sequences to my Migrate Windows XP to Windows 7 X86 collection. Having the task sequences optional instead of Mandatory means you get to choose which one you want from a list (provided that there are more than one Task Sequence). Once the Task Sequence wizard starts we can be prompted for a password, in this example we have none set so we can just click Next. If you want to set a PXE Service Point password then read this post. And then we see our list of task sequences, in this particular example only two optional task sequences are advertised to this collection, so that’s all we see. Select the appropriate one and click next. The task sequence starts and the appropriate variables are set, then folders are created and finally packages and files are xcopy’d into place. Once everything is in place, we kick off scanstate in Offline mode by initiating the scanstate batch file which all takes place in the do X86 Scanstate step. When scanstate is done hardlinking in OFFLINE mode in Windows PE, the task sequence downloads the windows 7 WIM which we captured before. Then the drive is wiped which deletes all of Windows XP but leaves our migrated and hardlinked data in c:\usmtoffline along with logs files and the captured Windows 7 wim... Windows 7 wim gets applied And then windows Reboots After the reboot we see the Windows 7 boot screen Windows setup starts installing devices etc… Installs the configmgr client...and Reboots again and then Restores all the migrated data (this bit requires that you set the following variable, otherwise it will fail with USMT error 38) OSDMigrateAdditionalRestoreOptions=/Hardlink /nocompress And finally we see the Windows 7 login screen. We login as the same Domain user that we migrated, (testuser) And that’s it, the data is all migrated using Offline mode while in Windows PE. Cool huh ? If you want to download the Task Sequences used above, click here.

i think you guys are having the same problem as this http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/70b3f6e4-6629-4e88-bc11-33b69fa2516b/#ceddfba7-87fb-48da-80d9-38d07f32dd00 and I quote:

if you want to rename the computer without using MDT try the suggestion here

App-V 4.6 is now available: http://blogs.technet.com/appv/archive/2010/02/22/app-v-4-6-is-now-available-plus-some-new-resource-kit-tools.aspx

Migrate XP to Windows 7 using Offline mode in Windows PE Once you have the above working you'll want to actually Migrate XP to Windows 7 using Offline Mode in Windows PE. Ok now you know it works, use the above theory and task sequence within a working Migrate XP to Windows 7 Task sequence. Here's how, Import the following task sequence XP to W7 Demo - X86 Offline Mode in WinPE-USMT 4.xml Once imported resolve the package requirements namely * X86 boot image * USMT 4 X86 package *special usmt 4 package containing only the x86 folder) * Operating System image (captured Windows 7 image if you don't have one yet read this) * ConfigMgr client package from definition * USMT 4 (both) package containing the native x86 and x64 folders for USMT 4... * runscanstate.bat package from above the key bits in the TS are set hard-link load parameters and the rest is the same as above I'll post some more screenshots soon but here's two to get you excited XP desktop before migration Windows 7 desktop after migration If you are having problems understanding the USMT4 packages used in this workaroun/proof of concept then please read all of this post Related reading: How to use USMT 4 hardlinking in a Configuration Manager 2007 Task Sequence http://blogs.technet.com/b/configurationmgr/archive/2010/06/30/how-to-use-usmt-4-hardlinking-in-a-configuration-manager-2007-task-sequence.aspx How can I use Offline Mode in Windows PE using USMT 4 Using a scanstate (using offlinewindir in winpe ) Task Sequence in SCCM 2007 SP2 Some Sample XP to Windows 7 task sequences showing Hardlinking hardlinking and SMP Customise the XML files http://technet.microsoft.com/en-us/library/dd560786%28WS.10%29.aspx What does USMT 4 migrate ? http://technet.microsoft.com/en-us/library/ff383238(WS.10).aspx have fun ! cheers niall

why are you trying to import a winpe image ? and to import the nic drivers you need the windows 7 network drivers for the notebook in question, once you have them, select your boot image in the OSD node of configmgr, click on drivers and add the driver there, distribute it to a dp, once done, import that driver into your boot image by right clicking on the boot image, choose the windows PE tab, select the driver cheers niall

Create New Collection right click on Collections in the SCCM Configuration Manager console, choose New Collection. when the New Collection wizard appears, give the collection a name like All Windows Vista Systems fill in the comments and click Next, In the membership rules page, click on the New Query Statement icon, in the Query Rule Properties, give the rule a name eg: All Windows Vista systems then click on Edit Query Statement In the General tab, click on Show Query Language and paste in the code we copied from above. Change the value at the end of the query from 5.0 to 6.0 and click Ok, then Ok, then next, next, next and close. original query below select sms_r_system.ResourceID,sms_r_system.ResourceType,sms_r_system.Name,sms_r_system .SMSUniqueIdentifier,sms_r_system.ResourceDomainORWorkgroup,sms_r_system.Client from sms_r_system where OperatingSystemNameandVersion like '%Workstation 5.0%' change to this select sms_r_system.ResourceID,sms_r_system.ResourceType,sms_r_system.Name,sms_r_system .SMSUniqueIdentifier,sms_r_system.ResourceDomainORWorkgroup,sms_r_system.Client from sms_r_system where OperatingSystemNameandVersion like '%Workstation 6.0%' that's it, you now have a new collection called All Windows Vista Systems now that you are done and you know how to make the collection, you can also create one for All Windows Server 2008 systems here's the query for you select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM .SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from sms_r_system where OperatingSystemNameandVersion like '%Server 6.0%' Here's Microsofts Technet page on making Collections.

Using the same steps as done in the Create New Collection as outlined here we will:- Create a New Collection and call it All 64 bit Systems, for Membership rules Click on the Yellow cylinder (to create a New Query), Create a New Query, call it All 64 bit systems query, click on Edit Query Statement then Criteria, Show Query Language, replace the text that reads:- Select * from SMS_R_System by pasting the following in for the query select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_PROCESSOR on SMS_G_System_PROCESSOR.ResourceID = SMS_R_System.ResourceId where SMS_G_System_PROCESSOR.AddressWidth = 64 done !

select Microsoft as the manufacturer, do you see it then ? if not post a screenshot of what you see

did you see this post ? http://www.windows-noob.com/forums/index.php?/topic/1660-customising-windows-7-deployments-part-1/

can you please give me a download link for this software and i'll take a look, unfortunately i don't have a HP laptop but i'd still like to take a look

download and install the right-click tools, they can give you that ability and a lot more

what does the 3d drive guard software do and what problem are you having with it exactly ?

on one of the clients that's reporting as client=no if you do a data discovery cycle manually do you see a change ?

hi all, Note: This post has been reproduced in a webcast, so if you'd like to see a video of Offline Mode in WinPE then click here well this feature in USMT 4 is handy, as it allows you to do a scanstate while in Windows PE in other words, not in the OS so no problems with services running or applications running meaning that you get to backup everything you want without any locked files stopping from doing so. Offline mode does however have some restrictions, read this page on Technet for details of that. To get around these restrictions and to migrate wallpaper see here, to migrate your network printers see here. Great, but how do I do Offline Mode in Windows PE using SCCM ? according to Microsoft, we can use the /offlinewindir switch in USMT 4 with scanstate. However, implementing it isn't so straigtforward as you've probably already discovered and documentation about getting it to work within SCCM is as far as I can see pretty much non-existant, so here courtesy of windows-noob.com is one way of doing it, feel free to show us other ways. The theory behind this:- As the Capture User State Step in a standard task sequence can only run in Windows, we cannot use that step to do our scanstate while in Windows PE, therefore we will use some tricks to run scanstate from WinPE. To do this we create two special packages, the first package contains a batch file which calls the scanstate.exe file and the second package is the entire USMT X86 scanstate files and folders, (note: in this example we are using scanstate from the X86 folder). This means that we create a separate package to the normal USMT4 package and this is only because this example is a workaround or proof of concept to prove that Offline Mode in Windows PE can be done via a Task Sequence in SCCM. Update: If you would like sample code to check for and use the correct USMT architecture in offline mode then see Peters post here Get your lab ready We need a Windows XP client machine to test scanstate on and you should enable the F8 command prompt option in your boot.wim (you'll need it). The Task Sequence You can use this Task Sequence in SCCM by importing it. Please note this task sequence only has the 4 groups in it, if you want the 4 groups plus OSD then use the other Task Sequence further down. Offline Mode in Windows PE using USMT 4.xml The task sequence depends on three packages, the X86 bits from your USMT 4 (ie: copy everything in the X86 folder from C:\Program Files\Windows AIK\Tools\USMT folder. There are two versions, one for 32bit (X86) and one for 64bit (amd64), we are only using the X86 bits in this guide), the Batchfile I break up my task sequence into four distinct groups, Set, Create, xcopy and Run SET In the Set group I set SystemDrive to c: (otherwise it will try and do this on the windows PE x: drive) Next we set the OSDStateStorePath Task Sequence Variable to %systemdrive%\USMToffline which translates to c:\USMToffline, this directory will store our migration data during scanstate operations and when the new os is being applied. Finally we set the hardlink load parameters CREATE In the Create group we just create two folders, c:\USMToffline, and c:\USMTbits\X86 the c:\USMTbits\X86 will store all our scanstate native files. XCOPY In the xcopy group we do the clever stuff, we copy the X86 USMT stuff to the newly created folder, and then we copy our batch file for later user. The batch file itself has the following contents @set USMT_WORKING_DIR=%~2%\USMTbits\x86 "%~2\USMTbits\x86\scanstate.exe" "%~1" /c /o /hardlink /efs:hardlink /nocompress /offlinewindir:c:\windows /v:5 /l:%~2\windows\TEMP\SMSTSLog\scanstate.log /progress:%~2\windows\TEMP\SMSTSLog\scanstateprogress.log /i:%~2\USMTbits\x86\miguser.xml /i:%~2\USMTbits\x86\migapp.xml You can download the batchfile below however you must rename it back to .bat runscanstate-offlinewindir.bat.txt RUN The Run group does the actual running of the batch file and passes two variables to the file. Testing Offline Mode. Create an optional advertisement to a Migrate XP to W7 X86 collection for the Task Sequence and PXE boot your XP client (press F12 first....), select the Task Sequence when the wizard appears, at this point press F8 to bring up the command prompt, you are doing this to verify that your data is getting migrated in OFFLINE mode. So here we can see the command prompt is open. Ok switch back to the TS and start the task sequence. You will see it starts creating the folders, copying the USMT stuff and our batch file(s) and then actually running the scanstate command. Once it is completed your migrated data will now be stored in C:\USMToffline\USMT browse it and verify If you want to see a working SMSTS.log file from the above test see below smsts.log Ok now what ?

well if it's enterprise are you using a KMS server or MAK keys or what ? take a look at this resource while you are checking: it has videos explaining activation: * Fundamentals of volume activation * Activating Windows ® 7 with MAK * Activating Windows ® 7 with KMS * Understanding activation and validation in Windows ® 7 and Windows Server 2008 R2 http://technet.microsoft.com/en-us/library/dd996588.aspx

what version of Windows 7 are you deploying ?

standard is fine unless you want to cluster it in which case you should consider enterprise, there is a very big difference in licensing cost between standard and enterprise... use SQL 2008 sp1

When deploying Windows Server 2008 or Windows Server 2008 R2 on a server that contains disks that are not local (such as SAN or SAS disks) using an SCCM 2007 OSD Task Sequence, when the Task Sequence completes the additional disks may not come online and may show as offline. http://blogs.technet.com/configurationmgr/archive/2010/02/17/when-deploying-windows-server-2008-using-an-sccm-2007-osd-task-sequence-additional-disks-may-show-as-offline-when-the-task-sequence-completes.aspx J.C. Hornbeck | Microsoft http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/7e06ee89-df1f-4db4-a164-b1ae0679956c