britechguy
Well-known member
@Will Watts:
Amen! But I'll go back to my original statement in direct support of yours. Microsoft is the very entity that controls whether a given official upgrade/update path is available at all. Period. End of Sentence.
If such exists, then it has to be authorized. They are the authority that either allows it or doesn't.
I use the analogous argument with regard to licenses for Microsoft software (or any software, really) and reinstallations of same. When I am doing work on a new machine, and transferring software from an old one (either before or immediately after which that software will be removed if it's a single user license to the best of my knowledge) I cannot and do not know all of the details regarding whether the license was OEM, retail, or other and it is beyond the scope of a repair technician to research that for each and every license key that is presented or can be extracted. If I go through any software maker's prescribed installation process, and during that installation process enter a key when they dictate doing so, if they activate it then the only logical conclusion is that the license is legitimate. They are the entity that is in charge of license authorization and their own internal processes should be in place to do license checking when a key is presented. There are so many factors that make it difficult to impossible to know what is a valid license key when you are not dealing with brand spankin' new software. The authorizing entity is responsible for either authorizing, or declining, activation for a presented license key. If they do, then it's valid.
While we as individuals are ethically and legally required not to engage in fraud (which means you have to intend to install something in violation of known limitations) it is still the authorizing entity that is the ultimate gatekeeper. If they don't block my entry, and I have behaved in good faith, what more am I supposed to have done?
Amen! But I'll go back to my original statement in direct support of yours. Microsoft is the very entity that controls whether a given official upgrade/update path is available at all. Period. End of Sentence.
If such exists, then it has to be authorized. They are the authority that either allows it or doesn't.
I use the analogous argument with regard to licenses for Microsoft software (or any software, really) and reinstallations of same. When I am doing work on a new machine, and transferring software from an old one (either before or immediately after which that software will be removed if it's a single user license to the best of my knowledge) I cannot and do not know all of the details regarding whether the license was OEM, retail, or other and it is beyond the scope of a repair technician to research that for each and every license key that is presented or can be extracted. If I go through any software maker's prescribed installation process, and during that installation process enter a key when they dictate doing so, if they activate it then the only logical conclusion is that the license is legitimate. They are the entity that is in charge of license authorization and their own internal processes should be in place to do license checking when a key is presented. There are so many factors that make it difficult to impossible to know what is a valid license key when you are not dealing with brand spankin' new software. The authorizing entity is responsible for either authorizing, or declining, activation for a presented license key. If they do, then it's valid.
While we as individuals are ethically and legally required not to engage in fraud (which means you have to intend to install something in violation of known limitations) it is still the authorizing entity that is the ultimate gatekeeper. If they don't block my entry, and I have behaved in good faith, what more am I supposed to have done?