SCCM 2012 R2 - Build and Capture Image issue

[mdrabble]

Ok, so Ive just setup SCCM and all going well, imported some previously captured images from my MDT box and I can deploy those no problem.

 

I've extracted and copied both 32/64bit Windows 7 to a share on my SCCM box (same share used by the othe images)

 

Ive added them as OS Installers and distributed them to the distribution point and they are showing green.

 

I go to create a new Task and select Build and Capture a Reference OS Image, select a Boot Image, click next.

 

The screen asks me to select an Image Package, so I click on Browse - but only my previously captured WIM images appear - not my OS Installer.

 

 

Any one any ideas what I'm doing wrong? I've followed the guide on Windows-Noob.

 

Cheers

[clareq]

Don't they need to be in Operating System Images, not Operating System Installers?

[mdrabble]

From what I understand looking at the tutorial (and I very well may be wrong) the Operating System Installers are to install a fresh instances of Windows to allow you to create a custom image etc. - The Operating System Images are custom WIM images captured from the Installers (if that makes sense)

 

If I tried adding the extracted Windows ISO as an Operating System Image - It looks for a WIM file.

 

 

Cheers

[Norphy]

For operating system installers, you need to extract the ISO to a network share somewhere and point the wizard at the folder that you extracted the ISO to.

 

However, this is no longer a supported method with ConfigMgr 2012. The best way to do this is to add the the install.wim as an OS image and create a task sequence to deploy the OS from that. The only additional thing you should do is to set a task sequence variable called OSDPreserveDriveLetter to False. This will make sure that the OS gets deployed to C:, not D:

[mdrabble]

Ahhh.......... I see......... Slightly confused becuase if no longer a supported method, why include the options :confus

 

At least I stop backing my head on my desk

[Norphy]

Buggered if I know. All I know is that I spent a looooong time trying to get that option to work but eventually giving up when I read somewhere that they're not supporting it any more.

[AliG]

We just build a master PC (Virtual) and update the sccm image regularly using the capture media then roll the virtual machine snapshot back to original state ready for next time this works well for us

[mdrabble]

Got image building nicely and installing updates.

 

I've created a collection based on a Query on an OU and deployed a packages to that collection.

 

Am I right in thinking that the package should deploy to the computers in that collection?

[clareq]

Yes that's right

[free780]

I think its because MDT used to use setup.exe but switched to just imagex/dism in 2012. In s faster.

[heckle]

When I build my images I build them as virtual machines in Hyper-V. I also use a boot (capture) media iso to run the capture sequence. During deployment, I have the driver packs queried to install the proper drivers during the OSD task sequence.

[mdrabble]

Ive just moved my test network from an isolated VM networks to a small physical network so I can test the building of physical stations etc.

 

Ive found PXE boot to be extremely slow - excess of 30 mins before I even get the SCCM TS selections.

 

I've added the relevant hotfix 2905002 and 2910552 but not made any difference.

 

Ive added a reg key RamDiskTFTPBlockSize with either 8192 or 16384 and still no real difference.

 

Any one else suffer from very slow PXE Boot via SCCM?

[Fazza]

Any one else suffer from very slow PXE Boot via SCCM?

 

Yes and no.

 

Yes on older computers, no on newer ones.