This is gradually evolving into a Windows SCCM blog but there's a bit of "me stuff" in here too as I like to write so have a look at some of my work. I've had a problem with the old girl recently - our SCCM 2007 environment had been chugging along nicely until a few weeks ago. 500 collections with update schedules running pretty evenly throughout the day.
I've checked my boundaries, DP settings, web server configs, as well as my client & server logs but am not positive what I should be looking for specifically.
These are the ramblings of a 30 something (going on 60) year old disgruntled IT Professional.
Which I could update to and see if its sorted, but they do specify many issues can carry accross in the upgrade so it's best to get them sorted first. Now the hourglass just wont go away, have had it there for over a week. SCCM has a habit of doing some decent logging, what about the log files on the server and viewing them with cmtrace when you try and add to a collection i've troubleshot several problems with the existing sccm at work and have used the logfiles many times to work out whats going on (or what was not) hasn't been any changes to account rights on sccm itself, or any of the service / network accounts your system uses?
I went to google it yesterday and came across the fact there's a new SCCM version (current branch). So I'm doing this and they are not moving and the hourglass appears.
“But Problem Resolution guy surely this is a new feature offered by Microsoft and they want us to use it, what harm could it possibly cause? Well, it depends on your environment and if you’ve adhered to Microsoft best practices.