Blog Posts tagged with k1000

Ask a question

[KACE] What is in the nightly administrator emails generated by the KBOX

  • Summary: Information contained in the nightly administrator emails from the kbox.
  • Symptoms: Nightly emails from the kbox titled "KBOX Daily Run Output" and "KBOX Security Run Output".
  • Cause: Standard FreeBSD process.
  • Steps to resolve issue: Comments in bold are below the sample output. Your output will vary slightly from that shown below.

Removing stale files from /var/preserve:
Cleaning out old system announcements:
Removing stale files from /var/rwho:
Backup passwd and group files:
Verifying group file syntax:
Backing up mail aliases:
All of the above are the standard freebsd maintenance messages
Disk status:
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/twed0s1a 2026030 36780 1827168 2% /
devfs 1 1 0 100% /dev
/dev/twed0s1f 134105316 1003568 122373324 1% /kbox
/dev/twed0s1e 10154158 6365810 2976016 68% /usr
/dev/twed0s1d 2026030 3858 1860090 0% /var
/dev/twed1s1d 151368706 2722542 136536668 2% /kbackup
Last dump(s) done (Dump '>' file systems):
This table reports various information about your disks.
Of interest are /kbox and /kbackup.
/kbox is where all the software for the kbox server lives. It's also where we keep the
software packages you upload to the server.
If this starts getting close to full you should consider removing old unused packages
or contacting KACE for an upgrade.
/kbackup is the drive where /kbox is backed up to. It should generally be about as full
as the /kbox. Again if it is near full you should consider some cleanup actions.
The other mount points should not move very much in terms of usage.
 
Network interface status:
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
em0 1500 00:30:48:73:07:4c 332146 0 204673 0
0
em0 1500 192.168.2 kboxdev 308055 - 201832 -
-
em0 1500 fe80:1::230:4 fe80:1::230:48ff: 0 - 4 -
-
em1* 1500 00:30:48:73:07:4d 0 0 0 0
0
plip0 1500 0 0 0 0
0
lo0 16384 699 0 699 0
0
lo0 16384 your-net localhost 699 - 699 -
-
lo0 16384 localhost ::1 0 - 0 -
-
lo0 16384 fe80:4::1 fe80:4::1 0 - 0 -
-
 
This table is reporting information about the network status of the KBOX.
In general, you should be making sure that Ierrs/Oerrs are zero. Other values
indicate some sort of network failure. If you are noticing consistant errors
please contact KACE support for assistance.
 
Local system status:
3:04PM up 3 days, 4:12, 0 users, load averages: 0.05, 0.20, 0.15
 
This indicates the amount of time the kbox has been up since the last time it was powered off.
You shouldn't see any users logged into the machine, and the load averages will vary with
how busy the kbox was when this report was run.
 
Mail in local queue:
/var/spool/mqueue is empty
Total requests: 0
Mail in submit queue:
/var/spool/clientmqueue is empty
Total requests: 0
Security check:
(output mailed separately)
Checking for rejected mail hosts:
Checking for denied zone transfers (AXFR and IXFR):
tar: Removing leading /' from member names
 
Standard freebsd messages regarding the health of the mail systems.
There should not be anything in the Mail queues. If there is, please
check your SMTP setting from the KBOX ui
 
[Thu Mar 17 15:05:31 PST 2005] KBOX Backup: Backup Complete.
Backup files available for off-box storage via ftp.
 
This is a KBOX specific message telling you that the backups have
successfully completed and are on the /kbackup disk,
available through the ftp interface.
 
[Thu Mar 17 15:05:31 PST 2005] KBOX RAID Status
Disk Array Detail Info not available during a rebuild.
If Rebuild in progress, % completion listed below
Disk Array Detail Status:
Unit UnitType Status %Cmpl Port Stripe Size(GB) Blocks
-----------------------------------------------------------------------
u0 RAID-1 OK - - - 149.05 312579760
u0-0 DISK OK - p0 - 149.05 312579760
u0-1 DISK OK - p1 - 149.05 312579760
Disk Array REBUILD Status:
/c0/u0 is not rebuilding, its current state is OK
 
Indicates the status of your raid drives. this information is available in the
KBOX admin UI under Disks/Backup tab. If you ever see the disks DEGRADED or not
REBUILDING properly, please contact KACE support to address the problem.
 
[Thu Mar 17 15:05:31 PST 2005] KBOX Database Maintenance
Daily routines to maintain database performance.
DB Table Maintenance Log:
# Connecting to localhost...
# Disconnecting from localhost...
KBDB.ADVISORY OK
KBDB.AUTHENTICATION OK
KBDB.CATEGORY OK
KBDB.CLIENT_DISTRIBUTION OK
KBDB.FILTER OK
KBDB.FS OK
KBDB.FS_LABEL_JT OK
KBDB.GLOBAL_OPTIONS OK
KBDB.LABEL OK
KBDB.LDAP_FILTER OK
KBDB.LICENSE OK
KBDB.LICENSE_MODE OK
KBDB.MACHINE OK
KBDB.MACHINE_CUSTOM_INVENTORY OK
KBDB.MACHINE_DISKS OK
KBDB.MACHINE_LABEL_JT OK
KBDB.MACHINE_NICS OK
KBDB.MACHINE_PROCESS OK
KBDB.MACHINE_SOFTWARE_JT OK
KBDB.MACHINE_STARTUP_PROGRAMS OK
KBDB.MESSAGE OK
KBDB.MESSAGE_LABEL_JT OK
KBDB.MI OK
KBDB.MI_LABEL_JT OK
KBDB.NETWORK_SETTINGS OK
KBDB.NOTIFICATION OK
KBDB.OPERATING_SYSTEMS OK
KBDB.PORTAL OK
KBDB.PORTAL_LABEL_JT OK
KBDB.PRODUCT_LICENSE OK
KBDB.REPORT OK
KBDB.SCHEDULE OK
KBDB.SERVER_LOG OK
KBDB.SOFTWARE OK
KBDB.SOFTWARE_LABEL_JT OK
KBDB.SOFTWARE_OS_JT OK
KBDB.THROTTLE OK
KBDB.TIME_SETTINGS OK
KBDB.TIME_ZONE OK
KBDB.USER OK
KBDB.USER_HISTORY OK
KBDB.USER_KEYS OK
KBDB.USER_LABEL_JT OK
-- End of daily output --
 
The database is checked nightly for any inconsistancies and automatically repaired.
If you seen any failures from this output, please contact KACE support for assistance.


Be the first to comment

K1000 5.4 SP1 is released

The new SP1 for K1 5.4 is released since this night:

http://downloads.kace.com/support/customer/release/K1000/5.4.76847/k1000_server_5.4.76847.kbin

 

Be the first to comment

Dell KACE K1000 Series Videos

Dell KACE K1000 Series Videos

This series of blogs and videos will help provide some basic information on the K1000 appliance.  The videos can serve as initial helpers for new customers as well as refresher items for those needing some gaps filled in.  Please note that the version described in the titles below show what version of the product was available when the videos were designed.  Regardless of their specific version, they may still be applicable to other versions of the product.

K1000 5.5 Videos

What's New

K1000 5.5 Overview

 


 

K1000 5.3 Videos

Configuration

K1000 Settings

KBOX 101 Series: Configuration

Agent

Agent Fundamentals

Inventory & Labels

Inventory Fundamentals

Label Fundamentals

KBOX 101 Series: Inventory

Distribution

Software Distribution Intro

Replication Intro

KBOX 101 Series: Software Distribution

Patch Management

Patch Management Intro

Scripting

KBOX 101 Series: Scripting

Service Desk

KBOX 101 Series: Service Desk

Assets

KBOX 101 Series: Assets

 


 

 

If you would like to provide feedback, we'd love to hear it!  You can provide comments below, rate this post, or just email elearning@kace.com and tell us what you think.

Be the first to comment

K1000 5.4 - Machine Actions

In 5.4 we can now create more than two machine actions!  Once I realized how easy these were to manipulate I started adding and adjusting them like a kid in a candy store.  My machine action drop-down now has 9 items and we find them all useful.  It was well-timed with an effort to make KACE more useful for our service desk.

If you like to use Firefox I highly recommed the plugin "IE Tab 2" so you can launch the K1000 admin console in a "IE Tab".  This prevents the pesky error: "Sorry, this Machine Action is only supported when using Microsoft Internet Explorer."

Here are my Machine Actions:

Admin Share
Computer Management
Ping
PsList
PsLoggedon
Services
Shutdown –i
UVNC Win 7
UVNC Win XP

All of our machine actions are “Custom action…” from the drop down except for ping.  That one is “Ping using host IP”

The machine actions that start with Ps require PStools to exist at C:\pstools.  There's probably a better way to do this (call from a network share?) but it was simple at the time and works for us.  (Please feel free to comment and tell me there’s a better way!)

Here’s my syntax for all of our machine actions:

Admin Share:
explorer.exe \\KACE_HOST_NAME\c$

Computer Management:
cmd.exe /c compmgmt.msc /Computer:KACE_HOST_NAME

PsList:
cmd.exe /K "c:\pstools\PsList.exe" \\KACE_HOST_NAME -t -s

PsLoggedon:
cmd.exe /K "c:\pstools\PsLoggedon.exe" -accepteula \\KACE_HOST_NAME

Services:
cmd.exe /c services.msc /Computer:KACE_HOST_NAME

Shutdown -i:
shutdown.exe –i

UVNC Win 7:
"c:\\Program Files\\UltraVNC\\vncviewer.exe" /dsmplugin SecureVNCPlugin64.dsm KACE_HOST_NAME

UVNC Win XP
"c:\\Program Files\\UltraVNC\\vncviewer.exe" /dsmplugin SecureVNCPlugin.dsm KACE_HOST_NAME

We have many shared PCs where there is an auto-user logging into the PC and our users log into context with the secondary logon.  PsLoggedon is great for use on those machines to see the user that is logged in.

I had a shutdown.exe -m \\KACE_HOST_NAME -r -t 30 -f but it was too easy to accidentally kick off a reboot.  If I could get this to prompt, "Are you sure?" I wouldn't use shutdown.exe -i

The rest are fairly self-explanatory.  Let me know if you find them useful!

-awingren

View comments (13)

Update to SLA Timer Ticket Rules Series

I was going through the SQL for the rules to create a SLA Timer from this series: http://www.itninja.com/blog/view/creating-true-sla-timers-in-the-kbox-helpdesk-part-iii-the-rules. I noticed that the custom fields for Modified and Last updated are working correctly, but it appears that the fields for Total Time Opened and Total Time Stalled are not updating properly. They continue to contain 0.

I see that the first rule adjusts Total Time Opened and Total Time Stalled to '0'on ticket creation. The rule that should be ticking the counter every 15 minutes has this as the select query:

select HD_TICKET.ID
from 
            HD_TICKET
        JOIN HD_FIELD QF ON QF.HD_QUEUE_ID=HD_TICKET.HD_QUEUE_ID 
            and FIELD_LABEL='Counter Last Updated' and QF.NAME='CUSTOM_15'
where
  /* only care about tickets where relevant time has changed */
    NOW()>ifnull(cast(CUSTOM_FIELD_VALUE14 as datetime),'0000-00-00')
    and
    (
        LENGTH(HD_TICKET.CUSTOM_FIELD_VALUE12)>0 OR
        LENGTH(HD_TICKET.CUSTOM_FIELD_VALUE13)>0
    )

If the fields are set to '0', then the rule to incrementally increase these two fields will never run because they will always = 0 and never be >0. Am I right? I changed the rule to incrementally update the counter to say

and
    (
        LENGTH(HD_TICKET.CUSTOM_FIELD_VALUE12)>=0 OR
        LENGTH(HD_TICKET.CUSTOM_FIELD_VALUE13)>=0
    )

and it appears to be working now.

There was also a reference to a column 'HOURS.BIZ' that hasn't been created in the tutorial yet that was giving me an error because it doesn't exist. Maybe the tutorial could be edited to add this in when the Business Hours piece is created in the next steps.

I believe the same problem might exist in the Proact to OTS Rules that adjust status. When the ticket saves if the ticket was just created in the last 15 minutes the custom fields will still = '0' and the change in status will not register. Changing it to >=0 should solve that issue here as well.

View comments (3)
Showing 1 - 5 of 17 results

Top Contributors

Talk About Hardware