Sms client push install fails error 1726

From: Antoine Desy (antoinedesy_at_hotmail.com)
Date: 12/13/04

  • Next message: Jeff Harbaugh [MSFT]: "Re: Sms client push install fails error 1726" 
    Date: Mon, 13 Dec 2004 11:05:01 -0800

    Hi,
    I have a couple client stations thare aren't able to install the client via
    the SMS admin console.
    You'll see in the following logs that the error message : "Unable to connect
    to
    remote registry for machine name "MACHINE", error 1726. On this particular
    machine, the OS is NT4/Sp6 with IE6. So the "remote registry" service can't
    be enabled/disabled via the services.
    I'm abble to install the legacy client manually on this station.

    Thanks for helping!
    Antoine Desy

    ======>Begin Processing request: "VW96ZMKY", machine name: "B15154"
    ---> Trying the 'best-shot' account which worked for previous CCRs (index =
    0x0)
    ---> Attempting to connect to administrative share '\\B15154\admin$' using
    account 'hl\adminaccnt'
    ---> The 'best-shot' account has now succeeded 86 times and failed 59 times.
    ---> Connected to administrative share on machine B15154 using account
    'hl\adminaccnt'
    ---> ERROR: Unable to connect to remote registry for machine name "B15154",
    error 1726.
    ---> ERROR: Unable to access target machine for request: "VW96ZMKY", machine
    name: "B15154", error code: 1726
    STATMSG: ID=3014 SEV=W LEV=M SOURCE="SMS Server"
    COMP="SMS_CLIENT_CONFIG_MANAGER" SYS=HASSIUM SITE=HL1 PID=2420 TID=1860
    GMTDATE=Mon Dec 13 14:58:22.692 2004 ISTR0="B15154" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    Retry request id for "VW96ZMKY" set to "B15154.HL"
    Stored request "B15154.HL", machine name "B15154", in queue "Retry".
    <======End request: "B15154.HL", machine name: "B15154".

  • Next message: Jeff Harbaugh [MSFT]: "Re: Sms client push install fails error 1726"

    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)
    • RE: sbsb2003 premium and ISA
      ... another account. ... Run setup - install on IIS is generally the only selection available. ... Accept the client installation for the SBS (installs the Officescan ... settings for the server versus the clients. ...
      (microsoft.public.windows.server.sbs)
    • Re: Advanced client
      ... you're probably having a permissions problem. ... before even thinking of push install, you have to set up a Client ... Installation account and it has to be a local admin on the client so it ...
      (microsoft.public.sms.admin)