Sign in
 
Home2012Previous VersionsLibraryForumsGallery

More From Boe Prox

Get-SCCMClientUpdate
(5)

SCOM Agent Installation and Reporting Script

This script is best run as a scheduled job where you have access to the SCOM SnapIn. The script will query Active Directory for all servers in the domain and compare that collection with the servers that have the SCOM Agent installed. Those servers that do not have the agent in

 
 
 
 
 
(3)
935 times
Add To Favorites
System Center
2/9/2012
E-mail Twitter del.icio.us Digg Facebook
Report Abuse to Microsoft
Sign in to Ask a Question

  • Answer the Question | Hide
    Can this script be updated for SCOM 2012
    2 Posts | Last Post August 09, 2012
    • Written July 10, 2012 
      I have most of the cmdlets converted to 2012, but I am having trouble with the discovery part
$Discover = New-WindowsDiscoveryConfiguration -ComputerName $NonSCOM -PerformVerification -ComputerType "Server"
$Discover.ComputerNameDiscoveryCriteria.getComputernames() | ForEach {Write-Verbose ("{0}: Attempting to discover" -f $_)}
Write-Verbose ("[{0}] Beginning SCOM discovery" -f (Get-Date))
$DiscResults = Start-Discovery -WindowsDiscoveryConfiguration $Discover -ManagementServer $MgmtServer

The term 'New-WindowsDiscoveryConfiguration' is not recognized as the name of a cmdlet,

Thanks in advance!!
    • Written August 09, 2012 
      Hi mhanlon. Unfortuantly, I do not have access to SCOM 2012 at this time to verify what the correct cmdlet is, so I am not able to help you at this time. Once I have access, I will update the script for SCOM 2012.