Clients non monitored in MOM Workgroup Edition

Just wanted to clarify my understanding. MOM workgroup edition only monitors servers and not any clients?
LVL 1
habanagoldAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Stephen MandersonSoftware EngineerCommented:
That is correct it only monitors upto 10 Servers

Regards
Steve
wwwallyCommented:
Hello habanagold,

MOM workgroup can monitor servers and client.
The maximum of ten is only for the maximum deployed agents.
You can deploy a maximum of ten agents it does not matter if it a server or an client.

Good Luck,

Walter
habanagoldAuthor Commented:
It won't install on a client that I have.
Fundamentals of JavaScript

Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.

habanagoldAuthor Commented:
The MOM Server failed to perform specified operation on computer "workstation.domain.com".
 
Error Code: 5
Error Description: Access is denied.

I have upgraded MOM WE to SP1 which Technet stated would resolve this problem but it hasn't. I have attemtped to install the agent manually on the workstation but it does not show up in the MOM database as a "Agent-Managed" comuter. It does show up as an "Unmanaged Computer".

This is the basis for my original question. DOES MOM WE allow you to manage workstations? The documentation uses the term 10 "Servers" and unfortunately these noted technical experts tend to use terms haphazardly so that is why I was asking since the workstation installation is having issues?

So please, if someone knows beyond a shadow of doubt or can point me to confirming wherther workstations can be monitored with MOM WE, please don't guess as I have 2 points of view already that contradict each other.

IF it does allow you to monitor Workstations, then what could be the problem?
wwwallyCommented:
Here is a guide for deploying agents to servers and workstations.
http://www.microsoft.com/technet/prodtechnol/mom/mom2005/Library/cfe88cdd-e733-451e-852e-21e579233a4b.mspx?mfr=true

check if the latest windows installer is installed on the workstation .

Good luck,

Walter

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
habanagoldAuthor Commented:
Thanks, I'll check it out. I did get confirmation from Microsoft via their newsgroup that workstations are supported under the MOM Workgroup Edition. So, my focus has now changed to the problem I am having installing the agent on the workstation. It is a permissions issue I'm sure but where, I don't know.
wwwallyCommented:
Here is part of a technet article, perhaps its relevant (source link is below).

When you use the Install Agent Wizard to install a Microsoft Operations Manager (MOM) 2005 agent on an unmanaged computer, you receive the following error message:
The MOM Server could not access registry key or value 'SYSTEM\CurrentControlSet\Control \Session Manager\Environment' on computer unmanaged computer name.

Error code: 5

Error Description: Access is denied.
If you use computer discovery to install an agent, event ID 21034 is logged in the Application log on the computer that is running MOM Management Server. A corresponding alert appears in the MOM 2005 Operator console.
 Back to the top

CAUSE
This problem occurs when the following conditions are true:• MOM Management Server is installed on a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1).
• The server's action account does not have administrative credentials on the destination computer.

 Back to the top

RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Operations Manager 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

http://support.microsoft.com/kb/895195/

Good luck,

Walter
habanagoldAuthor Commented:
Unfortunately, I did review that technet note and did apply the service pack thinking I was home free but alas, this did not solve the problem. I believe I did state that in my post of Date: 09/12/2006 11:53AM EDT
habanagoldAuthor Commented:
Finally go around to using the tip from http://www.microsoft.com/technet/prodtechnol/mom/mom2005/Library/cfe88cdd-e733-451e-852e-21e579233a4b.mspx?mfr=true that stated to

Agent Installation Fails Due to Security Settings
In an Active Directory environment, mutual authentication between agents and the MOM Server is required by default. If mutual authentication is not enabled during agent installation, the installation fails.

Solution
To resolve agent installation failures caused by mutual authentication settings during manual agent installation, click Yes in the dialog box that asks whether mutual authentication is required.

If you do not want to use mutual authentication, you can disable it.

To disable mutual authentication
1. In the MOM Administrator console, expand Administration and then click Global Settings.
 
2. On the Administration pane, select Global Settings.
 
3. Select the Security tab, and clear the check box in the Mutual Authentication Required field.
 
4. Right-click the management pack folder, and click Commit Configuration Change.
 
5. Restart the MOM Service on all Management Servers in the management group.
 
This worked on the workstation but I did add the MOM account to the adminstrators group on the workstation when I did this. I perhaps would not have needed to do this if I would have specified a domain admin account when I ran the Agent install wizard. That's what I did with a server. At any rate the above steps appeared to have resolved the problem. Curious why I needed to do this though.
habanagoldAuthor Commented:
I should note that I did install the SP for MOM WE as well so I would say that should be involved in the troubleshooting process for anyone else experiencing this situation.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.