DEL:  We have been successful in getting the Exchange Agent to validate
using your instructions below, so long as we are running from the ADSM
scheduler against a schedule defined on the ADSM server.  We also ran a
scheduled backup of the overall file system successfully using the NT
client.

However, we have been unable to force a Full backup from the GUI of the
Directory and/or the Information store.  Each attempt fails with
     "Exchange Error:   Access is Denied"
one the GUI, with no further on-line help available.

It seems that the validation REQUIRES the scheduler (which is associated
with the Exchange Site Services Account) to launch the agent, .  The GUI
interface does not seem to enjoy the same association, either independently
from the scheduler or as a result of the scheduler's association.

The documentation is not clear on this point at all, and is quite fuzzy that
the scheduler is required for validation.  Without it you can't seem to
associate and service to the Site Services Account, because the Agent itself
doesn't appear as a service, even when its running.

We tried opening calls, but have been told by the IBM support line that no
help is available on the product until GA on April 24th.  It's great to have
ADSM people monitoring this list, but perhaps the limitation on support
could have been  made clearer.  Is there another avenue (other than trying
to find our marketing rep, which the support line suggested) to get through
the problems?

Thanks.

Steve Kuhn, Network Manager
AEGIS Insurance Services
kuhns%aegis AT mcimail DOT com

 ----------
From: "ADSM: Dist Stor Manager"
To: ADSM-L
Cc: AEGISLAN/AEGIS/KUHNS; AEGISLAN/AEGIS/MUGNOLL; AEGISLAN/AEGIS/kantorr
Subject: Re: Exchange Agent PB
Date: Wednesday, April 01, 1998 10:00PM


MCI Mail date/time: Wed Apr 01, 1998  2:57 pm  EST
  Source date/time: Wed, 01 Apr 1998 14:38:29 -0500
 -------------------

Eric,

This problem is normally caused when running the scheduled
command from some account other than the
Exchange Site Service Account.

Go into "Control Panel", "Services", "Startup".
Change the "Log on As:" field to run the service as the
Site Services Account for your Exchange Server.
(You can find this userid in the configuration for the
server using Microsoft Exchange Administrator if you are not
sure what this should be.)

Look at Appendix C, Step 5, under "On the Exchange Server:"
for more details on settings this up.

Let me know if you are still having trouble with this.

Del Hoobler
ADSMConnect Agent Development

>> Hello,
>> There is a good news, the Exchange Agent is available !
>>
>> But with the few test I have done, I have note a problem with Scheduled
>> Backup. Here comes the log of the script with is launch in the ADSM
>> Schedule. The two first are the result of a scheduled command, the last
>> one the script manually launch. If anybody have an idea ?
>> Thanks !