<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Justin,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Good point… I didn’t think about this… However, since we are
upgrading to new hardware… I could do the upgrade in the lab from 4.x on the
old to 6.x on the new, generate the license, and then blow the server away and
start fresh. Just seems like a lot of wasted man hours…<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Matt<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Justin Steinberg
[mailto:jsteinberg@gmail.com] <br>
<b>Sent:</b> Thursday, March 06, 2008 4:57 PM<br>
<b>To:</b> Linsemier, Matthew<br>
<b>Cc:</b> Jonathan Charles; Cisco Voip List; Frazee, Timothy<br>
<b>Subject:</b> Re: [cisco-voip] callmanager license migration from 4.x to 6.x<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>not exactly.<br>
<br>
If you install CM6 on your LAB 7835, the associated DMA license files will
generate with that lab 7835 MAC address<o:p></o:p></p>
<div>
<p class=MsoNormal>On Thu, Mar 6, 2008 at 4:45 PM, Linsemier, Matthew <<a
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>This would great, except for the fact that you still have to
perform the<br>
entire upgrade to get this result. Again, there are a lot of us out<br>
there that want to perform a more controlled migration to 6.x than just<br>
upgrading the entire box in one fell swoop.<br>
<br>
In our case we have an extra 7835 server in the lab so if I can't get<br>
licensing through using the SO I can pop a drive out of our production<br>
Publisher and perform the upgrade, get the new license without effecting<br>
actually upgrading our production environment. However, everyone can't<br>
necessarily do this.<br>
<br>
There still needs to be an easier way. Would just running a utility on<br>
a 4.x server that generates a 6.x license (for Cisco) without upgrading<br>
really make a huge difference? I understand that they are trying to<br>
prevent people from "cheating the proverbial licensing system", but<br>
there are so many workarounds already that it really doesn't matter in<br>
the grand scheme of things in my humble opinion.<br>
<br>
Matt<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
-----Original Message-----<br>
From: Jonathan Charles [mailto:<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>]<br>
Sent: Thursday, March 06, 2008 4:32 PM<br>
To: Linsemier, Matthew<br>
Cc: Frazee, Timothy; Cisco Voip List<br>
Subject: Re: [cisco-voip] callmanager license migration from 4.x to 6.x<br>
<br>
Then, here's what you do to make life easy<br>
<br>
Use the DMA tool and upgrade CCM to 6<br>
<br>
Then, get the license.<br>
<br>
Then blow the CCM6 box away and build it from scratch<br>
<br>
use the license you just got.<br>
<br>
<br>
<br>
Jonathan<br>
<br>
On Thu, Mar 6, 2008 at 3:23 PM, Linsemier, Matthew<br>
<<a href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>>
wrote:<br>
> We will be doing something similar as the original poster here within<br>
> the next month. We are installing a brand new cluster
specifically<br>
> because we don't want to upgrade. At Networkers Live in 2006,
the<br>
Cisco<br>
> personnel in the CallManager 5.x/6.x licensing breakout session<br>
stated<br>
> that you can get licenses generated by providing them with the<br>
original<br>
> Cisco Sales Order number.<br>
><br>
> On a side note, someone does need to take this back to Cisco to make<br>
> this process easier. In our case we have almost 5 years of
moves,<br>
adds,<br>
> changes, office closures, multiple upgrades of the database (from<br>
> versions 3.x to 4.x), old configurations lingering around, etc.
I<br>
don't<br>
> want this stuff imported into a fresh clean UCM 6.0 cluster. We want<br>
a<br>
> virgin start which is why we are planning to install from scratch.
I<br>
> imagine we are not alone.<br>
><br>
> Matt<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Jonathan<br>
> Charles<br>
><br>
><br>
> Sent: Thursday, March 06, 2008 1:34 PM<br>
> To: Frazee, Timothy<br>
> Cc: Cisco Voip List<br>
> Subject: Re: [cisco-voip] callmanager license migration from 4.x to<br>
6.x<br>
><br>
> No.<br>
><br>
> There are only two methods of getting data from CCM 4 to CCM 6<br>
><br>
> METHOD 1: DMA and then a clean rebuild of CCM6 referencing the DMA<br>
file.<br>
><br>
> METHOD 2: BAT, export the info from CCM 4, reimport into CCM6<br>
><br>
><br>
><br>
> Jonathan<br>
><br>
> On Thu, Mar 6, 2008 at 12:05 PM, Frazee, Timothy<br>
> <<a href="mailto:Timothy_Frazee@adp.com">Timothy_Frazee@adp.com</a>>
wrote:<br>
> > Can you do the upgrade on the 4.x box to 6.x, to get all of
your<br>
> > licenses upgraded and such, then do a backup/restore from
the<br>
> upgraded<br>
> > 4to6 box to a newly installed 6 server?<br>
> ><br>
> > A lot of work I know.<br>
> ><br>
> ><br>
> > -----Original Message-----<br>
> > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> > [mailto:<a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Jonathan<br>
> > Charles<br>
> ><br>
> ><br>
> > Sent: Thursday, March 06, 2008 11:08 AM<br>
> > To: Aman Chugh<br>
> > Cc: Cisco Voip List<br>
> > Subject: Re: [cisco-voip] callmanager license migration
from 4.x<br>
to<br>
> 6.x<br>
> ><br>
> > Do the windows upgrade.<br>
> ><br>
> > Seriously, you only have two other options...<br>
> ><br>
> > Option 1: Buy licenses for everything.<br>
> ><br>
> > Options 2: Convince Cisco to give you one.<br>
> ><br>
> ><br>
> ><br>
> > Jonathan<br>
> ><br>
> > On Thu, Mar 6, 2008 at 9:23 AM, Aman Chugh <<a
href="mailto:aman.chugh@gmail.com">aman.chugh@gmail.com</a>><br>
> wrote:<br>
> > > Thanks all for replying. I am not doing a backup and
restore ,<br>
I<br>
> have<br>
> > two<br>
> > > different clusters one 4.x cluster and one 6.x
cluster , We are<br>
not<br>
> > using<br>
> > > the backup of 4.x on 6.x, I build a new 6.x system
and did a new<br>
> > install on<br>
> > > it, Now we are taking down the 4.x system and want
to migrate<br>
all<br>
> > phones on<br>
> > > it to 6.x. How do I get this file as I am not doing
a windows<br>
> upgrade<br>
> > for<br>
> > > 6.x. I extracted the tar file which DMA generates ,
i could not<br>
> find<br>
> > any<br>
> > > license xml fle.Hope I am clear.<br>
> > ><br>
> > > Regards,<br>
> > ><br>
> > > Aman<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > On 3/6/08, James Buchanan <<a
href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>> wrote:<br>
> > > > Hello,<br>
> > > ><br>
> > > > FYI...it fails because the first one or two
lines of the XML<br>
are<br>
> > > > actually not XML. Omit those lines in the copy,
and all should<br>
be<br>
> > well.<br>
> > > ><br>
> > > > Thanks,<br>
> > > ><br>
> > > > James<br>
> > > ><br>
> > > > -----Original Message-----<br>
> > > > From: <a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> > > > [mailto:<a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of<br>
Jonathan<br>
> > > > Charles<br>
> > > > Sent: Thursday, March 06, 2008 8:07 AM<br>
> > > > To: Justin Steinberg<br>
> > > > Cc: Cisco Voip List<br>
> > > > Subject: Re: [cisco-voip] callmanager license
migration from<br>
4.x<br>
> to<br>
> > 6.x<br>
> > > ><br>
> > > > Just a quick note...<br>
> > > ><br>
> > > > The last four times I have done this, it has
failed and said,<br>
> > 'invalid<br>
> > > > XML file'... I then sent it to <a
href="mailto:licensing@cisco.com">licensing@cisco.com</a> and got a<br>
> license<br>
> > > > in a few hours... no biggie... but expect it to
fail...<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > JOnathan<br>
> > > ><br>
> > > > On Thu, Mar 6, 2008 at 6:51 AM, Justin
Steinberg<br>
> > <<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>><br>
> > > > wrote:<br>
> > > > > on the new cm6 system, login to ccmadmin
goto<br>
> > system>licensing>license<br>
> > > > file<br>
> > > > > upload. You can download the xml
file there and then you<br>
will<br>
> > need to<br>
> > > > > upload that file to cisco's website and
they will then email<br>
> you a<br>
> > > > permanent<br>
> > > > > xml license file.<br>
> > > > ><br>
> > > > > The above process will give you:<br>
> > > > > 1) DLU's for your system<br>
> > > > > 2) CM node licenses<br>
> > > > ><br>
> > > > > However, you will need to use the PUT to
order a CM4to6<br>
upgrade<br>
> > and<br>
> > > > they<br>
> > > > > will ship you a PAK that you can use to
license the CM6<br>
feature<br>
> > > > license.<br>
> > > > > Without this feature license the CM
service will not start.<br>
> > > > ><br>
> > > > > Justin<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > On Thu, Mar 6, 2008 at 5:36 AM, Aman Chugh<br>
> <<a href="mailto:aman.chugh@gmail.com">aman.chugh@gmail.com</a>><br>
> > > > wrote:<br>
> > > > ><br>
> > > > > ><br>
> > > > > ><br>
> > > > > ><br>
> > > > > ><br>
> > > > > > I need some help with this, I am
migrating licenses from<br>
ccm<br>
> 4.x<br>
> > to<br>
> > > > 6.x, I<br>
> > > > > have ran DMA and I am looking for the
intermediary license<br>
file<br>
> > which<br>
> > > > all<br>
> > > > > the documents talk about, I am not doing a
complete restore<br>
of<br>
> 4.x<br>
> > on<br>
> > > > 6 .x ,<br>
> > > > > I just need licenses to be migrated from
the old system to<br>
the<br>
> new<br>
> > > > one. I<br>
> > > > > have looked at tar file which DMA creates
but can't find<br>
that<br>
> xml<br>
> > file<br>
> > > > > needed for new license generation.<br>
> > > > > ><br>
> > > > > > TIA<br>
> > > > > ><br>
> > > > > > Aman<br>
> > > > > ><br>
> > > > > ><br>
> > > > > >
_______________________________________________<br>
> > > > > > cisco-voip mailing list<br>
> > > > > > <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > > > > > <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > > > > ><br>
> > > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > >
_______________________________________________<br>
> > > > > cisco-voip mailing list<br>
> > > > > <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > > > > <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > > > ><br>
> > > > ><br>
> > > > _______________________________________________<br>
> > > > cisco-voip mailing list<br>
> > > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > > > <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > > > _______________________________________________<br>
> > > > cisco-voip mailing list<br>
> > > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > > > <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > cisco-voip mailing list<br>
> > > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > > <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > ><br>
> > ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> ><br>
> ><br>
> > This message and any attachments are intended only for
the use of<br>
the<br>
> addressee and may contain information that is privileged and<br>
> confidential. If the reader of the message is not the intended<br>
recipient<br>
> or an authorized representative of the intended recipient, you are<br>
> hereby notified that any dissemination of this communication is<br>
strictly<br>
> prohibited. If you have received this communication in error, please<br>
> notify us immediately by e-mail and delete the message and any<br>
> attachments from your system.<br>
> ><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> CONFIDENTIALITY STATEMENT<br>
> This communication and any attachments are CONFIDENTIAL and may<br>
> be protected by one or more legal privileges. It is intended<br>
> solely for the use of the addressee identified above. If you<br>
> are not the intended recipient, any use, disclosure, copying<br>
> or distribution of this communication is UNAUTHORIZED. Neither<br>
> this information block, the typed name of the sender, nor<br>
> anything else in this message is intended to constitute an<br>
> electronic signature unless a specific statement to the<br>
> contrary is included in this message. If you have received this<br>
> communication in error, please immediately contact me and delete<br>
> this communication from your computer. Thank you.<br>
><br>
CONFIDENTIALITY STATEMENT<br>
This communication and any attachments are CONFIDENTIAL and may<br>
be protected by one or more legal privileges. It is intended<br>
solely for the use of the addressee identified above. If you<br>
are not the intended recipient, any use, disclosure, copying<br>
or distribution of this communication is UNAUTHORIZED. Neither<br>
this information block, the typed name of the sender, nor<br>
anything else in this message is intended to constitute an<br>
electronic signature unless a specific statement to the<br>
contrary is included in this message. If you have received this<br>
communication in error, please immediately contact me and delete<br>
this communication from your computer. Thank you.<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<P><FONT face=Arial color=#808080 size=1>
<HR>
</FONT></P>
<P><FONT color=#808080><FONT face=Arial size=1>CONFIDENTIALITY STATEMENT<BR>This
communication and any attachments are CONFIDENTIAL and may be protected by one
or more legal privileges. It is intended solely for the use of the addressee
identified above. If you are not the intended recipient, any use, disclosure,
copying or distribution of this communication is UNAUTHORIZED. Neither this
information block, the typed name of the sender, nor anything else in this
message is intended to constitute an electronic signature unless a specific
statement to the contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete this
communication from your computer. Thank you.</FONT> </FONT></P>
<P><FONT color=#808080>
<HR>
</FONT></P>
</body>
</html>