Re: a way to set source for capinst.exe?

From: GMan Slater (gmanslater_at_hotmail.moc)
Date: 10/05/04 

Date: Tue, 5 Oct 2004 10:57:18 -0400

I do this (d in the list) now and run Ccmsetup.exe specifying the source
when the user is a local admin and I don't want capinst to have to pull from
a MP. I had thought about using the /service switch IF my logon script
determines the person was not an admin, and the PC was in AD (we still have
some PCs in older resource domains that have yet to be migrated), BUT
thinking it over it didn't sound too plausable. Seems like that whatever
account kicks off ccmsetup /service would have to have local admin rights to
allow this process to run under the system (a local admin) context. The
only advantage to this /service switch I see is that the account that
started this process doesn't have to remain logged in and the SMS client
will still get installed. But the account that kicks it off initially would
need local admin rights.

Note this text from an SMS ref site:

"/service
Forces Ccmsetup.exe to run in the local system account context. The
Client.msi file download and the client installation are both performed in
the local system context. Use this option only when you are using Active
Directory and the client computer account has access to the SMSClient\i386
shared folder on the management point. If the user does not have
administrative credentials, the operation will fail. "

Note that last line.

If I'm missing something from your post please enlighten me. 

-- 
GMan
"TerryM" <terry@nospam.com> wrote in message
news:eEIGS4sqEHA.2924@TK2MSFTNGP12.phx.gbl...
> By the way I found this blurb that may be helpful...
>
> Alternatives to this requirement of having a user logged on to the
computer
> to complete the Advanced Client installation are:
>
>   a.. Specifying a valid client connection account.
>   b.. Specifying the /service command-line option after Ccmsetup.exe.
>   c.. Specifying the /useronly command-line option after Ccmsetup.exe.
>   d.. Running a dependent program first that downloads Ccmsetup.exe,
> Client.msi, and any relevant languages-specific files or folders, such as
> Client.mst, to the client computer. Then, the program calls another
program
> that runs Ccmsetup.exe from the local hard disk. Finally, another program
> runs later to delete the downloaded files.
>       Alternative
>      Reason to use
>      Caveats and restrictions
>
>       /service command-line option
>      Use this on computers that are rarely logged on to (such as file
> servers). Ccmsetup.exe uses the computer account to download Client.msi to
> the client.
>      Active Directory is required.
>
>       /useronly command-line option
>      Use this on computers that are rarely logged on to (such as file
> servers).
>      a.. Blocks further software distribution advertisements until
> installation is completed.
>         b.. If the client computer is rebooted or the Advanced Client
> Installer fails for any other reason, software distribution does not
> automatically retry the advertisement.
>         c.. First connects to package source shared folder using the
> SMSCliTokenLocalAcct& account to impersonate a user with Administrative
> security credentials, risking a potential account lockout.
>         d.. Can cause the software installation account to connect to the
> package source shared folder, risking a potential account lockout.
>
>       Dependent program
>      The Advanced Client Installer finds Client.msi on a local hard disk
and
> performs the Advanced Client installation immediately without requiring a
> user to log on.
>      Installation fails if a dependent program does not run.
>
>
>
> Sounds like you could use one of these options so that the msi gets sent
to
> the client, but they do not require admin rights, ... this msi would come
> from a distribution point which hopefully you have closer to your clients
> besides across a WAN link...
>
> Terry
>
> "Al Corsi" <alcoit@optonline.net> wrote in message
> news:OV5NnevpEHA.2052@TK2MSFTNGP10.phx.gbl...
> > BlankHi - anyone know a way to set the source when running capinst.exe
> > from a logon script?
> >
> > We're running capinst.exe from the domain controllers netlogon share
(with
> > ccmsetup.exe and client.msi in the same location).
> >
> > But when ccmsetup.exe takes over, the client loads from the management
> > point's smsclient share instead of the DC.
> >
> > We're trying to keep clients from loading from the MP across a WAN link
> > when there's a local DC there.
> >
> > thanks - Al
> >
>
>
Loading