Hi There, I'm new in this sccm. At the moment, this is my configuration: - windows server 2008 sp2 x64 (updated) - ms sql server 2008 standard sp1 - sccm 2007 r2 - iis7 - set up as a secondary DC with DNS - a group policy is in place that points the client (including DCs) to the currently active WSUS on another server At the moment I'm having 2 problems (not sure if they're connected): # smsexec.exe will clog the machine and usually takes 99% of CPU so it pretty much renders it useless # when I check the sccm status here: System Status > Site Status > my_site ... under Component Status There are warning (and the related error message) for: SMS_CI_ASSIGNMENT_MANAGER Type: Milestone Message ID: 5804 Process ID: 2220 Thread ID: 260 Description: SMS CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. SMS_COLLECTION_EVALUATOR Type: Milestone Message ID: 2521 Process ID: 2220 Thread ID: 3812 Description: SMS Collection Evaluator failed to retrieve collection "SMS000HS" from the collection source. (On primary sites, the collection source is the SMS site database. On secondary sites, it is \Sms\inboxes\colleval.box.) Possible cause on primary sites: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause on secondary sites: The file in \Sms\inboxes\colleval.box is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. under Site System Status The following roles have critical status with Availability column listed as failed: ConfigMgr management point ConfigMgrsoftware update point ConfigMgr SQL server (Database) ConfigMgr SQL server (Transaction Log) Maybe they're all caused by the Component Status issue above? I'm following this guide in setting up sccm: http://www.windows-noob.com/forums/index.php?/topic/489-how-can-i-configure-sccm-2007-sp1-in-windows-server-2008/ I also followed the other component configuration from that link as well (WSUS, IIS, SQL, etc) If this is SQL server issue, how do I fix it? (again, not much experience with SQL server) I really appreciate your help! also, let me know if I'm posting to the wrong place.

Have you added the computer account of the secondary site to the local admins on the SQL box? Any failed logins (SQL management studio: SQL Server logs)? Firewall on the SQL server?

Hi,Check out following:http://technet.microsoft.com/en-us/library/bb693554.aspxHTH.Jie-Feng Ren - MSFT

eirik, If this is what you're asking: http://www.windows-noob.com/forums/uploads/monthly_08_2008/post-1-1219338502.jpg the user account is in AD. Also, since the server is an AD, I can't really have a local account, right? These are the services + user account used: format: Startup_type - service_name - DOMAIN\logon_account Automatic - SQL Server Integration Services 10.0 - MEDOTO\barryv Manual - SQL Full-text Filter Daemon Launcher - NT AUTHORITY\LOCAL SERVICE Automatic - SQL Server - MEDOTO\barryv Automatic - SQL Server Analysis Services - MEDOTO\barryv Automatic - SQL Server Reporting Services - MEDOTO\barryv Disabled - SQL Server Browser - NT AUTHORITY\LOCAL SERVICE Manual - SQL Server Agent - MEDOTO\barryv

Sorry everyone, I found the solution some time ago but forgot to update this one. I applied this hotfix from MS. http://support.microsoft.com/default.aspx?kbid=973065 the reason why the SQL server didn't communicate well is due to the high CPU usage.