<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">2 days? I'd be happy with 2 WEEKS from
most of my interactions with licensing recently. And having to
get account team to escalate to get some of them resolved in that
time frame. (CallManager/Unity and Prime Collaboration
Assurance/Provisioning licensing issues in the last couple weeks,
both a major headache.)<br>
<br>
If you have current UCSS/ESW and know your contracts and have all
your licenses that you've purchased registered and activated on
the system, theoretically it follows their script. If you have
any unapplied licenses, get those fixed before you even run the
utilities and open a case. We purchase licenses as we bring users
onto the system, so we had 150+ purchases of licenses, some of
which were 1 or 2 at a time. Any of those that got missed on
CUCM/UConn are lost in the process if they aren't in the system
before you upgrade.<br>
<br>
If you have an account team, get them involved with it and make
sure you have records of exactly how many and what type of
licenses you've purchased. The LCT will downgrade everything to
the lowest possible license. So a user with one phone will get
assigned UCL licenses even if you have only ever purchased a CUWL
Std/Pro licenses. Getting this straight with licensing has been a
6-8 week headache even before we began our upgrade.<br>
<br>
If you don't have users assigned to in-use phones, try to take
care of that on 8.6, it will save you a lot of licensing hassle
once you get to 10.5, that said, there's a very easy to run report
on 10.5 to show you all those unassigned devices that doesn't
appear to exist anywhere on 8.6.<br>
<br>
Good luck, and remember that once you do the upgrade you have 60
days to get it fixed or you can't make any administrative changes.<br>
<br>
That said, once you do get to 10.5, things like codec preference
lists have made interop issues just go away. Our lead VoIP guy
was less stressed 2 days after the upgrade than he had been in
months due to many of the weird little problems with 8.6 just
going away after the upgrade. Next step is to get some additional
Subs built to get us where we need to be for our growth on the
system, and hostname/certificate changes and to enable Expressway
C/E.<br>
<br>
Jeremy "TheBrez" Bresley<br>
<a class="moz-txt-link-abbreviated" href="mailto:brez@brezworks.com">brez@brezworks.com</a><br>
<br>
On 12/11/2014 5:45 PM, Josh Warcop wrote:<br>
</div>
<blockquote
cite="mid:BLU406-EAS1156CD7125343CD4D9BE981B3630@phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>
<div style="font-family: Calibri,sans-serif; font-size: 11pt;">I'm
not sure what licensing team you're working with but there is
a specific migration team for Collab products. We do several
upgrades monthly for clients and it has never been over 24
hours. Understanding everything that needs to be done prior to
engaging TAC is usually the fault of the engineers or client.<br>
<br>
SWSS Contract in place? If not still current ESW/UCSS? Have
you verified with UCSS support? Has LCT been submitted
properly with the online form? Has PUT been used properly to
acquire any licensing?<br>
<br>
This can all be done in advance and within a day. If you can't
get the stuff via the automated methods and open a case
presenting everything properly is necessary to get past level
1 GLO and to migration support.
<br>
<br>
Like I mentioned earlier we are never two business days beyond
getting ELM licensed after an upgrade.<br>
<br>
Thanks!<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir="ltr">
<hr>
<span style="font-family: Calibri,sans-serif; font-size: 11pt;
font-weight: bold;">From:
</span><span style="font-family: Calibri,sans-serif; font-size:
11pt;"><a moz-do-not-send="true"
href="mailto:btalley@gmail.com">Bill Talley</a></span><br>
<span style="font-family: Calibri,sans-serif; font-size: 11pt;
font-weight: bold;">Sent:
</span><span style="font-family: Calibri,sans-serif; font-size:
11pt;">12/11/2014 6:36 PM</span><br>
<span style="font-family: Calibri,sans-serif; font-size: 11pt;
font-weight: bold;">To:
</span><span style="font-family: Calibri,sans-serif; font-size:
11pt;"><a moz-do-not-send="true"
href="mailto:ewellnitzvoip@gmail.com">Erick Wellnitz</a></span><br>
<span style="font-family: Calibri,sans-serif; font-size: 11pt;
font-weight: bold;">Cc:
</span><span style="font-family: Calibri,sans-serif; font-size:
11pt;"><a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net">cisco-voip</a></span><br>
<span style="font-family: Calibri,sans-serif; font-size: 11pt;
font-weight: bold;">Subject:
</span><span style="font-family: Calibri,sans-serif; font-size:
11pt;">Re: [cisco-voip] licensing turn around time 8.6 to 10.5</span><br>
<br>
</div>
<div class="BodyFragment">
<div class="PlainText">Hahahahahahahahahahaha...<br>
<br>
Sorry I shouldn't laugh, but Cisco's license upgrade process
for UC 10 is laughable at best. Licenses have to be approved
by a product manager and its now increased to a 10-12 business
day process. Luckily theres a lengthy grace period before
you're locked out of provisioning the servers.<br>
<br>
Sent from an Apple iOS device with very tiny touchscreen input
keys. Please excude my typtos.<br>
<br>
> On Dec 11, 2014, at 5:19 PM, Erick Wellnitz
<a class="moz-txt-link-rfc2396E" href="mailto:ewellnitzvoip@gmail.com"><ewellnitzvoip@gmail.com></a> wrote:<br>
> <br>
> All,<br>
> <br>
> Quick question about licensing for CUCM/UCONN<br>
> <br>
> Going from 8.6 to10.5 I should be able to run the license
count tool and submit to licensing along with a contract
number, correct? Is there usually a long turn around time or
is it still a day or less?<br>
> <br>
</div>
</div>
</blockquote>
<br>
</body>
</html>