Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


Licensing Issue

By qballrail ·
This question is regarding my personal equipment which is NOT in any way used for business gain. I have an older model HP Pavilion tower that originally shipped with XP Home. I very much would like to use this as a file & print server. We own several HP notebook computers and I had taken one of the discs containing XP Pro installation and I was required to activate. The Microshaft rep informed me that this is actually a violation of SOX!

My questions are as follows:

1) Why is Microsoft requiring activation when I actually had Pro installed and running previously? Note that the previous installation was fresh, not an upgrade.

2) Is it actually considered software piracy to use a license from one computer on anoter if they are personal machines not used for business purposes?

3) How does SOX apply in this case? I'm certainly not making any money with this!

I cannot believe there is no longer anything considered "fair use" anymore when being used for personal endeavors. This is strictly used for my family because we each have a wireless notebook and it will save us from having to either purchase a print server or a new license, even having to go to the printer and plug in.

This is a real problem because I have intended use as outlined above. We own 3 notebook computers, all of the same make as the desktop and each running XP Pro.

Thanks in advance for your help

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Microsoft Licensing policy is

by zlitocook In reply to Licensing Issue

Percomputer not perinstallation. Not sure about the SOX remark tho.

Collapse -

M$ and the Consumer

by qballrail In reply to Microsoft Licensing polic ...

I understand it is per computer.

Microsoft does not provide leniency for consumers? I would need to purchase a license for Pro in order for this to work?

Collapse -

Microsoft has no

by zlitocook In reply to M$ and the Consumer

Leniency for any one except maby a nonfor profit. Yes you have to buy one copy per computer, There are multi seat licences that you can buy but they cost more.
You would be better off running some version of Linux for the rest of your computers. With the new GWA they check each computer and flag you if your computer is not legal.

Collapse -


by mjwx In reply to M$ and the Consumer

the consumer is a tap you get money out of.

I dont know about the legality of it in the US (NV I'm assuming thats Nevada), but here in AU (Australia) I can use a volume license copy as long as I can show evidence that I own a licence of each installed copy of windows, that means the MS COA (Certificate of Authenticity)

This is called fair use down under.

When I have to ring the Microshaft support Indian, I just tell them my motherboard has died. No questions asked.

Also the MSDN is quiet leniant as long as you follow the rules. I can deploy as many servers as I want for development purposes only, I can show these demo's to clients as long as the machine I am demonstrating on has a MS CAL in my organisation and a office license if I use office in the demo. I dont think I can demonstrate an MSDN licensed server on Linux though (no CAL). But I can deploy one hundred billion kazillion 2003 servers as long as I use them for development and not production.

(I know there are spelling mistakes, I dont have office installed.)

Collapse -

one hundred billion kazillion

by zlitocook In reply to To MS

Man I can only do half of that :)

Collapse -

Yes you are right sort of anyway

by HAL 9000 Moderator In reply to To MS

When I buy Volume License copies I just get a CD and a Product Key with a letter telling me how many computers I can install it on. I don't even get a COA for the number of Licenses that I buy as effectively they would all be the same Key.

Now if you had of used a Volume License copy here you wouldn't have needed to go through the Activation Process and this wouldn't be an issue.

As far as the SOX goes MS AU has outsourced all these telephone calls to Singapore so you most likely got hit with a Language barrier problem as SOX doesn't really apply in this case here.

Actually this will already be listed so you can not do anything about it but if you use Keg Finder and change the Product Key to a different one that you have there all you need say is that you've had a Hardware Crash and the OS needs reactivating after the repair because the M'Board and several other components have had to be changed.

You can use Magic Jelly Bean Key Finder to do this in a few seconds and then hit MS Activation Centre about 2.00 AM Local Time and they will just give you a replacement Activation Key so you can go on your merry way without a problem though strictly speaking this is Illegal you can get away with it by saying that you have to deliver this computer back at the beginning of the working day Tomorrow. :0

If you really sound desperate and very frayed around the edges you shouldn't have any problems.

But I didn't tell you that right? ?


Collapse -

Actually, MSDN Subscribers

by w2ktechman In reply to To MS

Can use 10 copies unless otherwise stated. I have never used all of mine for any app/OS.

Furthermore, I thought the restrictions were for testing only? Am I wrong here?

Collapse -

Sort of

by mjwx In reply to Actually, MSDN Subscriber ...

This after a long talk with MS licensing, a very long talk. There is a limit on production licenses. Development and testing licenses have no limit as long as they are not used in production. If they are shown to clients it must be done on a machine within your organisation dictated by the production licensing arrangement between your company and Microsoft (small business/enterprise/reseller).

Collapse -

i think so..

by heml0ck In reply to Actually, MSDN Subscriber ...

Our msdn subscription allows for ten installations in a non-production environment, for both testing and development.
When reading further into the usage agreement, I seem to recall it stating something along the lines of "... not generally accessible..." as part of the definition of "for development use."

edit for typo

Collapse -

I know that the first suggestion by MS Techs

by HAL 9000 Moderator In reply to Actually, MSDN Subscriber ...

Is to try another install with a different product. I've lost count of the number of times that I've been told to use My Volume License Stuff to install on a Problem computer. Yes it's always Windows but I've had my fair share of real problems as well and the Top tier Techs at MS always suggest that I load a Known Good OS before attempting to find out where any problems lay. There was one case a while ago when ever I loaded SP1 to XP Pro it deleted the MBR's on both HDD Fitted.

MS answer was to try a different version of XP to see if that helped unfortunately it didn't but it did at least prove that the problem was hardware related and not Windows Related. Before the techs at MS know that I have Volume License Stuff here their first question is always Do I have a OEM CD available with a Product Key? It doesn't matter if it's new or not just do I have one here to install from. Provided it isn't activated there is no problem as if it's only installed for testing purposes they are more than happy to have this happen as it solves problems in the code for them.

In the case of the SP1 install it was all traced back to a Samsung DVD Rom I had mistakenly taken it for granted that the Known Problems with the CD Burner would cause problems so I had disconnected it prior to installing the Service Pack. What I really should have done was leave the CD Burner installed and disconnected the DVD Drive. But it did list another piece of hardware with Known Issues.

I only wish it wasn't me who was the one who found this problem.


Related Discussions

Related Forums