WLSE with WDS

Hi,
I've 2 units of WLSE, performing redundancy, and 2 WDS configured.
In the WDS, at the WNM config, I've enter the virtual IP of the WLSE, but it give a message of "NOT AUTHENTICATED"..
May I know why is that??
Thanks.

WLSE need's to authenticate to each WDS in your network using leap. Refer to the online doc in the WLSE for this or this link.
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_13/u_gd/devices.htm#wp1594013

Similar Messages

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).

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

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

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.

WLSE - AP/WDS fails to complete full authentication phase

I need the patch for the following bug. I can't find it anywhere.. Can someone help.. I know people have used it to fix their issues before.
This issue is documented in Cisco bug ID CSCsb47726.
There is a pointed patch available for ACS 3.3.3 (both ACS software and solution engine).
To install the patch on the software ACS, perform these steps:
1.Browse C:\Program Files\CiscoSecure ACS v3.3\Support.
2.Re-name the AironetEAP.dll file to AironetEAP.dll.bak.
3.Copy the new AironetEAP.dll to the same folder.
4.Re-start the ACS services.
To install the patch on the solution engine, perform these steps:
1.Run the autoexec.bat file from inside the patch directory.
2.Log into ACS.
3.Go to System Configuration > Appliance Upgrade Status. Choose the appropriate download.
4.Enter the IP address of the computer from which you run the autoexec.bat
file.
5.After you have uploaded the patch to the ACS, click Install Upgrade.
6.Re-start the ACS services.
Make sure to create an ACS backup before the patch is applied.

The fix for this bug is a patch that needs to be installed on Cisco Secure ACS. In order to download the patch, open a service request with the Cisco Technical Assistance Center (TAC).
http://supportwiki.cisco.com/ViewWiki/index.php/Wireless_LAN_Services_Module_(WLSM)_access_point_(AP)/Wireless_Domain_Services_(WDS)_fails_to_fully_authenticate_with_Cisco_Secure_ACS_3.3_and_4.0

Windows 8 not picking up embedded product key when installed with WDS

Ok so here is my setup.
Server 2008 R2, running WDS and serving various images.
the Windows 8 image is a vanilla boot.wim and install.wim imported from a system builder iso.
If I burn the ISO or extract it onto a USB drive, then the install process picks up the embedded Windows product keys no problem.
If I deploy the same thing via WDS, the setup wizard asks for the keys, ergo, is not picking them up from the UEFI firmware. Is this an inherent limitation of WDS or am I doing something wrong?

Hi,
As it has been a while since you post the question, whether the issue still exists? Have you tried to entered the product key in unattended file? If issue still exists could you share the unattended file with us?
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forum a great place.

Weird Problems with WDS (Macbook + xbox)

Hi - Hope someone can help...
I have a Powermac G4 that does not support an airport card. So I bought 2 Airport Express' last year and set up a WDS network to act as a bridge between my Cable modem which is on a different floor to my Mac. After some fiddling this worked perfectly. Had the odd guest with a windows pc who could log on no problem. I did not use wireless security.
A few months ago my girlfriend got a 13inch White Macbook. Connected no problem. I decided to add a WEP password using 6 letters. No Problems.
2 weeks ago I got and xbox 360 with a wireless adapter. Couldn't connect as it said that the password was not correct - not the right format. I decided to temporarily take my security off. Xbox connected fine.
Weird thing was the macbook could no longer get on to the web. Tried putting the password back on. No luck only now xbox cannot connect either.
No I have tried changing the settings in all possible ways but neither macbook nor xbox can connect to the internet??? I have gone so far as factory reseting bot airports and setting up from scratch. But still neither can get internet.
The bridge to the G4 still works fine. I'm at my wits end. Any ideas?
The macbook can see the airports and appears to connect but no internet (same with xbox accept can see but not connecting to airport when tested). The network settings on the macbook say that it is using a self assigned ip therefore may not be able to connect to internet...

Hello Freedgull. Welcome to the Apple Discussions!
To facilitate the WDS set up, try the following:
o Perform a "hard" reset on the AirPort Extreme Base Stations & a "factory default" reset on the AirPort Express Base Stations (AX) before setting up the WDS.
o Place the base stations within near proximity of each other during the set up phase, and then relocate them to their desired locations when complete.
o To avoid having to "switch" wireless networks during the WDS setup, attach each of the remote/relay base station, via an Ethernet cable, to the main base station. Of course, this would be dependent on the AirPort types used for the main/relays/remotes.
o Be sure to jot down the AirPort IDs (MAC addresses) for each of the base stations to be used in the WDS as these will be required during the setup.
o When enabling wireless encryption, configure the relay/remote base stations first and the main base station last. I suggest using WPA for your security level.

WIreless solution with WDS/Active Directory/mutiple ssid

I'm in a project where the mail goal is to implement a wireless solution for our company.
I will try to explain our dimention.
We want two kinds of wireless solutions based on the same AP, secure and unsecure.
The unsecure is a "guest" net for Internet-access. We want a solution where the users have to contact our reseption to be given a username/password to access this network (same kind you find in airports, some hotels and so on). It has to be able to give a permanent access, access by the hour/day. Username/password can be random, but don't have to be.
The secure is a "work" net for our company computer services. We want the wireless network to be encrypted (a good standard) and the computer itself has to have some kind of certificate. We also want the user to authenticate itself using Microsoft Active Directory.
These two wireless networks should have their own SSID with different security levels. Both of them should support WDS.
Can somebody give me some information on which equipment we need, what kind of server services needes and so on.
The solution has to be robust, but of course the cost aspect is hanging over us as a ghost... ;-)
Regards
Eirik

Guest solution and secured wireless solution is very much possible with Cisco Unified wireless solution. The document available at http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008070ba8f.shtml explains how to setup guest and internal WLAN in a network. This should help.

Slipstream Office Updates with WDS

Hi guys,
I have a problem with slipstreaming the Office 2010 updates. We use a WDS server to do this. During the installation process, WDS needs to slipstream the Office updates. However, this does not happen. When the Office setup is completed we have noticed that
the Office updates are not installed (SP2 and other updates). Because of this, the updates are retrieved by Windows Update. The updates can be found on our network share in \Apps\Office2k10\x32\Updates. Also Office setup looks in this folder during the installation
for the updates but the updates are still not installed.
We really don't know what the problem is. Hopefully you guys can help me with this.
Kind regards,
Mo

Hi,
What's the folder structure of your Office installation source?
Remember that you'll need to extract all the files from service pack's EXE file first, then copy the content (several .txt, .xml, .msp files) into the Updates folder.
For more information about Using the Updates folder to deploy software updates during an Office 2010 installation, please refer to:
http://blogs.technet.com/b/office_resource_kit/archive/2011/05/05/using-the-updates-folder-to-deploy-software-updates-with-an-office-2010-installation.aspx
http://www.askvg.com/guide-how-to-slipstream-service-packs-into-microsoft-office-setup/
Hope this helps.
Thanks,
Ethan Hua CHN
TechNet Community Support

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.

HELP! Imaging thinkpad tablet 2 with WDS

I am on a strict timeline and need to image over 100 tablets (thinkpad tablet 2) and I'm running into issues with my WDS setup. I've imaged many laptops etc before but this has the UEFI BIOS. I'm using a WDS server on Server 2012.
I've setup a boot image using Windows 8 32bit.
-Attempted to use the Lenovo 3.0 USB/Network Dongle. (I've since heard that you can only use the 2.0 ver?)
-Turned off the secure boot in the BIOS
-set the USB device as the first boot item
-turned off F12 in the BIOS and in WDS
-set my DHCP opt 67 to: boot\x86\wdsmgfw.efi
When I boot the tablet it won't even see the USB/PXE boot. It boots to the hdd. Is it truly due to the USB 2.0 dongle vs. the 3.0? Anyone? Bueller? HELP!
Do I need to do anything else on my WDS server?

Sounds to me like it could be a driver issue. What's the error message that appears on the "frowny face" screen?
Also, have you checked out this thread? It may have some useful information for you:
https://forums.lenovo.com/t5/Enterprise-Management-IT/Deploying-Windows-8-to-the-new-ThinkPad-Tablet...

WLSE with WDS

Similar Messages

Maybe you are looking for