| Author |
Message |
Brandon
Guest
|
Posted:
Fri Nov 04, 2005 1:50 am Post subject:
Agent computer not on same domain as MOM server |
|
|
I have a mom server that is in our primary domain, and then I have an SMTP
server that is in a seperate workgroup. It has no affiliation with the
domain, but it is on the same network as the mom server. I cannot do a push
install, says access denied. I can do a manual install of the agent, but it
never show up in the MOM console, and never receives any information. Does
anyone know how I can get this to work. The message that comes up in the
event log which I think may be related is this...
'The Agent could not load any cached configuration information. This error
may occur when the configuration cache file is not present (which will be the
case when an agent/server gets installed for the first time), or when the
file becomes corrupted.
Management Group: PMTS
The Agent will not process data until it successfully retrieves
configuration information.'
Thanks for any assistance |
|
| Back to top |
|
 |
David Tyra
Guest
|
Posted:
Fri Nov 04, 2005 9:51 am Post subject:
Re: Agent computer not on same domain as MOM server |
|
|
Brandon,
Push installation will not work to servers in a workgroup or non-trusted
domain, but manual installation will work as you saw. Check to make sure
that the mutual authentication is not enabled in Global Settings. If it is,
workgroup agents would not be able to communicate since they can't
participate in mutual authentication.
Regards,
David Tyra
"Brandon" <Brandon@discussions.microsoft.com> wrote in message
news:5B36713A-E070-40DB-9CDA-D4209A048870@microsoft.com...
| Quote: | I have a mom server that is in our primary domain, and then I have an SMTP
server that is in a seperate workgroup. It has no affiliation with the
domain, but it is on the same network as the mom server. I cannot do a
push
install, says access denied. I can do a manual install of the agent, but
it
never show up in the MOM console, and never receives any information.
Does
anyone know how I can get this to work. The message that comes up in the
event log which I think may be related is this...
'The Agent could not load any cached configuration information. This error
may occur when the configuration cache file is not present (which will be
the
case when an agent/server gets installed for the first time), or when the
file becomes corrupted.
Management Group: PMTS
The Agent will not process data until it successfully retrieves
configuration information.'
Thanks for any assistance
|
|
|
| Back to top |
|
 |
Brandon
Guest
|
Posted:
Fri Nov 04, 2005 5:51 pm Post subject:
Re: Agent computer not on same domain as MOM server |
|
|
Thanks for your reply David,
I disabled mutual authentication, and then re-installed the MOM client on
the workgroup machine, and I still can't see it in the console.
"David Tyra" wrote:
| Quote: | Brandon,
Push installation will not work to servers in a workgroup or non-trusted
domain, but manual installation will work as you saw. Check to make sure
that the mutual authentication is not enabled in Global Settings. If it is,
workgroup agents would not be able to communicate since they can't
participate in mutual authentication.
Regards,
David Tyra
"Brandon" <Brandon@discussions.microsoft.com> wrote in message
news:5B36713A-E070-40DB-9CDA-D4209A048870@microsoft.com...
I have a mom server that is in our primary domain, and then I have an SMTP
server that is in a seperate workgroup. It has no affiliation with the
domain, but it is on the same network as the mom server. I cannot do a
push
install, says access denied. I can do a manual install of the agent, but
it
never show up in the MOM console, and never receives any information.
Does
anyone know how I can get this to work. The message that comes up in the
event log which I think may be related is this...
'The Agent could not load any cached configuration information. This error
may occur when the configuration cache file is not present (which will be
the
case when an agent/server gets installed for the first time), or when the
file becomes corrupted.
Management Group: PMTS
The Agent will not process data until it successfully retrieves
configuration information.'
Thanks for any assistance
|
|
|
| Back to top |
|
 |
Brandon
Guest
|
Posted:
Fri Nov 04, 2005 9:51 pm Post subject:
Re: Agent computer not on same domain as MOM server |
|
|
Yes, I did commit the changes, then re-installed. I am using none for the
control, and local system as the other options. I have also tried installing
with Full control, still with no luck.
I see the same error about config information on the agent machine, but I
don't see anything on the MOM server.
"davidtyra@hotmail.com" wrote:
| Quote: | Brandon,
Did you commit configuration changes after disabling mutual
authentication? You will need to do this if you haven't and then try to
reinstall the MOM agent again.
Regards,
David Tyra
|
|
|
| Back to top |
|
 |
davidtyra@hotmail.com
Guest
|
Posted:
Fri Nov 04, 2005 9:51 pm Post subject:
Re: Agent computer not on same domain as MOM server |
|
|
Brandon,
Make sure your management server is not set to reject manual agent
installs in Global Settings in the Admin Console. Make sure that you
can telnet to port 1270 on the management server from this agent. Other
than that I am about out of ideas...
Regards,
David Tyra |
|
| Back to top |
|
 |
davidtyra@hotmail.com
Guest
|
Posted:
Fri Nov 04, 2005 9:51 pm Post subject:
Re: Agent computer not on same domain as MOM server |
|
|
Brandon,
Did you commit configuration changes after disabling mutual
authentication? You will need to do this if you haven't and then try to
reinstall the MOM agent again.
Regards,
David Tyra |
|
| Back to top |
|
 |
Brandon
Guest
|
Posted:
Fri Nov 04, 2005 9:51 pm Post subject:
Re: Agent computer not on same domain as MOM server |
|
|
Looks like it's working now. Mutual authenitcaion is set to none on the
agent, and off on the MOM console.
Try trick was, even though you commit changes, I had to restart the MOM
service on the management server.
"davidtyra@hotmail.com" wrote:
| Quote: | Brandon,
Make sure your management server is not set to reject manual agent
installs in Global Settings in the Admin Console. Make sure that you
can telnet to port 1270 on the management server from this agent. Other
than that I am about out of ideas...
Regards,
David Tyra
|
|
|
| Back to top |
|
 |
|
|
|
|