Computers not checking in
I have several windows machines that are not checking in to Kbox.
When I look at the details of the computer I see under Kbox Agent Logs that there are question marks next to Kbox client & Kbox Scripting Updater. I have just recently updated to 5.0 and the client on all of the computers that have this problem (that I have found) are running 4.2.
So-far I've tried a Forced Check in with no luck and I have even remoted in to that computer and uninstalled the old client and installed the latest. Still no change.
I have checkd the Kace website support page but have not found anything that has help so-far.
If someone can assist me I would be greatful.
When I look at the details of the computer I see under Kbox Agent Logs that there are question marks next to Kbox client & Kbox Scripting Updater. I have just recently updated to 5.0 and the client on all of the computers that have this problem (that I have found) are running 4.2.
So-far I've tried a Forced Check in with no luck and I have even remoted in to that computer and uninstalled the old client and installed the latest. Still no change.
I have checkd the Kace website support page but have not found anything that has help so-far.
If someone can assist me I would be greatful.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
jkatkace
13 years ago
I encourage you to open a ticket with support at http://support.kace.com/
There are a variety of reasons this could happen, and we'll help you sort through them.
There are a variety of reasons this could happen, and we'll help you sort through them.
Posted by:
dtuttle
13 years ago
the details of the computer I see under Kbox Agent Logs that there are question marks next to Kbox client & Kbox Scripting Updater.  I have just recently updated to 5.0 and the client on all of the computers that have this problem (that I have found) are running 4.2. So-far I've trie
I have had problems with the settings in the config.xml file going back to 'default' (IE - hostname back to kbox). I would check that...
if it turns out that, you are having this problem to all you need to do is stop the service, fix the file, start the service.
Posted by:
kdasanmartino
13 years ago
I looked at the xml file as you suggested and it shows serverhost as the ipadddress of the kbox appliance.
Posted by:
dtuttle
13 years ago
if you see
<ServerHost>Kbox</ServerHost>
that is a fluke
it should be
<ServerHost>YOURKBOXHOSTNAME</ServerHost>
replace yourkboxhostname .. well with your kbox hostname or IP address...
<ServerHost>Kbox</ServerHost>
that is a fluke
it should be
<ServerHost>YOURKBOXHOSTNAME</ServerHost>
replace yourkboxhostname .. well with your kbox hostname or IP address...
Posted by:
kdasanmartino
13 years ago
The one I checked has an IP address of my Kbox.
So I should be good.
So I should be good.
Posted by:
RichB
13 years ago
ORIGINAL: dtuttle
if you see
<ServerHost>Kbox</ServerHost>
that is a fluke
Our server's hostname is kbox so it's not a fluke for us! With DNS and Search Domains properly configured by our DHCP server the clients connect fine with the default setting.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.