Archive for the 'Microsoft' Category

Current Project: Winsitter.com

This blog has seen less action over the last year due to my activities related to a personal obsession of mine: Creating a web startup to help keep Windows Servers up and running on autopilot.

As a consulting engineer for various small and large organizations, I can say it is the norm for users to actually be de facto monitoring solution.  They are the first to know of an outage.  Many small and medium business admins settle for this because they (and management) seem to assume that either:

  1. Good server monitoring is expensive or too hard to even consider.
  2. That it’s possible to prevent some outages with basic monitoring.

All this goes on while server manufactures and the Windows Server OS doesn’t offer the one feature they need: a basic built-in notification service for the 20% of issues that cause 80% of the problems.  Hardware and OS’s tend to log the problems, but those get lost in a sea of log data.  Why doesn’t my Dell server ask me for an email address to notify of hardware errors/warnings on first boot?  Why doesn’t Windows have a one-button option to turn on basic email alerting of service failures, unplanned reboots, or other monitoring 101 stuff?

Well enough wishing.  Time we did something about that for those who don’t have the time, budget, server recourses, or skills to deploy an in-house monitoring solution.

Sign up for my beta invite list and stop guessing if your servers are OK. http://winsitter.com

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.

IE9 RC and Java

If you’re running the IE9 Release Client (huge improvement over IE8) and sites are crashing it could be that your Java isn’t updated to version 6 update 24.  Versions before that (I had update 23) will crash the web page and send it in a loop of crash, reload, crash, etc.  You can also click the compatibility mode button (if you’re fast enough) to prevent the crash.

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.

Subscribe

Twitter Updates