Showing posts with label sccm agent. Show all posts
Showing posts with label sccm agent. Show all posts

Thursday, August 18, 2016

Detecting Windows License Activation Status Using ConfigMgr DCM and OpsMgr

If someone already done the work, why not share it ?

Tao Yang's post about this is amazing, like all the other posts he makes.

http://goo.gl/84qkX1

I followed his post until the end, and suddenly i came up with some errors in SCCM about the Powershell Scripts Execution Policie ...!

So, i've made this VBScript for the workaround (already post it too in Tao's blog!)

Just replace the part of the Powershell script with this VBScript if you bump into some execution policie issue.

 strComputer = "."   
 Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")   
 Set colItems = objWMIService.ExecQuery( _  
   "Select * from SoftwareLicensingProduct Where PartialProductKey IS NOT NULL AND ApplicationID = '55c92734-d682-4d71-983e-d6ec3f16059f'",,48)   
 For Each objItem in colItems   
 select case objItem.LicenseStatus  
         case "0"  
                 Wscript.Echo "Unlicensed"  
         case "1"  
                 Wscript.Echo "Licensed"  
         case "2"  
                 Wscript.Echo "Out-of-Box Grace Period"  
         case "3"  
                 Wscript.Echo "Out-of-Tolerance Grace Period"  
         case "4"  
                 Wscript.Echo "Non-Genuine Grace Period"  
         case "5"  
                 Wscript.Echo "Notification"  
         case "6"  
                 Wscript.Echo "ExtendedGrace"  
 end select  
 Next  

Cheers,

Thursday, May 19, 2016

SCCM (ConfigMgr) - SHA-2/256 is NOT supported on this platform | Unix/Linux Systems

It's a new error for me.
It happened in a Solaris 10, and i got stuck for a while to troubleshoot and solve - fortunately i've got some nix skills from earlier professional experiences, the same way i've got google search skills.

So, if you came up with the error message in your (/var/opt/microsoft/scxcm.log) :

"SHA-2/256 is NOT supported on this platform"


You need to do this :
(as root)
cd /opt/microsoft/configmgr/bin

./uninstall

cd ../../
rm -Rf configmgr

Now, re-install your agent with the '-ignoreSHA256validation' parameter :

./install -mp CCM_MP_SERVER -sitecode SITE_CODE -ignoreSHA256validation -nostart ccm-Sol10sparc.tar


(you might need to replace 'ccm-Sol10sparc.tar' to your correct package)


cd /opt/microsoft/configmgr/bin
./ccmexecd start

So, if you go to your SCCM console, your new device will show up correctly.