Junior SCCM guy to top dog.
Posted on 2016-08-23
I've been prepping a wim/task sequence for a USMT migration from Windows 7 to Windows 10, then my main SCCM Architect left. I was just told I'm inheriting the entire SCCM environment. Its a small shop about 250 users. They have 1 primary and 1 secondary servers. The main site has 240 users and the offsite datacenter has maybe 10 users. I've been packaging and deploying apps and OS's once before, but now I'm asked to upgrade all the Win Servers OS's from 2012 R2 to CB, in addition to upgrading the SCCM servers to CB 1607 before the migration starts. I read up that all the CM Servers that are running Windows Server 2012 R2 need to be upgraded and all problems fixed before the SCCM servers are upgraded to CB 1607.
I looked in the All Devices collection and there are over 650 pc/laptops and 350 servers so the SCCM guy that just left was not cleaning up AD or SCCM and I have a ton of duplicates devices to clean up and we don't have anything like a Nagios server to scavenge pcs that haven't been logged into in over 90 days.
Could you please point me in the right direction on maybe a PS script to check and see if the pc's in SCCM and AD are valid, logged into in the pass 90 days, are in a proper Computer AD-OU and don't have the Machine Account disabled?
Also all the monthly OS/Office monthly updates groups for the past year have a 36% to 54% success compliance rate. What else should I check on a daily bases?