Shutting down 2010 CAS/MBX/HUB server

Hi.

I'm migrating our Exchange 2010 server (single server setup) to a 2013CAS+2013MBX server setup at the moment. The below list is completed.

- All mailboxes have been moved (also arbitrary and discovery).

- PF not being used (so I'll just delete it when uninstalling).

- All external access (owa, activesync, Outlook anywhere, SMTP) now goes to the 2013 CAS server.

- OABs and distribution of 'em are now on 2013

- 2010 server has been removed from the Internet send connector as the logs showed me that it hadn't sent any outgoing mail for the last 2-3 weeks.

- I've checked the IIS logs and only activity I can see in those is from the 2013 mailbox server and when I start EMS on the 2010 server, apart from that everything is quiet.

So I think that I'm about ready to shut it down for a week or so to see if everything still works as it's supposed to. But the RPC log still shows me that Outlook clients are connecting to the 2010 server and this worries me a bit.

My question is therefore if I can safely ignore the RPC connections and shut the 2010 server down? If "yes" should I get myself a maintenance window where I can make sure that no users are connected, or can I just shut it down and then users will automatically connect to the 2013CAS server. 

Thanks for your time

Best

Thomas

May 27th, 2015 9:17am

Hi.

I'm migrating our Exchange 2010 server (single server setup) to a 2013CAS+2013MBX server setup at the moment. The below list is completed.

- All mailboxes have been moved (also arbitrary and discovery).

- PF not being used (so I'll just delete it when uninstalling).

- All external access (owa, activesync, Outlook anywhere, SMTP) now goes to the 2013 CAS server.

- OABs and distribution of 'em are now on 2013

- 2010 server has been removed from the Internet send connector as the logs showed me that it hadn't sent any outgoing mail for the last 2-3 weeks.

- I've checked the IIS logs and only activity I can see in those is from the 2013 mailbox server and when I start EMS on the 2010 server, apart from that everything is quiet.

So I think that I'm about ready to shut it down for a week or so to see if everything still works as it's supposed to. But the RPC log still shows me that Outlook clients are connecting to the 2010 server and this worries me a bit.

My question is therefore if I can safely ignore the RPC connections and shut the 2010 server down? If "yes" should I get myself a maintenance window where I can make sure that no users are connected, or can I just shut it down and then users will automatically connect to the 2013CAS server. 

Thanks for your time

Best

Thomas

You still have legacy PFs? If you want get rid of them, you need to follow this first. 

https://technet.microsoft.com/en-us/library/dd876883%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 9:45am

PFs are not being used for anything. The database was created when the 2010 server was installed but it has never been used for anything. So I don't worry about that.

I'm almost positive that everything is ready so I can do a test-shutdown. Probably the only thing I'm actually asking is: Is it normal to still have RPC activity on the server and what will happen with the connected clients if I just shut it Down while they are connected. I don't wan't to leave them in a disconnected state so I wanna be sure that they will autmatically connec to the 2013 CAS server.

May 27th, 2015 9:53am

PFs are not being used for anything. The database was created when the 2010 server was installed but it has never been used for anything. So I don't worry about that.

I'm almost positive that everything is ready so I can do a test-shutdown. Probably the only thing I'm actually asking is: Is it normal to still have RPC activity on the server and what will happen with the connected clients if I just shut it Down while they are connected. I don't wan't to leave them in a disconnected state so I wanna be sure that they will autmatically connec to the 2013 CAS server.

If a PF database exists, then you will need to follow those instructions regardless if its being used. I suspect what you are seeing is the hierarchy connection in the Outlook clients to the PF database. Do the RPC logs indicate what the clients are connecting to? Does the Outlook client show a connection to a 2010 server in the Connection Status? Is the legacy PF Database set as the default PF database for the 2013 mailbox database properties?
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 12:35pm

Hi,

According to your description, I understand that you have migrate Exchange 2010 to Exchange 2013 with all mailbox, all VDs and mail flow. However, RPC log stills show outlook client connect to Exchange 2010.
If I misunderstand your concern, please do not hesitate to let me know.

Please run below command to check the value of RPCClientAccessServer:
Get-MailboxDatabase | FL Identity,*RPC*

If it still point to original Exchange 2010 server, please run below command to change:

Get-MailboxDatabase | Set-MailboxDatabase -RpcClientAccessServer FQDN

More details about Understanding RPC Client Access, for your reference: https://technet.microsoft.com/en-us/library/ee332317%28v=exchg.141%29.aspx?

May 28th, 2015 2:39am

Hello Allen and thanks for your reply.

I have run the command on the 2013 MBX server and the databases located on the 2013 server had the 2013mbx server as rpc server.

I have also run it on the 2010 server and the 2010 databass has the 2010 server as rpc server. Since they are all empty (no mailboxes) I guess that is as it should be.

I'll take a look at the PF removal that Andy adviced me to, I believe that it could be the reason why the 2010 RPC traffic is happening.

Thanks.

Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 7:35am

Hi Andy.

Thanks for your reply. I believe you a re right, didn't think about that when I replied earlier. The Outlook clients are showing a connection to the 2010 server, just a single one and they do show Public Folder so that must be it. Thanks for pointing that out :)

If it is not being used at all, can I just remove it during business hours by doing what your link describes or should I do it in a maintenance window.

Best

Thomas

May 28th, 2015 7:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics