So after watching a machine provision, I realized something strange. Here's a generic timeline:
1:05PM - Provisioning says that Adobe Reader Software Distribution starts (but the log file we have it create doesn't exist)
1:25PM - Log file shows up and Adobe Reader is acutally installed.
1:26PM - According to the log file Adobe Reader installed successfully - Provisioning still shows the task active.
1:41PM - Provisioning finally shows the task successful and moves to the next.
After the task begins, CPU Usage on the machine is 0% until the log file shows up so it's obviously not doing anything. The same is true from the time the install finished until provisioning says the task was successful. This isn't just with the Adobe Reader install. This happens with most of the software distribution pacakges in the provisioning template.
So, what would cause provisioning to just sit there for so long without running the software distribution tasks?