Re: Advanced client install!

From: ipsec23 (ipsec23_at_discussions.microsoft.com)
Date: 07/14/04


Date: Wed, 14 Jul 2004 08:46:19 -0700

Hi Jeff,
Thanks for the response. Well on the "Client Push Installation" properties ,accounts tab, i have added <Domainname/administrator>. This account definitely exists as a part of local accounts on the DC. Also 95% of my clients have the SMS advanced Client installed on them and they are working great! Its just these three machines that i am having problems with. I believe there is another person who has posted on this thread about having a simiar issue.It would great if you could let us know the solution to this.
Many Thanks!!

"Jeff Harbaugh [MSFT]" wrote:

> That is access denied. Your Push installation account must be a member of
> the local admin group on the DC's.
>
> --
> Thanks,
> Jeff Harbaugh [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "ipsec23" <ipsec23@discussions.microsoft.com> wrote in message
> news:624DE8FF-EF3F-4C6A-BE26-8D0ACBFCE03A@microsoft.com...
> > Hi,
> > I had SMS 2003 up and running when i ran into some complex problems that
> > made me deinstall the whole setup which i was running for the past 4
> > months. Now have brought up a new installation and things are working fine
> > except that a few clients are not installing advanced clients. These
> > clients happen to be domain controllers!Following is the snippet of the
> > ccm.log from the site server giving information of the status of the
> > installation.
> > ccm.log snippet
> > =========
> > ======>Begin Processing request: "TUMERIC", machine name: "tumeric"
> > ---> Attempting to connect to administrative share '\\tumeric\admin$'
> > using account 'XYZ\administrator'
> > ---> Trying each entry in the SMS Client Remote Installation account list
> > ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using
> > account kidzonline2000\administrator (0000052e)
> > ---> LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account
> > XYZ\administrator (0000052e)
> > ---> ERROR: Unable to connect to remote registry for machine name
> > "tumeric", error 5.
> > ---> ERROR: Unable to access target machine for request: "TUMERIC",
> > machine name: "tumeric", error code: 5
> > Stored request "TUMERIC", machine name "tumeric", in queue "Retry".
> > <======End request: "TUMERIC", machine name: "tumeric".
> > Submitted request successfully
> > Getting a new request from queue "Retry" after 100 millisecond delay.
> > Sleeping for 60 minutes for queue "Retry".
> > CCR count in queue "Retry" is 9.
> > Sleeping for 916 seconds...
> > Thread has been inactive too long. Closing thread
> > --- This thread is terminating due to inactivity
> > ----- Terminated CCR processing thread. There are now 0 processing threads
> > The Site Control File has not changed since the last parameter update.
> > Updating Site Parameters
> > Default MP: NUTMEG
> > *** Advanced Security Mode detected ***
> > Checking configuration information for server: \\NUTMEG\.
> > Install on DC: False
> > Sleeping for 1200 seconds...
> > Waiting for change in directory "D:\SMS\inboxes\ccr.box" for queue
> > "Incoming", (30 minute backup timeout).
> >
> > All the three servers show the ccm.log output. Looks to me like there is
> > some admin account securty problem! Well i am able to logon to the server
> > using the same credentials and also able to connect to a remote share on
> > the server from the site server using the same account. Could someone
> > kindly let me know what problem i am running into.
> > Many Thanks!
>
>
>



Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control panel can you do an "Auto Detect site Code" successfully? ... See Adsysdis.log on site server ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Failed to create virtual directory
    ... primary site to the DP local admin group I re-pushed the Software ... For some reason I can't push any install or ... >> installed on the Distribution Point Server that needs to support Background ... >> components are installed on the local SMS Site Server, ...
    (microsoft.public.sms.swdist)
  • Re: Moving SMS2003 to another server
    ... > Can this new Site Server also have a new name or does the name has to be the ... > same as the old Site Server? ... You can find the document at the SMS 2003 Product Documentation ... The current installation is in a single ...
    (microsoft.public.sms.setup)
  • Re: New Secondary Site
    ... > server or to run it from the Primary Site server using the create secondary ... > at files on the secondary site server on the Installation Source Files ... >>> Hi Kim, ...
    (microsoft.public.sms.setup)
  • Re: New Secondary Site
    ... server or to run it from the Primary Site server using the create secondary ... at files on the secondary site server on the Installation Source Files ... >>> MVP SMS ...
    (microsoft.public.sms.setup)