Breaking 100Mbps on Multicast with WDS

I'm building WDS (with MDT) servers that will be replacing legacy Symantec Ghost imaging environments.
I really like the "Auto-cast" concept of a revolving multicast. That could really be game-changing.
However, all my servers refuse to go past the 100Mbps seemingly artificial limit. This has been seen on various HP, Dell, and VMWare servers running Windows Server 2008 R2, 2012, and 2012 R2.
For the most part, the transmission stays pegged at 99.9-100Mbps, occasionally suffering a drop to lower speeds, and then jumping back up.
A Ghostcast on the other hand will jump from 30Mb to 300Mb wildly.
The network is full Gig, all gig ports, and all switches with IGMP(v3) support and snooping set up.
What can I do to unlock full Gig multicast speeds? Even a jump from 100Mb to 500Mb will be a huge jump.
I am multicasting to SSD devices and modern machines- I do not believe that disk I/O on the target device is a problem. Server I/O is on a RAID 5 or greater.
Thanks for any help...!

Hi,
Notice: Content referred modifying registry, please backup before any operation.
The setting is also available via registry setting. In order to make sure the settings are applied, we ca have atry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC
Change the value of "DefaultProfile" to the desired setting (10Mbps, 100Mbps, 1Gbps, or Custom).
If using Custom, make sure to make the necessary customizations under the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Profiles\Custom
Do not make any customizations to any of the built in profiles (10Mbps, 100Mbps, 1Gbps). Use the Custom profile if any customizations
are desired.
Hope this helps.

Similar Messages

What To Expect With MDT 2013 Multicast from WDS 2008 R2?

I am having a hard time finding out what to expect when setting this up. I don't think anyone has posted a demo video showing it in action or even a detailed blog with screenshots. The only multicast videos I have seen were old ones of WDS multicasting
that had no reference to MDT.
What I understand is, once I have working WDS integration with PXE boot, all I need to do is go into properties of the deployment share then select the option to enable multicast support and then update the deployment share. After that everything is
supposed to work as long as the network supports multicasting.
So, how does it work from there? How do you take advantage of it?
When I boot up a workstation to deploy to, where do I configure the specific deployment task to use multicasting (or not if I am just imaging a single system)? When I boot the second and third machine to image, what are the steps to join the ongoing
multicast? Do you pick the deployment task from the wizard again or does any machine booted to MDT join any in-progress multicast automatically?
Can you use the wizard to select different optional installed applications for different machines when using a multicast?
If you are imaging 30 workstations, can you configure it start the multicast when the 30th connection is made or does it start as soon as the first one joins?

Once multicasting is set in the deployment share it will become the default method of deploying an image for clients connecteing to that deployment point. As far as I'm aware the boot disk does not need to be updated for this to take affect.
Multicasting in WDS is a rolling session.. It will start as soon as the first client connects and will end when the last machine finishes. Machines can come and go throughout the session.
There are more options that can be applied (such as number of machines to wait for) but you need to change registry settings to do this.
I did have a GUI for this on my to do list.. but never got around to it. Maybe it's worth another look.

Multicasting with an SGE2010P

Hi,
I have just purchased a SGE2010p switch. I am hoping to multicast with windows deployment services WDS
and also hoping someone might be able to give a basic explanation (configuration would be brilliant!) on the process.
On the switch webpage, we ticked the box for IGMP snooping. WDS configured with multicasting and that part of
it works. Getting transfer rates of 16,000KBps (according to WDS console). Would have thought gigabyte should be
better than that, but still better than the 250KBps without IGMP snooping.
The problem is that all traffic is still being sent to all other ports on the switch. There is only the switch
and no routers involved. Some documents indicate IGMP querier is required, but there seems no option for that that
I can find. I believe we later enabled autolearn (but not certain - dont have access to the switch at the moment)
and then WDS broke <again>.
So I am hoping someone can please educate me!
What needs to be done to prevent the switch from forwarding data to all ports
Is AutoLearn the same as an IGMP querier?
What is bridge multicast forwarding? Sounds like passing multicasts across routers?.
Do we need to create a multicast group on the switch? I would think no, that WDS does all that.
Does this switch support MLD snooping?
Any help appreciated
thank you!

That's not going to work; manually defining groups means static multicasting (ie not dynamic nor scalable). That sort of defeats the purpose of IGMP snooping.
The problem is Microsoft's default multicast range is incompatible with IGMP and switches.
When a multicast layer 3 address is mapped to layer 2 (for the switch multicast layer 2 address), only the last 23 bits of the IPv4 address come across. The other bits are lost as we need specify the ethernet OUID owned by iana. (01-00-5e).
So the default range by microsoft 239.0.0.1-239.0.0.255 maps out at the ethernet layer: 01-00-5e-00-00-01 to 01-00-5e-00-00-ff
The problem is, the 224.x.x.x mulicast control messages also map out like that, e.g. 224.0.0.1 maps to 01-00-5e-00-00-01.
So 224.0.0.1 and 239.0.0.1 map to the same ethernet (layer 2) mac address. Therefore the switch has no alternative but to broadcast as 224.0.0.1 = all nodes.
So try changing the default WDS address to something that wont get confused by the switch, e.g. 239.67.54.3 to 239.67.54.255.
Have tested this in a lab only but should fix the problem.
bye
Oh, bridge multicast forwarding is for when the traffic needs to be forwarded (ie to another switch or router). Filtering is only to be touched to block all multicast traffic - perhaps for permanent groups that need to be manually configured. You dont need to touch that.

Multiple SSIDs with WDS, custom DHCP addresses, & Web interface

I just bought an Aiport Extreme Base station along with an Aiport Express. So far, everything is great, but I had a few of things I would like configure a certain way, and I am having a little problem.
Just to let you know, I am using the base station as the main router/firewall (with my cable modem). I am using the express basically as a wireless bridge (via WDS).
The way Apple takes care of things with WDS, is by assiging the same SSID to both the base station and express for seamless roaming. However, I would like them both to have their own SSID. I cannot seem to get this working, and I know that some other vendors allow this (Buffalo, Linksys).
The other issue is regarding DHCP on the LAN side. I want to for example hand out IP addresses 192.168.2.50-60 to my internal clients, and I want the base station to have an address of 192.168.2.1 and the express to have 192.168.2.5. It seems this also I am having problems with. It seems like the base station is very rigid on what options I have in this regard.
Lastly, I wondered if there is any other way to administer these guys (like a web browser). Sometimes I need to remotely make changes to the router, and don’t really want to install another app just for this purpose (especially at work, or some other remote location).
Thanks
Mac Mini 1.25 GHz Mac OS X (10.4.3) 1 Gig of RAM

The way Apple takes care of things with WDS, is by
assiging the same SSID to both the base station
and
express for seamless roaming. However, I would
like
them both to have their own SSID.
I don't know why you'd want that but if you are
extending the range of your wireless network with WDS
it isn't possible with Airports.
The other issue is regarding DHCP on the LAN side.
I
want to for example hand out IP addresses
192.168.2.50-60 to my internal clients, and I want
the base station to have an address of 192.168.2.1
and the express to have 192.168.2.5. It seems this
also I am having problems with.
You can set the DHCP range and then assign static
IP's to anything that conforms to that network as
long as it won't conflict with something
automatically assigned by DHCP. As a router NAT must
be enabled so if you want a unique range of numbers
only DHCP is used which won't work in your case.
In other words set the range at 192.168.1.1 and that
is the address of the base station. That can be used
for the statically IP'd device's router and DNS
entries as well like this:
Device 1 IP 192.168.1.101
Device 1 subnet 255.255.255.0
Device 1 router 192.168.1.1
Device 1 DNS 192.168.1.1
Device 2 IP 192.168.1.102
Device 2 subnet 255.255.255.0
Device 2 router 192.168.1.1
Device 2 DNS 192.168.1.1
etc...
Lastly, I wondered if there is any other way to
administer these guys (like a web browser).
Not that I'm aware of. Airport Admin Utility is all
there is. I have seen a java utility but it wasn't
very friendly.
Thanks for the answers. Despite these minor limitations, so far the Apple hardware is some of the best 802.11 stuff I have used (except for maybe a Cisco 1200).

Is there a Non Break space or Keep with?

Is there a "Non Break space" or "Keep with next word"?
In a data merge scenario some records need to stay together such as <<Year>>.<<Make>> and Vin <<VIN>>
Is there a character to keep these together?
ID CS5.5

You could make the spaces between them non-breaking, (rt-click > Insert White Space > Non-Breaking Space), or apply a no-break Character Style to the fields and the spaces between them.

Type 2 Virtual Machine in Hyper-V will not PXE boot with WDS

Hi
Bit of a wierd scenario this but I'm doing a bit of a lab experiment kind of thing. The setup is as follows:
VMWare Workstation 10 with Windows Server 2012 R2 running as a virtual machine. In VMW10 I have a NAT network interface and a Bridging interface set to load with the virtual machine. These seem to work fine (although the NAT doesn't seem to want to connect
to the internet but that's why the bridging one is there in addition).
Server 2012 is configured with the following roles:
ADDS, DHCP, DNS, Hyper-V, Printer, WDS
I have correctly configured WDS to work on the same machine as DHCP and I can get PXE boot working with WDS on a Type1 Virtual Machine in Hyper-V using the Legacy Network adapter. My problem is when I try and PXE boot on a Type2 Virtual Machine (this type
is new in R2 and should eliminate the need for a legacy network adapter) using the same network interface that I used for the Type1 machine, I get an IP address from DHCP but WDS doesn't seem to respond. Instead I get the "PXE-E16: No Offer Received"
message. I have tried just about everything I can think of and spent the whole day trying to figure out why this is the case but came up with nothing. Has anyone else encountered this or can anyone shed any light on the matter?
Many thanks in advance

"VMWare Workstation 10 with Windows Server 2012 R2"and "Server 2012 is configured with the following roles: ADDS, DHCP, DNS, Hyper-V, Printer, WDS"
Hyper-V is not supported to be run as a VM. It is a Type 1 hypervisor, which means it works on the bare metal. You have it running as a VM on a Type-2 hypervisor, so it has no access to the bare metal. Yes, VMware may have made it so some
things work in that environment, but it is not a supported (or tested) environment for Hyper-V.
.:|:.:|:. tim

Did Apple Break HD-DVD Playback with Mountain Lion using Apple DVD Player?

First of all, kindly spare me the commentary about Blu-Ray beating HD-DVD. Agreed and not the question. I have perfectly good reasons for using HD-DVD and it works very well for my purposes.
I authored an HD-DVD in DVD Studio Pro 4.2.2. as I have done many times before on Snow Leopard, but this time on Mountain Lion. When I try to play the HD-DVD, either from the physical disk from a disk image, the menu appears, but when the play button is pressed, the menu stays on screen, but the player shows the timecode of the movie playing, but with no sound or picture.
Thinking that perhaps the menu got corrupted, I put the same HD-DVD into a MacBook Pro running Snow Leopard, and it played perfectly! Conclusion: Not a DVD Studio Pro problem.
Thinking that it might be DVD Player, I copied DVD Player 5.4 from the Snow Leopard MacBook Pro to the Mountain Lion MacBook Pro (which was running DVD Player 5.6), and the HD-DVD still had the same issue on the Mountain Lion MacBook Pro, under either of the DVD Player versions. Conclusion: Not a DVD Player issue.
The HD-DVD does mount and initialize, so it's not a hardware issue with the optical drive.
Conclusion: It would appear to me that it's an OS issue with Mountain Lion breaking (either intentionally or unintentionally), HD-DVD playback. Anyone know anything more about this issue? Anyone else saddened to see Apple turn into Microsoft circa 2005, and the MacOS turn into Vista? I haven't seen much of anything about it in the forums, which is why I'm posting it here.
Thanks Apple. I just spent the better part of 3 days transcoding and authoring this HD-DVD, only to have you screw it up for me 2 days before my film festival (the perfectly good reason for using HD-DVD). Kindly spare me the, "Why don't you encode a ProRes blah blah blah quicktime movie." Heard it all before.
I knew I would regret upgrading to Mountain Lion, and I do more and more each and every day as I continually find more things that it broke. Yet another reason to add to my list for downgrading to Snow Leopard. I'm up to about 30 of them. Or to abandon Final Cut for Adobe products.
Thanks and sorry for the rant, but I'm justifiably frustrated.

Update: The Apple Store in Nashua, New Hampshire replicated the issue on their own hardware, so yes, Apple did break HD-DVD playback with Mountain Lion (it does still work in Lion, they discovered). The Apple Store reported the issue to engineering, but the more people that report the issue, the more likely Apple will do something about it. Thanks Apple.

Connect more than 3 router with WDS

hi,can i connect more than 3 router with WDS,in need to connect 8 wifi router with wireless, plz help me,Tnx

Its not possible you can try the same with access points.

Consistent Roaming with WDS on AP1142n WAPs

Hi there
Background
I have 3 Cisco AP1142n with one as the WDS and running local radius, the WDS then authenticates to an external FreeRadius server. The SSID is using EAP-TLS authentication.
The other 2 AP's are running as WDS clients and they have registered and authenticated fine against local radius on WDS AP
Problem
Users are able to roam however 90% of the time this does not work and users who are connected to a VPN lose their connection and have to re-ath to the SSID.. I am also seeing the pattern is that when users roam from WDS-Client AP 1 to WDS-Client AP2 , this does not work however when they then re-auth to WDS-Client AP2 and back to AP1 this works fine.
I have following debug enabled on the WDS device
General OS:
AAA Authentication debugging is on
AAA Authorization debugging is on
dot11/wlccp authenticator:
receive packet debugging is on
transmit packet debugging is on
state machine debugging is on
process debugging is on
Mac Authentication debugging is on
Dispatcher debugging is on
List of MNs with WDS events debugging enabled :
b88d.1213.1b3a
The question I have is the following line which I keep seeing in the output
May 13 12:24:47.980: AAA/AUTHOR: auth_need : user= 'xxx' ruser= 'AP-WDS-01'rem_addr= '10.x.x.x' priv= 1 list= '' AUTHOR-TYPE= 'commands'
May 13 12:24:51.243: AAA/AUTHOR: auth_need : user= 'xxx' ruser= 'AP-WDS-01'rem_addr= '10..x.x.x' priv= 15 list= '' AUTHOR-TYPE= 'commands'
May 13 12:25:17.259: AAA/AUTHOR: auth_need : user= 'xxx' ruser= 'AP-WDS-01'rem_addr= '10.x.x.x' priv= 15 list= '' AUTHOR-TYPE= 'commands'
Do these lines tell me anything?
Also in addition
WDS Statistics for last 4d19h:
   Current AP count: 3
   Current MN count: 0
   AAA Auth Attempt count: 12
   AAA Auth Success count: 12
   AAA Auth Failure count: 0
   MAC Spoofing Block count: 0
   Roaming without AAA Auth count: 15
   Roaming with full AAA Auth count:5
   Fast Secured Roaming count: 0
   MSC Failure count: 0
   KSC Failure count: 0
   MIC Failure count: 0
   RN Mismatch count: 0
What do the above bold lines tell me?
Kind Regards

Agree with Rasika..
if you are using 802.1x, then only you would want to configure WDS for the key caching.
if you are using a PSK, then all you need to do is configure the AP exactly the same way, with the exception of the IP address on the BVI interface, as long as the ssid and encryption are the same, and there is overlap between the cells the client should roam between the AP
Regards

Multicast deployment with WDS 2012R2

Hi,
Testing WDS multicast deployment using Server 2012 R2. DHCP is also on the same box.
Unicast deployment work fine. Tested multicast scenarios but didn't helped.
Following the URL:
http://social.technet.microsoft.com/forums/windowsserver/en-US/bba1f5d1-41ff-4351-8d6c-3070b2052a59/wds-and-multicasting-session-is-starting-too-soon
But it didn't helped either, nothing found in logs we well, even there were no log generated for multicast transmission.
Note: I don't have configured anything on Switch right now.
Any suggestions?
N.A.Malik

Hi,
I think this article will be helpful, please refer to subtitle “Prerequisites
for creating a multicast transmission”
Performing Multicast Deployments
http://technet.microsoft.com/en-us/library/dd637994(v=ws.10).aspx
Hope this helps.

MultiCasting with applets ??

Hi
I would like to ask about how can i avoid the problem of using the multicast socket with the applet as i want to build an applet and i knew that multicasting is not applicable with applets
but also i wanna use multicast socket for the multicasting of data stream in conferencing project
so any suggestions related to this problem is appreciated
thanks alot in advance

That's not going to work; manually defining groups means static multicasting (ie not dynamic nor scalable). That sort of defeats the purpose of IGMP snooping.
The problem is Microsoft's default multicast range is incompatible with IGMP and switches.
When a multicast layer 3 address is mapped to layer 2 (for the switch multicast layer 2 address), only the last 23 bits of the IPv4 address come across. The other bits are lost as we need specify the ethernet OUID owned by iana. (01-00-5e).
So the default range by microsoft 239.0.0.1-239.0.0.255 maps out at the ethernet layer: 01-00-5e-00-00-01 to 01-00-5e-00-00-ff
The problem is, the 224.x.x.x mulicast control messages also map out like that, e.g. 224.0.0.1 maps to 01-00-5e-00-00-01.
So 224.0.0.1 and 239.0.0.1 map to the same ethernet (layer 2) mac address. Therefore the switch has no alternative but to broadcast as 224.0.0.1 = all nodes.
So try changing the default WDS address to something that wont get confused by the switch, e.g. 239.67.54.3 to 239.67.54.255.
Have tested this in a lab only but should fix the problem.
bye
Oh, bridge multicast forwarding is for when the traffic needs to be forwarded (ie to another switch or router). Filtering is only to be touched to block all multicast traffic - perhaps for permanent groups that need to be manually configured. You dont need to touch that.

Voice calls breaking up on EDGE with iphone and AT&T

When I am on a voice call using the iPhone on EDGE the callers voice often breaks up. This also happens when I dial voicemail and listen to messages.
This is my first time using AT&T. Is this normal for AT&T's EDGE network or is this possibly a problem with my iPhone. This happens even if I have full bars on EDGE. I've tried resetting the phone as new and getting a new sim card and updating the firmware but voices still break up. Has anyone else experienced this?

I got a replacement iphone and the problem with voice calls breaking up persists. I have no idea what the problem is since there are so many variables and I don't have all the information. I just know that I never had this sort of problem in the 9 years I was on Verizon with any phone. I really enjoy this device for everything besides the phone functionality. It would be cool if I could just pay for data on this phone without the voice so I could get a Verizon phone for voice and keep the iphone for data but I know that would never happen. Well, I still have a couple weeks to figure out what I'm going to do.

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.

Adding a non-wireless PC to an Airport Extreme network with WDS, or extend

I have an Airport Extreme base station (802.11n), a Time Capsule, and a cable modem. Currently the Time Capsule is wired by WAN to my cable modem. It is broadcasing a wireless network to my iMac Intel Core2Duo running 10.5.2 and my AppleTV, and my MacBook Pro running 10.4.11. I'd just acquired a Windows XP PC with no WiFi card but a built-in NIC card. I'm having difficulty adding the Airport Extreme base station to the network of the Time Capsule, so the non-wireless PC can use the LAN port of the Airport Extreme and pickup an internet connection. I don't want anything connected to the WAN port of the Airport Extreme. The PC can't be moved to the room with the cable modem. Should I:
1. Set it up from the Airport Utility of my iMac or MacBook Pro?
2. Switch the placement of the Airport Extreme and Time Capsule?
3. What steps should I take from Airport Utility, to add a reset Airport Extreme or Time Capsule to the network already tied to my Cable modem?

Since both of your base stations are 802.11n, I suggest that you use the "extend a network" feature available to these, instead of creating a WDS.
1. Set it up from the Airport Utility of my iMac or MacBook Pro?
Your choice, you could use the AirPort Utility from either of these Macs to configure the base stations.
2. Switch the placement of the Airport Extreme and Time Capsule?
I'd suggest leaving the Time Capsule connected to the modem and use the AEBSn to extend its wireless network.
3. What steps should I take from Airport Utility, to add a reset Airport Extreme or Time Capsule to the network already tied to my Cable modem?
Here are the basic steps to configure the extended network:
o If practical, place the base stations in near proximity to each other during the setup phase. Once done, move them to their desired locations. You may also want to temporarily connect the AEBSn directly to one of the TC's LAN ports during setup.
o Open AirPort Utility and select the TC.
o Choose Manual Setup from the Base Station menu.
o Click AirPort in the toolbar, and then click Wireless.
o Choose “Create a wireless network” from the Wireless Mode pop-up menu, and then select the “Allow this network to be extended” checkbox.
o Next, select the AEBSn, and again choose Manual Setup from the Base Station menu.
o Choose “Extend a wireless network” from the Wireless Mode pop-up menu, and then choose the TC's wireless network from the Network Name pop-up menu.
o Click Update to update the base station with new network settings.
o Upon completion of the setup, you can now relocate the AEBSn to its desired location.
(ref: Page 46 of "Designing AirPort Networks Using AirPort Utility.)

Iphone Disconnecting from Wi-Fi with WDS

Hi,
We are having a problem with my home's wifi connection and the both Iphone 5s that we have. We got and Tplink primary router and a secondary one (also Tplink) working in WDS mode, in the same LAN. The problem is that when the secondary router is in range, the phone stays well connected to the wifi. But when the secondary router is far way (or has been turned off) and the primary one is much closer, than the phone is not able to make a connection. It even finds the wifi, but does not connect. Even dont recognize the password.
But, if we turn off the secondary router and reboot the Iphone, after than it is able to connect to the primary router. If we turn on the secondary router, the connection maintain well put. But if we, then, turn off the secondary router, them the Iphones cant connect to the wifi using the first router, even if the phone and the router is side by side.
That problem does not occur with notebooks and other phone that is not Apple.
Help us.

I maybe be stupid but i answer anyway, is your APN settings right? Because in my old phone i had to set those before i could use mobile data.
You can change your APN settings in: Mobile network -> Mobile Data Network -> Then there is it.
Plz anyone smarter do not judge me because me comment.

Breaking 100Mbps on Multicast with WDS

Similar Messages

Maybe you are looking for