WSUS downloading updates

WSUS downloading updates

Settings are found under WSUS Console -> Options -> Update Files and Languages

Snip:

These settings will download any update that is approved.

One of the issues with WSUS downloads is that if your bandwidth falls below a certain threshold the downloads will cease all together - I actually limit my server to 5KBps using a 3rd party app and the WSUS does not try to download.

To check to see if your downloads are occurring (wsus uses svchost.exe to download which can muddy weather or not they are downloading or another sub svchost process is using the bandwidth) navigate to your <WSUS Drive>:\WSUSUpdates\WsusContent and sort by 'Date Modified' to see how recent the last download folder was.

Snip:

Ping 127.0.53.53

Ping result of 127.0.53.53

In setting up my environment I had an old active directory domain that I built in 2009 called fight.club.

After initial set up I can across an interesting ping result of 127.0.53.53 when pinging my domain fight.club.

127.0.53.53 is a response when there is a name collision with a local domain an existing internet domain. One thing I had failed to think of is that the TLD .club had come into existence since the last time I had used my domain. The .club TLD came into existence on the 18th January 2014

Further reading:
https://www.icann.org/resources/pages/name-collision-2013-12-06-en#127.0.53.53

127.0.53.53 is a special IPv4 address that will appear in system logs alerting system administrators that there is potential name collision issue, enabling a quick diagnosis and remediation. The "53" is used as a mnemonic to indicate a DNS-related problem owing to the use of network port 53 for the DNS service.

System administrators that encounter a system error due to name collision are encouraged to take the following steps:

1. Report the problem to ICANN »
   Instances where there is a reasonable belief of demonstrable, severe harm as a consequence of a name collision should be reported.
2. Read the Guide to Name Collision Identification and Mitigation for IT Professionals (version 1.1) [PDF, 476 KB] and implement the measures outlined therein.
3. Spread the word about the potential for name collision occurrence and mitigation in your professional circle.

Next step to rename my domain was needed.

WSUS Download Speeds

WSUS Download Speeds

Being on a metered internet connection I have to mind my downloads and also take opportunity to download as much as possible at the appropriate times, now being the time to download being the end of the month.

I kicked off my WSUS Sync and allowed the server to have access to the internet. The resulting data transfer was less than spectacular, averaging approximately 5-10 KBps.

Off to the googles with the following found: http://blogs.technet.com/b/msaad/archive/2010/09/24/increase-wsus-3-updates-download-speed.aspx

Command:
"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

Not having the executable "%programfiles%\Update Services\Setup\ExecuteSQL.exe" and also running 2012 which uses MICROSOFT##WID, not SSEE I moved on.

Next I checked my BIT's settings (Computer Configuration -> Administrative Templates -> Network, Background Intelligent Transfer Service -> Limit the maximum network bandwidth for BITS background transfers) which were fine.

This fine post http://social.technet.microsoft.com/Forums/windowsserver/en-US/3b9df918-411c-44f8-a905-024ad0dcc2a7/windows-2012-wsus-service-bits?forum=winserverwsus showed me the light.

I opened up an administrative cmd window to my sql 2012 folder "D:\Program Files\Microsoft SQL Server\110\Tools\Binn"

Command:
SQLCMD.exe -S \\.\pipe\Microsoft##WID\tsql\query -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

Snip:

After running the above commands I cycled the WID and the WSUS servers, speeds ramped up to use the full bandwidth.

The first post was primarily correct, just not for Server 2012 R2 and requiring the mssql installed exe

DD-WRT PXE Configuration

DD-WRT PXE Configuration

Being use to windows DHCP options, I had to do some research into enabling my DD-WRT Buffalo router to forward the PXE boot requests to my SCCM 2012 server.

The below is the configuration I needed to add to the routers DNSMasq additional options:

dhcp-boot=<PXEImageName>,<PXE HOST NAME>,<PXE IP Address>

It is also worth to note that the \'s in the output because single quotes ' such as the below:

dhcp-boot=SMSBoot'x64'wdsnbp.com

Snip:

SCCM 2012 R2 site storage thresholds

SCCM 2012 R2 site storage thresholds

I got a little tired of SCCM going a little warning crazy with its space alerts: Warning is set to 10gb, Error set to 5gb.

On the Warning/Error themselves they incorrectly states below:

Text:
Console by navigating to the Site Hierarchy --> WF1 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object.

Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the Configuration Manager Console.

Snip:

Note that it states that the Status Summarisers are found under the 'Site Hierarchy' which only exists under Monitoring. This is incorrect, the Status Summarisers are found:

Administration -> Site Configuration -> Sites -> Right click on the appropriate site - Status Summarisers