Or, do what I did, which *appears* to work perfectly: 1. Install Win2K adminpak.msi onto WinXP Pro. 2. Install E2K System Manager. 3. Uninstall Win2K adminpak.msi from WinXP Pro. 4. Install .NET Server Beta 3 adminpak.msi (which is downloadable from Microsoft's web site).
I'm running this way in production without any apparent problems. YMMV, but I think it will work for you, too. -Scott ----- Original Message ----- From: "Lefkovics, William" <[EMAIL PROTECTED]> To: "MS-Exchange Admin Issues" <[EMAIL PROTECTED]> Sent: Thursday, December 20, 2001 11:05 AM Subject: RE: System Manager for XP > Wait for the release code and don't use the beta for adminpak.msi in > production. > > William Lefkovics, MCSE, A+ > ----------------------------------------------------------- > Why just ride, when you can fly? > http://www.airborne.net > ----------------------------------------------------------- > Rent this space: [EMAIL PROTECTED] > > > -----Original Message----- > From: Preston Jeffares [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 20, 2001 10:25 AM > To: MS-Exchange Admin Issues > Subject: System Manager for XP > > > O.K. I found the adminpak.msi for WinXP and solved my Administration Tools > issue. Now when I go to install the system manager for exchange it wants > the Windows 2000 Administration Tools. Anyone know the work around? > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
