We're currently upgrading an old app from running on Windows Server 2003 to running it on Windows Server 2012.
Users and other systems communicate with this system via HTTP (i.e. users accessing the website), FTP (files to sync data from client devices) and Windows Shares (files to sync data from devices which don't have FTP capabilities).
To do this migration, I'd like to disable the current live system and repoint users to the new one. I want to ensure the old website, FTP and file shares are inaccessible so there's no chance of anyone communicating to the old locations (i.e. I want them to get an error if they somehow reach the old system; so we know there's an issue rather than waiting for someone to notice integrity issues due to (say) files queueing up on the shares).
However, after the migration we'll be running some tests to know if all's worked. If there are issues we may wish to roll back to the current solution - I want this to be painless & as risk free as possible.
For FTP: I'll stop & the FTP (FileZilla) service; meaning for roll back I just have to start this service and it will be instantly accessible, without any additonal configuration (e.g. recreating users & permissions).
For HTTP: I'll stop the IISAdmin and W3Svc services; same reasoning as above.
Is there a simple way to disable network sharing (i.e. make windows shares innaccessible without changing the permissions on those shares / their config) on Windows Server 2003 without losing configuration settings?