Hello,

I am a true novice at this so please be patient. We had the trial version of the K1000. During that time I was able to create a few test distributions (Firefox, SPSS, Acrobat, Reader Etc) and deploy them to Windows XP SP3 and Windows 7 SP1 client machines. We purchased the full version of the K1000 5.3 and I am able still able to deploy the client and push distributions, but the alert (Kuseralert?) seems to throw a script error rather than display the customized splash screen (Pre and post install). If I choose not to customize a message when sending the distribution, the error does not occur, however, I still do not get any type of splash screen. After some searching on the web, I found a reference to a similar issue indicating a problem in the amp.conf file. The person who had the problem indicated that the issue was caused by a space or a comma in this file.

When the script error occurs, the box displays "Kuseralert invalid parameter mary's"

Below is our amp.conf file

host=kbox.smcm.edu
log=amp.log
rto=20
wto=20
crto=10
pl=pluginDesktopAlerts,pluginPatching,pluginRunProcess,pluginWeb
companyname=St. Mary's College of Maryland
splashtext=Dell KACE Systems Management Appliance is verifying your PC Configuration and managing software updates. Please Wait...
lasthost=kbox.smcm.edu
serverversion=5.3.45496
appliance=k1000
ampport=52230
ampurl=https://kbox.smcm.edu:52230
webport=443
weburl=https://kbox.smcm.edu
debug=true

Here is what I think is the important part of the kuseralert.log.
[Thu Jan 26 15:10:29 2012] KUserAlert: Unknown parameter: mary's

usage: KUserAlert -name=PKGNAME [-message=MESSAGE]
[-title=TITLE] [-timeout=(seconds)]
[-multmessage="id^pkgname^message^timeout^^id^pkgname^message^timeout"]
[[-yesno] | ([-ok] [-snooze])] [-continue] [-cancel]
[-default=<yes|no|cancel|snooze|continue)>

-name and -message are mandatory.


If this is the issue, How do I go about changing the amp.conf. I tried to edit locally (to change the company name to something without spaces or comma's) but when the client connects, it seems to revert back to the original company name.

Any help would be greatly appreciated.

Thanks,
Jeff
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I think that this is a known bug that the space in the company name is causing the error.
Answered 01/26/2012 by: steelc
Senior Yellow Belt

Please log in to comment
0
Changing the company name to something without spaces resolved the issue.

Thanks,

Jeff
Answered 01/27/2012 by: smdjeff
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity