Hi

Can you create a global group named FileClient on the domain
and add the clients to this group
that way every client will 'log in' using the same account 
and the same account privileges?
The account would make management more centralised
and enable users to be added / removed / susupended more easily?

The global group account could be added to the server local account
admin group and assume those user rights within it.

Does this sound feasible?
Just a thought.

> -----Original Message-----
> From:	Pj Lightfoot [SMTP:peter-johnl@a...]
> Sent:	Friday, June 14, 2002 9:55 AM
> To:	professional vb
> Subject:	[pro_vb] RE: ActiveX
> 
> Hi everyone,
> 
> I've managed to connect a client application to an ActiveX server on a
> different machine. Apparently, the client user must have a user account on
> the server machine. Does anyone know how a client application can make use
> of a specific account, as opposed to using the account of the currently
> logged in user? - the problem is that I want the client to run on all the
> machines, but I can't create user accounts for everyone using them... I
> know
> services support something similar, where you can specify the account that
> the service must use to log in.
> 
> Ideally, I would like to create user "FileClient" on the server (K31DEV06)
> -
> and then have any client from any machine connect as K31DEV06\FileClient -
> Any ideas?
> 
> Pj Lightfoot
> Software Developer
> Contact Centre Solutions
> Absa Direct
> "The only reason for time is so that everything doesn't happen at once." -
> Albert Einstein (1879-1955)
> 
> ______________________________________________
> "The information contained in this communication is confidential and
> may be legally privileged.  It is intended solely for the use of the
> individual or entity to whom it is addressed and others authorised to
> receive it.  If you are not the intended recipient you are hereby
> notified that any disclosure, copying, distribution or taking action
> in reliance of the contents of this information is strictly prohibited
> and may be unlawful.  Absa is neither liable for the proper, complete
> transmission of the information contained in this communication, any
> delay in its receipt or that the mail is virus-free."
>