Microsoft Knowledge Base Email Alertz

When you deploy a client operating system by using the Microsoft Systems Management Server 2003 Operating System Deployment (OSD) Feature Pack, the client operating system joins a workgroup instead of a domain

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: 910200 - Last Review: October 27, 2006 - Revision: 1.1

When you deploy a client operating system by using the Microsoft Systems Management Server 2003 Operating System Deployment (OSD) Feature Pack, the client operating system joins a workgroup instead of a domain

SYMPTOMS

You use the Microsoft Systems Management Server 2003 Operating System Deployment (OSD) Feature Pack to deploy a client operating system. Before you deploy this operating system, you select the Join the computer to a domain after new OS is applied check box on the Network tab of the Properties dialog box for the package. However, the deployed client operating system joins a workgroup instead of a domain.

You notice this problem when the following conditions are true:
  • You use a pre-prepared Sysprep.inf file when you capture the operating system.
  • A "JoinWorkgroup" entry appears in the "[Identification]" section of the Sysprep.inf file.

CAUSE

This problem occurs because of a conflict between the "JoinWorkgroup" entry in the Sysprep.inf file and the "JoinDomain" entry in the Sysprep.inf file.

RESOLUTION

To resolve this issue, do not put the "JoinWorkgroup" entry or the "JoinDomain" entry in the "[Identification]" section of the Sysprep.inf file.

If the "[Identification]" section of the Sysprep.inf file does not have these entries, the OSD Feature Pack generates the entry that is specified on the Network tab of the Properties dialog box.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Systems Management Server 2003
Keywords: 
kbtshoot kbsmsdeploy kbsmsfeaturepack kbprb KB910200
       

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