Re: Adv Client with Workgroup Computers

Hi Steve,

Thanks for responding.

I was trying to use the SMS tools from the SMS server to initiate harware
Inv for example the account is a domain account but the Client PC is in a
workgroup.

Is there a procedure for installing the ADV client localy on a workgroup
machine?

I have WINS confiured ok, I have manually added to the WINS server.

Cheers

"Steve Thompson" <stevethompson@xxxxxxxxxxxxx> wrote in message
news:ON7V5yEnFHA.764@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Mikecl" <Mike_Clark_2@xxxxxxxxxxx> wrote in message
> news:%23kkg2XEnFHA.2580@xxxxxxxxxxxxxxxxxxxxxxx
> > Struggling to Get Workgroup machines managable.
> >
> > I have seen numerous posts for Workgroup machines
> > http://myitforum.techtarget.com/articles/8/view.asp?id=7747
> > and I followed this one in partucular.. The only thing I have not done
is
> to
> > set the Sms Service account to Localsystem I looked at that but I have
it
> > configured as a domain account at moment. I am not sure of the
> ramifications
> > of changing this and cant see how to change it to Localsystem account as
> it
> > wants Domain\User syntax
> > The Server is running in Standard Security Mode
> >
> > I have pushed out the Adv sms client to 2000 odd machines in different
> > domains ok
> >
> > I have a number of Workgroup computers I would like to manage via SMS
2003
> > (SP1). I understand I cant push the SMS Adv client to the machines so I
> > configured the Adv Network Access Account made sure it had rights to the
> > \\server\smsclient share. Then on a workgroup client machine logged on
and
> > mapped a drive using the Adv Network access Account and run a script
> calling
> > ccmsetup with the appropriate command line parameters. (not in AD so did
> not
> > use /service switch.
> >
> > Ccmsetup runs and downloads to the client, on the local machine it
starts
> > running then fails geting client.msi file saying
\\server\smsclient\i386\
> > inacessible even though I have a drive mapped to the same place to run
the
> > script.
> >
> > If I then copy the client.msi to the local machine ccmsetup dir and run
it
> > manually it installs the client ok and is displayed on the SMS server.
> Wins
> > is configured and is found ok in the locationlog on the client. I have
to
> > perform a repair as not all settings (cache Size) are not configured.
> >
> > If I try and connect from the SMS server i get access denied to the logs
> dir
> > or if I try changing or initiatiing any WMI actions on the client. e.g
> > Hardware or Software Inv
> >
> > I have three questions:
> >
> > 1. Why do I get \\server\smsclient\i386 inaccessible even though I use
the
> > same Adv network access account as configured on the Server and already
> > manually mapping a drive to \\server\smsclient?
>
> The client needs permissions at the sms server... the Adv Network access
> account comes into play after the client is installed.
>
> > 2. Is it normal to get acess denied in a workgroup scenario if I try and
> > connect from the server to the client logs dir or change any setting
like
> > run hardware Inv? I can open resource explorer for the machines in
> question.
>
> What credentials are you using from the server?
>
> > 3. Will I still be able to Push software to the machines ok?
>
> Once you get the client installed, yes.
>
> I suspect that the clients may not have WINS properly configured, you'll
> need a pointer back to your SMS site server. Also, you may want to
consider
> using the Advanced security model; it's more secure and it may solve some
of
> the issues you are experiencing. I did find one link that you may want to
> check:
>
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/plan/sp1supportedconfigs.mspx
>
> Steve
>
>


.

Relevant Pages

  • RE: Cant install Windows Small Business 2003 Client
    ... Make sure that the Small Business Server ... that if the client computer is asking for the user and password is because is ... Try deleting one computer and create a new user account and recreate the ... computer object to see if that account can be use connectcomputer then. ...
    (microsoft.public.windows.server.sbs)
  • Re: Using EFS with Network Shares and SFU 3.5
    ... It does not take EFS into account. ... could again use the sharing server audit logs to see if success ... Read extended attribute and Read data, since the NFS client may ... Windows and *nix clients. ...
    (microsoft.public.windows.server.security)
  • Re: Client Push keeps failing
    ... verified all of the permissions seem correct. ... No network access account provided. ... I thought that at first too and yet the SMS console still shows this ... I am trying to get the client push to work and it keeps failing. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • RE: configuring client users
    ... This newsgroup only focuses on SBS technical issues. ... | Thread-Topic: configuring client users ... |> computer to SBS server while we need use "set up computer wizard" to ... |> For user account issue, please understand that if you join the client ...
    (microsoft.public.windows.server.sbs)