Update the scripts
Follow these steps to update the new versions of your scripts to ensure that they do not refer to servers that you are planning to decommission.
To update new script versions
Log on as domain administrator on the computer that stores the scripts you intend to modify.
Browse to the locations where you copied your scripts.
Make sure that you modify the new copies of your scripts, not your originals.
Open each script in a text editor and examine each line.
If you see a reference to a tool or file that you copied to SYSVOL, update the reference to point to \\domainname\SYSVOL\domainname\scripts\.
Some legacy tools may not be able to handle UNC paths (such as \\domainname\SYSVOL). If this is the case, you will insert a net use command to map UNC paths to a temporary drive letter before invoking the tool. Remember to unmap this temporary drive letter in the script.
Here is an example of a net use command that temporarily maps a subfolder of the scripts folder to P:\:
net use P: \\domainname\SYSVOL\domainname\scripts\subfolder password /user:domainname\username
To unmap P:\, type
net use P: /delete.
If you see a reference to a server that you are going to decommission, copy a resource to SYSVOL or the Windows EBS Management Server and update the script to point to the new location.
Eliminate all direct references to servers by copying resources to SYSVOL if they are smaller than around 50 MB (or to a shared folder on Windows EBS Management Server if they are larger than 50 MB).
An example of a tool that you would move to SYSVOL is a 500 KB tool that is shared on \\adventure-works-fs\tools. An example of a tool that you should not copy to SYSVOL is the output directory of an asset tracking tool (you would store this tool in a file share on the Windows EBS Management Server).
While reading through your scripts, refresh your memory on what your scripts do. This will be useful when you are ready to verify your migration.