AD says that the server is a member of .../ou=Microsoft Security Groups /cn=Exchange Servers'; yet every10 minutesI receive this error: "Microsoft Exchange System Attendant failed to read the membership of the universal security group '/dc=com/dc=mydomain/ou=Microsoft Exchange Security Groups/cn=Exchange Servers'; the error code was '8007203a'. The problem might be that the Microsoft Exchange System does not have permission to read the membership of the group. If this computer is not a member of the group '/dc=com/dc=mydomain/ou=Microsoft Exchange Security Groups/cn=Exchange Servers', you should manually stop all Microsoft Exchange services, run the task 'add-ExchangeServerGroupMember,' and then restart all Microsoft Exchange services." I have not attempted the suggested resolution but I am doubtful it will help because AD shows membership. Any thoughts?

Try restarting the System Attendant on that Exchange server and see if that resolves it.

Did restarting the services fix the problem?

Actually, if you just restart the system attendant that should fix it.

Yes it did

Yes, thanks, that did stop the error. Any ideas why this occured?

I think the SA caches the server's distinguished name and if you move it to another location (another OU) the system attendant is looking in the group's membership for the old DN. IMHO, this is really a bug, albeit minor. I see this frequently when doing domain reorganization. It is annoying, but harmless.

Has anyone seen this as a result of a cluster failover? That appears to be the case here, but I'm not 100% sure.

Hi, We just got the same error when we moved our GC server roll to the new server. And after restarting System attendent the error disapeared Regards Roshan

After changing roles on DC's we had same error, indeedthe error dissapeared after restarting system attendant. thanks nav

Also got the same error when upgrading a 2003 domain controller to 2008. We did this to migrate the last remaining role (certificate authority) to a new 2008 DC. There were other DC's and this one did not have any FSMO's or other roles what so ever. Restarting the system attendanteliminated the error.Thanks, Don

Yep this happened to me to. Moved exchange servers to a new OU. Restarting the System Attendant on that Exchange servers olved it.