About Me

My photo
This is a blog for John Weber. One of my joys in life is helping others get ahead in life. Content here will be focused on that from this date forward. John was a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). I used to write a variety of articles (https://tsoorad.blogspot.com) on technical issues with a smattering of other interests. 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. The opinions expressed on this blog are mine and mine alone.

2013/04/12

Lync 2013 Internal and External Web Sites

Lync 2013 (and 2010 for that matter) documentation recommends using a Reverse Proxy to abstract the Lync Server Front End Web Services from the baddies on the outside world.  A cursory look at a Lync Front End Server will reveal that the Lync Server installation process does indeed create two websites.  But what is the difference?  What might be the possible reasons for having two websites?

Here is a typical Lync EE pool server IIS manager showing the Lync Web Services.

image_thumb[1]

Two websites. Because the websites are both using the same IP address, different ports are needed. If you look at the binding for each you will see the External answering on ports 8080 and 4443 while the Internal is setup on 80 and 443. 

image_thumb[5] image_thumb[6]

Because we are exposing our internal server we want the Reverse Proxy to stop traffic and play fetch for us.  Understandable, yes?  Because we have two websites that are different but on the same IP, we need different ports.  Again, understandable.  But if you look at the following eye-chart – you can also see that there are differences in the virtual directories. The Internal virtuals down below that are different from the external website (in addition to, and similar but named differently) simply have no business being exposed to non-internal users; I think the virtual directory names provide all the clues you need to agree with that assessment: CSCP (the control panel), OCSPowerShell, and RGSconfig (Response Group Configuration page) jump out at me. 

image

If your Lync Web Services get their authentication scheme messed up (now how would that happen?) you can also use this handy chart to return the website and virtual directories to their initial state.  How convenient is that?

So, we can see that there is a few reasons to have two websites:  two websites on the same IP but using different ports, the difference between virtual directories on the internal v external websites, and the content that is not very desirable to expose to external users who just might not be your best friend.

YMMV

2013/04/03

Lync 2013 CU1 UCWA Errors

Just had a small issue trying to publish Lync 2013 Topology where it would appear that the Lync Server 2013 CU1 update duplicated all the 2013 FE Server MSRTCSIP-TrustedService entries for the UCWAInternal and UCWAExternal services.  Everything looked fairly good until it came time to enable-cstopology.  Here is the error we got.

“Multiple Active Directory entries were found for type “MS-RTC-TrustedService” with ID of fqdn.domain.com/UcwaExternal.

image

Fixing ONE of these resulted in the next item on the list being found and then erroring out.

Ouch.

I went through and renamed the service names on all 4 FE servers to update so the enable-cstopology only saw one valid entry.  This was needed on three (3) Enterprise FE nodes and on an SE FE server in the environment.

image

Will update this accordingly if this proves to have borked up something else.  Why this occurred is not known to me, other than running the CU1 updates into the environment.

YMMV.

2013/03/27

Office WAC (WAS) Server Update and Lync 2013

Microsoft has an update, if you can call it that, to the Office Web Apps Server that is used (amongst others) by Lync 2013.

This “update” is 584MB of download, and will require the following procedure to update your Lync 2013 WAS (WAC) server(s).  If you have a one server pool, no problem.

Open powershell on the host server as and administrator….

Remove-OfficeWebAppsMachine

Do a Get-OfficeWebAppsFarm just to confirm the box thinks the farm is gone.  Then run the update.  It won’t take but about 10 minutes and wants a reboot.

Then recreate your Office Web Apps Farm with “new-OfficeWebAppsFarm”

If you have a pool of two or more servers, then you might think you can do one node at a time, right?!  Not so fast young Padiwan.  Remove the WebAppsFarm in its’ entirety.  As in take it completely down.  Go to each node in the farm, and run the Remove-OfficeWebsAppsMachine.  Once the last server is out of the farm, ensure the farm is really gone.  Then run the patch/update in, then reboot the entire mess. After that, recreate your Office Web Apps Farm.  You did record all those commands when you first put the farm together, right?

Enjoy taking the entire farm down for an update.

YMMV.

2013/03/25

Lync 2013 WAS Handler Error 500.21

This whole thing started very simply.  Install a Office Web Apps Farm for a Lync 2013 deployment. 

We are using Server 2008R2 SP1, fully patched.  The Web Apps Server (WAS) installed correctly, or so it seemed.  But then the farm failed to create.  This was tracked down to MS KB 2670838 getting in the way of installing MS KB 2592525 – removing MS KB 2670838 solved that – with a weird side-note – removing 2670838 also removed IE10.  There is ample evidence on the web that 2670838 is dirty dirty dirty, bad bad bad.  Things are starting to go sideways here!

So we finally got the patches straight, MS KB2592525 goes in.  Now the farm created, but then we could not hit https://fqdn.domain.com/hosting/discovery with an error of 500.21, and a claim of “ http error 500.21 handler “discoveryservice” has a bad module managedpipelinehandler” …  El Yucko!

After some searching back and forth, it seemed that asp.net was either not installed or was not registered properly.  Looking at the installed set of programs and features on the IIS indicated that ASP.net was indeed installed….

image

What was needed was to reregister the ASP.

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

Finally.

YMMV

2013/03/22

Logitech USB Headset Stereo H650e (A-00057)

Wow, what a name.  Makes me think that I am back in the Army looking at the “nomenclature” for a “pin, retaining, bolt, rifle, M14” or some such.

I also have a Logitech USB Headset Mono H650e (A-00050) on hand.  Comments here will apply to that device also, with the understanding that the single-ear headset will never touch my sacred skull except for testing.  I don’t know how people do this one-ear thing.  I have a hard enough time with my cell phone Bluetooth for a short call, let alone something for all day use.

As a disclaimer, Logitech did send these units to me for evaluation purposes; however, there were no strings attached, nor any pressure to say anything good – or bad – about these units. Folks who know me are well aware that if something sucks, I will say so.

Features

The headset itself is very comfortable.  I used it all day today – essentially non-stop.  I never got any feeling that I needed to take it off – not something I can about my other headset (also a Logitech) which is several years old and much heavier.  The microphone boom on these units is adjustable for both angle-of-dangle from the earpiece as well as actually adjusting the boom itself to be where you want it.

The wire/cable leading from the headset to the USB connector is flat – supposedly to be a non-tangle feature.  Well, it works out to be true.  There is also a handy-dandy clip you can attach to the headset lead to hold the lead to your clothing and keep the control module off the desk where I typically stick my arm on it leading to unpredictable button pushes.

The control module itself has a microphone mute button, volume up/down, and an answer button.  The nicest thing about this headset (other than it having excellent audio quality) is the interface with Lync.  The mute button toggles Lync itself – Lync reflects muted and not muted. 

image

The call answer button will answer a Lync call and also hang up a Lync call.  Nice.

Audio Quality is excellent.  The headset earpieces are all-day comfy and the headband has a nice cushion on it to keep your head from not getting a hot-spot and causing headaches.  The volume control worked well, and the definition was much better than my current (old) Logitech unit.  My one complaint about the unit is that the microphone is so good I had to go into Lync and turn the microphone sensitivity waaaaaay down to make it appear that I was not shouting.

image

As a final piece of niceness, the back of the microphone boom has a red light that lights up when you are on a call.  Someone walking up behind you has a visible indication of you being busy!  This worked twice already today when someone walking in could see I was active on a call.

image

Conclusion

Overall quality, IMHO, is most excellent.  Audio, fit, finish, comfort and controls are all at the top of the chart.  Installation onto my laptop consisted of plugging into a USB port, waiting about 10 seconds and starting to use it.  Painless, and very typical Logitech.  Nothing else required.

The stereo unit is now my daily device.

YMMV

2013/03/21

Lync 2013 RASK

 

Have you decided that you don’t have enough light reading in your life? 

Lync 2013 Rollout and Adoption Success Kit (RASK) Core Planning Resources

http://www.microsoft.com/en-us/download/details.aspx?id=37030

Lync 2013 Rollout and Adoption Success Kit (RASK) User Education and Training Resources

http://www.microsoft.com/en-us/download/details.aspx?id=37032

Lync 2013 Rollout and Adoption Success Kit (RASK) Resources

http://www.microsoft.com/en-us/download/details.aspx?id=37031

Enjoy!

2013/03/07

Lync 2013 User Quick Reference

Realizing that this is old news to you seasoned professionals out there, here is a great set of Lync 2013 User Guides – Quick Reference documents.  The imbedded links pull up PowerPoint documents that you can print and distribute to your users.

http://office.microsoft.com/en-us/quick-reference-cards-about-lync-HA103433496.aspx

YMMV

test 02 Feb

this is a test it’s only a test this should be a picture