Page 1 of 1

Windows file and print server migration

Posted: Sat Feb 20, 2021 2:08 pm
by 00
Source servers may consist of a Windows Server or a File Server Cluster resource.

If server get the share info from the registry.
If cluster file server resource, get it from this command:
get-smbshare to get scope name.
get-smbshare -scopename xyz | select name,path | export-csv c:\temp\blah.csv -not -append

On target server, find and replace the paths in the CSV with your target paths

Then run import-csv c:\temp\blah.csv | %{ new-smbshare -name $ -path $_.path -verbose}

If retaining the old NetBIOS name of the server in the form of a DNS alias, then create the SPN:
netdom computername new_hostname /add:old_name(new FQDN). This will create 2 SPNs, one single label and one new FQDN.
setspn -l new_hostname

DNS alias has to be an IP A record and not cname

For print servers;

reg add hklm\system\currentcontrolset\control\print /v DnsOnWire /t REG_DWORD /d 1

reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v DisableStrictNameChecking /t REG_DWORD /d 1

reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v OptionalNames /t REG_SZ

Add entries to the OptionalNames REG_SZ.
use regedit to add your CNAME alias FQDN in the newly created OptionalNames REG-SZ hklm\system\currentcontrolset\services\lanmanserver\parameters

multiple entries must be separated by a comma.

Step 4: Reboot the Print Server.
A reboot is required for the changes to take effect.