none
WDS Naming Computers

    Question

  • So I am trying to set up my WDS Server successfully. I have it working for the most part, the only problem that I have with it, is that I cannot get it to name the computers correctly. I prestage the computers with Active Directory and everything, but after I install the image on a computer with an Unattended Answer file, The computer just gets a random computer name, and that is totally useless to me in this Situation since I need to image a lot of computers and make sure their names are correct. ZTI would be best for me. Any help will be appreciated.  
    Thursday, March 01, 2007 5:06 AM

Answers

  • Hi Geokhal

    Thank you very much for your reply. I guess I was a bit quick off the mark to call the issue a bug without having real proof.  At the end of the day it will most likely turn out to be a typo or something stupid.

    I would like to take you up on your offer of help! I have WDS working exactly the way I want it to, apart from this issue I am having with the computer naming. It would be fantastic if you can point me in the right direction. I will post my entire ImageUnattend.xml and WDSClientUnattend.xml for you to have a look at. (Identifying data obscured.)

    WDSClientUnattend.xml:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
    http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Active>true</Active>
                                <Extend>false</Extend>
                                <Format>NTFS</Format>
                                <Label>Vista OS</Label>
                                <Letter>C</Letter>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Order>1</Order>
                                <Type>Primary</Type>
                                <Extend>true</Extend>
                            </CreatePartition>
                        </CreatePartitions>
                        <WillWipeDisk>true</WillWipeDisk>
                        <DiskID>0</DiskID>
                    </Disk>
                    <WillShowUI>OnError</WillShowUI>
                </DiskConfiguration>
                <ImageInstall>
                    <OSImage>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                        <WillShowUI>OnError</WillShowUI>
                        <InstallFrom>
                            <Credentials>
                                <Domain>DOMAIN</Domain>
                                <Password>password</Password>
                                <Username>Administrator</Username>
                            </Credentials>
                        </InstallFrom>
                    </OSImage>
                </ImageInstall>
                <UserData>
                    <ProductKey>
                        <WillShowUI>OnError</WillShowUI>
                        <Key>12345-12345-12345-12345-12345</Key>
                    </ProductKey>
                    <AcceptEula>true</AcceptEula>
                    <FullName>Organisation</FullName>
                    <Organization>Organisation</Organization>
                </UserData>
                <WindowsDeploymentServices>
                    <Login>
                        <Credentials>
                            <Domain>DOMAIN</Domain>
                            <Password></Password>
                            <Username>Administrator</Username>
                        </Credentials>
                    </Login>
                    <ImageSelection>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                    </ImageSelection>
                </WindowsDeploymentServices>
            </component>
            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
    http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SetupUILanguage>
                    <UILanguage>en-AU</UILanguage>
                </SetupUILanguage>
                <InputLocale>0c09:00000409</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UserLocale>en-AU</UserLocale>
                <UILanguage>en-AU</UILanguage>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://server/reminst/images/windows vista/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    ImageUnattend.xml:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="generalize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Home_Page>http://www.website.com.au</Home_Page>
                <IEWelcomeMsg>false</IEWelcomeMsg>
            </component>
            <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>EnableAdmin</Description>
                        <Order>1</Order>
                        <Path>cmd /c net user Administrator /active:yes</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>EnableAdmin_ploc</Description>
                        <Order>2</Order>
                        <Path>cmd /c net user Administrator_ploc /active:yes</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>UnfilterAdministratorToken</Description>
                        <Order>3</Order>
                        <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0c09:00000409</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UILanguage>en-AU</UILanguage>
                <UserLocale>en-AU</UserLocale>
            </component>
            <component name="Microsoft-Windows-TapiSetup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"

    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <TapiConfigured>0</TapiConfigured>
                <TapiUnattendLocation>
                    <AreaCode>""</AreaCode>
                    <CountryOrRegion>1</CountryOrRegion>
                    <LongDistanceAccess>9</LongDistanceAccess>
                    <OutsideAccess>9</OutsideAccess>
                    <PulseOrToneDialing>1</PulseOrToneDialing>
                    <DisableCallWaiting>""</DisableCallWaiting>
                    <InternationalCarrierCode>""</InternationalCarrierCode>
                    <LongDistanceCarrierCode>""</LongDistanceCarrierCode>
                    <Name>Default</Name>
                </TapiUnattendLocation>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <ProductKey>12345-12345-12345-12345-12345</ProductKey>
                <RegisteredOrganization>Organisation</RegisteredOrganization>
                <RegisteredOwner>JaySwift</RegisteredOwner>
                <ComputerName>%MACHINENAME%</ComputerName>
            </component>
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <Credentials>
                        <Domain>DOMAIN</Domain>
                        <Password>password</Password>
                        <Username>Administrator</Username>
                    </Credentials>
                    <JoinDomain>DOMAIN</JoinDomain>
                    <MachineObjectOU>OU=Windows Vista Workstations,OU=DOMAIN,DC=DOMAIN,DC=local </MachineObjectOU>
                </Identification>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0c09:00000409</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UILanguage>en-AU</UILanguage>
                <UserLocale>en-AU</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Display>
                    <HorizontalResolution>1024</HorizontalResolution>
                    <VerticalResolution>768</VerticalResolution>
                    <RefreshRate>60</RefreshRate>
                </Display>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>password=</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <DomainAccount wcm:action="add">
                                <Group>Administrators</Group>
                                <Name>Domain Admins</Name>
                            </DomainAccount>
                            <Domain>DOMAIN</Domain>
                        </DomainAccountList>
                    </DomainAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>password</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description>Computer Administrator</Description>
                            <DisplayName>Administrator</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Administrator</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <TimeZone>AUS Eastern Standard Time</TimeZone>
            </component>
        </settings>
        <settings pass="offlineServicing">
            <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DriverPaths>
                    <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                        <Path>C:\Drivers</Path>
                    </PathAndCredentials>
                    <PathAndCredentials wcm:keyValue="2" wcm:action="add">
                        <Path>X:\Drivers</Path>
                    </PathAndCredentials>
                </DriverPaths>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://server/reminst/images/windows vista/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    As stated before, my computers successfully joins the domain and I populate them in to the correct OU, but the computername is always a random name.

    It would be great if you can spot something wrong the in the answer files that will resolve my issue.

    Thanks & regards

    JaySwift

    Tuesday, March 20, 2007 8:35 AM
  • Hey Jay,
    I believe i just figured out how to do it. In your imageunattend.xml i think you can make your computer name this and it should get the prestaged computer name.
                <ComputerName>%MACHINENAME%</ComputerName>
    It worked for me.. let me know if you have the same situation. I hate this problem as I have probably imaged the same computer about 500 times over the last month now.   
    Tuesday, March 20, 2007 7:48 PM

All replies

  • Ok, So i just found out, that if you don't specify an Unattend Answer file for an image in WDS it will name the computer correctly. However, it makes the machine go through the OOBEUser Menus, and I want it to skip that. Does anyone know of a way to make the naming correct and have it skip the OOBE User screens?
    Friday, March 02, 2007 7:12 PM
  • Hi Doug

    Place the below in the ImageUnattend.xml

     <settings pass="specialize">
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <UnsecureJoin>True</UnsecureJoin>
                    <JoinDomain>DOMAINNAME</JoinDomain>
                </Identification>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
                <DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
                <RegisteredOrganization>OrganisationName</RegisteredOrganization>
                <RegisteredOwner>William Buck (NSW)</RegisteredOwner>
                <ShowWindowsLive>false</ShowWindowsLive>
                <ComputerName>*</ComputerName>
            </component>
        </settings>

    Check my full imageunattend.xml http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1127286&SiteID=17

    Cheers

    Monday, March 05, 2007 4:08 AM
  • Your Solution Did not work for me. I am still unable to do the task mentioned above.   
    Thursday, March 08, 2007 8:20 PM
  • Hi Doug

    Below is my complete "imageunattend.xml", note that you have to specify the skip user OOBE to true;  Mine also creates a local Admin user named "helpdesk" which will allow it to automatically join the domain successfully, as the "Local Admin" account in Vista is disabled by default.  All you need to to ensure now is that you have specified your "new client naming policy" parameters under the "directory services" tab in the properties in WDS.  Lastly for reference, I also have a WDSclient.xml file attached to the WDS server "client" tab which does my harddrive partitioning.  Hope this helps ..


    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="specialize">
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <UnsecureJoin>True</UnsecureJoin>
                    <JoinDomain>wbuck</JoinDomain>
                </Identification>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
                <DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
                <RegisteredOrganization>William Buck (NSW)</RegisteredOrganization>
                <RegisteredOwner>William Buck (NSW)</RegisteredOwner>
                <ShowWindowsLive>false</ShowWindowsLive>
                <ComputerName>*</ComputerName>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <UserAccounts>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <DomainAccount wcm:action="add">
                                <Group>Administrators</Group>
                                <Name>Domain Admins</Name>
                            </DomainAccount>
                            <Domain>wbuck</Domain>
                        </DomainAccountList>
                    </DomainAccounts>
                    <AdministratorPassword>
                        <Value>RwBNADAAMgAwADUAMAA0AGkAdABBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>RwBNADAAMgAwADUAMAA0AGkAdABQAGEAcwBzAHcAbwByAGQA</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <DisplayName>HelpDesk</DisplayName>
                            <Group>Administrators</Group>
                            <Name>HelpDesk</Name>
                            <Description />
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <TimeZone>AUS Eastern Standard Time</TimeZone>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <RegisteredOrganization></RegisteredOrganization>
                <RegisteredOwner></RegisteredOwner>
                <Themes>
                    <DefaultThemesOff>false</DefaultThemesOff>
                </Themes>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>en-US</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UILanguage>en-AU</UILanguage>
                <UserLocale>en-AU</UserLocale>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim:c:/vista_installation/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    Thursday, March 08, 2007 9:42 PM
  • What is your new client naming policy set as? I don't know the settings to use to say, get the name from AD.
    Thursday, March 08, 2007 11:02 PM
  • Hi Doug

    I just realised you prestage your computers.  I do not take that approach, but allow WDS to create the computer accounts for me and move them to my specified OU.

    The settings that I am talking about are located under the WDS properties.  Open up the WDS mmc, right click on your server and select properties and then select the Directory Services Tab.  All the settings are located there.

    My client naming policy is PC%03#, which will create the computers automatically and join them to the domain in the following logical format, PC001, PC002 etc.

    Hope this helps

    Thursday, March 08, 2007 11:32 PM
  • Yeah, So that wont help all that much then. Just because I prestage them. This is such a pain. I with is was just an easy solution. Thanks for your help though.
    Thursday, March 08, 2007 11:34 PM
  • All I need, Is to be able to use an Unattend file, and have it name the computer the same as the prestaged account in active directory. I dont care if it joins the domain, i mean Idealy it would join the domain but it doesnt need to. I have ways around that. Also I want it to skip the screens that ask for the EULA and for the User Account creation.
    Friday, March 09, 2007 6:45 PM
  • Hi Doug

    Not 100% sure about the prestaged account as I have not tested that method out.  However the xml file above will join the domain, and skip the eula screens and OOBE etc.  Please note that you have to create a local user account and as u can see my unattend file creates a local user account called Helpdesk.  My unattend file automates the entire process. Give it a go....

    Friday, March 09, 2007 11:35 PM
  • I did. It doesnt do what i want. The only thing i want it to do is name the computers per- the prestaged names i gave. It just gives it either a random name or it uses the naming policy from WDS. If i give it any answer file it doesnt name the computer correctly.
    Saturday, March 10, 2007 1:46 AM
  • Wow, So noone who has read this has this same situation at all i guess. Im suprised, because I would think any big enterprise situation with specifically named computer would want to do something like this. Unless they all use ghost, but If i could get WDS to work correctly I would think it would be faster/easier then ghost. Because ghost can be a pain to get working correctly. This is just so simple. But i cant get the stupid computer names to be right with any answer file. For some reason, if the image has no answer file on it, the computer is named correctly, and it joins the domain, but you have to go through the oobe menus to set up a user account when the image is first booted. And that is rather irritating. It would be much better if someone had a way to by pass these without using an answer file maybe.
    Monday, March 12, 2007 5:15 PM
  • Doug,

    I have exactly the same issue. If you use WDS to do the domain join and computer name generation it works without any issue (similar to RIS). However, as soon as you associate an ImageUnattend.XML answer file to take care of the unattended OOBE stuff etc, the computer name generation does not work. The best you get is a randomly generated name.

    I tried experimenting with not doing a Domain Join in ImageUnattend.XML but this produces a worse situation in that process does not resort to the WDS settings and the computer is not joined to the domain. Very frustrating.

    This is definately a bug (oversight) by Microsoft and I really hope they resolve this issue soon. Microsoft is really pushing BDD 2007, but it does NOT work properly with WDS.

    Good luck!

    JaySwift

     

    Sunday, March 18, 2007 9:55 AM
  • Im trying to find the part of WDS that generates the general Answerfile for use when you dont specify an answer file. I figure I can just take the part that gets the computer name and add that into a general answer file.   
    Monday, March 19, 2007 8:53 PM
  • Hi Jayswift

    There is no bug in WDS and automation of computer accounts.  I have successfully deployed WDS with the inclusion of the Imageunattend.xml and the WDSclientunattend.xml, and my computer accounts are generated successfully, eg. PC001,PC002,PC003.  Check my previous posts.  If you can provide me with more information I may be able to assist.

    Cheers
    Monday, March 19, 2007 10:53 PM
  • JaySwift,

    You are absolutely right about the BUG, I have raised a case at Microsoft in January and after several tests they came to the conclusion that it is a bug in WDS.

    The problem is related to the amount of computers you have already installed with RIS/WDS, if this amount is higher then 255 the naming of the computer does not work anymore.

    I have verified this by configuring a non default syntax for the computer account creation, so if you normally use "PC%4#" change it to "Test%4#", you will see that the computer name generation will work properly.

    So everyone who says it works properly work in an enviroment with fewer systems then 255 (installed by RIS/WDS).

    It is not sure yet if a fix will be provided or if they will wait until the next release of WDS is launched.

     


    Tuesday, March 20, 2007 6:59 AM
  • Hi Geokhal

    Thank you very much for your reply. I guess I was a bit quick off the mark to call the issue a bug without having real proof.  At the end of the day it will most likely turn out to be a typo or something stupid.

    I would like to take you up on your offer of help! I have WDS working exactly the way I want it to, apart from this issue I am having with the computer naming. It would be fantastic if you can point me in the right direction. I will post my entire ImageUnattend.xml and WDSClientUnattend.xml for you to have a look at. (Identifying data obscured.)

    WDSClientUnattend.xml:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
    http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Active>true</Active>
                                <Extend>false</Extend>
                                <Format>NTFS</Format>
                                <Label>Vista OS</Label>
                                <Letter>C</Letter>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Order>1</Order>
                                <Type>Primary</Type>
                                <Extend>true</Extend>
                            </CreatePartition>
                        </CreatePartitions>
                        <WillWipeDisk>true</WillWipeDisk>
                        <DiskID>0</DiskID>
                    </Disk>
                    <WillShowUI>OnError</WillShowUI>
                </DiskConfiguration>
                <ImageInstall>
                    <OSImage>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                        <WillShowUI>OnError</WillShowUI>
                        <InstallFrom>
                            <Credentials>
                                <Domain>DOMAIN</Domain>
                                <Password>password</Password>
                                <Username>Administrator</Username>
                            </Credentials>
                        </InstallFrom>
                    </OSImage>
                </ImageInstall>
                <UserData>
                    <ProductKey>
                        <WillShowUI>OnError</WillShowUI>
                        <Key>12345-12345-12345-12345-12345</Key>
                    </ProductKey>
                    <AcceptEula>true</AcceptEula>
                    <FullName>Organisation</FullName>
                    <Organization>Organisation</Organization>
                </UserData>
                <WindowsDeploymentServices>
                    <Login>
                        <Credentials>
                            <Domain>DOMAIN</Domain>
                            <Password></Password>
                            <Username>Administrator</Username>
                        </Credentials>
                    </Login>
                    <ImageSelection>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                    </ImageSelection>
                </WindowsDeploymentServices>
            </component>
            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
    http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SetupUILanguage>
                    <UILanguage>en-AU</UILanguage>
                </SetupUILanguage>
                <InputLocale>0c09:00000409</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UserLocale>en-AU</UserLocale>
                <UILanguage>en-AU</UILanguage>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://server/reminst/images/windows vista/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    ImageUnattend.xml:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="generalize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Home_Page>http://www.website.com.au</Home_Page>
                <IEWelcomeMsg>false</IEWelcomeMsg>
            </component>
            <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>EnableAdmin</Description>
                        <Order>1</Order>
                        <Path>cmd /c net user Administrator /active:yes</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>EnableAdmin_ploc</Description>
                        <Order>2</Order>
                        <Path>cmd /c net user Administrator_ploc /active:yes</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>UnfilterAdministratorToken</Description>
                        <Order>3</Order>
                        <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0c09:00000409</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UILanguage>en-AU</UILanguage>
                <UserLocale>en-AU</UserLocale>
            </component>
            <component name="Microsoft-Windows-TapiSetup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"

    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <TapiConfigured>0</TapiConfigured>
                <TapiUnattendLocation>
                    <AreaCode>""</AreaCode>
                    <CountryOrRegion>1</CountryOrRegion>
                    <LongDistanceAccess>9</LongDistanceAccess>
                    <OutsideAccess>9</OutsideAccess>
                    <PulseOrToneDialing>1</PulseOrToneDialing>
                    <DisableCallWaiting>""</DisableCallWaiting>
                    <InternationalCarrierCode>""</InternationalCarrierCode>
                    <LongDistanceCarrierCode>""</LongDistanceCarrierCode>
                    <Name>Default</Name>
                </TapiUnattendLocation>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <ProductKey>12345-12345-12345-12345-12345</ProductKey>
                <RegisteredOrganization>Organisation</RegisteredOrganization>
                <RegisteredOwner>JaySwift</RegisteredOwner>
                <ComputerName>%MACHINENAME%</ComputerName>
            </component>
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <Credentials>
                        <Domain>DOMAIN</Domain>
                        <Password>password</Password>
                        <Username>Administrator</Username>
                    </Credentials>
                    <JoinDomain>DOMAIN</JoinDomain>
                    <MachineObjectOU>OU=Windows Vista Workstations,OU=DOMAIN,DC=DOMAIN,DC=local </MachineObjectOU>
                </Identification>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0c09:00000409</InputLocale>
                <SystemLocale>en-AU</SystemLocale>
                <UILanguage>en-AU</UILanguage>
                <UserLocale>en-AU</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Display>
                    <HorizontalResolution>1024</HorizontalResolution>
                    <VerticalResolution>768</VerticalResolution>
                    <RefreshRate>60</RefreshRate>
                </Display>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>password=</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <DomainAccount wcm:action="add">
                                <Group>Administrators</Group>
                                <Name>Domain Admins</Name>
                            </DomainAccount>
                            <Domain>DOMAIN</Domain>
                        </DomainAccountList>
                    </DomainAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>password</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description>Computer Administrator</Description>
                            <DisplayName>Administrator</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Administrator</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <TimeZone>AUS Eastern Standard Time</TimeZone>
            </component>
        </settings>
        <settings pass="offlineServicing">
            <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral"

    versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DriverPaths>
                    <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                        <Path>C:\Drivers</Path>
                    </PathAndCredentials>
                    <PathAndCredentials wcm:keyValue="2" wcm:action="add">
                        <Path>X:\Drivers</Path>
                    </PathAndCredentials>
                </DriverPaths>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://server/reminst/images/windows vista/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    As stated before, my computers successfully joins the domain and I populate them in to the correct OU, but the computername is always a random name.

    It would be great if you can spot something wrong the in the answer files that will resolve my issue.

    Thanks & regards

    JaySwift

    Tuesday, March 20, 2007 8:35 AM
  • Hey Jay,
    I believe i just figured out how to do it. In your imageunattend.xml i think you can make your computer name this and it should get the prestaged computer name.
                <ComputerName>%MACHINENAME%</ComputerName>
    It worked for me.. let me know if you have the same situation. I hate this problem as I have probably imaged the same computer about 500 times over the last month now.   
    Tuesday, March 20, 2007 7:48 PM
  • Hey Jay,
    Maybe try not moving the OU for the computer. For some reason it works fine for me. And since I prestage the computers i just make the account in the OU i want it to be in. That way I dont need to move them around when you install it.

    Doug
    Wednesday, March 21, 2007 4:42 PM
  • Hi Doug

    Thanks for the advice / update. I tried using the %machinename% variable, but I ended up with the same result of a random name. I have not yet tried removing the OU specification, but will give it a go and let you know.

    I know how you feel about imaging the same computer about 500 times!! A large chunk of my life has gone down the abyss of deploying, sitting around for an hour in hopeful anticipation, dealing with my despondency when I notice the result, tweaking the answer file, getting another coffee and starting again!

    Thanks again!

    JaySwift

    Sunday, March 25, 2007 6:17 AM
  • Hi JaySwift

    You have <ComputerName>%MACHINENAME%</ComputerName> in your Imageunattend.xml.  Place * instead of %machinename%, and leave the naming automation to the Directory Services area - New client naming policy in WDS properties.

    e.g I have PC%03# as my format, hence producing computers with PC001,PC002 etc.

    Hope that makes sense.

    Cheers
    Wednesday, March 28, 2007 5:26 AM
  • Hey Jay,
    Not sure if this will help or not. But lets do a little debugging.
    Ok so, First to get the %machinename% variable to work you have to prestage your computers in Active Directory with the name you want the computer to be after the imaging process (Note: In the prestaging process you dont need to get the GUID you can also use the mac address of the computer, but if you do it needs to be prefixed by 20 Zeros, i.e. 00000000000000000000-macaddress)

    Now if you are not looking for a computer to be prestaged, then you should be able to put a * in for the computers name and the WDS server will name the computer in accordance to the naming policy you specified on the server. My situation was I had my computer prestaged and the naming policy was garbage for my enterprise.

    Now after you have the computer all prestaged in your Active Directory group, try making a very vanilla unattend.xml that just includes the computer name, nothing else. And take off your wdsclientunattend too. Just try the <Computername>%machinename%</Computername> setting and run it again. Let me know what happens after you do that. Keep in mind, if you want it to follow the naming policy make it <Computername>*</Computername>
       

    Wednesday, March 28, 2007 4:48 PM
  • hello,

    I have setup WDS server and playing with it for a month. I am using imageunttend.xml to automate installation everything works fine after installation finish it prompt me to specify computer name i am also using join domain to connect to my local domain in unattend.xml but after installation finish and come to login screen and i press ctrl -alt -del..i am unable to login using my domain account. I get trust relationship errror.

    I found on AD that random computer name is created and its different then my specified name at the end of installation.

    Also when i logon to vista PC using local account i found that it is connected to domain...but specified computer name is different than AD compute r account.

    How can i specified my desired name and join the domain at the same time. I have inventory sticker on my PC.so i want pc name same as my inventory sticker. I have worked with RIS and it  allow me to specify computer name before installation start...n i can connect to domain very easily.

    Can anybody help me please on this issue...of specify computername with joining domain correctly./

    Monday, April 02, 2007 2:17 PM
  • We use BDD Lite-Touch scenario to deploy Vista. In our customsettings.ini file, I specify ComputerName=%SerialNumber%. This will name the machine by serial number.
    Wednesday, April 04, 2007 12:06 PM
  • Hey Riz,
    Im using a lite-touch installation environment. Though it wouldnt be too hard to make it zero touch. But anyways, I prestage my computers in Active directory before I image them. Also, I have the WDS Server set to only respond to known clients. Then in Specialize->Setup->Computername I have %Machinename% set, and then the computer gets its name from what  you called it in active directory. As long as you keep the name in active directory the same as the name on the label then the computer will get that name when ever it is imaged.

    See my previous message for more information on prestaging and what-not.

    Hope that helps.  
    Wednesday, April 04, 2007 3:42 PM
  • Hello Doug,

    Thanks for your answer. I am not an expert..but i have used RIS before..and i can specify the computer name what i want. I never had to do prestage in AD.

    Also our organization put their own custom inventory label like C11280, C03555  etc. Is there any way i can install the vista unattended without prestage the computer name and still join the domain unattended and specify computer name of my choice.

     

     

    Thursday, April 05, 2007 2:26 PM
  • You could try the setting where you accept all clients to the WDS Server and then you need admin approval. Then when there is a pending device you can name it. But i dont think this is possible with just an imageunattend.xml. You have to either name the device before or have it use the naming policy.

    Doug 
    Friday, April 06, 2007 12:13 AM
  • <ComputerName>*</ComputerName>  ???

    Which means the computername will random.

     

    But if I would like the computername follow the policy like vistapc01 vistapc02... and so on??

    I had try to use vistapc%02#, but get error.

     

    I know we could setup on WDS->Servers->Specify Server->Properties->DS, but not work.

     


     

    Tuesday, April 17, 2007 6:25 AM
  • Hi Guys

     

    I apologise for the long hiatus. Work has been crazy!

     

    Unfortunately, despite all the troubleshooting / debugging advice you guys have provided, I am still not able to get the computer names to be correctly named. I am now going to rebuild WDS on another box and start fresh. Hopefully I can achieve a more favorouble result.

     

    Thanks again for all the feedback / assistance.

     

    JaySwift

     

    Thursday, May 03, 2007 2:04 AM
  • One question,

     

    Do you have more then 255 computers in the site where you are testing WDS now ?

     

    If so, you won't have any luck since it is related to a bug in WDS.

     

    Try changing the default name (on the Computer object of the WDS server) you use to generate computer accounts (ex. PC%3) and you'll see that it works.

    But if you use the name you are using by default and more then 255 computers are already named like this it is not going to work.

     

    Wait for MS to get a fix

    Monday, May 07, 2007 6:53 AM
  • Hey JaySwift,
    Sorry it has been a while since I read up on this thread. Could you maybe reiterate your problem to us so we can help you out? Are you maybe pre-staging your clients, or not? I will see if I can help you out then.
    Monday, May 07, 2007 4:36 PM
  • Hi

     

    I’m facing a similar problem that JaySwift reported at March 18.

    The whole WDS environment works fine for deploying Vista - except the computer naming. The systems are not pre-staged in AD.

    I got less than 255 installed systems; anyhow all I get are random computer names.

    I use Server 2003 SP1 where I first enabled and configured RIS following I installed the WINDOWS-DEPLOYMENT-SERVICES-UPDATE.

    I haven’t found the time to set up a Server 2003 SP2 system so far. Maybe that would work (without RIS). With SP2 there is no need to install WDS, so far I understood, WDS is already part of the OS and must just be enabled.

     

    I use WDSClientUnattend.xml for partitioning and ImageUnattend.xml to customize the installation.

     

    The “specialize-section” is set to <ComputerName>*</ComputerName>. The name doesn’t change even I leave it blank or use %machinename% instead.

    In WDS-properties-Directory Services I use Test%3#.

     

    What SP level and installation sequence do you guys use?

     

     

    Alex

    Monday, May 07, 2007 8:22 PM
  • Hey Alex,
    I am using Server 2003 with SP3 i believe, which ever one changes RIS to WDS. I am using a Lite Touch Installation method. Try removing your ImageUnatted.xml and just use your WDSClientUnattend.xml. Then Only put the computer name in the ClientUnattend.xml and see what happens. If you use %MACHINENAME% then your clients have to be prestaged in Active Directory with their GUID (or 20 zeros followed by its mac address). Let me know how these go.   
    Monday, May 07, 2007 10:57 PM
  • Hi Dough

     

    In the meantime I updated my system to SP2. But I’m unsure if I understand you:

    If I don’t use ImageUnatted.xml, the unattended setup won’t work.

    So I tried to store the whole information from ImageUnatted.xml inside the WDSClientUnattend.xml instead. But I got the error message “Windows could not  apply the Windows PE bootstrap setting specified in the unattended answer file.”. I’m still working on this. Did somebody see that before?

     

    Alternatively I edited the computer name in ImageUnatted.xml <ComputerName>PC001</ComputerName>: that works fine. But since that is definitely no solution I’m still looking for a way to get the computer name’s 3-digit extension increased automatically.

     

    There is most likely information in the logs that points to the problem. Unfortunately I couldn’t find it yet. Does somebody have an idea what to look for?

     

     

    thanks

    Alex

    Tuesday, May 08, 2007 8:03 PM
  • Try <ComputerName>PC#3</ComputerName>

    You don't NEED an ImageUnattend for the install to work. You just will manually have to do some stuff. Thats what i focus on when i have issues. Just make my unattends do only the thing im trying to get to work. And once i get that working throw everything else in. But that way you know what you want to work is working.

    Also try taking out the computer name portion of the unattend file.
    Tuesday, May 08, 2007 10:45 PM
  • Hi

     

    I tried <ComputerName>PC#3</ComputerName> and similar values.

    It didn’t work; the setup routine can’t handle that. It resulted in error messages.

    Removing the Computername section had no influence; a random name was created.

     

    I’m going to set up a new test environment from the scratch.

     

     

    Alex

    Wednesday, May 09, 2007 4:56 PM
  • Hey

     

    Finally I found the chapter Appendix C: Solution Extensibility in wdsupdate.chm that seems to be very interesting.

    I guess it’s pretty easy to write a little application that asks for the computer name and the OU (like RIS does). And it shouldn’t be a big deal to extend this application to increase a computer name extension like TestPC01, TestPC02… automatically.

     

    I’ll give it a try.

     

    Alex

    Wednesday, May 09, 2007 8:19 PM
  • Well if the situations that you tried dont work i think there has to be either something wrong with your unattend file or your wds set up. If you want you can post your ImageUnattend.xml and i will look it over for you, but make sure you are trying it without anything in your ClientUnattend.xml.  
    Wednesday, May 09, 2007 8:40 PM
  • I see a lot of questions regarding Machine Naming.. I will try summarize the behavior here and you can read more details from the WDS White paper below..

    http://go.microsoft.com/fwlink/?LinkId=81031

     

    Name Generation Policy:

       If your device is prestaged, then WDS Server tries to apply that Machine Name to your machine.

       If the device is not prestaged, then WDS Server tries to generate a machine name as specified by the machine naming policy of the WDS Server. and yes there is a bug if you are trying to generate more than 255 machine names with the same policy.

     

    Name Generation enforcement:

       If there is no ImageUnattend.xml file, then the WDS Server uses a template ImageUnattend file. This file is located in %windows%\system32\wdsunattendtemplate.xml.

       If there is an ImageUnattend.xml file for the image, then the WDS Server uses that. However, in order for domain join to work seamlessly without any credentials, you need to have the sections from the template unattend file as is.

       If UnsecureJoin flag for the DomainJoin section is missing or is set to False, then the WDS Server will just do the variable replacement for the ImageUnattend file like %MACHINENAME% and not do anything else. The replaced value will be based on the generated machine name form the policy above. Please not that, if UnSecureJoin is set to false, then you need to provide credentials in the unattend file in order to join the domain.

       All the above are followed only if domain join is enabled for new machines or prestaged devices on the WDS Server. If you have configured the WDS Server to not do domain join by default or a particular device to not join domain, then the WDS Server will not attempt any special steps, it will just use the ImageUnattend file specified and replace variables in it if necessary.

     

     

    Hope this clears things up..

    -Sudha

    Thursday, May 10, 2007 6:57 PM
  • Hi

     

    The WDS white paper is the document I mentioned yesterday (wdsupdate.chm).

    I worked through it and guess I configured all according to the document.

    But there is still this computer naming problem (even less than 255 installations).

     

     

    @ Doug

    In case you will find the time; here are both scripts.

    Maybe you can find the culprit.

     

    Thanks 

    Alex

     

     

    ImageUnattend.xml

    <?xml version="1.0" encoding="utf-8"?>

    <unattend xmlns="urnTongue Tiedchemas-microsoft-com:unattend">

        <servicing></servicing>

        <settings pass="windowsPE">

            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <DiskConfiguration>

                    <Disk wcm:action="add">

                        <ModifyPartitions>

                            <ModifyPartition wcm:action="add">

                                <Active>true</Active>

                                <Extend>false</Extend>

                                <Format>NTFS</Format>

                                <Label>Vista</Label>

                                <Letter>C</Letter>

                                <Order>1</Order>

                                <PartitionID>1</PartitionID>

                            </ModifyPartition>

                        </ModifyPartitions>

                        <DiskID>0</DiskID>

                        <WillWipeDisk>true</WillWipeDisk>

                        <CreatePartitions>

                            <CreatePartition wcm:action="add">

                                <Order>1</Order>

                                <Size>20000</Size>

                                <Type>Primary</Type>

                            </CreatePartition>

                        </CreatePartitions>

                    </Disk>

                    <WillShowUI>OnError</WillShowUI>

                </DiskConfiguration>

                <ImageInstall>

                    <OSImage>

                        <InstallTo>

                            <DiskID>0</DiskID>

                            <PartitionID>1</PartitionID>

                        </InstallTo>

                        <WillShowUI>OnError</WillShowUI>

                    </OSImage>

                </ImageInstall>

                <UserData>

                    <ProductKey>

                        <WillShowUI>Never</WillShowUI>

                    </ProductKey>

                    <AcceptEula>true</AcceptEula>

                </UserData>

                <PageFile>

                    <Path>C:\</Path>

                    <Size>1024</Size>

                </PageFile>

            </component>

            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <SetupUILanguage>

                    <UILanguage>&lt;UI Language&gt;</UILanguage>

                </SetupUILanguage>

                <InputLocale>DE-DE</InputLocale>

                <SystemLocale>DE-DE</SystemLocale>

                <UILanguage>EN-US</UILanguage>

                <UserLocale>DE-DE</UserLocale>

                <UILanguageFallback>EN-US</UILanguageFallback>

            </component>

        </settings>

        <settings pass="oobeSystem">

            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <OOBE>

                    <HideEULAPage>true</HideEULAPage>

                    <ProtectYourPC>1</ProtectYourPC>

                    <SkipMachineOOBE>true</SkipMachineOOBE>

                    <SkipUserOOBE>true</SkipUserOOBE>

                </OOBE>

                <AutoLogon>

                    <Password>

                        <Value>QQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgAxAEAAUABhAHMAcwB3AG8AcgBkAA==</Value>

                        <PlainText>false</PlainText>

                    </Password>

                    <Enabled>true</Enabled>

                    <LogonCount>1</LogonCount>

                    <Username>Administrator</Username>

                    <Domain>smslab</Domain>

                </AutoLogon>

                <VisualEffects>

                    <FontSmoothing>ClearType</FontSmoothing>

                </VisualEffects>

                <UserAccounts>

                    <AdministratorPassword>

                        <Value>QQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgAxAEAAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>

                        <PlainText>false</PlainText>

                    </AdministratorPassword>

                    <LocalAccounts>

                        <LocalAccount wcm:action="add">

                            <Password>

                                <Value>QQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgAxAEAAUABhAHMAcwB3AG8AcgBkAA==</Value>

                                <PlainText>false</PlainText>

                            </Password>

                            <Description>Support User</Description>

                            <DisplayName>Support User</DisplayName>

                            <Group>Administrators</Group>

                            <Name>Support</Name>

                        </LocalAccount>

                    </LocalAccounts>

                </UserAccounts>

                <Display>

                    <ColorDepth>32</ColorDepth>

                    <HorizontalResolution>1024</HorizontalResolution>

                    <VerticalResolution>768</VerticalResolution>

                    <RefreshRate>60</RefreshRate>

                </Display>

                <RegisteredOwner>AvR</RegisteredOwner>

                <TimeZone>(GMT+01:00)</TimeZone>

            </component>

        </settings>

        <settings pass="specialize">

            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <OEMInformation>

                    <Manufacturer>AvR System Engineering</Manufacturer>

                </OEMInformation>

                <RegisteredOrganization>AvR System Engineering</RegisteredOrganization>

                <RegisteredOwner />

                <ComputerName>*</ComputerName>

                <TimeZone>W. Europe Standard Time</TimeZone>

            </component>

            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <Identification>

                    <Credentials>

                        <Domain>smslab</Domain>

                        <Password>Administrator1@</Password>

                        <Username>Administrator</Username>

                    </Credentials>

                    <JoinDomain>smslab</JoinDomain>

                    <MachineObjectOU>OU=Test Computers,OU=Test Environment,DC=smslab,DC=de </MachineObjectOU>

                </Identification>

            </component>

            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <InputLocale>DE-DE</InputLocale>

                <SystemLocale>DE-DE</SystemLocale>

                <UserLocale>DE-DE</UserLocale>

                <UILanguage>DE-DE</UILanguage>

                <UILanguageFallback>EN-US</UILanguageFallback>

            </component>

        </settings>

        <cpiSurprisefflineImage cpiTongue Tiedource="wim:e:/install/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urnTongue Tiedchemas-microsoft-com:cpi" />

    </unattend>

     

    WdsClientUnattend.xml

    <?xml version="1.0" encoding="utf-8"?>

    <unattend xmlns="urnTongue Tiedchemas-microsoft-com:unattend">

        <settings pass="windowsPE">

            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <DiskConfiguration>

                    <Disk wcm:action="add">

                        <ModifyPartitions>

                            <ModifyPartition wcm:action="add">

                                <Active>true</Active>

                                <Extend>false</Extend>

                                <Format>NTFS</Format>

                                <Label>Vista</Label>

                                <Letter>C</Letter>

                                <Order>1</Order>

                                <PartitionID>1</PartitionID>

                            </ModifyPartition>

                        </ModifyPartitions>

                        <DiskID>0</DiskID>

                        <WillWipeDisk>true</WillWipeDisk>

                        <CreatePartitions>

                            <CreatePartition wcm:action="add">

                                <Order>1</Order>

                                <Size>20000</Size>

                                <Type>Primary</Type>

                            </CreatePartition>

                        </CreatePartitions>

                    </Disk>

                    <WillShowUI>OnError</WillShowUI>

                </DiskConfiguration>

                <ImageInstall>

                    <OSImage>

                        <InstallTo>

                            <DiskID>0</DiskID>

                            <PartitionID>1</PartitionID>

                        </InstallTo>

                        <WillShowUI>OnError</WillShowUI>

                    </OSImage>

                </ImageInstall>

                <UserData>

                    <ProductKey>

                        <WillShowUI>Never</WillShowUI>

                    </ProductKey>

                    <AcceptEula>true</AcceptEula>

                    <Organization>AvR System Engineering</Organization>

                </UserData>

                <WindowsDeploymentServices>

                    <Login>

                        <Credentials>

                            <Domain>smslab</Domain>

                            <Password>Administrator1@</Password>

                            <Username>Administrator</Username>

                        </Credentials>

                    </Login>

                    <ImageSelection>

                        <InstallImage>

                            <Filename>Install.wim</Filename>

                            <ImageGroup>Vista</ImageGroup>

                            <ImageName>Windows Vista ULTIMATE</ImageName>

                        </InstallImage>

                        <InstallTo>

                            <DiskID>0</DiskID>

                            <PartitionID>1</PartitionID>

                        </InstallTo>

                    </ImageSelection>

                </WindowsDeploymentServices>

                <EnableFirewall>true</EnableFirewall>

                <EnableNetwork>true</EnableNetwork>

            </component>

            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <SetupUILanguage>

                    <UILanguage>EN-US</UILanguage>

                </SetupUILanguage>

                <InputLocale>DE-DE</InputLocale>

                <SystemLocale>DE-DE</SystemLocale>

                <UILanguage>EN-US</UILanguage>

                <UserLocale>DE-DE</UserLocale>

                <UILanguageFallback>EN-US</UILanguageFallback>

            </component>

        </settings>

        <cpiSurprisefflineImage cpiTongue Tiedource="wim:e:/install/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urnTongue Tiedchemas-microsoft-com:cpi" />

    </unattend>

    Thursday, May 10, 2007 7:24 PM
  • Now the next question would be, is the machine prestaged? Also what is your naming policy set as? and what name did this give the computer when you imaged it?
    Thursday, May 10, 2007 8:33 PM
  • Hello guys.  I have been studying this thread(and others) to figure out my problem, no solid answer yet.  Those of us that are not prestaging our computer accounts and having trouble with naming need to know what configs in the ImageUnattend.xml or on the server can cause the WDS naming policy to be overwritten or not applied at all.  Like alex and (i think) jay, my naming policy works just fine when ImageUnattend.xml is not applied.  After digging into setupact.log, i see that the computer is properly named, then improperly named later on.  As i change my configs and reimage, i have seen my literal naming policy in the log file as well as the one it should be (SW%MAC vs SW001143######).  I have tried deleting the ComputerName config, leaving it blank, and both * and %MACHINENAME%.  I have moved it between unattend files.  What i need to know is the logical process setup goes through regarding computer names so i can see where my WDS naming policy is being stomped.  If someone has an answer for me, try to be specific procedurally as we all know the order of how things are done can matter with MS software even when it shouldn't.  And now for the files.....

    WDSClientUnattend.xml

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urnTongue Tiedchemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Extend>true</Extend>
                                <Type>Primary</Type>
                                <Order>1</Order>
                            </CreatePartition>
                        </CreatePartitions>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Active>true</Active>
                                <Extend>false</Extend>
                                <Format>NTFS</Format>
                                <Label>Vista</Label>
                                <Letter>C</Letter>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                        <DiskID>0</DiskID>
                        <WillWipeDisk>true</WillWipeDisk>
                    </Disk>
                    <WillShowUI>OnError</WillShowUI>
                </DiskConfiguration>
                <ImageInstall>
                    <OSImage>
                        <WillShowUI>OnError</WillShowUI>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                    </OSImage>
                </ImageInstall>
                <UserData>
                    <AcceptEula>true</AcceptEula>
                    <FullName>xxxxx</FullName>
                    <Organization>xxxxx</Organization>
                    <ProductKey>
                        <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key>
                        <WillShowUI>OnError</WillShowUI>
                    </ProductKey>
                </UserData>
                <WindowsDeploymentServices>
                    <ImageSelection>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                    </ImageSelection>
                </WindowsDeploymentServices>
            </component>
            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SetupUILanguage>
                    <UILanguage>en-US</UILanguage>
                </SetupUILanguage>
                <InputLocale>en-US</InputLocale>
                <SystemLocale>en-US</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>en-US</UserLocale>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>xxxxx==</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                </UserAccounts>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                    <SkipMachineOOBE>true</SkipMachineOOBE>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <TimeZone>US Mountain Standard Time</TimeZone>
                <RegisteredOrganization>xxxxx</RegisteredOrganization>
                <RegisteredOwner>xxxxx</RegisteredOwner>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <AutoLogon>
                    <Password>
                        <Value>xxxxx=</Value>
                        <PlainText>false</PlainText>
                    </Password>
                    <Username>Administrator</Username>
                    <Enabled>true</Enabled>
                </AutoLogon>
                <TimeZone>US Mountain Standard Time</TimeZone>
                <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey>
                <RegisteredOwner>Starwood Systems Phoenix</RegisteredOwner>
                <RegisteredOrganization>Starwood Hotels &amp; Resorts</RegisteredOrganization>
                <ComputerName>%MACHINENAME%</ComputerName>
            </component>
            <component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipAutoActivation>true</SkipAutoActivation>
            </component>
        </settings>
        <cpiSurprisefflineImage cpiTongue Tiedource="catalog:c:/sundry/working/wds/install_windows vista enterprise.clg" xmlns:cpi="urnTongue Tiedchemas-microsoft-com:cpi" />
    </unattend>

    ************************

    ImageUnattend.xml

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urnTongue Tiedchemas-microsoft-com:unattend">
        <servicing></servicing>
        <settings pass="specialize">
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <Credentials>
                        <Domain>xxxxx</Domain>
                        <Username>WDS</Username>
                        <Password>xxxxx</Password>
                    </Credentials>
                    <JoinDomain>xxxxx</JoinDomain>
                </Identification>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <ComputerName>%MACHINENAME%</ComputerName>
                <RegisteredOwner>xxxxx</RegisteredOwner>
                <RegisteredOrganization>xxxxx</RegisteredOrganization>
                <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey>
                <TimeZone>US Mountain Standard Time</TimeZone>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                    <SkipMachineOOBE>true</SkipMachineOOBE>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <TimeZone>US Mountain Standard Time</TimeZone>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>xxxxx==</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                </UserAccounts>
                <AutoLogon>
                    <Password>
                        <Value>xxxxx=</Value>
                        <PlainText>false</PlainText>
                    </Password>
                    <Username>Administrator</Username>
                    <Enabled>true</Enabled>
                </AutoLogon>
                <RegisteredOrganization>xxxxx</RegisteredOrganization>
                <RegisteredOwner>xxxxx</RegisteredOwner>
            </component>
        </settings>
        <cpiSurprisefflineImage cpiTongue Tiedource="catalog:c:/sundry/working/wds/install_windows vista enterprise.clg" xmlns:cpi="urnTongue Tiedchemas-microsoft-com:cpi" />
    </unattend>


    Keep in mind this was just my last attempt.  Again, everything works fine except the computer name which comes up random, and should be 'SW' followed by the computer's mac address.  I have verified that the WDSClientUnattend.xml file will name them properly without the ImageUnattend.xml file attached to the image file.  Thanks in advance for your help my nerdy peeps.
    Friday, May 11, 2007 12:20 AM
  • Hey El_Wayman

    Ok, So From what im reading, your client unattend xml file looks to have a lot of unneeded garbage in it. So here I will describe my set up to you.

    I have a Simple Client Unattend xml File, and in this file i just give the credentials to get into the WDS image selection screen. (Mainly because the image selection could be different and disk formatting could be different as well) Anyways that Is ALL i have in my client unattend file.

    In my Image unattend file i have it join the domain, set the computer name (I think this is done in the Specialize phase) enter the product key, set the computer resolution, log in with a domain admin and run a script that activates vista and installs an SMS client.

    So i think you could cut alot of the stuff out of your image unattend, or even not use it while you are trying to get your computer name to work correctly (as it is really not needed, it just makes things easier and potentially all you have to to is network boot a computer for the image to install correctly). Then you could try just building a basic Image unattend that only has two things, maybe joining a domain and naming the computer correctly. So then here is what I understand the naming scheme to be. First off keep in mind that I prestage my clients because I have names I want them to be but I did come across many errors as i was getting to this point. Anyways here it goes.

    <ComputerName>*</ComputerName>
    This set up gives you a RANDOM name, I don't believe this one is supposed to give you the naming policy, as * is wild card. In all of my cases when i gave it this one i would get names like LH-07810PAP92199GANI. And those are useless to me.

    <ComputerName>%MACHINENAME%</ComputerName>
    This set up attempts to get a PRESTAGED name from Active Directory. This is what I use because I have set names that I need the computers to be. Keep in mind too, that when you prestage the comptuers you have to set them as managed computers and enter the guid for the computer, which can be found/entered a couple of different ways, First (I would only use this way if you prefer it) you can network boot and the computer should give you the GUID, which is pretty much total garbage. Then you would enter that number in as the guid of the prestaged computer and it would work fine then. You can then specify that only recognized computers should be answered, so that only prestaged computers will get pxebooted. The second (more preferred method for me) is that you get the comptuers Mac Address, and then enter the GUID as 20 zeros followed by the mac address, something like this 000000000000000000000014BC78A9.

    Now I believe if you want to get the naming policy to work, you have to leave the
    <ComputerName></ComputerName> part out of your answer file. Because anything in there will either error into a random name or give you a name you don't want.

    Since you know that it works without an Answer file, try an answer file with just one property that you want to test with, and see if you get your naming policy to work. Then slowly add the rest of it back in, probably one at a time. This is what I had to do to figure out how to use my computer naming.

    So what you would do here, is Dont use either of your Unattended files, then make a new image unattend file. In this file you would just put a single property, then image a computer and see if the name works. If it does, add another one and do it again. and see if it works. Do this until you build the answer file you are looking for (if you know more then one thing won't affect the name then wait and add those all at the same time at the end) After you have a working Image Unattend file make a client unattend that does just what you need it to. Keep in mind all it is good for is stuff up until you format the disks and start the installation, then the Image Unattend takes over.

    Let me know if you have anymore problems, i know this seems like a long an tedious way of working through this problem, but once you get it working you should have a better understanding of how to make it work from scratch again. As this is what i had to go through to get to the point i am at now.
    Friday, May 11, 2007 2:17 AM
  • Hi Doug
     
    The machine isn't prestaged. I try to install it by using the original install.wim from the DVD in combination with these two answer files. The naming policy is set to use Test%3#. The computer name is set to something like LH-078XXXXXX after the unattended setup. I don't find any hint in the logs according to the naming convention (Test%3#). It is simply ignored.
     
    I guess I'll give your advice (to set up new xml files from the scratch) a try. Do I understand you right - you have already fixed the problem you mentioned March 1? Maybe you could post your answer files; so I could compare them with my stuff. Although you use prestaged systems I guess I will find a hint.
     
     
        Alex
    Friday, May 11, 2007 1:44 PM
  • Hey Alex,
    I did get mine working, my problem was fixed just by the %MachineName% part. Here are my unattend files, let me know if you need anything else.

    ClientUnatten.xml
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urnTongue Tiedchemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <WindowsDeploymentServices>
                    <Login>
                        <Credentials>
                            <Username>DomainAdmin</Username>
                            <Password>Password</Password>
                        </Credentials>
                    </Login>
                </WindowsDeploymentServices>
            </component>
        </settings>
        <cpiSurprisefflineImage cpiTongue Tiedource="wim:c:/documents%20and%20settings/builder/desktop/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urnTongue Tiedchemas-microsoft-com:cpi" />
    </unattend>

    ImageUnattend.xml
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urnTongue Tiedchemas-microsoft-com:unattend">
        <servicing></servicing>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <SkipMachineOOBE>true</SkipMachineOOBE>
                    <SkipUserOOBE>true</SkipUserOOBE>
                    <ProtectYourPC>1</ProtectYourPC>
                    <NetworkLocation>Work</NetworkLocation>
                    <HideEULAPage>true</HideEULAPage>
                </OOBE>
                <TimeZone>Pacific Standard TIme</TimeZone>
                <RegisteredOrganization>Org</RegisteredOrganization>
                <RegisteredOwner>Owner</RegisteredOwner>
                <ShowWindowsLive>false</ShowWindowsLive>
                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
                <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
                <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>ZwBvAGIAZQBhAHYAJABQAGEAcwBzAHcAbwByAGQA</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <DisplayName>Admin</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Admin</Name>
                        </LocalAccount>
                    </LocalAccounts>
                    <AdministratorPassword>
                        <Value>ZwBvAGIAZQBhAHYAJABBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                </UserAccounts>
                <AutoLogon>
                    <Password>
                        <Value>JAB1AHAAZQAmAG0AXgBuAFAAYQBzAHMAdwBvAHIAZAA=</Value>
                        <PlainText>false</PlainText>
                    </Password>
                    <Domain>domain</Domain>
                    <Enabled>true</Enabled>
                    <LogonCount>1</LogonCount>
                    <Username>domainadmin</Username>
                </AutoLogon>
                <FirstLogonCommands>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>cscript \\aurora\software\scripts\setupcomputer.vbs</CommandLine>
                        <Order>1</Order>
                        <Description>Set up computer</Description>
                    </SynchronousCommand>
                </FirstLogonCommands>
                <Display>
                    <HorizontalResolution>1280</HorizontalResolution>
                    <VerticalResolution>1024</VerticalResolution>
                    <ColorDepth>32</ColorDepth>
                </Display>
                <StartPanelLinks>
                    <Link0>c:\Windows\Script\Install New Programs.lnk</Link0>
                </StartPanelLinks>
            </component>
            <component name="Microsoft-Windows-Sidebar" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SidebarOnByDefault>false</SidebarOnByDefault>
                <SidebarVisible>false</SidebarVisible>
                <Gadget1 />
                <Gadget2 />
                <Gadget3 />
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <ComputerName>%MACHINENAME%</ComputerName>
                <RegisteredOrganization>Org</RegisteredOrganization>
                <RegisteredOwner>Owner</RegisteredOwner>
                <TimeZone>Pacific Standard Time</TimeZone>
                <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>
            </component>
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <Credentials>
                        <Username>DomainAdmin</Username>
                        <Password>Password</Password>
                    </Credentials>
                    <JoinDomain>Domain</JoinDomain>
                </Identification>
            </component>
            <component name="Microsoft-Windows-RemoteAssistance-Exe" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <fAllowFullControl>false</fAllowFullControl>
                <fAllowToGetHelp>false</fAllowToGetHelp>
                <MaxTicketExpiry>1</MaxTicketExpiry>
            </component>
            <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <fDenyTSConnections>false</fDenyTSConnections>
            </component>
        </settings>
        <settings pass="generalize">
            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
        </settings>
        <cpiSurprisefflineImage cpiTongue Tiedource="wim:g:/sources/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urnTongue Tiedchemas-microsoft-com:cpi" />
    </unattend>


    Friday, May 11, 2007 5:27 PM
  • Oh, that is strange!

     

    Thanks for the XMLs. After some minor modifications (the setup routine disliked the “Specialize” section) I got it to work. BUT NOW the computer name is set to  WINDOWS-FUIRUJE instead of LH-078XXXXXX.

    Fortunately I have the entire weekend to work on this.   ;-)))

     

                   Alex

     

    Saturday, May 12, 2007 4:26 PM
  • Finally I got it working (computer naming) .
    With enabling the <UnsecureJoin> option the computer name policy operates.
    By now I'm unsure if that has bad influence to the Domain security.
     
    Alex
     
    Saturday, June 02, 2007 3:01 PM
  • Hi folks, may be I'm a little late but I think there is still somebody out there who want's to know how to solve the naming-problem.

    With WDS and XP it is a little tricky.

    Here is the result of my work:

    At first put some ********* or nothing into the credentials-part of winpe-unattended, so somebody must logon

    <Login>
                        <Credentials>
                            <Domain>bwielsch</Domain>
                            <Username></Username>
                            <Password></Password>
                        </Credentials>
                    </Login>

    Next thing todo is to put the now logged user into the sysprep.inf:

    Here you go:

    Check this out, it will name the user with logged in username+incremental number counting up:

    Changes to sysprep.inf:

    [UserData]

    UserName=%61Username%# (You can see it's calling the same variable like WDS)

    Next change:

    [Identification]
        JoinDomain=%MACHINEDOMAIN%
        DoOldStyleDomainJoin=Yes

    Now, have a beer and enjoy your OS-DEPLOYMENT

     

    P.S.: Watchout the path where your sysprep.inf is placed.May be you won't menture it'snot working

    E:\REMINST\Images\YourImageGroup\NameOfYourWIM-IMAGE\$OEM$\$1\Sysprep

    In the folder "YourImageGroup" place your Install.wim

    Important is to name the subfolder of "NameOfYourWIM-IMAGE" with install.wim name (without extension)

     

    O.K. that's it and thanks to all the others I get the very important partly informations from while I googled the last week.

    • Proposed as answer by Condorfierro Monday, January 24, 2011 11:39 PM
    Monday, October 20, 2008 6:02 PM
  • Hey there! I'm going to sum up everything here (I'm using WDS in a 2K8 R2 Server)...

    There are several methods to name computers using WDS, and here are my conclusions:

    • All of them are for the "imageunattend.xml" answer file
    1. Put "%MACHINENAME%" (without quotes) inside the ComputerName tag (Microsoft-Windows-Shell-Setup_neutral -- Pass 4 Specialize) without Pre-Staging the computer in AD (Pre-Creating the computer in AD), then you should Right Click your WDS Server inside the WDS Console and go to Properties (remember to save your answer file), now click on the "PXE Response" Tab and Click the Radio Button "Respond to all Client Computers" and the Check Box "Require Administrator Approval..." and click OK, after that you might want to load your saved answer file in one of your Install Images. When the computer boots up from PXE and from WDS it'll wait for approval then in your WDS Console in the "Pending Devices" node click refresh and you will see the computer (unless it has already been accepted), right click it and select "Name and Approve" you can write a name, that's it your deployment will continue.....NOTE: THIS METHOD IS QUITE PROBLEMATIC, I RECOMEND YOU NOT TO USE IT BECAUSE, some devices have problems using the Administrator Approval feature and will not boot from WDS, another one is the pain for naming each computer one by one inside the pending devices node, but it works...
    2. Put "%MACHINENAME%" (without quotes) inside the ComputerName tag (Microsoft-Windows-Shell-Setup_neutral -- Pass 4 Specialize), in this case you will Pre-Stage your computer and when you're creating the Computer inside AD, it'll prompt you for the GUID, here you will enter 20 ceros and then your MAC Address like this 000000000000000000000014BC78A9, do not use the Administrator Approval unless you want it (but in that case you'll use just the "Approve" option not "Name and Approve"), then do the deployment and you'll see the name...NOTE: YOU'LL WASTE SOME TIME PRE-STAGING
    3. Put "*" (without quotes) inside the ComputerName tag (Microsoft-Windows-Shell-Setup_neutral -- Pass 4 Specialize) or LEAVE IT BLANK (EMPTY), both ways work, but in this case you will set to "true" the "UnsecuredJoin" tag inside "Microsoft-Windows-UnattendedJoin_neutral" node giving the option to use a null-session to join the computer anonymously in the Domain, actually it'll be unsecured in the case you do not prompt the user for the WDS Credentials in the boot answer file (unattend.xml), save your image answer file and load it in your Install Image, right click your server inside the WDS Console and go to properties, then click on the AD DS tab and write your format, mine was "PC%03#" without quotes, after that you should be good to go on your deployments, i recomend you to read the Help File about unsecuredjoin and mostly all of the credentials options, good luck, sorry for my bad english. My first deployment on "Win 7 Ent x64" gave a computer name like this "PC001". =P
    4. Another way to do this is by erasing the ComputerName tag directly from your xml file (<ComputerName></ComputerName>), then it'll prompt you for the computer name, i'm actually using this when i'm not joining the computer to the domain, because the policy applies only to AD DS, that's it.
    5. If you're trying to keep the name of an actual existing AD Computer, you'd like to use the "%MACHINENAME%" variable inside the ComputerName tag because it'll search in AD for a Computer with the same GUID and then it'll apply the name that used to have.
    6. Search another command and script ways for this using variables or anything else, inside Microsoft you should find everything, thank you.
    Tuesday, January 25, 2011 12:17 AM