| Author |
Message |
magnum42
Guest
|
 Posted:
Fri Oct 21, 2005 4:51 pm Post subject:
Client Domain change |
|
|
Hi,
A client for MOM 2005 was working fine. Now it changed from domain A (in
which are all of the other clients and the MOM server) to the domain B.
When I look in computers, I see it as unmanaged.
A created a new discovery rule to disover B\computer, launched a computer
discovery :
The task 'Agent Install and Discovery Task' is scheduled to run against
%MOMserv%
The task 'Computer Discovery' is scheduled to run against %MOMserv%
The task 'Push Agent Management Task' is scheduled to run against %MOMserv%
This last event many times ...
The following discovery rules did not match any computers
The MOM Server failed to open service control manager on computer
%computer%.%A-domain% / Access denied
The task 'Push Agent Task' has failed to execute against %A%\%computer%
It keeps on trying the old A domain and doesn't find any computers to match
the discovery. I'm sure that my discovery criteria is good. I can ping the
server, and if I "nbtstat" it, it returns the correct domain (B).
Also : I still have a pending action : uninstall agent A\computer which
keeps on getting access denied messages even if I give it correct logins,
since it wants to uninstall agent on A\computer, but now it's B:\computer.
Help !
Thanks. |
|
| Back to top |
|
 |
Microsoft MVP ¾¤¹ÅÀs for
Guest
|
| Posted:
Fri Oct 21, 2005 4:51 pm Post subject:
Re: Client Domain change |
|
|
Hello,
Thank you for your posting!
Please delete the computer first. You can also install the agent manually on
the computer, and then approve the manual installation in MOM Admin Console.
If you have any questions, please feel to let me know. I am glad to be of
assistance.
--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant
"magnum42" <magnum42@discussions.microsoft.com> wrote in message
news:88FA9461-89D3-4019-A596-AE4D37AD61FF@microsoft.com...
| Quote: | Hi,
A client for MOM 2005 was working fine. Now it changed from domain A (in
which are all of the other clients and the MOM server) to the domain B.
When I look in computers, I see it as unmanaged.
A created a new discovery rule to disover B\computer, launched a computer
discovery :
The task 'Agent Install and Discovery Task' is scheduled to run against
%MOMserv%
The task 'Computer Discovery' is scheduled to run against %MOMserv%
The task 'Push Agent Management Task' is scheduled to run against
%MOMserv%
This last event many times ...
The following discovery rules did not match any computers
The MOM Server failed to open service control manager on computer
%computer%.%A-domain% / Access denied
The task 'Push Agent Task' has failed to execute against %A%\%computer%
It keeps on trying the old A domain and doesn't find any computers to
match
the discovery. I'm sure that my discovery criteria is good. I can ping the
server, and if I "nbtstat" it, it returns the correct domain (B).
Also : I still have a pending action : uninstall agent A\computer which
keeps on getting access denied messages even if I give it correct logins,
since it wants to uninstall agent on A\computer, but now it's B:\computer.
Help !
Thanks.
|
|
|
| Back to top |
|
|
davidtyra@hotmail.com
Guest
|
| Posted:
Fri Oct 21, 2005 8:51 pm Post subject:
Re: Client Domain change |
|
|
Also, be sure you delete any computer discovery rule that is attemtping
to discover A\computer or you will continue to have problems. |
|
| Back to top |
|
|
Adam White
Guest
|
| Posted:
Mon Oct 24, 2005 6:24 am Post subject:
RE: Client Domain change |
|
|
I recommend uninstalling the MOM agent and deleting the discovery rule before
changing any part of a computer's FQDN. Then reinstall the agent afterwards.
- Adam
"magnum42" wrote:
| Quote: | Hi,
A client for MOM 2005 was working fine. Now it changed from domain A (in
which are all of the other clients and the MOM server) to the domain B.
When I look in computers, I see it as unmanaged.
A created a new discovery rule to disover B\computer, launched a computer
discovery :
The task 'Agent Install and Discovery Task' is scheduled to run against
%MOMserv%
The task 'Computer Discovery' is scheduled to run against %MOMserv%
The task 'Push Agent Management Task' is scheduled to run against %MOMserv%
This last event many times ...
The following discovery rules did not match any computers
The MOM Server failed to open service control manager on computer
%computer%.%A-domain% / Access denied
The task 'Push Agent Task' has failed to execute against %A%\%computer%
It keeps on trying the old A domain and doesn't find any computers to match
the discovery. I'm sure that my discovery criteria is good. I can ping the
server, and if I "nbtstat" it, it returns the correct domain (B).
Also : I still have a pending action : uninstall agent A\computer which
keeps on getting access denied messages even if I give it correct logins,
since it wants to uninstall agent on A\computer, but now it's B:\computer.
Help !
Thanks.
|
|
|
| Back to top |
|
|
magnum42
Guest
|
| Posted:
Mon Oct 24, 2005 4:51 pm Post subject:
Re: Client Domain change |
|
|
| Quote: | Please delete the computer first. You can also install the agent manually on
the computer, and then approve the manual installation in MOM Admin Console.
|
Yes, I was trying to delete it without success because it couldn't access it
to uninstall the MOM client.
I just found the solution today (it was simple) : "Force to Unmanaged
Management Mode...". Then I could delete it. The problem is I apparently lost
all the stats and all. But I don't think there was another solution. Was
there? |
|
| Back to top |
|
|
davidtyra@hotmail.com
Guest
|
| Posted:
Tue Oct 25, 2005 12:51 am Post subject:
Re: Client Domain change |
|
|
No, not really. The problem here is that the original agent can no
longer be contacted by the name that MOM has for it. Because of this,
you have to force the agent to unmanaged mode so you can delete it. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in