tcinfo
asked on
Migration to Exchange 2010 with new DAG
Our current production environment is one Exchange 2007 - Version 8.3 (Build 83.6) running Hub Transport, Client Access, Mailbox roles. There's also a orphaned Exchange 2007 that was never used, it was virtual and got deleted without being uninstalled.
I have inherited the task of moving existing to Exchange 2010, and have 2 servers located at 2 physical sites connected via mpls circuit, same AD domain and forest. I have managed to get both servers running: Exchange Server 2010 SP2 -14.2.247.5 however one failed and the Mailbox role did not install, so need assistance getting that done assuming it's needed for a DAG, the goal being if one site server goes down were still up and running, also want Outlook Anywhere working.
It's not a large install, about 100 mailboxes but as can be expected, critical to the business. Thank you.
I have inherited the task of moving existing to Exchange 2010, and have 2 servers located at 2 physical sites connected via mpls circuit, same AD domain and forest. I have managed to get both servers running: Exchange Server 2010 SP2 -14.2.247.5 however one failed and the Mailbox role did not install, so need assistance getting that done assuming it's needed for a DAG, the goal being if one site server goes down were still up and running, also want Outlook Anywhere working.
It's not a large install, about 100 mailboxes but as can be expected, critical to the business. Thank you.
Amit
What is the error you are getting? Post it.
ASKER
From ExchangeSetupLog file:
[09/19/2013 14:26:39.0894] [2] Active Directory session settings for 'New-OwaVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'ANMDC01.domain.LOCAL', Preferred Global Catalog: 'DC01.domain.LOCAL', Preferred Domain Controllers: '{ DC01.domain.LOCAL }'
[09/19/2013 14:26:39.0894] [2] Beginning processing new-OwaVirtualDirectory -DomainController:'DC01.do
[09/19/2013 14:26:39.0894] [2] Searching objects "ANMEXCH2010.domain.LOCAL"
[09/19/2013 14:26:39.0894] [2] Previous operation run on domain controller 'ANMDC01.TELEMUS.LOCAL'.
[09/19/2013 14:26:39.0894] [2] Processing object "EXCH2010\owa".
[09/19/2013 14:26:40.0113] [2] Unexpected Error
[09/19/2013 14:26:40.0113] [2] The virtual directory 'owa' already exists under 'ANMEXCH2010.TELEMUS.LOCAL
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [2] Ending processing new-OwaVirtualDirectory
[09/19/2013 14:26:40.0113] [1] The following 1 error(s) occurred during task execution:
[09/19/2013 14:26:40.0113] [1] 0. ErrorRecord: The virtual directory 'owa' already exists under 'EXCH2010.domain.LOCAL/Def
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [1] 0. ErrorRecord: System.ArgumentException: The virtual directory 'owa' already exists under 'EXCH2010.domain.LOCAL/Def
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [1] The following error was generated when "$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
" was run: "The virtual directory 'owa' already exists under 'EXCH2010.domain.LOCAL/Def
Parameter name: VirtualDirectoryName".
[09/19/2013 14:26:40.0113] [1] The virtual directory 'owa' already exists under 'EXCHANGE2010.domain.LOCAL
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponen
[09/19/2013 14:26:40.0113] [1] Setup is stopping now because of one or more critical errors.
[09/19/2013 14:26:40.0113] [1] Finished executing component tasks.
[09/19/2013 14:26:40.0159] [1] Ending processing Install-ClientAccessRole
[09/19/2013 14:30:36.0869] [0] End of Setup
[09/19/2013 14:26:39.0894] [2] Active Directory session settings for 'New-OwaVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'ANMDC01.domain.LOCAL', Preferred Global Catalog: 'DC01.domain.LOCAL', Preferred Domain Controllers: '{ DC01.domain.LOCAL }'
[09/19/2013 14:26:39.0894] [2] Beginning processing new-OwaVirtualDirectory -DomainController:'DC01.do
[09/19/2013 14:26:39.0894] [2] Searching objects "ANMEXCH2010.domain.LOCAL"
[09/19/2013 14:26:39.0894] [2] Previous operation run on domain controller 'ANMDC01.TELEMUS.LOCAL'.
[09/19/2013 14:26:39.0894] [2] Processing object "EXCH2010\owa".
[09/19/2013 14:26:40.0113] [2] Unexpected Error
[09/19/2013 14:26:40.0113] [2] The virtual directory 'owa' already exists under 'ANMEXCH2010.TELEMUS.LOCAL
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [2] Ending processing new-OwaVirtualDirectory
[09/19/2013 14:26:40.0113] [1] The following 1 error(s) occurred during task execution:
[09/19/2013 14:26:40.0113] [1] 0. ErrorRecord: The virtual directory 'owa' already exists under 'EXCH2010.domain.LOCAL/Def
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [1] 0. ErrorRecord: System.ArgumentException: The virtual directory 'owa' already exists under 'EXCH2010.domain.LOCAL/Def
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [1] The following error was generated when "$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
" was run: "The virtual directory 'owa' already exists under 'EXCH2010.domain.LOCAL/Def
Parameter name: VirtualDirectoryName".
[09/19/2013 14:26:40.0113] [1] The virtual directory 'owa' already exists under 'EXCHANGE2010.domain.LOCAL
Parameter name: VirtualDirectoryName
[09/19/2013 14:26:40.0113] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponen
[09/19/2013 14:26:40.0113] [1] Setup is stopping now because of one or more critical errors.
[09/19/2013 14:26:40.0113] [1] Finished executing component tasks.
[09/19/2013 14:26:40.0159] [1] Ending processing Install-ClientAccessRole
[09/19/2013 14:30:36.0869] [0] End of Setup
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Reinstall the orphaned server even though it was never used? Was thinking that as well to keep AD clean correct?
Regarding 2010, it previously had a db copy on it, though no mailboxes actually moved to it. The previous admin didn't document any of the install attempts. is starting over the only way forward?
Regarding 2010, it previously had a db copy on it, though no mailboxes actually moved to it. The previous admin didn't document any of the install attempts. is starting over the only way forward?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran PS get-exchangeserver from our production 2007 server, it also listed a 2003 exchange server, going to the server I see Exchange 2003 installed but none of the services running.
I started the IS service and ran ESM - see 3 mailboxes:
Microsoft system attendant
SMTP
SystemMailbox
Did not give me a option to remove them, so I can uninstall Exchange 2003 from this server, do I need the other services running also? This has probably been sitting in the background for years now.
I started the IS service and ran ESM - see 3 mailboxes:
Microsoft system attendant
SMTP
SystemMailbox
Did not give me a option to remove them, so I can uninstall Exchange 2003 from this server, do I need the other services running also? This has probably been sitting in the background for years now.
Those are system mailboxes, so try removing Exchange using add/remove programs.
You will need the original media as well. The services don't need to be running though.
If the uninstall routine tells you there are mailboxes on the server it is NOT those, but some others (probably mail enabled accounts that have never been used).
Simon.
You will need the original media as well. The services don't need to be running though.
If the uninstall routine tells you there are mailboxes on the server it is NOT those, but some others (probably mail enabled accounts that have never been used).
Simon.
ASKER
Yes that was the message received with Add/Remove programs, is there a ps command to find the accounts? thanks. Sembee2, not looking forward starting over but I am sure you're right.
Oddly enough I heard Exchange 2007 compared to Vista but it works well. Where I see the benefit in 2010 to be DAG and Outlook Anywhere, so it should be time well spent, especially since we have the hardware ready.
Oddly enough I heard Exchange 2007 compared to Vista but it works well. Where I see the benefit in 2010 to be DAG and Outlook Anywhere, so it should be time well spent, especially since we have the hardware ready.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found one user and a system mailbox, removed Exchange attributes (the only option available) for the user and then had the option to remove Exchange.
Unfortunately it asked for Exchange 2003 Disc one which I don't have at the moment, plus the server is remote to me. I pointed to C:\program files\exchsrvr but it proceeded to report errors "setup failed while installing sub-component Microsoft Windows Active Directory schema update with error code 0xC1037986". I will try again after locate or create media.
Unfortunately it asked for Exchange 2003 Disc one which I don't have at the moment, plus the server is remote to me. I pointed to C:\program files\exchsrvr but it proceeded to report errors "setup failed while installing sub-component Microsoft Windows Active Directory schema update with error code 0xC1037986". I will try again after locate or create media.
You need the media - just pointing to the installed location isn't enough. Very annoying.
I have to keep a copy of the Exchange 2003 ISO to hand and grab it if I need it. Fortuantely it is only 200mb.
Simon.
I have to keep a copy of the Exchange 2003 ISO to hand and grab it if I need it. Fortuantely it is only 200mb.
Simon.
ASKER
I was able to extract it to a location on the server and un-install exchange 2003, now get-exchange server lists only my orphaned 2007 server along with production 2007 and 2 2010 servers.
Final question I hope, now that one is gone, can I just start over on the server that was giving me mailbox role problems, seeing as the one 2010 server has a db copy on it already? Thanks.
Final question I hope, now that one is gone, can I just start over on the server that was giving me mailbox role problems, seeing as the one 2010 server has a db copy on it already? Thanks.
You really need to try and remove Exchange. You cannot really just wipe an Exchange server and expect things to work due to the tight integration in to AD. Therefore you have to either
a. Uninstall Exchange.
b. Fix the issue.
c. Wipe the machine and then recover the server using the command line switches.
Simon.
a. Uninstall Exchange.
b. Fix the issue.
c. Wipe the machine and then recover the server using the command line switches.
Simon.