Legacy Clients not upgraded

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mike (anonymous_at_discussions.microsoft.com)
Date: 05/05/04 

Date: Wed, 5 May 2004 07:43:34 -0700

Installed SMS 2003 2 weeks ago on one server. Had SMS 2
SP4 on another server, but uninstalled it and waited 4
days before installing SMS 2003 on a new W2003 server.
The original SMS 2 server is not on the network any more.
The problem is none of the pc's or servers that were on
the network when the SMS 2 server was installed are
installing the advanced client. Any servers or pc's that
were installed after SMS 2003 was installed are
installing the Advanced client. The OS's are XP SP1, W2k
Pro SP4 & Server SP4, and W2003 Server. The directories
are installed on the clients and show up as Assigned, but
not as Clients. The client.msi.log has "Error: 25001.
Setup failed due to unexpected circumstances. The error
code is 80004005." There are many Warnings on the SMS
Status Message Viewer with ID 3014: "SMS Client Manager
cannot connect to the machine "MachineName". The
operating system reported error 5: Access is denied". Any
advice is appreciated. Thanks.

Relevant Pages

  • 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: IPSEC question
    ... The important issue is to get the server working properly first without ... I hit the SBS weblog and tried their stuff. ... Microsoft network client: Digitally sign communications: ... 898060 Installing security update MS05-019 or Windows Server 2003 Service ...
    (microsoft.public.windows.server.sbs)
  • Re: Adv Client with Workgroup Computers
    ... 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 ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
    (microsoft.public.sms.setup)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)