<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2>Wes,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2>Thanks for the reply.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2>I attempted an install from an MS Disk but so many of the
devices showed up in Device manage as unknown, I figured I could get a stable
install off the MCS disks.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2>I'll go back to the MS Disks and fight through
it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2>BTW: My understanding was that the MCS install was a
vanilla install with specific services disabled.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=046464221-26042006> <FONT
face=Arial color=#0000ff size=2>What else makes it so
different?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006><FONT face=Arial
color=#0000ff size=2>Scott</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=046464221-26042006></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Wes Sisk [mailto:wsisk@cisco.com]
<BR><B>Sent:</B> Wednesday, April 26, 2006 4:44 PM<BR><B>To:</B> Scott
O'Donnell<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Installing Unity from MCS Hardware Detection Disk
Set?<BR></FONT><BR></DIV>
<DIV></DIV>the win-OS disks (2000.2.7, 2000.4.1, 2000.4.3) are for CM, PA, CRA,
CER only. Unity is not supported with those OS disks.<BR><BR>Unity does
have platform configuration disks that ship with a different (full featured)
version of windows.<BR><BR>You will need to use the windows install disk that
comes with unity or one directly from MS.<BR><BR>/Wes<BR><BR>Scott O'Donnell
wrote:
<BLOCKQUOTE cite=mid17A170DC8DD5CC44BA56B24B366EB60B01B46FE1@E3K-VS1.ccsi.local
type="cite">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR>
<DIV><SPAN class=625535619-26042006><FONT face=Arial size=2>Has anyone
installed Unity using the disk set for installing MCS
servers?</FONT></SPAN></DIV>
<DIV><SPAN class=625535619-26042006><FONT face=Arial size=2>I have a customer
that is providing the Windows Licensing for Unity but when installing from
their CD, the 7815 I'm installing for Unity shows up with a load of unknown
devices.</FONT></SPAN></DIV>
<DIV><SPAN class=625535619-26042006><FONT face=Arial size=2>Is there anything
installed (or not installed) with the MCS image install that will screw Unity
up and cause it not to work?</FONT></SPAN></DIV>
<DIV><SPAN class=625535619-26042006></SPAN> </DIV>
<DIV><SPAN class=625535619-26042006></SPAN> </DIV><PRE wrap=""><HR width="90%" SIZE=4>
_______________________________________________
cisco-voip mailing list
<A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE></BLOCKQUOTE></BODY></HTML>