Looks like it worked correctly, thanks! It didn't stamp the DAG computer account at the highest level of the NTFS permissions (it was on the created subfolder), and I'm not sure if it was needed so I put it on manually just from comparing to what is on the old server.
The only other annoyance is that it also didn't rename the cluster core resources in failover cluster manager, but I could see it is pointing to the new server in the quorum configuration, so I updated that name field manually under the properties. I really only even go in there when I'm checking to see if a server is back up (cluster health) after restarting for any reason. -Bonnie From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller Bonnie L. Sent: Friday, July 21, 2017 4:53 AM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Moving the file share witness Thanks Michael-our network admin just verified the network rules are in place, so I'm going to give it a go. -Bonnie From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, July 20, 2017 3:06 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Moving the file share witness It really is that simple. Permissions can sometimes be a weird thing. I've had to fix those manually from time-to-time, but it really isn't a big deal. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller Bonnie L. Sent: Thursday, July 20, 2017 4:12 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] Moving the file share witness Exchange 2013 DAG, we are migrating the file server that currently acts as the file share witness. Is moving it really as simple as it seems? Here is what I have pieced together: 1) Add the "Exchange Trusted Subsystem" group to the local admins group of the new domain member file server and restart. 2) Open needed ports between the new file server and exchange, both on the network gear and windows firewall 3) In EAC under Servers/Database Availability groups, edit the DAG properties and change the witness server name (and path if needed). (Then would be remove share from old server except in our case we are decommissioning). Is that the right way to do it and am I missing anything? It looks like the last step is going to create the share and assign the correct permissions for the DAG "computer" account. Seems too easy. Thanks, Bonnie
