Officially, VMWare can't spoof MAC addresses. It is possible, but it's a pain. In Windows you can't spoof it in the Windows driver. For UCM, it would require manually modifying and XML file on the server, but last I checked it was more difficult than it was worth.<br><br><span style="font-family:Prelude, Verdana, san-serif;"><br><br></span><span id="signature"><div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">Matthew Ballard<br>Network Manager<br>Otis College of Art and Design<br>mballard@otis.edu<br><br>Sent from my Palm Pre</div></span><span style="color:navy; font-family:Prelude, Verdana, san-serif; "><hr align="left" style="width:75%">On Mar 19, 2010 7:29 PM, Jeff Mottishaw <mottie@gmail.com> wrote: <br><br>>From my understanding VMware cannot spoof arbitrary MAC addresses.
<br>They must be VMware specific MAC addresses in the format
<br>00:50:56:XX:YY:ZZ.
<br>
<br>http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=219&sliceId=1&docTypeID=DT_KB_1_1&dialogID=69266812&stateId=1%200%2069270528
<br>
<br>I have tried installing in VMware and then converting to Hyper-V but
<br>networking does not function.
<br>
<br>Unfortunately I can't move forward with "not many changes". That is
<br>not acceptable to our users, especially without notification of the
<br>changes or training on the new
<br>version.
<br>
<br>On Fri, Mar 19, 2010 at 7:20 PM, Dennis Heim <Dennis.Heim@cdw.com> wrote:
<br>> You are looking at a 2 stage upgrade if you go to 7.1(3)x. There really are not many user changes between 6.x and 7.x
<br>>
<br>> Dennis Heim
<br>> Network Voice Engineer
<br>> CDW Advanced Technology Services
<br>> 11711 N. Meridian Street, Suite 225
<br>> Carmel, IN 46032
<br>>
<br>> 317.569.4255 Office
<br>> 317.569.4201 Fax
<br>> 317.694.6070 Cell
<br>> dennis.heim@cdw.com
<br>> www.berbee.com
<br>>
<br>> -----Original Message-----
<br>> From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jeff Mottishaw
<br>> Sent: Friday, March 19, 2010 9:53 PM
<br>> To: cisco-voip@puck.nether.net
<br>> Subject: [cisco-voip] UCM Upgrade
<br>>
<br>> We have a Call Manager cluster (pub + sub) that is horribly out of date (6.0.1.2000-3). We have intentionally avoiding updating because our phone users are all billable resources and some do not deal with change very well. Since we have no idea how our complex config will look on the new versions we can't come up with a training manual, etc etc. We are now running into a couple bugs (Extension Mobility and Call Parking) that are fixed in newer versions.
<br>>
<br>> I'm writing to ask how you all deal with testing updates. I initially looked at running a CallManager lab in VMware to give our admin staff a chance to try (manually change the TFTP server on their phones) the update before we rolled it out to the production server but the licensing limitations have temporarily killed that idea.
<br>>
<br>> If we roll out the upgrade on a Friday, have our admin staff come in on Saturday to test can we safely roll back to the previous version (backup partition) on Sunday provided we don't make any changes to the configuration?
<br>>
<br>> Thanks in advance for your help and feedback.
<br>>
<br>> Jeff
<br>> _______________________________________________
<br>> cisco-voip mailing list
<br>> cisco-voip@puck.nether.net
<br>> https://puck.nether.net/mailman/listinfo/cisco-voip
<br>>
<br>
<br>_______________________________________________
<br>cisco-voip mailing list
<br>cisco-voip@puck.nether.net
<br>https://puck.nether.net/mailman/listinfo/cisco-voip
<br></span>