GraphiX wrote:if you knew who i was then you'd not need ask that

don't quit your day job

Volume Activation 2.0
Volume Activation 2.0 is a new requirement in Windows Vista and Windows Server “Longhorn†requiring activation of each Windows Vista or Windows Server “Longhorn†license acquired under a volume licensing agreement. When designing and building the new volume activation technologies, Microsoft focused on two goals: first, to close significant piracy loopholes (volume license keys represent the majority of keys involved in Windows piracy); and second, to improve the volume customer experience. Volume Activation 2.0 is designed to provide increased protection and management of customer volume license keys in managed and non-managed environments as well as provide flexible deployment options for customers. The process is transparent for end users, and the Volume Activation 2.0 solution works in a variety of customer environments. It enables the following:
• Enhanced volume key protection
– Centralized management and protection of volume license keys
– Lower probability of keys leaking
– Less risk of re-keying entire organization
• Flexible deployment options
– Comprehensive range of product activation options
– Robust and scalable solution
– Centralized and controllable infrastructure
– No end-user involvement needed
• Peace of mind
– Better security checking for genuine software
– Clear road map to future software asset management tools
– Transparent Microsoft privacy policy on activations
Volume Activation 2.0 provides a simple and security-enhanced activation experience for enterprise customers, while addressing issues associated with volume licensing in previous versions of Windows and reducing risks of leakage to both Microsoft and its customers. Volume Activation 2.0 will provide system administrators with the ability to centrally manage and protect product keys, as well as several flexible deployment options to activate the computers in their environment no matter what the size. forwarding the future, it will provide the basis for an easy-to-use, comprehensive, integrated activation process that will support Microsoft and third-party applications. It is also the starting point for a strong software asset management system that will deliver immediate and future benefits.
Volume Activation 2.0 Options
This section describes each activation method and provides information to help organizations decide which method best suits their systems’ requirements. There are two types of keys that can be used with Volume Activation 2.0, and three ways to activate client PCs:
1. Multiple Activation Key (MAK)
a. MAK Proxy Activation
b. MAK Independent Activation
2. Key Management Service (KMS) Key
Multiple Activation Key
All customers who have valid license agreements with Microsoft are eligible to receive a MAK (pronounced ‘mack’) key with a limited number of activations associated to it. Each MAK can activate a specific number of machines and behaves much like a traditional retail activation key, requiring activation with Microsoft but allowing multiple activations. They may be used to activate any volume edition of Windows Vista.
The MAK may be obtained from MVLS or eOpen (depending on the user’s volume licensing program). As each machine contacts a Microsoft activation server, the allowed activation count is decremented. Activation may be performed over the Internet or by telephone. Users may check the number of remaining activations online and request additional activations as needed.
Advantages of MAK activation include the ability to automate key assignment and activation, availability of online reports regarding key utilization via Microsoft Operations Manager (MOM) or special deployment tools provided, and no requirement to periodically renew activation. Additional requirements include the need to request additional activations when the number of activations passes the preset limit, the need to manage the installation of MAK keys (automated by Business Desktop Deployment (BDD) 2007), and the potential need to manually activate systems using a telephone when no Internet connection is available.
There are two ways to activate machines using a MAK key:
a. MAK Proxy Activation is a scalable solution that enables a centralized activation request on behalf of multiple machines with one machine connected to Microsoft.
b. MAK Independent Activation requires that each machine individually connect and activate against Microsoft.
Key Management Service Key
A KMS Key is used to enable the Key Management Service on a machine controlled by an organization’s IT professional. KMS usage is targeted for managed environments where more than 25 machines are consistently connected to the organization’s network. Machines running Windows Vista activate by connecting to a central Windows Vista client or Windows Server “Longhorn†running the KMS service.
After initializing KMS, the KMS activation infrastructure is self-maintaining. Users can install a KMS key and enable the KMS service on Windows Vista systems or on systems running Microsoft Windows Server “Longhornâ€. The KMS service can also easily be co-hosted with other services on the same machine. There is no extra software to download or install. Microsoft is developing a solution to support KMS on Windows Server 2003, with availability scheduled for spring 2007. A single KMS service can support hundreds of thousands of KMS clients. It is expected that most organizations will be able to operate with just two KMS machines for their entire infrastructure (one main KMS machine and one backup machine for redundancy).
A KMS service must have at least 25 physical Windows Vista clients or five physical Windows Server “Longhorn†servers connect to it before any can activate (note that virtual clients do not count toward the 25). Clients must renew their activation by connecting to the KMS machine, which is a local machine, at least once every 180 days to stay activated. Clients not yet activated will attempt to connect with the KMS service every two hours (value configurable). Once activated, they will attempt to renew their activation (locally) every seven days (value configurable) and if successful will renew their 180-day activation life span.
Clients locate the KMS service using one of the two methods:
• Auto-Discovery, in which a client machine uses domain name service records to automatically locate a local KMS service.
• Direct-connection, where a user enters the machine name and port where the KMS service resides on their network.
Clients have a 30-day grace period to complete activation. Clients not activated within this time period will go into Reduced Functionality Mode (RFM), which is described later in this paper.
As mentioned above, machines activated with KMS periodically try to renew their activation. If they are unable to connect to a KMS machine for more than 180 days, they enter a 30-day grace period, after which they enter RFM until a connection can be made with a KMS machine, or until a MAK is installed and the system is activated online or via telephone. This feature prevents systems that have been removed from the organization from functioning indefinitely without adequate license coverage.
Machines operating in virtual machine environments can be activated using KMS but do not contribute to the required 25 machine minimum for KMS activation.
Deciding Which Volume Activation Method to Use
There are five key steps in deciding which Volume Activation 2.0 methods should be used in a particular environment. The first is preparation: understanding Volume Activation 2.0 using the Business Desktop Deployment guide, understanding how target environments are configured, and understanding how the users will connect to the network. The second step is to map computers to Volume Activation 2.0 solutions. For example, in environments where there are fewer than 25 clients, or in situations where client PCs do not connect to the network for more than 210 days, MAK Proxy or MAK Independent are the preferred solutions. The third step is to install KMS to ensure activation for any machines without a MAK. The fourth step is to set up reporting for ongoing maintenance and troubleshooting as needed. These reports can be generated by the provided MOM pack or Volume Activation Management Tool, as well as any third party application. The last step is to prepare the support center by making sure support scripts are available to the Help Desk. For example, steps to convert from KMS to MAK, and handle activation warning messages as included in the BDD guide.
As with Windows XP, customers can still purchase pre-installed and pre-activated OEM SKUs from their OEM of choice. Unless re-imaged, these PCs do not require further activation.
While these new methods for activating volume licensed products may require some additional planning and management, each method provides its own benefits and advantages.
Better Software Compliance
Administrators will be able to generate reports on Windows Vista Volume Activation 2.0 using a provided reporting tool, a Microsoft Operations Manager pack, or non-Microsoft license auditing tools. These tools utilize published properties and events. By knowing the number of activated machines in their environment, administrators can monitor volume activations and know when to request additional activations. Information on how to request additional activations may be found on MVLS and eOpen.
Better License Management Tools
Using the BDD 2007 best-practice methodology and tools, which include full technical guidance on Volume Activation 2.0, administrators can prepare reference systems for image capture. Windows can be activated using scripts after systems are imaged, providing automation of activation and reducing administrative effort. These new capabilities allow better control of activation keys.
It is recommended that businesses consider additional planning to support deployment with either the KMS or MAK solutions; however, once configured the overhead required to manage either solution should be minimal. Some early adopters of this technology have seen additional benefits to both solutions beyond the improvements in activation. These include improved tracking of installations, the opportunity the required checkback for KMS activated systems offers for IT departments to touch the systems at predictable intervals, and improved anti-tampering technology.
Windows OEM Activation
OEM Activation for Windows Vista is a software protection technology for the Windows Vista operating system that improves upon System-Locked Preinstallation, which is available for Microsoft Windows XP operating systems. OEM Activation helps prevent the copying of legitimately licensed Windows Vista software onto non-licensed computers by associating the Windows operating system to the firmware of the physical computer.
In Windows XP, Microsoft started an initiative in the original equipment manufacturer (OEM) channel called System-Locked Preinstallation, to combat illegally installed copies of Windows while at the same time allowing OEMs to pre-activate Windows machines on the factory floor. OEM Activation for Windows Vista improves on this initiative, making the process easier for OEMs and making it much harder for pirates to crack the system by ensuring that Windows Vista SKUs licensed to an OEM will function only on that OEM’s hardware. With this innovation, counterfeiters attempting to use Windows media improperly will be unable to install and activate the product using media intended for recovery and reinstall that is distributed by an OEM.
Advantages of OEM activation include persistent activation, activation without connecting to any activation provider, and the ability for OEMs to use custom media images. (The recovery media is also activated.) Additional requirements for the customer are the need to maintain recovery media specific to each OEM system configuration versus having a generic image to use across all hardware.
It is important to note that organizations can also provide system images created from volume license media for an OEM to image; however, these systems must be activated either by retail or volume activation options discussed later in this document.
Fartingbob wrote:MS is a business. It has shareholders. Shareholders have the final say in general plans because they own the company.
lordfoul wrote:I'm curious how MS will fair with their new OS and sales. I don't think this is going to go as well as they had hoped. :roll:
thejynxed wrote:1)
2) Unsigned drivers will not run in Vista. No more virtual devices. No more Omega Drivers, NGO Drivers, etc. Microsoft controls what hardware and software you get to install. They do this by extorting companies into paying a yearly fee to have their drivers "signed" and keep them "signed".
LD50% wrote:Umm, let me understand this......
A cooperation makes a massive investment to bring out their (as they see it) best ever product and they are being questioned on the price hike?
This may come as a revelation to acer types, Microsoft is a money making entity NOT a charity!
The same argument could be levelled at ANY product by any cooperate company with a return on investment price hike.
I will never need or want Vista but I have been testing it ever since the code hit the net years back, friends close and enemies closer and all that.
The Vista bashing is the same as the XP bashing was way back. Vista will be a massive success, M$ do not loose money they make it, mountains of it!
Sure Vista will be full of holes and for the time being all the new ones found will be all over the news, sound familiar?
TorrentMama wrote:Fartingbob wrote:MS is a business. It has shareholders. Shareholders have the final say in general plans because they own the company.
Shareholders have a say in next to nothing. Shareholders vote on trival things, lets see the last shareholder absentee balot I recived asked token things like- 1. Boardmembers should have no managerial duties. - yes or no- and whatelse was on there, some question about a salary cap for CEO.
Shareholders have nothing to do with day to day operations, just ask Enron investors.
Fartingbob wrote:This really makes me laugh. If slyck had a comedy forum, this would have to be moved there.
JayC32 wrote:Graphix let's take a look at it like this: You don't have to buy Vista, even the Christmas rush for PC sales will not have it on. Simple answer to those complaining about the price.
Ms have every right to protect their products from illegal use and to make up a price for it we have every right not to buy it if we don't agree with either. I take it then that if you have a job, Graphix and P2P, you do it for free. If not why should any business?
There will be various flavours of Vista at different prices, just like there are two flavours of XP. Therefore the prices will vary, for crying out loud look at what some of the speculated prices were for XP I remember £200 being mentioned at one time (approx $374 US) and that was years ago.
Yes LD I remember hearing exactly the same arguments about XP. It didn't take long for it to be craked and hacked for customisation. The same will more than likely happen to Vista, MSs past record at preventing such things is lousey.
MS will be releasing the kernal to third party AV and firewall companies as they have taken heat over it, full page ads in newspapers didn't help them. If they tried to lock them out they could look forward to another visit to the courts for breaking monopoly laws, at least in the EU which hasn't shown any fear of doing it.
I don't like MS dominance in the market but there are no real viable alternatives for everyday average PC users. Before anyone mentions Linux average users play games, big stumbling block. Nor are they as easy to cinfigure straight out of the box so to speak. Until these are overcome Linux based oses will always be minority players and niche market items. I like linux by the way.
LD50% wrote:I use openBSD and Linux for everything, but I still think Vista will be a massive hit DRM or not!
Name one thing M$ have done that has failed to sell (note: failed to sell, not failed to work properly) and make lots of cash for Mr Gates?
Edit: because..
Fartingbob wrote:Thats why they have a encylopedia sized EULA agreement that you have to accept before installing. Although I wonder if you decline it if you can get your money back (you cant read it before purchase because its on the disc). Somehow i doubt that.
Arstechnica wrote: Vista's hardware tolerance: one significant change before support remediation
10/30/2006 10:42:51 AM, by Ken Fisher
Windows Vista's licensing terms have raised eyebrows among PC enthusiasts. As previously reported, Windows Vista sports a new Software Protection Platform (SPP) aimed at curbing piracy. Among SPP's many features is a service that monitors PCs for evidence of significant hardware changes. New hard drive? New motherboard? Windows Vista will recognize and keep track of the hardware in your PC, much like its predecessor Windows XP did, and it will use that information to monitor licensing compliance.
What has enthusiasts concerned are language changes to the retail license for Vista that restrict the number of times you may transfer Vista from one device to another. The license reads: "The first user of the software may reassign the license to another device one time. If you reassign the license, that other device becomes the 'licensed device.'" Putting SPP and the new license together, many have wondered if Windows Vista would permit major hardware changes such as swapping out a motherboard. To make matters more confusing, reports circulated last week claiming that Windows Vista would allow for 10 re-activations stemming from hardware changes. We decided to contact Microsoft to get to the facts.
Of re-activations and algorithms
A Microsoft spokesperson told Ars Technica that "the hardware tolerance of product activation for Windows Vista has been improved and is more flexible than that for Windows XP," indicating that re-activations caused by minor changes to a PC should be less common. "We believe these improvements will better accommodate the needs of our PC enthusiast customers," the spokesperson said.
Microsoft told Ars Technica that SPP monitors the system and measures changes against the original hardware configuration of the PC in an attempt to determine if the software has been moved to a new device. SPP uses an undisclosed algorithm to to track changes, and it remains unclear how the algorithm assesses different hardware changes. The spokesperson reiterated the company's view that Vista's hardware tolerance is more flexible than before. As to the issue of multiple re-activations, Microsoft is standing behind the language of its licenses.
"Validation will fail if the software detects a substantially different hardware configuration," the spokesperson said. "At that point, the customer is able to use the one reassignment for the new device. If, after using its one reassignment right, a customer again exceeds the tolerance for updated components, the customer can purchase an additional license or seek remediation through Microsoft’s support services."
Asked specifically about the rumors that Vista would permit 10 such re-activations instead of only one, Microsoft indicated that the company had no further comments.
Waiting game, redux
For those reading between the lines, Microsoft's response is telling. The option of seeking remediation through Microsoft support is a good sign that the company has left a giant safety net in place, much as they did with Windows XP.
As I have noted before, similar concerns over hardware upgrades surfaced before Windows XP launched. The reality since that launch has been far less dramatic than many commentators predicted. In our extensive experience with re-activations caused by hardware changes, the outcome experienced most often amounts to this: we had to use Microsoft's automated phone system to retrieve a new activation code. No money changed hands. On average, the calls took less than five minutes.
Will history repeat itself with Windows Vista? Time will tell, but from where we sit, SPP appears to have all of the bark and the bite of a pack of pugs. It might sound scary, but the reality is something else.
LD50% wrote:I use openBSD and Linux for everything, but I still think Vista will be a massive hit DRM or not!
Name one thing M$ have done that has failed to sell (note: failed to sell, not failed to work properly) and make lots of cash for Mr Gates?
Edit: because..
Users browsing this forum: No registered users and 0 guests