anyweb

and here's yet another post about how to do it (hardlinking etc) http://myitforum.com/cs2/blogs/nbrady/archive/2010/01/26/migrating-windows-xp-to-windows-7-using-hardlinking-setting-up-a-demo.aspx

hmm what DVD did you pull the boot image from ?

please provide DETAILS of your problem, there's a capture windows 7 guide here, did you try it ? did you see if adobe whatever (because you never told us) is in add remove programs after the capture ? can you give us some actual details of the actual problem ?

System Center recognizes that technology has evolved since you first deployed your SMS 2003 environment. New platforms have become available, you are supporting new working styles, and security is more important than ever. We want you to benefit from the latest platforms and security features available, and to achieve this we want to help you migrate to our latest management platform. http://www.microsoft.com/systemcenter/configurationmanager/en/us/sms.aspx Can you spot Wally in the video ?

please stop raising new topics for the same problem, we need more details about what you've done, and how you are doing it. is this still the same problem as before, adobe software not appearing after the capture ? cheers niall

does the software show up in add/remove programs

of course it's possible, did you see this post ? http://www.windows-noob.com/forums/index.php?/topic/1543-how-can-i-capture-windows-7/

A 17-year-old bug in Windows will be patched by Microsoft in its latest security update. The February update for Windows will close the loophole that dates from the time of the DOS operating system. First appearing in Windows NT 3.1, the vulnerability has been carried over into almost every version of Windows that has appeared since. The monthly security update will also tackle a further 25 holes in Windows, five of which are rated as "critical". Home hijack The ancient bug was discovered by Google security researcher Tavis Ormandy in January 2010 and involves a utility that allows newer versions of Windows to run very old programs. Mr Ormandy has found a way to exploit this utility in Windows XP, Windows Server 2003 and 2008 as well as Windows Vista and Windows 7. The patch for this vulnerability will appear in the February security update. Five of the vulnerabilities being patched at the same time allow attackers to effectively hijack a Windows PC and run their own programs on it. more > http://news.bbc.co.uk/2/hi/technology/8499859.stm

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..

glad you sorted it and thanks for posting the resolution

via > Nexus SC: The System Center Team Blog Hi everyone, recently we recorded a look into the new scale and performance improvements we will ship in ConfigMgr 2007 R3. There are 3 main areas of enhancement being made to the core capabilities of ConfigMgr. These are as follows: Delta Active directory Discovery – AD discovery has 2 main tasks. Discovering changes to users or machines that may effect targeting. Also, periodic full scans capture users and machines last logged time, ensuring active users or systems are not made obsolete. The AD queries that this is supported on include User, User Group, System and System Group. Fast Collections – Combined with Delta AD Discovery is a concept called ‘Fast Collections’. When a Collection Membership Rule is configured to dynamically add new resources, a few things happen. This applies to a few resources. Those that are initially discovered, OSD provisioned systems, HW inventories scanned systems, or ConfgMgr Client version upgrades. When Fast Collections are configured, a Resource ID is inserted into the change tracking table where a separate collection evaluator thread is run (5min) and evaluates collections marked for fast evaluation. This setting does not apply to known machines , and full evaluations are still processed the same way. The result is significant gains of time savings to get advertisements to users and systems. Admin Console Improvements – There have also been some improvements to the Admin console, helping the Administrator save time in their daily tasks. For example, new right click options off a resource to add to collection (existing) add to new collection, remove from collection and add resources, are all designed to save console steps. Here is a short video demonstrating these improvements. http://blogs.technet.com/systemcenter/archive/2010/02/04/scale-and-performance-improvements-in-configuration-manager-2007-r3.aspx

here's the solution http://www.windows-noob.com/forums/index.php?/topic/1672-solution-status-0xc0000001-when-deploying-windows-7/

When deploying Windows 7 via OSD in SCCM 2007 SP2, upon rebooting from the WinPE stage to Windows 7 Mini-Setup, Windows may not start and the following error occurs instead: Status: 0xc0000001 Info: An unexpected error has occurred. Examining the following logs may reveal the following errors: SMSTS.log PkgMgr.log This issue can occur if you are attempting to use a WinPE 2.x based Boot Image created with the WAIK 1.x for a Windows 7 deployment. Windows 7 deployments require a WinPE 3.0 or newer based Boot Image created with the WAIK 2.x or newer. Examining the logs reveals that the deployment is trying to use Pkgmgr.exe (Package Manager), which is a WinPE 2.x/WAIK 1.x tool, to try to inject drivers into Windows 7. PkgMgr.exe is not compatible with Windows 7 and it has been replaced with DISM.exe in WinPE 3.x/WAIK 2.x. DISM.exe is required to inject drivers properly into Windows 7. Using the incorrect Boot Image causes the deployment to try to use a combination of PkgMgr.exe and DISM.exe, and ends up causing it to fail. Resolution Check to make sure that the Task Sequence deploying Windows 7 is using a WinPE 3.x based Boot Image. To check the Boot Image that the Task Sequence deploying Windows 7 is using: 1. In the ConfigMgr 2007 console under the "Operating System Deployment" --> "Task Sequences" node, right click on the affected Task Sequence and choose "Properties". 2. Click on the "Advanced" tab 3. Under the option "Use a boot image:", make sure that the Boot Image selected is a WinPE 3.x based Boot Image To check the version of the Boot Image to verify that it is a WinPE 3.x Boot Image: 1. In the ConfigMgr 2007 console under the "Operating System Deployment" --> "Boot Images" node, right click on the Boot Image as determine in the above steps and choose "Properties". 2. Click on the "Images" tab. 3. Click on the "Reload" button. 4. Check the value of the field "OS version". For WinPE 3.x based Boot Images, the version number should at least be at 6.1.7600.16385. If the version number is 6.0.6001.18000 or older, this is a WinPE 2.x based Boot Image which will not work with Windows 7 deployments. Frank Rojas | Configuration Manager Support Escalation Engineer

verify that the key can be used with the actual iso you are using, ie: verify they match up regardless of it actually activating after the install

leave out the key or get a version of the ISO that will work with the key you are trying to use, are you using KMS ?

good info, was it SEP 11 ?

did you try restarting the dhcp and wds services ?

read this post and use the same method, ie: make your desired changes in unattend.xml using Windows SIM cheers niall

did you see this post ? My link

are you lucky enough to go to MMS 2010, vote ! and tell us about it

Consider the following scenario: * You install the System Center Configuration Manager 2007 Service Pack 1 (SP1) client or the System Center Configuration Manager 2007 Service Pack 2 (SP2) client. * You install security update 974571 on this computer. * A SCCM task sequence runs on this client. This task sequence includes the Capture User State task sequence step and the Restore User State task sequence step. In this scenario, user state migration fails. At the same time, the following error message is logged in the Ccmexec.log file: This issue occurs because an embedded NULL character is in the Friendly name property of a certificate. The security update 974571 prevents the action that imports the certificate when its Friendly name property has an embedded NULL character. Therefore, the certificate cannot be imported. For all the details including a download link to the hotfix see the following new Knowledge Base article: KB977203- User state migration fails on a SCCM 2007 SP1 client or on a SCCM 2007 SP2 client after you install security update 974571 J.C. Hornbeck | System Center Knowledge Engineer

not that i am aware of nope cheers niall

you need sccm 2007 sp2 to properly support Windows 7, as regards the client installing and uninstalling how are you pushing the client out ? can you please include the ccmsetup logs from a client with the problem ? is the firewall disabled (for testing) on the XP client ?

hold on a minute, are these workstations scsi or sata ? if sata then check the bios settings for AHCI or whatever it's called today, try changing it to compatible, or failing that tell me how you built the original image, and what options in the bios for hdd you have on the workstation

do you have 512mb of ram or more in that vm ?