Geek projects, tidbits and things I'm working on at the moment…

We had an employee who had a broken installation of Office 2010 Pro Plus. We use Microsoft Online Services (now called Office 365) and in particular we use their E3 plan for most of our employees.

Simply doing a …

cd "%ProgramFiles(x86)%\Microsoft Office\Office14\"

dir *.vbs (you're looking for the OSPP.VBS file.)

cscript ospp.vbs /dstatus
(will show you something like this)
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
SKU ID: ae28e0ab-590f-4be3-b7f6-438dda6c0b1c
LICENSE NAME: Office 14, OfficeProPlusSub-Subscription edition
LICENSE DESCRIPTION: Office 14, TIMEBASED_SUB channel
LICENSE STATUS:  ---LICENSED---
ERROR CODE: 4004FC04 as licensed
ERROR CODE: 0x4004FC04
ERROR DESCRIPTION: The Software Licensing Service reported that 
the application is running within the timebased validity period.
Last 5 characters of installed product key: HMBFK
REMAINING GRACE: 26 days  (37247 minute(s) before expiring)
---------------------------------------
---------------------------------------
---Exiting-----------------------------

C:\Program Files (x86)\Microsoft Office\Office14>

Can show you whether or not you’ve got a problem. If you do, you can reactivate the Office subscription if yours shows —NOTIFICATIONS— for its license status by going into directory…

C:\Users\faileduser>cd "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE14"

and running

osaui.exe /K or /F

via cmd with either /K to do a password reset or /F to change users or reset the subscription back to basics. You can also do a /r if you need to remove another device which is using your current subscription.

Here’s a couple of links:

http://support.microsoft.com/kb/2684927  (Very helpful! Gives the actual error codes your users will probably see!)

http://office.microsoft.com/en-us/word-help/reactivate-subscription-license-by-using-osaui-exe-HA102053194.aspx

http://support.microsoft.com/kb/2512834  (Remove some other device from your subscription. /r will show you a list and you can see whom to remove!)

http://technet.microsoft.com/en-us/library/gg702620.aspx (General troubleshooting tips for Office 365 Pro Plus)

http://blogs.technet.com/b/lystavlen/archive/2011/12/05/in-opp-five-is-the-magic-number-but-then-what.aspx

So, for some time now I’ve worked w/ HTTPS and SSL and have had no real issues. Today however, I finally got a chance to put multiple SSL sites on one IIS 6.0 server which wasn’t very intuitive. HTTPS is funny in that the host header data that a web server needs to have access to is encrypted and can’t be used until it’s decrypted. Course for it to decrypt the packet, it must know which certificate to use and very quickly we’ve got a circular issue. Long story short, web servers CAN host multiple SSL websites so long as the sites are variations of  <something>.example.com and you use an apporpriate wild card certificate that will cover all the different sites on your HTTPS web server (such as an SSL certificate issued to *.example.com to cover all of the variations of <something>.example.com.) Ya, I know, confusing.

So while I was applying my craft to a Windows Server 2003 R2 box running IIS 6.0 I quickly encountered an error when I tried to put another website on port 443. Error was, “Cannot register the URL prefix https://*:443/ for site ‘<your site identifier here>’. The necessary network binding may already be in use. The site has been deactivated.” I believe it was event ID 1007 in the event viewer system logs. God I love logs 🙂

Quick search on Google reveals you’ve got to go command-line for this one by executing cscript.exe like so:

cd C:\Inetpub\AdminScripts
cscript.exe adsutil.vbs set /w3svc/Identifier/SecureBindings ":443:host header"

.
.
.
.

You can find your site identifier inside of IIS for the site you’re trying to attach on port 443 and just use your site’s FQDN for the host header field.

See this link for a more thorough walk thru:
http://www.digicert.com/ssl-support/configure-iis-host-headers.htm