OSD Reference Image Sequence

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

OSD Reference Image Sequence

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> OSD Reference Image Sequence

Page: [1]

Message

<< Older Topic Newer Topic >>

OSD Reference Image Sequence - 2/29/2008 2:18:47 PM

rjarrett

Posts: 595
Score: 17
Joined: 5/26/2004
Status: offline

According to Microsoft http://technet.microsoft.com/en-us/library/bb680965.aspx, the sequence to capture a defined "reference image" is to:

Configure the reference computer.
Run SysPrep with option to shutdown computer.
Create Image Capture Media (SCCM Console).
Boot reference computer with Capture Image Media.
Run Image Capture Wizard.

This makes no sense to me at all. What is more, I cannot make it work. Set aside the fact that you ought to have your "Image Capture Media" prepared BEFORE attempting any of this, here is what I have found to work:

Create Image Capture Media (SCCM Console).
Configure the reference computer.
Run Image Capture Wizard.
The Image Capture Wizard runs SysPrep and shuts down the computer.
Boot reference computer with Capture Image Media.

Am I smoking something? When I follow their documentation, the SysPrepped machine simply boots back into the mini-setup and never "captures" the image. Their documentation suggests that you SysPrep and then "capture" that SysPrepped image during the reboot. In fact, you have to go through the mini-setup, logon, then run the capture wizard which runs SysPrep all over again. Am I missing something?

My sequence seems to flow smoothly, but I don't know if I am getting a "proper" image. The attached image shows the MS flow chart an a parallel flow with the changes I have mentioned.

Comments would be welcome!

Thumbnail Image

Attachment (1)

< Message edited by rjarrett -- 3/5/2008 9:28:58 AM >

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

Post #: 1

RE: OSD Reference Image Sequence - 2/29/2008 2:42:20 PM

jdavis375

Posts: 150
Score: 17
Joined: 5/1/2006
From: Minneapolis, MN
Status: offline

Going through this very process right now myself. What I am doing is using a "build and capture" task sequence to create my base image. I am doing this on a virtual machine. This enables me to build a base image that doesn't have extraneous drivers in it. When I deploy the image I will have the Task Sequence inject the proper drivers to accomodate various hardware. I have the VM either PXE booting or booting from a bootable TS Media. Then it runs the "build and capture" task sequence and handles all of the build process, reboots, and upload. Got it to work fine yesterday.

Not sure if that helps or not, but that's my two cents.

_____________________________

Jarvis

My Blog: The Realm of the Verbal Processor

If my post was helpful, a rating would be appreciated!

(in reply to rjarrett)

Post #: 2

RE: OSD Reference Image Sequence - 3/1/2008 1:11:40 PM

MhermanNBME

Posts: 74
Score: 3
Joined: 4/4/2007
Status: offline

I agree with your logic, and that is what worked for me. I actually was working from a lab from microsoft management summit last year which pretty much followed your order.

(in reply to rjarrett)

Post #: 3

RE: OSD Reference Image Sequence - 3/3/2008 7:46:25 PM

wbracken

Posts: 1036
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline

Yep. As with Jarvis I am doing the build and capture sequence (using the intergation from MDT to import the task sequence).

You are correct though in your logic that the first scenerio does not make sense. You want to boot into Windows PE (via SCCM TS or via physical capture media) after sysprep runs and shuts the machine off otherwise yes mini-setup runs thus rendering you capture reference machine unusable and you must start again.

I also would recommend looking at building your reference machine in a VM (Virtual PC 2007/VMWare Server are free) and like Jarvis said keep unwanted drivers out of the base build and allows you to always have the "hardware" available to reproduce the base build process as needed.

_____________________________

William Bracken

Visit my new Blog
http://wbracken.wordpress.com/

(in reply to MhermanNBME)

Post #: 4

OSD Reference Image Sequence - 3/5/2008 9:12:08 AM

rjarrett

Posts: 595
Score: 17
Joined: 5/26/2004
Status: offline

My reference machine is a VMWare Server 1.0.4 machine. I have used both the VM and Intel Pro-100/1000 drivers.

I have not yet been successful in creating bootable media by "applying" drivers to the SCCM Vista x86 boot image. The drivers added nicely into the SCCM console. They "applied" to the boot image and the distribution points were updated. However, when I create an ISO from that image, it does not support the network. I am still investigating.

On the good side, I created a custom VMWare WXP SP2 compatible boot image that includes those NIC drivers using Windows AIK and its default Vista x86 boot image. Using that custom boot image, I was able to prepare a capture media. I then captured my WXP SP2 machine to an image file. I have successfully tested bare metal installation with that WXP SP2 image, using both standalone media and network boot images. Thus far, I have not done a PXE boot install.

The next step is to capture a Vista x86 reference machine. Then I should be able to test bare metal deployments and upgrades both. In any case, VMWare has proven useful. The next step is to test its installation on a physical machine. Even if it fails, the procedures used to add the VM and Intel NIC drivers to the image will permit adding other drivers, as needed.

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to wbracken)

Post #: 5