We are doing some integration with another company (we're all owned by the same parent compay). They are currently on Novel/Groupwise. My plan is to add setup a new DC and add a domain for this company (about 30 users) to our forest. Next, make the necessarry changes to exchange which include adding an additional accepted domain and editing the email address policy (they must retain their current email address). Our goal is to be able to have their contacts in our GAL and be able to see users free/busy data for either company. Does it sound like I'm on the right track or have I overlooked something? Thanks!

Why a new domain? Why not an OU in your existing domain? I can't imagine what compelling reason you would have for a new domain. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Mike Pietrorazio" wrote in message news:c4f833f0-9a60-4374-ba96-6036bb59caaf... We are doing some integration with another company (we're all owned by the same parent compay). They are currently on Novel/Groupwise. My plan is to add setup a new DC and add a domain for this company (about 30 users) to our forest. Next, make the necessarry changes to exchange which include adding an additional accepted domain and editing the email address policy (they must retain their current email address). Our goal is to be able to have their contacts in our GAL and be able to see users free/busy data for either company. Does it sound like I'm on the right track or have I overlooked something? Thanks! Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Fri, 25 Jun 2010 17:51:30 +0000, Mike Pietrorazio wrote: > > >We are doing some integration with another company (we're all owned by the same parent compay). "Integration" or "Migration"? >They are currently on Novel/Groupwise. My plan is to add setup a new DC and add a domain for this company (about 30 users) to our forest. Next, make the necessarry changes to exchange which include adding an additional accepted domain and editing the email address policy (they must retain their current email address). Our goal is to be able to have their contacts in our GAL and be able to see users free/busy data for either company. Does it sound like I'm on the right track or have I overlooked something? Thanks! You're not going to be accepting e-mail for their domain so I don't know why you'd want to add their domain as an "accepted domain". You're not going to be able to see their F/B info unless you have some sort of connector that can translate between the two different systems -- unless you make them use Exchange, or you publish your (and their) calendars to a common web site. Putting in a DC just for Contacts? No need. Just add them to your AD. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks for the replies. Maybe I should have provided more detail. We are taking them off of Novell and will need to do additional integration such as file sharing etc... Also, considering they are a remote location, a new domain with a DC at their location make both physical and logical sence. I also assumed that since we would be adding their mailboxes to our exchange server, we would need AD accounts from their domain to make this work while maintaing their current email namespace. Am I right?

You are wrong that a new domain makes both physical and logical sense, epsecially since you're starting their service from scratch. You are right that you will need an AD account for each mailbox. You are mistaken if you think that you need a new domain to have a different e-mail namespace. E-mail domains and AD domains do not have to have any relationship whatsoever. Again, you should just create an OU for them in your existing domain. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Mike Pietrorazio" wrote in message news:3115be60-50f7-4be1-91fd-a2a9847c17d0... Thanks for the replies. Maybe I should have provided more detail. We are taking them off of Novell and will need to do additional integration such as file sharing etc... Also, considering they are a remote location, a new domain with a DC at their location make both physical and logical sence. I also assumed that since we would be adding their mailboxes to our exchange server, we would need AD accounts from their domain to make this work while maintaing their current email namespace. Am I right?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Because they are a different company, It makes no sence to put them on our domain, with our namespace. For performance reasons it will make sense that they have their own DC at their location anyway. Perhaps it's not "necessary", but I can't think of a reason why this would be a bad idea. We already have 3 domains representing our 3 physical locations. As long as I know the exchange part will work with their unique address and being able to share free/busy/calendar information...

It's a bad idea because: - You are making a more complicated infrastructure than you need. - You will need more domain controllers. You shouldn't have less than two for any domain, and you'll need one in the same site as the Exchange server. - Best practice is to now start a design with a single domain and expand only when necessary. Nothing you have said points to any necessity for a separate domain. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Mike Pietrorazio" wrote in message news:9a8f3000-131e-4527-9030-9b11bbe73716... Because they are a different company, It makes no sence to put them on our domain, with our namespace. For performance reasons it will make sense that they have their own DC at their location anyway. Perhaps it's not "necessary", but I can't think of a reason why this would be a bad idea. We already have 3 domains representing our 3 physical locations. As long as I know the exchange part will work with their unique address and being able to share free/busy/calendar information... Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Let me add: - Exchange 2007 and 2010 management is more complicated with multiple domains. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Ed Crowley [MVP]" wrote in message news:e00785f2-b6c5-47f3-94ef-2429f9b52ce3... It's a bad idea because: - You are making a more complicated infrastructure than you need. - You will need more domain controllers. You shouldn't have less than two for any domain, and you'll need one in the same site as the Exchange server. - Best practice is to now start a design with a single domain and expand only when necessary. Nothing you have said points to any necessity for a separate domain. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." "Mike Pietrorazio" wrote in message news:9a8f3000-131e-4527-9030-9b11bbe73716... Because they are a different company, It makes no sence to put them on our domain, with our namespace. For performance reasons it will make sense that they have their own DC at their location anyway. Perhaps it's not "necessary", but I can't think of a reason why this would be a bad idea. We already have 3 domains representing our 3 physical locations. As long as I know the exchange part will work with their unique address and being able to share free/busy/calendar information... Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I appreciat the comments. I agree that for a small office a new domain is not necessarry, especaially with a RODC. Since this is for another company, management may give me no choice. My original question was regarding exchange, not the consideration of a new domain. I expect that whatever domain implimentation is used, exchange will perform the same, as long as it's all the same forest. Back to the original question... I creates accounts in "some" domain, add accepted domain, email address policy to exchange, I should be good to go for all email addresses (currenty/new company). Correct?

Yes. But you will want to be sure you have at least one and preferably two DCs for the new domain in the same site as your Exchange server. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Mike Pietrorazio" wrote in message news:ec020c04-cf90-4793-95bd-c1c1655c54d2... I appreciat the comments. I agree that for a small office a new domain is not necessarry, especaially with a RODC. Since this is for another company, management may give me no choice. My original question was regarding exchange, not the consideration of a new domain. I expect that whatever domain implimentation is used, exchange will perform the same, as long as it's all the same forest. Back to the original question... I creates accounts in "some" domain, add accepted domain, email address policy to exchange, I should be good to go for all email addresses (currenty/new company). Correct?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

One more thing--you will need to run Setup /PrepareDomain in in the new domain as well. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Ed Crowley [MVP]" wrote in message news:e3876403-68b5-4022-9cb6-4d2fa3561e3d... Yes. But you will want to be sure you have at least one and preferably two DCs for the new domain in the same site as your Exchange server. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." "Mike Pietrorazio" wrote in message news:ec020c04-cf90-4793-95bd-c1c1655c54d2... I appreciat the comments. I agree that for a small office a new domain is not necessarry, especaially with a RODC. Since this is for another company, management may give me no choice. My original question was regarding exchange, not the consideration of a new domain. I expect that whatever domain implimentation is used, exchange will perform the same, as long as it's all the same forest. Back to the original question... I creates accounts in "some" domain, add accepted domain, email address policy to exchange, I should be good to go for all email addresses (currenty/new company). Correct? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Upon further reflection, I feel compelled to ask why management would give you no choice. I've not known management to want to spend more money than it has to unless mahogany or executive jets are involved. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Mike Pietrorazio" wrote in message news:ec020c04-cf90-4793-95bd-c1c1655c54d2... I appreciat the comments. I agree that for a small office a new domain is not necessarry, especaially with a RODC. Since this is for another company, management may give me no choice. My original question was regarding exchange, not the consideration of a new domain. I expect that whatever domain implimentation is used, exchange will perform the same, as long as it's all the same forest. Back to the original question... I creates accounts in "some" domain, add accepted domain, email address policy to exchange, I should be good to go for all email addresses (currenty/new company). Correct?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks again. I'm aware of the multi-DC preference and domain prep involved. We currently have 3 domains in our forest so I've done this all before and it's fairly easy. We'll no doubt have multiple servers at the remote location so using Hyper-v to host an additional DC is an option and the only added cost would be an OS license. I'll be presenting management the option of using an existing domain and go from there. I'm anticipating being told to keep them as seperate as possible. It would be easier if they were just a branch of our company.

On Mon, 28 Jun 2010 11:34:08 +0000, Mike Pietrorazio wrote: >Thanks for the replies. Maybe I should have provided more detail. We are taking them off of Novell and will need to do additional integration such as file sharing etc... Also, considering they are a remote location, a new domain with a DC at their location make both physical and logical sence. Having a Global Catalog server in the remote location is a good idea. Depending on the number of users at the location and your need for them to log on if that one GC goes down you may want to have two GCs at the location. I'm not sure I buy into the idea of a new AD domain, though. You'll all be in the same AD forest, so why have separate domains? Will there be different GPOs? Different password policies? Different organization structures? Will AD objects such as mail-enabled groups be in all the domains? Do you expect users to manage the membership of the groups? What makes a new domain important or necessary? I've worked for companies that used that multi-domain forest design and it's usually done that way becasue of politics and turf battles. Everyone want to do things their own way and it can get pretty messy pretty fast unless you have some strong central management to rein in the empire builders. If you think you need multiple domains because you may sell a company then think hard about working with multiple AD forests and directory synchronization. It's more difficult, and expensive, than a single AD forest but cutting loose a company (and its forest) is a whole lot easier than exticating that company from its entanglement with a common forest and e-mail system. You also eliminate all those "we used to do it this way" and "this is the way it should be done" battles. >I also assumed that since we would be adding their mailboxes to our exchange server, we would need AD accounts from their domain to make this work while maintaing their current email namespace. Am I right? You'll certainly need an AD user account. A mailbox is managed with a set of properties owned by an AD user object (which is why you can only have one mailbox per user). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Mon, 28 Jun 2010 17:07:02 +0000, Mike Pietrorazio wrote: >I appreciat the comments. I agree that for a small office a new domain is not necessarry, especaially with a RODC. Since this is for another company, management may give me no choice. My original question was regarding exchange, not the consideration of a new domain. I expect that whatever domain implimentation is used, exchange will perform the same, as long as it's all the same forest. Exchange will work as well either way. It may not appear to work the same way to the people that use it or administer it. >Back to the original question... I creates accounts in "some" domain, add accepted domain, email address policy to exchange, I should be good to go for all email addresses (currenty/new company). Correct? Don't forget to prep the new domain with Exchange setup before you try doing anything. Other than that, what you stated is basically what you need to do. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP