Can you throttle your WDS deployment bandwidth?

During our class discussion on Windows Deployment Services, we talked about the network bandwidth considerations. It is recommended that you utilize a gigabit back bone for deployment activities, but a 100 MB backbone will work during low network activity. It is possible to throttle the bandwidth used by WDS be using the following procedure.

To throttle your multicast bandwidth usage:

From the WDS MMC, open the Server Properties page.
Go to the Network Settings Tab.
Select the Custom network profile.
Click start and type Regedit32 and press enter.
In the registry, browse to HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Profiles\Custom
Set the TpMaxBandwidth setting to something less than 100. It's the percentage of available bandwidth that the server uses.

Reference: http://social.technet.microsoft.com/Forums/en/winserversetup/thread/09fe5ed6-aea5-4eb1-9df9-17c095c51b8f

Comments

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne. I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10. This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit. In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate. I needed to make sure the environment is set up for me to be able to utilize this cmdlet. If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place: Remote Scheduled Tasks Management (RPC) Remote Scheduled Tasks Management (RPC-ERMAP) Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Jason Yoder, MCT

Search This Blog