WDS + HD

Hi,
I wonder if anyone can confirm that this works?
Internet --> AirPort Extreme --(WDS)-->AirPort Extreme
To the second Extreme I will be connecting three computers and what I wonder is does the USB Port work for HD's in WDS, I know that it works for printers but not sure about for Harddrives.
Thanks adamsen

Yes

Similar Messages

Unable to WDS install Win 8.1 VM on Hyper-V 2012 R2

Hi.
We've recently gone from Server 2008 R2 (Data Center) to Windows 2012 R2 (Data Center) and we're now trying to install Windows 8.1 clients on our Hyper-V solution.
When using the virtual machine creation wizard I create two test machines.
One machine is a gen1 and one machine is gen2 both are set to install via network (MDT 2013) and both a given a 40GB disk and 4GB of ram. Both installations fail.
"Windows setup could not configure windows to run on this computer's hardware".
According to everything I've found on the web this could happen if you try and install Windows 7 - something to do with 4K disks I think. This shouldn't happen on Windows 8.x.
I've seen a few posts where they explain the IDE controller being unable to handle 4K disks so that might explain something but in my case I also have a gen2 machine where disk is attached to a SCSI controller.
As I understand it a server 2012 R2 with Hyper-V should be able to have a Windows 8.1 installed on a VHDX file on a SCSI controller.
Can anyone help out here?
Thank you!

According to the web setup.exe /quiet /norestart should be valid parameters for the components.
What I mean by Applicaton Install is that there's a part of a Deployment Share where you can choose to install applications. A Task which will run at a appropriate time, e.g. Office is installed into our base image at that time. I tried including the Integration
Components before the Office install creating a base image with Office 2013 and the IC.
I also tried to use the base image a create a task for VMs only where no driver what so ever gets installed - it simply installs the base image created and activates Windows and nothing more. That doesn't work either.
The problem in a nutshell is this:
I want to install via MDT/WDS. I don't care if it's a regular machine or a virtual one. Both should work.
I've created several base images (Win7_x86, Win7_x64, Win8_x64 etc.) with Office included and everything has worked fine except when I try and install Windows 8 as a VM.
I must say that I've tweaked around and tried a few things while trying to find the problem so I probably have to test some things again to make sure what I say goes but we've installed both Win7 & Win8 on regular machines without problems but I can't
seem to install a Windows 8 machine via MDT/WDS for some reason as a VM - only on regular PCs.
As tested above installing via ISO works fine and creating a new image didn't help either.
The way I capture an OS is by simply write DoCapture=YES in my Deployment Share Rules section and boot into that Deployment Share (then I get a menu where I can choose to capture the machine and it simply installs the imported Windows ISO via a Standard
Client Task Sequence (where it also installs Office - there's an Application Install section part of the Standard Client Task Sequence).
So really really short; the image I try to install works fine on a regular PC but won't install on Hyper-V.

Unable to get Airport Express to extend Time Capsule via WDS

Hi all,
I have a Time Capsule that's a couple years old, and recently decided to try to extend its network given that we recently did a lot of re-arranging things in our home. I followed the instructions posted here for using version 5.5.2 of the Airport Utility but I'm not having any luck... I've triple-checked that the SSID, security settings, etc. are identical between the two devices. I set the Time Capsule as the main WDS device and entered the airport ID of the Airport Express into it, and set the Airport Express as the remote WDS device and put the airport ID of the Time Capsule there. As far as I can tell I've got all the settings correct.
What really confuses me is that I can get the two devices so that the Time Capsules status light is green but the Airport Extreme's status light is yellow. The Time Capsule reports that WDS is functioning properly but the Airport Extreme is unable to connect to the WDS network. I have the two devices only about 5 feet from each other so signal strength certainly shouldn't be an issue.
Any ideas what's going on?
Thanks,
-Bruce

I would not use WDS unless your AEX is so old that is all it supports. Much easier to configure the TC to allow the network to be extended under the Wireless tab. Then configure the AEX's Wireless Mode to Extend Existing Network from the dropdown menu.

The Difference between Extending a Wireless network and WDS?

I have an Extreme (n) and an Express (n).
I want to make sure the signal is strong upstairs and share a printer (connected to the express) and use AirTunes. I also may add an external drive to the Extreme.
What's the difference between Extending a Wireless Network and using WDS? Will there be a speed difference?
Message was edited by: J. Christopher Edwards

I think you don't get it
If I have another draft N router that operates at 2.4G and I have only n devices I can still use WDS and it will connect using draft n in the 2.4G band.
If one g device connects to the network will go in mixed mode.
The AEBS will still report 130 Mbps for your n clients and 54 for your g clients.
If the other router is g only obviously you can't connect between the two router at n mode but still the AEBS will be in mixed mode and not in g. The Extreme will still report 130 Mbps for the connected n clients.
I can tell you that because I have actually implemented it am not taking off the documentation.
The same device if I try to use the "extend n network" does not even see the AEBS but will happily keep the n in the WDS mode and though the bandwidth is halved it is still more than g.
In any case enough for this!

WDS and Surface Pro 2

I have a Windows Deployment Server and I am using Windows ADK to load essential drivers onto my boot/install images.
I downloaded the latest Surface Pro 2 driver pack and used DISM to load drivers on to an offline boot image from a Windows 8.1 ISO. I then un-mount the image and load it onto my WDS server.
My problem is the Surface Pro 2 won't pxe boot into my Windows Deployment Server. When I PXE boot, it displays media present and then waits for user input to start PXE over IPv4. I press enter but it times out and then prompts for IPv6 (no error given) when
that times out it boots the machine into windows.
I had been successfully imaging Surface Pro tablets from this deployment server using the same methods, but we recently got in the Surface Pro 2 and I haven't been able to get it working.
I have the latest version of MDT installed but I'm not that familiar with it. When we first started deploying tablets I had attempted to create boot wims with MDT but I never got it working and decided just to use the WADK and DISM.
Any ideas on what I could try next?

I am running WDS on Windows server 2008 R2.
I am using a Type Cover 2 from Microsoft.
I am using the Microsoft Surface Ethernet Adapter. I loaded the drivers for the adapter into the boot image as well as the other drivers from the February driver pack.
Thank you for your response.

XP with AirPort Express and WDS ... works brilliant!!! Read how to ...

I have worked out an interesting setup which uses max. power of AE with my 3Com Router, Dell and Denon AVR-4306.
It took some hours of testing and finding the right configs, which was a pain in my brain. But now: YEEEHAAA!
My home setup is:
- AirPort Express 6.3
- 3Com OfficeConnect Model 3CRWDR100B-72
IMPORTANT: IT SUPPORTS WDS!!!
- Dell Inspiron 9300 with WLAN
- Epson Stylus Color 740
- DENON AVR-4306 [Receiver with Ethernet connection]
Till yesterday I used AE as a client which turns off the ethernet port. And I had a router without WDS support. AND: I had those audio drop outs which made no fun.
The new configuration at the end is not such complicated.
AE is connected by WDS to my router, by Toslink and ethernet cable to my receiver. A printer by USB of course.
Now I am able to:
- WLAN stream AAC by Dell with AirTunes through AE to my receiver
- WLAN printing
- WLAN config of my receiver and internet radio streaming
- write that posting by WLAN and DSL ... STRIKE!
AND THE BEST: NO AUDIO DROP OUTS ANYMORE!!!
The configuration:
I will not discribe the WLAN setup between my Dell and 3Com in all details because this should be a basic knowledge.
First I configure router and Dell with WEP. I didn't test WPA with WDS yet. I set the router to my ISP settings to get connection to DSL. The router config by webbrowser is not complex. This is done by the shipped manual. DHCP turned on etc..
Next step I will setup my DELL for WLAN connection to the router. My router eg. just uses WEP HEX. I can use a ASCII passphrase but this will be converted to HEX. What's now important: I had to use HEX also for DELL WLAN config and AE WITHOUT "$" before the key what's often discribed in the web. Otherwise AE config will give an error message and ASCII will prevent connection by WEP. I set my DELL to IP by DHCP. I use the same ISSD of the router and set WEP. The first setup was done by ethernet cable which is discribed in my manual. After all steps I turned off LAN and am able to connect to WLAN DSL.
Now the important part:
I configured the router after config and restart of AE again. The router MUST SUPPORT WDS!!! Otherwise my config will not work. In my 3Com config I turn on WDS and scan for AE when it is set up right. This will grab the right MAC address automatically. But it's also possible to set the AE MAC manually and then:
I will do a AE reset by holding down the reset button till the yellow light flashes fast. This will set the AE to basic settings. After a while you will recognize the AE's factory name in your WLAN network list on your PC where you also see your router WLAN connection.
Now drop the router connection by connecting to AE which is unprotected.
Open the AirPort Admin Utility.
Choose the factory AE name.
Open the config.
Change the password of your AE which is basic "public" to the SAME of your router.
Choose „AirPort“ and set „Wireless Mode“ to „Create a Wireless Network“.
Eg. I use for „Network Name“: „DELL9300“ which matches with the SSID of the router.
Set „Channel“ to „1“ [it seems most robust here].
Set „Wireless Security“ with WEP. In my case I have to use the router's HEX key.
On page „Internet“ set „Connect using“ to „AirPort (WDS)“.
The „MAC Address“ MUST be the MAC address of the WLAN router, BUT THE WLAN ADDRESS ... NOT LAN ADDRESS!!!
[this was one trap and time killer because I just tried to use the printed MAC address on my routers label which is WRONG because there's a WLAN MAC ADDRESS I found by accident in my router's config overview]
Activate „Also allow wireless client computers“.
I use a static IP:
IP 192.168.1.200
Subnet 255.255.255.0
Router 192.168.1.1
DNS 192.168.1.1
On page “Network” activate “Distribute IP addresses”.
On page „WDS“ set to „remote base station“.
Activate „Allow wireless client computers“.
You will recognize here that the WLAN MAC address was copied automatically.
On page "Music" activate AirTunes and define a name. In my case "DENON".
Save the config to harddrive and then save it to AE.
AE will restart automatically.
NOW PRAY! If everything is done right you will reconnect your PC to the router [automatically because AE is dropped or try manually] and after a while the AE lamp shows "green".
The full power of AE is unlocked and ... actually ... AirTunes still plays without drop outs. GREAT! This could also be router related or WDS works generally better than client mode.
president

The 802.11n AirPort Express Base Station (AXn) can be configured in a number of ways when the topic is around extending.
If you just want to support wired clients, you can configure the AXn as a wireless Ethernet bridge. In this configuration, the AXn would "join" an existing wireless network and share that connection via its Ethernet port.
The other option is to configure the AXn to extend another AirPort. In this configuration, the AXn would both extend the other AirPort's wireless range, but it would also have its Ethernet port enabled for wired clients.

WDS capture image on a Windows 2012 R2 server fails with a winload error

Hello,
I have been fighting with this problem for days now. I have to install
30 Win8.1 Pro PC's with WDS. The WDS service is running on a Win2012 R2
server. I added the Win 8.1 Pro boot and install images and created a capture image.
Now when I boot the reference computer I get a Boot Manager message saying that winload.exe is missing or corrupt. The original boot wim works
correctly.I removed and added the WDS role a couple of times, I tried the procedure with a 32 bit Win7 boot image, and that worked, But when I added the capture image created from the original Win8.1 boot.wim, that spoiled both capture images. I tried
the same thing with a Win2012 R2 Standard server after removing and adding the WDS role again, but the capture image generated the same error as above. .I see that since about mid-April many people has the same problem.Different solutions are suggested, but
none of them worked for me. One of them is to mount and unmount the capture image, that didn't help for me.
Any help is appreciated.
Thanks
Gabor

Do I understand correctly that if you deploy original wim file to your testPC1 it works all right, but if you deploy an image that you captured on buildPC to testPC1 then you get the winload.exe error ?
Are you formatting (deleting all the partitions) on testPC1 during the
deployment of captured image ? Can you check and confirm if the HDD seting for AHCI or IDE (yes, its still around) is the same option on both stations?

Please Help: old Airport Extreme, new Aiport Express, want to WDS

Hi,
I'm sorry if this topic has been covered before, but I can't seem to find a post with my exact situation. I have a G4 desktop (no Airport card) connected to an Airport Extreme Base Station (about 2 years old) which is connected to a 2wire DSL model. My wife and I have been able to use the wireless network in our house for a year or two now with our laptops (PowerBook and few month old MacBook Pro). We've been able to connect to the internet and can print to our laser printer with no problem. However our living room is just out of range (one bar and usually drops out) so I thought extending the range of the Base Station with an Airport Express would allow us better access from the place we hang out in the most.
After reading the very sketchy start up manual as well as trying various combinations of steps posted here, I am still having trouble setting this thing up. Simply plugging in the AX and using Airport Set Up Assistant, I was able to create a WDS and add the AX as a remote station by entering its MAC address (it was not recognized automatically). However, when pushing "update" a message came up saying the AX needed to be set up manually.
So, I realized maybe I needed to plug the ethernet cable directly into the AX and use the Aiport Assistant. I tried that once and nothing happened. Yellow light flashing. I tried it again adjusting a setting for "Join an existing network" and named the network the same as our already established network. The light turned green! So, not knowing what to do next (Hello, Apple! Please write better instructions) I crossed my fingers and unplugged the Ethernet cable and put it back in the existing Base Station. Did that. Still green! Then I had to move the AX from the office out into the hallway toward the living room. Cross fingers, unplugged AX and ran it down hallway. Plugged it in, wait for Yellow light, hey it turned green! I took the MacBook to the living room, turned it on, 4 bars, cool! Started Safari and.... nothing. No web page loaded. No email. Nada. Great looking bars, though.
So, frustrated, I unplugged the AX and just left it a day. Last night, I moved it back to the office and tried to see if I had a setting wrong. Create new network? Join existing network? Same or different channel as Base Station? Use password security on AX? on just the Base Station? both? Why doesn't the manual mention these things? I even tried soft reset and hard reset. I could never get the green light to come on again.
Does anytone know where I find simple step-by-step instructions to help me? I thought Apple was supposed to be "easy". Am I missing something? My G4 desktop does not have an Aiport card, so I can't configure both Stations without having the Ethernet cable plugged directly into either gadget.
Any help would be greatly appreciated. Thanks.
MacBook Pro Mac OS X (10.4.8) Airport Extreme, Airport Express, PowerBook, G4 Desktop

Yeah, Duane posted the link to the good directions. The directions given in the printed manual for the base station and the online help for the base station is inadequate when it comes to WDS set up.
I have an Airport Extreme and two Airport Express. When I was setting up WDS, it did take a while because certain errors did keep coming up. But eventually it worked. I now get the hang of it.
One difference that kept me really confused but now I understand is the difference between relay and remote base station.
Picture these two diagrams
A) Airport Extreme <--> Express1 <--> Express2
B) Airport Extreme <--> Express2
The <--> signs mean wireless connection.
In picture (A), the Extreme is broadcasting to Express1 which then relays the signal to Express2. In this case, Express1 is a relay base station and Express2 is a remote base station.
In picture (B), the Extreme is broadcasting to Express2. In this case, the Express2 is also a remote base station and not a relay. There is not relay base station in (B).
I don't know why that kept me so confused but once I got it, I got it. Hope this helps for your WDS set up.

New Airport Extreme N wireless network setup questions (WDS, D-Link)

I have finally been able to set up my Airport Extreme N network after numerous attempts over the last few weeks. I was getting a very weak signal in front of the house where my wife's G4 is connected wireless to an old Airport card and where all the systems (XBOX 360; Wii and PS3) are also wirelessly hitting the network.
The current configuration is as follows: In the office in the back of the house I have an Airport Extreme N basestation connected to the cable modem and have three workstations (One Mac and two PCs) wired to it. I set up a WDS network, so I set up the Airport Expresses as remotes. In the living room I have another Airport Extreme N basestation (as a remote as well) that is hooking up to the XBOX 360, Wii and PS3. I have enabled WEP security (not effecting the XBOX 360 since it is now "wired"). Here is the weird thing - I have a PC laptop with a D-Link Xtreme N card ( DWA-652) that cannot connect to the network. I enter the WEP password but it does not connect. Am I missing something on the basestation setup? Do I need to add the MAC address of the card anywhere. When I use the laptop's built in wireless it connects with no problem. By creating a WDS network did I disable the n functionality of the base station(s)? I am a lttle condused.
Also, prior to going to an all Apple wireless network setup, I bought the D-Link Xtreme N Gigabit Router (DIR-655). I was regretfully about to return it to Best Buy but I had an idea which may or may not work. I know that the D-Link does not support WDS but if I was to set it up as the main router and added the "main" Airport basestation as a wired bridge could I maintain the WDS network? The reason I ask this is because I would love to keep the gigabit for the wired machines in the office. Also, I am wondering if the D-Link notebook card is incompatible with the Airport network.
All I know is that I have spent alot of money and sleepless nights just trying to set this network up but thankfully Best Buy has a thirty day return policy so I will return what I can't use.
I appreciate any help and advice anyone can give me.
Thanks.
V
MacPro Mac OS X (10.4.9)
MacPro Mac OS X (10.4.9)

Hello!
I have noticed that some manufacturers (Linksys and possibly D-LINK) only accept upper-case WEP keys only.
This drove me nuts when trying to integrate a Linksys PC PCMCIA card into my old "g" network.
As far as using WEP, it's bad and broken; but I understand that your choice of security is limited to the devices that you are trying to network.
For what it's worth, I have my network set up with the AEBS 'n' connected to my Cable Modem, with one of the ports going to a gigabit switch for my wired network. I then have two AirTunes set up as WDS extensions for music & Internet delivery to two separate areas. The AEBS 'n" serves up DHCP and routing for the entire network.
It works quite well; I get 54 mbits/sec for the two WDS AirTunes, and 145 mbits/sec to one of my ATV's. My gigabit wired machines see data rates of 15-27 MBytes/sec (depending on the type of transfer).
Good luck!

How to connect A extreme to A express in WDS so i can use A express as LAN port with RJ 45. A express is old and does allow WDS, but A extreme is n technology and doesnt allow wds anywhere in configuration. do i hvae to buy a new A extreme or new A expr

I have an airport extreme 4th generation (n) and airport express i think model 1084, which is not n technology. I want to connect the express to extreme base station wirelessly and then use the port on express to connect a non wireless PC or TV to the internet. I do not want to run a wire from base station to the computer and wanna use express's ethernet port as LAN port. I understand this can be done in wds mode, but my extreme (n) does not allow anywhere to set up a wds under the airport utility.
do i need to buy a new express or a new extreme? If i buy a new extreme can i connect the new extreme to old extreme base station without a wire and then use the LAN ports on the new extreme to connect to a computer or tv using rj45.
thanks

but my extreme (n) does not allow anywhere to set up a wds under the airport utility.
Suggest that you download and install the more functional and useful AirPort Utility 5.6 for Mac OS X Lion , which can be used to administer both the older "g" and newer "n" devices.
Open AirPort Utility 5.6
Select the AirPort that you want to administer
Click Manual Setup
Click the Wireless tab below the icons
Hold down the option key on your Mac while you click on the Wireless Mode selection box and the WDS setting will appear so that you can make further adjustments as needed.

WDS and Closed Network

In an already existing WDS network (functioning in G model) is it possible to select the "Closed Network" in all my WDS routers and still have WDS functioning?
The reason I ask is because it is possible one of my neighbours is sabotaging my network and making it "invisible" there might a less likely chance for him to find my network (as long as he's not that savvy). What's been happening is I discovered today that the reason Time Capsule backups were happening so slowly is because my network conflicts with his--but only recently. I was on radio signal 1 and so was he/she. So I switched it to radio signal 11. Less than 2 hours later, his/her network radio signal is also on 11. So I have my suspicions...

Yes, my network is closed now. Security has always been enabled at WPA2 but enabling security does nothing to remedy malicious radio interference (if that is what my neighbour is doing). The reason I want to set it to "close" (invisible) is so that if the neighbour is not savvy enough, s/he will think my network is gone and no longer try to use the same channel I am.
Yesterday, I realised the reason my Time Capsule backups were going so slowly is because my neighbour was using the same radio frequency as I was (Channel 1). His/her network has existed for a while now and we never clashed before. So I thought it must have been just conincidence. So then I switched over to Channel 11. Well, two hours later, his/her network was also on Channel 11 making my network go from speeds of 54 to 11. So, I thought this is possibly him/her playing around and interfering with my network so I decided to go "invisible."
You are right that someone who is a bit more knowledgeable can figure out what the invisible networks are. It's not that hard. Even I can use iStumbler to see them. But, may s/he is not that savvy--I'm hoping.
Enabling security does nothing for radio interference. I've always had WPA2 security on.

Problems setting up WDS with AE

I recently had some problems with my home network and performed a hard reset on both of my AE base stations in order to reconfigure the network. I am trying to set up a WDS network with the two AE's (one being connected to the internet and the other serving as a remote to extend the range and use AirTunes function). When using Airport Utility and going through the setup process, I set up the primary AE with the connection to the internet. I am then using Airport Utility to try and configure the second AE to join the main network, but AU is not allowing the remote AE to connect/join the primary network. I keep getting an error message saying that the Apple wireless device could not join the WDS network and that I should close Airport Utility and try again. I have tried this a number of times, as well as performing more hard resets of both AE's and nothing seems to be working - any suggestions??
This is the first time I have ever had this problem using AU. In past versions of the program this has always worked setting up the network automatically, but does not seem to be working this time. Any suggestions would be helpful.
Thanks,
JB

You would get better responses if you posted in the airport section of the forum.
http://discussions.apple.com/category.jspa?categoryID=140

Problems setting up WDS with old AX and new AEBS

Hi all,
after buying a new AEBS last week, I want to put my old AX back into service. Here's what I have planned:
The cable modem sits in the living room near my stereo. The AX should connect to the cable modem and the stereo and be the main station in a WDS network with the AEBS. The AEBS will be in my study as a remote station to the AX.
Sounds trivial, but apparently it isn't I have spent the evening setting up the two base stations again and again. For some reason, the Airport Utility cannot see both stations at once as soon as they are configured. The AEBS won't find the AX even though the MAC address is correct.
I tried with and without WPA/WPA2, but I cannot figure out what's wrong
Could someone please give me a step by step guide of what to do? I am quite desperate by now...
Cheers from Switzerland
Daniel

Well, what can I say... Of course, I could not give up
Finally I got it to work. For future reference, here's how:
I first set up the AEBS to create a network, then used the Wizard of the Airport Utilitiy to add the AX as a WDS-device (it sets up the whole WDS automatically). Then I flipped the settings - set the AX to be main and the AEBS to be the remote.
I also had to adapt the Internet-Settings. Both base stations were set to bridge-mode, which doesn't work in my case because I only get two IPs from my ISP. So, I set the AX (the main) to share an internet connection and get its IP by DHCP. The AEBS on the other hand needed to get an IP manually (outside of the address space of the DHCP server created by the AX, but within its subnet).
After that it all worked - even AirTunes The AEBS now sits on my desk and the AX provides internet from the living room.
Cheers,
Daniel

Airport Extreme N works fine but not when WDS activated

I replaced my old Airport Extreme by the new 802.11n.
Works fine with our Macbooks (pro) enabled for n.
But when I activate WDS (I'd like to use my old airport Express for airtunes sometimes), an error message appears (WDS error) in the summary, and the light flashes alternatively in green and yellow... Everything else seems to work (internet connexion), but it seems no WDS possible... If I swtich it off, everything is just fine and green...
Of course I reinitialized the base, I once used the Airport utility assistant and then manually reput my personal options. I upgraded my airport firmware to 7.1 and WDS error message is still there with the flashing light... And I tried to see if my old express would make it but nope.

I had similar issues. To roll the firmware back to an earlier version try this:
- With the option key depressed, launch the Airport Utility (located: /Applications/Utilities)
- Select your problematic extreme base station and then while holding option again, click "Continue" and then choose Manual Setup.
- It should prompt you to choose a firmware version to upload. You can select 7.0 or 7.1.
The process is a little different on PC. Let me know if this solves your problem or if you need the directions for doing this from within Windows!

Sysprep unattend file not applying when image is captured with wds (no errors)

So I've been around the block a bit using sysprep and wds. Recently I've created a reference image with a virtualbox environment using windows 7 x64. I was succesfully able to create a reference image, sysprep it and capture it to the wds server. My
plan there after was to create driver specific images for each model computer we use here after not having much success using the driver store (another story)
Any how So I take my reference image and deploy it to a new computer... In this case an HP Probook 5310m. Install any missing drivers and Sysprep it with the following command. sysprep /generalize /oobe /unattend:unattend.xml /shutdown
Below is the sysprep file I have been using
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" 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">
<SkipRearm>0</SkipRearm>
</component>
<component name="Microsoft-Windows-PnpSysprep" 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">
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>
<settings pass="specialize">
<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>
<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">
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Eastern Standard Time</TimeZone>
<CopyProfile>true</CopyProfile>
<ProductKey>74fdj-7dtw8-q9mp9-ypth8-qb27y</ProductKey>
</component>
</settings>
<settings pass="oobeSystem">
<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">
<OEMInformation>
<Logo>c:\windows\system32\oemlogo.bmp</Logo>
<SupportHours>Regular Business Hrs (Overnight Support Provided)</SupportHours>
<SupportURL>url</SupportURL>
<SupportPhone>Phone number</SupportPhone>
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<HideWirelessSetupInOOBE>false</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>TAAxAEQAMwBzAHQAcgBpACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Administrator</Description>
<DisplayName>Root</DisplayName>
<Group>Administrators</Group>
<Name>Root</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<TimeZone>Eastern Standard Time</TimeZone>
<ShowWindowsLive>false</ShowWindowsLive>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>slmgr.vbs /ipk {serial key}</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<CommandLine>slmgr.vbs /ato</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>
</component>
<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-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<cpi:offlineImage cpi:source="catalog:v:/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
The machine succesfully syspreps and shuts down. I restart the computer pxe boot and capture the image succesfully.
Now here comes my problem...
Upon deploying the above driver specific image.. my sysprep file is not applied. Nothing from the OOBE wizard answers to the pc logo , or first logon commands are applied ... nothing.. I have gotten no errors during this whole process. I have
started to try to read the logs within the panther folder but havent gotten far.
What is weird to me is that I have tried recreating this image... deploy the reference image... add drivers ... sysprep ...shutdown. And if I boot normally (without capturing the image) the computer shows all of the sysprep changes.. Only when
i capture the image does it not apply the changes....
I'm stumped...
Any ides?

Confirm this scenario: You installed Windows, then ran sysprep and used the /unattend switch. Then you captured the image.
In this scenario there are 2 deployment methods.
1. If you deploy the image with DISM, the answer file generated by sysprep is detected on first boot and settings are applied. It is the same function as if you ran sysprep and chose to restart.
2. If you deploy the image using Setup.exe, it does not use the answer file specified by sysprep prior to capturing. I have not looked into *why* this happens, but I suspect that after the image is applied, it replaces the unattend.xml with the generic one.
If you are using Setup.exe, you need to use its /unattend switch and point to the answer file location. This location cannot be inside of the image. If you are not using setup.exe in a manual method (using WDS) you will need to apply the answer file to the
install image in the WDS snap-in.

WDS 2012 R2 - Cannot PXE multiple clients at the same time

Hello All,
This is my first post on here so I apologize if this is the wrong place. I work for a school district and we are implementing WDS 2012 R2. We've been extremely satisfied with the speeds and ease of use through unattend files. However, for
the past month I've been looking for a possible answer to a problem that has plagued us from day one of implementation.
So here's the problem:
I have a stand alone WDS server which is not a domain controller and is not our DHCP server. I have IP helpers and broadcast forwarders setup on the network. As well as option 66 and 67 in DHCP. So far so good right!
Well that's partially right. When we boot one client at a time to the WDS server. Everything works as intended. We can TFTP the necessary files from the WDS server. Everything boots up and we're off and running.
However, if we boot up two or more clients at the same time. The WDS server never responds to the traffic. The clients get their DHCP information. They start the referral and download from the WDS server, but get no response. I'm
really hoping that someone on here would have some insight of something I can try. I've about exhausted my list of peers and contacts. They're all stumped as well and were smart enough to stay with 2008 WDS.
I would prefer to stick with 2012 R2 since it's setup and working for the most part. With only this one hiccup.
Thanks in advance for any guidance!

Hello Daniel,
I appreciate the reply and apologize for taking so long to get back to this. Things have been a little hectic over here.
I have tried everything on this forum and I am still unsuccessful in PXE booting multiple clients at the same time.
Multicast is enabled on the server, and it works for the clients. However, as stated in the original post. I cannot boot multiple machines at the same time. I can start them from the image selection screen around the same time though. So,
that appears to be working fine.

WDS + HD

Similar Messages

Maybe you are looking for