[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference chefs::ms-exchange

Title:Microsoft Exchange Server
Notice:
Moderator:FLASK2::SYSTEM
Created:Fri Feb 17 1995
Last Modified:Thu Jun 05 1997
Last Successful Update:Thu Jun 05 1997
Number of topics:1099
Total number of notes:5174

889.0. "MS Exchange Remote Management" by NETRIX::"[email protected]" (Rene Buettiker) Wed Feb 19 1997 15:39

Hi all
We�re involved in an outsourcing project including an exchange server.

We need to find all possible management tools /utilities which allow
us to manage the exchange server (on a Alpha 1000) from remote.

These should include console connections (in case system is down) 
and administrative tasks.

I�d appreciate some pointers if someone has some experience with 
remote server management.

Rgs,
Rene

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
889.1PYRO::RONRon S. van ZuylenThu Feb 20 1997 01:0423
    Exchange application management is done via the Exchange Administrator
    tool, which can run on any Windows NT Workstation or Server.
    
    Various built-in Windows NT tools work remotely, too.  User Manager,
    Server Manager, Event Viewer, Performance Monitor, etc.  Heck, the
    first three even run on Windows 95.
    
    The term "remote server management" is too generic.  Give specifics on
    what you need to do.
    
    There is no "console" on an NT box.  If the system is dead, it's dead.
    The closest thing is the "Remote Server Manager" EISA card via a modem
    you can dial into.
    
    If you're talking about simply "taking over" the display remotely (while
    it's working, of course) for tasks that require local access, SMS 1.2 can
    do it... so can PC-Anywhere 32 (nicely, but not very integrated) and
    McAfee Remote Desktop 32 (the slowest and buggiest, but integrated).
    There are probably more.
    
    Have fun.
    
    --Ron
889.2Remote ManagementNETRIX::"[email protected]"Rene BuettikerThu Feb 20 1997 09:3517
Hi Ron,

Thanks for the info.

It seems that the exchange admin utility can only be used if your PC is logged

onto the same domain as the exchange server. This looks to be the only tool
that passes on the originating domain and user name, which causes a No Access
situation (unless you could set up trust, which the customer won�t
appreciate due to security).


Any ideas?

Regards,
Rene
[Posted by WWW Notes gateway]
889.3Logon Credentials...16.72.224.33::frandsenCharacter: Doing what's right when no-one's lookingThu Feb 20 1997 15:275
The alternative to a domain logon, would be using the same "logon
credentials" for workstations in different domains.

John Frandsen
NSIS