this type of question is probably getting tiring.<br>Upgrading from 2.46 to 3.x<br>currently unity is a DC (w2K) and exchange 5.5 on same box<br>Callmanger 3.12C is in it's own workgroup<br>(unity and callmanager on own Vlan 10 (subnet 10)<br>Lan is vlan 172 (subnet 172)<br><br>This appears to be recommended way (trying to keep simple):<br>1. do cleanup<br>2. export<br>3. uninstall unity<br>4. install unity 3.0 and import<br><br>question: what is best method: (note: currently to be voice mail and later to become unified messaging)<br>- Note: unity 3.0 will be pointing to corporate E2K (off unity box)<br>1. CCM and unity on same vlan (subnet), different from Lan (E2K routing then)<br>2. CCM on own subnet (vlan) and Unity on corporate (lan) segment (routing btwn CM and Unity)<br>3. or ???<br><br>also, since < 16 ports, MSDE will be used, what is the recommended filesystem layout (example below)<br>mirror set 0f 18GB drives.<br><br>C: NTFS for OS and pagefile (4GB)<br>D: NTFS for logs (4GB)<br>E: NTFS for MSDE (SQL) (10 GB)<br><br>is MSMQ recommended or a must (usually Q'g bwtn SQL - but MSDE on same box as Unity...)<br><br>anythings else you wish to add would be appreciated<br><br>
