On Jun 17, 2015, at 2:55 PM, Lev Veyde <lveyde(a)gmail.com> wrote:

Hi Patrick,

First of all lets clear some misunderstanding here - you don't need to manu= =3D ally install Python.

The installation of oVirt WGT is fully self contained, and while the oVirt = =3D Guest Agent it includes is indeed programmed in Python, the version include= =3D d is converted using py2exe (check py2exe.org for more detai= ls i=3D f it interests you) into a standalone executable (well, almost - just like = =3D Windows version of Python.exe, it depends on Microsoft Visual Studio CRTL, = =3D but we install it during the installation of the oVirt WGT).

Now about the automated installation. Generally we suppor= t =3D silent installation of oVirt WGT.

You just need to supply /S command parameter to the insta= ll=3D er.

However there is a catch - unfortunately Windows will pop= up=3D warning messages due to the fact that the drivers supplied are non-WHQL'd.= =3D That is because the drivers are signed by Red Hat, Inc. and not by Microso= =3D ft certificate.

This is a security feature of Windows OS itself, and ther= e =3D is not much we can do about it right now.
The side effect of this is that you need to manually approve the drivers in= =3D stallation for each driver, or choose to trust all drivers from Red Hat, In= =3D c., and then no more popups will show up. Unfortunately, you still need to = =3D do this manually at least once, and you can't pre-approve Red Hat, Inc. to make this process automated. Fo= =3D r more information on installing oVirt WGT you can check this article: http://community.redhat.com/blog/2015/05/how-to-install-and-use-ovirts-wind= =3D ows-guest-tools/ by yours truly.

There is a workaround though, and it's to create a progra= m =3D that will automatically approve such unsigned drivers dialogs. It's relativ= =3D ely easy to program with i.e. AutoIt scripting engine (check: https:= //ww=3D w.autoitscript.com/site/autoit/ ), which is free (like in free beer, bu= =3D t unfortunately not as in freedom because source code for it is not supplie= =3D d). Note that you must be quite careful with that, as by doing so you basically disabling the security mechanism t= =3D hat Microsoft had put in place for a reason, and potentially you may uninte= =3D ntionally install other non-WHQL'd drivers - if the installation attempt fo= =3D r these other drivers will be made while your auto-approver program will run.

Thanks in advance,
Lev Veyde.