Re: Active directory discovery after SP1
From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 01/28/05
- Next message: Jeff Harbaugh [MSFT]: "Re: Initiate actions fails. again"
- Previous message: Steve: "Software Distribution Site Settings for the client are missing from WMI."
- In reply to: alfred: "Re: Active directory discovery after SP1"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 Jan 2005 10:53:37 -0800
Have you configured the permissions correctly on the AD system container?
Also can you check to verify the RPC services are running on the other
machine?
Are you in a single forest or multiple forest configuration?
-- Thanks, Jeff Harbaugh [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "alfred" <armand_dandy@hotmail.com> wrote in message news:1e1601c50519$76d85ee0$a601280a@phx.gbl... > Hello, > > All the AD discovery are running,in the adsysdis.log file > it seem that it discover 2000+ systems, the only error in > this file is : > > DsAddressToSiteNames Failed . Error: 1722~ > $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><jeu. janv. 27 > 00:28:03.423 2005 Romance Standard Time><thread=24640 > (0x6040)> > ERROR: Unable to get AD site name for system PEN525104, > DS Error=1722. Win32 Error=0~ > $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><jeu. janv. 27 > 00:28:03.423 2005 Romance Standard Time><thread=24640 > (0x6040)> > > The systems.resource.Directorylocation are not update so > i conclude that the new add container are not discovered > or are not correctly write in the DB. > > If you have an idea... > > Thanks for your support > >>-----Original Message----- >>Are you running Active Directory System Group Discovery? > If so that >>discovers user groups. >>If you want machines you need to run Active Directory > System Discovery. THis >>will return machines. >> >>-- >>Thanks, >>Jeff Harbaugh [MSFT] >>This posting is provided "AS IS" with no warranties, and > confers no rights. >> >>"Alfred" <anonymous@discussions.microsoft.com> wrote in > message >>news:14c201c50452$e6f2fa40$a601280a@phx.gbl... >>> Here is the log >>> >>> It is time to run on the schedule. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:02 14284 (0x37CC) >>> Starting the data discovery. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:02 14284 (0x37CC) >>> Number of Assigned Systems found = 2753. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:02 14284 (0x37CC) >>> Bound to AD Container >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:05 14284 (0x37CC) >>> Server name: servername.domain.fgov.be >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:05 14284 (0x37CC) >>> Searching AD Container >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:06 14284 (0x37CC) >>> Server name: servername.domain.fgov.be >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:06 14284 (0x37CC) >>> Current Status: number of systems discovered = 100 >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:00:33 14284 (0x37CC) >>> Current Status: number of systems discovered = 800 >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> 27/01/2005 0:02:57 14284 (0x37CC) >>> SMS_EXECUTIVE started > SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT >>> as thread ID 24072 (0x5E08). >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 20640 (0x50A0) >>> ** Service Thread is starting ** >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Removing redundant containers and validating them... >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> The Run Count value in the site control file is 7. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> The Schedule token value in the site control file is >>> 001818C000500008. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> !!!!Valid AD container 0: >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Current time is 27/01/2005 0:17:04 Romance Standard > Time >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Last Run time is 26/01/2005 0:17:58 Romance Standard > Time >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Next Run time is 27/01/2005 0:00:00 Romance Standard > Time >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> It is time to run on the schedule. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Starting the data discovery. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Number of Assigned Systems found = 2753. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Bound to AD Container >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Server name: servername.domain.fgov.be >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Searching AD Container >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Server name: servername.domain.fgov.be >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Current Status: number of systems discovered = 100 >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Current Status: number of systems discovered = 2500 >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Searching AD Container >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be. >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> Server name: servername.domain.fgov.be >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> AD Discovery under container >>> LDAP://OU=ADwork,DC=domain,DC=fgov,DC=be found 2596 >>> objects SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> STATMSG: ID=5503 SEV=W LEV=M SOURCE="SMS Server" >>> COMP="SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT" SYS=HORUS- > 2003 >>> SITE=CEN PID=10372 TID=24072 GMTDATE=mer. janv. 26 >>> 23:30:10.189 2005 ISTR0="2441" ISTR1="2441" ISTR2="0" >>> ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" >>> ISTR9="" NUMATTRS=0 >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> STATMSG: ID=5502 SEV=I LEV=M SOURCE="SMS Server" >>> COMP="SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT" SYS=HORUS- > 2003 >>> SITE=CEN PID=10372 TID=24072 GMTDATE=mer. janv. 26 >>> 23:30:10.189 2005 ISTR0="1" ISTR1="2596" ISTR2="2596" >>> ISTR3="0" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" >>> ISTR9="" NUMATTRS=0 >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> *** Shutting Down ************************ >>> SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1/01/1601 >>> 0:00:00 24072 (0x5E08) >>> >>>>-----Original Message----- >>>>Can you attach the log file? >>>> >>>>-- >>>>Thanks, >>>>Jeff Harbaugh [MSFT] >>>>This posting is provided "AS IS" with no warranties, > and >>> confers no rights. >>>> >>>>"Alfred" <armand_dandy@hotmail.com> wrote in message >>>>news:249c01c503b9$deddad30$a501280a@phx.gbl... >>>>> Hello, >>>>> >>>>> My active dicovery method don't discover any machines >>> or >>>>> containers add in the AD after the up to sms sp1. >>>>> >>>>> In SMS log for AD discovery there is no error > messages. >>>>> >>>>> My AD discovery use custom ldap at the root of my AD >>>>> and i check the recursive and include groups > checkbox. >>>>> >>>>> Can you help me? >>>>> >>>>> >>>>> >>>> >>>> >>>>. >>>> >> >> >>. >>
- Next message: Jeff Harbaugh [MSFT]: "Re: Initiate actions fails. again"
- Previous message: Steve: "Software Distribution Site Settings for the client are missing from WMI."
- In reply to: alfred: "Re: Active directory discovery after SP1"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
