Re: Unable to install the standard client using login scripts

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Nguru (nguru_nospam_at_houston.rr.com)
Date: 03/25/04 

Date: Wed, 24 Mar 2004 23:01:47 -0600

I am sorry I meant to say \\smsserver\smsclient\i386
I typed \\smsserver\client\i386 by mistake

But in any case, you got the idea I hope.

Thanks in advance.

"Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
news:%23z%23LsmcEEHA.1544@TK2MSFTNGP09.phx.gbl...
> What are you using in the logon script to do installs? Are you using
> capinst? Also are you in advanced security or standard security? Have you
> configured your client push installation account and also any client
> connection account if you are in advanced security. (The legacy client
needs
> an account it can connect to the CAP on you site.) If you provide an AD
User
> ID for the client connection account then your clients should be able to
use
> this account to connect and install.
>
> --
> Thanks
> Jeff Harbaugh [MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Nguru" <nguru_nospam@houston.rr.com> wrote in message
> news:%23SoULjaEEHA.1272@TK2MSFTNGP11.phx.gbl...
> > I have SMS 2003 in AD on Windows 2003 Servers. I have a two way trust
with
> > selective-authentication.
> >
> > I need to push the client via login script because network discovery was
> not
> > very effective. The users are getting "Extended Error has occurred" I
> > granted the users NTFS rights on the shares to their nt4domain\domain
> users
> > It did not help either.
> >
> > They could browse the Active Directory Domain where SMS lives, but when
I
> > try to browse shares on the SMS servers (or any servers) I get "User not
> > found" Error 2221. I even tried adding the nt4domain\domain users group
to
> > local users on the server .. No luck.
> >
> > If I login with an AD user ID on the NT4 boxes, then, as expected .. I
> could
> > browse the SMS Servers shares.
> >
> > Is there any way to make this work without changing the External trust
to
> > "Domain-Wide Authentication"? I prefer login scripts because I could do
> the
> > client installation based on group memberships in the login scripts.
> >
> >
> > Regards
> >
> >
>
>

Relevant Pages

  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)
  • Re: Client Push Installation Security (Micorosft pls assit)
    ... > %machinename%\account for the Client push installation. ... > Network Access, can i specify a Domain Users rather than a Domain Admin ... >> Software Installation account: ...
    (microsoft.public.sms.swdist)
  • Re: a way to set source for capinst.exe?
    ... > account kicks off ccmsetup /service would have to have local admin rights ... > started this process doesn't have to remain logged in and the SMS client ... >> installation is completed. ...
    (microsoft.public.sms.admin)
  • Re: Adv Client Install Problems??
    ... The push installation account is located in Client Installation methods/Push ...
    (microsoft.public.sms.setup)
  • Re: Adv Client Install Problems??
    ... When you try advanced client push what does ... >>>>The SQL account should be fine. ... Ok I just checked the push installation account and ...
    (microsoft.public.sms.setup)