Hi,

we also have a windows server product which needs to be installed 
interactively. We have (click-)automated the installation process with AutoIt.
To get around the issue mentioned below, you might want to run your script in 
the context of a “real” user and load the user’s profile. CMD.exe’s “runas” 
does not let you specify the password on the command line, so it is no good for 
scripts. Maybe psexec or even a Powershell session, but I have not tried that.
As said,  an Autoit Program, run from the Jenkins slave (running as a service), 
does the trick for us.

Cheers,
Sebastian

From: [email protected] 
[mailto:[email protected]] On Behalf Of Benjamin Lau
Sent: Thursday, April 6, 2017 9:51 AM
To: Jenkins Users <[email protected]>
Subject: Re: Invoke Windows Installer in Interactive mode Through Jenkins

Bangar,

I'd suspect the problem is similar to the one described in this thread about 10 
days ago:
https://groups.google.com/forum/#!topic/jenkinsci-users/zzECJya_vDY

Is your jenkins slave running the agent as a service? Try running the agent as 
a non-service as slide suggested and see if that works for you.

Cheers,
Ben

On Thu, Apr 6, 2017 at 12:17 AM, Bangar Milind 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

We are trying to automate the deployment of a windows application in which 
Setup.exe runs a MSI.

The MSI launches in interactive mode and has fields which will be required to 
updated dynamically.

We have written a Powershell script , which works fine when running on the 
Windows app server , but doesn't  when PS is called from Jenkins using a 
Windows slave.

If anyone has an experience on the same, request some help.

Please let me know, if further information is required.,

Regards
Milind
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/208c57d1-462e-4102-94c6-e6833faf7f12%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/208c57d1-462e-4102-94c6-e6833faf7f12%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BvtdQY5-8suoTWOG43Zc7UTBkHSCwug-uHFjiuPbKZcNV_YiQ%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CA%2BvtdQY5-8suoTWOG43Zc7UTBkHSCwug-uHFjiuPbKZcNV_YiQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/F43D44A13A035247BEDF314F8ECFF2F331F95E1F%40ctd-exchange02.
For more options, visit https://groups.google.com/d/optout.

Reply via email to