<div dir="ltr">Ryan,<div><br></div><div>It sounds like you haven't seen/used the DAT?</div><div><br></div><div><a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/udat/userguide/UDAT_BK_U1401523_00_device-assignment-tool-user-guide.html">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/udat/userguide/UDAT_BK_U1401523_00_device-assignment-tool-user-guide.html</a><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 17, 2015 at 2:30 PM, Ryan Huff <span dir="ltr"><<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Scott,<br><br>The DLU <-> CUWL license model change was and continues to be a significant change for customers; no arguments there. <br><br>However, once you make it to the other side, the CUWL licensing model makes a lot more sense and is ultimately easier to manage and predict usage. Having said that; there are techniques you can use to make the 'true-up' (associating devices to users) process a little less painful. <br><br>For instance, you can use BAT to export a user list and device list. By using Excel pivot tables and a little join magic you can usually come up with a device re-import that will slap user associations on the devices (beats clicking through 1,000+ devices in GUI). If you have IM & Presence, you could do something similar for line ownership (needed for line presence).<br><br><br>Thanks,<br><br>Ryan<br><br><div><hr>Date: Thu, 17 Sep 2015 11:55:54 -0700<br>From: <a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a><br>To: <a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>; <a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br>Subject: Re: [cisco-voip] Feature Request to fix Licensing issues with EM<br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><div><div class="h5"><br><br><div dir="ltr">We are 100% EM in CM 8.6. Now I have to associate phones to Users so I can get the licensing that I have support on. 1000 users rather than 1600 phones. (450 are soft clients). Since I'm licensed for 1000 I have to "true up" my licensing ($24k). so if convert over to CUWL for 1000 why should I buy more licensing that I already have? thus working through the association of devices to users.<div><br></div><div>So now I'm stuck in a Associating user / device nightmare. which I can work through. But now I have to keep my associations current moving forward (we move users often) so I don't get out of Licensing complainants again.</div><div><br></div><div>Scott</div></div><div><br><div>On Thu, Sep 17, 2015 at 11:44 AM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Can you briefly explain this EM licensing nightmare? I'm not sure I'm aware of it.<div><br></div><div>Also, it sounds like what you are describing, implies that license compliance checks are run frequently and multiple times throughout the day, and to my knowledge they are not. How else would you keep up with all of the logging in and out of devices, unless the license compliance check was run in real time? Which was probably how it worked prior to ELM. Just spitballing a few ideas.</div></div><br><div><div><div><div dir="ltr">On Thu, Sep 17, 2015 at 1:29 PM Scott Voll <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>> wrote:<br></div></div></div><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">OK, everyone has complained about the licensing nightmare that EM plays in CM 9 and 10.<div><br></div><div>My coworker has come up with a fix......</div><div><br></div><div><br></div><div><p>In thinking this all through, I thought about how I would
like it all to work mechanically. Here
is what I would like to request as a Feature/Enhancement Request:</p>
<p> </p>
<p>When I log into a device for the first time with Extension
Mobility, I am assigned as the device owner.
That ownership is retained until one of two things happen:</p>
<p>1.<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'"> </span> I log into another like device (i.e.: I have a
8861 at my desk, and I log into Scott’s 8861 at his desk) </p>
<p>2.<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'"> </span> Someone else logged into my device.</p>
<p> </p>
<p>This way, the ownership of the device is always assigned by
the extension mobility profile and follows the user. If I have an iPhone, IPad or Jabber or other
such device, since those all require a user to log in, the ownership would be
added in the same way. This would
mitigate the licensing issues caused by extension mobility (in my opinion). </p>
<p> </p>
<p>Using this would really simplify the licensing requirements
in my thinking.</p>
<p> </p>
<p>Any thoughts?</p><p><br></p><p>Thanks</p><p><br></p><p>Scott</p><p><br></p></div></div></div></div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
</blockquote></div><br></div>
<br>_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div></div></div> </div></div>
</blockquote></div><br></div>