Manually Export Printer Drivers to install on a Terminal Server


Recently I had a client who was unable to print to his local printer on his Windows 7 x64 bit machine from a Windows 2008 R2 x64 server. Checking the event viewer I could see that Windows was unable to find the driver for the Canon printer. Canon did not have a driver download for a Windows 7 machine or a x64 bit machine for that matter that I could find on their website.

To install the printer driver from the client’s machine i opened the registry and found this printer listed in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\

for x86 its located here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3\

from there if you select the printer key you will see a string value for InfPath

It should give you a path to C:\Windows\System32\DriverStore\FileRepository\ and the corresponding folder the cached driver is in.

I copied the contents of that folder to the Terminal Server. From there I installed on the Server a local printer – Clicked’Have Disk..’ and selected the inf from the folder I copied to the Server.

As a test I logged into the Terminal Server with the users credentials and found that his local printer now redirects correctly. The only thing left to do was delete the dummy local printer we created and your golden.

Special thanks to Vittorio Pavesi for getting me on the right track.

Windows Explorer Defaults to Libraries Folder in Windows 7


When you open Windows Explorer in Windows 7, it opens the Libraries folder by default. You can change the default startup folder using the Windows Explorer shortcut properties, as you did in earlier versions of Windows. Note that you cannot change the default start folder if you’re using WinKey + E to launch Explorer.

In Windows 7, right-clicking on the Windows Explorer Taskbar icon will show the Jump Lists. To access the shortcut properties, hold the SHIFT key down, right-click on the shortcut and choose Properties. Rest of the procedure is the same as in other versions of Windows.

To change the startup folder to (My) Computer, use this target path:

explorer.exe ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Where the GUID {20D04FE0-3AEA-1069-A2D8-08002B30309D} represents the My Computer folder.

For Documents folder, use this target path:

explorer.exe ::{450D8FBA-AD25-11D0-98A8-0800361B1103}

You may also suffix the full path instead of using GUID. For example,

explorer.exe D:\Scripts

Source: WinHelpOnline

PrivateKeyMissing Exchange Certificate Install


I was trying to renew my UCC certificate for my Exchange 2010 server. All was going fine until I tried to enable the certificate. I got the following error message:

Enable-ExchangeCertificate : The certificate with thumbprint *** was found but is not valid for use with Exchange Server
(reason: PrivateKeyMissing).
At line:1 char:27
+ Enable-ExchangeCertificate -Thumbprint *** -Services "IIS"
  1. Open MMC and add the Certificate Snap-In for the Local Computer account.
  2. Double-Click on the recently imported certificate.
  3. Note: In Windows Server 2008 it will be the certificate missing the golden key beside it.

  4. Select the Details tab.
  5. Click on the Serial Number field and copy that string.
  6. Note: You may use CTRL+C, but not right-click and copy.

  7. Open up a command prompt session. (cmd.exe aka DOS Prompt)
  8. Type: certutil -repairstore my “SerialNumber” (SerialNumber is that which was copied down in step 4.)
  9. After running the above command, go back to the MMC and Right-Click Certificates and select Refresh (or hit F5 in the MMC)
  10. Double-Click on the problem certificate. At the bottom of this window (General tab) it should state: “You have a private key that corresponds to this certificate.
  11. Note: In Windows Server 2008 there will be a golden key to the left of the certificate, so there is no need to double-click the certificate.

  12. Now that the Private Key is attached to the certificate, please proceed to enable Exchange Services via Enable-ExchangeCertificate.

Exchange 2010 for SMB’s


I’ve been deploying Exchange 2010 more and more now. Most of them are single server installations or at the very least they only have one server available for exchange. Below are a few tricks I’ve found that help in the deployment.

Recipient Validation

To reduce the load on the server and the amount of Non-Delivery Reports sent by the server (which can get you on blacklists) I strongly recommend that you use Recipient Validation. This will allow Exchange 2010 to reject unknown recipients immediately rather than let your server accept the message and attempt to deliver it and fail. Also, while Microsoft has documentation on how to do this, it is all written with the assumption that you’re using/have an Edge Transport Server. This is how to do it on a Hub Transport server.

First open the Exchange Management Shell
Change the directory to:

C:\Program Files\Microsoft\Exchange Server\V14\Scripts

Run the following command:


Restart the Exchange Transport service.

 Restart-Service MSExchangeTransport

After it restarts you need to tell the service what your internal SMTP servers are, even if you only have one you have to specify it.

  Set-TransportConfig -InternalSMTPServers

Where is the internal IP of your server.
Last but not least you want to enable Recipient Validation you can do that with this command:

Set-RecipientFilterConfig -RecipientValidationEnabled $true

You’re all set! You can test it out with or some other tool of your choosing.

SMTP Banner

I find that this gets skipped a lot. By default your server is probably not reporting your external mail server’s address. This should be the same address that the reverse DNS is reporting. To change this you must do it in the shell. It can be achieved with this command:

Set-ReceiveConnector "From the Internet" -Banner "220"

You must include 220, however, you can change everything else after.

Hope this helps!


Response Point D-Link DVX-2000MS


At my office we have a new phone system called Microsoft Response Point. The system we have was made by D-Link. Great system, you can read countless good reviews on it. However we had a problem with external calls. If the inside caller and the external caller tried to talk at the same time the inside caller would not be able to hear the external user.

The way I finally managed to get this fixed, is by logging into the Response Point Gateway – DVG-3104MS – Remember its IP:9999. The username by default is admin along with the password of admin. Click Advanced and then click Call Control on the left. Change the Default Codec to G. 726-32. voice

I’m not saying that’s the only way to fix the problem, but that seemed to work for us. You can play with the different codec options and see which works best.

Go to Top