Deployment help

[ginger9991]

Hi Guys,

I have created a deployment package for a piece of software with a list of steps. Now this seems to run fine when i run it locally but when i use a deployment product (LANDesk) i get an issue where it will launch the correct installer but because the window isnt "active" or "live" it wont progress. If i click on the window attached "issue" the program will then run through and work as planned.

So basically i need to make this window active. This is the start of my command, Im a complete newb so any help would be really appreciated. Its seems like the winwaitactive command isnt working but when i run it locally its fine. Thanks in advance.

Run ("msiexec /i SystmOne.msi")
winwaitactive ("[CLASS:MsiDialogCloseClass]")
Send ("!n")
Sleep (2000)
Send ("{tab}")
Send ("{tab}")
Send ("{tab}")

[JohnOne]

Run ("msiexec /i SystmOne.msi")
WinWait ("[CLASS:MsiDialogCloseClass]")
WinActivate ("[CLASS:MsiDialogCloseClass]")

 

[Radiance]

I'm assuming you're in a corporate environment.

Deploying software with LANDesk should always be made in the background.

If you make random windows appear while the user is working, he will most likely interfere with your setup routines by closing the window or else.

For almost every good software there's an option for a "silent install" which runs completely invisible and saves yourself a lot of window-management work.

[water]

A quick Google search led me to this site describing how to silently install the software:

http://www.bundlecommander.com/index.php/blog/48-carefusion-systmone

 

[ginger9991]

Hi Radiance,

Yep your 100% correct, however the package isnt deploying, it runs and sits there so running as the client account gives me a bit of insite into what the program is doing and where its getting stuck. The software does has a silent install however we require the software install to be customized and do several different steps after.

 

Hi Water - I found that article however, i want to find out why its happening as i have several pacakge to create after this that has no silent install so i might as well figure it out now rather then leave it with next weeks problems

[water]

I assume LANDesk is running as a service in the background. Is the service enabled to interact with the desktop?

[ginger9991]

Water- Yes, I have also specified it to run with my admin account and have the same issue when deployed with Landesk. Run locally it is fine.

[water]

Isn't it possible to use the Control* functions instead of Send etc?
 

[ginger9991]

I have to be honest i have not tried control. by looking at a few other bits online im guessing it will be controlsend Send ("!n") instead of how i have it listed above?

[water]

What does Send ("!n") do?

[ginger9991]

!n is the n key. Basically clicking next.

[water]

You would need to run the AutoIt Window Info Tool and grab the ControlId of the "next" button.
Then use

ControlClick("TPP SystmOne Setup", "", Control-ID as retrieved by the AutoIt Window Info Tool)

 

[ginger9991]

Hi Water, I have just done that and tested it local and it works but again through LANDesk it doesnt seem to. Im wondering if its not kicking off the MSI. If i run the job locally i can see 3 MSIEXEC services kick off. When running through LANDesk i can only see 1 start. I have added the file path in but i dont seem to be making any progress.  Thanks for your help with this.

FileChangeDir ("C:\Program Files\LANDesk\LDClient\sdmcache\packages$\SystmOne")
Run ("msiexec /i SystmOne.msi")
winwait ("[CLASS:MsiDialogCloseClass]")
WinActivate ("[CLASS:MsiDialogCloseClass]")
ControlClick("TPP SystmOne Setup", "", 226)

[water]

Set the working dir for Run:

Run ("msiexec /i SystmOne.msi", "C:\Program Files\LANDesk\LDClient\sdmcache\packages$\SystmOne")

 

[ginger9991]

unfortunatly im hitting the same issue. Cant get my head around this.