Michael

have you tried doing a directed recovery of the new  servers file from the 
server to all the clients (before renaming the server) ? ... I don't see why 
that shouldn't work. The nsr.dir directives on the clients would be a problem 
for the recoveries. They apply to backups only (or do they?).

I haven't tried it myself yet. I'm back from work and the idea just came up. 

jee

On Tuesday 18 Jun 2013 08:41:05 Michael Leone wrote:
> D'OH! My boss came back to work today, and pointed out something obvious I
> had overlooked. (not an unusual occurrence ..)
> 
> All these machines will be rebooted for Windows Update patching this
> weekend (and occasionally other needed updates, such as drivers, etc). So
> I can copy the script I have and the new file to the folder we keep on
> each machine for storing such update files. Then, when we go to run
> Windows Update this Sun, we can just run the script locally, since we'll
> be logged onto each machine anyway. (we use WSUS, but only apply the
> updates manually, since most of our applications have their own specific
> shutdown order/procedure).
> 
> So I don't have to worry about executing the script remotely. Mind you, it
> means it pushes back my NW server rename project to next week, since the
> point is to have each client know the new name of the server before the
> server gets changed. But that's fine, too ...
> 
> Now I just need to tweak the script to copy the new servers file a bit
> more robust and resilient, and write another script to copy that one (and
> the new servers file) to each client. But that shouldn't be too a problem.