Moved my Exchange 2003 SP2 server out of the AD "Computers" and started to get these messages every ten minutes. I understand from other KB articles it about the name of the computer changing when I moved it out of the OU. I have moved the Exchange computer back to the "Computers" OU. My question this is a busy server and I would rather not restart the System Attendant service until after the first of 2010 when we have our planned server maintenance. Everyone seems to be accessing their email from the server with no problems for a few days now. Can the restart of the service wait the next few weeks or will other problems occur even though I moved the computer back to the original OU and have verified it's membership in the Exchange Domain Server and Exchange Enterprise server groups?Thanks,Robert

Hi Robert, According to following KB: http://support.microsoft.com/kb/271335/en-us The Event is logged because the DN is changed after moving Exchange Server to another OU and the DN is cached by System Attendant service. Therefore, we need to restart SA service to refresh the Cache. Nevertheless, as you have moved the Exchange Server back to “Computers”, I think that two events are not logged currently. If I am off base, please let me know. Regarding whether you will encounter other problems, I would like to explain that it is hard to say as the recommended method by Microsoft is to restart SA service. Nevertheless, as server works well currently, I think that you can keep monitor the issue and restart SA service when you have opportunity. Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Mike,Thanks so much for your response. We are only a small single Standard edition server site and client connectivity to the server and mail is flowing with no issues. I'm thinking this cached group membership might be a urgent issue in a larger install. Since I moved the server back to it's original "Computers" OU and confirmed the group membership the messages are still being generated in the app log but that is all. No other issues. When we do the server maintenance the first weekend of Jan 2010 I will update and reboot the server. I just wanted to make sure there was no ticking time bomb so to speak that others like yourself have observed. If you and others are interested I would be pleased to follow up and let you know.Thanks again for the input.Robert