+ Post New Thread
Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 37
O/S Deployment Thread, Win7 Unattend.xml Not Being Applied in Technical; The name I use is "ImageUnattend.xml". Once you point to the unattend file in the properties of the image, it ...
  1. #16

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    The name I use is "ImageUnattend.xml". Once you point to the unattend file in the properties of the image, it automatically moves the file where it wants it (image folder\image\unattend\) and renames it to "unattend.xml".

    Thanks.

  2. #17

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    When trying the $OEM$, dont forget to remove the unattend.xml attached to the image under WDS.

    Are you trying to deploy Windows 7 x86 or x64?

    How big is the setupact.log file?

    Regards
    Sukh
    Last edited by sukh; 28th February 2011 at 07:38 PM.

  3. #18

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    The setupacct.log is 533 kbs. I'm limited to 488.

    Deploying Win7 x86. Again, the image works fine, I am just not getting the changes in the unattend file applied.

    Thanks again.

  4. #19

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    Can you try to cut and paste the log file into two text files and upload each one in a seperate post?

    Regards
    Sukh

  5. #20

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    The following errors occurred with your submission

    The text that you have entered is too long (546473 characters). Please shorten it to 12000 characters long.

    Sorry......

  6. #21

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    Email to me.

    Regards
    Sukh
    Last edited by sukh; 28th February 2011 at 08:20 PM.

  7. #22

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    Can you confirm your boot image is x86?

    I can see from the log that the unattend.xml is not being applied during setup mode. Still investigating. Please confirm the boot image.

    Regards
    Sukh

  8. #23

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Yes....X86 image.

  9. #24

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    When you create the unattend.xml with WSIM. There is a section called ImageSelection under components>microsoft-windows-setup>windowsdeploymentservices.

    Can you check to see if this is configured correctly. If not can you configure and try.

    Can you check to see if the FileName, ImageGroup and ImageName are configured or empty?

    Before you try deployment again, let me know if this is configured properly or not?



    Regards
    Last edited by sukh; 28th February 2011 at 10:14 PM.

  10. #25

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    With the ImageUnattend.xml, I did not include that section. I understood to leave that blank to prompt for the image.

    With the WDSUnattend.xml it is configured:

    <InstallImage>
    <ImageName>Image Name as displayed in WDS</ImageName>
    <ImageGroup>Image Group</ImageGroup>
    <FileName>WIM Image Filename</FileName>
    </InstallImage>

  11. #26

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    Can you post the WDS Client unattend.xml?

    Regards
    Sukh

  12. #27

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    WDSUnattend.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>
    <WillShowUI>OnError</WillShowUI>
    <Disk wcm:action="add">
    <CreatePartitions>
    <CreatePartition wcm:action="add">
    <Order>1</Order>
    <Type>Primary</Type>
    <Extend>true</Extend>
    </CreatePartition>
    </CreatePartitions>
    <ModifyPartitions>
    <ModifyPartition wcm:action="add">
    <Active>true</Active>
    <Format>NTFS</Format>
    <Label>WinXP</Label>
    <Letter>C</Letter>
    <Order>1</Order>
    <PartitionID>1</PartitionID>
    </ModifyPartition>
    </ModifyPartitions>
    <DiskID>0</DiskID>
    <WillWipeDisk>true</WillWipeDisk>
    </Disk>
    </DiskConfiguration>
    <WindowsDeploymentServices>
    <Login>
    <Credentials>
    <Domain>acsd4.local</Domain>
    <Username>wds</Username>
    <Password>###</Password>
    </Credentials>
    </Login>
    <ImageSelection>
    <WillShowUI>OnError</WillShowUI>
    <InstallImage>
    <ImageName>Image Name as displayed in WDS</ImageName>
    <ImageGroup>Image Group</ImageGroup>
    <FileName>WIM Image Filename</FileName>
    </InstallImage>
    <InstallTo>
    <DiskID>0</DiskID>
    <PartitionID>1</PartitionID>
    </InstallTo>
    </ImageSelection>
    </WindowsDeploymentServices>
    </component>
    </settings>
    </unattend>

    Thanks.

  13. #28

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    78
    Hi

    Can you let me know how the results of the $OEM$ test ?

    If this failed, can you also do the following.

    1. From WSIM save the answer file as Autounattend.xml

    2. Copy the Autounattend.xml file to a USB flash drive, then try to install Windows 7 from DVD on an reference computer. Or copy the Autounattend.xml to the root od the DVD which has the Windows 7 source files.



    Note: Windows 7 Setup (Setup.exe) will begin automatically. By default, Windows Setup will search the root directory of all removable media for an answer file called Autounattend.xml.

    Regards
    Sukh

  14. #29
    tarquel's Avatar
    Join Date
    Jun 2005
    Location
    Powys, Mid-Wales, UK
    Posts
    1,740
    Thank Post
    13
    Thanked 45 Times in 35 Posts
    Rep Power
    30
    just to add another option to point 2, with a particularly nippy USB pen, put the install on the pen, along with the answer file, and boot and install it from that

    To do that easily, use this: Microsoft Store: Windows 7 USB/DVD Download Tool Help

    Direct link to the download: http://images2.store.microsoft.com/p...B-DVD-tool.exe

    Instruction on how to do it (tho its very very simplez) are on the page of the first link

    Cheers

  15. #30

    Join Date
    Jan 2011
    Location
    Anderson
    Posts
    35
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    I continue to appreciate all the help and suggestions but I am not trying to "install" Win7....I am working with a reference image.

    I began with saving the unattend file with the name "Autounattend.xml". The name appeared to make no difference as some resources referred to it as the autounattend, others as imageunattend, and still others as just unattend. Regardless of the name I use, WDS moves the unattend file to a location of it's choosing and renames it when it is assigned to the image through the image properties.

    I will give the older WinXP $OEM$ format a go and see what that does.

    So far my testing shows parts of both unattends are being applied while parts of both are not. The WDSunattend is naming the drive but not adding the computer to the domain or prompting for our naming convention for the computer name. The imageunattend is handling the EULA correctly and the time zone correctly, but not the Network type (Home, Work), not adding the CD Key, or the administrator password. If I remove the imageunattend, the WDSunattend works as expected....and the computer reboots with all prompts (time, EULA, etc.)

    I feel as though there is some WDS setting or setting on the reference computer itself that is set up incorrectly or not at all. Since the unattend is being copied from the WDS server to the computer during imaging, I feel something is failing to "tell" the imaging process to apply the unattend file completely.......or there is confusion between the two unattends.

    Again, thanks for all the time, help, and suggestions. It is GREATLY appreciated.



SHARE:
+ Post New Thread
Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. [MDT] unattend.xml
    By garethedmondson in forum O/S Deployment
    Replies: 8
    Last Post: 28th November 2011, 03:38 PM
  2. windows 7 WDS unattend.xml files not working!
    By staylor1972 in forum O/S Deployment
    Replies: 11
    Last Post: 15th February 2011, 12:01 PM
  3. [SCCM 2007] Windows 7 unattend.xml help
    By ptotham in forum O/S Deployment
    Replies: 1
    Last Post: 21st September 2010, 01:13 PM
  4. Replies: 1
    Last Post: 19th August 2010, 01:24 PM
  5. [WDS] Win 7 unattend.xml help
    By Ste_Harve in forum O/S Deployment
    Replies: 5
    Last Post: 1st February 2010, 02:51 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •