
KEY POINTS The recent havoc wreaked by a cybersecurity company’s update reverberated through global IT systems, causing widespread outages across various industries, including banking, healthcare, and airlines. This resulted in disrupted services for banks and healthcare providers, blank screens for TV broadcasters, and pronounced turbulence in the air travel sector, leading to grounded planes and
So I naturally tried to access Win32_ComputerSystem WMI class using a Wbemtest but I was getting an Invalid class error This looked like a corrupt WMI repository. use CMD to run command net stop winmgmt select Yes or Y sc config winmgmt start= disabled cd %windir%\system32\wbem for /f %s in (‘dir /b *.dll’) do
For all Workgroup Windows Servers and workstation I used this queries below, the key thing is I queried the variable found in the resource Explorer Domain Role and Operating system Name & version %server% or %Workstation%. The domain Role attribute class value classifies the status of the devices there are 5 classes please see list below. Computer System
In my previous post, Getting Started with MBR2GPT, I showed a first look at the MBR to GPT conversion utility that is going to be released with the upcoming Windows 10 Creators Update. In this post… Source: Using MBR2GPT with Configuration Manager OSD
http://blogs.technet.com/b/configmgrteam/archive/2015/11/20/issue-with-the-windows-adk-for-windows-10-version-1511.aspx
Excellent blog by Eirik Holgernes Find all Collections with Auto Incremental update in ConfigMgr 2012
http://blogs.technet.com/b/configmgrteam/archive/2015/09/04/announcement-scap-extensions-3-for-sc-configmgr-is-now-available.aspx
Take a look at @MS_SystemCenter’s Tweet: https://twitter.com/MS_SystemCenter/status/639088960518524928?s=09
Source: Application installation is failing in OSD task sequence SCCM2012 R2 CU4
Issue: When deploying applications in an Image deployment Task Sequence in SCCM 2012R2 CU4, ConfigMgr looks at the old revisions of applications when deploying and consequently fails a deployment. This issue should have been resolved post release of SCCM 2012 SP1, however i have found it is still being experienced at SCCM 2012 R2 CU4. This