Had this problem on a few machines during a failed upgrade. I found the fix here at Read, Deploy, Enjoy!. Here’s the link. Basically it involves setting the permissions to the STClient Login object under DCOM Config in your Component Services to to “Everyone”.
What I ran into was slightly different. The object wasn’t even showing up on a few computers. I think this is related to how the Communicator is installed from GPO. Especially the old versions if you had to use a ‘trick’ to get the MSI files. This could also be a problem if you have some variation of Roaming Profiles.
Here’s how to remedy the problem.
Step 1 – Uninstall ShoreTel Communicator under the problem users profile, delete all registry keys associated with it, delete the folder under Program Files or Program Files (x86).
Step 2 – Log in as a Local Administrator, or a Domain Admin that doesn’t have any special home profile folders or anything.
Step 3 – Install ShoreTel Communicator from the ShoreWare Director Page on your Server.
Step 4 – Reboot and log back in as the problem user and it SHOULD work correctly. If not follow the instructions on Read, Deploy, Enjoy!
My suspicion is that an installation task fails during an automated install and causes the DCOM object not to be created properly. This probably happens near the end of the install and doesn’t always trigger a failure in the install. Newer versions of Communicator may not use this object at all, so it may be a symptom of a downgrade procedure as well.
Sometimes the Office activation procedure just won’t work for you. No matter how many times you try to get it to connect through the GUI it just won’t do it. You will get this annoying error even though you’re connected to the internet and everything else is working just fine:
Well there’s a way to activate Office 2010, and probably Office 2007 through the command line. This also works with Office 2013, and I’m assuming Office 2016 as well.
Activating Microsoft Office 2007, Microsoft Office 2010 and Microsoft Office 2013 Through the Command Line
Step 1 – Click on your start menu and type “cmd”. This works with windows 8.1. If you’re using Windows 8 or Windows 10, just hit the Windows button on the keyboard and start typing.
Step 2 – Right click on the Command Prompt Icon and click “Run as Administrator”.
Step 3 – Type “cd \” to make sure you are at root.
Step 4 – Type “cd Program Files” (if you are running a 64 bit version of Windows with a 32 bit version of Office type ‘cd “Program Files (x86)”‘
Step 5 – Type “cd Microsoft Office”
Step 6 – Type “cd Office14” if you have Office 2010 “cd Office12” if you have Office 2007. This might work with older versions of Office. The folder you’re looking for will be “Office#”. If you have Office 2013 it will be Office15.
Step 7 – Type “cscript ospp.vbs /act”
Office will be activated if your Product Keys were valid.
I’d like to thank Robert for providing the screen shots for this article.
Update 05/08/2017 – I just confirmed this works the same for Office 2013. I don’t have access to a retail copy of Office 2016 yet but if someone would like to let me know and send a screen shot I would definitely give you credit and use the screenshot. The only Office 2016 I have access to at the moment is a copy of Office 365.