The response I received was that this application would support Windows Server 2008 but not Windows Server 2008 R2. I asked about plans to support R2 and was told that the application would not support Server 2008 R2 for some time. In other words they have no plans right now to support it.

My first thought was that this was a bit of an odd practice since Windows Server 2008 R2 is the current version of Server OS from Microsoft. Then I got to thinking about some of the considerations I might need to make to work this application. The only testing to be done is to ensure that the application, once installed, communicates to its supported devices over our network.

My plan is to set the application up using a Windows Server 2008 R2 Virtual Machine just to see if it will even run. If it doesn’t work, a 2008 VM will be tested, but since the functionality of the application is very limited in scope, I thought it was worth a shot. My goal is to spin up a 2008 R2 guest for this testing very soon (next week sometime).

I also started thinking about the difference between “not supported” and does not work. There are many applications that vendors no longer support and configurations they choose not to support that work just fine. Case in point, Windows 2000. Microsoft doesn’t support Windows 2000 anymore. But if I install it, it will run just like it was 1999.

If an application can run on an operating system one step (or half step) prior to current, there are few things that would make it unusable on the current OS. This to me, warrants giving it a shot. I believe that the requirements I got didn’t rule out x64 architecture, thus making it likely to work just fine on the current version of Windows Server. This way all of the servers in our upcoming environment will be consistent on the same OS (for a little while anyway). I also have to admit there are times when I like a challenge… and this is one of those times.

When considering supported applications, it is generally good to follow supported guidelines given by the manufacturer. When the application or vendor provides no technical reasoning or explanation for this choice, it might be worth a try. It comes down to the cost of your time and availability of your resources. If you have the time and resources to test, go for it. If not, well, convenience (and downgrade rights) say that following the stated guidelines is the easiest course.

Applications like VMware do not work on things outside their stated hardware compatibility list. Sure there are some who might be able to work on the edges of that list, but mostly it is definitely easier to work amongst the guidelines of the HCL. Being someone new to VMware, I am following the HCL for sure.

My advice here is dependent on your time and interest. If you are curious and have the resources, test it. If not, do not bother testing it. Being a bit of a geek, I rather enjoy the idea of testing things just for the sake of trying them out. It has helped me learn many different ways to do things as well as just learning about technology. Which I certainly encourage.

I am not saying auditing for internal knowledge of what your organization owns isn’t a good idea, in fact far from it.  I am currently shopping for new tools to aid in keeping an accurate record of what my organization owns against what they are using.  Sure most companies are in compliance when it comes to licensing, but let’s face it, organizations do not run out and get another copy of Office or whatever the app may be when one more user is added to the staff.

Typically, a specific number of licenses are purchased, say 5 or 10 at a time to avoid one off calls to the reseller for another copy of an application and when there is a need for the set minimum copies, another order is placed.

Is this the perfect way to handle licensing, not at all.  Is it recommended? Nope.  However the reality is that there are companies trying to keep up and this is the best way they know how with the budgets they have.

Is it acceptable for an IT manager to refuse to load Office for the new Sales person because they are out of licenses?  Probably not, but should a one off copy be purchased because of the new hire?  Probably not, depending on the budget for IT.  The issue isn’t if an organization will buy the applications they use, in most cases they will.  For me the issue is timing of spend.  If I am working with a budget, I will know when the budget is prepared how much I can spend on licenses early in the year.  Once I have used all allotted monies for applications,  a one off purchase can be quite challenging to handle.

How to manage the audit issues

There are several applications available to help with software counts and tracking, but the most important thing is that the project gets tackled and reviewed regularly.  Since licensing is evolving with every release and companies have to watch their cash more than ever in this economy, knowing where you stand with application licenses could be a great way to invest and save money long term. 

Note: Normally I would review a product to aid with license auditing and compliance, but having not selected on myself I cannot yet provide a review.

We are looking at a couple products:

IQuate – IQ Netscan

GFI – Languard

And I also keep the information I know in an excel spreadsheet.  Hopefully once we have an auditing solution in place, the maintenance of the Excel sheet will be far less intensive.

What to watch for

The biggest thing to keep track of is the number of licenses that your organization owns for each product they use.  So if you have 25 licenses for Office, keeping track of that number and modifying it as more are added is beneficial for sure.

Also, make sure you know how many copies of an application are installed.  This will likely be the hardest task without some help, but getting this number figured out is important.

These two pieces of information will be extremely useful in determining the discrepancy between owned and installed licenses (if any).  This way you can determine how many licenses you’ll need to buy to match the install count. 

Another useful thing to note is the cost per license of the application.  This way you can approximate the cost of the licenses needed and weigh hard numbers against the cost of not being in compliance.  Surly purchasing licensing is more affordable.

Good luck in the realm of License management and hopefully the links and tips provided can help you keep your organization compliant.

Using programs like Microsoft Software Assurance and Open Value can help your organization stay up front with both applications and their licensing which is so important for IT administrators to consider.

I am not a licensing expert – yet.  Hopefully in the near future I will get started down that path, simply to help my organization and others better understand the lengthy and very snooze worthy EULA.

Licensing seems to be the glue that either holds the IT organization together or the frustration that causes early baldness in IT pros all over.  I am not sure why the documents are so hard to comprehend (and yes I know that they really aren’t that bad, but you have to read them).

It seems to me that Microsoft (and other organizations) want to get all the possible scenarios into the license so they do not miss anything or leave any loopholes, which is understandable, but the efforts to do so seem to pull all of the trustworthy out of computing.  If you cannot trust your users and have to put huge license agreements out for all products except Bob (surely all of you have seen MS Bob), most aren’t going to read the EULA anyway.  This does two things:

1. gets the user to agree blindly to the terms laid out in the EULA

2. gets the vendor nowhere in terms of its customers understanding the agreements they put out.

One thing I would like to know is where can one go to find materials to learn about how licensing works not to mention get the EULA for a product before purchasing it?  Sure there are sites and books and blogs about licensing, but what training material is out there for the beast?

I do not have a huge issue with licensing other than trying to learn it.  Really it is there to protect the manufacturer and the user and should be followed, but when I saw the Windows Server 2008 Licensing for Dummies hand out at Tech Ed, it made me wonder why would they need to even joke about a Dummies manual for licensing?

Hopefully licensing gets more user friendly in the future, after all the word user is even in the title of the document.  They aren’t called the IT Professional License Agreement.

Have any of you found a good tactic for learning more about licensing or a way to gain from reading product EULAs?  If so, post in the comments or contact me, I would be interested in finding out how others handle it.

Update: Poll added below

[poll id="6"]