Ad isn't a mess it's quite clean now, once a split happens I guess you could consider it a mess but I've done worst and never had any Ill effects. The Exchange org.. I'm still wondering on. We just had a Health check from MS on it and got the thumbs up. But as I stated in order to get the email address' Correct we have to uncheck the automatic. OWA is keyed off the Primary (or first) email address in the setup (yes we have setup new sites and it still falls backt o the primary). Here is an example
If you have the following (remember your talkin exchange 2000 because 2007 is still a slave to it) Default policy = name @1.com Smtp Policy 2 = name @a.1.com Smtp Policy 3 = name @b.com Smtp Policy 4 = name @a.b.com Etc.. for 19 of these OWA only works off the default policy (this is how it was back in the exchange 5.5 days) so if you get rid of the name @1.com OWA fails to work. I've setup new OWA web sites pointing to name @a.1.com etc..etc.. but they do not work either without the default smtp address being on the account. (remember where I've said MS has given us the thumbs up) I still question how this could be with such a problem. On our Test domain where I have installed just 1 Exchange 2000/2003/2007 server. (note: not 1 each just 1 each time for testing currently it is a 2007 server) I can get the OWA site to work off any of the Policies as advertised. I'm being told it's the upgraded org from Exchange 5.5 that has caused this mess. (and here again we get a thumbs up from MS GRRR) We have set all accounts to not update automatically, but when I move someone from 2000 to 2007 it get's checked again. From the sounds of it I should just install a 3rd 2007 server and get rid of our 2000 servers faster. Maybe 2007 will help with the Policy problem... -----Original Message----- From: Troy Meyer [mailto:troy.me...@monacocoach.com] Sent: Monday, January 19, 2009 11:32 AM To: MS-Exchange Admin Issues Subject: RE: Dueling Exchange server Jim, Its sounds like you have already laid out the groundwork, but you still cant install a separate exchange org in the same domain. To each their own, but if your AD is a mess and you have issues from a 5.5 conversion still haunting you, wouldn't you want to move to a clean fresh AD? This is like a gift all tied up in ribbon; Directories stay around for a loooong time, being able to start over for a new spin-off company that would be the absolute best way to go. (end sales pitch) BUT it sounds like you have other issues. Why would you have to uncheck automatically update email addresses, this has nothing to do with how many email addresses your org has (we have about 15 suffixes covering 4 different companies). That is what email address policies are for. If you choose not to use policies and manually set that flag, do it in powershell where you could do it to your entire org with one line (get-mailbox * | set-mailbox -emailaddresspolicyenabled:$false) note: I would not do my entire org in one line. What exactly is your OWA bug/issue (it sounds like you are ranting here, but if you expand a bit, perhaps its something fixable? -troy -----Original Message----- From: Martin, Jim P [mailto:jmar...@clinitech.net] Sent: Monday, January 19, 2009 8:30 AM To: MS-Exchange Admin Issues Subject: RE: Dueling Exchange server This is where I disagree, we are running a dummy domain now as our root so 1.a.com and 2.a.com can keep the root domain and the child domain without issue. Once the split happens 1 side will have a root domain controller (fsmo etc..) and a child domain. The other will have to seize rolls on the root domain controller (fsmo etc..) and the child domain controllers. Clean up is simply asdiedit out the "other" sites domain controllers. As for renaming the Domain we could care less, it's a dummy anyway (2003 AD native mode). We have setup alias for our Organization inside Ad so people can logon properly I.e. j...@abc.corp they will stay with each org. My biggest issue is the Exchange org has been around and upgraded from Exchange 5.5 and it's a mess. Moving to an new domain to clean It up would never fly it took 5 years (1999 - 2004) to get on AD. I'd really like to be able to install a new Exchange server and not have it touched by all the old policies and what not sitting around from the upgraded one. MS has been through our Exchange servers and say nothing is wrong. While I would agree they work, having to uncheck on every user "Automatically update e-mail addresses based on e-mail address policy" SUCKS. We have 19 email address, depending on who/what/where you are is what you get. Also the bug in OWA for email is still a killer I think it's due to our policies though MS still says everything is fine... -----Original Message----- From: Michael B. Smith [mailto:mich...@theessentialexchange.com] Sent: Friday, January 16, 2009 4:38 PM To: MS-Exchange Admin Issues Subject: RE: Dueling Exchange server What he said. I've been involved in several divestitures over the years where they split the root domain controllers and each side took one. Typically, the next question is "how do I change the name of this domain?" The REAL answer is: you can't. Therefore, go ahead and plan for a forest migration now. Test it, learn your tools, get used to it. Buy something from Quest or learn ADMT really well. Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Troy Meyer [mailto:troy.me...@monacocoach.com] Sent: Friday, January 16, 2009 4:38 PM To: MS-Exchange Admin Issues Subject: RE: Dueling Exchange server Jim, I don't think you can have separate Exchange orgs in the single forest. That being said, why would you want it? If you separate companies, wont you be creating a new forest and domain structure for at least one if not both companies? Since you will most likely be migrating user accounts and mailboxes to a new domain, why not either create the domain now and prepare it for migration OR leave the exchange infrastructure as-is and simple move mailboxes to servers in the domains\sites they should be in so they are ready to be moved to the new forest/domain structure. If you were thinking of just taking 2.a.com and leaving it as is at a new location, it will still look for 1.a.com and a.com. While you could most likely remove the 1.a.com references, you can't take away the references to the top level domain a.com. It sounds like it might be effort saving to meet with the folks supporting both domains and set out a long term plan for both infrastructures. hth -troy -----Original Message----- From: Martin, Jim P [mailto:jmar...@clinitech.net] Sent: Friday, January 16, 2009 12:13 PM To: MS-Exchange Admin Issues Subject: Dueling Exchange server I have been hesitant to ask but here goes. Let me lay some ground work before I get into what I'd like to do with exchange. We have a Root Domain A.com with 2 child domains 1.A.com and 2.a.com the Root domain is empty of users and only has 2 Servers in it both domain controllers for A.com. We have 2 Exchange servers in 1.A.com Exchange 2000 and Exchange 2007 with 5 Domain controllers in 1.a.com site. We have 2 Exchange servers in 2.A.com Exchange 2000 and Exchange 2007 with 5 Domain controllers in 2.a.com site. Everything works just fine there are no issues except. Some day in the next 1 - 2 years 1.A.Com and 2.A.com will become separate companies. So I've been asked if I can introduce new Exchange servers with NEW email address, to a New connection. But keep it all wrapped up in the existing AD structure. Because when we split 1 of the A.com controllers will stay with 1.a.com and 1 will stay with 2.a.com. We will just do some clean up in AD ridding ourselves of the other. 1 of the clean up tasks will be to move the MX records/users mailbox and such but when we do that we want it all on the "new" exchange server. So the question Is there a way to install a new exchange server 2007 into its own not "connecting" it to the existing Servers. I have no issues with making another site or sub domain to make it work i.e. z.1.a.com Any suggestion ---------------------------------------------------------------------------- -- This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy the message. ============================================================================ == ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ------------------------------------------------------------------------------ This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy the message. ============================================================================== ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ------------------------------------------------------------------------------ This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy the message. ============================================================================== ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
