sterlingdev
asked on
System Center Operations Manager 2007 R2 - Windows Operation System Not monitored
I have just set up a brand new server for this to be installed onto, and not-to my suprise, out of the box it is not working correctly.
The documentation is a massive minefield and doesn't contain any useful hints at getting started. However I have managed to get some monitoring of servers to work, primarily using the Dell MP and the Microsoft SQL 20005/2008 MP's.
BUT...
The "Windows Operating System" colummn for every server I have installed the agent on so-far just reports "Not monitored"
I don't understand this. Did some searching around, its not that silly 3-day NETBIOS thing because these servers I am attempting to monitor have never previously had this client installed onto them
Anyone suffer this previously and can offer ideas or solutions? Thanks. If I cannot get this working to monitor the Windows OS this product is not fit for purpose.
The documentation is a massive minefield and doesn't contain any useful hints at getting started. However I have managed to get some monitoring of servers to work, primarily using the Dell MP and the Microsoft SQL 20005/2008 MP's.
BUT...
The "Windows Operating System" colummn for every server I have installed the agent on so-far just reports "Not monitored"
I don't understand this. Did some searching around, its not that silly 3-day NETBIOS thing because these servers I am attempting to monitor have never previously had this client installed onto them
Anyone suffer this previously and can offer ideas or solutions? Thanks. If I cannot get this working to monitor the Windows OS this product is not fit for purpose.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found the answer
If you want to avoid the rambling go to the bottom of this post for the advice ;-)
Hi SterlingDev,
As far as what SCCM does (it's about the same as Landesk and other 3rd party products) but it also pulls together WSUS, MDT, PXE, WDS.
I am one person controlling all client software installations, Operating system deployments (both side-by-side and Wake on Lan refreshes during the night) , Software updates, for 500 desktop machines.
It takes a long time to learn because it is so huge. In my experience, and this doesnt only apply to SCCM, anyone shooting a product down in flames like this just hasn't had the time to learn it due to the pressure of time constraints... One of the biggest things SCCM has done for this firm is to introduce control to deployments. "Requests For Change" are now part of life here and "flying by the seat of your pants" is long forgotten
Trust me - SCCM is worth learning! It may take up to a 6 months to get the hang of it!
--------------------------
The SCCM Technet flowcharts are pretty comprehensive and a good place to start!
http://technet.microsoft.com/en-us/library/bb680531.aspx