Re: sms deployment basic questions

Tech-Archive recommends: Speed Up your PC by fixing your registry

ok, I have no idea what happened but for whatever reason when I checked it
this morning all the machines I put in the "all systems" appeared, I guess it
took overnight for it to fully refresh?? this is really cool.

Now I right clicked and did a "install client" I did the advanced client
since these are windows xp machines and as of right now there is nothing
installed on them. where can I go to check to see the status of the client
install? How long does it usually take to install on a local network with a
gigabit connection?



"Kim Oppalfens" wrote:

>
> Seems like you have ad discovery configured correctly now.
> Are the machines that do not show up registered in dns?
>
> On the site server open a dos box and execute the following
> nslookup
> then type in the name of one of the clients that is missing
>
> Does this return the ip address of the client?
>
> Kim Oppalfens
> MVP SMS
>
> In article <25F9DB2E-5103-4899-B57E-8F045D743DA2@xxxxxxxxxxxxx>,
> bpin@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > 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
>
.

Relevant Pages

  • Re: sms deployment basic questions
    ... started on all the machines but only one showed up under the "all systems" ... I haven't tried to install ... > In your discovery methods, ... >> client it was telling me it couldn't access some container, ...
    (microsoft.public.sms.admin)
  • 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: 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)