How do I – Activate my MSDN copy of Visio 2013 Professional?

Written by Cornelius J. van Dyk on . Posted in Blog, How Do I...

Situation:  You have a MSDN subscription and you have downloaded Office 2013 or one of the Office products, like Visio 2013 Professional, from Microsoft and have installed said product.  You have a license key provided by MSDN, but the installer never prompts you for the license key.  This is a departure from traditional installer behavior where you would enter the license key before the install can even be done.  Once you’ve completed the install, you open your product and are confronted by this little gem of a warning just below the Ribbon:


Since you have a license key, you click the “Activate” button.  You are presented with this screen which is there for a while, so be patient:             


Eventually, you’re presented with a Sign In screen like this:


Having gotten your license key from MSDN, you promptly enter your MSDN UserID and password and click the “Sign in” button.  Unfortunately, you’re presented with an error thus:


After trying the login a couple more times (just in case you fat fingered the password), you click the “Can’t access your account?” button.  Your browser opens and you’re taken to this page:


Again, you enter your MSDN UserID as well as the CAPCHA code and click the “Next” button.  This time you’re presented with an error screen stating that your ID doesn’t exist thus:


So now what?

This is the problem with the new installer.  In order to use our MSDN license key, we’re going to have to follow these steps:

  1. Click “Start”.
  2. On the popup menu, click “Control Panel”.
  3. In the Control Panel, double click the “Programs and Features” icon.
  4. Scroll down through the list of installed products and locate the product in question.  In this example it was “Microsoft Visio Professional 2013”.
  5. Select the target product.
  6. In the toolbar above the list, click the “Change” button.screenshot.498
  7. When the configuration window appears, select the “Enter a Product Key” radio button and click “Continue”.screenshot.499
  8. No enter your product key and click “Continue”.screenshot.500
  9. Unfortunately, you have to go through the configuration piece again.  For a simple license key addition, I don’t see the need in this, but that how it works for now.  You could just click “Continue” but in my case, I wanted to make sure nothing was getting reset so I clicked “Customize”.screenshot.501
  10. Ensure your configuration settings are as desired and click the “Continue” button.screenshot.502
  11. It sets in the Configuration Progress screen for quite a while.  Just be patient.screenshot.503
  12. Once the configuration completes, click the “Close” button.screenshot.504
  13. Finally re-launch the application and the red warning should now be gone.screenshot.505


This took me a while to figure out, so hopefully this saves someone some time.




InfoPath is dead!

Written by Cornelius J. van Dyk on . Posted in Blog

InfoPath is dead!  We all knew it had to happen eventually.  The Office Team blogged on the Office Blog today noting the death of InfoPath.  From the third paragraph:

“This means that InfoPath 2013 is the last release of the desktop client, and InfoPath Forms Services in SharePoint Server 2013 is the last release of InfoPath Forms Services. The InfoPath Forms Services technology within Office 365 will be maintained and it will function until further notice.”

There will be no future version of InfoPath.  Not much beyond that is shared at this time, except the assurance that there’s another 9 years left of official support for On-Prem InfoPath deployments.  A sneak peak of what’s to come is supposed to be in the “Update on InfoPath and SharePoint Forms” session at the SharePoint Conference in March.  We all knew it was coming so it shouldn’t be a big surprise that it’s finally here.  I think more surprising is the fact that Microsoft waited this long to announce that the 2013 version was the last version.  That should make for some interesting developments as far as SharePoint forms go.