/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Scripted Install

05/24/2017 714 views
hello, 

Is there anyway to find out what the name of the scripted install that was used, 

I want to be able to use a ps script that can detect that and then install what is necessary for that scripted install
0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

1
I don't believe that there are any files stored on the local device that would indicate this. It would be easy enough to create a post install task that does, however. You can try to detect which scripted install was used by looking in the c:\kace\engine\tasks.xml file. Alternatively, if you don't have that kind of scripting experience, you create a post-install task per scripted install that places a marker file on the computer.

The bigger question is why not just include the necessary software installations with the scripted install as post-install tasks?

Answered 05/25/2017 by: chucksteel
Red Belt

All Answers

0

The bigger question is why not just include the necessary software installations with the scripted install as post-install tasks?


I wanted to create a script that would detect the Scripted Install name so it Can name the computer accordingly and then join the domain and put in OU based on the name it has, so I can just  apply the Post-install task to "Rename-Join Computer" to all my scripted installs,  but it looks like I have to create a script for each Scripted Install name.

Answered 05/25/2017 by: garduno
White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
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