 | | |
| | |
|
Spaces home  Emma Explains Microsoft ...PhotosProfileFriends |  Tools   |
|
|
August 22 Licensing Events at TVP - Reading - Sign Up Now
Hi All We will run some free Licensing events at the Microsoft office in Reading in October, there are two dates to choose from
Session 1 on the 2nd October is a beginner level broad licensing overview of Programmes and Products 2 October 2008, Reading: An Introduction and overview of Microsoft Licensing
Session 2 on the 21st October is the above plus the advanced virtualization licensing with me! 21 October 2008, Reading: Understanding Microsoft’s Server Product Licensing in a Virtual Environment
Choose wisely........... :-) Emma August 19 Knocking Down Barriers to Virtualisation – Changes to Server Application Licensing and Support for Hyper-V
What’s happening? We’re giving our customers greater flexibility by removing the need to wait 90 days to reassign a server application licence. This means you can move server applications between servers in a server farm* as often as you want without paying any extra licensing fees. We will also be offering extended support, including for third party virtualisation solutions, across 31 of our server application products. When? This comes into effect on September 1st 2008. Why? We’ve been listening to our customers and partners, who’ve been asking for this change. We are evolving our licensing rules in response to their feedback and to keep pace with rapid innovation in (and adoption of) virtualisation technologies. Waiving the 90 day reassignment rule means customers can set up far more dynamic, agile IT infrastructures that make the most of the flexibility that virtualisation offers. On top of this, our customers will now get the same level of support in a virtualised environment that they are used to in a non-virtualised environment. And of course, changing the rules in this way helps us to drive adoption of our virtualisation solutions.
Which products are covered? This change only applies to licences bought through a Volume Licensing agreement. However, customers don’t need to have Software Assurance to take advantage of the new rules. All Server Application Products licensed in the Server and CAL Mode All Enterprise editions of Products licensed in the Per Processor Mode Please note that Windows Server 2008 is not in the scope of these changes.
Download the Volume Licensing brief
* Microsoft’s definition of a server farm:A server farm consists of up to two data centres each physically located:• in a time zone that is within 4 hours of the local time zone of the other (Coordinated Universal Time (UTC) and not DST),and/or• within the European Union (EU) and/or European Free Trade Association (EFTA)Each data centre may be part of only one server farm. You can reassign a data centre from one server farm to another but not on a short term basis (ie not within 90 days of the last assignment).August 14 Virtualisation Licensing Changes in the Pipeline -Keep Posted
I attended the IT Pro Virtualisation event yesterday in London, many thanks to all of you who took the time out to attend, it was a great day filled with all that is technology, some very passionate people obviously doing jobs they love I had many licensing questions during the day, and for all of you still interested check out my 2 posts Server Virtualisation and Desktop Virtualisation We also had some heated discussions about the assigning and re-assigning of licenses - Hot Topic! for us all I am please to say that you will receive some fantastic news on the 19th as we have had a re-think on a few key areas regarding licensing in a virtual world- we really do listen!!! :-) Look out for my extended blog post on this next week................. August 10 SQL Server 2008 - Special Focus
SQL Server 2008 is around the corner!! The licensing of SQL Server 2008 will remain consistent with SQL Server 2005 with similar pricing, sighs of relief :-) Look out for the new Web SKU which has been added to SPLA for August and will become available in Volume Licensing around the October timeframe
The notable SKU related changes for SQL Server 2008 from SQL Server 2005 are:
Note for ISVs: A nominal charge has been introduced for ISV Royalty runtime servers The licensing model for SQL Server 2008 is also similar to that of 2005. The notable differences are:
For more details on SQL Server 2008 licensing visit: http://www.microsoft.com/sql/howtobuy/default.mspx August 04 Software Asset Management - The advantages of having a good SAM practice
I think that everyone acknowledges software is one of the most valuable assets an organisation can own, well lets hope :-) But, if you don't know what you have how can you make it work for you effectively and optimise your IT spend or resources? With a Software Asset Management (SAM) programme in place, you could gain better control of your software estate and benefit from:
We have designed a Software Asset Management (SAM) Programme to help you manage your software estate effectively. Through the Microsoft SAM programme, you can benefit from a free consultancy session with a qualified SAM partner, free SAM Basics training and work with a partner to review your software assets, validate your licenses and gain a Microsoft recognised certificate to validate your software licenses for 12 months. Read how one of our customers took advantage of the SAM Programme to assess and maintain their assets To find out more about how Software Asset Management can help you click here July 28 System Center Family - Migration and Transition Plans
I meet up with James and Andrew to talk a little about System center as its a very popular topic, below you will find the new licensing rules and the exceptions granted under the new license terms Please refer to my additional blog entry for more info System Center Configuration Manager 2007 The next version of Systems Management Server (SMS) 2003 R2 is System Center Configuration Manager 2007. Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. System Center Configuration Manager 2007 Client Management License (Client ML) The next version of Systems Management Server (SMS) Client CML version 2003 R2 is System Center Configuration Manager 2007 Client Management License (Client ML). Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. System Center Configuration Manager 2007 Enterprise Server Management License (Enterprise Server ML) Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. System Center Configuration Manager 2007 Standard Server Management License (Standard Server ML): The next version of Systems Management Server (SMS) Server CML version 2003 R2 is System Center Configuration Manager 2007 Standard Server Management License (Standard Server ML). Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. License Grant: One-time License Grant of System Center Configuration Manager 2007 to License Holders of Systems Management Server 2003:As a one-time exception in connection with the shift from per device to per operating system environment (“per OSE”) licensing, we are granting Select, Enterprise, Open License, Open Value, and Campus and School customers with active Software Assurance on Management Licenses for Systems Management Server 2003 as of November 1, 2007 the following System Center Configuration Manager 2007 Management Licenses at no additional charge:
System Center Configuration Manager 2007 with SQL Server 2005 Technology The next version of Systems Management Server (SMS) 2003 R2 w/SQL Tech 2005 is System Center Configuration Manager 2007 with SQL Server 2005 Technology. Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. System Center Data Protection Manager 2007 The next version of System Center Data Protection Manager 2006 is System Center Data Protection Manager 2007. Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change for System Center Data Protection Manager 2007 effective as of November 1, 2007 (please refer to October 2007 PUR for specific details):
System Center Data Protection Manager 2007 Enterprise Server Management License (Enterprise Server ML) Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change for System Center Data Protection Manager 2007 effective as of November 1, 2007 (please refer to October 2007 PUR for specific details):
System Center Data Protection Manager 2007 Standard Server Management License (Standard Server ML) The next version of System Center Data Protection Management License 2006 is System Center Data Protection Manager 2007 Standard Server Management License (Standard Server ML). Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. Summary of licensing model change for System Center Data Protection Manager 2007 effective as of November 1, 2007 (please refer to October 2007 PUR for specific details):
License Grant: One-time License Grant of System Center Data Protection Manager 2007 to License Holders of Data Protection Manager 2006: As a one-time exception in connection with the shift from per device to per operating system environment (“per OSE”) licensing, we are granting Select, Enterprise, Open License, Open Value, and Campus and School customers with active Software Assurance on Management Licenses for System Center Data Protection Manager 2006 as of November 1, 2007 the following System Center Data Protection Manager 2007 Management Licenses at no additional charge: One complementary Data Protection Manager 2007 Standard Server Management License for every 10 qualifying Data Protection Manager 2006 Data Protection Management Licenses (DPMLs) with active Software Assurance the customer holds as of November 1, 2007
System Center Essentials 2007 One-time License Grant of System Center Essentials 2007 to License Holders of Microsoft Operations Manager 2005 Workgroup Edition: As a one-time exception in connection with the discontinuation of Microsoft Operations Manager (MOM) 2005 Workgroup Edition, we are granting Select, Enterprise, Open License, Open Value, and Campus and School customers with active Software Assurance for MOM 2005 Workgroup Edition as of June 30, 2007, the following System Center Essentials (Essentials) 2007 licenses at no additional charge, other than the media costs (if applicable). For each qualifying MOM 2005 Workgroup Edition license with Software Assurance:
The right to use Essentials 2007 under this offering is in place of the right to use MOM 2005 Workgroup Edition. Note that the combination of Essentials licenses granted above is equivalent to the Essentials 2007 license you can purchase in VL programs. Customers who migrate but require more than 10 Server MLs or more than 50 Client MLs may acquire them individually under their agreement. Essentials licenses granted under this offer will include Software Assurance coverage. That coverage will expire when the corresponding MOM 2005 Workgroup Edition coverage expires. Upon expiration of that coverage, customers may renew their Software Assurance on the Essentials 2007 licenses. A customer’s use of Essentials 2007 under this offer will be subject to the terms and conditions of its license agreement and the Essentials 2007 product use rights. The right to use Essentials 2007 expires when the corresponding MOM 2005 Workgroup Edition license expires. Customers may not transfer the Essentials 2007 licenses granted under this offer separately from the corresponding MOM 2005 Workgroup Edition licenses. System Center Operations Manager 2007 Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. The licensing model for System Center Operations Manager 2007 will also change in November to be consistent, but existing customers will have the options outlined below. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. Starting November 1, customers acquiring licenses for System Center Operations Manager under enrollments or Open agreements entered into prior to November 1, 2007 may use that software under the revised license terms. They also have the alternative of using the software under the license terms for System Center Operations Manager 2007 contained in the July 2007 Product Use Rights. With either option, customers must apply all of the license terms from the same Product Use Rights (either July or October) to all use of System Center Operations Manager 2007. Use of System Center Operations Manager 2007 by customers acquiring licenses under enrollments or Open agreements entered into on or after November 1, 2007 is subject to the revised license terms contained in the October 2007 PUR. System Center Operations Manager 2007 with SQL Server 2005 Technology Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. The licensing model for System Center Operations Manager 2007 will also change in November to be consistent, but existing customers will have the options outlined below. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. Starting November 1, customers acquiring licenses for System Center Operations Manager under enrollments or Open agreements entered into prior to November 1, 2007 may use that software under the revised license terms. They also have the alternative of using the software under the license terms for System Center Operations Manager 2007 contained in the July 2007 Product Use Rights. With either option, customers must apply all of the license terms from the same Product Use Rights (either July or October) to all use of System Center Operations Manager 2007. Use of System Center Operations Manager 2007 by customers acquiring licenses under enrollments or Open agreements entered into on or after November 1, 2007 is subject to the revised license terms contained in the October 2007 PUR. System Center Operations Manager 2007 Standard Server Management License (Standard Server ML) Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. The licensing model for System Center Operations Manager 2007 will also change in November to be consistent, but existing customers will have the options outlined below. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. Starting November 1, customers acquiring licenses for System Center Operations Manager under enrollments or Open agreements entered into prior to November 1, 2007 may use that software under the revised license terms. They also have the alternative of using the software under the license terms for System Center Operations Manager 2007 contained in the July 2007 Product Use Rights. With either option, customers must apply all of the license terms from the same Product Use Rights (either July or October) to all use of System Center Operations Manager 2007. Use of System Center Operations Manager 2007 by customers acquiring licenses under enrollments or Open agreements entered into on or after November 1, 2007 is subject to the revised license terms contained in the October 2007 PUR. License Grant: One-time License Grant of System Center Operations Manager 2007 to License Holders of System Center Operations Manager 2007: As a one-time exception in connection with the shift from per device to per operating system environment (“per OSE”) licensing, we are granting Select, Enterprise, Open License, Open Value, and Campus and School customers with active Software Assurance on Management Licenses for System Center Operations Manager 2007 as of November 1, 2007 the following System Center Operations Manager 2007 Management Licenses at no additional charge: One complementary Operations Manager 2007 Standard Management License (Standard ML) for every 10 qualifying Operations Manager 2007 Standard Management Licenses with active Software Assurance the customer holds as of November 1, 2007.
System Center Operations Manager 2007 Enterprise Server Management License (Enterprise Server ML) Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. The licensing model for System Center Operations Manager 2007 will also change in November to be consistent, but existing customers will have the options outlined below. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. Starting November 1, customers acquiring licenses for System Center Operations Manager under enrollments or Open agreements entered into prior to November 1, 2007 may use that software under the revised license terms. They also have the alternative of using the software under the license terms for System Center Operations Manager 2007 contained in the July 2007 Product Use Rights. With either option, customers must apply all of the license terms from the same Product Use Rights (either July or October) to all use of System Center Operations Manager 2007. Use of System Center Operations Manager 2007 by customers acquiring licenses under enrollments or Open agreements entered into on or after November 1, 2007 is subject to the revised license terms contained in the October 2007 PUR. License Grant: One-time License Grant of System Center Operations Manager 2007 to License Holders of System Center Operations Manager 2007: As a one-time exception in connection with the shift from per device to per operating system environment (“per OSE”) licensing, we are granting Select, Enterprise, Open License, Open Value, and Campus and School customers with active Software Assurance on Management Licenses for System Center Operations Manager 2007 as of November 1, 2007 the following System Center Operations Manager 2007 Management Licenses at no additional charge: One complementary Operations Manager 2007 Enterprise Management License (Enterprise ML) for every 10 qualifying Operations Manager 2007 Enterprise Management Licenses with active Software Assurance the customer holds as of November 1, 2007.
Customers’ right to use the software is evidenced by this product condition note and evidence of their corresponding qualifying licenses. A customer’s use of the software under this offer will be subject to the terms and conditions of its license agreement and the product use rights for the software. The right to use the software under the complimentary licenses expires when the right to use software under the qualifying licenses expires. Customers may not transfer the licenses granted under this offer separately from the corresponding qualifying licenses. System Center Operations Manager 2007 Client Management License (Client ML) Changes in the Licensing Model: The October 2007 Product Use Rights (PUR) documents a change in the Management Server licensing model. This change takes effect November 1, 2007 with the introduction of System Center Configuration Manager 2007 and System Center Data Protection Manager 2007. The licensing model for System Center Operations Manager 2007 will also change in November to be consistent, but existing customers will have the options outlined below. Summary of licensing model change taking effect as of November 1, 2007 (please refer to October 2007 PUR for specific details):
To support this, we have introduced two new management license types: a per user option and a per operating system environment (OSE) option. The per user option applies to client management licenses. The per OSE option applies to both client and server management licenses. We will no longer offer a per device option, other than for client management licenses purchased via the Core CAL and Enterprise CAL Suites. Also, for servers, the System Center Server Management Suite Enterprise permits management of any number of OSEs running on the device to which it is assigned, analogous to a per device option. Starting November 1, customers acquiring licenses for System Center Operations Manager under enrollments or Open agreements entered into prior to November 1, 2007 may use that software under the revised license terms. They also have the alternative of using the software under the license terms for System Center Operations Manager 2007 contained in the July 2007 Product Use Rights. With either option, customers must apply all of the license terms from the same Product Use Rights (either July or October) to all use of System Center Operations Manager 2007. Use of System Center Operations Manager 2007 by customers acquiring licenses under enrollments or Open agreements entered into on or after November 1, 2007 is subject to the revised license terms contained in the October 2007 PUR. System Center Server Management Suite Enterprise System Center Server Management Suite Enterprise is version-less and product use rights are determined by the status of System Center Server Management Suite Enterprise Software Assurance coverage. If coverage lapses, access rights under perpetual licenses are determined based on the product use rights in effect prior to the lapse in coverage. System Center Server Management Suite Standard The next version of System Center Standard Server Management License 2006 is System Center Server Management Suite Standard. System Center Server Management Suite Standard is version-less and product use rights are determined by the status of System Center Server Management Suite Standard Software Assurance coverage. If coverage lapses, access rights under perpetual licenses are determined based on the product use rights in effect prior to the lapse in coverage. License Grant: One-time License Grant of System Center Server Management Suite Standard to License Holders of System Center Server Management License: As a one-time exception in connection with the shift from per device to per operating system environment (“per OSE”) licensing, we are granting Select, Enterprise, Open License, Open Value, and Campus and School customers with active Software Assurance on Management Licenses for System Center Server Management License as of November 1, 2007 the following System Center Server Management Suite Standard Management Licenses at no additional charge, other than the media costs (if applicable): One complementary Server Management Suite Standard ML for every 10 qualifying Server Management Licenses with active Software Assurance the customer holds as of November 1, 2007
Note on System Center Essentials and Product keys Product Key Requirements The technical limits of 30 Windows-based server OSEs and 500 Windows-based PC OSEs are effective across all distribution channels. However, whether product keys must be input to scale up to those limits is not consistent across distribution channels. Both the Essentials 2007 Server and each ML license pack require the input of product keys for purchases made through the Retail and OEM distribution channels to unlock the number of Windows-based PC and server OSEs which can be managed. It is not necessary to input the product keys for ML license packs purchased to manage other Windows-based OSEs and non-Windows-based OSEs. At this time, product keys are not required for purchases made through VL programs. This means that customers must decide carefully between Retail/OEM and VL channels before making their initial Essentials 2007 purchase because any subsequent purchases of ML packs will need to be made through the same channel due to the differences in product key input requirements. Customers who initially acquire Essentials 2007 through the OEM channel may purchase subsequent ML license packs with product keys through the Retail channel to scale up. For Retail and OEM purchases, a product key must be input during the Essentials 2007 setup as part of the product registration information section to unlock the management server software as well as ability to manage Windows-based PC and server OSEs based on the number of Client MLs and Server MLs included in the base configuration. Essentials 2007 sold through the Retail channel comes with the MLs to manage 10 server OSEs and 50 non-server OSEs. Essentials 2007 sold through the OEM channel may have different base configurations. When additional ML license packs are acquired, the associated product key can be entered through the Essentials 2007 Licensing Wizard to unlock the number of Windows-based PC and server OSEs that can be managed based on the MLs that you purchased. Only one product key is associated with each ML license pack, regardless of the number of MLs included in that license pack. The product key is delivered as part of the packaging in the Retail channel, and on the Certificate of Authenticity in the OEM channel. July 17 Erratic PostsHi All
I know it has very quiet from me recently
I am in the USA at the moment writing the new Licensing MCP exams
I will try to answer all comments and Qs during this time
The posts will be a little erratic
Emma! July 10 Windows Remote Desktop Licenses - RDLs - What are they? Do I need them?
Many computer manufacturers (OEMs) have introduced a new desktop environment using blade hardware technology and Microsoft® Windows® XP Professional. This technology solution enables end users to access Windows XP Professional running on these blade PCs that are stacked securely in a data center rather than sitting under or on an end user’s desk. In this solution, end users connect to the blade PC using a small connection port and one of many different types of access devices, ranging from a desktop PC to a thin client. Businesses can employ a variety of devices for access: desktop PCs or thin client devices running an embedded operating system. RDP (or a similar technology) is used to access Windows XP Professional running on the PC. Unlike server models which provide simultaneous access of multiple users to a single piece of server hardware, each blade PC can have only one user accessing it at a time.
Licensing Desktop Operating Systems for blade Infrastructures The Microsoft® Remote Desktop License for Microsoft® Windows® XP Professional has been added to the Volume License programs as of November 1, 2004. RDLs are procured in the form of a license; there is no software provided with them. The RDL permits a remote device (laptop, PDA, cell phone) to access any other device that is running Windows XP Professional without the need for the remote device to be licensed separately for Windows XP Professional. Please Note: An RDL does not provide you the right to access any desktop application running on the blade PC. It permits access to the Windows XP Professional software experience and to files and other data on the PC. Customers must refer to the use rights for any other application that resides on the blade PC to determine if this kind of access is permitted under the use rights for that application. The accessing devices use RDP or similar technologies to access the Windows XP Professional software. Like some server Client Access Licenses (CALs), the customer has the flexibility to choose to license the accessing devices in their infrastructure in one of two ways —by device or by user:
Each business can decide whether they want user-based or device-based licensing of RDLs, or a mix of the two. This will depend on what makes the most sense economically, technically, and operationally for each customer. Did you know: When a customer acquires blade PCs from their OEM partners, Microsoft Windows XP Professional Blade PC Edition is preinstalled. Each preinstalled license of Windows XP Professional Blade PC Edition includes one RDL license. Only blade PCs acquired from OEMs will include one RDL license with Windows XP Professional Blade PC Edition. Additional RDLs will be available from OEMs and through all volume license programs. Basic Licensing Model
The following cases compare the RDL model to the licensing model that existed prior to November 1, 2004.
Case 1: Pre-RDL solution Case 2: New solution (device-based)
In both cases, the customer needs a total of 25 licenses. However, with the pre-RDL solution, the customer would need to acquire a total of 25 licenses (all Windows XP Professional). In the new RDL solution, the customer only needs to acquire 15 licenses (10 Windows XP Professional Blade PC Edition and 5 RDLs). Because 10 RDLs are included with each license of Windows XP Professional Blade PC Edition preinstalled on the blade PCs, they only need to acquire an additional five RDLs for Windows XP Professional. In Case 2, we assumed the customer has decided on a device-based solution. The following section explores the options a customer has for choosing the environment (device-based, user-based, or mixed) that best suits their business needs.
LICENSING OPTION SCENARIOS Scenario 1: Mixing user-based and device-based RDLs for Windows XP Professional Assume we have the same scenario as in Case 2 above, but with 15 users instead of 15 accessing devices. Nine of these fifteen users are shift workers in three shifts of three and never overlap. Each shift has three devices available, one for each user on the shift. The other six users are sales staff each of whom has 3 devices they use to access a blade PC. In this scenario, the customer would elect three device-based RDLs for the shift workers and six user-based RDLs for the sales staff. With a mixed RDL approach, the customer needs to have nine RDLs. Since they are licensed for to up to 10 RDLs that were included with Windows XP Professional installed on the blade PCs, there is no need for additional license purchases. In fact, they have one RDL for Windows XP Professional that is unused and available for future growth.
Two months from now, the customer adds two more workers per shift and two more thin client devices to support the new workers on each shift. Also, assume the customer hires three more sales staff each requiring the use of three devices. The table below shows the additional licenses they will need to acquire from their OEM or volume licensing reseller.
Scenario 2: Using desktops already licensed for Windows XP Professional Let’s go back to our Case 2 example above. Assume 10 of the 15 accessing devices are thin clients running an embedded operating system, and five are desktop PCs running Windows XP Professional. How many RDLs for Windows XP Professional do you need? Per Volume Licensing Product Use Rights, below, devices already licensed with Windows XP Professional do not need RDLs to access other workstations running Windows XP Professional. You will only need 10 RDLs for the ten thin clients. The 5 accessing devices (in this case desktop PCs) which are already licensed for Windows XP Professional do not need RDLs. And, in this case, the 10 RDLs for Windows XP Professional were included with your Windows XP Professional Blade PC desktop operating system license from the OEM, so you do not need to acquire additional RDLs.
When do I need to acquire a Remote Desktop License (RDL) for Windows XP Professional? If you need remote access to PCs running Windows XP Professional, you will need an RDL unless you meet the criteria in the Windows XP Professional EULA or Volume Licensing Product Use Rights for Windows XP Professional: you are the primary user of the PC, or the device you are using to access the PC is already licensed for Windows XP Professional. If you set up your blade PC infrastructure so that each blade has a single, primary user[1], then the primary user will not require an RDL to access their blade PC. They will need an RDL if they access another person’s blade PC [1] The primary user is the individual who uses the computer most of the time it is in use.
From the PUR Remote Desktop. The single primary user of the licensed device may access a session from any other device using Remote Desktop or similar technologies. A “session” means the experience of interacting with the software, directly or indirectly, through any combination of input, output and display peripherals. Other users may access a session from any device, using these technologies, if:
For other common FAQs see the RDL Brief here July 02 Microsoft Select Plus - What's it all about?
I have been hinting for a few months that we had an announcement around the corner, so here it is, we are introducing a new program, Select Plus I know, I know, another new program, but does'nt Microsoft want to simply and reduce licensing contracts? well the answer is YES we do, but we cannot get to nirvana without a little bit of "change" so bear with us, these changes are for the long term vision...!! So what is Select Plus about, what's the difference between Select and Select Plus and Enterprise Agreement and Select Plus, what's the advantage to me as a customer? Hopefully I will answer all or at least most of the above Qs in this blog What is Select Plus? Select Plus is the new program launching in the UK on October 1st 2008, this program is NOT an immediate replacement for Select, its a new offering designed for customers in the 250PC space who want a
Select Plus, What is the SAME as Select?
Select Plus, What is DIFFERENT to Select?
10 Reasons for you to buy through Select Plus •Simple, one-page affiliate registration makes participation fast and simple. •A single, enterprise-wide contract offers the same pricing level for all business units. •The perpetual agreement term keeps renewals at the IT budget level rather than the boardroom level, with flexibility to buy as needed. •Centralized and decentralized purchasing aligns with how the business works. •Immediate price-level adjustments based on actual purchase volume across the organization helps ensure the right price. •Provides a clear view of the entire license portfolio to support asset management and reporting. •Software Assurance is available but not required. Get access to full value of benefits like training vouchers and deployment services. •Manage migration from expiring agreements at any pace. •Sign an EA and consolidate other agreements under a Select Plus for better manageability and a better overall price level for volume purchasing. •Stronger support from Large Account Resellers (LARs) for purchasing guidance. July 01 Answering Comments and emails on the Blog
Hi All Just a note on comments and emails Alot of you have submitted Qs that I am unable to reply to you on due to email restrictions I want to reply to all emails, so please put your email address into the BODY of the message and I will reply to you all Cheers June 25 Special Feature:Office Communication Server 2007 - Which licenses are right for me?
OCS 2007 is licensed in per Server and CALs mode You need a Server license for each running instance of OCS on the server and CALs for every User and Device accessing the services of the OCS Server
The following usage scenarios for OCS will require that CAL licenses be in place for each user or device:
The following usage scenarios for OCS will NOT require that CAL licenses be in place for each user or device:
To compliment the Office Communication Server and CALs we also have the Public IM Connectivity, licensed via the Online Services Model, its a subscription based offering
So what does PIC mean? Basically PIC allows you and your users to interact with other IM servers, so AOL, Yahoo, MSN etc, and see presence information, as below
Really good doc on here June 22 Microsoft Open License Transfer - What you need to know!!
License transfer is really a world of legality, each agreement may have different terms and conditions, also different versions of the agreements may have different T&Cs, bottom line, always check your own paperwork, the "transfer" section is always in there! I want to cover off the "common" issues when transferring licenses purchased through Volume Licensing Agreements Remember that OEM software is tied to the original hardware it was purchased with and cannot be transferred, the whole unit <hardware and software> may go together, no software separation is permitted The first mistake made is the difference between re-assignment and transfer, alot of people get these 2 mixed up **Reassignment is removing the software license off a device you own and installing or assigning onto a new or alternative device you or your legal affiliate owns, reassignment rules are discussed at the bottom of this blog Transfer is to permanently remove software licenses off a device you own and give ownership of these licenses to an affiliate or an unaffiliated 3rd party, under specific criteria, with the understanding that you do not and will not have the licenses back Lets look at the transfer rules by Agreement Open Agreement Version 6.5 and Prior Open transfer is "all or nothing", under a single authorisation you may have numerous licenses, you must transfer all those licenses at the same time, no license splitting is permitted in Open transfer How to transfer licenses to affiliates or third parties. You may transfer the licenses and Software Assurance coverage identified in the online records to a single individual or legal entity only if:
When transfers are not permitted. You may not transfer
Key notes on new changes to Transfer on Open Agreements 6.6 onwards Right to transfer. Customer may transfer the Licenses identified in the Online Records to (if Customer is an eOpen Customer) or on the paper License confirmation (if Customer is a pOpen Customer)
To do so, (1) such transfer must include all Licenses issued in connection with the initial purchase order and any subsequent purchase order placed under the Authorization Number, and the right to acquire additional Licenses in the future under the Authorization Number; and (2) Customer must complete and send to Microsoft a transfer notice in a form which can be obtained from http://microsoft.com/licensing/contracts within 30 days of the date of transfer. All other transfers require Microsoft’s prior written consent. Guidance on what types of transfers are permissible can be found at http://microsoft.com/licensing/contracts. No License transfer will be valid unless Customer provides to the transferee, and the transferee accepts in writing, the applicable Product use rights, use restrictions, limitations of liability, and the transfer restrictions described in this section. Any transfer not made in compliance with this section will be void. The resale of Licenses is expressly prohibited. Certain transfers not permitted. Customer may not transfer any of the following:
Did you know: You will need to put on the new open transfer request form why you want to transfer, choice of Divesture, Merger, Acquisition and Other, if Other you need to state your business reason Did you know: You must transfer within region, for open, “Defined Region” means the geographical region as defined on the regional listing located at http://www.microsoft.com/licensing/programs/open/openregional.mspx where the Originating Customer is organized and operated Always work with your channel partner on License transfer requests, these guys have the skills to cover this off for you, they also have the access to the internal Microsoft tools to get these transfers "signed and sealed"
**Reassignment: Internal reassignment of licenses. You may reassign licenses for products other than desktop operating system. However, you may not reassign: (i) licenses on a short-term basis (90 days or less), or (ii) except as provided in Subsection (d) below, Software Assurance coverage or other upgrade rights separately from the underlying license. You may not reassign desktop operating system licenses from the device on which the software is first installed. Internal reassignment of software Assurance coverage for the desktop operating system. You may reassign Software Assurance coverage ordered for an underlying desktop operating system product installed on one computer to a replacement computer as long as:
You may not otherwise separate Software Assurance coverage or any related upgrade right from the underlying license for which it is ordered. June 17 MOSS - Microsoft Office SharePoint Server - Common Licensing Scenarios
When I meet people and tell them I do a licensing job they normally reply with "licensing material doesn't cover real life", I think what they mean is the PUR or the Briefs don't actually represent the mixed bag of scenarios that the technology associated with these products permits, and "plugging in" the licensing can prove to be a minefield for many people I have decided to cover off some "real life" scenarios or pain points :-) if there are more specific scenarios required, send to me, and I will post I will start with the one of the most popular products of the moment - MOSS 2007 Intranet Portal for your internal employees, contractors, anyone in your internal network or on your site working for you Not for NON-employees or anyone you provide a service Overview 1000 Users access the MOSS portal, 50 additional Users access the MOSS Portal acting as Content Authors, 10 additional Users access MOSS Portal for development purposes Only the 1000 Users who have access to the Ent Functionality will also require the MOSS Ent CAL on top of there MOSS Std CAL All users should be covered with CALs, the developers will also require VS or MSDN licenses
Scenario 2 - Intranet and Extranet, so a mixed environment of your internal employees and some business partners who work with you on collaboration/projects etc I know it looks a little harrowing, but its not that difficult, let me cover this off Overview Intranet usage is as above, no change Extranet is covered off with MOSS For Internet Sites <MOSS FIS> licenses, buy a MOSS FIS license, assign it to the server, this permits any and all NON-Employees access to this server, it also provides both Standard AND Enterprise MOSS Functionality Dont forget that these external Users will also need Windows CALs, as an alternative you can buy the Windows Server External Connector, it can only be used, like MOSS FIS to cover external NON-employees, and not for any type of service or hosted environment
Once again MOSS FIS and Windows External Connectors <EC> will cover access to the MOSS/Win servers by unlimited non-employees, business partners, alumni etc, basically anyone that you don't employ, who isn't affiliated to you or to whom you provide a service Overview MOSS FIS for each server, note the Dev Server will be covered with MSDN or VS Windows EC will ONLY be required if the users are NOT anonymous or individually identified by your servers, pure anonymous Internet users = NO Win CALs or EC, only the Windows Server and MOSS FIS licenses need to be purchased in this example If you set up AD or login/password authentication then Win EC would be required also
* Did you know: SQL per Processor licenses will cover all Internal AND External access to the SQL Server * Did you know: The choice between MOSS FIS and MOSS CALs for EXTERNAL users is a financial one, usually 450+ External Users = MOSS FIS
Some pointers:
June 13 Microsoft Desktop Optimization Pack and Kidaro/MEDV Licensing
I am from the school of a picture speaks a 1000 words, and in the case of licensing, sometimes a pic puts it into perspective! MDOP in a nutshell below, |
Print
