cleitet / wpkg-gp

Running WPKG as a Group Policy Extension
https://github.com/cleitet/wpkg-gp/wiki
25 stars 17 forks source link

WpkgPipeClient Problems - wont work all the time #120

Open sonicnkt opened 8 years ago

sonicnkt commented 8 years ago

Hey, I create a thread on this topic on the google board as well but got no answer yet. Maybe here someone can help me :)

Im using WPKG in combination with WPKG-GP now for a while and im very happy. But i wanted a way for the user to execute WPKG while the system is running without a reboot, especially for mobile system that arent alway connected to the network at boot up time.

I searched arround and stumbled open the WpkgPileClient.exe which allows normal users to execute WPKG, looks like the perfect solution for me, especially since WPKG-GP is coded in python and i could just integrate the pipeclient code into my little application.

The app starts after the user logged in a resides in the system tray, the user can right click the icon to execute WPKG Sync, with appropriate Warnings that any application could force close and the system might reboot of course. While WPKG runs the user will be presented with a small progress bar using the percentage output of WPKG-GP.

Now on to my problem, this seems to only work once every few minutes, i couldnt determine the correct time yet. If i execute the function runClient after it successfully worked it only outputs "Initializing Wpkg-GP software installation" and stops right after that.

I looked at the code but most stuff is currently beyond me. Is there a forced delay between runs?

Thanks for any help!

PS: At the moment its only possible to run the Client with "Execute" or "Cancel", would it be possible to add a option of a dryrun or query wpkg command in the future? This way i could inform the user of what will be happening to the system before wpkg is executed? I dont want to mess with the wpkg-gp code on my own yet because i probably break more than i would accomplish :)

sonicnkt commented 8 years ago

Well i finally figured it out myself... It was a problem with my samba server and the login. for some reason the first login to the server would always work but after that it blocked the connection. Everything is working now.