The 2 extra connections to are for shared mailboxes that exist on the 2010 server. Given almost all of our employees have some form of additional mailboxes opened in outlook, I went ahead and did this to see if that would have any problem. I did not, however, test clients moving from 2010 to 2016. I initially created 3 test accounts, all on the 2016 server to verify they could talk to the 2010 server, to each other, etc. Internal DNS points only to the new server's IP for the mail A-record. The certificate has been exported and imported into 2016 properly. local to prevent potential access to powershell from the internet. The only one that isn't is the PowerShell VD is a. Thanks for the information! I looked over the virtual directories again, and the directories all seem to be set to the right URL. Disabling the two UM services solved this, as i don't make use of any UM services for any of our users at this time. It was creating about 1GB in the span of 5-10 minutes just in. It was being caused by the UM Call Routing service starting and stopping rapidly, and dumping a bunch of process dumps to this folder. The internal record points to the internal IP of the new 2016 server.ĮDIT 2: Fixed the C:\Windows\Temp folder filling up. It has slowed now that the day is drawing to a close, but I've already had to extend its VHDX file to make more space on the drive.ĮDIT: In case it's not clear, we have a split DNS setup for our. When I say quickly, I mean at least a few GB per hour. Going to use WinDirStat real quick see what it is, but almost certain it is transport/queue related. The only user accounts that connect to the 2016 server are those whose mailboxes were created on the 2016 server itself.Īlso, I've noticed the C:\ drive on the Exchange 2016 server is filling up REALLY quickly. However, once a mailbox is moved from 2010 to 2016, the outlook client used still points to the 2010 system. My original thought was that given both servers are both running a Mailbox service and a Client Access Service, Outlook clients would just connect to whatever server held their mailbox. I'm rather new to this, and i feel like there's something obvious I'm missing. Logging into the OWA of the 2016 box shows that any test messages sent/received are present and accounted for.
#Tinyterm wrong server update#
Once a test mailbox is moved from the 2010 server to the 2016, Outlook will no longer update given the mailbox is on the 2016 server and it is connecting to the 2010 server. When I moved a test user from 2010 server to the 2016 server, their outlook still connects to the 2010 server.Ĥ. When configuring outlook with any of the test accounts I created on the 2016 server, they connect to the 2016 server.ģ. All existing users' are still connecting to the 2010 server.Ģ.
#Tinyterm wrong server how to#
I am having a strange issue that I'm unsure of how to resolve. the internal A-record for the mail server has been switched to point to the new 2016 server's IP. There are also two SCPs in AD for the two servers, 20.
local domain, so I am using an SRV record for autodiscover. So, right now nothing business-critical is being disrupted given mailflow is still working fine.
Mail is properly delivered to the 2010 clients' mailboxes, and is properly sent as well. The 2016 server is what is sending/receiving all mail at this point, but has no mailboxes other than test mailboxes when I was verifying functionality. Then, I brought up a 2016 server to begin migration. Standard single-server setup for 2010 (Mailbox, Client Access, Hub Transport, etc.) Originally, we had a single 2010 Exchange server.
0 kommentar(er)
