We have been using MDT2008 for the last 2 years to create our copr images and didn't had any issue, our process was the following
-Create a new Operating System from the source files of Windows XP SP3
-Created standard task sequence with the new OS
-Created applications
Then we booted from our litetouch and selected out TS and applications.....then sysprep kicks in and reboot then capture the image.
The we created a new OS from the new wim then new ts, image get install then reboot goes to sysprep and once on the desktop runs the scripts and finally we got the "Succesfully Completed".
Now, we have upgraded our MDT Server to MDT2010 Update 1 and did the following
-Created new OS from the source files of XP SP3
-Created ts for build and capture, we selected our Windows XP SP3 as the OS.
The we booted form the Windows XP SP3 CD and did our installation, customization, ect... once finish we did a map network drive to our mdt server and launched the litetouch.vbs, we selected our "build and capture for XP" task sequence, gave the wim a name and finally click on finish, first issue that we had was an error about the CloneTag registry key that could not be found (we fixed this issue), then sysprep started then it rebooted and did the capture with no error.
Once again we created a new OS and new TS, then we booted from litetouch selected the new TS, entered the domain information, account....., the image got install and then rebooted, this time it didn't got to sysprep and went almost straight to the crtl-alt-del login window, i login in as administrator and noticed that the sysprep folder was in the c:, obviously the pc was not on the domain and no script ran.
Doing the same process for Windows 7 works fine so my question is, is the build and capture not compatible for creating Windows SP Images?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
We have been using MDT2008 for the last 2 years to create our copr images and didn't had any issue, our process was the following
-Create a new Operating System from the source files of Windows XP SP3
-Created standard task sequence with the new OS
-Created applications
Then we booted from our litetouch and selected out TS and applications.....then sysprep kicks in and reboot then capture the image.
The we created a new OS from the new wim then new ts, image get install then reboot goes to sysprep and once on the desktop runs the scripts and finally we got the "Succesfully Completed".
Now, we have upgraded our MDT Server to MDT2010 Update 1 and did the following
-Created new OS from the source files of XP SP3
-Created ts for build and capture, we selected our Windows XP SP3 as the OS.
The we booted form the Windows XP SP3 CD and did our installation, customization, ect... once finish we did a map network drive to our mdt server and launched the litetouch.vbs, we selected our "build and capture for XP" task sequence, gave the wim a name and finally click on finish, first issue that we had was an error about the CloneTag registry key that could not be found (we fixed this issue), then sysprep started then it rebooted and did the capture with no error.
Once again we created a new OS and new TS, then we booted from litetouch selected the new TS, entered the domain information, account....., the image got install and then rebooted, this time it didn't got to sysprep and went almost straight to the crtl-alt-del login window, i login in as administrator and noticed that the sysprep folder was in the c:, obviously the pc was not on the domain and no script ran.
Doing the same process for Windows 7 works fine so my question is, is the build and capture not compatible for creating Windows SP Images?
Thanks
Share this post
Link to post
Share on other sites