5:30 p.m.
--_000_D966748B4F044F819D8B48A958681BB6volusioncom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Thank you Lev for the clarification. We had been installing manually via th=
e ISO, but I had mis-read some other articles about using python to automat=
e the process.
I will pass on the notes around /S and your article to our internal windows=
team. Maybe they have some ideas around the cert store, or at the very lea=
st pass off the manual instructions to our NOC.
I appreciate the response,
Patrick
On Jun 17, 2015, at 2:55 PM, Lev Veyde <lveyde@gmail.com<mailto:lveyde@gmai=
l.com>> wrote:
Hi Patrick,
First of all lets clear some misunderstanding here - you don't need to manu=
ally install Python.
The installation of oVirt WGT is fully self contained, and while the oVirt =
Guest Agent it includes is indeed programmed in Python, the version include=
d is converted using py2exe (check py2exe.org<http://py2exe.org/> for more =
details if it interests you) into a standalone executable (well, almost - j=
ust like Windows version of Python.exe, it depends on Microsoft Visual Stud=
io CRTL, but we install it during the installation of the oVirt WGT).
Now about the automated installation. Generally we support silent installat=
ion of oVirt WGT.
You just need to supply /S command parameter to the installer.
However there is a catch - unfortunately Windows will popup warning message=
s due to the fact that the drivers supplied are non-WHQL'd. That is because=
the drivers are signed by Red Hat, Inc. and not by Microsoft certificate.
This is a security feature of Windows OS itself, and there is not much we c=
an do about it right now.
The side effect of this is that you need to manually approve the drivers in=
stallation for each driver, or choose to trust all drivers from Red Hat, In=
c., and then no more popups will show up. Unfortunately, you still need to =
do this manually at least once, and you can't pre-approve Red Hat, Inc. to =
make this process automated. For more information on installing oVirt WGT y=
ou can check this article: http://community.redhat.com/blog/2015/05/how-to-=
install-and-use-ovirts-windows-guest-tools/ by yours truly.
There is a workaround though, and it's to create a program that will automa=
tically approve such unsigned drivers dialogs. It's relatively easy to prog=
ram with i.e. AutoIt scripting engine (check: https://www.autoitscript.com/=
site/autoit/ ), which is free (like in free beer, but unfortunately not as =
in freedom because source code for it is not supplied). Note that you must =
be quite careful with that, as by doing so you basically disabling the secu=
rity mechanism that Microsoft had put in place for a reason, and potentiall=
y you may unintentionally install other non-WHQL'd drivers - if the install=
ation attempt for these other drivers will be made while your auto-approver=
program will run.
Thanks in advance,
Lev Veyde.
--_000_D966748B4F044F819D8B48A958681BB6volusioncom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <9A57CAB2415424468673D216BEA8E33D(a)namprd04.prod.outlook.com Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
</head <body
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"" Thank you
Lev for the clarification. We had been installing manually via th=
e ISO, but I had mis-read some other articles about using python to automat=
e the process.
<div class=3D""><br class=3D""
</div <div class=3D"">I
will pass on the notes around /S and your article to our =
internal windows team. Maybe they have some ideas around the cert store, or=
at the very least pass off the manual instructions to our NOC. </div <div class=3D""><br class=3D"" </div <div
class=3D"">I appreciate the response, </div <div class=3D"">Patrick</div <div class=3D""><br class=3D"" <div <blockquote
type=3D"cite" class=3D"" <div
class=3D"">On Jun 17, 2015, at 2:55 PM, Lev Veyde <<a
href=3D"mailt=
o:lveyde@gmail.com" class=3D"">lveyde(a)gmail.com</a>&gt;
wrote:</div <br
class=3D"Apple-interchange-newline" <div
class=3D"" <div dir=3D"ltr"
class=3D"" <div class=3D"" <div class=3D"">Hi Patrick,<br
class=3D"" <br class=3D"" </div First of
all lets clear some misunderstanding here - you don't need to manu=
ally install Python.<br class=3D""
</div The installation of oVirt WGT is
fully self contained, and while the oVirt =
Guest Agent it includes is indeed programmed in Python, the version include=
d is converted using py2exe (check
<a href=3D"http://py2exe.org/" class=3D"">py2exe.org</a>
for more details i=
f it interests you) into a standalone executable (well, almost - just like =
Windows version of Python.exe, it depends on Microsoft Visual Studio CRTL, =
but we install it during the installation
of the oVirt WGT).<br class=3D"" <div
class=3D"" <div class=3D"" <div class=3D""><br class=3D"" </div <div
class=3D"">Now about the automated installation. Generally we support =
silent installation of oVirt WGT.<br class=3D""
</div <div class=3D"">You
just need to supply /S command parameter to the install=
er.<br class=3D"" </div <div class=3D"">However there is a catch -
unfortunately Windows will popup=
warning messages due to the fact that the drivers supplied are non-WHQL'd.=
That is because the drivers are signed by Red Hat, Inc. and not by Microso=
ft certificate.<br class=3D"" <br
class=3D"" </div <div class=3D"">This is a security feature of
Windows OS itself, and there =
is not much we can do about it right now.<br class=3D"" The side effect of this is that you need to manually approve
the drivers in=
stallation for each driver, or choose to trust all drivers from Red Hat, In=
c., and then no more popups will show up. Unfortunately, you still need to =
do this manually at least once,
and you can't pre-approve Red Hat, Inc. to make this process automated. Fo=
r more information on installing oVirt WGT you can check this article:
<a href=3D"http://community.redhat.com/blog/2015/05/how-to-install-and-...
ovirts-windows-guest-tools/" class=3D""
http://community.redhat.com/blog/2015/05/how-to-install-and-use-ovirts-wind=
ows-guest-tools/</a> by yours truly.<br class=3D"" <br class=3D""
</div <div
class=3D"">There is a workaround though, and it's to create a program =
that will automatically approve such unsigned drivers dialogs. It's relativ=
ely easy to program with i.e. AutoIt scripting engine (check:
<a href=3D"https://www.autoitscript.com/site/autoit/"
class=3D"">https://ww=
w.autoitscript.com/site/autoit/</a> ), which is free (like in free beer, bu=
t unfortunately not as in freedom because source code for it is not supplie=
d). Note that you must be quite careful
with that, as by doing so you basically disabling the security mechanism t=
hat Microsoft had put in place for a reason, and potentially you may uninte=
ntionally install other non-WHQL'd drivers - if the installation attempt fo=
r these other drivers will be made
while your auto-approver program will run.<br class=3D"" </div <div
class=3D""><br clear=3D"all" class=3D"" <div class=3D"" <div
class=3D"" <div
class=3D"gmail_signature" <div
dir=3D"ltr" class=3D"">Thanks in advance,<br
class=3D"" Lev Veyde.<br
class=3D"" </div </div
</div </div </div
</div </div </div
</div </blockquote </div <br
class=3D"" </div </body
</html
--_000_D966748B4F044F819D8B48A958681BB6volusioncom_--