<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>I agree, it's confusing...but to make it more confusing "different server" doesn't mean "different server class". My SE made it very clear that if you upgrade from a 7835 class to a 7845 class regardless of how you get there, you have to pay for the 7835 to 7845 upgrade SKU.<br><br>YMMV ;)<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Ted Nugent" <tednugent73@gmail.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "Jason Aarons (US)" <jason.aarons@us.didata.com>, cisco-voip@puck.nether.net<br>Sent: Friday, November 13, 2009 3:40:53 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] call manager licensing<br><br><link href="/zimbra/css/msgview.css?v=081117021119" rel="stylesheet">To further blow your mind why do you need the server migration SKU when upgrading within the same versions but not when upgrading more than 2 hops??? And what mechanism is used when its required for UCSS upgrades... I had a horrid time getting a clients contracts straight because another partner upgraded them via UCSS and went from a 7825 to a 7835 and CM 4.1 to CM 6.1 (no SKU required according to the info below right?), they then let their ESW lapse and tried renewing it but ESW was on the 7825 not the 7835 so Cisco tried making them buy new 7835 node license and ESW.... Sorry didn't mean to highjack your thread just got my blood pressure up thinking about it again....<div>
<br></div><div><div>===========================================</div><div>Server Migrations require ordering a Hardware Migration SKU (to cover royalties Cisco owes to its</div></div><div><div>suppliers) only if you are transferring licenses to a different server AND the Cisco Unified</div>
<div>Communications Manager major version changes by less than two (e.g. 3.3 4.3, 4.24.3,</div><div>5.16.0, 6.1(2) 6.1(3), 6.06.1/7.0, etc.). If you are not transferring licenses to a different</div><div>server OR you are upgrading by two or more major versions, a Hardware Migration SKU is not</div>
<div>required. These rules also apply for customers migrating from and/or to their own “Software-only”</div><div>hardware.</div><div>Notes on UCSS:</div><div>• UCSS coverage for Hardware Migration SKU is not required/supported</div>
<div>• Hardware Migration SKU requirements apply whether software is licensed via a la</div><div>carte/traditional, or licensed via UCSS.</div><div>Examples:</div><div>• Hardware Migration SKU is required for:</div><div>o Migrate to different server, no software upgrade</div>
<div>o Migrate to different server, upgrade 6.0 to 6.x</div><div>o Migrate to different server, upgrade 6.x to 7.x</div><div>• Hardware Migration SKU is NOT required for:</div><div>o Migrate to different server, upgrade 5.x to 7.x</div>
<div>o Migrate to different server, upgrade 4.x to 6.x/7.x</div><div>o Keeping same server, no software upgrade</div><div>o Keeping same server, upgrade 6.0 to 6.x</div><div>o Keeping same server, upgrade 6.x to 7.x</div>
<div>o Keeping same server, upgrade 5.x to 7.x</div></div><div><br></div><div>===========================================</div><div> <br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br></blockquote></div><br></div>
</div></body></html>