HI,
Have been following the migration guide for SBS 2011 to Exch 2016, have completed all of the steps (double checked), however, when I migrate a test mailbox from SBS 2011 mail server to the new exchange 2016 mail server, Outlook (2016) remains disconnected.
I can access the mailbox from https:\\IP of exch 2016\owa and send and receive email from that mailbox, so all looks good from that point of view but Outlook remains disconnected.
Have migrated the mailbox back to SBS 2011 mail server, and Outlook reconnects instantly - so don't want to proceed until I can understand why Outlook won't connect - at present all mailboxes are back on the SBS 2011 server.
Reading and looking at other cases it seems to suggest that I may have something wrong with the SCP, but have been through the guide again and checked it all and everything looks o.k.
Could you advise on some troubleshooting steps please.
Thanks,
Mike
MIke,
Make sure that any DNS records or zones you have on your local DNS like mail.domain.com points to the IP address of the new Exchange Server. Exchange Server 2016 can up and down proxy but Exchange Server 2010 cannot do that.
You also need to have all virtual directories and ECP configured so that is uses the new Exchange Server
Hi,
Just to aid understanding of the IP's in use etc;
SBS 2011 192.168.1.7
EX2016. 192.168.1.4
have pointed mail.domain.com (internal zone) to 192.168.1.4
Outlook anywhere is set to mail.domain.com on EX2016
Have then checked the virtual directories on new ex2016 server
ecp - https://mail.domain.com/ecp
ews - https://mail.domain.com/ews/exchange.asmx
mapi - same/mapi
Eas - same/microsoft-server-activesync
OAB - same/OAB
owa - same/owa
default web site - same/powershell
Checking Outlook Anywhere on SBS 2011 shows;
SBS 2011 Basic {Basic, Ntlm} False mail.domain.com
Checking client access server on SBS 2011 shows;
SBS2011 https://mail.domain.com/autodiscover/autodiscover.xml
Checking client access server on EX2016 shows;
EX2016 https://mail.domain.com/autodiscover/autodiscover.xml
Setting DNS
mail.domain.com (public IP lookup) goes to public IP address of Exchange server
mail.domain.com (internal lookup) goes to 192.168.1.4 (new EX2016 server)
SRV record
_autodiscover._tcp.domain.com points to mail.domain.com
So all DNS looks good so far.
If I check SCP (get-clientaccessservice) on EX2016 I see
SBS2011
EX2016
If I check SCP on SBS 2011 (get-clientaccessserver) I see
Are there any further troubleshooting steps I can follow?
As far as I can see it looks good. I have some questions:
OS of client is Windows 10 Pro 1909 (will update this to a later version it is used as a test machine)
Outlook 2016 version 2203 (16.0.15028.20178)
SBS connector not installed (WSE 2016 client connector is installed)
ipconfig /all
Host Name . . . . . . . . . . . . : DESKTOP-BNEJT7F Primary Dns Suffix . . . . . . . : domain.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.local
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : domain.local Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter Physical Address. . . . . . . . . : 00-15-5D-32-0C-01 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d096:928b:af8c:6ce1%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 29 November 2021 09:14:25 Lease Expires . . . . . . . . . . : 22 April 2022 14:46:24 Default Gateway . . . . . . . . . : 192.168.1.254 DHCP Server . . . . . . . . . . . : 192.168.1.3 DHCPv6 IAID . . . . . . . . . . . : 100668765 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-A8-E6-51-00-15-5D-32-0C-01 DNS Servers . . . . . . . . . . . : 192.168.1.3 NetBIOS over Tcpip. . . . . . . . : Enabled
For reference 192.168.1.3 is the main DC1 server which is Server 2016 with DNS role installed.
Mike,
It looks all good to me but can we arrange a meeting to see if something else is going on? Want to understand and help with this issue.
Hi Mariette,
Apologies for the delay had to put this one on hold, whilst we finished another project. Could you let me know when you're free and we can take a look and move this one on please.
Can we do this tomorrow (Friday) sometime in the afternoon? I will contact you through email to set a schedule.
Thanks for the response tomorrow afternoon is perfect - let me know how you would like to connect.
See you tomorrow :)
In this case the User that was migrated we could not logon was disabled in ADUC....almost felt like candid camera....