Question Locked

Is my company getting ripped off?

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am trying to find out if my company is getting shafted by their licensing situation with a software company.

We recently migrated our server to a new box. The company that we bought our server 2007 licenses from says that we now need to pay $5200 for more licenses.

We have about 20 employees. They each have a computer running Exchange Server, either Outlook 2000 or 2003.

We have an old server, a backup server and our current server. The backup and current server are identical hardware.

Our Reorder/Upgrade End Date: 2009-02-28

Microsoft? Exchange Server Standard 2007 English OPEN No Level
part# 312-03545 2007
# of licenses 1

Microsoft? Exchange Standard CAL 2007 English OPEN No Level Device CAL Device CAL
part#381-03096 2007
# of licenses 25

Microsoft? Outlook? 2007 English OPEN No Level 543-03828 2007
#licenses 10

Is there any reason we would need to pay for more licensing? Can't we just transfer the license from one computer to another?

We are currently running MS Server 2003 on the server. We downgraded since most users are using 2003 or earlier, and were told it would be cheaper to do it this way.

I am not familiar with all the ins and outs of licensing Server 2007, nor even my IT dept.'s server setup, but I will do my best to fill in any blanks if you have questions.

6 replies

by oh smeg

Most Likely Microsoft has a habit of Extortion but what you need to ask yourself is it worth the Risk of being hit by M$ for .25 of a Million for a first offense and more if it's not the first time to not Pay M$ Licensing Fees?

The company supplying the hardware isn't the problem here it is Microsoft who demand this action so in an attempt to save your or the company money they are following M$ Licensing Requirements. I would do exactly the same thing here as I don't deliberately expose my customers to prosecution. But you may feel differently about it. Personally I think that a few K here & there is much better than going bankrupt when M$ comes calling and wants the fees for you being a Pirate.

You could always use Open Source Servers and dump Microsoft unless there is a overriding need to use Windows.

but in relation to this [i]I am not familiar with all the ins and outs of licensing Server[/i]

Doesn't matter which version I don't think anyone is familiar enough with M$ Licensing Requirements except the Head of their Legal Department. God only knows that the staff at M$ certainly are not familiar with Licensing as you get a different story every time you ring them about Server CAL's and so on. If you speak to 2 different People at M$ on the same day within minutes of each other you are likely to get 2 different stories.

[i]They each have a computer running Exchange Server, either Outlook 2000 or 2003.[/i]

They are running Outlook on each Workstation not Exchange Server but you will need extra CAL's for the server so that all 20 workstations can log in simultaneously.

[i]Microsoft? Exchange Standard CAL 2007 English OPEN No Level Device CAL Device CAL
part#381-03096 2007
# of licenses 25[/i]

The company most likely supplied a 20 CAL Pack here because it is far cheaper than 1 X 10 CAL and 1 X 5 CAL Packs and leaves room for some growth without the need to buy more CAL's which are expensive in small numbers. You can pay more for 1 X 5 pack of CAL's than for the actual Server Application at times.

[i]Can't we just transfer the license from one computer to another?[/i]

Depends on the License Type you have if it is OEM no you [b]Can Not[/b] as the License is tied to Original Hardware by M$. Technically if you change a Optical Drive under the EULA End User License Agreement from Microsoft you could be asked to buy new Licenses of everything running on that particular computer. As Server Products are not Volume License the License is actually Tied to the Hardware it is loaded on.

If you want to know about Licensing try looking at M$'s Web Sites here but I would suggest a lot of Pain Killers be handy or a Shotgun so you can blow your head off as it's less painful that way.

MS Client Access Licensing otherwise known as CAL's

http://tinyurl.com/rlt6

The Main Site of the Official Lie Microsoft Software Licensing

http://tinyurl.com/5apr63

The XP End User License Agreement all 6 pages of it I might add

http://tinyurl.com/dnqgs

While there is more that is probably enough to let you know that the supplier here is erring on the side of caution as Lawyers tend to cost a lot more per hour then a pack of CAL's do and they are a one off expense where as an Hour with a Lawyer is just the start of a very big bill. If you want all the End User License Agreements so your Legal Team can look them over post back & I'll post the Web Sites where they are listed but you'll need a lot more and $250,000.00 to pay for the Legal Opinion that may not be correct and can only be considered as usable after being tested in Court.

So in answer to your Original Question are you being Ripped Off the answer is Probably but not by the Supplier of the stuff here but by Microsoft who have their hand buried deeply into all Business Pockets and have done since the introduction of Windows.

I hope that is of some assistance to help you understand of what is involved in Licensing and Microsoft.

Col

by moriarty67

That is helpful, actually. The server license is in fact OEM. Can't we use one of these extra CALs to provide the server license?

by oh smeg

A desktop to Access a Server, they are not actually a License to a OS at all but a Add On for a Server Application that allows more than the Basic 5 Workstations to be concurrently connected to the Server.

With Windows Server Products you pay a License Fee to M$ for the OS and then more money to allow desktops to access the server well more than 5 anyway as every Server Product comes with 5 CAL's built into the system. If you don't need concurrent connections then you may be able to use the existing CAL's that come in the OS but this limits the Server dramatically.

The actual Server OS's themselves are tied to the Servers [Hardware] as well as any CAL's purchased to allow computers access to the Server so you can not transfer a Server OS between computers when you replace a Server and it's even marginal to do major repairs on a Server as far as M$ Licensing is concerned. Replacing things like HDD's are not a problem but the moment you start to replace M'Board and CPU's things start to get difficult. The last repair I had to do was for a Insurance Company who balked at the Software costs and insisted that they didn't need to purchase any new Software for the Insurance Claim.

In that case they dealt with M$ and come to some sort of agreement and I was allowed to reuse the existing Software on the new server to replace the one destroyed when fire sprinklers went off but the Insurance Company Paid for the CAL's. Personally I would have preferred to pay for the OS and let M$ give me the CAL's as it would have been cheaper. But as all OEM product is tied to [b]Original Hardware[/b] if you reuse the Software "Windows" on replacement Hardware this is a Form of Piracy which M$ can quite rightly get upset about. And I wasn't about to believe the Guy from the Insurance Company on this they provided me with a M$ Document telling me that I could reuse the Software which I still have on File in case it is required latter.

Of course they can also authorize the reuse of software but they have to be contacted directly. When you buy a License you don't actually own anything well from M$ at least all the License allows or entitles you to do is use a M$ Product and even M$ reserve the right to terminate that agreement at their discretion.

You really need to look at the EULA provided by M$ for their products but in this case it is effectively the same for a Windows Server Product as the XP OEM License Agreement is with a change of XP to 2003 and the addition of Client Access Licenses. It is available to on download here under the heading of Microsoft Windows Server 2003 EULA

http://tinyurl.com/6zznsf

Then you also have to remember that there are a couple of Products being talked about here the First is Windows the next is Exchange which comes with Server maybe and is a separate product designed to run on Windows Server 64 in the case of Exchange 2007 and the 32 Bit version of 2003 in the earlier versions of Exchange. ISA most likely as well and whatever the particular version of Server comes with that you are purchasing. While you may think that you are getting something for nothing it doesn't work out that way as you need to pay to connect to the software included that M$ includes with the Install Disc's. So over all while M$ may be ripping us all off the supplier of the Server and the M$ Product isn't doing anything wrong here.

Of course if business where not prepared to fork over the money in the first place and use a Dedicated product that didn't come from M$ things would be very different but as M$ include these items in the package many people think that it is part of Server and just use it thinking that they are saving money. :D

Col

by notsochiguy

...I'd suggest speaking with one of the 'big boys', such as Insight or CDW. They have pretty helpful people when it comes to traversing the maze that is M$FT licensing.

Like the other reply said, going through M$FT licensing is headache inducing!

Best of luck!

by cookieorc

Yes, you are getting ripped off... But try not to feel special... It happens to all of us :)

This discussion is closed to new replies.