My responses are inline: </snip> > It's _may_ be a known bug in WPKG Client which affects some setups - the > service starts too early and it can't connect to the network, although > technically, the network should be already up. Hmmm. I changed the startup type from the default Automatic start to Automatic(Delayed Start) to see if that will address the network delay problem. No, it does not. However, I tested it multiple times and the WPKG service did start long after the network was available, when Automatic(Delayed Start) was enabled. So, I am unsure if it is the network delay for my instance. To take this one step further, I did the following: In my settings.xml file - http://pastebin.com/d7b8b28a7 - my pre-action is to map a network share to X: and post-action is to tear down this network share after WPKG is done with its business. I modified my settings.xml file to perform pre-action and removed post-action. Well, I rebooted the machine. WPKG was set to do a delayed start, which it did successfully, but nothing further. It did not execute the pre-action process of mapping a network share to X: There are no error logs entries in the Event viewer either. > Did you check the event log to see why it fails? I did, it _does_not_ fail. It successfully is initialized, but isn't doing anything after. Here is what I found in chronological order in the Event Viewer: - WPKG Service trying start... - WPKG Service->RegisterServiceCtrlHandler: successfuly done - WPKG Service->SERVICE_START_PENDING: successfuly done - ServiceStart - Set script security context: successfuly done. |