Comments on: A Tale of Build Numbers and Deployment http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/ Tales from the Datacenter Wed, 01 Sep 2010 16:36:52 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-863 Stefan Wed, 01 Sep 2010 16:36:52 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-863 addendum zu previous post: after installing the network drivers manually via USB stick, I logged off and on again as ADMINISTRATOR and the deployment wizard continued where halted. Nice! addendum zu previous post:

after installing the network drivers manually via USB stick, I logged off and on again as ADMINISTRATOR and the deployment wizard continued where halted. Nice!

]]> By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-862 Stefan Wed, 01 Sep 2010 16:01:18 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-862 update: I followed the youtube tutorial of MS-tech specialist Jay Paloma and came to the problem in this thread. I NOW got it running and want to say that >>> it is NOT dependant on the Build numbers !!! <<< The problem with "SETUP NOT FOUND" came from the steps in MDT, while importing the WIM into MDT. -In MDT: you go left pane to OPERATING SYSTEMS. -Right mouseclick "IMPORT". -Next you are asked what OS TYPE to import. -You select CUSTOM IMAGE FILE and select your WIM you have captured. -on NEXT you come to the crucial point that was wrong described. You select the second entry "Copy Windows Vista, Win server 2003 or later setup files from specific path" -You select the earlier imported original Windows-installation-CD as Source for the SETUP files. (should be no WIM but all files in a subfolder) NOW, your captured custom WIM is beeing imported in MDT and the Setup files are added from the original installation medium. It was no problem for me. (well exept missing network drivers on one desktop PC, so the BDD-autorun Script refused to continue under Win7) Hope this helped. update:
I followed the youtube tutorial of MS-tech specialist Jay Paloma and came to the problem in this thread.
I NOW got it running and want to say that
>>> it is NOT dependant on the Build numbers !!! <<<

The problem with "SETUP NOT FOUND" came from the steps in MDT, while importing the WIM into MDT.

-In MDT: you go left pane to OPERATING SYSTEMS.
-Right mouseclick "IMPORT".
-Next you are asked what OS TYPE to import.
-You select CUSTOM IMAGE FILE and select your WIM
you have captured.
-on NEXT you come to the crucial point that was wrong described. You select the second entry "Copy Windows Vista, Win server 2003 or later setup files from specific path"
-You select the earlier imported original Windows-installation-CD as Source for the SETUP files. (should be no WIM but all files in a subfolder)

NOW, your captured custom WIM is beeing imported in MDT and the Setup files are added from the original installation medium.

It was no problem for me.
(well exept missing network drivers on one desktop PC, so the BDD-autorun Script refused to continue under Win7)

Hope this helped.

]]> By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-859 Stefan Wed, 18 Aug 2010 14:52:04 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-859 update: after UPGRADE sysprep could not be started in an upgraded environment. So I have to install from scratch. d*mn update:

after UPGRADE sysprep could not be started in an upgraded environment.
So I have to install from scratch. d*mn

]]> By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-858 Stefan Wed, 18 Aug 2010 14:17:17 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-858 update: I run Win7 on the different version number (7600.16539) I ran the setup under the system and chose "Upgrade" The Version number is now restored to it's source version (7600.16385) I keep you posted if deployment works now. update:
I run Win7 on the different version number (7600.16539)
I ran the setup under the system and chose “Upgrade”
The Version number is now restored to it’s source version (7600.16385)
I keep you posted if deployment works now.

]]> By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-857 Stefan Wed, 18 Aug 2010 12:09:09 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-857 is there a "dirty" way to change the build/lab number in Win7 so the installer thinks it's the old version? I already tried to alter the registry but it jumps back after rebooting. is there a “dirty” way to change the build/lab number in Win7 so the installer thinks it’s the old version?
I already tried to alter the registry but it jumps back after rebooting.

]]> By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-856 Stefan Wed, 18 Aug 2010 10:22:31 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-856 strangely there is no KB977165 installation in the installed software overview :-/ strangely there is no KB977165 installation in the installed software overview :-/

]]> By: Stefan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-855 Stefan Wed, 18 Aug 2010 09:29:38 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-855 imho you can include the patch via MDT. The base WIM is not beeing affected. The patch will be included after installation. imho you can include the patch via MDT. The base WIM is not beeing affected.
The patch will be included after installation.

]]> By: Patrick http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-834 Patrick Wed, 02 Jun 2010 01:46:43 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-834 Not that I know of. I think we're going to have to wait for a service pack so Microsoft will update the DVD and the source wims. Not that I know of. I think we’re going to have to wait for a service pack so Microsoft will update the DVD and the source wims.

]]> By: Mark http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-833 Mark Tue, 01 Jun 2010 23:53:05 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-833 I just came across the same problem with the build numbers not matching and getting the error "unable to find setup". Is there a way to include the updated source files in MDT so I don't have to worry about excluding MS10-015 before capturing? Thanks, Mark I just came across the same problem with the build numbers not matching and getting the error “unable to find setup”. Is there a way to include the updated source files in MDT so I don’t have to worry about excluding MS10-015 before capturing?
Thanks, Mark

]]> By: Dan http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/comment-page-1/#comment-832 Dan Wed, 14 Apr 2010 19:41:50 +0000 http://www.pburch.com/blog/2010/03/05/a-tale-of-build-numbers-and-deployment/#comment-832 Just an FYI, people who use fat images, and pre-install windows updates to the wim will be unable to deploy an image that has been captured after installing MS10-015 - KB977165. This update modifies the kernel version number, and ZTI will fail saying it can not find setup files for deployment. More information on MS10-015 - KB977165: http://support.microsoft.com/kb/977165/ I would say its best to install this update after deployment if this is the route you go. -Dan Just an FYI, people who use fat images, and pre-install windows updates to the wim will be unable to deploy an image that has been captured after installing MS10-015 – KB977165. This update modifies the kernel version number, and ZTI will fail saying it can not find setup files for deployment.

More information on MS10-015 – KB977165:

http://support.microsoft.com/kb/977165/

I would say its best to install this update after deployment if this is the route you go.

-Dan

]]>