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

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Wally Mead [MS] (wallym_at_online.microsoft.com)
Date: 10/03/04 

Date: Sun, 3 Oct 2004 11:13:22 -0700

One reason would be you can only have one MP per site, so if these are
clients that are remotely connecting to the site, they will only use the
default MP (likely at the central location with the site server). You can't
really put MPs by the clients unless the clients are located in SMS sites. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"TerryM" <terry@nospam.com> wrote in message
news:%23tqYc2KqEHA.592@TK2MSFTNGP11.phx.gbl...
> Why not create additional MPs closer to your clients...
> T
>
> "Al Corsi" <alcoit@optonline.net> wrote in message
> news:u7AZ3N7pEHA.592@TK2MSFTNGP11.phx.gbl...
> > Terry - we're working towards a solution that handles low-rights users,
> > hence the need for capinst.exe (which ultimately runs ccmsetup.exe via
> > client push installation).
> >
> > Anyhow, running client.msi is possible, but you're in for some trouble
> > during client upgrades and repairs as this method does not cache the
> > client locally (note that client.msi is cached locally for future
repairs
> > by running capinst.exe or ccmsetup.exe).
> >
> > Regards, Al
> >
> > "TerryM" <terry@nospam.com> wrote in message
> > news:%23WN1YjxpEHA.2696@TK2MSFTNGP15.phx.gbl...
> >> This may be a dumb response, but can't you just put client.msi (I
assume
> >> you mean adv client since you are talking about MPs)  in the logon
share
> >> and run it directly without going through capinst?
> >>
> >> Put logic in your logon script to determine who should get the advanced
> >> client add the right command lines and do it that way?
> >>
> >> Is there another issue you are asking about?
> >>
> >> Terry
> >>
> >> "Al Corsi" <alcoit@optonline.net> wrote in message
> >> news:%23zAeEZwpEHA.3464@TK2MSFTNGP14.phx.gbl...
> >>> dang - i did see that posting after submitting this one! sorry for the
> >>> repeat....
> >>>
> >>> Anyhow, how about the public SOURCEDIR property?! It's usually
available
> >>> for a standard MSI.... but doesn't seem so for client.msi.
> >>>
> >>> thanks for the follow-up - al
> >>>
> >>> "GMan Slater" <gmanslater@hotmail.moc> wrote in message
> >>> news:OUrnt%23vpEHA.896@TK2MSFTNGP12.phx.gbl...
> >>>> Search this newsgroup, this question has been asked and answered
> >>>> already.
> >>>>
> >>>> Short answer is no, the /AdvCliCmd switch passes MSInstaller args but
> >>>> you
> >>>> can't pass /Source= to ccmsetup this way. Bummer as I like the fact
> >>>> that
> >>>> capinst gets a CCR gnerated for users that are not admins, but I
don't
> >>>> want
> >>>> client.msi pulled from the MP all the time either. I ended up doing a
> >>>> check
> >>>> for local admin rights and if the user has them it runs ccmsetup
(with
> >>>> the
> >>>> source specified) instead of capinst. Works pretty good as:  1) Our
> >>>> newest
> >>>> images have the adv client installed already.  2) The first person to
> >>>> logon
> >>>> when we setup a new PC is a tech with admin rights.
> >>>>
> >>>> "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
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>

Relevant Pages

  • RE: Event ID 529 on cleint workstation
    ... Security Event ID 529 is a failure audit for logon/logoff. ... "logon events" generate the events on domain controllers for domain account ... The Event 529 was caused by the machine account password not being ... I suggest that you re-join the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 529 on cleint workstation
    ... "logon events" generate the events on domain controllers for domain account ... The Event 529 was caused by the machine account password not being ... I suggest that you re-join the client to ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Local Administrators
    ... When you connectcomputer the first time you logon as ... Administrator and select the Computer you are joining. ... the second reboot you login as Domain Administrator so that the Client apps ... and others which insist on Admin rights but that is another story. ...
    (microsoft.public.windows.server.sbs)
  • Re: NT4 -> Win2K3 question
    ... "not allow me logon to domain." ... I suspect you still unable to join the ... client into domain, right? ... Get Secure! ...
    (microsoft.public.windows.server.migration)
  • Re: windows client cant start completely...get blank desktop and no icons, start button, task bar, e
    ... "Logon to the problematic client as a user who can logon to other ... Logon to a working client as the user who encountered the problem. ... please check the following registry keys that define the ... not supported in newsgroup support. ...
    (microsoft.public.windows.server.sbs)