I need to move all network printing from one server to another server in an Active Directory environment. The printer connections are currently defined in each users local profile on their machines.
I need to
1. Remove all current network printer mappings from local user profiles -
This I can do with WshNetwork.RemovePrinterConnection in the domain login script, HOWEVER there doesn't seem to be a way to check if the printer connection exists first?? Not all network printers currently exist in each user profile, they tend to have only the printers which are on their floor. If I try to remove a printer connection which doesn't exist, it gives an error, which I can't really have.
I was hoping there would be an easy way (the hard way is to EnumPrinterConnections and parse the result) to say "If this network printer connection exists, remove it" in Windows Scripting Host, but I can't seem to find it ...
2. Re-create all network printer mappings using the shared printers on the new server -
This I can do with WshNetwork.AddWindowsPrinterConnection in the domain login script, and I can use the optional paramter bUpdateProfile to make it part of the user's profile, but my question is should I? Is there a better way to define a set of network printer connections for all domain users in an Active Directory environment?
- Qualm
I need to
1. Remove all current network printer mappings from local user profiles -
This I can do with WshNetwork.RemovePrinterConnection in the domain login script, HOWEVER there doesn't seem to be a way to check if the printer connection exists first?? Not all network printers currently exist in each user profile, they tend to have only the printers which are on their floor. If I try to remove a printer connection which doesn't exist, it gives an error, which I can't really have.
I was hoping there would be an easy way (the hard way is to EnumPrinterConnections and parse the result) to say "If this network printer connection exists, remove it" in Windows Scripting Host, but I can't seem to find it ...
2. Re-create all network printer mappings using the shared printers on the new server -
This I can do with WshNetwork.AddWindowsPrinterConnection in the domain login script, and I can use the optional paramter bUpdateProfile to make it part of the user's profile, but my question is should I? Is there a better way to define a set of network printer connections for all domain users in an Active Directory environment?
- Qualm