Re: SMS client installation failures
- From: "Bog Standard" <spazzcaptain@xxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 11:45:56 -0000
I assume you do not include the SMS client in the PC images? If you do
remove it.
Also if using the login script method check in the local temp directory the
capinst.log file. This should give some background on what's going on.
When using the logon script method the client tries to install (pull) when
the user logs in. If the user does not have the necessary rights to install
the client a request is sent to the SMS server to then 'push' the client out
with the necessary admin rights.
Personally I prefer to use the logon script method as it gives me more
control over what workstations the client gets installed on. We have many
PCs that are cash tills or kiosks where no user logs in. We don't therefore
want SMS clients pushed to these PCs. If you just enable the push method SMS
will go off and install to anything it can discover.
"Asem" <Asem@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:365DA12C-0795-4497-9F12-591CF5C6FE74@xxxxxxxxxxxxxxxx
> I'm actually not sure how you installed the clients using logon script!
but
> if the user is not an administrator on his machine the installation would
> fail. using a startup script would use the machine account to install the
> client.
>
> The SMS it self will install the client software on the machines appearing
> in the console 'After they were discovered', I guess the wizard will do
the
> installation process better than the script.
>
> Check the ccm.log file on your server to figure out why you had no luck
when
> installing the client using the push cleint wizrd.
>
> "Brian" wrote:
>
> > Hello. I help to administer a mixed network (Windows NT, Windows 2000,
> > Windows XP) of roughly 350 machines. We install the SMS client by way
of a
> > network logon script. Several of our machines cannot load the client
> > properly when a user logs on.
> >
> > There is no hardware issue since many of the failing machines are
exactly
> > the same hardware as the machines that the client loads fine on. It
wouldn't
> > seem to be a configuration issue on the client machines as we image our
> > machines, so the identical machines are being imaged and therefore have
the
> > same configuration. It isn't a user issue since I have tried logging
into
> > machines that do not load the client with user ids that the client loads
fine
> > with.
> >
> > I have tried to push the client software out to the machine using SMS
admin
> > console, but no luck. I have signed onto the failed machines and
browsed out
> > to our server which houses the SMS installation files and tried running
> > client.msi, but it still doesn't load the client. The installation runs
fine
> > and doesn't kick back any errors, but we still cannot remote to the PC.
> >
> > One thing I noticed is that in the services, there is an SMS agent host
> > service running, but on the failed machines, there is no SMS remote
control
> > agent service on the machine. I would imagine that is a service that
needs
> > to run in oreder to remote to a machine.
> >
> > Any thoughts as to what I can check? I cannot find a common thread
between
> > all failed machines.
> >
> > Thanks,
> > Brian
.
- Prev by Date: Re: Side By Side Upgrade - secondaries with Legacy clients
- Next by Date: RE: MP Install issue
- Previous by thread: Re: Side By Side Upgrade - secondaries with Legacy clients
- Next by thread: RE: MP Install issue
- Index(es):
Relevant Pages
|
