This text is intended to provide answers to basic questions that users of Microsoft products have. For more information on licensing, I recommend that you visit Microsoft's site: A Step Towards

1. Types of OS licenses Windowsand volume licensing programs

Microsoft has designed different types of operating system licenses and licensing programs to best meet the needs of a variety of customers:

- OEM versions intended for use by systems builders for installation on new PCs or upgrades / modifications to existing PCs (OEM - original equipment manufacturer or equipment manufacturer);

- Boxed versions or FPP(full packaged product or fully packaged product) for retail sale and subsequent consumer use;

- Version for licensing the installed operating system Windows XP Professional(Get Genuine Kit). The version is intended for installation on already used PCs with previously installed counterfeit, pirated, obtained in another illegal way, or an unlicensed copy of Windows XP Professional and available to buyers since November 2006.

- Corporate licenses Volume licensing programs for organizations that require at least 5 licenses. Attention! By volume licensing programs full OS versions are not supplied. In Volume Licensing programs, you can only purchase update version... Full versions are supplied in the 3 types of product presented above.

2. How to choose the right operating system license Windows

OSWindowsfor a new computer

There are only two ways to purchase a licensed Windows operating system for a new PC:

· OEM version preinstalled on a new computer and supplied with it;

· Retail boxed version.

Buying Windows as a pre-installed OEM version is the most economical solution.

If you already have a PC

The advantage of Microsoft's licensing policy is the choice that is presented to the user and allows you to find the optimal solution when installing the OS on an already used PC.

Option 1.PC modification.

To modify an already used PC, when there is no need to save system settings and data stored on the hard disk, you can contact your system builder to install OEM OS versions Windowson a PC. When using an OEM license, the system builder must fulfill the requirements of the builder's license agreement, including:

1) Mandatory installation of operating systems on the hard drive of a fully assembled computer using the OPK preinstallation kit (clause 6 of the system builder license). Those. when installing all old data and settings are deleted, if they were .

2) The system builder must affix a Certificate of Authenticity (COA) sticker to the case of the fully assembled computer (clause 7 of the system builder license)

3) A system builder who installs a separate software license and distributes hardware components is required to provide technical support on terms no worse than that provided by the system builder for fully assembled computers. The technical support telephone number must be prominently displayed in the help files of fully assembled computers and in the end-user documentation. (clause 8 of the system builder license)

In accordance with clause 1 of the system builder license, the following organizations can act as a system builder:

1) Organizations engaged in the manufacture of computer technology.

2) Organizations that deal with refurbishment, i.e. the purchase of used computers for their further repair, modification and bringing to a working condition suitable for resale or transfer to a new owner.

3) Organizations providing software pre-installation services.

Option 2. Legalization of an already used PC with an unlicensed OS

"Windows XP Professional / Vista Business. Version for licensing the installed operating system" (Get Genuine Kit) is the only Microsoft recommended solution for installation (legalization) on already used PCs with previously installed counterfeit, pirated, obtained in any other illegal way, or an unlicensed copy of Windows XP Professional / Vista Business.

The main benefits of the Get Genuine Kit for Windows XP Professional / Vista Business are:

· The ability to install on top of the operating system in use - during installation, the data is not completely deleted from the hard disk and, thus, this is the most convenient way for the user to transfer a PC to a licensed OS;

· Get Genuine Kit support is provided by Microsoft Support;

More product information can be found at the link:

http://www.microsoft.com/Oem/Russian/Licensing/GetGenuine/Default.mspx

Option 3. Boxed version of Windows OS

It can be used both for modification (upgrade) and for PC legalization. The boxed version provides the user with a wider set of rights to use the product compared to OEM versions. The license can be transferred from one computer to another, however, there should not be more copies installed than allowed by the terms of the license agreement. Recommended for home PC licensing users.

Option 4. OS update Windows

If you already have a licensed OS installed Windows and you want to upgrade to a new version of the product, you can purchase the upgrade version ( upgrade ), available through volume licensing programs and in the form of box versions.

3. Confirmation of the user's licensing rights and verification of the authenticity of the copy of the OS installed on the computer

3 a.Necessary and sufficient confirmation user license rights is a COA (Certificate of Authenticity) glued to the PC case or found on the product packaging in the case of a boxed version of the OS.

3b.Examination genuine copy of Windows installed on the PC

Types of licenses and signs sufficient for OS authentication Windows

View product	CertificateauthenticitySOA ( SOA– Certificate Of Authentity)		Supporting documentation and software product components
OEM-license	Certificate of Authenticity (COA) glued to the PC case Product Key)
Boxed product - FPP	Certificate of Authenticity (COA) pasted on the box and is a confirmation of the user's licensing rights. The certificate contains the product name and a 25-character product key ( Product Key)	To confirm the rights to use the product, users of boxed versions should keep components of the purchased product, as well as supporting payment documents. Components WindowsXP: Product packaging with SOA glued to the top; Information carrier (disc with a copy of the product and a hologram); Printed version of the license agreement (if included in the package); Components WindowsVista: Product packaging, certificate of authenticity sticker COA with a barcode attached to the back of the case for DVD; Information carrier - disk DVD with a hologram is inside the case.
Version for licensing the installed operating system Windows XP Professional / Vista Business (Get Genuine Kit)	Certificate of Authenticity (COA) glued to the PC case and is a confirmation of the user's licensing rights. The certificate contains the product name and a 25-digit product key ( Product Key)
Corporate license	Certificate of Authenticity (COA) glued to the PC case or pasted on the product packaging in case of using the boxed version.	A package of documents confirming the right to use corporate licenses. For Open Licenses: - Open License Agreement - License Certificate - ht tps: // eopen. m i crosoft. c o mas additional confirmation For programs Enterprise Agreement / Enterprise Agreement Subscription EA Agreement Registration agreement Confirmation of orders Payment confirmation : For programs C announcement Open Value / Open Value Subscription / OSL / MYO Acceptance letter Annual orders Confirmation of orders Payment confirmation

DMITRY BUTYANOV

How do I buy software from Microsoft? Features of purchasing and using OEM-versions

"Why is this necessary?" - many will answer with a crooked grin when it comes to the need to use licensed software. Now you can buy almost any software "on trays" very cheaply! And it's almost like a real one! What more could a sysadmin want?

But one has only to work for a while with such a "lotosh" product, and the system administrator begins to sigh, boring the ceiling with long glances and cursing in every way those who slipped this disk to him. It seems that you are doing everything right, and smart people on the forums give sensible advice, but the system lives according to its own laws, incomprehensible to people. And the numbers are chipping away such that even experienced specialists who have eaten more than one gigabyte shrug their shoulders and cannot recommend anything except reinstallation. So, maybe it's not about you, but about the software that you got almost for nothing and on which your company works from now on?

It's no secret that pirates, when making their ... hmm ... products, sometimes make significant changes to the distribution kit, throwing out, at least, driver libraries and other things of little importance to them. What torment the administrator will then experience, they do not care much. This will not affect their profits. In addition, the system is overgrown with "Resets" and other little appetizing software that makes this wretched cripple somehow work. As a result, we get a lot of problems, solving which we spend most of our time, instead of doing business.

In whose hands the system was before it got to the pirate's tray, the pirates themselves often do not know. What these unknown fighters of the pirate front did with this system, and why now a couple of hundred programs are placed on one DVD, they also cannot explain. How viable this whole structure is, life can show, in other words, they sell you your problems for your money. You need it?

And the problem will not be limited to incorrectly working software. The legislation of the Russian Federation in the field of copyright protection (combating piracy) has undergone significant changes over several years, and is now being built on the basis of international standards in this area. Under certain conditions, pirated software in a company office can also become a criminal offense. And what it can do with your profile and job opportunities, you can imagine yourself.

There is a perception that legal software is so expensive that companies simply have no choice - they go broke on the purchase. As a rule, this opinion is shared by people who do not know its value. Do not believe me - ask them. Get the answer "Very expensive". But nothing concrete.

Almost any company, even a small one, can now buy licensed software. By the way, you don't have to buy, but rent (very few people know about this). Became interesting? Read on.

There is an opinion that purchasing licensed software is not much different from buying, for example, a teapot - you gave the money, received the goods, use it as you want. Actually this is not true. By purchasing this or that software, you buy the right to use it. In other words, the manufacturer allows you to use their product, but on their own terms. These conditions are stipulated in the License Agreement, and must be followed. Required! Failure to comply with these requirements is piracy. So keep in mind - you can become a pirate out of ignorance.

What are the specifics of purchasing and using?

You can purchase Microsoft software in a variety of ways. In all cases, it is accompanied by a license agreement, either in electronic form or in hard copy. Please note that the terms of use of the software depend not only on the product itself, but also on the way it was purchased. That is, the same product purchased in different ways can be used in different ways.

I will list the types of licenses and how to purchase them:

• FPP License(Full Packaged Product - boxed). Boxed products are designed for individual clients and home offices. In some cases, the box version can be purchased for installation in company offices, but my advice to you is to consult with your reseller first.
• OEM License- intended for suppliers of computing equipment.
• Volume Licensing Licenses- designed for organizations of all sizes. Discounts for the volume of the order are already included in the cost of licenses.

There are special product licensing programs for ASP - Application Service Providers that provide access to Microsoft applications to third parties. For example: hosting SQL Server databases, hosting Exchange Server mail servers. SPLA - Service Provider License Agreement. In some cases, you can download the product over the Internet. Let's dwell on the three most popular options: boxes, OEM licenses, and volume licensing programs.

The box is nice, but a little expensive

The easiest (and most expensive) way to purchase a software product is by purchasing a box (FPP). Buying the boxed version, you receive in the kit: License Agreement (often only in electronic form), original media with anti-counterfeiting elements, User's Manual (often only in electronic form), packaging with a Certificate of Authenticity (COA). In order to verify the authenticity of the purchased software, you must keep the entire delivery set, plus documents confirming the purchase. Not all of the software can be bought in the form of a boxed version, some products are not distributed in this way. As a rule, these are products aimed at a corporate user, for example, Microsoft Office Pro Enterprise Edition cannot be bought in a box. The right to use the boxed product is unlimited, i.e. you can use it all your life. In addition, such a product can most often be installed on two PCs (the right to install on a laptop). You can read more about the rules for using the boxed version of the product in the documentation that comes with the delivery. I would like to dwell in more detail on the purchase methods that are most often used by corporate customers.

OEM - simple and angry

Compared to the box, you can purchase an OEM version of a software product much cheaper. Not all products are distributed as OEM versions - only Windows XP Home & Pro, Office 2003, Windows Server, Small Business Server. Formally, OEM versions of the product are intended for suppliers (assemblers) of computer equipment and should be distributed only along with their products. In other words, OEM versions of products are not intended to be distributed to end users separately from computer hardware. The term of the license in the OEM delivery is the same as the term of use of the computer. Please note: there are no update versions, no special academic pricing for educational institutions. What is the update version? This is a Windows XP Pro Upgrade disc, not for installation on a blank computer, but for upgrading another operating system, such as Windows XP Home Edition, to Windows XP Pro.

The OEM version in the initial delivery looks like a cardboard box, without beautiful printing. The box must be accompanied by the System Builder License Agreement. The number of disks inside the box (and hence the number of purchased products) can be one, three or thirty. Moreover, the server software always comes in packs of one piece, and thirty pieces of disks can only be for Windows XP. Each boxed product consists of hologram media, COA, End User License Agreement (electronic), printed user manual (rare). The product license confirmation consists of the entire package plus purchase documents.

How can an OEM version get into your company?

First, you can purchase a computer with a pre-installed version. Second, you can buy the OEM version as such, separate from your computer. First, about the first method. If you are buying a computer with an OEM version already installed, then take a look at the paragraph above! You can only confirm the authenticity of this version if you have the whole set in your hands: a disc with a hologram ("native"), an SOA sticker, documentation, if there was one - you should have all this together with your new computers. Require this from suppliers without fail. There is one exception to the rule. It applies to large computer manufacturers, the so-called Direct OEM. These are companies that have signed a direct contract with Microsoft and have documented their Direct OEM status. For large computer manufacturers (Direct OEM), there are three options:

• BIOS locked recovery procedures enable major computer manufacturers to create a CD-ROM with an operating system and device drivers for a factory restore. The CD is marked by the PC manufacturer, it is tied to a specific computer, which prevents copyright infringement.
• Large computer manufacturers may also place system recovery tools on the hard drive — usually on a separate partition on the hard drive.
• Sometimes the major computer manufacturers do not supply any system recovery media. However, they are required to provide software recovery tools as required by customers.

In addition to the CD-ROM, OEMs can also place an additional copy of Windows on the hard disk, which can be customized for a specific customer.

COA is an anti-counterfeiting feature that helps end users distinguish legal from illegal copies. This is a sticker that should be visibly stuck to the computer case. It cannot be distributed separately from the rest of the kit, and by itself is not a guarantee that the copy is legal.

• The COA has a security feature in the form of two holes, one in the shape of an ellipse and the other in the shape of the Windows Flying Windows logo. The outer layer of the laminate is absent within these openings, so the individual fibers of the paper structure are visible.
• The metallized thread embedded in the structure of the sticker has color transitions that become visible at an angle.
• The COA sticker contains microtext - a security feature in the form of text that is only readable under a magnifying glass.
• The new COA sticker does not have a laminated finish.

If you do not have a COA, then you are not legally licensed to use Microsoft software. The COA is not a software license - it is a visual aid to help you identify the Microsoft software you are using.

There are certificates of authenticity for applications (such as Microsoft Office). They are attached to the end-user documentation and are not stickers. They should be provided to you along with the documentation. You do not need to attach such a certificate to your computer.

And you can do that!

Now about the second option for purchasing OEM-versions, namely, buying them separately from computers. Surely, if you read this article carefully, you will be surprised. Indeed, I have already written that these versions are not intended for end users. But in the context of OEM proliferation, there is one great phrase: "except when the end user is himself a system builder." Immediately I will say that the very concept of "System Builder" at Microsoft is very extensible - it covers not only those who are directly involved in the assembly of computer equipment, but also persons (legal or physical) involved in installing software on previously purchased computers. Thus, you can quite safely purchase the OEM version of the product separately from your computer (you already have it) and complete the installation. One important note: in this case, you will not be considered an end user, but a system builder. Accordingly, you fall under the requirements of the System Builder License Agreement, which is pasted on the box. This agreement takes effect the moment the box is opened. Microsoft's OEM System Builder License is a "break-the-seal agreement" that comes into effect when you open the package — you open the package and thereby accept the terms of the license agreement. This is a simple procedure, devoid of bureaucracy. You do not need to sign any additional documents in order to be eligible to distribute OEM versions as a system builder (this method of accepting an agreement is designed to provide the widest possible sales channel, since it replaces the signing of documents). And from here two important points follow - you must buy an unopened box; in addition, you cannot return an opened box. In addition, you will have to install software products that you get from an open OEM package on end-user computers - further distribution of software from this box in any other way, except in the pre-installed form, is prohibited (exception: server software) ...

We carry out the activation procedure

All OEM versions of the product require an activation procedure. Starting with Microsoft Office XP and Microsoft Windows XP, a special technology is included in a number of Microsoft software products - Microsoft Product Activation. This technology is designed to protect both Microsoft and its customers from piracy by helping them make sure they get exactly what they paid for: genuine and licensed, high quality software. Product activation technology is designed primarily to counteract such violations as copying software by end users - when users install a software product from one genuine information carrier on more computers than is allowed by the terms of the license agreement. According to experts, about half of the damage caused by computer piracy to the economies of various countries of the world is caused by this type of violations.

Microsoft Product Activation technology is designed to exclude the possibility of using copies of products if the user does not have a license agreement with the copyright holder for the right to use this software product.

If the license agreement permits the installation and use of a software product only on one personal computer, installation of the same product on other personal computers leads to a violation of the terms of the license agreement, as well as a violation of the legislation of the Russian Federation on copyright protection. Activation technology allows you to technically limit the number of working copies of the product and exclude the installation of one licensed copy on an unlimited number of personal computers. Moreover, the number of installations and activations on the same personal computer is not limited.

The activation process begins after the software product is installed on the user's computer. In order to install and then activate the software product on a specific PC, the user must have:

• CD with software product distribution kit;
• product key.

The product key is a 25-character number divided into groups of 5 characters and has the following format: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, where X is one of the numbers from 0 to 9 or one of the letters of the Latin alphabet from A to Z ...

The product key is required to complete the installation of the software product on the user's computer; performing the activation of the installed software product on a specific PC. It is impossible to install the product on a computer without entering the key.

There are the following two types of keys: a one-time installation and activation key (type A) - used to install a boxed product on one PC (unless otherwise specified in the license agreement for a specific product and type of delivery). Keys of this type are intended for installation and activation of a product, the license for which allows its use by only one user (boxed product or OEM-version of the product).

Volume Licensing Key (Type B) is used to install a product purchased through a Volume Licensing program. Keys of this type are intended for purchasers of licenses for various volume licensing programs and can be used for multiple installations of the product (depending on the key capacity).

When using these keys, you do not need to complete the activation procedure from each computer. The product key, which is required to install the OEM version of the product, is indicated on the COA sticker.

The activation process itself is extremely simple. When you start a non-activated product, the Activation Wizard window appears on the screen. The activation itself can be performed either via the Internet or by telephone. If you choose activation via the Internet in the wizard, then after entering the key, everything goes through automatically. If you choose activation by phone, then you will need to select a country, after which you will see a phone number. Call this number, a robot will answer you. Switch the phone to tone mode, then follow the instructions of the robot. Pretty fast. If you need to perform a large number of OEM installations, then you can perform the automatic activation procedure.

When performing an upgrade, the system may ask you to reactivate it, this happens when the computer undergoes an upgrade, in which a large number of hardware components (usually more than three) are changed. But since the motherboard was not replaced, the product will allow itself to be activated. It's another matter if the motherboard has been replaced.

Let me remind you that according to the Terms of Use, maintaining the license is only possible if this replacement was associated with the elimination of a defect in the motherboard itself.

It will not be possible to activate the product via the Internet; you will have to call and explain the situation to the operator. Further - how it will turn out: either they will immediately reset the activation counter, or (more often) they may ask you to send a document confirming the fact of repair by mail or fax.

Software Assurance helps you save money

And one more thing that is important to know about. After purchasing OEM Server products and Windows Professional, and OEM Office Small Business 2003 or Office Professional 2003, you can purchase the great Software Assurance within 90 days of purchasing your product. You can buy it for a period of two or three years, with the possibility of further renewal at least indefinitely. During this period, you will receive free of charge all new versions of the OEM product for which you have acquired Software Assurance.

If you buy now the 2003 versions of servers, offices, etc., and buy Software Assurance for them, then very soon, in the winter, you will receive Vista, Office 2007 ... so to speak, somewhat cheaper than they cost. Software Assurance costs between 25% and 29% of the product license cost per year - you can calculate the savings yourself.

In addition to direct profit, this program will give you a wagon of bonuses, which makes it very difficult to list them within the framework of this article. I'll send you to the site http://www.microsoft.com/rus/licensing/volume/softwareassurance/advantagesoverview.mspx, and if you're interested, I'll write about Software Assurance separately in the next article.

The last paragraph - and not a word about the price! You are absolutely right, there will be no pricing information in this article. With a little patience, next time I'll do a cost comparison of legal software for a small to midsize organization. How much will it cost to purchase licensed software in the form of OEM, as well as for various volume licensing programs.

So I don’t say goodbye!

Application

How to legalize an operating system?

Let's assume that the decision to switch to licensed software has been made. But here one more pitfall awaits us. After all, the software is already worth it, it works! Pirate, stolen, some kind of no, but requiring rearrangement and everything that will follow from this. In other words, a temporary paralysis of the company and a fifteen-year-old sysadmin. What options are there? If we are talking about Windows XP Professional, then to legalize the operating system on such computers, you can purchase a special version of the operating system called Get Genuine Kit for Windows XP Professional. The Get Genuine Kit includes the same components - a Certificate of Authenticity (COA), a distribution kit with a product, an End User License Agreement (EULA). Like regular OEM versions, this operating system is tied to the PC it was first installed on and cannot be ported to another PC. The main differences between Get Genuine Kit and regular Windows XP Professional OEM licenses are described below:

• Get Genuine Kit for Windows XP Professional is designed for computers with a previously pirated, counterfeit, or unlicensed operating system and cannot be bundled with new computers.
• Get Genuine Kit technical support for Windows XP Professional is provided by Microsoft.
• A complete installation of the operating system (installation on a blank disk) is optional - a re-installation with data saving or a product key update is possible.

If we talk about other software products, then there is no such set for them. In addition, there is no trade-in either, and the cost of the old legal software will not be credited to you.

How to avoid becoming a pirate using OEM versions of products?

Or, in other words, what responsibilities and rights do you have? The most common violation of the OEM version is to exceed the allowed number of installations. Remember - one OEM version can only be installed on one computer. Once installed, it becomes an integral part of the computer itself. The lifespan of the OEM version is equal to the lifespan of the computer itself. You cannot transfer this OEM version to another computer. The operating system cannot be transferred to a new or different PC. The entire computer, however, can be transferred to a new user along with the licensing rights for the software installed on it, i.e. provided that all components of the OEM license are transferred to the new user: hologram media, certificate of authenticity, documentation. It is also recommended that you hand over the original invoices or receipts of purchase to the OEM by the original user. In this case, the original user should not keep any copies of the software product.

Will the OEM license remain if I need to upgrade or repair existing computers?

The license is tied to the computer, and we start upgrading it, i.e. change the original glands! Microsoft acted simply: one component is highlighted, which uniquely identifies the same source computer. I think you have already guessed which one. That's right - the motherboard. The general rule of thumb is that you can upgrade and replace almost anything except the motherboard while maintaining the original Windows license. If you are updating or replacing a motherboard and the replacement is not related to the elimination of the detected defect, then such a computer requires a new operating system license, because by replacing the motherboard, you actually created a "new" computer. If you are replacing a defective motherboard, then a new operating system license is not required. If you are transferring an upgraded computer to a new user - the software license, media, COA, and user manuals must all be transferred together to the new user.

Attention!

Changes to Microsoft Sales Policies

Since the release of the first article on the specifics of purchasing OEM licenses (No. 12 2006), Microsoft has changed the rules for selling OEM versions of software products. Since the end of 2006, OEM sales to end users have been allowed only if the end user assembles his own computer. If the end user already owns the assembled computer, then he cannot use the OEM version of the software product. Thus, for legalization purposes, you can use either boxed versions of products, or, for Windows XP Professional, purchase Get Genuine Kit.

Sales of OEM versions of Microsoft Office 2007 have also changed. When you ship this product as part of an assembled PC, you get a free preinstalled version of Office 2007 for 60 days. During this period, the product can be activated, which requires the purchase of a product key. Thus, you can become the owner of an OEM version of a software product, but you will not have a CD with a distribution kit. Instead of a disc, the component of the license is the key you purchased in the form of a DVD box. Media can be purchased for a fee. The new Microsoft Office 2007 sales program is called Office Ready.

The rules for selling Windows Vista Business Upgrade, the version of the operating system purchased through volume licensing programs, have changed. Windows Vista Upgrade is available with Windows XP Professional or Windows 2000 Professional. Purchasing a combination of Windows XP Home + Windows Vista Upgrade is only available if Windows Vista Business Upgrade is purchased as a boxed product.

The second part of the article.

Boxed versions are the easiest, but also the most expensive way to purchase Software from different manufacturers.
Boxed versions of products (FPP) are probably the most consistent with the idea of ​​how a software product should look, due to the fact that the buyer immediately receives all the necessary components for installing and using the product, namely, a license agreement, a certificate of authenticity, a distribution kit with a software product, usually a registration card and paper documentation.
Boxed versions can be purchased from computer retail stores, online, and from any software vendor. They are a box containing a license for one copy, an installation disc and instructions.
Examples of boxed supplies are: Kaspersky Internet Security 2010, Dr.Web Security Space Pro,
ESET NOD 32 Smart Security.
Pros of buying boxed versions:
- fast (obtaining licenses on the day of purchase);
- easy (no need to fill out any forms and wait for a response);
- available (you can just come and buy in any store that sells licensed software);
- profitable (if you need to purchase a license for only 1 computer).
Cons of buying a boxed version:
- expensive. Each box contains 1 license, distribution kit, instructions, possibly other materials. While when purchasing Corporate licenses, you pay for the distribution kit only 1 time, buying the required number of licenses. In addition, when purchasing a corporate license, you often receive additional bonuses, such as an administrator program for managing all antiviruses in the network.
- as a rule, there is no possibility of additional purchase of licenses for other computers of the organization during the validity period of the boxed license.

For example, you bought a box of antivirus on May 1 for 1 computer. Do you remember that on April 30 next year you need to renew your license. After 2 months, on July 1, you bought another 1 box of antivirus for another computer. Now you remember that on June 30 next year you need to buy another box. Then one more computer appeared in your company ...

OEM versions

The key difference between OEM-versions of products and “boxed” versions of software is that OEM-versions of products come pre-installed on the computer immediately upon purchase.
Computers preinstalled with OEM versions of Microsoft products are intended for both retail customers and for sale within an organization.
As a rule, purchasing computers with pre-installed OEM versions is the most economical option for purchasing Microsoft software for all types of customers.
OEM versions can ONLY be used on the computer on which they were ORIGINALLY installed. The product is bound to a computer, motherboard (as a rule). At the same time, "boxed" versions can be transferred to other computers without restriction.
Another difference is from a legal point of view. The OEM product end user license agreement is between the end user and the system builder; The boxed product license agreement is between the end user and the Software Provider. OEM is always a license for a computer builder.
Why are OEM licenses not intended to be purchased by the end user separately from the computer?
The customer, by obtaining an OEM license (Original Equipment Manufacturer) and opening it, thereby accepts all the conditions of the "License for a system builder".
In particular, it assumes that the assembler (in this case the client himself) will have to independently install the software on computers, sell them and independently support these computers.

Limitations of OEM licenses

The OEM version can only be used on the PC on which it was originally installed. This is the main limitation that distinguishes OEM versions from versions purchased under other licensing methods.
- If a customer purchases a new computer, they must purchase a new copy of the OEM product for it. You cannot transfer an OEM license from an old PC to this computer, even if the old computer is no longer in use.
- If a user wants to transfer or sell an old computer with an OEM version of the software installed on it to another user, then all parts of the OEM license are transferred along with the computer.

Corporate licenses

Volume licenses are for organizations that purchase one product for multiple computers. When purchasing products through volume licensing programs, the customer pays only for licensing rights and can use one licensed disk as a sample for installation.
This not only reduces acquisition costs, but also eliminates the complexities of deploying the product to a range of PCs in an organization. Volume Licensing offers significant cost savings, ease of deployment, purchasing flexibility, and payment options and other benefits such as Software Assurance.
Volume licensing offers tangible savings and increased investment value compared to purchasing individual user licenses.
Pros of purchasing volume licenses:
- Discount. You get a discount for purchasing multiple licenses. Whereas when buying boxes, the price of the product is usually fixed;
- Saving. You do not always need to purchase a licensed disc (media) with a software product distribution kit. Often software vendors allow you to download licenses for product installation for free when you purchase a volume license. If you need to buy a licensed media, you usually only need to buy 1 disc for an unlimited number of licenses; - Often vendor licensing programs allow you to "re-purchase" licenses during the term of the main license.
For example, if you purchased 5 product licenses for 100 rubles on January 1, and on July 1 decided to purchase another one, then its cost will be 100 (rubles) / 5 (persons) / 12 * 6 (months) = 10 rubles.
- flexibility of purchase. Boxes are a ready-made product with a fixed price. Licensing, however, allows more flexibility in obtaining special discounts from the software vendor.
Cons of purchasing volume licenses:
- Generally, purchasers of 5 or more licenses can participate in the volume licensing program.

Windows operating systems traditionally reach users in a variety of ways. Microsoft uses slightly different licensing methods for a copy of an operating system depending on the distribution channel.

At the same time, if the terms Retail and OEM are familiar to many IT specialists, then many admins sometimes forget about the intricacies of the Volume License. As a result, the question often arises which of the distributions to install.

So, below are the details of a particular delivery scheme.

Retail- the usual "box" version sold in stores. Now, in the age of digital distribution development, the concept of a “boxed” version is more of an image than a real box with a disc in a store. This version supports both a "clean" installation from scratch on a computer, as well as updating a previous version of the operating system to a purchased one. This version must be activated via Microsoft servers (Internet required).

Windows retail boxes

OEM- the version of Windows that comes with computers and servers. OEM copies of the operating system are not intended to be sold separately. As a consequence, this version only supports a "clean" installation from scratch, technical support for users of OEM-copies of Windows is provided not by Microsoft, but by a computer hardware supplier. This version also requires activation on Microsoft servers over the Internet.

Windows OEM box

Volume License- the corporate version, shipped only to large customers, in the role of which are various organizations. The most significant difference between this version and those described above is that the activation of VL copies of Windows is carried out through an internal KMS server ( Key Management Server) organization. This procedure is convenient for corporate users, since it does not require constant Internet access for all machines. However, there is also a downside. VL versions of Microsoft software products must maintain communication with the KMS server and periodically go through the reactivation procedure (up to 180 days). This is done to combat piracy.

What other Windows delivery schemes are there?

In addition to the three main options, there are more exotic ones.

GGK (Get Genuine Kit)- the so-called Microsoft licensing program. It can be purchased by a user who has decided to make his own pirated version of Windows licensed. Package includes Windows disc and Certificate of Authenticity label. The GGK distribution can be deployed over an installed pirated copy of the OS. Suitable for individuals and organizations that need to license no more than 5 computers.

Certificate of Authenticity sticker

GGWA (Get Genuine Windows Agreement)- a licensing program suitable for corporate clients who need to license more than 5 computers. Includes a license certificate and a set of documents. There is no Windows media, but it can be ordered separately. Or the distribution kit can be downloaded from the Microsoft website.

bundle / Not For Resale- the version is not for sale.

Making a request

Microsoft Product Licensing Considerations

Nstor

This article provides information on what types of licenses Microsoft offers, which one to choose, and how to properly license the OS, applications, and server products. Currently, a lot of information and materials are available from official sources, PUR (Product use rights) is regularly updated, all this is present on the Microsoft website.

But the main problem with all this documentation is the complexity of its perception by end users who are first faced with the topic of software licensing at their enterprise or firm. In this article we will try to understand the licensing jungle, according to Microsoft policy, in more or less understandable language, as much as possible.

Types of Microsoft licenses.

Below we will analyze the three main licensing options, consider their advantages and disadvantages, in order to further understand their difference from each other.

Boxed licenses (FPP).

As a rule, this is the most expensive way to buy licenses, it has a number of advantages, such as constant availability with dealers and distributors. These licenses are perpetual, this is the fastest way to purchase, but it also has a number of drawbacks: limited server products and updates, no Downgrade right (use of previous versions). Sold with VAT. The boxes include:

• The box itself, its presence is usually a confirmation of the legality of the product.
• Installation disk (distribution kit).
• End User License Agreement (EULA).
• Sticker (COA).
• This type of license is suitable for home users and small organizations with a PC fleet of less than 5 workstations.

Licenses (OEM).

Unlike boxed versions of OEM licenses are the cheapest, this is due to the following: they are supplied only with equipment by system builders, with the exception of Windows XP (GGK).

The lifespan of OEM versions is limited by the lifespan of the hardware on which the software was installed, in a word, a piece of hardware dies - the license dies, OEM versions are supported not by Microsoft, but by the system builder from whom the hardware was purchased.
The product line is even more limited here, there are no updates, the Downgrade eligibility applies only to desktop and server operating systems.

The package includes EULA (license agreement) and COA (sticker), may not contain an installation disc. The proof of legality is the SOA and the accounting documents of the purchase.

Corporate licenses (OLP).

The most common and most convenient way to purchase licenses for organizations with five or more workstations. There are several license options: permanent, temporary and purchased in installments in the form of annual payments, it is also possible to purchase (SA - a set of privileges and benefits from Microsoft).
Corporate licenses provide customers with the widest possible use of products, a flexible system of discounts, the ability to upgrade to new versions, a more in-depth downgrade right, here is the most complete line of products.

The license agreement is concluded directly with Microsoft and is assigned to a specific organization.
The package includes only registered licenses, the installation disc is purchased separately, the licenses themselves are not subject to VAT.

Now let's look at how Microsoft invites the end user to use its products in more detail by referring to documents called EULA (End User License Agreement) and PUR (Product Use Rights).

The EULA is included in all three options - FPP, OEM, and OLP and clearly defines all the actions that the user can take in relation to a specific product.
What specifically regulates the EULA: limiting the number of installed copies under a license, using previous versions of the product (downgrade), using a different language version (cross language), the right to transfer and transfer licenses, etc.

PUR governs volume licensing product use rights. There is simply no point in quoting the entire PUR, let's look at the general rules that you need to know when licensing.

Much depends on what kind of product it is, what category it belongs to, and through which licensing channel it was purchased. Let's take a closer look at such a thing as the right to use the previous version (downgrade). Here you need to clearly understand that basically this right applies to corporate licenses (OLP), this right also applies to OEMs, but, as mentioned above, only to operating systems, and not more than one step down. That is, instead of Windows Vista Business or Ultimate, the client can use Windows XP pro and, accordingly, instead of Windows XP pro, the client can use Windows 2000.
The same goes for server operating systems: instead of Windows Sever 2008, you can use Windows Server 2003 R2.
For volume licenses (OLP), downgrade downgrades are neither limited nor limited to product categories, i.e. if you are licensed for Windows Vista, you can use Windows 95, or you can install Office XP instead of Office 2007. The only thing to consider when using the downgrade right is that the version you intend to use must only be installed from the original installation disc, this is a strict Microsoft requirement. But, in turn, Microsoft does not guarantee the delivery of the distribution kit (installation disc) of old versions of the product, and if the distribution kit cannot be purchased or downloaded from the official website, you need to contact Microsoft directly. For boxed versions, the downgrade right does not apply.

Next, we will consider the right to use another language version (cross language), there is a clear rule here: if the cost of the licenses used is equal to or cheaper than that language version, then it can be used, if it is more expensive, then, accordingly, it is impossible. Example: if you purchased Office Russian, you can use English. The right does not apply to boxed and OEM versions. For boxed versions, you can purchase the Multilanguage Pack.

The right to transfer and transfer licenses.

As for the transfer of OEM licenses, they can only be transferred together with the hardware on which the product was originally installed. You cannot transfer to another device, even if the original one is out of order. Boxed versions can be transferred from one workstation to another, as well as, one-time transfer of the box to another person with the entire set of delivery.
After that, the user is obliged to remove the program and all its components from his PC.

With corporate licenses, everything is different: they can be transferred from one PC to another only for a long period of at least 90 days, and it is possible for a smaller one, but only in the event of a PC failure. It is prohibited to transfer an operating system license to another PC; corporate licenses can be transferred only if they are paid in full. You can transfer OS licenses only together with the PC on which it was first installed.
And a renegotiation of the contract with Microsoft is required.

Microsoft product classification.

All products manufactured by Microsoft are divided into five classes, each of which has its own licensing model.

So, what classes they are divided into:

1. Operating systems.
2. Applications.
3. Server products.
4. Development tools.
5. Hardware.

Let's take a closer look at the most basic of them and tell you about their licensing models.
For operating systems and development tools, the model is the same, for server products as many as five, and for Internet services there is only one model.

OS.

The basic operating system licensing model clearly regulates the golden rule: one license can only install one copy on one computer, more under this license, it cannot be installed anywhere. Only one user can use it at a time, with the exception of Remote Assistance, it is strictly forbidden to change the properties of the operating system, for example, to install Windows XP on a terminal server. It is also prohibited to supplement the OS with your own development tools that change its properties.

Desktop applications.

Now for the desktop licensing model, let's start with the most common application called Microsoft Office. For volume licensing, each computer on which Office is installed must be assigned a primary user. It is fixed by an order for the enterprise and this gives the right to install another copy on a laptop or on a virtual machine.

Using Microsoft Office in Terminal Mode.
Terminals also have a clear rule: Office and other applications are licensed per device only. Accordingly, in order to connect to the terminal server, each device, one way or another, accessing the server must be licensed and the license versions on the device must be at least the version installed on the terminal server. And one more rule: not all versions of offices can work in terminal mode, in order to raise the terminal mode, Office Professional Plus is needed, therefore, the versions on the device must be at least Office Professional Plus.

Development tools.

Development tools include the following applications: Visual Studio, MSDN, TechNet.

Unlike desktop applications, development tools are licensed per user, this user must be secured by an internal order of the enterprise, i.e. the order should clearly state that a particular employee has the right to use this application. The application can be installed on any number of PCs and an unlimited number of copies, but only the user who is assigned the license can use the product. And one more important rule: when licensing development tools, applications can only be used for design, development and testing. That is, it is strictly forbidden to install these tools on the client's computer, this rule is spelled out in the license agreement.

Example: Let's say a developer company has developed a program that requires SQL Server to run. If you take from the development tools SQL Server and install on a client computer to demonstrate this program, you are violating the license agreement.

An internal order for the company on securing the user is mandatory, otherwise it will be extremely difficult to prove to the inspection authorities that only a specific employee uses the applications, and one more important aspect that must always be remembered: you need to study the EULA and PUR in detail.

Server applications.

We will analyze this section in more detail, since the main part of the questions related to the problems of understanding the principles of licensing arises precisely during the implementation of server applications. As it may seem at first glance, the licensing scheme for server applications is quite simple, but for each product there are many nuances that the first time do not fit into the minds of even people with sufficient technical education and experience in the field of software licensing. We will try to present everything as accessible as possible.

OS servers.

The licensing model for server applications is as follows: all products are licensed according to the scheme - a license for a server and for a client connection (CAL) or, if necessary, an External Connector, we will talk about CAL and External Connector in more detail later, while we understand the main models of server licensing.

Service servers.

The most common service server is Exchange, the licensing model is similar to the server OS model, the license for the server itself and for client connections and, if necessary, External Connector. Servers per processor.

In the per-processor model, it would seem, everything is simple, until the concept of a virtual processor appeared. Previously, the physical processor itself was licensed and no questions arose, but when the concept of "virtual environment" appeared, a lot of nuances appeared that also needed to be analyzed. In principle, when licensing "per processor" additional licenses for client connections are not required with the exception of Data Center Edition, but more on that later.

Management servers.

Management servers are licensed as follows: this is a license for the management server itself and a license for the device that the server will manage. We will also talk about this model in detail, since there will also be a lot of interesting things.

Specialized servers.

For dedicated servers, the simplest licensing model applies and only requires a server license.

How server products are licensed and what are CALs.

So how are server products licensed? The topic is very complex, so we will try to explain it with a specific example.
Let's say that there is a company with a small park of PCs about 5 workstations on which licensed Windows Vista is installed (you must take into account the fact that the operating system license does not give any rights to connect to the server). The company has a need to purchase a server, they decided to install Windows Server Standard 2008 on this server, so the company will need to purchase a license for Windows Server Standard itself, and in order to gain access to this server, you need client licenses (CAL - Client Access License). Since the company has 5 PCs, 5 CALs are required.

Suppose that after a while the company needs to install another server, let's say Windows Server Enterprise 2008. In this case, the company will need to purchase a license only for Windows Server Enterprise 2008 itself, in this case it is not necessary to purchase additional client licenses, since all 5 workstations already have Windows Server CALs. Client licenses for Windows Server give the right to connect to any of the editions of both Standard and Enterprise, but you need to take into account another important fact that the CAL version must be at least the version of the server to which you are connecting. Example: with CALs to Windows Server CAL 2008, you can connect to Windows Server 2003, but not vice versa, the exception is that using Windows Server CAL 2003, you can connect to Windows Server 2003 R2. Now let's assume that Exchange Server 2007 is installed on one of the servers, so you will have to purchase a license for the Exchange Server itself and Exchange Server CAL for five PCs.

One more point: in the delivery of OEM and boxed versions, client licenses are included in the delivery set of 5 pieces for volume licenses, OLP are purchased separately.

There is another version of licenses - Terminal CAL - licenses are intended for terminal access. Let's try to figure it out with an example: let's say a company decided to expand its PC park and buy 5 more thin clients (terminals) to save money and space (more information about thin clients can be found on the Internet). In this case, the company will have to purchase 5 more Windows Server CALs and 5 Terminal CALs. the latter, give the right only to connect terminals.

There are two types of CALs, user CAL and device CAL. The most common device CAL, that is, the device itself is licensed to connect to the server, and multiple employees can connect from that device to the server. The second option “user license” is beneficial in cases where the number of employees who need access to the server is limited, say, 20 PCs and only two employees need access. In this case, it will be more profitable to purchase 2 client licenses, and these two employees will be able to connect to the server from any PC, but only these two employees who are assigned a user license. It is fixed by an order for the enterprise, otherwise, during the check, you will not prove in any way that only two employees are connected to the server.

Multiplexing.

The concept of multiplexing is extremely difficult to explain to a non-technical person, but let's try to explain it with a specific example. Let's imagine two servers connected to each other, let's call them C1 and C2. The company needs to install SQL Server and provide 10 employees with the database and, accordingly, the company wants to save on the purchase of client licenses. What they do: Install SQL Server on C2, and on C1 some free database that does not require any client licenses. As a result, it turns out that the main database lies on SQL Server, which is installed on C2, and employees actually contact C1, which in turn receives a request, takes data from C2 and sends it to the client, i.e. works as an intermediary and thus 10 employees connect to SQL Server for free.
This C1, an intermediary switch, is a multiplexer and this scheme is prohibited and, if checked, will entail criminal liability under Art. 146 of the Criminal Code of the Russian Federation. The rules clearly state that multiplexing and intermediate equipment does not affect either the licensing rules or the number of licenses.

To summarize, you need 10 SQL Server CALs to get 10 employees working with SQL Server.

External Connector.

Let's try to analyze what the External Connector is with a specific example.
In this case, the best example would be the need to create an online store. Imagine that a certain company decided to open an online store or some kind of information portal to provide goods or services to its company. In this case, you will have to provide access to external users to their resources and this requires all appropriate CALs for each connection. In this case, it is basically impossible to calculate exactly how many client licenses will be needed in a given period of time, since we do not know how many clients will simultaneously contact the online store, and it is simply not profitable to purchase many client licenses at once so that it is guaranteed that there will be enough. In this case, the External Connector will be needed - this is a license for unlimited connection to the server, that is, instead of a huge number of client licenses, you can purchase one External Connector. But there is one nuance: only external Users who are not employees of the company can connect via the External Connector, in any form. Those. in our case, only customers of the online store can connect.

Processor licensing.

Now let's take a look at processor licensing and look at the example of the most common server product licensed per processor - this is SQL Server.
What's the best way to license SQL Server? There is a standard option here: you can license the server itself and purchase the required number of client licenses for it, but you can also buy a processor license.
Again, let's imagine a physical server on which we are going to install SQL Server and connect five users to it, which we need for this, in addition to the Windows Server license and client licenses to it. Since we will be installing SQL on Windows Server, we will consider licensing the SQL Server itself. So, in a situation where we need to connect five users, we purchase a license for the SQL Server itself and, accordingly, five CALs for it SQL Server CAL. This scheme is beneficial when you need to connect a small number of users. Now suppose we need to connect 100 users to SQL Server, buying a license for the server itself and for 100 client connections is not economically viable, in this case it will be profitable to buy a processor license and then we will not need a license for SQL Server itself and no CALs are required because the processor license includes a license for the server itself and unlimited client connections, both internal and external.

That is, the physical processor itself, the piece of hardware itself, is licensed, regardless of the number of processor cores. The following server products are licensed under this scheme:

• Microsoft BizTalk Server 2006
• Microsoft Commerce Server 2007
• Microsoft ISA Server 2006
• Microsoft SQL Server 2005/2008
• Microsoft Visual Studio Team System 2008

With the exception of Windows Server 2008 Datacenter Edition, this product requires a processor license and separate CALs.