• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 356
  • Last Modified:

Exchange 2010 post migration

Hello,

abc is my old 2003 exchange server

def is the new 2010 exchange server

Moving mailboxes completed but now OWA does not work. I'm assuming it's because DNS still point to abc when looking for OWA.

So I know I can change the IP of def to abc but can I rename the server also?
0
Darth_mark67
Asked:
Darth_mark67
  • 7
  • 5
1 Solution
 
DLeaverCommented:
If you just change the port forwarding on your router to DEF's internal IP then the OWA should start working.  

However Exchange 2010 it won't be using the /Exchange virtual directory anymore but /owa so you would need to setup page redirection on DEF to ensure the /Exchange redirects to the new /owa

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/1e87ca5b-163d-4276-9d53-a05e987d4bd7/
0
 
Darth_mark67Author Commented:
Thanks DLeaver,

I figured once I change the internal IP to the old abc server it should work. I guess my question should be can I change the server name from def to abc? outlook clients are setup looking for abc.domain.local.
0
 
DLeaverCommented:
If you have moved the mailboxes then your clients should now be pointing to def

Changing the server name and IP of def to abc on your internal network is going to cause you a number of issues.

Can you describe your setup a bit, DC's, migration plan used....
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
Darth_mark67Author Commented:
I should have said the "test" mailboxes are moved.
2 2003 dc
I used the transition guide by milind Naphade.
I am in the process of syncing the public folders before they are moved.

If I don't change the IP then I have to change the MX record to point to the new server IP. I would then have to go to every client that has outlook and change what mail server it is looking at.
0
 
DLeaverCommented:
If you are using Outlook 2007 onwards then the clients will auto repoint themselves to the new Exchange.

In Exchange 2003 renaming he Exchange server would break it, you have to consider all of the DS and IIS functionality and this hasn't changed much in Exchange 2010.  So in short I wouldn't try it.

Changing your external MX isn't necessary as the port forwarding explained above would change that.  Changing any internal MX would be a minor step in comparison.
0
 
Darth_mark67Author Commented:
Right now I'm using NAT and not port forwarding.  I figured if I change the IP then all should be ok. Am I thinking correctly?
0
 
DLeaverCommented:
Same thing, at the moment do you have a rule which points external traffic on port 25 through to the abc server?  Change this to the def server on the internal network.  You will need to setup your receive connector on the Exchange 2010 if you haven't already

If you tell me what router/firewall device you are using that would be useful
0
 
Darth_mark67Author Commented:
We have a Sonicwall 240 NSA. But all mail is going through MXToolbox and I have the settings for that. I just can't change directories to program files in EMS.

I do a "cd  Program files " and get:


         Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Tip of the day #80:

The Get-RoleGroupMember cmdlet lists all the members on a management role group. But if you want to get more details abo
ut the members of the role group, use the Get-ManagementRoleAssignment cmdlet. The Get-ManagementRoleAssignment cmdlet e
nables you to view the members of universal security groups that are members of role groups, view the management scope t
hat applies, and more.


[PS] C:\Windows\system32>cd..
[PS] C:\Windows>cd..
[PS] C:\>cd program files
Set-Location : A positional parameter cannot be found that accepts argument 'files'.
At line:1 char:3
+ cd <<<<  program files
    + CategoryInfo          : InvalidArgument: (:) [Set-Location], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

[PS] C:\>
0
 
DLeaverCommented:
just type

cd pro

and then press the tab key to auto complete the line
0
 
DLeaverCommented:
So in the SonicWALL you will have the Firewall option on the left , from here there will likely be a WAN to LAN rule that is sending SMTP traffic to the abc server -and ideally a LAN to WAN rule that only allows SMTP out from the abc server......
0
 
Darth_mark67Author Commented:
right! Thanks I gave you total credit for the solution since all your info did the trick.
0
 
DLeaverCommented:
Thanks
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now