Re: RE:RE:Client Install Issue!

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 11/01/04


Date: Mon, 1 Nov 2004 11:11:27 -0800

Check the Push installation account to verify the account. Also, do you have
an SLP installed? The clients need an SLP to determine the site list and
which site they belong to.

-- 
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"JAJ" <JAJ@JAJ.com> wrote in message 
news:%23Qs6scCwEHA.1308@TK2MSFTNGP09.phx.gbl...
> Jeff,
>
> After doing a little bit more research, I found out that the BITS had to 
> be
> selected under IIS. After selecting this in the ADD/Remove programs, it
> eliminated most of my problems that i was getting (errors in the MP log 
> and
> CCSETUP log). I then unchecked and rechecked the MP under site settings.
> After doing this whole process, i was able to see the SMS server as being
> the client, which was a good sign. I then proceeded to install the client 
> on
> my XP, NT, and my 2000 domain controller...this is where i am still having 
> a
> problem. When i initialize the client install through the SMS console, i
> noticed that the CCMSETUP is running on the client. But it would disappear
> and comes back up out of nowhere. it looks like it was restarting. looking
> at the ccmsetup.log on the client, i noticed this error "unable to locate
> sites list," " shutdown has been requested."
>
> i do have the SMSClient shared out.
> MP is installed correctly
> i am in Advanced Security with the AD extended
> and YES, i can add network access account.
>
> What else should i check?
>
>
>
> "Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
> news:OFDLd9evEHA.2172@TK2MSFTNGP14.phx.gbl...
>> Do you see the folder sms\client shared as SMSClient?
>> Check the MPSetup.log on the MP to make sure it installed correctly.
>> Also are you in advanced security? Have extended the AD Schema?
>> You can add a network access account under Admin Console\Site
> Heirarchy\Your
>> Site\Site Settings\Component Configuration\Software Distribution
>>
>> -- 
>> Thanks,
>> Jeff Harbaugh [MSFT]
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "JAJ" <JAJ@JAJ.com> wrote in message
>> news:Ourjo5evEHA.4076@TK2MSFTNGP14.phx.gbl...
>> > Jeff, Thanks for the reply.
>> >
>> > I did configure a Management Point on the Site Settings->\\smsserver
>> >
>> > I selected everything on this server. My SMS is currently my DP, SLP,
> MP,
>> > RP, etc.
>> >
>> > Did I miss a step?
>> >
>> > I did see a folder called c:\sms\clients\i386 where it had 
>> > ccmsetup.exe,
>> > capinst.exe, smsman.exe, client.msi.
>> >
>> >
>> >
>> >
>> > "Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
>> > news:ei4QGwevEHA.3376@TK2MSFTNGP12.phx.gbl...
>> >> You have to configure a Management Point. The MP then creates the
>> > smsclient
>> >> share which your clients will download the files to install.
>> >>
>> >> -- 
>> >> Thanks,
>> >> Jeff Harbaugh [MSFT]
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >> "JAJ" <JAJ@JAJ.com> wrote in message
>> >> news:OJmohqevEHA.1452@TK2MSFTNGP11.phx.gbl...
>> >> >I would like to elaborate on my reply earlier...
>> >> > Basically the ccmsetup.log indicated that i386 path was 
>> >> > inaccessible.
>> >> > However, I do see that file under c:\sms\client\i386 which has the
> EXE
>> >> > files. So I thought i'd create a shared file called smsclient but
> that
>> > did
>> >> > not work. i also noticed this message in the log, "CCMSETUP is being
>> >> > restarted due to administrative action."
>> >> >
>> >> >
>> >> >
>> >>
>>
>>> -------------------------------------------------------------------------
> -
>> > --
>> >> > -----------
>> >> >
>> >> > After looking at the ccmsetup.log on the xp client, I noticed that
>> >> > "...\\smsserver\smsclient\i386 was inaccessible."
>> >> >
>> >> > Of course, it's not accessible because it doesn't exist. The correct
>> > path
>> >> > is
>> >> > \\SMSSERVER\SMS\Client\i386. Do you think this is the problem? I
>> > sincerely
>> >> > think so. If that's the case, how do i change the path?
>> >> >
>> >> > Thanks!
>> >> >
>> >> >
>> >> > "Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in
> message
>> >> > news:ekOAlLevEHA.1308@TK2MSFTNGP09.phx.gbl...
>> >> >> Check on the client the ccmsetup.log to see what is happening.
>> >> >> Are you in standard or advanced security?
>> >> >> Have you configure the Client Push Installation Account - Admin
>> > Console -
>> >> >> Installation Methods - Client Push Installation - Accounts tab
>> >> >> This is where to start looking.
>> >> >> The advanced client does not support NT4 so you ahve to choose by
>> >> > Operating
>> >> >> System so it will install the legacy client on the NT4 machines.
>> >> >> Also you will need client connection accounts if in advanced
> security.
>> >> >>
>> >> >> -- 
>> >> >> Thanks,
>> >> >> Jeff Harbaugh [MSFT]
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> > rights.
>> >> >>
>> >> >> "JAJ" <JAJ@JAJ.com> wrote in message
>> >> >> news:u77Aq$dvEHA.4072@TK2MSFTNGP15.phx.gbl...
>> >> >> > Hello Everyone,
>> >> >> >
>> >> >> > I finally got my SMS 2003 Lab set up. Here is my configuration:
>> >> >> >
>> >> >> > Windows 2000 Server
>> >> >> > -Domain Controller, AD
>> >> >> > -DHCP, DNS, WINS
>> >> >> >
>> >> >> > Windows 2003 Server
>> >> >> > -SMS 2003
>> >> >> > -SQL 2000
>> >> >> >
>> >> >> > Windows XP
>> >> >> > Windows NT SP6a
>> >> >> >
>> >> >> > Here's my question:
>> >> >> >
>> >> >> > I can see all of the computers under COLLECTIONS->ALL SYSTEMS.
> After
>> >> >> > right-clicking on the Windows XP client to do a Client Install, I
>> > check
>> >> > on
>> >> >> > the XP client and noticed that the CCMSETUP is running. Great,
> that
>> > is
>> >> >> > fine,
>> >> >> > but nothing happens after that. CCMSETUP is supposed to bring
>> >> >> > another
>> >> >> > process after it but it doesn't. After going back to the SMS
> Console
>> >> >> > and
>> >> >> > update the collection, the XP client is still showing as a
>> > non-client.
>> >> >> > What
>> >> >> > am i doing wrong? I also tried this on my NT client, but nothing
>> >> > happened.
>> >> >> >
>> >> >> > JAJ
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • 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)
  • Problem installing advanced client - ccmsetup service stays active.
    ... I am having a problem with 1 PCinstalling the advanced client. ... -Pushed client install from console but install ... SMS Advanced Client is not installed. ...
    (microsoft.public.sms.setup)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)