/build/static/layout/Breadcrumb_cap_w.png

k1000; Install before login, MI not executing or downloading and Script doest block login

Hi All,

I'm hoping someone can give me a good solution to my problem.

I have built a powershell script that uninstalls 6 bits of now defunct software, and installs new versions of 4.

Per install it sets reg properties which I created as a custom inventory to deploy as. 


My managed installs don't execute on boot at all. The files only sometimes download to programdata, perhaps just slowly. Running a manual inventory doesn't help.

They work fine if I set them to any other option, such as 'Anytime', perfectly.

I tried moving them into offline scripts, and while the files download and execute fine, the user can log in while they are running and launch things which will kill the install.


We are primarily laptops and this is a major version change to our core systems, so its imperative that the files are pre-downloaded and ready to execute all on the same day.

Is there any way to force the files to pre-download before execution, and block login before they are complete?



I'm relatively new to the KACE ecosystem so I'm not sure if I'm missing something.


Do managed installs not pre-download if needed to be run at boot?



Many thanks


0 Comments   [ + ] Show comments

Answers (1)

Posted by: MGruber 5 years ago
Senior White Belt
1

If I'm not wrong MIs at boot will be executed with the system account. This means that the system account needs to have executive rights wherever your install files are stored.

You also need to make sure that you have a network connection before the windows login appears and before the script gets stated.

There is a way to do this via GPO: "Always wait for the network at computer startup and logon"

Source: https://stackoverflow.com/questions/16204789/windows-7-connect-to-network-before-startup-process-and-login#31617687

If you have files uploaded to KACE they will be downloaded before the script is running.

Can you make some screenshots of the MI?

Maybe you will find the issue in the KACE log: C:\ProgramData\Quest\KACE\user\KAgent.log

https://support.quest.com/de-de/kb/133819/reading-the-kagent-log-managed-install


I hope this is useful and you will find the issue.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ