<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>This could have changed, but from what I understand, Dell's models and components change faster than is common in other manufactures like HP and IBM. This inconsistency of hardware, while fine for consumer applications, might cause issues <span>with enterprise apps.<br><br>Just a thought. They might do things differently now.<br><br><span name="x"></span>---<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 (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Jason Gurtz" <jasongurtz@npumail.com><br><b>To: </b>"cisco-voip" <cisco-voip@puck.nether.net><br><b>Sent: </b>Thursday, January 19, 2012 12:29:39 PM<br><b>Subject: </b>Re: [cisco-voip] CUCM 8.6 hardware<br><br>> Still no roadmap for Dell.<br><br>I am also intrigued by the lack of Dell validation. We're primarily an HP<br>shop, so not really affected here, but it seems odd to me when the #2 (I<br>think?) server vendor is explicitly called-out as unsupported. My boss<br>says, "maybe Dell doesn't do good enough hardware QC." ;)<br><br>Anyone have insight on the vetting process?<br><br>~JasonG<br><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>