[wpkg-users] Wifi-Only Clients & Software Deployment

[Geoff Brown]

We use 802.1x authentication.

Our computers can logon using their machine accounts (via MSCHAPv2) in Active Directory before any user logs in.


---
Geoff Brown
IT Services, SFU Surrey Campus

_______________________
Simon Fraser University Surrey
250 - 13450 102nd Avenue
Surrey, BC
V3T 0A3

> On Dec 15, 2016, at 5:41 AM, Holger Kröber <kroeber at biom.uni-freiburg.de> wrote:
> 
> Hi,
> 
> more and more clients in our environment no longer have a LAN cable plugged in regularly.
> Most of the time, they have a wifi connection. This has some side effects for software deployment with WPKG.
> WPKG is executed in the context of the system account trough Group Policy startup scripts (Active Directory), before user login.
> But this will only work, if the client already has established a connection to the LAN at this time.
> With WIFI, the connection is established after the user has logged in - this is too late :)
> 
> How do you manage this in your environment?
> Do you use tasks that run in the system context after the user has logged in and are executed as soon as the WIFI connection is established?
> How do you avoid conflicts (user tries to execute the program that you want to upgrade right in the middle of the installation process etc.).
> How do you give the user feedback about the installation process? If you install software in the system context, the user normally won´t
> see any messages because of session 0 isolation.
> 
> Thanks,
> Holger
> 
> 
> ---------------------------------
> wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
> _______________________________________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> https://lists.wpkg.org/mailman/listinfo/wpkg-users