Erik Langeland schrieb: > The first issue I discovered is that the Wpkg Client service, if it is set to Automatic start, would start while Group Policy software installations were still processing. I have also determined that in some cases, the service finishes before Windows enters wpkglogon.dll, which runs wpkgMessage.exe to display the dialog. If the service has already finished before the dialog displays, the dialog will not close until the timeout expires, unless the service is started a second time manually. > > My first attempt to resolve this was to change the wpkg service to Manual start and using "sc start WpkgService" in a Group Policy startup script to run the service. Although this resolves the first problem, it dos not always resolve the second. The second problem also appears to be more acute on notebook PCs, since the service finishes very quickly when the computer is off the network. It makes little sense to use both GPO (or its ability to deploy MSI packages) and WPKG for software deployment. If you use both and are not careful, you may find yourself in an endless loop - GPO installing packages, WPKG uninstalling, or the other way around. -- Tomasz Chmielewski http://wpkg.org |