Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

How to deploy a SMS 2003 Operating System Deployment (OSD) image by using Remote Installation Services and Microsoft Business Desktop Deployment 2007

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 933554 - Last Review: October 31, 2007 - Revision: 1.2

How to deploy an SMS 2003 Operating System Deployment (OSD) image by using Remote Installation Services and Microsoft Business Desktop Deployment 2007

View products that this article applies to.

On This Page

INTRODUCTION

This article describes how to deploy a Microsoft Systems Management Server (SMS) 2003 Operating System Deployment (OSD) image by using Remote Installation Services and Microsoft Business Desktop Deployment 2007.
Back to the top

MORE INFORMATION

The "legacy flat" method

A common method to deploy operating system images to client computers is to use the SMS 2003 OSD Feature Pack. This method is known as the "legacy flat" method. It involves staging the OSD image installation CD on a Remote Installation Service (RIS) server for Pre-Boot Execution Environment (PXE) computers. The OSD documentation describes how to configure an RIS server to initiate the OSD image deployment.

This method is compatible with both the Microsoft Windows 2000 version of RIS and the Microsoft Windows Server 2003 version of RIS. This method requires Microsoft Windows Preinstallation Environment (Windows PE) 2004.

Note By default, Microsoft Windows PE 2004 is used in the OSD.
Back to the top

The "RAM disk" method

Windows Server 2003 Service Pack 1 (SP1) also provides another option for using RIS to initiate the OSD image deployment. This is the "RAM disk" method. Although this method is not documented in the OSD documentation, it is the preferred method to deploy Business Desktop Deployment (BDD) 2007 images when you initiate the OSD image by using RIS. However, Windows PE 2005 is required to use the RAM disk method. By default, the current release of the OSD feature pack does not include Windows PE 2005. To upgrade to Windows PE 2005, select the Update Windows PE option in BDD 2007, and then enter the path of Windows PE 2005 installation files.

If you are using BDD 2007 and if you want to use SMS 2003 and RIS, the Windows PE 2005 image that is required for OSD and for BDD 2007 must be generated by BDD 2007. You must update the OSD deployment point, and then use the Windows PE 2005 image that is generated by BDD to update OSD and RIS.
Back to the top

REFERENCES

The Microsoft Systems Management Server 2003 Operating System Deployment Feature Pack User's Guide describes how to update the Windows PE image. This guide is included with the SMS 2003 OSD Feature Pack.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
304992  (http://kbalertz.com/Feedback.aspx?kbNumber=304992/ ) How to deploy Microsoft Windows Preinstallation Environment from an RIS server by using PXE-enabled clients
Back to the top
APPLIES TO
  • Microsoft Systems Management Server 2003
Back to the top
Keywords: 
kbhowto kbexpertiseinter kbinfo KB933554
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting