Does Exchange Services group still necessary in Exchange 2003? Can we just delete it?

On Mon, 29 Nov 2010 05:00:59 +0000, SAMATA wrote: >Does Exchange Services group still necessary in Exchange 2003? Can we just delete it? None of the Exchange services use that account, but what else might be using it only you can know. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I'm asking that question because my SA service stay in starting state when I reboot my Exchange 2003 and I realize this article http://support.microsoft.com/kb/910413 is applied to me: ---------------------------------------------------------------------------------------------------------------------------------- When the System Attendant service starts, it searches for the following groups in only the default Users container: Exchange Enterprise Servers Exchange Services Exchange Domain Servers If these groups are not in the default Users container, the System Attendant service determines that the groups do not exist. Therefore, if these groups are not in the Users container when you start the System Attendant service, the service does not start. ---------------------------------------------------------------------------------------------------------------------------------- The only grp in my case which is not in Users container is Exchange Services.

On Mon, 29 Nov 2010 05:25:43 +0000, SAMATA wrote: > > >I'm asking that question because my SA service stay in starting state when I reboot my Exchange 2003 and I realize this article http://support.microsoft.com/kb/910413 is applied to me: > >---------------------------------------------------------------------------------------------------------------------------------- > >When the System Attendant service starts, it searches for the following groups in only the default Users container: Exchange Enterprise Servers Exchange Services Exchange Domain Servers > >If these groups are not in the default Users container, the System Attendant service determines that the groups do not exist. Therefore, if these groups are not in the Users container when you start the System Attendant service, the service does not start. > >---------------------------------------------------------------------------------------------------------------------------------- > >The only grp in my case which is not in Users container is Exchange Services. Sorry. I misread the subject and took your question to be about an exchange service _account_. There's no Exchange Services group in Exchange 2003. The SA *not* starting isn't the same as the SA start not completing. The situation when the SA stays in the starting state can be cause by many things since the SA has many threads that perform tasks concurrently. Are there any events recorded in the Application Log or System Log? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, Yes, by default there is no Exchange Services in Exchange 2003. Most of the SA problems are caused by communication issue between DC/GC Server and Exchange Server. The Exchange SA service requires to communicate with the Domain Controllers/Global Catalog servers in the domain and would not be able to start if the DC/GCs are unreachable. 1. Run dcdiag and see if there's any errors. 2. If exchange server has firewall installed, please disable it for testing. 3. If there's two netword cards in exchange server, please disable the external network card then test to see if the issue persists. Please 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. Thanks Gen Lin-MSFT

Should I run DCDIAG just on GC DC or all DC in the subnet that Exchange can reach?

I run DCDIAG and there is no prob so I have to conclude that is du to "Exchange Services" was not on Users container. Thanks