New Tool: ConfigMgr Client Notification

cnt-1

smsagent

Today I whipped-up a very simple tool for ConfigMgr admins and support staff. It allows you to send client notifications (using the so-called fast channel), such as downloading the computer policy, collecting hardware inventory, checking compliance etc, to remote computers from your local workstation independently of the ConfigMgr console.

CNT

The tool connects to your ConfigMgr site server using a Cimsession and PSSession, so you need WsMan operational in your environment. You simply provide some computer name/s in the text box, enter your site server name, select which client notification you want to send and click GO. The tool will get the online status of the clients from the SMS Provider to give you an indication of which systems will receive the client notification. Then it will trigger the client notification on online systems from the site server.

The tool is coded in PowerShell / Xaml and uses the MahApps Metro…

View original post 112 more words

Monitor Content Downloads Between an SCCM Distribution Point and a Client

smsagent

Sometimes you want to monitor the progress of a content download on an SCCM client from a distribution point. You can use the Get-BitsTransfer PowerShell cmdlet, but it doesn’t currently support running on remote computers, so I wrapped the cmdlet in a bit of extra code that lets you get Bits transfer information from a remote computer, and adds a couple of extra values like the transfer size in megabytes and gigabytes as well as a percent complete value. Run it while there’s an active transfer to monitor the progress.

Simply provide a computer name like so:

Get-BitsTransfers -ComputerName PC001

Function Get-BitsTransfers { [CmdletBinding()] Param ( [Parameter(Mandatory=$true, ValueFromPipelineByPropertyName=$true, Position=0)] $ComputerName ) Invoke-Command -ComputerName $ComputerName -ScriptBlock { $BitsTransfers = Get-BitsTransfer -AllUsers Foreach ($BitsTransfer in $BitsTransfers) { [pscustomobject]@{ DisplayName = $BitsTransfer.DisplayName JobState = $BitsTransfer.JobState OwnerAccount = $BitsTransfer.OwnerAccount FilesTotal = $BitsTransfer.FilesTotal FilesTransferred = $BitsTransfer.FilesTransferred BytesTotal = $BitsTransfer.BytesTotal MegaBytesTotal = [Math]::Round(($BitsTransfer.BytesTotal / 1MB),2) GigaBytesTotal…

View original post 24 more words

ConfigMgr : Query Machines with LocalGroupMembers where users are admins on machine

Enable the class LocalGroupMembers from here > http://praveenkumarsharma1.blogspot.com/2014/10/enable-members-of-all-local-groups-of.html   SQL Query to find domain users who are administrators on the workstations/servers SELECT v_R_System.Netbios_Name0, v_R_System.User_Name0, v_R_System.AD_Site_Name0, LocalGroupMembers_DATA.Account00, LocalGroupMembers_DATA.Category00, LocalGroupMembers_DATA.Disabled00, LocalGroupMembers_DATA.Domain00, LocalGroupMembers_DATA.Name00, LocalGroupMembers_DATA.Type00 FROM LocalGroupMembers_DATA INNER JOIN v_R_System ON LocalGroupMembers_DATA.MachineID = v_R_System.ResourceID where Name00 like '%Administrators%' and Type00 like '%Domain%' and Category00 like '%UserAccount%' Output :

SCCM 2012: dynamic app install Policy download failed

When Rebooting Is Not The Answer

I had an issue the other day with an application not installing that I had been installing for a long time through the UDI wizard with the MDT Integration with SCCM 2012.  Suddenly it had stopped installing and I got the below error in the SMSTS.log.

Make sure the application is marked for dynamic app install Policy download failed, hr=0x80004005. The operating system reported error 2147500037: Unspecified error

While this error can be caused by symbols such as a comma or ampersand in the application name for me it was because I had changed the application name to a more user-friendly name which in turn broke the UDI as it doesn’t dynamically update application names.  I simply went into the UDI and removed and re-added the application and it started working again.

View original post

Reimaging with OEM licenses

When Rebooting Is Not The Answer

I came across a TechNet blog post on Microsofts site the other day that taught me something new I thought I would pass along in case it would help someone out.  If you don’t have software assurance with Microsoft but are a volume license customer you can deploy volume license media providing you have keys and the edition of the OEM OS and the Volume License match.  This means you don’t have to be purchasing volume licenses to reimage provided you do have at least a few volume licenses of the software you are trying to deploy.  The below blog posts provide more info.  Guess you learn something new every day.

https://blogs.technet.microsoft.com/volume-licensing/2014/02/13/licensing-how-to-reimaging-rights-top-5-questions/

http://www.aidanfinn.com/?p=14534

View original post

How Candy Crush can break your Windows 10 image capture

When Rebooting Is Not The Answer

I’ve been struggling to get SCCM 1602 and imaging of windows 10 to play nice and the below is one of the latest issues I’ve encountered.  If your running Windows 10 build 1511 and try to capture you might encounter error code 0x00004005.  One of the possible causes can be all the Appx packages (Candy Crush and Twitter etc.) Microsoft decided to install even in Enterprise edition (that one I don’t understand I could see home even pro but enterprise?).  As was pointed out in this technet article running a Get-AppxPackage -AllUsers | Remove-AppxPackage remedies the issue before capture.

View original post

Critical Update Confusion

When Rebooting Is Not The Answer

Happy Wednesday, (Well as happy as an Wednesday can be I guess…) I was prompted by a user that their machine was behind on updates as were many others as they tried updating from the web and got lots of updates.  I did some checking and all the updates looked to be fairly recent within the last month but were listed as Critical level updates.  This confused me as I have critical level updates deploying more often than once a month to not get behind on security vulnerabilities as Microsoft patches them.  After some research I realized there is a difference between Critical level severity and Critical level update classifications.  Microsoft defines Critical Updates as “A widely released fix for a specific problem that addresses a critical, non-security-related bug.”  So just because it’s in the critical update classification it may not have an severity level of critical.  In fact critical…

View original post 95 more words

Quickly fix Windows is not Genuine from different Windows versions.

When Rebooting Is Not The Answer

I had an issue today with an old KMS server that some machines had been talking to getting shut down and then the machines months later complaining that they couldn’t find the KMS server.  I  then removed the KMS server’s DNS entries and prevented it from publishing them to dns which had been missed before.  That isn’t the purpose of this post though so if you need more info the below two links help out a lot.

How to remove a KMS Server from your Infrastructure

Additional info for Server 2008 only.

Back to the purpose of my post was when I get tickets for activations (as I have over the past few days) I wanted an easy script to run slmgr, remove the product key, input, and activate the new key.  We use MAK keys in our environment so just for the few machines that were set up for…

View original post 121 more words

SCCM WSUS Sync errors/WSUS cleanup

When Rebooting Is Not The Answer

As an SCCM administrator it is easy to install SCCM and simply forget about WSUS being an integral part of SCCM and forgetting its even there.   That is until you start getting synchronization errors or other WSUS errors.  So to fix or prevent that from happening you should really go to the wsus server cleanup wizard which can be found in the wsus console under options.  What do you do though if you haven’t been running it and the wsus server cleanup wizard fails.
wsus error

Well to start you can rerun the wsus server cleanup wizard with all but the first option and then rerun with only the first option but that won’t always work especially if you are really behind on wsus cleanup.  So your options are to reinstall the wsus database or do a manual cleanup.  In the past when I had seen issues with this occur I had…

View original post 135 more words

SCCM Package not distributing

When Rebooting Is Not The Answer

So I had to delete a package off a distribution point and redistribute yesterday and ran into an issue where it would not distribute.  I continued to read my logs and noticed that the distmgr.log continually retried the package but never actually distributed it.  It just kept saying no action specified for package.  Well after a ton of research I came across a blog post detailing how resolve that.

First check your action and updatemask

This particular distribution point had an update mask and action totally different than any of the other servers.

snip_20180515141509

I then deleted that record.

Once I did that I was able to finally redistribute the content.

Thanks a bunch to Daniel Eyer’s blog.

http://www.danieleyer.com/blog/2012/07/19/sccm-keeps-processing-package/

View original post