Is it still essential to keep Exchange Services group in Exchange 2003?

Is it still essential to keep Exchange Services group  in Exchange 2003? I mean can we just delete it?
LVL 1
SAM2009Asked:
Who is Participating?
 
AwinishConnect With a Mentor Commented:
Yes, you can delete it. The group is there, if you have performed an upgrade from exchange 5.5 to above.

Make sure that your Exchange Domain Servers and Exchange
Enterprise Servers groups are in the Users container in your Active
Directory.
0
 
Premkumar YogeswaranAnalyst II - System AdministratorCommented:
Hey,

Do you want ot delete, exchange adminisatrators group from AD...?

may i know the reason for deleting the exchnage group?

If you are deleting the exchange group with out delegating the correct access to other group or user.. you will find issue on opening the Exchange system manager console...

If you have deleted the account and need to get back the groups.. for that you can run forest prep in your domain to have the exchange service group back..

Thanks,
Prem
0
 
MegaNuk3Commented:
"Exchange Services", do you mean Exchange Servers?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
SAM2009Author Commented:
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.
0
 
SAM2009Author Commented:
I has just fixed my "SA service keep in starting state after reboot" problem by moving Exchange Services group in Users container so if I delete that group could I get the same prob again?
0
 
R--RConnect With a Mentor Commented:
The Exchange Services group is created during the installation of Active Directory Connector (ADC).

check this.
http://www.freelists.org/post/exchangelist/Exchange-Services-Group,5
0
 
MegaNuk3Connect With a Mentor Commented:
If you no longer have an Exchange 5.5 environment and don't use the ADC, then set your Exchange Org to Native and delete the Exchange Services group. Otherwise just leave it in the users container and forget about it.
0
 
SAM2009Author Commented:
Thanks for all your advices. Because there is no issue so I will leave Exchange Services group in Users container.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.