techy32 Posted April 27, 2013 Posted April 27, 2013 (edited) We have recently installed new SCCM 2012 with SQL 2012. After installing SCCM 2012 successfully it discovered only 40 machines instantly and all the users( 2505 ) in AD. We are unable to discover any other machine since the first discovery ( 40 PCs only ). All discovery methods are enabled. Anybody has the same issue or already resolved it before. We have also checked the system discovery logs. Please help to resolve the issue. Edited April 27, 2013 by techy32
FN-GM Posted April 27, 2013 Posted April 27, 2013 (edited) Why are you using all methods? Do you need them all? Ideally just turn on AD discovery. Select the OU you want to discover and all is good to go. In Devices on a discovered machine, right click one and properties, what method was used to discover it? How have you setup you boundaries and boundary groups? How long have you left it to discover? Edited April 27, 2013 by FN-GM
synaesthesia Posted April 27, 2013 Posted April 27, 2013 As above, you should only really enable AD discovery. Benefit to that is that it only picks up machines you want it to so it can be limited to certain OUs or AD sites. Install everything and you'll end up with performance issues with it polling just about every part of your network every (however often you've set it). Especially heartbeat discovery, although that requires the client to be already installed. Have you clicked "run discovery now" and left it for half hour or so?
techy32 Posted April 27, 2013 Author Posted April 27, 2013 We enable system discovery initially but unable to discover machines so had to enabled all methods. We have setup boundaries correctly. its been few weeks now.............and still waiting..... all the services in SCCM 2012 are also running ..........
synaesthesia Posted April 27, 2013 Posted April 27, 2013 weeks? Checked relevant firewall permissions on the server & clients respectively?
free780 Posted April 27, 2013 Posted April 27, 2013 Have you given the account used for ad system discovery read access to the ou's?
FN-GM Posted April 27, 2013 Posted April 27, 2013 We enable system discovery initially but unable to discover machines so had to enabled all methods. We have setup boundaries correctly. its been few weeks now.............and still waiting..... all the services in SCCM 2012 are also running .......... I really dont know how you can expect us to help without giving us more information. Please can you answer my questions above?
techy32 Posted April 27, 2013 Author Posted April 27, 2013 We are using domain Administrator account, which have full permission to AD?
techy32 Posted April 27, 2013 Author Posted April 27, 2013 I really dont know how you can expect us to help without giving us more information. Please can you answer my questions above? I will remote in to find out the answers of your questions. I will post the answers later today/tomorrow.
FN-GM Posted April 27, 2013 Posted April 27, 2013 We are using domain Administrator account, which have full permission to AD? Thats not advised. You need an account that has read only rights. A standard Domain User will do the trick. I will remote in to find out the answers of your questions. I will post the answers later today/tomorrow. Thanks
techy32 Posted April 27, 2013 Author Posted April 27, 2013 Once all my PCs are discovered I will setup a standard domain user for this purpose which is always the best. Thank for pointing out..
techy32 Posted April 30, 2013 Author Posted April 30, 2013 In Devices on a discovered machine, right click one and properties, what method was used to discover it? Agent Name: SMS_AD_SYSTEM_DISCOVERY_AGENT All I checked are discovered with above discovery method How have you setup you boundaries and boundary groups? Desktop Range ip subnet 172.16.0.0 ( which is our internal IP range )
Gatt Posted April 30, 2013 Posted April 30, 2013 Boundaries and Boundary Groups are vital in SCCM 2012 - without them yo will get a lot of unexpected results!
techy32 Posted April 30, 2013 Author Posted April 30, 2013 (edited) @Gatt SCCM 2007 /2012 guru (sort of) Like it.... What's the best way of setting up boundaries and boundary groups. Edited April 30, 2013 by techy32
Gatt Posted April 30, 2013 Posted April 30, 2013 In SCCM 2012 Console - Goto Administration -> Overview -> Hierarchy -> Boundaries.. Create a new Boundary (I use my AD Site (EG DEFAULT-SITE-NAME) Then, In Administration -> Overview -> Hierarchy -> Boundary Groups .. Create a New Group (EG "My Boundary Group") and and your Boundary or Boundaries to it
free780 Posted April 30, 2013 Posted April 30, 2013 http://channel9.msdn.com/Events/MMS/2013/UD-B304 A boundary group defines the mp and dp for the client. Sccm is used in huge organizations with multiple sites and subnets.
Gatt Posted April 30, 2013 Posted April 30, 2013 @Gatt SCCM 2007 /2012 guru (sort of) Like it.... Sorry missed this last time! Keep meaning to do my MS exams for 2007 and 2012.. Just need some kind person to come up with a nice badge for my name here ;-)
techy32 Posted May 18, 2013 Author Posted May 18, 2013 I have noticed that any new machine which we are building and joining the domain, SCCM is picking them. We currently have 43 machines in SCCM which initially was 38. Our total no is about 500. Any thoughts on it? I am not sure if I have mentioned that we are using SCCM & SQL version 2012? Is there any issue with SQL 2012?
techy32 Posted June 3, 2013 Author Posted June 3, 2013 And after half term, I noticed that there are 73 machines in SCCM as we have reimage one ICT Room and all rebuild machines are in SCCM which were not there before.................... Strange problem.................. Any SCCM 2012/SQL Server 2012 Guru can shed some light on it??????
synaesthesia Posted June 3, 2013 Posted June 3, 2013 Discovery schedule set too long? Initial discovery never took place?
techy32 Posted June 3, 2013 Author Posted June 3, 2013 Resolveddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 600 machines in SCCM!!!!!!!!!!!!!!!!!!!!!!!!!!! Thank you @synaesthesia I have disabled the Active directory system discovery option Only discover computers that have updated their computer account password in a given period of time ( which was 90 days ) We have disabled the policy on the domain due a software installed on our network.............................. Thank you very much to all who suggested different options...........especially @synaesthesia............you are a starrrrrrrrrrrrrrrrrrrrrrrrrrr................. Thank you very much......................
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now