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.


Static Routes in Server 2008 R2 Not Consistent

The Issue:

Onsite with a customer setting up the initial E2010 DAG MBX servers.  In constructing the MAPInet and REPLnet NICs on each server, we noticed that the static routes were not behaving as expected.

We checked the commands for establishing the static routes and how the NICs were setup.  We were consistent across the board, on both subnets and sites.  As an example, here is what we were using from the one site:

route add mask if 15 –p

This resulted in a 80% failure rate at that one site to establish a static route for the REPLnet traffic (for you score keepers, this equates to 40% failure across the environment).  Obviously, we cannot continue with DAG construction until this is resolved.

The Fix

netsh int ipv4 add route “replnet”

Using the netsh method resulted in 100% success at not only putting a persistent route into place but actually having it work!

Thanks to http://fixmyitsystem.com/2010/10/adding-static-route-using-netsh-and.html for having a nice little article on this subject.



2008r2 and TMG and VPN = NO!

The Issue

Having just ran around the world on this, it would appear that even with TMG SP1, Server 2008R2 does not allow TMG to do simple PPTP VPN. I foolishly thought I would insert the VPN service into my lab as a quick test.  All my web publishing rules continued to work flawlessly; Lync Web Components; NAT for my Lync, Exchange 2010 publishing – everything worked except VPN.

If you are intensely interested, the VPN connection would be made, but no traffic was allowed to flow.  Don’t know why, and at this point I don’t much care. 

The Fix

I fixed it by building a new server on 2008 SP2.   If you are doing a project that includes TMG and want to have the same TMG provide VPN, you should most likely think about it and lab it before you continue.

Hopefully, someone can point out the errors of my ways and show me what I did wrong.  YMMV.


Open Services applet in Standard Mode

Ever since somebody at Microsoft decided we needed the services.msc applet to open in “extended” mode, I have been clicking on “standard” to get the view I wanted.  This last week I finally got fed up with this, and decided to do something about it.  As it turns out, this is not the easiest thing to change.  Apparently, us poor users are not allowed to change the behavior for the named services.msc.  We are not worthy. 


What you have to do is author a new named instance – and of course remember to use that one.  I was unsuccessful at renaming, deleting, or otherwise removing the original services.msc.  I am sure there is some method to do so, but I was unwilling to dink too much with an operating system that was working before I messed with it.  YMMV.

Here is what I did: (the example is using an x64 Win7 O/S, but it works equally well for Server 2008, and I imagine, Vista (why are you using that?).

Go to c:\windows\system32 and locate the services.msc applet.  Right-click it and select “author.”


When services opens, click File | Options as shown.


Now, change that console mode to “author.”


Say OK to this…

Change the view to standard…


Now, save this to a name and location of your choosing…


Now when you go to a command line (or in my case about 90% of the time a powershell prompt), and type in jmwservices.msc, I get this “new and de-proved” services applet in standard mode.  I suppose you could mod the original references to the new applet if you want to get fancy.




Lync Client Add-ins


Tabbed IM conversations!  Nice! 


Conversation Translator.  Conversation Translator provides a real-time language translation service for Lync instant messaging (IM) conversations. With Conversation Translator, both the sender and receiver can converse in their native language, and Conversation Translator handles the translation. 


Conversations Analyzer for Microsoft Lync 2010. Conversations Analyzer is an application that reviews your Microsoft Lync instant messaging (IM) conversation history and gives you scores for your use of trust-building language in day-to-day communications with business associates and friends. Conversations Analyzer applies trust rules to determine the occurrence of words and phrases that have a positive or negative effect on trust. 


test 02 Feb

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