• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Vista's Volume Activation 2.0

Nocturnal

Lifer
For those who are in the IT field, do you guys see yourselve's encountering problems when rolling out new products that utilize VA2.0? Previously if you had a VLK key then you enter that and you bypass activation. Now no matter what, if you are rolling out five workstations or several hundred, you will have to activate each one.

Now, maybe the first time won't be bad but what happens when you attempt to reactivate certain boxes due to problems that crop up every now and then?

Do you really feel like reading off a bunch of letters/numbers to an operator for each box that you're trying to reactivate? Does MS really think that this will make all of the users of their software happy go lucky?
 
Can't you avoid this by making a disk image of an already activated Vista install and using that image for several computers?
 
Now, maybe the first time won't be bad but what happens when you attempt to reactivate certain boxes due to problems that crop up every now and then?

Maybe if you setup the boxes properly so that the users can't break them so frequently you won't have this problem.

Can't you avoid this by making a disk image of an already activated Vista install and using that image for several computers?

Even with XP the activation hash was unique to that specific computer, so if you put an image from one computer onto another the hash won't match and it'll need reactivated.
 
Since you'll probably end up using a KMS (perferred method) or MAK, activation in an enterprise deployment really is a non-issue. There is no operator to call, etc.
 
Back
Top