Printer Remapping in Windows 7 Deployments

re: Printer Remapping in Windows 7 Deployments

RobSampson — Sun, 28 Apr 2013 23:35:57 GMT

No problem. I also found the same approach to be helpful in situations where you need to apply other "current user" settings as well. I have the step 2 script copy some other scripts to the StartUp folder that apply 64 bit user specific settings (for when HLKM doesn't cut it) for specific applications.

Glad it helped.

re: Printer Remapping in Windows 7 Deployments

DamonJohns — Sun, 28 Apr 2013 10:27:31 GMT

Thanks Rob, appreciate your response. Your post is exactly what I was after.

Cheers

Damon

re: Printer Remapping in Windows 7 Deployments

RobSampson — Fri, 26 Apr 2013 04:25:23 GMT

Hi Damon, I have set it up basically as a four step process.

Step 1 is to create a deployment task sequence. I based mine on the Client.xml template, and right down the bottom, I added a "Run Command Line" task that runs:

cscript.exe "%SCRIPTROOT%\ZTI_Custom_Copy_Printer_Remap_Script.wsf"

Step 2 is to create the ZTI_Custom_Copy_Printer_Remap_Script.wsf script in the %SCRIPTROOT% folder that contains this code:

skydrive.live.com/redir

Step 3 is to create the ZTI_Custom_Remap_Printers_To_Print_Queues.vbs script in the %SCRIPTROOT% folder that contains the below code. This is the script that is copied to each StartUp folder within each profile on the new computer:

skydrive.live.com/redir

Finally in step 4, create your new printer queues on the new server, then create a text file called ZTI_Custom_Remap_Printers_To_Print_Queues_Reconnection_Map.txt in the %SCRIPTROOT% folder, that has contents like the following, with the old and new printers being separated by a semi-colon:

\\OldServer\ShareName1;\\NewServer\NewShareName1

\\OldServer\ShareName2;\\NewServer\NewShareName2

\\OldServer\ShareName3;\\NewServer\NewShareName3

So, what happens when the task sequence runs, the VBS is copied to the StartUp folder for each user (C:\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup) and the TXT is copied to the Temp folder for each user (C:\Users\%username%\AppData\Local\Temp). When the user logs in, the VBS runs and deletes itself, and you will find a log of its actions in the %TEMP% folder per user as well.

Rob.

re: Printer Remapping in Windows 7 Deployments

DamonJohns — Sat, 20 Apr 2013 02:11:09 GMT

Would you be willing to share your modified script Rob and the basic steps in your MDT TS that you used to achieve this?

re: Printer Remapping in Windows 7 Deployments

RobSampson — Tue, 02 Apr 2013 06:07:40 GMT

Hi, I have found that instead of using

StrKeyFullPath=strKeyPath&"\"&Subkey

objReg.DeleteKey HKEY_CURRENT_USER,StrKeyFullPath

it is better to use

objNetwork.RemovePrinterConnection Replace(strSubKey, ",", "\"), True, True

since this removes the printer connection properly. Otherwise, the connection still appears under Devices and Printers.

I have now combined a modified version of this script into a post LoadState task in my MDT Task Sequence, which places itself in the C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup folder by enumerating the Users folder, and creating the Startup folder. This way, it runs when the user logs in, and reconnects their printers, and remove the old ones.

re: Printer Remapping in Windows 7 Deployments

Jose Barba — Thu, 21 Feb 2013 16:32:54 GMT

Thanks for sharing

re: Printer Remapping in Windows 7 Deployments

Mohammed Imran — Wed, 13 Feb 2013 01:05:40 GMT

Nice post. Will be really handy in x86-x64 migration scenarios.