I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
Vast quantity of our Secondary site servers reported SMS_OUTBOX_MONITOR and SMS_INBOX_MONITOR components have gone critical, but there are no status messages.
Quick look at the inbox\outbox logs, shows -2700 for the next polling cycle.
Waiting until the next polling cycle in -2700 seconds from now.
You can restart the components or restart the SMS_EXECUTIVE to fix this.
It seems to be due to DST (timezone) changes. We rolled out http://support.microsoft.com/kb/959257 to our Primary site servers last week, assume this is why the primary site servers are not complaining as the secondaries are.
See this thread on myITforum for more info, it helped us!
Good info Rob.
And for those still running SMS 2003, I blogged about GMT/BST time changes back in October.
wmug.co.uk/.../alert-bst-to-coordinated-universal-time-gmt-change.aspx
Looks like the hit counter went right up on this posting this morning, guess lot of folk saw this again today (30-03-2009) as we switched in to BST ;-) I did :-(
Update: There is a KB telling you to restart SMS_EXECUTIVE here: support.microsoft.com/.../972400
But more importantly, ConfigMgr 2007 SP2 has a fix included for this.
We have another timechange taking place soon in Europe, we will have to see if SP2 stops the problem manifesting