RE: Exchange Design Recomendation
I know. Its more political than anything else. From: Michael B. Smith [mailto:mich...@owa.smithcons.com] Sent: Tuesday, October 27, 2009 3:42 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Design Recomendation That doesn't require a subdomain. It simply requires that you put a particular user as a local administrator on the Exchange server and delegate them permissions for a particular OU full of users. Really, truly, there are rarely reasons for subdomains anymore. From: Mayo, Shay [shay.m...@absg.com] Sent: Tuesday, October 27, 2009 2:04 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Design Recomendation For the most part, we want them to be able to fully admin their exchange servers. I think we want them to be able to manage their servers but make sure they can't screw up the entire org. From: Don Ely [mailto:don@gmail.com] Sent: Tuesday, October 27, 2009 11:23 AM To: MS-Exchange Admin Issues Subject: Re: Exchange Design Recomendation What kind of management is required on the Exchange servers is required by the admins in the sister company? On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay mailto:shay.m...@absg.com>> wrote: We are about to merge our 2000 user sister company into our Active Directory. We have always had a single domain architecture and now are wanting to move to a multidomain architecture so the sister company's admins can still manage their resources. So I am looking for design ideas. I think the best approach would be to install all of the exchange servers in the same domain and delegate administration to certain Exchange servers to the sister company admins, but I have to present other approaches such as installing the sister company's Exchange servers in their sub domain and discuss why this would or wouldn't be a good idea. So if anyone has any input or can point me to a good article, it would be greatly appreciated! This will be all Exchange 2007 servers. Shay CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege. CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege. CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege.
Re: Exchange Design Recomendation
Exactly On 10/27/09, Michael B. Smith wrote: > That doesn't require a subdomain. > > It simply requires that you put a particular user as a local administrator > on the Exchange server and delegate them permissions for a particular OU > full of users. > > Really, truly, there are rarely reasons for subdomains anymore. > > > From: Mayo, Shay [shay.m...@absg.com] > Sent: Tuesday, October 27, 2009 2:04 PM > To: MS-Exchange Admin Issues > Subject: RE: Exchange Design Recomendation > > For the most part, we want them to be able to fully admin their exchange > servers. I think we want them to be able to manage their servers but make > sure they can’t screw up the entire org. > > From: Don Ely [mailto:don@gmail.com] > Sent: Tuesday, October 27, 2009 11:23 AM > To: MS-Exchange Admin Issues > Subject: Re: Exchange Design Recomendation > > What kind of management is required on the Exchange servers is required by > the admins in the sister company? > On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay > mailto:shay.m...@absg.com>> wrote: > > We are about to merge our 2000 user sister company into our Active > Directory. We have always had a single domain architecture and now are > wanting to move to a multidomain architecture so the sister company’s admins > can still manage their resources. So I am looking for design ideas. > > I think the best approach would be to install all of the exchange servers in > the same domain and delegate administration to certain Exchange servers to > the sister company admins, but I have to present other approaches such as > installing the sister company’s Exchange servers in their sub domain and > discuss why this would or wouldn’t be a good idea. > > So if anyone has any input or can point me to a good article, it would be > greatly appreciated! > > > This will be all Exchange 2007 servers. > > Shay > > > CONFIDENTIALITY NOTICE. This electronic mail transmission may contain > privileged and/or confidential > > information and is intended only for the review of the party to whom it is > addressed. If you have > > received this transmission in error, please immediately return it to the > sender, delete it and destroy > > it without reading it. Unintended transmission shall not constitute the > waiver of the attorney-client > > or any other privilege. > > > CONFIDENTIALITY NOTICE. This electronic mail transmission may contain > privileged and/or confidential > information and is intended only for the review of the party to whom it is > addressed. If you have > received this transmission in error, please immediately return it to the > sender, delete it and destroy > it without reading it. Unintended transmission shall not constitute the > waiver of the attorney-client > or any other privilege. > > -- Sent from my mobile device
RE: Exchange Design Recomendation
That doesn't require a subdomain. It simply requires that you put a particular user as a local administrator on the Exchange server and delegate them permissions for a particular OU full of users. Really, truly, there are rarely reasons for subdomains anymore. From: Mayo, Shay [shay.m...@absg.com] Sent: Tuesday, October 27, 2009 2:04 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Design Recomendation For the most part, we want them to be able to fully admin their exchange servers. I think we want them to be able to manage their servers but make sure they can’t screw up the entire org. From: Don Ely [mailto:don@gmail.com] Sent: Tuesday, October 27, 2009 11:23 AM To: MS-Exchange Admin Issues Subject: Re: Exchange Design Recomendation What kind of management is required on the Exchange servers is required by the admins in the sister company? On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay mailto:shay.m...@absg.com>> wrote: We are about to merge our 2000 user sister company into our Active Directory. We have always had a single domain architecture and now are wanting to move to a multidomain architecture so the sister company’s admins can still manage their resources. So I am looking for design ideas. I think the best approach would be to install all of the exchange servers in the same domain and delegate administration to certain Exchange servers to the sister company admins, but I have to present other approaches such as installing the sister company’s Exchange servers in their sub domain and discuss why this would or wouldn’t be a good idea. So if anyone has any input or can point me to a good article, it would be greatly appreciated! This will be all Exchange 2007 servers. Shay CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege. CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege.
Re: Exchange Design Recomendation
But what does fully admin mean to you? Is it create and manage users? Do you want them creating transport rules? Do you just want them to be able start and stop services? What is it you want them to have the ability to do? I work with around 20 IT staff that have the ability to "manage?admin" exchange in a way that fits within the organizations needs. Do they have full, carte blanche access? Nope, not in a million years. But they have a level of admin access that they feel is full admin access to them... On Tue, Oct 27, 2009 at 11:04 AM, Mayo, Shay wrote: > For the most part, we want them to be able to fully admin their exchange > servers. I think we want them to be able to manage their servers but make > sure they can’t screw up the entire org. > > > > *From:* Don Ely [mailto:don@gmail.com] > *Sent:* Tuesday, October 27, 2009 11:23 AM > *To:* MS-Exchange Admin Issues > *Subject:* Re: Exchange Design Recomendation > > > > What kind of management is required on the Exchange servers is required by > the admins in the sister company? > > On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay wrote: > > > > We are about to merge our 2000 user sister company into our Active > Directory. We have always had a single domain architecture and now are > wanting to move to a multidomain architecture so the sister company’s admins > can still manage their resources. So I am looking for design ideas. > > > > I think the best approach would be to install all of the exchange servers > in the same domain and delegate administration to certain Exchange servers > to the sister company admins, but I have to present other approaches such as > installing the sister company’s Exchange servers in their sub domain and > discuss why this would or wouldn’t be a good idea. > > > > So if anyone has any input or can point me to a good article, it would be > greatly appreciated! > > > > > > This will be all Exchange 2007 servers. > > > > Shay > > > > CONFIDENTIALITY NOTICE. This electronic mail transmission may contain > privileged and/or confidential > > information and is intended only for the review of the party to whom it is > addressed. If you have > > received this transmission in error, please immediately return it to the > sender, delete it and destroy > > it without reading it. Unintended transmission shall not constitute the > waiver of the attorney-client > > or any other privilege. > > > > CONFIDENTIALITY NOTICE. This electronic mail transmission may contain > privileged and/or confidential > information and is intended only for the review of the party to whom it is > addressed. If you have > received this transmission in error, please immediately return it to the > sender, delete it and destroy > it without reading it. Unintended transmission shall not constitute the > waiver of the attorney-client > or any other privilege. > >
RE: Exchange Design Recomendation
For the most part, we want them to be able to fully admin their exchange servers. I think we want them to be able to manage their servers but make sure they can't screw up the entire org. From: Don Ely [mailto:don@gmail.com] Sent: Tuesday, October 27, 2009 11:23 AM To: MS-Exchange Admin Issues Subject: Re: Exchange Design Recomendation What kind of management is required on the Exchange servers is required by the admins in the sister company? On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay mailto:shay.m...@absg.com>> wrote: We are about to merge our 2000 user sister company into our Active Directory. We have always had a single domain architecture and now are wanting to move to a multidomain architecture so the sister company's admins can still manage their resources. So I am looking for design ideas. I think the best approach would be to install all of the exchange servers in the same domain and delegate administration to certain Exchange servers to the sister company admins, but I have to present other approaches such as installing the sister company's Exchange servers in their sub domain and discuss why this would or wouldn't be a good idea. So if anyone has any input or can point me to a good article, it would be greatly appreciated! This will be all Exchange 2007 servers. Shay CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege. CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege.
Re: Exchange Design Recomendation
What kind of management is required on the Exchange servers is required by the admins in the sister company? On Tue, Oct 27, 2009 at 7:41 AM, Mayo, Shay wrote: > > > We are about to merge our 2000 user sister company into our Active > Directory. We have always had a single domain architecture and now are > wanting to move to a multidomain architecture so the sister company’s admins > can still manage their resources. So I am looking for design ideas. > > > > I think the best approach would be to install all of the exchange servers > in the same domain and delegate administration to certain Exchange servers > to the sister company admins, but I have to present other approaches such as > installing the sister company’s Exchange servers in their sub domain and > discuss why this would or wouldn’t be a good idea. > > > > So if anyone has any input or can point me to a good article, it would be > greatly appreciated! > > > > > > This will be all Exchange 2007 servers. > > > > Shay > > > > CONFIDENTIALITY NOTICE. This electronic mail transmission may contain > privileged and/or confidential > information and is intended only for the review of the party to whom it is > addressed. If you have > received this transmission in error, please immediately return it to the > sender, delete it and destroy > it without reading it. Unintended transmission shall not constitute the > waiver of the attorney-client > or any other privilege. > >
Exchange Design Recomendation
We are about to merge our 2000 user sister company into our Active Directory. We have always had a single domain architecture and now are wanting to move to a multidomain architecture so the sister company's admins can still manage their resources. So I am looking for design ideas. I think the best approach would be to install all of the exchange servers in the same domain and delegate administration to certain Exchange servers to the sister company admins, but I have to present other approaches such as installing the sister company's Exchange servers in their sub domain and discuss why this would or wouldn't be a good idea. So if anyone has any input or can point me to a good article, it would be greatly appreciated! This will be all Exchange 2007 servers. Shay CONFIDENTIALITY NOTICE. This electronic mail transmission may contain privileged and/or confidential information and is intended only for the review of the party to whom it is addressed. If you have received this transmission in error, please immediately return it to the sender, delete it and destroy it without reading it. Unintended transmission shall not constitute the waiver of the attorney-client or any other privilege.
