This does not seem to be true for Windows XP. I have not tested this on
Windows 7, but if I had to guess I would think it is
connection-dependent. The user is asked to configure the Wireless
Connection (if applicable) in the OOBE when setting up Windows - which
occurs before a login occurs. This deserves some more investigation
with multiple wireless authentication schemes.
To the original poster:
I would investigate forcing the WPKG service to depend on the Wireless
Connection. It will not start until the service or system component
becomes available. You should be careful with what you select, because
you may run into situations that won't let WPKG start. I've only worked
with service dependencies on Windows XP, but I'm sure there's
documentation out on the net that will help you. Note that the service
depends on AFD and TCP/IP by default. That should be a start, in any case.
Justin
Kevin Keane wrote:
I believe Windows establishes the wireless connection only at login. This is
because with some types of wireless authentication (Enterprise/RADIUS-based),
the Windows user name and password actually doubles as wireless user name and
password.
-----Original Message-----
From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-
boun...@lists.wpkg.org] On Behalf Of jetsho...@o2.co.uk
Sent: Thursday, March 11, 2010 8:11 AM
To: wpkg-users@lists.wpkg.org
Subject: [wpkg-users] "The network path was not found." - Windows 7,
wireless connection.
I have Windows 7 machines which are connected only by wireless. WPKG is
set to run at startup. However, no packages are installed, instead the
Event Viewer has an error entry
WNetAddConnection2-> The network path was not found.
from WPKGService.
If I manually start the service, all is well. So I think the problem
is that WPKG is running before the wireless connection is established.
I'm not actually sure when Windows 7 establishes the wireless
connection - at startup or at login.
How can I make wpkg wait until the connection is established, then
run, rather than quitting as is currently the case? Possibly something
with the 'Execute Before' option?
-----------------------------------------------------------------------
--
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
-------------------------------------------------------------------------
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
-------------------------------------------------------------------------
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
