Re: trying to install advanced client

For push install, the Admin$ share is 'required'. So is the access to the
registry and the service control manager.

If you can't do push, you might want to try group policy. There is always
the manual install option too.

"Nathan" <Nathan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C8461076-A4CE-48DF-90C1-2B4C484B92A1@xxxxxxxxxxxxxxxx
> Sorry it's been awhile - got sidetracked on another project.
> Yes to the first 3 questions
> No to the last 3 questions
>
> One thing I have found so far is that there is no Admin$ share on client
> machines. It is a classified network and every-time I do a client install
> push or and advertised program to push the advanced client; the ccm.log on
> the SMS site server logs:
>
> Attempting to connect to administrative share on machine \\machine\admin$
> Error unable to connect to the remote registry of the machine
> Error unable to access target machine for request
>
> Is there a way to install the advanced clients without the Admin$ share
> present on the client machines? It is a classified network and the
> Admin's
> will not allow Admin$ to be shared or created. (And I wouldn't think SMS
> is
> soley dependant on the Admin$ share, as there have to be other networks
> "locked" down such as this)
>
> Also anyone with any information on setting up patch management in a
> "disconnected network" configuration? IE: I did it sucessfully with WSUS
> by
> exporting the WSUS content and metabase from a "live" network and
> importing
> into the WSUS on "disconnected" network. WSUS has helped with the
> patching,
> but I really need SMS to "complete" the patch management solution. So far
> I
> am unable to install the SMS2003 scan tools, as the installtion wizards
> attempts to connect to the internet to download the .xml files - but there
> is
> no internet connection - and the wizard will not continue or allow for a
> manual import during installation.
>
>
> Any help is appreciated.
>
>
>
> --
> Nate
>
>
> "Anthony Puca" wrote:
>
>> Let me start with Basic ?'s...
>> Did you do AD Schema Extensions?
>> If so, did you set the ACL on the AD Systems/Systems Management
>> container?
>> Are you doing Adv. Security?
>> Are your clients running Windows Firewall or any other 3rd party
>> firewall?
>> Are the clients running any form of Anti-Spyware software?
>> When you push to a client, does it get the System32\ccmsetup folder?
>>
>> --
>> Anthony Puca
>> MCSE, SMS
>> Interlink Group
>> Denver, CO
>> "Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:MPG.1d44e0ab302a13398a06b@xxxxxxxxxxxxxxxxxxxxxxx
>> >
>> > Just wanted to comment that sms uses any form of name resolution, not
>> > just netbios name resolution. If the systems are resolvable by dns or
>> > any other means you should be fine.
>> >
>> > In article <#vjt1TkiFHA.3568@xxxxxxxxxxxxxxxxxxxx>,
>> > sofuoglucem@xxxxxxxxxxx says...
>> >> SMS uses NetBIOS names to access clients as you can see from the CCM
>> >> log
>> >> file. To check whether NetBIOS name resolution is working properly on
>> >> your
>> >> network, ping this machine with its NetBIOS name on the SMS server. In
>> >> this
>> >> case "ping PRGGP22". If client's name couldn't resolved by SMS server
>> >> client
>> >> installation will not work.
>> >>
>> >
>> > --
>> > Kim Oppalfens
>> > MVP SMS
>> > Computacenter Belgium
>>
>>
>>


.

Relevant Pages

  • Re: pushing software to non domain servers
    ... access to the machine to push the client. ... network access account defined. ... >> For systems in the workgroup you will need to install the agent manually. ...
    (microsoft.public.sms.misc)
  • Re: Client Push install not working for secondary site, Advanced c
    ... You have to enable push on the secondary site. ... > But You say that client push only works from the primary site. ... > understand is that Automated install will work and this will install the ...
    (microsoft.public.sms.setup)
  • Re: Deny Interactive Logon but Allow Runas
    ... that occasionally an install can become 'corrupt' and needs re-installing. ... client has version 6 of the software, with fix pack 2, so they need to get ... We've tried virtualisation, running VMware, and giving the users local admin ...
    (microsoft.public.windowsxp.security_admin)
  • Re: A couple of SMS problems
    ... client, you mean that in the context of the push install. ... For a site-wide push, each install only happens because a discovery record ... We are running win2k server sms 2.0sp5. ...
    (microsoft.public.sms.admin)
  • Re: pushing software to non domain servers
    ... "Berni" wrote in message ... > I have test to push by using a variable and also a defined workgroup ... I read from your post that you already have the client ... supported way to install the client on workgroup machines is manually. ...
    (microsoft.public.sms.misc)