• T-group Driver License
• T-group Driver Test
• T-group Driver Salary

TEAMGROUP has a professional R&D capability, excellent product quality, fast production efficiency, extensive global sales network and good customer service. Because of the rapid growth of TEAMGROUP T-FORCE gaming memory, RGB memory, DDR4 memory, server Memory, high-speed memory card, SD memory card, MicroSD memory card, OTG flash drive, SSD solid state hard drive, and mobile accessories in. Jul 12, 2019 Does anyone know how this works? On Teams website they claim this is possible and even on Thermaltakes site they say you can control this memory with TT RGB Plus software. I cant find any options anywhere in the TT software that it can even see the Ram. Ive Googled this issue and cant find any in.

Where I work, we have PACS workstations (running Windows XP Professional) that are owned and controlled by our vendor and are on a different subnet (which is also completely controlled by the vendor). Some interesting quirks we've noticed are: We can navigate to 'workstationnamec$' without any trouble, but if we navigate to 'workstationname' (to see a list of shares or printers), we do not see any printers, unless at least one printer on the workstation is shared. For now, these instructions will refer to machines where no printers are shared. We also are not able to install a printer through Windows Explorer because we get an access denied message (even though we have successfully authenticated to the admin share of the computer via Windows Explorer).

The steps I'm about to share with you have not only enabled us to overcome these quirks, but they've also helped us be able to remotely administer printers without ever having to interupt our physicians who need to continue using the workstations. I also believe that these steps will be helpful to some of you for other reasons as well. I hope that many of you will find a very beneficial use for this!

NOTES: These directions pertain to any XP Professional workstation that you are able to remotely view through Windows Explorer (ex: 192.168.1.100c$), but not able to remotely view/manage printers through Windows Explorer. We are performing all of the remote administration from Windows 7 Professional workstations to Windows XP Professional workstations.

The vbs scripts we’ll be using are installed by default in Windows 7 (%WINDIR%System32Printing_Admin_Scriptsen-US), and they are as follows:

prnport.vbs ---> Creates, deletes, and lists standard TCP/IP printer ports, in addition to displaying and changing port configuration.
prndrvr.vbs ---> Adds, deletes, and lists printer drivers.
prnmngr.vbs ---> Adds, deletes, and lists printers or printer connections, in addition to setting and displaying the default printer.

Copy all three of these scripts to a folder called 'scripts'.

The other two commands we’ll be using are also installed by default in Windows XP & 7 in the %WINDIR%System32 directory. So these files will not need to be copied, since they will already exist on your remote computers:

cscript ---> Starts a script so that it runs in a command-line environment.
rundll32 printui.dll,PrintUIEntry ---> Automates many printer configuration tasks. Printui.dll is the executable file that contains the functions used by the printer configuration dialog boxes.

The psexec program is part of the PSTools suite. It’s just an exe file that you download and put in C:WindowsSystem32 and/or C:WindowsSysWOW64 (On the computer you plan to do the remote administration from). I personally always put it in both folders, just in case.

For this entire document, I’m going to be using the following information as my example:

Target Computer = 192.168.1.100
Printer IP = 192.168.1.200
Printer Port Name = IP_192.168.1.200
Printer Name = Our Site – Checkin Dept – Ricoh 4002
Printer Drivers = You will need to copy whichever ones you need ---> to a “drivers” folder on the remote computer. They will need to already be “unpacked” (there should be a relevant .inf file located in whichever drivers folder you plan on using). The files I’m using for this example are stored in “z53149endisk1”, which I copied to the “c:hpdrivers” folder on the remote computer. I personally stored them in the folder “C:hp” because it’s a safe place where people, including the vendor, won’t generally notice them.

Let's begin!

9 Steps total

Step 1: Prepare The Files

(Repeating what I referenced in my NOTES above)

a. Copy 'prnport.vbs', 'prndrvr.vbs' and 'prnmngr.vbs' from %WINDIR%System32Printing_Admin_Scriptsen-US (from a Windows 7 computer) to a folder called 'scripts'.

b. Download the correct printer drivers, and unpack/extract them to a folder called 'drivers'.

Step 2: Transfer The Files To The Remote Computer

Open Windows Explorer and navigate to the admin share of the remote computer:
192.168.1.100c$

Copy the 'scripts' and 'drivers' folders to wherever you want on the remote computer. In our example, we copy them to C:hp

Step 3: Connect To The Remote Computer Through A Command Prompt

From your computer, open a command prompt and type the following:

psexec 192.168.1.100 -u –p cmd

(enter an admin username and password that has rights on the remote computer).

This opens an administrative command prompt connection to the remote computer you’re working with.

Step 4: Delete The Port & Printer Name (Just In Case They Already Exist)

Now that you’re connected remotely, essentially what you’re going to use for this step is the specific port name and printer name that you plan to use, just to make sure neither already exists.

(This step has been edited based on a tip provided by IUCN5406 - it's best to try to delete the printer name before deleting the port, otherwise the name may still be in use. Thanks for the info IUCN5406!)

(delete the printer name, in case it already exists)
cscript 'C:hpscriptsPrnmngr.vbs' -d -p 'Our Site - Checkin Dept - Ricoh 4002'

(delete the printer port, in case it already exists)
cscript 'C:hpscriptsPrnport.vbs' -d -r IP_192.168.1.200

NOTE: In some circumstances, you may need to delete the printer name before you are able to delete the printer port

Step 5: Create The Printer Port

OK, now we’re going to create the port we want to use:

cscript 'C:hpscriptsPrnport.vbs' -a -r IP_192.168.1.200 -h 192.168.1.200 -o raw -n 9100

Step 6: Install The Printer Driver

Next, we’re going to install the driver we want to use:

cscript 'C:hpscriptsPrndrvr.vbs' -a -m 'RICOH Aficio MP 4002 PCL 5e' -i C:hpdriversz53149endisk1oemsetup.inf -h C:hpdriversz53149endisk1

Step 7: 'Tie It All Together'

Lastly, we’re going to name the printer and tie it to the printer port we created:

cscript 'C:hpscriptsPrnmngr.vbs' -a -p 'Our Site - Checkin Dept - Ricoh 4002' -m 'RICOH Aficio MP 4002 PCL 5e' -r IP_192.168.1.200

Step 8: Share The Printer (Optional, But Recommended)

At this point, you still won’t be able to view or manage the printers through Windows Explorer. But we’re going to fix that now by sharing the printer. Enter the following two commands, one at a time (type one, hit enter, then type the next one and hit enter):

T-group Driver License

rundll32 printui.dll,PrintUIEntry /Xs /n 'Our Site - Checkin Dept - Ricoh 4002' Sharename 'Ricoh 4002'

rundll32 printui.dll,PrintUIEntry /q /Xs /n 'Our Site - Checkin Dept - Ricoh 4002' Attributes Shared

-OR, this can be accomlished via cscript-

cscript 'C:hpscriptsPrncnfg.vbs' -t -p PRINTERNAME +shared -h SHARENAME

ex: cscript 'C:hpscriptsPrncnfg.vbs' -t -p “Our Site - Checkin Dept - Ricoh 4002” +shared -h “Ricoh 4002”

Step 9: Set The Printer As Default (Optional)

Please refer to my detailed write-up for this:
http://community.spiceworks.com/how_to/119857-configure-a-default-printer-for-all-new-users

More documentation for each script/command can be found here:

prnport.vbs: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prnport.mspx?mfr=true

prndrvr.vbs: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prndrvr.mspx?mfr=true

prnmngr.vbs: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/prnmngr.mspx?mfr=true

rundll32 printui.dll,PrintUIEntry: http://technet.microsoft.com/en-us/library/ee624057%28v=ws.10%29.aspx

psexec: http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

cscript: http://technet.microsoft.com/en-us/library/ff920171%28v=ws.10%29.aspx

References

• Auto Install Local TCP/IP Printer Script

13 Comments

• Mace
  Rockn May 15, 2013 at 04:16pm

  All of that to install a printer? Wouldn't group policy preferences be an easier option?

• Datil
  Shuey May 15, 2013 at 04:21pm

  If the computers were part of a domain that WE controlled; yes. But these are all controlled by the vendor (vendor's subnet, vendor's servers, etc). This is our only option right now because they won't work with us.

• Ghost Chili
  Nick42 May 15, 2013 at 05:18pm

  Understand the frustration, but at least you found a way to make it work for you! Not to mention nice references material too.

• Thai Pepper
  Mike Diesel May 15, 2013 at 09:00pm

  Good information. I always like learning how to do mundane tasks from the command line. It adds a bit of spice to my day.

• Datil
  spike7 May 16, 2013 at 06:25pm

  Awesome to learn command prompt better - thanks for sharing this.

• Datil
  Shuey Jun 11, 2013 at 11:37am

  Thanks for the spam post Chris, it was very relevant and helpful to this topic.

• Tabasco
  Pikkoenig Aug 26, 2013 at 09:25am

  I was searching the whole Internet for a description like this (at least it felt like the whole Internet).
  Google was not my friend that day. All the How tos wer not what I was looking for or did not describe the parts I needed.
  Until I found a nice How To with a comment that helped me.
  Today I thought to myself... Take a look in the Spicy How To's and I think I should not have done that because it shows me now, that this should have been the first thing to do :-|

  I made it to install the printers without this How To, but I would have saved a lot of time if I had found this How To before :)

• Datil
  Shuey Aug 26, 2013 at 12:14pm

  Glad you found it Pikkoenig! :)
  I hope I'll have more good articles/how-to's to come ;)

• Pimiento
  IUCN5406 Feb 13, 2015 at 02:19pm

  Thank you for the clear explanation! I found I had to remove the printer name before I could remove the printer port. If I did it the other way arround I got an error message saying something like: the device is still in use.

• Tabasco
  Joe979 Aug 31, 2015 at 01:13am

  Very interesting how-to! And the frustration is definitely real when it comes to dealing with vendors that won't work with you... That is quite awesome that you were able to come up with a way around it :) I've had instances where I had no other way of doing something outside of the CLI, so I absolutely had to poke around various commands to get the output I was looking for. I actually stumbled on this trying to figure out why a printer would map to someone's profile that didn't have any GPO triggering it, but I'll keep this one bookmarked so I can play around with it later!

• Pimiento
  xaerienamnori Apr 19, 2017 at 08:47am

  This was a very great walk through. You made it seem very simple. Not one error on my end during this whole process. I really appreciate the time you took to explain this from your perspective. This script (and more importantly your break down of usage) saved my team and I hours of manual work.. Thank you again!

• Serrano
  Dusty_White_Hat Dec 7, 2017 at 09:02pm

  I think it's waaaay easier just to use the remote functionality of the built in MMC component:

  Here is the write up for that:
  https://community.spiceworks.com/how_to/127141-install-or-delete-printers-remotely-with-print-manager

• Datil
  Shuey Dec 7, 2017 at 09:05pm

  Dusty: Your idea would be great if we had the ability to administrative authenticate to our vendor workstations with Print Administrator, but that's impossible in our environment.

CEO

Phil Cartmell

Group revenue up 33% (H1 2019 : £20.60m)

Adjusted EBITDA (H1 2019: £2.3m)

T-group Driver Test

Group closing order book up by 13% (H1 2019: £56.8m)

“We have a robust core business built on delivering mission-critical solutions for a safer world. Using our proven professional services and technologies, we are investing in some of the most exciting global growth markets including clean energy, autonomous navigation and artificial intelligence.”

Andrew McCree

Non-executive chairman

Key Links

T-group Driver Salary

Cookie Policy | Privacy and Cookies | Terms and Conditions | Modern Slavery Act