SCCM 2012 R2 - best image capturing method?
I'm told that it's not a good practice to build a VM with Windows 7 and Office 2013 from scratch, join domain and install WSUS updates, then leave domain and use the Capture Media .iso to capture the image.
I'm not sure what way to go...
I have a Hyper V virtual machine setup. Should I "Build and Capture" PXE boot to it? I have driver issues with this in that I have to not use a drive package but have Apply Drivers step instead otherwise nothing ever finishes.
I'm not sure what way to go...
I have a Hyper V virtual machine setup. Should I "Build and Capture" PXE boot to it? I have driver issues with this in that I have to not use a drive package but have Apply Drivers step instead otherwise nothing ever finishes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi - you need to enable F8 on your boot WIM. Go to the properties and tick the box "Enable for debugging". Then you can use cmtrace to look at the logs.
ASKER
Are you referring to “Enable command support (testing only)”?
If so, that is already enabled.
Also am I really in the Boot image when the Task Sequence is installing an application?
If so, that is already enabled.
Also am I really in the Boot image when the Task Sequence is installing an application?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I built the image and then ran the capture media program from the ISO I put on USB. It captured the image and I copied the OS to SCCM share to use for deployment.
Now when I try PXE booting and running the task sequence, it runs and applies the OS but when it gets into the Setting up Windows screen, I get the error:
windows could not parse or process the unattend specialize
I'm not sure why that is. The capture image process ran its own Sysprep.
My "Apply Windows Settings" task sequence step has a simple Username, orgarnization and the KMS product key put in for Windows 7.
Now when I try PXE booting and running the task sequence, it runs and applies the OS but when it gets into the Setting up Windows screen, I get the error:
windows could not parse or process the unattend specialize
I'm not sure why that is. The capture image process ran its own Sysprep.
My "Apply Windows Settings" task sequence step has a simple Username, orgarnization and the KMS product key put in for Windows 7.
ASKER
I don't think the issue is the .wim file.
I was able to use ImageX from a WinPE USB bootable device and apply the .wim and it applied fine, with no errors.
So thinking it's something with the task sequence? I'll try removing the product key from it.
I was able to use ImageX from a WinPE USB bootable device and apply the .wim and it applied fine, with no errors.
So thinking it's something with the task sequence? I'll try removing the product key from it.
ASKER
In SCCM 2012 I removed the Product Key from the Apply Windows Settings, and that appears to have fixed the error I was getting.
What's strange is that it worked fine when I was deploying the raw install.wim file from the Win7Pro iso file. But hey, I guess it's working fine now!!
What's strange is that it worked fine when I was deploying the raw install.wim file from the Win7Pro iso file. But hey, I guess it's working fine now!!
Good to hear. That step also allows you to provide a full Custom unattend.xml with the key in if you want. I rarely, if ever edit that.
ASKER
However after the screen of running command line setup.exe finishes, it disappears and I'm left staring at a wallpaper (the task sequence wallpaper background), as if the task sequence has stopped.
It has been sitting at that screen for like 40 mins.
The supposed next steps after that are supposed to be is Restart Computer and then Install Updates.
It's a bit annoying that I have no way of knowing what's going on. F8 won't bring up a command prompt. Ctrl+Alt+Del does nothing.