HOW TO ADD A PRINTER FOR ALL USERS (PER MACHINE CONNECTION) – PrintUI.dll

HOW TO ADD A PRINTER FOR ALL USERS (PER MACHINE CONNECTION) – PrintUI.dll

1-) Log in as “Administrator” in Windows

2-) Browse once \\Print to enter the credentials of someone who has access to print server.

3-) Open “CMD” and type the following command to add a printer connection on the machine.

Rundll32 printui.dll PrintUIEntry /ga /n\\Print\PRIXXXX

 

HOW TO REMOVE A PRINTER FOR ALL USERS (PER MACHINE CONNECTION) – PrintUI.dll

1-)Repeat the steps “1” - “2” and “3” as explained above.

Enter the following command to delete a per connection printer from the machine.

Rundll32 printui.dll PrintUIEntry /gd /n\\Print\PRIXXXX

After these steps, you have to reboot the computer.

Next time a user with an Active Directory account connects to this computer, the user will have all the printers that were added with this method.

Kubilay Elmas

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more