Recently, after setting up a number of new machines with Office 2013, I discovered one had the wrong product key and needed to be changed. The easiest and quickest way I found to change it was from the command line.

Open up a Command Prompt (Press the Windows Button and type CMD or navigate to All Programs -> Accessories -> Command Prompt).  Then you just need to use the command below that matches your OS.


For 32 bit Windows:

[geshi lang=”winbatch” nums=”0″ target=”_self” ]

cscript “C:\Program Files\Microsoft Office\Office15\OSPP.VBS” /inpkey:yourproductkeyhere


For 64 bit Windows (assuming you are using 32 bit Office):

[geshi lang=”winbatch” nums=”0″ target=”_self” ]

cscript “C:\Program Files (x86)\Microsoft Office\Office15\OSPP.VBS” /inpkey:yourproductkeyhere


Obviously, you need to replace yourproductkeyhere with your actual Office product key.


Note:  If you are installing a 64 bit version of Office on 64 bit Windows, the command for 32 bit Windows should be used (or just delete the (x86) part since it won’t be installing to the C:\Program Files (x86)\ directory).


A common error that terminal server administrators will bump into every now and then is the “The terminal server has exceeded the maximum number of allowed connections” message.

This problem happens because Windows only allows two remote terminal services connections when you are in administrative mode, and you’ve either got two people already on that server, or more likely, you’ve got a disconnected session that still thinks it is active.

If you happen to be at the same location as the server and can physically log into its console then you this is fine as you can log in and clear the connections. However, things can get a little more annoying if the server is at a remote or client site.
Open a command prompt and type:

mstsc /v: /admin


mstsc /v: /console

Replace “” with your server’s IP Address.

This will connect to the physical console session on the server, thus temporarily getting around the session limit. Please note, however that you may only get one chance at this and if you get disconnected from this session you may have no choice but to physically go to the machine. Therefore, once you get logged in, go straight to Administrative Tools, open Terminal Services Manager and clear those pesky logged sessions! 😉

Today I needed to capture a screen shot of the Windows 7 UAC prompt for a How-To document I was writing and discovered that you can’t… by default.

Fortunately, there is a registry change that can allow the PrtScn key to work while these prompts are on the screen.

To prevent Windows from switching to Secure Desktop mode when the UAC prompt appears:

  1. Click Start
  2. Enter regedit in the Search box
  3. Navigate to the key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
  4. In the right-hand pane, right-click, select New, and then DWORD (32-bit) Value
  5. Enter PromptOnSecureDesktop for the new entry’s name
  6. Right-click your new entry and click Modify
  7. Enter 0 in the Value data box and click OK
  8. Close the Registry Editor

You may have to reboot your system for this change to take effect, although I didn’t today.


The latest update to Windows 7 known as “Windows 7 Service Pack 1” was released yesterday so some of you may be wondering what new and exciting things installing this will bring to your PC.

The truth is most people won’t notice any difference in how Windows 7 looks or operates after installing this update. Believe it or not, that’s actually good news! It means that Microsoft learnt from their mistakes with Vista and turned out a Windows update that was relatively problem-free, right from the start.

The new features are reserved for Windows Server 2008 which shares the same foundation as Windows 7.

However, it is still important to install this update from a security perspective. You want to keep your computers up-to-date to help ensure you are protected from “security holes” as much as possible.

And for those still clinging to Windows XP, unless you are completely attached to the almost nine year old system, the wait to upgrade is over.