/build/static/layout/Breadcrumb_cap_w.png

How to stop admin password from popping up during a scripted install?

I'm deploying an app called Alertus to several hundred macs. None of the apps I've installed previously have ever asked for the administrator password during a scripted install. This one is and I'm trying to figure out why and how to stop it. Shouldn't KBOX be a special system user and be able to do everything without user interaction?

Its a .dmg made by the Alertus Deploy tool. Inside are the pkg, the config file and the logo.

Here is part of the script:

/usr/bin/hdiutil mount -nobrowse "$KBOX53PATH/alertusosx2924994.dmg"
sleep 5

/usr/sbin/installer -pkg /Volumes/alertusosx2924994/alertus-desktop-osx-2.9.24.994.pkg -target /

 

I know its writing to the Library folder in the Application Support folder and in the Preferences folder underneath. Symantec does the same thing. I think its at this point that its asking for the password so it can write itself in as a login item in the loginitems.plist file but I'm not sure.

 

Any suggestions are welcome!

Asked 11 years ago 2900 views
0 Comments   [ + ] Show comments

Answers (2)

Posted by: jknox 11 years ago
Red Belt
0

The agent should be running as root.  Enable debug, run the script and look for the KBOT_LOG: http://www.kace.com/support/resources/kb/article/how-to-enable-debug-logs-on-the-kace-k1000-client-kbox-client-deployment

Once the package is on the client (after the script fails), are you able to run the same commands in terminal successfully?

Comments:
  • Enabled the debug and ran the script, one through kbox server, the other locally. Same results, got asked for the admin password and both worked. Here are the logs. I see more entries in the locally run one but not seeing where the issue might be:

    KBOX Server log:
    Tue Jul 9 10:42:22 2013] Client read 133 bytes
    [Tue Jul 9 10:42:22 2013] Client processing 133 bytes
    [Tue Jul 9 10:42:22 2013] Header: msgid (110207879); msgType (0)
    [Tue Jul 9 10:42:22 2013] Payload: pluginId: Web (5); payloadLen (122)
    [Tue Jul 9 10:42:22 2013] Got todo item on worker thread
    [Tue Jul 9 10:42:22 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110207879, statusCode=200
    [Tue Jul 9 10:42:24 2013] Client read 155 bytes
    [Tue Jul 9 10:42:24 2013] Client processing 155 bytes
    [Tue Jul 9 10:42:24 2013] Header: msgid (110207886); msgType (0)
    [Tue Jul 9 10:42:24 2013] Payload: pluginId: Web (5); payloadLen (144)
    [Tue Jul 9 10:42:24 2013] Got todo item on worker thread
    [Tue Jul 9 10:42:24 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110207886, statusCode=200
    [Tue Jul 9 10:42:25 2013] Client read 237 bytes
    [Tue Jul 9 10:42:25 2013] Client processing 237 bytes
    [Tue Jul 9 10:42:25 2013] Header: msgid (110207891); msgType (0)
    [Tue Jul 9 10:42:25 2013] Payload: pluginId: RunProcess (6); payloadLen (226)
    [Tue Jul 9 10:42:26 2013] Got todo item on worker thread
    [Tue Jul 9 10:43:22 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110207891, statusCode=0

    This is the log from locally:
    [Tue Jul 9 11:04:15 2013] Client read 141 bytes
    [Tue Jul 9 11:04:15 2013] Client processing 141 bytes
    [Tue Jul 9 11:04:15 2013] Header: msgid (110215887); msgType (0)
    [Tue Jul 9 11:04:15 2013] Payload: pluginId: Web (5); payloadLen (130)
    [Tue Jul 9 11:04:15 2013] Got todo item on worker thread
    [Tue Jul 9 11:04:15 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110215887, statusCode=200
    [Tue Jul 9 11:04:22 2013] Client read 143 bytes
    [Tue Jul 9 11:04:22 2013] Client processing 143 bytes
    [Tue Jul 9 11:04:22 2013] Header: msgid (110216014); msgType (0)
    [Tue Jul 9 11:04:22 2013] Payload: pluginId: Web (5); payloadLen (132)
    [Tue Jul 9 11:04:23 2013] Got todo item on worker thread
    [Tue Jul 9 11:04:23 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110216014, statusCode=200
    [Tue Jul 9 11:04:45 2013] Client read 159 bytes
    [Tue Jul 9 11:04:45 2013] Client processing 159 bytes
    [Tue Jul 9 11:04:45 2013] Header: msgid (110216341); msgType (0)
    [Tue Jul 9 11:04:45 2013] Payload: pluginId: Web (5); payloadLen (148)
    [Tue Jul 9 11:04:46 2013] Got todo item on worker thread
    [Tue Jul 9 11:04:53 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110216341, statusCode=200
    [Tue Jul 9 11:05:08 2013] Client read 157 bytes
    [Tue Jul 9 11:05:08 2013] Client processing 157 bytes
    [Tue Jul 9 11:05:08 2013] Header: msgid (110216553); msgType (0)
    [Tue Jul 9 11:05:08 2013] Payload: pluginId: Web (5); payloadLen (146)
    [Tue Jul 9 11:05:08 2013] Got todo item on worker thread
    [Tue Jul 9 11:05:30 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110216553, statusCode=200
    [Tue Jul 9 11:05:33 2013] Client read 143 bytes
    [Tue Jul 9 11:05:33 2013] Client processing 143 bytes
    [Tue Jul 9 11:05:33 2013] Header: msgid (110216972); msgType (0)
    [Tue Jul 9 11:05:33 2013] Payload: pluginId: Web (5); payloadLen (132)
    [Tue Jul 9 11:05:33 2013] Got todo item on worker thread
    [Tue Jul 9 11:05:33 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110216972, statusCode=200
    [Tue Jul 9 11:05:41 2013] Client read 177 bytes
    [Tue Jul 9 11:05:41 2013] Client processing 177 bytes
    [Tue Jul 9 11:05:41 2013] Header: msgid (110217037); msgType (0)
    [Tue Jul 9 11:05:41 2013] Payload: pluginId: Web (5); payloadLen (166)
    [Tue Jul 9 11:05:42 2013] Got todo item on worker thread
    [Tue Jul 9 11:05:42 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110217037, statusCode=200
    [Tue Jul 9 11:05:54 2013] Client read 242 bytes
    [Tue Jul 9 11:05:54 2013] Client processing 242 bytes
    [Tue Jul 9 11:05:54 2013] Header: msgid (110217155); msgType (0)
    [Tue Jul 9 11:05:54 2013] Payload: pluginId: RunProcess (6); payloadLen (231)
    [Tue Jul 9 11:05:55 2013] Got todo item on worker thread
    [Tue Jul 9 11:05:55 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110217155, statusCode=0
    [Tue Jul 9 11:06:03 2013] Client read 139 bytes
    [Tue Jul 9 11:06:03 2013] Client processing 139 bytes
    [Tue Jul 9 11:06:03 2013] Header: msgid (110217214); msgType (0)
    [Tue Jul 9 11:06:03 2013] Payload: pluginId: Web (5); payloadLen (128)
    [Tue Jul 9 11:06:04 2013] Got todo item on worker thread
    [Tue Jul 9 11:06:04 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110217214, statusCode=200
    [Tue Jul 9 11:06:11 2013] Client read 153 bytes
    [Tue Jul 9 11:06:11 2013] Client processing 153 bytes
    [Tue Jul 9 11:06:11 2013] Header: msgid (110217241); msgType (0)
    [Tue Jul 9 11:06:11 2013] Payload: pluginId: Web (5); payloadLen (142)
    [Tue Jul 9 11:06:12 2013] Got todo item on worker thread
    [Tue Jul 9 11:06:12 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110217241, statusCode=200
    [Tue Jul 9 11:06:15 2013] Client read 205 bytes
    [Tue Jul 9 11:06:15 2013] Client processing 205 bytes
    [Tue Jul 9 11:06:15 2013] Header: msgid (110217277); msgType (0)
    [Tue Jul 9 11:06:15 2013] Payload: pluginId: Web (5); payloadLen (194)
    [Tue Jul 9 11:06:15 2013] Got todo item on worker thread
    [Tue Jul 9 11:06:16 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110217277, statusCode=200
    [Tue Jul 9 11:06:38 2013] Client read 241 bytes
    [Tue Jul 9 11:06:38 2013] Client processing 241 bytes
    [Tue Jul 9 11:06:38 2013] Header: msgid (110217360); msgType (0)
    [Tue Jul 9 11:06:38 2013] Payload: pluginId: RunProcess (6); payloadLen (230)
    [Tue Jul 9 11:06:39 2013] Got todo item on worker thread
    [Tue Jul 9 11:06:39 2013] KACE Agent Lib: main: kpiKmsgrMsgDoneCallback: msgIdDone=110217360, statusCode=0 - thefishyfew 11 years ago
  • I can recreate it each time by killing the Alertus process, deleting it from the Applications folder, removing 2 pref files from /Library/Preferences and deleting the Alertus folder from /Library/Application Support/ folder. Then i do a killall Finder to reset everything. - thefishyfew 11 years ago
Posted by: ms01ak 11 years ago
10th Degree Black Belt
0

Why not take the dmg and make it a distribution instead of a script? When it's a distro it will automatically mount the drive and install the pkg inside with that command.

Comments:
  • I couldn't get it to open the .dmg file to open. We are running kbox 5.3. Doesn't distros only open .pkg and .app files? - thefishyfew 11 years ago
  • No a distro will mount the dmg and then look for a pkg inside, if it's an mpkg or multiple pkg it won't work. It all depends on how it packaged. I usually find that it works fine for most apps, the other ones I just repackage using composer as a pkg wrapped in a dmg - ms01ak 11 years ago
  • Testing the distro theory now. Originally the problem was the Alertus software wouldn't immediately poll the server. With a script I could stop/start the process and ensure that it was running. I could also hide the app from the user so they couldn't delete it. Can't really so that with a distro, i believe. - thefishyfew 11 years ago
 
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