http://bugzilla.wpkg.org/show_bug.cgi?id=172
--- Comment #8 from Jason Oster <parasy...@gmail.com> 2009-12-02 21:27:45 --- That's correct. The service starts, launches cscript, and begins updating all installed packages. It also spews all of its success messages to the Event Log. :) Just that [on some of these computers] it doesn't get this far during Windows' startup. The majority of computers work as they should; all are configured the same way, with Unattended ( http://unattended.sf.net/ ). The only tangible difference is where they are on the network. I was hoping there is a specific service that I can mark as a dependency to delay the WPKG service startup. Forcing it to start after the group policy is applied and/or the Domain startup scripts completed would either 1) workaround the issue, or 2) prove there is a coding error in the service causing it to believe the network is unavailable when it actually is. Unfortunately, this is very difficult to debug due to the process running so early in Windows' startup. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
