O/S Deployment Thread, Tips for beginners in Technical; Got a problem at the very begining saying: error code: 0xe0000102 And it doesnt go any further, anybody ever encountered ...
1. ## Re: WDS - Tips for beginners

Got a problem at the very begining saying:

error code: 0xe0000102

And it doesnt go any further, anybody ever encountered this?

Thanks

2. ## Re: WDS - Tips for beginners

Originally Posted by Andi
Oooh, I have both my DCs set to be a global catalogue server. Is that a bad thing?

General recommendations for FSMO placement
â€¢ Place the RID and PDC emulator roles on the same domain controller. It is also easier to keep track of FSMO roles if you cluster them on fewer machines.

If the load on the primary FSMO load justifies a move, place the RID and primary domain controller emulator roles on separate domain controllers in the same domain and active directory site that are direct replication partners of each other.
â€¢ As a general rule, the infrastructure master should be located on a nonglobal catalog server that has a direct connection object to some global catalog in the forest, preferably in the same Active Directory site. Because the global catalog server holds a partial replica of every object in the forest, the infrastructure master, if placed on a global catalog server, will never update anything, because it does not contain any references to objects that it does not hold. Two exceptions to the "do not place the infrastructure master on a global catalog server" rule are: â€¢ Single domain forest:

In a forest that contains a single Active Directory domain, there are no phantoms, and so the infrastructure master has no work to do. The infrastructure master may be placed on any domain controller in the domain, regardless of whether that domain controller hosts the global catalog or not.
â€¢ Multidomain forest where every domain controller in a domain holds the global catalog:

If every domain controller in a domain that is part of a multidomain forest also hosts the global catalog, there are no phantoms or work for the infrastructure master to do. The infrastructure master may be put on any domain controller in that domain.

â€¢ At the forest level, the schema master and domain naming master roles should be placed on the same domain controller as they are rarely used and should be tightly controlled. Additionally, the domain naming master FSMO should also be a global catalog server. Certain operations that use the domain naming master, such as creating grand-child domains, will fail if this is not the case.

In a forest at the Forest Functional Level Windows Server 2003, you do not have to place the domain naming master on a global catalog.

Hope this helps.

3. ## Re: WDS - Tips for beginners

Hi

I'm new to WDS and I used this guide
to help me (excellent by the way)

I've come across a problem I've created to boot images fine,
syspreped client,
booted client up to network client finds WDS Server,
selected Boot image get to the wizard,
select volume to capture and name it,
On the image capture screen I've ticked upload image to WDS Server
in the box below that entered its name clicked connect.

I get a error "the network is not present or not started"

Any help would be appreicated :?

4. ## Re: WDS - Tips for beginners

As promised, how to add drivers to windows PE

First you need to install the windows Automated Installation Toolkit. This contains a couple of important programs you will need to edit the image, and add the drivers.

The Windows AIK can be downloaded from Microsoft here It is a big download, and you will need to burn it to a DVD to install it.

Once you have the AIK installed;

1. Locate the .wim file containing the windows PE image you want to add drivers to.

2. Create a local copy of this on the machine you're working on. If this is the server, then make an alturnate copy somewhere else on the server.

3. You need to mount the Windows PE image into a directory using the ImageX untility. this is installed as part of the AIK.

e.g imagex /mountrw C:\install.wim 1 C:\wim_mount

You can then use the PEIMG utility to add the driver into the windows PE image. You will need the drivers you want to add in another directory on your computer.

e.g peimg /inf=c:\drivers\intelpro1000\e1000325.inf c:\wim_mount\windows

This will install the specified driver into the windows PE image. The last step is to write these changed back to the WIM image, which you do by using the command;

imagex /unmount /commit C:\wim_mount

This will update the WIM file with the changes made. Then simply add it as a new boot image in WDS. I wouldn't recommend overwriting the existing boot image, incase the new one has problems.

I've written these instructions from some scribbled notes I took at the time I was preparing our images at the beginning of August, so apologies if there's in-accuracies in them. I'm sure that's it thou.

@rush_tech. Adding the correct network drivers into your boot image might solve your problem. However you can just create the .WIM file on the local hard drive and manually copy it to your WDS server after, you don't have to upload it straight to the WDS server.

However, you will still need to install the required network drivers into windows PE to download this image onto workstations.

5. ## Re: WDS - Tips for beginners

priceless maniac good man

6. ## Re: WDS - Tips for beginners

can you do this for the wds boot images as well?

7. ## Re: WDS - Tips for beginners

I use it primerily for putting the drivers into the boot image. I've not used it to add drivers to the actual workstation image, as these are all pre-installed into windows before I take the image.

Mike.

8. ## Re: WDS - Tips for beginners

@maniac It did occur after reading your post on how to add a driver to a .wim image ops: I'll give that a bash

Cheers

9. ## Re: WDS - Tips for beginners

update......Ive managed to get the network driver into the image ok but it was a xp network driver (this did'nt work) I'm using images that come with AIK. So its a vista boot image. I'm trying to image a Hp D530 on looking to download the vista driver from HP site It shows in the listing but there is no file so I guess I'll have to wait for the driver to be put back. stopped in my tracks

unless someone knows of a place i can download it other that hp site.

Oh I have also tried the driver from broadcoms site no luck.

10. ## Re: WDS - Tips for beginners

I've found XP drivers sometimes work with windows PE, and sometimes don't. The driver MUST be signed in order for it to work thou.

Some of our machines have broadcom drivers, and I don't to recall having any problems getting a working driver. Infact our HP 6310 laptops have a broadcom network card, and these worked without a hitch. B44win was the .inf file name, is this the one you've tried??

Mike.

11. ## Re: WDS - Tips for beginners

No its the one attached b57nd60x "see attached file"
Broadcom NetXtreme Gigabit i'm not sure if its signed or not :?

12. ## Re: WDS - Tips for beginners

Windows could not display the images available for installation

This is sometimes caused by using an oem boot.wim (from a Dell Vista CD in my case) rather than a Select or Genuine MS one. But fear not, we can fix this.

Assuming youâ€™re on a machine where the Windows Automated Install Kit is installed, grab a _fresh_ copy of boot.wim from OEMCD\Sources\boot.wim and copy it to the machine.

Open a command prompt (the AIK stuff is in the system path on my machine) and mount the boot.wim
Code:
mkdir E:\path\to\temporary\folder
imagex /mountrw e:\path\to\boot.wim 2 e:\path\to\temporary\folder
go into e:\path\to\temporary\folder\Sources and delete pid.txt

exit the path (cd \ ) and then unmount the image
Code:
imagex /unmount /commit e:\path\to\temp\folder
Then add the boot image to WDS in the usual way (and call it something descriptive).

13. ## Re: WDS - Tips for beginners

I've been using one image on my WDS server for a while now, but the time has come where I need to add a second image to the server.

My current image is fully unattended and uses a autounattend.xml to do all the tricks. The trouble I have is that the unattended file is on the main server config. If I try to attach it to the image itself I get a "This image version doesn't support adding an unattended setup file using this method" error.

This means that to use the other image, I have to tell the server which .xml to look at BEFORE I start to build those machines.

I'd like to be able to have multiple images, all with Unattended files which can be selected from the workstation via te PE Image Selection (which I have yet to see!) not the server.

Any ideas what I need to change?

14. ## Re: WDS - Tips for beginners

Hello All,

Just started playing with WDS and am testing image rollout however I have a problem the laptops I want to image have 4 partitions on them and I want to have wds wipe these and create a single drive spanning the whole size of the disk.

I am using an WDSClientunattend.xml file to perform certain unattended functions and have set it to wipe the drive but it just does not do it.

Anyone done this successfully or got any ideas??

My .xml file:

<?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">
<DiskConfiguration>
<WillShowUI>Never</WillShowUI>
<Disk>
<CreatePartitions>
<CreatePartition>
<Order>1</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<ModifyPartitions>
<ModifyPartition>
<Active>true</Active>
<Extend>False</Extend>
<Format>NTFS</Format>
<Label>SYSTEM</Label>
<Letter>C</Letter>
<PartitionID>1</PartitionID>
<Order>1</Order>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
<WindowsDeploymentServices>
<Credentials>
<Domain>JKHS-PD</Domain>
</Credentials>
</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-UK</UILanguage>
</SetupUILanguage>
<InputLocale>0809:00000809</InputLocale>
<SystemLocale>en-UK</SystemLocale>
<UILanguage>en-UK</UILanguage>
<UserLocale>en-UK</UserLocale>
</component>
</settings>
<cpifflineImage cpi:source="wim://srv001/distribution\$/operating%20systems/windows%20vista%20enterprise%20x86/sources/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

15. ## Re: WDS - Tips for beginners

Getting this part of my WDS system working was a pain. Problem is if you get any of the commands in the wrong order, then it seems to ignore the entire section, but it doesn't actually tell you it's doing that.

This is my unatend.xml file which does exactly what you are aiming for. We use it on our system. See if it works for you.

Code:
<?xml version="1.0" ?>
- <unattend xmlns="urn:schemas-microsoft-com:unattend">
- <settings pass="windowsPE">
- <component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
- <WindowsDeploymentServices>
<WillShowUI>OnError</WillShowUI>
- <Credentials>
<Domain>DOMAINHERE</Domain>
</Credentials>
- <ImageSelection>
<WillShowUI>OnError</WillShowUI>
- <InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
- <DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
- <Disk>
<DiskID>0</DiskID>
- <CreatePartitions>
- <CreatePartition>
<Extend>true</Extend>
<Order>1</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<WillWipeDisk>True</WillWipeDisk>
- <ModifyPartitions>
- <ModifyPartition>
<Order>1</Order>
<PartitionID>1</PartitionID>
<Letter>C</Letter>
<Label>NBC</Label>
<Format>NTFS</Format>
<Active>true</Active>
<Extend>false</Extend>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
</component>
- <component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
- <SetupUILanguage>
<WillShowUI>OnError</WillShowUI>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<UILanguage>en-US</UILanguage>
</component>
</settings>
</unattend>
I think the ordering is a bit different on mine compared to your's, this may be the problem. Took me days to get it working properly.

Mike

16. ## Thanks to maniac from:

box_l (21st November 2008)

SHARE:
Page 4 of 10 First 12345678 ... Last