WDS Client:

How to Resolve.
An error message dialog is displayed in client side , "WdsClient:
An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment."
Ananda

Just to add -
The image machine i setup was Virtual
When i try to deploy the image to a virtual machine it works fine.
Am only getting the above error when deploying to a Physical PC
If I do Shift and F10 when the error appears, i get a Command prompt. If i do ipconfig i just get back
Windows IP Configuration
Nothing else
i am unable to ping anything on the network
I also enabled client logging and opened setuperr.log on the client, i am seeing this error:
2015-02-15 17:51:54, Error [0x0b003e] WDS QueryAdapterStatus: no adapters found.[gle=0x000000cb]
2015-02-15 17:51:54, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
The setupact file goes all the way through then has these errors:
2015-02-15 17:51:54, Error [0x0b003e] WDS QueryAdapterStatus: no adapters found.[gle=0x000000cb]
2015-02-15 17:51:54, Info WDS Spent 0ms confirming network initialization; status 0x80004005
2015-02-15 17:51:54, Info WDS WaitForNetworkToInitialize failed; ignoring error
2015-02-15 17:51:54, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2015-02-15 17:51:54, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2015-02-15 17:51:54, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network
segment.]

Similar Messages

Unattended wds client setup - language/locale page is still displayed

Hi
I am running WDS in Windows Server 2008 R2. I have created an WDS Client answer file to automated first screen (UI Language/Locale page) and disk partitioning. However, I still get the first UI Language/Locale selection page. automated disk configuration
works just fine.
I have further noticed that if I include <Login> section and automated user/password/domain portion, it doesn't display UI Language/Local page!
I just want to see the Login page and Image selection page.
Here is a copy of my current wdsClientUnattend.xml file:
<?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="amd64">
<WindowsDeploymentServices>
<ImageSelection>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition>
<Order>1</Order>
<Type>Primary</Type>
<extend>true</extend>
</CreatePartition>
</CreatePartitions>
</Disk>
</DiskConfiguration>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" 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>
</unattend>
Thanks in advance!
uc
cheers..uc

Thanks for the reply Dale.
My requirement is to hide the "Locale/keyboard input method" selection screen and disk partitioning screen.
I removed ImageSelection section as you mentioned however, I still get "Locale/Keyboard input method" selection page.
Here is the modified file:
<?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="amd64">
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition>

<Order>1</Order>
<Type>Primary</Type>
<extend>true</extend>
</CreatePartition>
</CreatePartitions>
</Disk>
</DiskConfiguration>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" 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>
<UserLocale>EN-US</UserLocale>
<SystemLocale>EN-US</SystemLocale>
<UILanguage>EN-US</UILanguage>
<InputLocale>0409:00000409</InputLocale>
</component>
</settings>
</unattend>
Not sure what is wrong here.
cheers..uc

WDS Client Naming Policy with image unattend mode problem

I have created a standard Windows 7 Pro 64-bit PC for my company with all our applications installed and configured. I used SYSPREP to generalize it and then used PXEBoot to capture this image to our WDS Server (which is the PDC). I used WAIK
to create the two required answer files, one for the WDS server and the PXE boot stage of deployment and another linked to the image that sets the region/keyboard/time zone and other simple settings.
To test I've setup up Oracle VirtualBox and PXE booted it. The PXE part works fine and the correct image begins to deploy. However when using the image's answer file I get a random computer name generated and it fails to join the domain, when I
don't use the image answer file I have to sit at the PC and set the region/keyboard/timezone etc settings from prompts on the screen but the virtual PC does join the domain and does pick up the correct name!
The AD DS properties tab shows this as 'Client Naming Policy' FBCLIENT%02# which is correct and results in PCs called FBCLIENT01 FBCLIENT02 etc when NOT using the image answer file.
How can I modify my image answer file so that the PC is joined to the domain and picks up the correct generated name in sequence?
Here's my image answer file...
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" 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>*</ComputerName>
<ProductKey>JXTG8-4MY4D-TXJQB-M492H-J4G77</ProductKey>
<RegisteredOrganization>Fiona Bruce LLP</RegisteredOrganization>
<RegisteredOwner>Fiona Bruce LLP</RegisteredOwner>
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>GMT Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" 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>fionabruce</Domain>
<Password>**REMOVED**</Password>
<Username>**Admin_User**</Username>
</Credentials>
<JoinDomain>fionabruce.local</JoinDomain>
<UnsecureJoin>true</UnsecureJoin>
</Identification>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" 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>Enable local admin</Description>
<Order>1</Order>
<Path>net user LocalAdmin /active>yes</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" 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>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" 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-GB</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" 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>false</HideEULAPage>
<HideWirelessSetupInOOBE>false</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>QQBkAG0AaQBuADIAMAAxADQAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Admin</Description>
<DisplayName>LocalAdmin</DisplayName>
<Group>Administrators</Group>
<Name>LocalAdmin</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<AutoLogon>
<Password>
<Value>QQBkAG0AaQBuADIAMAAxADQAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>2</LogonCount>
<Username>LocalAdmin</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk JXTG8-4MY4D-TXJQB-M492H-J4G77</CommandLine>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://fbserver01/masters/autoinstall/win7pro64bit.wim#Win7Pro64Bit" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Phil Tyler

Guys i have similar problem
but i wont the name of the machines to be chosen from the "CLIENT NAMING POLICY" in WDS
I have tried the below:
i know that <ComputerName>*</ComputerName>
gives random names
and <ComputerName>%MACHINENAME%</ComputerName> gives the names of the machine already
prestaged in AD.
and if i dont put computername Tag at all in the XML file, it will prompt me to enter the computer name,
and after the deployment the computer is loosing trust relationship with the DC
can someone helps please, its kind of urgent

WDS Client Initializing Problem

I am installing Windows 8.1 using WDS. But on client I get this error:
WdsClient: There was a problem initializing WDS Mode.
Here is setuperr.log:
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2014-08-27 11:45:22, Error [0x0b0003] WDS CallBack_WdsClient_DetectWdsMode: Reading server name and IP Address failed. Error [0x8007000D]
I can ping WDS server by FQDN or IP on the client. Also there is only one NIC on the client.
How do I solve it?

Hi
Have you installed WDS on a DHCP server or on a different. If on different server have you checked if you have port 66 and 67 configured.
Also once you are in WDS PXE mode you can press Shift+F10 and type wpeutil initializenetwork to intilize the network card.
Thanks

WDS Client throwing error 0x80070570 every time it trying to deploy OS.

HI
I have WDS and DHCP on subnet A and Clients on Subnet B. DHCP has server options of 66 set to wds server IP Address and 67 set to \boot\x64\wdsnbp.com. I have not setup option 60.
When i try to boot a client from WDS it get ip address and starts to format but in midway when it says expanding windows files it throws up error 0x80070570 and installation fails. I have tried to re import the image and also deleted the image group and
recreated it. Still have this issue.
Any help would be appreciated.

Hi,
Actually, that would be a different question and really out of the forum. Just some explaination here:
DHCP protocol is used during the communications between client and WDS server. But as we know, we cannot receive a DHCP broadcast from another subnet or VLAN by default. So we need IP helper here to forward DHCP broadcast.
About the setting you can need refer to network device manufacture. Since you have two subnets, there must be a router or switch. Another workaround is just to put WDS and DHCP server into the same subnet with the clients.

WDS - Client Configuration Help

Hi All,
I have many ap1252ap's, I have configured WDS on the one ap and it authenticate to itself OK - to the locally configured radius server.
state = wlccp_ap_st_registered
The problem is that I do not know where to go from here.
I have followed the docs (Fast Roaming, WDS) but I cannot get very far, in fact I do not think that my clients are even attempting to authenticate with my AP. I have modified the following taken from the sraom doc,
AP# configure terminal
AP(config)# dot11 ssid fastroam
AP(config-ssid)# authentication network-eap eap_methods
SSID CONFIG WARNING: [fastroam]: If radio clients are using EAP-FAST, AUTH OPEN with EAP should also be configured.
AP(config-ssid)# authentication key-management cckm
AP(config-ssid)# exit
AP(config)# interface dot11radio0
AP(config-if)# encryption mode ciphers ckip-cmic
AP(config-if)# ssid fastroam
AP(config-if)# exit
AP(config)# end
But something is still not right or missing. I have added users (or at least I think I have from an authentication point of view) with the username and password as the MAC of the clients to the local radius server, using command
ap(config-radsrv)#user xxx password xxx
But i do not understand how this links in with the client, basically how do I configure a client to attach using cckm, where do i put in a username and password for the network profile, if i pick leap, then I am prompted for the username/password, but what username/password is this, is it the username/password entered with
ap(config-radsrv)#user xxx password xxx
Any help would be much appreciated.
Regards

Hi,
Thankyou for reading my Post, I have managed to work out how to configure my WDS with usernames and passwords, if anybody else is interested, this is what I did.
dot11 ssid fastroam
authentication open eap method_clients
authentication network-eap method_clients
authentication key-management wpa
(method_client is basically a list pointing with IP of server providing WDS/Radius)
Interface dot11radio 0
ssid fastroam
encryption mode ciphers tkip
no shut
To configure user/passowords
conf t
radius local-server
user testing password testing123
then on client
athentication:
configure LEAP
user: testing
password: testing123
encryption:
tkip
the client should now authenticate to AP/WDS.
The only thing I have not worked out yet is how to configure a backup WDS. nor do I quite understand which of the authentication methods the client is using when it succesfully connects.
Please can you advise: When you have a username/password on the radius server, does it mean that any/or all clients can use the same username/password.
or will the radius server detect that the login is already is use and prevent another attempt. reason behind my question is that if the username/password gets into the wrong hands.
Thanks and Regards

WDS Client error

Hi there,
We have been using WDS to roll out some J2-580 EPOS terminals which has been going great for us. We have now started to roll out another model J2-630 and have found that i get the following errors.
I am using the 32 bit windows 2008 server with WDS, the boot image is from the same server CD.
What is happening is the initial load takes place but when trying to load the setup.exe I get this error:-
WDSClient: An error has occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment.
Things I have tried so far:-
Added the Network card driver to boot image - this gave the same result.
Removed the setup.exe from the boot image to see what state things are in and found that I get the following error when running ipconfig:-
An error occurred while releasing interface loopback Pseudo-Interface 1: The system cannot find the file specified. The operation failed as no adapter is in the state permissible for this operation.
I am about to setup a discovery image and see what happens with that so will let you know, but if any one has any advice if the they have come across this before it would be greatly appreicated, many thanks.

this is an driver issue. look you are adding the same drivers to J2-580 to j2-630.
take the drivers DVD that came with the J2-630
copy the drivers into a shared folder
make a new group and add the drivers from that folder into that group.
note: the group should be separate, don't mix
it with other drivers.
then add the new boot and installation images . remember which is new and old.
now right click on the j2-630 boot image and click add drivers to the boot image
and in attributes, remove everything other than the architecture attribute value which will be
(x86 or x64)
then add new attribute which will be driver group name which should be the one which you added now.
let the drivers be added to the boot image and then restart the machine/ server and try wds. i am sure this will work

WDS clients not joining the domain

Hi all
Recently set up a 2012R2 server in our domain as a WDS server. After syspreping Win7 x64 with an unattend file and capturing images the machines just don't want to join the domain, after windows install it gets to the "Applying system settings"
and hangs for 15 minutes (while i assume it tried to join the domain) then eventually restarts but with no domain join, everything else in the unattend file works fine bar the domain join. I've tried with secure join and unsecure join but none work. Using
no unattend file the domain join works fine.
I've searched every forum and tried various methods to get this working but still no joy.
Can anyone suggest anything?
Thanks

HI ,
please read this link :
https://technet.microsoft.com/en-us/library/cc730845%28v=ws.10%29.aspx
You have the option to add the domain computer using unattend file
My Website:www.Pelegit.co.il Mcitp /Mcsa 2012

WDS Client Permissions

I have created WDS server and it is up and running.
I have two install images which contain Windows 7 and Windows 8. Also, I have created two users in AD, call X1 and X2.
My question is, Can X1 or X2 get access to run only one install image.? They should not get access to run the both install images. Each one could access to run only one install image.

We must create a Windows 7 image group and a Windows 8 image group. Thereafter, you give different permissions on groups.

Maximun WDS Clients

Hi,
I've read in some Cisco document that you should not have more than 30 APs in the same WDS domain. I have over 100 APs in a campus wide installation that are all on the same management (native) vlan. So they are all in the same IP subnet. What's the best way to activate WDS on these APs?
Thanks

I agree with you that the concept is not well defined. I think I've read all the documentations available about WDS and still have found more questions then answers. All paper from cisco always refer to the WDS documentations for more details but there I'm still searching it. I would realy like to have an in depth technical coverage of WDS.
I'm using LEAP so the FastRooming feature of WDS should help in my case but, for me, the main reason to use it is to enable the Radio Management feature of WLSE.
I'm still concerned about the fact of having a lots of APs on the same segment (VLANs) with WDS enabled.
Thanks anyway for your thoughts.
Merci et Bonne Journée aussi.
Michel

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

# of APs per WDS?

Hello, we are in the process of starting to implement WDS and have well over 100 access points. I've read 2 different docs from Cisco, 1 saying that the max # of APs in each WDS should be 30 and another document saying 100. Does anyone have any suggestions/experience with how many APs in a WDS?
FYI, I'm planning on using an AP WDS if that matters and need to figure out how many APs I need to sacrifice to get this running.
thanks

I read the exact same thing in the setup for WDS, then in the new update for WLSE 2.7.1, it says
"Note A WDS AP can handle up to 100 APs in the same subnet if it is not handling radio traffic (a "dedicated WDS"). This requirement ensures that the AP has enough processing power to effectively handle roaming."
So that is where my confusion started.
I have close to 100 access points in one VLAN, so you are saying that I need to split them up in order to utilize WDS and have them all as WDS clients?

WDS: How to replace or remove a device GUID?

We have a number of computers that are registered in WDS so they are auto-named when imaged. Though, as they age I am having to move hardware around to rapidly fix failed power supplies, etc.
I've run into a problem, trying to reuse a computer that was used somewhere else, where it previously had its GUID registered, but now I need to assign its GUID to a different computer name in Active Directory, and I am not allowed to do it:
wdsutil /set-device /device:EL900-MUSIC-D /id:4C4C4544-0032-3010-8053-C2C04F354A31
WDSUTIL has detected duplicate GUIDs in Active Directory. The duplicate computers are:
Name: E205-SB
DN: CN=E205-SB,OU=Computers - EL Staff,DC=XXXX,DC=YYYYY,DC=ZZZZZZ
MAC/GUID: 44454C4C320010308053C2C04F354A31
Referral server:
Boot program:
WDS client unattend file:
Boot image path:
Join domain: Yes
An error occurred while trying to execute the command.
Error Code: 0xC1040134
Error Description: A computer with the same GUID already exists.
Looking through the commands for wdsutil, it is very odd because there is only a "/set-device" command. There is no "/replace-device" or "/replace-GUID" or "/delete-device" or "/delete-GUID" commands.
So how do I remove or replace the GUID in the conflicting AD Computer object, without completely deleting the Computer object and rejoining the other machine to the domain?

Hi,
The article described the reason that cause duplicate GUID and how to remove duplicate GUID:
Managing Duplicate Microsoft Systems Management Server Unique Identifiers
http://technet.microsoft.com/en-us/library/cc917513.aspx
Hope this helps.

So how to specify different answer file for different install images in WDS snap-in?

hello
in WDS snap-in, in properties on server name, on client tab, we can define an answer file for unattended windows installation on WDS clients.
my question is, maybe we have added multiple images in WDS snap-in (win xp image, win 7 , win 2008,...)
now this one answer file applies to all of them ?
so how to specify different answer file for different install images in WDS snap-in?
thanks in advanced

Under the "Client" tab of WDS, you should only use an answer-file with settings relevant for the installation. This would be credentials for the WDS deployment share, international settings used during the setup and possibly also destination drive
details (if you want the installation to take care of partitioning the disk etc). The settings relevant for unattend-files used under "Client" would only be of those in phase 1 (WinPE).
However, if you would like to have specific unattend file for every installation, e.g. Win7, Server 2008, Win 8 etc, you can browse to the image under "Install Images" under the image Groups. There you can select properties for every image and
have a personal unattend-file.
hi Joel
very cool. thanks a lot, that really helped me.
best regards

WAP4410N stops accepting wireless clients

I have two WAP4410N. One of he accesspoints is connected to our wired LAN, called by now AP1. The other accesspoint is connected to the first accesspoint by WDS (Client mode) called now by AP2. I have upgraded both accesspoints to firmware 2.0.4.2. Both accesspoints are set to the same SSID and channel (6) and are set to mixed mode (B/G/N). After I two weeks they started to fail. When I connect to AP1 I don't reveive an IP-address of our DHCP server from our LAN. I'm able to connect to AP1 from our LAN. When I SSH to the box and I do an dmesg command, I see the following messages:
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
I'm still testing these devices and I hope I can use these devices in our production environment,which is not possible with these errors and outages.
I can't connect to AP2 right now. I think the whole wireless interface isn't working anymore, unless I power off/power on the box. But it's hard testing when it works ok for two weeks and then stops.
Message was edited by: Sander Cornelissen

After your advice I did a factory reset of both AP's. From 17 october until today it worked fine. Today it crashed and the connection to the device isn't usable.
In the dmesg, from the SSH console to the AP, I did notice the following text:
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Going to erase from sector 00000085 to 00000086..
erasing bf7e0000...
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
I have to power off and power on again to make the device work.

WDS Client:

Similar Messages

Maybe you are looking for