I come from Singapore but find myself now living and working in the Netherlands, specialising in SMS 2003 / Configmgr 2007. I enjoy working and connecting people with computers and I hope I can share as much information as I can here through this blog.
“Computers do not just work like that, at the press of a button. From the moment a computer is switched on in your office, magic happens. That’s why you need an IT department and they do more than crawling under your desk to plug in that wire you kicked out.”
Imagine the scenario where you find yourself waiting longer then usual for a package to reach a Distribution Point. You have tried a refresh, a removal and every other possible action within the Configmgr Console GUI. Yet, the package never reaches and remains in the "Install Pending" state. Here are 3 nifty logs found in the SMS installation path that will help save you some drops of blood and empower you to find out the problem fast.
DESPOOL.LOG DISTMGR.LOGSCHEDULE.LOGIf you see the following entry in the DESPOOL.LOG, the following steps may be able to address your problem.
Received package AAA9999A version 4 SMS_DESPOOLER 9/15/2010 10:11:46 AM 6024 (0x1788)There is already a newer version of the compressed package for package AAA9999A, discard this one. SMS_DESPOOLER 9/15/2010 10:11:46 AM 6024 (0x1788)
However, when you look at the path and also in the package status, you see that it is not there, and still pending. The above message effectively tells Configmgr there is no need to send the package down since there is a newer one. But this is not true, therefore here is a quick work-around.
It's time to put aside the GUI and go straight to the raw locations of these packages and IDs. It is important to note that prior to attempting this steps, please ensure that the packages are not distributed to the affected distribution point by verifying for example through the GUI.
If you have any thoughts and comments, please feel free to share with me, as always!