Re: Local Administrators

From: Andy (andy.baguley_at_cwcom.net)
Date: 06/19/04 

Date: Sat, 19 Jun 2004 19:47:19 +0100

Frank

Thanks

I was'nt aware the "warning" was bogus!! but I seem to recall (could be
wrong) it repeating until the user had admin rights.

However when in the connect computer procedure you add users to the client,
does that not add those users as local admin?

Then the new user joins the company and was not part of the original connect
computer list?

Rgds
Andy

"Frank McCallister" <anonymous> wrote in message
news:uWoBysiVEHA.1012@TK2MSFTNGP09.phx.gbl...
> Hi Andy
>
> That is not correct. When you connectcomputer the first time you logon as
> Administrator and select the Computer you are joining. You then add the
> Users who are going to use that Workstation. After completing the Wizard
on
> the second reboot you login as Domain Administrator so that the Client
apps
> will be Downloaded and installed. After that any user who was selected can
> logon without Admin rights and use those programs. Unfortunately they will
> get a bogus warning about rights on the first use but Outlook will Open
and
> Setup correctly. Also unfortunately there are some rogue programs like
MYOB
> and others which insist on Admin rights but that is another story.
>
> Frank McCallister
> COMPUMAC
> "Andy" <andy.baguley@cwcom.net> wrote in message
> news:%23$6mlgiVEHA.3428@TK2MSFTNGP12.phx.gbl...
> > Michael
> >
> > I wish you well.
> >
> > It will mean you have to log on to every client, as every anticipated
> > user,
> > and them presumably demote them afterwards.
> >
> > If a new user then comes into the org, you have to set them up on each
> > client they are likely to use first.
> >
> > It's begining to defeat the point of central management from a server
!!!!
> >
> >
> > "Harlequin" <michael.mason@arraspeople.co.uk> wrote in message
> > news:OxyFWciVEHA.2700@TK2MSFTNGP10.phx.gbl...
> >> Andy
> >>
> >> as a workaround I have decided to configure all PCs myself before they
> > enter
> >> the domain.
> >>
> >> this of-course is an impractical solution for some but I am only going
to
> > be
> >> setting up maybe 10 PCs at most (I hope).
> >>
> >> -----------------------------
> >> Michael Mason
> >> Arras People
> >> www.arraspeople.co.uk
> >> -----------------------------
> >>
> >> "Andy" <andy.baguley@cwcom.net> wrote in message
> >> news:%23S$GSUiVEHA.1048@tk2msftngp13.phx.gbl...
> >> > During the client install it became apparent that all users had to be
> >> > members of the local admin group to effect the "first time" prog
> >> > install
> >> of
> >> > client apps.
> >> >
> >> > This then leaves them free to do virtually anything to the
client!!!!!
> >> >
> >> > Is this by design, and can I demote them after the first run to
> >> > preserve
> >> > some semblance of client standardisation and reliability?
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

Relevant Pages

  • Re: Adv Client Login Script Install
    ... I've created a user with domain admin rights and verified that the acct ... when trying to use the logon script to install the client. ... SLP HTL-SMS specified on the command line, ...
    (microsoft.public.sms.setup)
  • Re: a way to set source for capinst.exe?
    ... for local admin rights and if the user has them it runs ccmsetup (with the ... images have the adv client installed already. ... when we setup a new PC is a tech with admin rights. ... > a logon script? ...
    (microsoft.public.sms.admin)
  • Re: BDC Problem (Client can not join domain)
    ... Is this failing for users without admin rights only? ... If failing for Domain Admins ... Can you authenticate from Windows 2000 machine to SBS 2003 server? ... Adding a client should should success provided DC and GC are available. ...
    (microsoft.public.windows.server.active_directory)
  • Re: a way to set source for capinst.exe?
    ... how about the public SOURCEDIR property?! ... > images have the adv client installed already. ... > when we setup a new PC is a tech with admin rights. ... >> a logon script? ...
    (microsoft.public.sms.admin)