On 02/19/2013 10:12 AM, Paul Griffith wrote:
> On 02/19/2013 04:49 AM, David Petterson wrote:
>> On 2013-02-18 23:14, Stefan Pendl wrote:
>>> Am 18.02.2013 19:16, schrieb David Petterson:
>>>> On 2013-02-15 16:29, Marco Gaiarin wrote:
>>>>> Mandi! Kühne Jörg HCARE-ZLM
>>>>> In chel di` si favelave...
>>>>>
>>>>>> We use the WPKG Client version 1.3.6. Since our network replacement
>>>>>> to 1GB we
>>>>>> use to have problems with our software distribution. Normally WPKG
>>>>>> works fine
>>>>>> when we kick off it manually but during restart of our hosts
>>>>>> (several) the
>>>>>> WPKG-Service (start-type: auto mode) do not working properly. Maybe
>>>>>> it has
>>>>>> something to do with our WPKG settings, see below:
>>>>>
>>>>> 1.3.6 have known trouble in this aspects, so please move to the latest
>>>>> (1.3.14) and retry.
>>>>>
>>>>> More or less, the trouble came from WPKG Client service not correctly
>>>>> depending on the network setup, so starts before the network came in.
>>>>> And fail.
>>>>>
>>>>
>>>> I have the same problem with 1.3.14. On "some" computers, WPKG Client
>>>> will start before the network causing the service to fail startup.
>>>> "WNetAddConnection2-> The network path was not found"
>>>>
>>>> A fix for this is most welcome!
>>>>
>>>>
>>>
>>> There have been some fixes posted, so you just need to search for them.
>>>
>>> One was to introduce a dependency on the network service, if I remember
>>> correctly.
>>
>> None of the "fixes" I found so far works. I have added all network
>> related services that I could find as dependants and it still wont work.
>> I am currently testing a scheduled start (on system start) that seem to
>> work.
>>
>
> Hi David,
>
> I had the same issue, and I used the setting "WPKG execution on failure"
> to solve my issue.
>
> ---snip----
> On 04/10/2012 04:06 PM, John Danks wrote:
> > I use the setting in WPKG Client called "WPKG execution on failure"
> > repeat count set to 3 seems to be enough.
> ---snip---
>
> Best Regards,
I will post this to the list, in case someone else run into this issue.
You can configure the the retry attempt in two ways.
1 - Via the GUI (1.3.14),Run the WPKG GUI Client and in the tab Misc Settings you should see
"WPKG execution on failure" with a Repeat Count field that you can set. I personally set ours to 3.
2 - via the settings.xml file, look for the tag <repeat-count-on-failure>.
Here is what mine looks like!
<repeat-count-on-failure>3</repeat-count-on-failure>
--- Here is my original posting snip - snip ----
On Tue, Apr 10, 2012 at 12:22 PM, Paul Griffith <paulg at cse.yorku.ca
<mailto:paulg at cse.yorku.ca>> wrote:
Greetings,
I am running into a startup problem with WPKG Client version
1.3.14 on Windows 7 x64. I am working on testing Win7 deployments.
I am using MDT 2010 to deploy the OS and WPKG to deploy the
applications.
I am running into a networking issue, it seem that when WPKG starts
up that the network isn't fully up yet so WPKG fails.
In the eventviewer I see the following error:
WNetAddConnections2 -> The network path was not found
If I login and run "net start wpkgservice", the installation
continues until another reboot. Is there solution to this problem?
With unattended, which I currently use to deploy WinXP, it would
keep retrying to mount/map the install share. Does WPKG have a
similar feature ?
FYI I am running Win7 within a VM, VMware Hypervisor 5
Regards,
Paul
----snip-----
Best Regards,
Paul
|
|