I have a collection I used by MDT to advertise OS installations to computers. More than once in the last week, I have added a computer to the collection, but it won't refresh. I've left it sit for hours and the hourglass won't go away (yes, I've been hitting F5 to refresh). I eventually have to reboot the site server.The collection does include x86Unknown Computer and x64 Unknown Computer. I'm assuming this is the root of the problem, but I'd rather make this work than have to remove the unknown computers from the collection.

Hi,Can you check the colleval.log and see if the collection evaluator process is running. I have seen a few SP2 installations where the component for some reasons stops. Restarting the SMS_executive service solves the problem.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

Well, my system is working properly right now, but the next time it hangs, I'll check CollEval.log.

OK. It has finally happened again. I checked the colleval.log and discovered that it hadn't been updated for the last 8 hours. Using the ConfgMgr Service Manager, I discovered that 30 components that should be 'Running' are 'Starting'. Comparing time stamps in colleval.log and the Windows application event log, I believe that the components aren't successfully starting after a site backup has been run. The event log shows that the service was started successfully, but that is simply the SMS_EXECUTIVE server - right? Sitecomp.log shows that all of these components are running. I stopped the SMS_EXECUTIVE service (the components that were 'starting', were still 'starting'). I restarted the SMS_EXECUTIVE and all of the components started successfully. What might be causing my problem?

Yes I know this is an old post, just cleaning up old post. This KB should fix your problem. http://support.microsoft.com/kb/982399 http://www.enhansoft.com/