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

Outlook cannot connect to Exchange server after SBS 2003 Hardware migration

I recently migrated Windows SBS 2003 to a new hardware. Everything went smoothly until I shutdown the old SBS server. When I shut it down none of the users can connect to the Exchange server. All other access works fine, ie shared directories, logins, internet, printers. etc. The users are all using Outlook 2007 for their Exchange clients. All mailboxes were moved to the new server. I verified that Outlook was configured to connect to the correct exchange server. DHCP points all of the clients to DNS on the new server.
0
Sabertec
Asked:
Sabertec
  • 8
  • 6
1 Solution
 
gupnitCommented:
Hi,
Please see if from use PC you can resolve the new Exchange server. Actually Outlook 2007 should pick up the new server on its own when you move mailboxes.
Still check and see if DNS is fine. Where is your DC
Thansk
Nitin
0
 
SabertecAuthor Commented:
I cannot resolve the new Exchange server unless the old server is running. Outlook 2007 is only automatically resolving to the new server if the old server is running.

There are no error's in the DNS event logs. IPconfig on the client shows the new server as the DNS server.
0
 
gupnitCommented:
Hi,
Is there any HOST File entry for old Exchange server in the PC.
Can you just try recreating one users Outlook Profile and confirm
Thanks
Nitin GUpta (gupnit)
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
SabertecAuthor Commented:
No HOSTS file settings at all.

I'll try creating a new profile.



0
 
SabertecAuthor Commented:
Same result. I tried creating the new result with the old server offline. I could not connect to the exchange server to verify the user name.
0
 
gupnitCommented:
Hi,
From the PC, goto cmd prompt do a nslookup for the new exchange server see what you get
Thanks
Nitin
0
 
SabertecAuthor Commented:
nslookup for the new server resolves to the correct address and fddn.
0
 
SabertecAuthor Commented:
I've noticed another problem as well. It may not be related but I feel I should at least mention it. The user desktops are redirected to the server. I've updated Group Policy to reflect the server change but if DC(original server) is off line users desktop icons disappear as well. My configuration in Group Policy is set to redirect the desktops to \\dc1\userdesktop$\%username%  but when the icons fail to load it is still referencing the old setting of \\dc\userdesktop$\%username%.
0
 
gupnitCommented:
Hi,
  • In PC please goto Control Panel - User Accounts - Advanced - Manage Password and see if any caching is happening
  • From command prompt, run gpupdate /force
Let me know
Thanks
Nitin
 
 
0
 
SabertecAuthor Commented:
gpupdate does refresh but doens't resolve the issue.

The user accounts in question are domain user accounts not local user accounts.

Also removing a PC from the domain and adding it again does not resolve the problem either.
0
 
gupnitCommented:
How many DC do you have....change the dns on pc to another dc and see.
Can you tell me what error you get when you try to create the user profile
0
 
SabertecAuthor Commented:
2 domain controllers both are Win 2003 SBS. Both DNS server's are listed as name server's in DNS on both servers.

Creating a new Outlook profile doesn't generate an error. The error comes from when Outlook tries to connect to dc1(new server) while DC(old server) is offline.
0
 
SabertecAuthor Commented:
I think I've resolved it. First a little more background. All the user's profiles are redirected through group policy to a location on the server to allow them to work at any computer in the building. During the migration I didn't actually move the files for each user's appdata and desktop folder's. I changed the path in group policy under the assumption that a different path would cause the profiles to be redirected to the new location. This only worked for a couple users which I didn't discover until recently. I believe that this was caused by the user being granted exclusive rights to their various folders. Group Policy wasn't configured that way but I had to go to each user's folder's take ownership and then reset the security. I then had to use robocopy to move all the files from the old server to the new server. After this the locally stored profile on each user's computer updated properly.  

Thanks for your efforts Gupnit. :D
0
 
gupnitCommented:
Great :-), thats what the objective is - a solution, it doesn't matter who does it, if you get it even better as that shows you have control over your setup
Cheers
Nitin
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now