O/S Deployment Thread, Confusion over how wim file installs.... in Technical; I've been testing win7 with a view to getting ahead of the game so that we can start rolling out ...
6th April 2011, 10:50 AM #1
Confusion over how wim file installs....
I've been testing win7 with a view to getting ahead of the game so that we can start rolling out machines from september 2011.
Policy and software testing is now completed and I have been looking at deployment.
I started small and have worked out how to create a custom install image which is on a bootable USB pen drive. With the help of users on here I successfully injected newer drivers for network card and audio for a motherboard of newer type than the one which I used for my base image.
Yesterday I installed WDS on one of our member 2003 SP2 servers and that went OK.
I copied my install.wim from my USB pen drive up to the WDS server by choosing the "Add Install image" (around 8Gb)
I copied my boot.wim from my USB pen drive up to the WDS server by choosing the "Add Boot image" (around 140Mb)
When I created my custom image it was with an unattend.xml.
Here it is:
<?xml version="1.0" encoding="utf-8"?>
<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">
<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">
<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">
<TimeZone>GMT Standard Time</TimeZone>
<CommandLine>cmd /c del c:\windows\panther\unattend.xml</CommandLine>
<cpifflineImage cpi:source="wim:d:/sources/install.wim#Windows 7 Professional" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
I took a test PC and made it PXE boot F12.
It finds the WDS server and I change the Locale and Keyboard to UK from US.
It then asks me to login to connect to the WDS server so I enter admin username and password.
I choose my image (it's the only one listed)
I choose my partition for install (advanced then format before proceeding)
It then starts to intall Windows
Reboots and installs devices.
Reboots again and starts windows.
I then have to choose the correct Country, Time & Keyboard layout.
I get CTRL+ALT+DEL
Strangely this PC is now on the network with name "Admin4" and it's in the Generic "Computers OU"
Why? Where did "Admin4" come from?
How do I just get it to boot up with a generic name so I can rename manually and add to the domain?
(Sorry for long post)
IDG Tech News
6th April 2011, 10:53 AM #2
What was the name of the PC that you imaged?
6th April 2011, 11:39 AM #3
blimey - cant remember
I've just PXE booted another test PC and this one joins the domain with the name ADMIN5 so at least it's not giving the same name each time.
It's not really a problem I guess - I just have to remove them from the domain, rename and rejoin, but it would be nice to know why it's doing this.
6th April 2011, 11:49 AM #4
The properties of the WDS server "Directory Services" Tab state the naming convention to be : %61Username%#
And the client account location is set too.
Does nt seem to be an option to NOT join AD.
6th April 2011, 11:57 AM #5
To associate an image unattend file
1.Create an Unattend.xml file
2.Save Unattend. xml files. Save Unattend.xml files to any location, and then associate the file with an image. To do this, open the MMC snap-in, right-click the image that you want to associate with the unattend file, and then click Properties. On the General tab, click Allow image to install in unattend mode, click Select File, browse to select the unattend file, and then click OK twice. The Unattend.xml file will be saved to the following location: \RemoteInstall\Images\<imagegroup>\<imagename>\Una ttend\ImageUnattend.xml.
Will give it a try....
6th April 2011, 12:30 PM #6
That's done the trick
6th April 2011, 12:31 PM #7
If you dont have a pre-staged computer account for the pc, then it will use a naming policy. If this is not configured then it will use a automatic naming policy. This is what your are experiencing.
"The automatic naming policy is based on the user's name and adds an incremental number to ensure that the computer name is unique. The settings on this tab will be applied when using the Pending Devices policy to create a computer account and when using the Windows Deployment Services client to create a computer account."
Last edited by sukh; 6th April 2011 at 12:33 PM.
By vasto in forum O/S Deployment
Last Post: 3rd November 2010, 04:16 PM
By Bluetooth in forum O/S Deployment
Last Post: 7th October 2010, 03:26 PM
By dezt in forum O/S Deployment
Last Post: 23rd June 2010, 11:28 AM
By garethedmondson in forum O/S Deployment
Last Post: 28th September 2009, 01:30 PM
By philjones2000 in forum Windows
Last Post: 30th August 2007, 11:52 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)