birz

Here's my scenario: build&capture task sequence for Windows then I add the created image as an "Operating system image" I choose "Schedule updates" and select all of them. it installs fine, then the DP are getting update iwth the image containing all the updates So far everything work as expected, when deploying the image it has all the updates already installed. My problem now: If I need to re-run the "build&capture" TS for some reason, let's say I want to add a software to it. Once done I update my DP with the newly captured image. I assume that I would need to re-schedule the offline servicing portion, but when I try to add the update it says that no updates are available for installation. If I look at the image property "update status" it says that all the updates are installed, which isn't tru, the image has just been re-done. So far my only work around is to delete the "operating system image" from the SCCM console and create a new one and do the process offline servicing again. I have to open up all my TS that needs that image to corect them with the new one. It's not really efficient and it is time consuming. Is there a way to avoid this? Am I doing something wrong? Thanks,

Really? no one knows

http://www.windows-noob.com/forums/index.php?/topic/7723-sccm-2012-sp1-mdt-2012-upd-1-windows-7-x64-sp1/ see my last post. I know you don't use the MDT integration, but it might help anyway.

I finally got it to work In my initial TS to build the reference image I removed the BDE partition creation and put a checkmark on "make this the boot partition" so now it only creates 1 partition for the "C" drive. On my deploy TS I leave the BDE partition creation step, but I change the value of "OSDPreserveDriveLetter" to "TRUE" it works fine for Windows 7 and Windwos 8 deployment. I'm happy now Thanks everyone.

Hi, I have tried to find an swer to the following question to no avail. When you configurethe DP rate limit tab, section: "limites to specified maximum transfer rates by hour" does the time is the one from the DP? site server? UTC? We have offices that span on 3 time zones so I want to set it up properly. This question can go for the tab "schedule" too. Anyone? Thanks in advance.

I don't know how you missed it, but my title clearly states that is is an MDT task sequence (SCCM 2012 SP1+ MDT 2012 upd 1) maybe we both need glasses

I have looked and couldn't find anything. Can you please tell me "which" guide? Thanks,

Hi, Can anyone tell me the right process to build&capture a Windows 7 x64 SP1 image and then create another client TS to deploy it to the "C" drive letter???? here is what I use and do: I have the MDT 2012 upd1 integration active in my console I use Hyper-V to create the Reference image I have created a MDT client task sequence I use the Install.wim from the Windows 7 x64 SP1 ISO to build the Reference image in the TS. I added a step to set the task sequence variable "DoCapture" to "Yes" just before the capture image step. I modified the "format and partition disk 6.1" step to remove the creation of the BDEDrive, and only Everything works fine, the image is successfully captured. even when I log in to the reference image after the capture process is finiched I see the "C" drive labeled as "OSDisk" and no other drive. Which is perfect On my other Task sequence used to deploy the reference image. I let all the format and partition steps the way they are automatically created with the MDT TS. Everything works fine except the "OSDisk" ends up being on the "D" or "E" drive depending the bootmedia used. I have tried to play with the TS variable "OSDPreserveDriveLetter'" True or False to no avail. Any guideline or help would be appreciated.

Hi, On my TS reports I always see that there's a some computers running some TS, in reality they aren't. It's really an outdated info, couple months old. Although it doesn't affect productivity and it's more an aesthetic issue, it really bugs me. How can I clean the info so the report won't show this? I have looked on the client in the SMS reigtry hive, but nothing is in the TS registry entry. I have attached a picture of what I see. I'm highliting ony one thing but I suspect there are other erroneous info showing in the report. Thanks in adance.

OK I've answered my own question, the statestore is moved to "C:\Windows\Temp"

You have to be aware that you need to change a line in the ZTIUserstate.wsf script in the MDT package, if you don't your USMT will be screwed from XP to Win7, it won't locate the manifest files. Look for that section in the file: ' Workaround for USMT bug in Windows 7 AIK If oEnvironment.Item("DeploymentMethod") = "SCCM" and oEnvironment.Item("OSVersion") = "XP" and oFSO.GetFileVersion(sFoundScanState) = "6.1.7600.16385" then oUtility.RunWithHeartbeat "cmd.exe /c xcopy /iesryh """ & sUSMTPath &"\DlManifests"" """ & oEnv("SystemRoot") & "\system32\DlManifests" &""" 1>> " & oLogging.LogPath &"\zticopyUSMT.txt 2>>&1 " End if and make sure you change the file version to this: 6.1.7601.21645 Microsoft teams don't talk to each other it seems.

OK thanks for the answers, although I dn't really understande the purpose of the "local" backup,,, when Windows 7 is being installed, the backup is gone as well. Maybe it is hidden, but it is definately not in the statestore folder after the refresh is done. What I see is that the backup is gone in the process, so I think it's a waste of time. Correct me if I'm wrong though.

Hi, I'm in the process of doing a "refresh TS" to migrate "Windows XP x86" to "Windows 7 x64" and there's a thing that I can't seem to get to work here it is: I want to for the "backup" to go on a network share instead of the wim file file being saved in "C:\_SMSTaskSequence\StateStore". I've tried setting up the following variable in both the customsettings.ini and directly in the TS as "set task sequence variable", either solutions didn't work out.. computerBackuplocation=Network backupdir=%computername% backupshare=\\somenetworkshare\xxx here is what I find in the ZTIBackuplog: Microsoft Deployment Toolkit version: 5.1.1642.01 ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Drive C: 32277992 ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Local store path = C:\_SMSTaskSequence\StateStore ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Total used space: 32277992 ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Available space at C:\_SMSTaskSequence\StateStore: 211918008 ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Backup can use local path ztibackup 08/04/2011 2:21:48 PM 0 (0x0000)Property USMTLocal is now = True ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Using a local or mapped drive, no connection is required. ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) Beginning backup of drive C: ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) About to run command: cmd /c ""C:\_SMSTaskSequence\WDPackage\Tools\X64\imagex.exe" /capture /compress maximum C: "C:\_SMSTaskSequence\StateStore\MTL7CAC03000QD.wim" "201104081421CDrive" >> X:\windows\TEMP\SMSTSLog\ZTIBackup_imagex.log 2>&1" ztibackup 08/04/2011 2:21:48 PM 0 (0x0000) ZTI Heartbeat: command has been running for 6 minutes (process ID 1576) ztibackup 08/04/2011 2:27:00 PM 0 (0x0000) ZTI Heartbeat: command has been running for 12 minutes (process ID 1576) ztibackup 08/04/2011 2:33:00 PM 0 (0x0000) ZTI Heartbeat: command has been running for 18 minutes (process ID 1576) ztibackup 08/04/2011 2:39:00 PM 0 (0x0000) Return code from command = 0 ztibackup 08/04/2011 2:44:22 PM 0 (0x0000) Successfully created image of drive C: ztibackup 08/04/2011 2:44:22 PM 0 (0x0000) Skipping drive X: because it's not C: ztibackup 08/04/2011 2:44:22 PM 0 (0x0000) ztibackup COMPLETED. Return Value = 0 ztibackup 08/04/2011 2:44:22 PM 0 (0x0000) Property BackupScriptComplete is now = YES ztibackup 08/04/2011 2:44:22 PM 0 (0x0000) ztibackup processing completed successfully. ztibackup 08/04/2011 2:44:22 PM 0 (0x0000)

I'm in the same boat as you. I'm on W2K8R2 (hence x64) and SCCM 2007 R2 SP2, there a re no download forthat platform. Weird...

I'm finding similar issues: here but the solutions don't seem to work in my environment, I find this really odd from SCCM. It's quite basic and should work as advertised....