Solved

Exchange 2013 Legacy name space when using 3rd party email filtering

Posted on 2015-02-16
11
96 Views
Last Modified: 2015-03-06
I am upgrading from Exchnge2007 to Exchange2013

We use a 3rd party for filtering with an MX record  professorsnape.contoso.org

How will this affect setting up the legacy namespace?  Do I need to set up the external legacy namespace?

Thank you,
John
0
Comment
Question by:beefwilliams
  • 7
  • 4
11 Comments
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 500 total points
ID: 40612478
Nope. You only make a legacy namespace for client connection to the CAS servers.

Mail flow is just cut over from one server to the other. So for your filtering service you would just point it to the new public IP of your 2013 server.
0
 

Author Comment

by:beefwilliams
ID: 40615689
So if I want to keep my same IP address so don't have to change the numerous places we have it set.

Do you see any issues if I change the IP address of the server with the current Exchange2007 to something different and set the new exchange2013 to my preferred IP, before I start the upgrade.  

Thank you!
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40615912
I think the biggest problem would be DNS propagation. Before you switch the IPs around, drop all the Time To Lives (TTLs) on your external hosting provider to 1 hour. If it was set to 48 hours beforehand you will need 48 hours for that new TTL to propagate. Then once everyone knows about your low TTLs you can quickly change things around. I would do this all after hours though.
0
 

Author Comment

by:beefwilliams
ID: 40623894
We use a 3rd party for filtering and they forward all incoming mail mail to an outside facing address thropugh our firewall.  So the way I understand it the DNS settings will only be internal ones which I can set manually.  The external TTL is set to 15 minutes by our provider.

Is there anything that I have wrong or need to consider?  Yes I am doing this after hours.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40625006
I think that's it. Going back to my original comment you just need to change the IP of where the 3rd party service routes mail.
0
Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

 

Author Comment

by:beefwilliams
ID: 40625031
I just finished the install and received this error when I opened the Exchange Man Shell:

This is part of the output from the shell, I have attached a file with the complete output.  It looks like it tried 3 times .

The name of the Exchange2007 server is hermes2, the 2013 is hermes3.
The name of our AD is "forsyth"

Any ideas?
Thank you!
------------------------------------------------------------------------------------------
VERBOSE: Connecting to hermes3.forsythpl.org.
New-PSSession : [hermes3.forsythpl.org] Processing data from remote server hermes3.forsythpl.org failed with the
following error message: [ClientAccessServer=HERMES3,BackEndServer=hermes3.forsythpl.org,RequestId=2d2dcfef-3753-4c3e-b
207-3845ca5d6833,TimeStamp=2/23/2015 2:31:07 AM]
[AuthZRequestId=45093630-4a0f-4c08-a5ff-4d6bf230c5b5][FailureCategory=AuthZ-SetupVersionInformationCorruptException]
Unable to determine the installed file version from the registry key
'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine'. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site HP. Connecting to an Exchange server in another
 Active Directory site.

Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
ExchangeManagementShell-Error.docx
0
 

Author Comment

by:beefwilliams
ID: 40625933
Here is what I see in the Event Log on the new Exchange2013 server I see numerous events that have the following in common:

Microsoft.Exchange.Diagnostics.SetupVersionInformationCorruptException: Unable to determine the installed file version from the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine'.


When I look at the registry "PowerShellEngine'" does not exist under PowerShell\1\ but I do see it under PowerShell\3\
0
 

Author Comment

by:beefwilliams
ID: 40625960
Also I am concerned about this error in the Exchange Man Shell:
WARNING: No Exchange servers are available in the Active Directory site HP. Connecting to an Exchange server in another
  Active Directory site.

Our site is "forsyth"  not "HP".  We used to have 2 sites one was HP but HP is no longer in use.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40626308
Does HP still exist in Active Directory Sites and Services? If so, and its no longer in use, I would look into removing it. It could also be possible that a subnet that is actually in FORSYTH is assigned to the HP site.

Because these are new questions can you close this one and open a new one? Feel free to reference back to this question as well in your new question.
0
 

Author Comment

by:beefwilliams
ID: 40649548
I had some AD issues which are now fixed
0
 

Author Closing Comment

by:beefwilliams
ID: 40649551
Thank you, I hope to finish up this Sunday
0

Featured Post

Want to promote your upcoming event?

Attending an event? Speaking at a conference? Or exhibiting at a tradeshow? Easily inform your contacts by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now