CU3 is out. Not listed on the update resource center quite yet, but here they are:
Lync 2010 Hotfix KB 2571543 (64 bit)
Lync 2010 Hotfix KB 2571543 (32 bit)
Lync Server 2010 Hotfix KB 2493736
Lync 2010 Group Chat Hotfix KB 2500446
YMMV
CU3 is out. Not listed on the update resource center quite yet, but here they are:
Lync 2010 Hotfix KB 2571543 (64 bit)
Lync 2010 Hotfix KB 2571543 (32 bit)
Lync Server 2010 Hotfix KB 2493736
Lync 2010 Group Chat Hotfix KB 2500446
YMMV
Onsite with a client and we are having issues with getting Exchange 2010 to enumerate CAS websites.
Here is the lovely error we got:
-------------------------------------------------------
An IIS directory entry couldn't be created. The error message is The remote procedure call failed and did not execute. . HResult = -2147023169 + CategoryInfo:NotInstalled: (servername\Rpc (Default Web Site):ADObjectId) [Get-OutlookAnywhere],
-------------------------------------------------------
Oh lovely. Cannot enable, disable, or get anywhere with this. Poked, prodded, googled, etc. Nada. Finally, in disgust, I believe what I am being told, to whit:
Action 'Disable Outlook Anywhere' could not be performed on object 'servername.'
Servername
Error:
The Outlook Anywhere feature has multiple configurations on servername.domain.com.
OK, so where does powershell get this data from? AD. So off we go to AD. And what did I find hiding out:
CN=Rpc (Default WebSite),CN=HTTP,CN=Protocols,CN=servername, CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
??
Two, count ‘em TWO RPC definitions. Yup, the server (and AD) thought there were multiple configurations. I carefully deleted one, and restarted the server. And now I get much better response in enumerating Exchange web sites/services. And OA can be configured again.
How it got there I have zero idea. Three other CAS servers in the Org are just fine. This one was just fine until about 1750 on 28 June 2011 when it was modified (according to AD) both at the same time. Some sort of hitch in the get-along as far as I can tell.
YMMV.
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26800
The above link shows step-by-step configuration tasks to set up the Direct SIP connectivity between Cisco Unified Communications Manager (CUCM) and Lync Server 2010. These steps include configuration of the media bypass feature that optimizes media flow by allowing Lync endpoints to directly establish a media connection with a gateway or private branch exchange (PBX) without going through the Lync Server Mediation Server.
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 10.12.93.0 mask 255.255.255.0 10.1.26.1 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.
netsh int ipv4 add route 10.12.93.0/24 “replnet” 10.1.26.1
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.
YMMV.
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.
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.
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.
Enjoy!
Tabbed IM conversations! Nice!
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e6e96569-43da-48fa-a4bc-cd63cda1b2de
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.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3db63eb2-190b-47c8-bb8e-e8bbdaf74b07
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.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8bb96deb-2872-4ee8-a96b-9e8e61719ee8