About Me

My photo
TsooRad is a blog for John Weber. John is a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). My day job is titled "Technical Lead, MS UC" - I work with an awesome group of people at CDW, LLC. I’ve been at this gig in one fashion or another since 1988 - starting with desktops (remember Z-248’s?) and now I am in Portland, Oregon. I focus on collaboration and infrastructure. This means Exchange of all flavors, Skype, LCS/OCS/Lync, Windows, business process, and learning new stuff. I have a variety of interests - some of which may rear their ugly head in this forum. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. One of these days, I intend to start teaching. The opinions expressed on this blog are mine and mine alone.


LM and OC password lockout

A bit of trivia I discovered today.  The OC client and the LM client are sort of linked at the hip. I backed into this via Outlook and the LM addin…because I got locked out of my office account while testing the client’s install.  Something got bollixed up with the passwords…and here is what happened.

While doing some testing I had to change the login account on my OC.  I noticed that when I did that, the LM client picked up the change.  Nice!


But alas!  the password in the LM client account setup remains as the previous login…


Naturally, this resulted in the account being locked out for password failure.  So, while the LM did pick up the user name change, it bombed on the password.

Also, note that this is different depending on which way you work it…certainly not a two way street.  In the first scenario, I changed the username from OC, and LM picked up the change but not the password.  Going the other way is even worse; changing the username in LM only sent the sign-in name to OC client… the underlying verification stayed the same in both clients – and both were wrong.  In addition, the LM had the password from the other account!


Let’s hope this get’s fixed in CS 2010 where the LM and OC are one client.

disable “Schedule a Conference Call” button in Outlook LM plugin


I got asked today on how to do this.  Being as clueless as I am, I started with a little research.  Doggoned if I didn’t hit paydirt after only a few reads.  This is good stuff, so I want to make sure that I don’t lose it.

See this article here for the original material – figures there would be a KB for this.  I am reposting here for my own edification.

There is a registry entry that can be used to disable this button:

1. Locate and then click to select the following registry subkey:

HKEY_LOCAL_MACHINE\Software\Microsoft\Live Meeting\Addins

Note Use this subkey for x86-based systems. If you are running a x64-based system, locate and click the following subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Live Meeting\Addins

2. After you select the subkey that is specified in step 3, point to New on the Edit menu, and then click DWORD Value.

3. Type RemoveConferenceCall, and then press ENTER.

4. Right-click RemoveConferenceCall, and then click Modify.

5. In the Value data box, type 1, and then click OK.

6. On the File menu, click Exit to close Registry Editor.

Change the Value to 0 and the button will be available again.

A full list of livemeeting registry keys can be found here: http://technet.microsoft.com/en-us/library/dd637135(office.13).aspx

What Vacation Taught me

I took vacation this year; a formal thing with travel, schedule coordination, planned activities, and days full of interacting with others. ...