Welcome to MrBoDean.net on Github pages

WSUS Automation


So there is a new blog that SCCM admins should take a peek at. Bryan Dam is my hero for having the time to combine most WSUS maintenance into one script. http://damgoodadmin.com/2017/11/05/fully-automate-software-update-maintenance-in-cm/ I encourage you to go take a look at his blog and the presentation he did about the script. https://www.facebook.com/DeploymentResearch/videos/2141149579244220/

Seriously good info. As a thank you to Bryan for saving me time I am going to respond to a statement in the blog post on his script. “Once an update has been declined in WSUS and synced to Configuration Manager I honestly don’t know how you bring it back. I’m … sure … there’s a way somehow.”

Well as someone forced into aggressive declines to keep the WSUS catalog to a reasonable size I was forced to learn how. Once you know how to restore a declined update you can decline without fear. So how do you do it? Approve the update in WSUS and sync. But you say it is not that simple, “I tried it and it did not show up”. Well when has the WSUS and Configuration Manager interface ever been simple. The trick is that the sync must be a full sync not a delta sync. To trigger a full update run this powershell on your primary site server

$siteserver = "YourServer"
$sitecode = "XXX" #Your 3 Digit Site Code
$SUP = [wmiclass]("\\$siteserver\root\SMS\Site_$sitecode:SMS_SoftwareUpdate")
$Params = $SUP.GetMethodParameters("SyncNow")
$Params.fullSync = $true
$Return = $SUP.SyncNow($Params)

One other thing to note when re-approving in WSUS. Unapproved is an approved status for SCCM. Basically everything that is not declined will sync to SCCM. By approving the patch as unapproved you will return it to the normal state that SCCM maintains. If you have any systems that patch via WSUS directly using your Software Update Point then approve as needed as it will not impact SCCM.

Maintenance Window Troubleshooting Tip


I keep looking this up so thought I would clearly document it for myself and the rest of the interweb.

When troubleshooting Configuration Manager Maintenance Windows the runtime number in the ServiceWindowManager.log is in seconds OnIsServiceWindowAvailable called with: Runtime:6600, Type:2 6600/60 = 110 minutes

(6600/60)/60 = 1.83 hours, Or 1 hour and 50 minutes

See https://msdn.microsoft.com/library/jj155419.aspx

Quickly remove mapped connections


Just a quick tip to remove mapped connections with PowerShell and NET USE

(net use).split(' ')'%{If($_ -match "\\"){net use /delete $_}}

To see your connections

(net use).split(' ')'%{If($_ -match "\\"){$_}}

Understanding and Troubleshooting Content Distribution in Microsoft Configuration Manager


While working a issues that required opening a case with Premier Support I was given a link to a great resource to use while troubleshooting distribution points and content distribution issues. If you do not know about it take moment to review and save it for when you need it. https://support.microsoft.com/en-us/help/4000401/content-distribution-in-mcm

Special thanks to Vinay Pamnani, Senior Support Escalation Engineer with Microsoft. He shared the link and has published several tools that are part of many Configuration Manager Administrators tool belt.

Configuration Manager Update not progressing


Technical Preview 1708 was released yesterday and I fired up the lab virtual machines to give it a try. Several Hours Later I am still trying to install. 1st I had a few SQL issues to sort out but mainly they were let the database start before opening the console. Next the download would not start. It turns out the sms_site_component_manager was crashing. Luckily a quick search found that is was a known issue https://social.technet.microsoft.com/Forums/msonline/en-US/54d5a139-a4b1-4cb5-9644-2b826c4b56eb/site-component-manager-crashing-once-per-hour-after-upgrade-to-1706?forum=ConfigMgrCBGeneral

OK, now that the component manager is running the download completes and I can start the install. Everything looks normal and I head off to bed to let it cook overnight. Imagine my surprise to find that this morning the status has not changed. The next step in the update would be to run the prerequisite change and it has no status. Off to the logs and I find that the CMUpdate.log has not been updated in a while. And one of the last updates is “CONFIGURATION_MANAGER_UPDATE service is signalled to stop…” So I check the windows services and sure enough the CONFIGURATION_MANAGER_UPDATE service is not running. After starting that service up now everything is progressing again. Adding this to my growing list of upgrade checks and making a pot of coffee while I watch the logs for this upgrade.