[ConfigMgr] Why you can’t install ConfigMgr R2 on a Non-Eval Version of ConfigMgr SP1

I made a post earlier today referring to a workaround that someone had blogged about on how to install the RC version of ConfigMgr R2 on a non-eval copy of ConfigMgr SP1.

Well I’ve decided to change the post and pass on some more information I’ve received.

The reasons you should NOT workaround this “issue” are:

  • Any modifications to the R2 code are completely unsupported.
  • Modifying the code breaks the End User Licensing Agreement (EULA), which specifically states: “You may not: * work around any technical limitations in this software”.
  • This is pre-release software (remember we’re talking Release Candidate here NOT Released to Manufacturing (RTM) which IS the final product), and no pre-release software is supported by Microsoft in a production environment (unless you’re on something like a TAP in which case you’ll be covered by a supplemental EULA that DOES support this).

What you choose to do about this is entirely up to you – you pays your money and takes your chances but personally I’d recommend you play by the rules to avoid any issues.

Published Thursday, July 10, 2008 5:49 PM by chobbs

Comments

# re: [ConfigMgr] Why you can’t install ConfigMgr R2 on a Non-Eval Version of ConfigMgr SP1

Sounds familiar...

Thursday, July 10, 2008 12:52 PM by rodtrent