Active directory integration and changing the the secondary management server
At my company I'm using AD integration for the assigment of agents to a primary management server and fallback management server. I had one primary server assigned (MS1) with two manually assigned fallback management servers (MS2 and MS3). This week I have to scratch one of the fallback servers (MS3). As it is impossible to edit this with the console I did a remove of the configuration and redefined it with primary server MS1 and fallback server MS2. I was surprised by the fact that all agents did generate a Health Service Heartbeat Failure alert and I had to restart the health service on the MS1 and all agents to solve this. My question: what is the best procedure when using AD integration and one of the management servers used in the AD assignment rules needs to be scratched or an update is needed in the assignment of Primary or Secondary management server without the risk that the agents are not monitored during a certain period of time ? Roland Roland
December 8th, 2010 3:07pm

Hi, To remove a management server from computer, I would like to share the following article. It has detailed steps about how to do it: How to Remove a Management Server From a Computer in Operations Manager 2007: http://technet.microsoft.com/en-us/library/cc540378.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2010 1:27am

Does not answer my question: how to change the failover management servers when using AD integration without the risk the target agents are becoming unmonitoredRoland
December 10th, 2010 1:37pm

Hi, Might be irrelevant regarding the heartbeat alert creation but why don't you assign the failover servers through AD integration also? On what point exactly did the HB alerts get created? Did you check one of the agent logs what it was actually doing and why it didn't failover to another management server? Or was it only that the alerts were created but no failovers happened? -TeroMCT | MCSE | MCITP | MCTS SCOM, SCCM, SCVMM, SCDPM
Free Windows Admin Tool Kit Click here and download it now
December 11th, 2010 9:01pm

I had RMS, MS1, MS2 and MS3: in AD integration I had defined all agents to MS1 as primary server and MS2 and MS3 as fallback servers. I had to scratch MS3 so I thougth the best way was to adapt the AD integration : all agents to MS1 and only MS2 as fallback server. I checked before that all agents where assigned to MS1 as primary server At the moment I deleted the AD integration rule (no other way to change the fallback servers) and recreated it with all agents to MS1 as primary and only MS2 as fallback server all agents generated the alert and I had to restart the Health Management Service on all agents This week my MS3 will be available again and I wonder which steps I shouldtake to have again AD integration enabled withMS1 as primary and MS2 and MS3 as fallback without the risk of loosing the monitoring ogf the agents. RolandRoland
December 13th, 2010 3:02pm

Hi, Did you check from AD that the rules you defined actually had been updated correctly to AD before you turned off the ms3? Under AD tree, there is Operations Manager container and undert that there are containers and groups for your mgmt servers which the agents will read. AD replication interval, SCOM ad update schedule and agent ad update interval all affect the amount of time before the agents have gotten the updated information even though SCOM console will show it to you immediately. -TeroMCT | MCSE | MCITP | MCTS SCOM, SCCM, SCVMM, SCDPM
Free Windows Admin Tool Kit Click here and download it now
December 14th, 2010 7:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics