Re: sms deployment basic questions

ok, I did as you said, I added machines via the AD containers and out of 5
machines I have 1 that showed up. I saw that the "ccmsetup" service was
started on all the machines but only one showed up under the "all systems"
collection. I took a look at the log file and here is an excerpt that leads
me to believe something is working ok.

Central Daylight Time><thread=1912 (0x778)>
Server name: MYDOMAINCONTROLLER.MYDOMAIN.net
$$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Jun 28 10:01:25.501 2005 Central
Daylight Time><thread=1912 (0x778)>
AD Discovery under container LDAP://CN=Computer
Name,CN=COMPUTERS,DC=MYDOMAIN,DC=NET found 1 objects
$$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Jun 28 10:01:25.642 2005 Central
Daylight Time><thread=1912 (0x778)>
STATMSG: ID=5202 SEV=I LEV=M SOURCE="SMS Server"
COMP="SMS_AD_SYSTEM_DISCOVERY_AGENT" SYS=MYSMSSERVER SITE=001 PID=320
TID=1912 GMTDATE=Tue Jun 28 15:01:25.735 2005 ISTR0="6" ISTR1="6" ISTR2="6"
ISTR3="0" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
$$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Jun 28 10:01:25.735 2005 Central
Daylight Time><thread=1912 (0x778)>
*** Shutting Down ************************~
$$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Jun 28 10:01:25.735 2005 Central
Daylight Time><thread=1912 (0x778)>

This is farther than where I have gotten so thank you! do you see anything
that I am doing wrong or somewhere I should look? I haven't tried to install
the sms client yet but I'm more concerned about the other ones not showing up
at this point.

"Kim Oppalfens" wrote:

>
> Ok, Lets take this one step at a time.
> First thing to get you going is make sure we have at least one
> "computer" discovery method working.
>
> In your discovery methods, check Active Directory system discovery.
> Do you have a target container configured?
> If not Click the Yellow star, and select whether you want to discovery
> all machines in the entire forest, entire domain, or a specific
> Organizational unit.
>
> Next on the schedule tab, configure a schedule, and select the checkbox
> to run ASAP.
>
> Be patient for 10 minutes, then go to the All Systems collection, right-
> click it, select all tasks update collection membership.
>
> Press F5, you should now see some systems in the all systems collection.
> If not verify the Adsysdis.log on the server.
> --
> Kim Oppalfens
> MVP SMS
> Computacenter Belgium
>
> In article <05D09A6E-DCE0-486E-B19A-1C436CA9796F@xxxxxxxxxxxxx>,
> bpin@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > "Ok, what discovery method do you use, and how do you have it configured?
> > I am guessing you are using the "windows user group" & "windows user
> > discovery" method.
> > You state that you don't want to use AD because you don't have
> > permissions to modify AD, for discovery purposes you only need read
> > rights to AD (Which by default any ordinary user has). So you might want
> > to rethink using AD anyway for discovery. "
> >
> > Hi Kim, thanks for responding. in my Discovery Methods, I have them all
> > enabled just to see if I could get anything to show up, the only collections
> > that I get are "all user groups" and "all users".
> >
> > I was under the impression for me to use Active Directory to install the
> > client it was telling me it couldn't access some container, I reinstalled sms
> > on my server so I lost that log in the process.
> >
> > "Do you see anything in the All systems collection?
> > If so, you should be able to right-click a client in there and under the
> > all tasks option you should find the install client option. (Make sure
> > you have configured a client push installation account that has local
> > admin privileges on these clients)"
> >
> > in the "all systems" collection, the only thing that i see is my sms server.
> > the local admin privliges have been set but I don't see any clients just my
> > server and thats it. the only place where I see anything else is in the "all
> > users" and its just the user's login, nothing with the machine name.
> >
> > "You can create collections based on ip ranges and then push the client
> > to that collection only. (Pushing to users is not an option without some
> > tweaking)."
> >
> > I created a collection by essentially modifying the queries that list the
> > users and searching for a specific user, this of course has been unsuccessful
> > at installing or doing pretty much anything on this. How do I select
> > machines based on an ip range, is this in the membership rules?
> >
> > "Run capinst.exe /advcli should perform the installation of the advanced
> > client on a machine."
> >
> > I installed the client via \sms\client\i386 and installed the advanced
> > client via the msi, it told me it was installed correctly however, when I go
> > to the control panel it cannot find the sms server, when I tell it to update
> > the site code via the sms control panel it fails and gives me an error
> > "automatic site code discovery was unsuccessful", I installed again on a new
> > machine the way you stated and it didn't seem to do anything and as far as I
> > can tell nothing was installed.
> >
> > "Ok, next steps would be to check your site boundary configuration, and
> > verify in the all systems collection whether your systems show up as
> > assigned."
>
>
.

Relevant Pages

  • Re: sms deployment basic questions
    ... for discovery purposes you only need read ... I was under the impression for me to use Active Directory to install the ... "Do you see anything in the All systems collection? ... you should be able to right-click a client in there and under the ...
    (microsoft.public.sms.admin)
  • Re: sms deployment basic questions
    ... this morning all the machines I put in the "all systems" appeared, ... Now I right clicked and did a "install client" I did the advanced client ... >>> In your discovery methods, ...
    (microsoft.public.sms.admin)
  • Re: XP clients do not appear in Collections
    ... So your XP machines are or are not being discovered? ... installation methods have NOT been enabled. ... Very soon after enabling the discovery methods, ... >>> have any site listed or indicate the client has installed. ...
    (microsoft.public.sms.admin)
  • Re: SMS Admin Issues
    ... > information can be sent back to the SMS site server. ... The report indicated that 82 machines were missing SP2. ... > installation delay is occur (i.e., ... > "Active Directory System Group Discovery" this discovery can detect the OU ...
    (microsoft.public.sms.admin)
  • Re: Client Agent Push
    ... If they are not assigned the client will not push to those machines. ... MP and SLP on the primary server and also I have ... heartbeat discovery scheduled to run every 2 hours ...
    (microsoft.public.sms.admin)