Same here.
In fact, if you comment out the DOMAIN statement, ALL-LOCAL is what you get
by default.
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************




> -----Original Message-----
> From: Moir,Betsy [SMTP:betsy.moir AT ABBOTT DOT COM]
> Sent: Tuesday, July 20, 1999 9:40 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: DOMAIN statement
>
> Unless there is a reason why you *wouldn't* want one of your clients to
> back
> up all locally attached drives, there should be no problem.  We've used
> the
> default of ALL-LOCAL from the start and haven't run into any problems.
>
>
>
>
> ADSM-L AT vm.marist DOT edu on 07/20/99 08:33:35 AM
> Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
> To: ADSM-L AT vm.marist DOT edu @ INTERNET
> cc:
> Subject: DOMAIN statement
>
> I have a number of clients (both NT and Netware) running on ADSM v3.1
> where
> the
> DOMAIN statement in the client dsm.opt is coded for specific local
> drives/volumes respectively (like DOMAIN C: D:) I've shot myself at times
> where
> a new
> drive was added to an NT server and was not caught in the backup for some
> time.
> Does anyone know of any 'gotchas' or such using DOMAIN ALL-LOCAL in both
> NT
> 4.0
> and Netware 4.11(soon to be v5.0) clients?
> If all is fine, i plan to changes the OPT files soon to use DOMAIN
> ALL-LOCAL
>
>