Tag Archive for 'Microsoft'

Lync 2010 Virtualization Support Summary

Taken from the Deployment Guide and the Server Virtualization Guide:

  • If you decide to go virtual, Lync only supports Hyper-V R2 or ESX 4.0 platforms. Windows Server 2008 Hyper-V is NOT supported as “A number of enhancements that are critical for running virtualized Lync Server media workloads were implemented with Windows Server 2008 R2 to address network packet loss.”
  • If you choose virtual. All roles in virtual must run on Windows Server 2008 R2 as the guest/child OS, citing more network optimizations.
  • In general, all roles can be virtualized, except for the 3rd party Survivable Branch hardware appliance (obviously).
  • You need to decide physical or virtual on a per pool basis. Inside the pool, the roles on separate servers (physical or virtual) need to be of similar resources (hardware), as “Balanced end-to end-performance is required.”
  • The exceptions to this rule, is you can always choose the Front End to be virtual and the DB backend to be physical in any scenario.
  • Virtualization high availability features (Windows clustering, VMotion, Live Migration, etc.) are not a substitute for Lync’s built-in redundancy features inside its architecture (multiple front-end’s, SQL redundancy, etc.).
  • Even in a small virtualized pool, the following are not recommended: shared networking port for host and guests, shared disk spindles for host and guests or for multiple guests, network connectivity less than 1GB, and dynamic disks.
  • Disabling IPv6 on the host and guests will improve performance (although it doesn’t specify which technique to use for disabling. Is unchecking the box in Network Connection Properties enough even though it doesn’t completely disable IPv6?).
  • Notes are included for enabling VMQ on Intel network adapters and other driver/reg modifications to improve performance.

Maybe it’s just me, or maybe I’ve not read other Microsoft server virtualization recommendation white papers… but this one was particularly detailed and full of real-word guidance for sizing virtual and physical machines, including what perfmon counters to use for baselining. Bravo Lync team. If only all server apps came with this level of detail.

Share Your Paid Wifi with Friends

Virtual RouterEver been in a hotel, airport, coffee shop, or some place that you pay per computer to use their Wireless Internet?  Windows 7 has a new feature “Virtual Wifi” that lets you use your wireless as if it was multiple wireless NIC’s, but why do we care?  One way to use that virtual wifi feature is to use free software to allow connecting to wireless Internet while also turning your wireless into it’s own hotspot.  Great for the wife’s or coworkers laptops sitting next to you.  Pay once, surf many.

There’s been a similar feature since XP to share connections, but this required you to use two different NIC’s and only supported peer-to-peer network. This software fixes both issues.

Software: Virtual Router – Wifi Hot Spot for Windows 7 – 2008 R2

Info: Share Wireless Internet Connection In Windows 7 Without Ad Hoc

Quickest Way to install SQL 2008 on Windows Server 2008 R2

From KB 955392 there’s lot of info there, but the quickest “one time” install method is to follow “Procedure 1: Basic slipstream steps”

  1. Install the .NET Framework 3.5.1 feature
  2. Download the SQL SP1 service pack
  3. Expand the service pack by using 7zip or the command SQLServer2008SP1-KB968369-x64-ENU.exe /x:C:\SP1
  4. Install the SQL Setup Support files from the SP1 download C:\SP1\x64\setup\1033\sqlsupport.msi
  5. Now run the SQL Setup.exe from DVD or network and point setup to where SP1 is Setup.exe /PCUSource=C:\SP1

Note the long term best method is “Procedure 2: create a merged drop” but the above is great for the 1 or 2 installs.

The OCS 2007 R2 Communicator hyperlink mystery

I don’t think this problem/solution is much different in older versions.

Problem: when you send a link from Communicator client to another, the link isn’t clickable, has a _ (underbar) in front of it, or both.  Results may be different on different computers. It’ll look like this

_http://www.google.com

Solution:  Two things are happening here that are not related.  The first is the OCS Server (and Edge Server) have the URL Filter enabled, which are adding the _ underbar to all links.  Also called “Intelligent IM Filter”.  You need to tone that filter down or disable all together to your liking.  If users are coming in through an Edge Server, they will follow the Filter settings of the Edge Server they are using, which seams to supersede the Front End Server (my guess is the most restrictive wins).  So be sure to set it on both servers separately.  Results were instant in new IM’s.

The other issue is the lack of a clickable hyperlink.  If you disable the URL Filters above, the underbar goes away but links are still not blue and underlined.  To fix this you need to apply a GPO or set a local registry setting to allow Communicator to make hyperlinks clickable:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator\
new DWORD EnableURL=1

After that exit and restart Communicator.

In both of these cases they are secure by default, which is great; but even years after this features release over several versions their use and configuration are still a mystery to most starting out.

ActiveSync Random Password Prompts Fixed

They were getting random prompts for passwords in ActiveSync on Windows Mobile 6.0 and 6.1.  They had Exchange 2007, and ISA Server 2006, but this problem showed up months after Exchange was migrated to 2007.  It seemed random.  The error on ActiveSync was the generic:

please log in access was denied 0×85010002

In the ISA Monitoring you would see a denied connection on your ActiveSync rule with this status:

12239 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator.

I tested with Windows Mobile Emulator from outside the firewall and was able to reproduce the error within hours (just letting it sit there).

I first thought this was the HTTP session timeout that changed with a Exchange 2003  service pack when Direct Push came out back in 2005.  I remembered that setting and looked under the ISA Web Listener for ActiveSync on the Connections tab>Advanced>“connection timeout”.  The wizard had correctly set it to 1800 seconds (30 minutes). No dice.

I poked around the web listener settings some more and noticed the timeout settings for forms authentication were set (this same web listener was used for OWA).  ISA is supposed to be smart enough to not apply any of the forms auth settings to clients that don’t support it (falling back to basic auth as with ActiveSync).

ISA Web Listener Advanced Form Options

Tom and the forums at isaserver.org confirmed my suspicion.  The forms auth timeout was indeed affecting ActiveSync.  To find it, look for the web listener of your ActiveSync rule, go to properties>Forms tab>Advanced> and make sure “apply session timeout to non-browser clients” is unchecked. 

 

Subscribe

Twitter Updates