[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 717
  • Last Modified:

Re-mapping printers after mass computer rename

Hi everyone :)

This is my first question here. I'm looking for ideas because I have hit a wall. I need to rename 1500 computers (all are domain members). You already see where this is going - mass rename would be devastating for users that have mapped connections to printers shared on other computers. My initial idea was to use a script and rename all 1500 computers in one go. But hundreds of users not being able to print would mean riots.

So far I have been unable to figure out a way to re-map or update the user's existing printer mappings in accordance with the new names of computers. Since mapped printer connections are stored in the registry, I was thinking of exporting "HKCU\Printers\Connections" key, updating the exported file with a script and importing it back. This is how an export looks like:

[HKEY_CURRENT_USER\Printers\Connections\,,computer123,HP LaserJet 4L]
"Server"="\\\\computer123"
"Provider"="win32spl.dll"

The script would need to add a prefix to "computer123", save the file and import it into the registry. Is there any way this could be done?

Any other suggestions on how to approach this problem?


Many thanks :)
0
aLienat3d
Asked:
aLienat3d
  • 3
  • 2
  • 2
2 Solutions
 
zelron22Commented:
I take it that these printers are local to the computers?  How many printers are we talking about?  You might be better off setting up a dedicated print server and putting the printers on the network (or replacing them with commercial printers).  2003 R2 has a method for publishing printers using GP.  I suppose you could do the same thing after the computer rename.

May I ask why you're renaming 1500 computers?  Is this something that could be handled through CNAME records in DNS?  Then as you roll out new computers you could use your new naming convention, but not touch the existing ones.

0
 
aLienat3dAuthor Commented:
Yes, the printers are local to the computers and there's 100 or so of them. I was thinking of setting up a print server, but I don't have any hardware available. Existing servers are overloaded as is and there is no chance of getting new ones since the budget cuts. :(

As for the renaming, I'm doing it because AD is a mess. Regional offices have their administrators who didn't exactly adhere to our naming conventions. I'm hoping that this new naming convention along with security policies will keep them in line. Also, there is a chance that we could be joining a new corporation-wide forest with multiple domains and this new naming policy would identify our computers more transparently. Therefore, I need the renaming done in a relatively short amount of time.
0
 
geewillyCommented:
Could you clarify if you are simply adding a prefix to all 1500 pc's?  So if the prefix is like "na" then all of your pc's will be naComputer123, naAnything and so forth?  I mean you are not doing something like a different prefix for different departments?
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
zelron22Commented:
Do you have any spare workstations (if you have 1500, you must have something sitting around!)?  You could install a server product on one and use it (or depending on volume) a few of them as print servers.  You're already relying on workstation class machines for printing, the fact that it (they) wouldn't be a server class machine shouldn't be an issue.  This would simplify it going forward, too.  

Another thing you may want to consider that if you may be joining a new corporate wide forest, they may have their own naming convention that they would like you to adhere to.  In which case you may end up changing names more than once.  

Good luck, it sounds like geewilly may have an answer for you.
0
 
aLienat3dAuthor Commented:
geewilly, yes - I'm adding a prefix to computer names. Not one but seven different ones that follow the same logic. One letter defining my company, two letters defining a region (or OU) the computer is located in and a dash to separate the prefix from the current computer name. Grand total of 1500 computers, 900 of which are in our headquarters. Those are the trickiest ones and if I could find a solution for them I could apply it to other OU's as well.

zelron22, I took the idea of print servers more seriously once you've mentioned it. Installing Server 2003 R2 as a print server and deploying printers from it sounds like a good idea. As for the corporate-wide forest, they don't have any written naming conventions. XD
0
 
geewillyCommented:
aLienat3d,

Yeah, print servers would by far be the best solution.  If it were just a matter of adding the same prefix to all pc's then a vbs would not be that difficult.  Giving your situation though a vbs would be pretty tricky and clever because you wouldn't know which prefix you used on a pc that had the printer setup locally on.  Unless you made an array that identified all pc's that have a printer locally setup on and what their prefix is going to be and then when you changed peoples printer mappings you would just refer to that array.  If you choose to go vbs way then let me know and I can probably work through it with you.
0
 
aLienat3dAuthor Commented:
I was thinking a script could add a designated prefix in the first and second line of the registry export. Then again, there are computers that have 2 or more mapped printers... Not to mention my complete lack of scripting skills.

Thank you both for the help. :))
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now