Re: SMS 2003 Advanced Client Not Installed or Assigned

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mark Scott [MSFT] (marksc_at_online.microsoft.com)
Date: 04/21/04

  • Next message: Charlie Chen: "Re: SMS 2003 Advanced Client Not Installed or Assigned" 
    Date: Wed, 21 Apr 2004 10:04:32 -0700

    Charlie,

    Glad you're system is working. If you are in advanced security, then adding
    the machine account is sufficient. Make sure to give it rights to "This
    container and all sub containers".

    Mark Scott [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

    "Charlie Chen" <SMS2003.10.fluteboy@spamgourmet.com> wrote in message
    news:13f501c42670$c67e38d0$a501280a@phx.gbl...
    > Okay, that was rather annoying... Chapter 15 never
    > mentions that the "System Management" container had to be
    > created in the Systems container. And, Chapter 15 says to
    > add either the SMS admin account or the SMS Site Server
    > to the permissions, but for good measure, I've added both.
    >
    > Now, it works!
    >
    >>-----Original Message-----
    >>The reason your clients are not assigning could be due
    > to the fact that you
    >>don't have your MP published in AD or your SLP is not
    > published in either AD
    >>or WINS. I'll assume you are using Active Directory
    > since you said you
    >>extended the schema. Here's is what you need to do to
    > fix the problem.
    >>
    >>1. Using ADSIEdit or other tool create the "System
    > Management" container in
    >>AD and set permissions. See Chapter 15 of the Concepts,
    > Planning and
    >>Deployment Guide on your SMS 2003 cd for details. Look
    > for "Creating SMS
    >>Containers in Active Directory".
    >>
    >>2. Once that is complete, hiearchy manager (hman.log)
    > will be able to
    >>publish the MP to AD. When this is complete, your
    > advanced clients will
    >>find their site code on install or if you push
    > the "Discover" button in the
    >>UI.
    >>
    >>I think that has answered your questions.
    >>
    >>Mark Scott [MSFT]
    >>This posting is provided "AS IS" with no warranties, and
    > confers no rights.
    >>
    >>
    >>"Charlie Chen" <SMS2003.10.fluteboy@spamgourmet.com>
    > wrote in message
    >>news:018d01c4240b$9a867600$a001280a@phx.gbl...
    >>>I have a lab of three machines, SRVDC1-SMS (DC, GC, DNS,
    >>> WINS), SRVSMS (SMS 2003), and PC1-SMS (client) in the
    >>> <i>sms.org</i> domain. All machines are registered in
    > AD,
    >>> DNS, and WINS. All machines are Discovered in SMS 2003
    >>> under All Systems. SMS\Administrator is a member of the
    >>> Domain Admins group, the latter of which is a member of
    >>> the local administrators group on all machines.
    >>>
    >>> I have set the following under Site Settings:
    >>>
    >>> . Client Installation Methods > Client Push
    >>> Installation > General > Enable Client Push
    > Installation
    >>> to assigned resources (all System types)
    >>> . Client Installation Methods > Client Push
    >>> Installation > General > Enable Client Push
    > Installation
    >>> to site systems (Advanced Client)
    >>> . Client Installation Methods > Client Push
    >>> Installation > Accounts > SMS\Administrator
    >>> . Client Installation Methods > Client Push
    >>> Installation > Advanced > SMSSITECODE=SFO (also tried
    >>> with =AUTO)
    >>> . Component Configuration > Software Distribution >
    >>> Drive on site server > C:\
    >>> . Component Configuration > Software Distribution >
    >>> Legacy Client Software Installation Account >
    >>> SMS\Administrator
    >>> . Component Configuration > Software Distribution >
    >>> Advanced Client Software Installation Account >
    >>> SMS\Administrator
    >>> . Connection Accounts > Clients > SMS\Administrator
    >>> . Site Systems > \\SRVSMS > Management Point > Use
    > this
    >>> site system as a management point
    >>> . Site Systems > \\SRVSMS > Client Access Point > Use
    >>> this site system as a client access point
    >>> . Site Systems > \\SRVSMS > Distribution Point > Use
    >>> this site system as a distribution point
    >>> . Site Systems > \\SRVSMS > Distribution Point >
    > Enable
    >>> Background Intelligent Transfer Service (BITS)
    >>>
    >>>
    >>> Even with the Enable Client Push Instillation selected,
    >>> and also by right-clicking on the computer/group and
    >>> selecting All Tasks > Install Client, the client still
    >>> does not show up under the Collections as being
    > installed
    >>> or assigned. The Site Code is obviously blank because
    > the
    >>> client has not been installed. However, opening the
    >>> C:\WINDOWS\system32\ccmsetup\ccmsetup.log says
    >>> that "Installation succeeded."
    >>>
    >>> Looking at the Control Panel, I see the Systems
    >>> Management applet present on all machines. When I open
    >>> the Systems Management applet, all the components are
    >>> installed, though it has been three days and the Client
    >>> still does not show up as installed under the SMS 2003
    >>> Collections. Looking under the Advanced tab of the
    >>> Systems Management applet, I notice that the "Currently
    >>> assigned to site code" is blank. Clicking
    > on "Discover,"
    >>> I get the error, "Automatic site code discovery was
    >>> unsuccessful." Now, once I manually enter in my Site
    > Code
    >>> of "SFO," the Client shows up in the Collections, it's
    >>> Assigned, and the Client Type is Advanced.
    >>>
    >>> This guy is having the same problem: <http://www.tek-
    >>> tips.com/gviewthread.cfm/pid/22/qid/796826>. However,
    > for
    >>> me, trying to install the Legacy Client does not work,
    >>> either. In addition, MSFT is not going to be supporting
    >>> the Legacy Client in the near future.
    >>>
    >>> When I try to run the Remote Control Agent on another
    >>> machine (though it's been installed per the Systems
    >>> Management applet), it does not work. When I use SMS
    > 2003
    >>> Toolkit 1's "Adv Client Spy," I can Connect to all
    >>> machines all see all properties. So, the problem is
    > that
    >>> although the client is installed, the Site Code is not
    >>> being pushed, and hence, the Client does not work.
    >>>
    >>> Questions:
    >>> 1) How do I get the Advanced Client Install to install
    >>> and show up under the Collections?
    >>> 2) How do I do this so that I don't have to manually
    >>> enter the Site Code locally at each Client?
    >>
    >>
    >>.
    >>

  • Next message: Charlie Chen: "Re: SMS 2003 Advanced Client Not Installed or Assigned"
    • Quantcast