Server/Agent ver 5.3 combination
In December I upgraded both server and clients to 5.3 - (Server 5.3.47927) (Client 5.3.47657) and we pushed the client upgrade through GPO and included in our image process. All of the clients (90%) stopped checking in. I found the issue to be the amp.conf does not contain the information it did in previous versions like hostname, ampurl, companyname, plashtext, localhost... A few clients had no issues with the transition with no rhyme or reason why. What is the best corrective action to push out the correct information to the non-reporting clients?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
GillySpy
12 years ago
when you pushed it out did you rename the msi or add a host name parm?
http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=848&artlang=en#5_3_Agent
you can correct it by removing it and redeploying it with those settings. OR
the defaults are for it to look for a server call "K1000". you could:
1) create a CNAME DNS record to point to your real kbox.
2) After they all connect you can remove the CNAME record.
3) They will update themselves at step 2 with the real kbox host name as a backup (lasthost)
4) they will reconnect and fail on the cname and try the backup name
5) the backup name will become primary (host)
http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=848&artlang=en#5_3_Agent
you can correct it by removing it and redeploying it with those settings. OR
the defaults are for it to look for a server call "K1000". you could:
1) create a CNAME DNS record to point to your real kbox.
2) After they all connect you can remove the CNAME record.
3) They will update themselves at step 2 with the real kbox host name as a backup (lasthost)
4) they will reconnect and fail on the cname and try the backup name
5) the backup name will become primary (host)
Posted by:
icn2pcs
12 years ago
We used the same procedure as before by renaming the msi to include the hostname of the kbox which worked on the previous version. We were told not to reconfig the parameters of the msi anymore.
Posted by:
GillySpy
12 years ago
Ok. I suggest a support ticket so someone can reproduce / verify and log an issue. To get you over the hump could you also try the HOST=technique on the command line? perhaps call it with a batch?
Posted by:
cmccracken
12 years ago
When I ran into forgetful amp.conf files I ran:
amptools.exe -resetconf host=kboxnamehere
I used PSExec because we didn't have that many, but I think you could also push it with a GPO.
Casey
amptools.exe -resetconf host=kboxnamehere
I used PSExec because we didn't have that many, but I think you could also push it with a GPO.
Casey
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.