/bundles/itninjaweb/img/Breadcrumb_cap_w.png

Blog Posts tagged with Kace K1000 Management Appliance 5

Ask a question

KACE:Installing an Adobe application larger than 1.7 GBs on Mac agents running 5.3

The below guideline is how to install an Adobe application where the file size is 1.7GBs or larger to Mac agents.  The application used in the below example is CS5 premium.

First goal is to create an unattend install package (.pkg) of the product following these directions below:

  1. Copy the install file for the package to a local Mac workstation. This process works for any of the CS5 products (Dreamweaver, Photoshop, full CS5 package, etc).
  2. Download and install AAMEE (Adobe Application Management Enterprise Edition). Found here: http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html
  3. Run AAMEE. It will launch a fairly long wizard, in which you will set the unattended install parameters for the Adobe package.



    NOTE: If you are unfamiliar with this application, Adobe has a tutorial video on how to create a package. To access this video, Click Here .

  4. Select CREATE INSTALL PACKAGE.
  5. Follow the instructions to create the install package.
  6. When the install package is complete, upload the package as a software inventory item to the K1000. If the browser upload fails, copy it to the clientdrop share on the K1000 appliance to attach it to the software item. 
  7. Create a corresponding MI package. Set the installation command to Configure Manually and leave the command window blank. Nothing needs to be ran here.


    NOTE: In the Configure Manually field, put a '.' so it will allow you to save the Managed Install.

  8. Deploy the PKG to a test system. The purpose of this is to not deploy and install the package, but to determine the actual package identification number given to its folder on the actual test system.
  9. Look at the test system for the exact path of the CS5 install package. It will be /Library/Application Support/Dell/KACE/data/packages/xxx. It's very important to find out what the actual 'XXX' number is for the file downloaded.

The next part is to create an Online Shell Script to deploy the Managed Install. Navigate to Scripting. Under Choose Action, select Add New Item. Change the Script Type to Online Shell Script. The script will need to include both the unzip command and the install command.

  1. The unzip command will need to target the exact path of the CS5 (or alternate Adobe application) package. It's "unzip <absolute path to package>".
  2. The install command is tricky and largely depends on how the unzip command above is used. This is because the default location of the file unzipped is the script dependancy folder (/Library/Application Support/Dell/KACE/data/scripts/xxx). It's advised to not specify an unzip location. Therefore the install command would be something like "installer -pkg /Library/Application Support/Dell/KACE/data/scripts/xxx/CS5_install.pkg"



  3. Finally, a Custom Inventory Rule would need to be created to ensure the rule detects the download of the package so it doesn't keep downloading it over and over.  The Custom Inventory Rule will also prevent the install of the application on every check-in. Create this rule in the same Software inventory item used to upload the application in Step 6.



  4. Application is now ready for deployment.

Be the first to comment

KACE::Barcode Asset Management via the KACE 1000 Series Appliance

Summary:
The use of barcodes is becoming standard practice for asset management in many institutions. Often we will see these barcodes on computers, monitors and printers but they can be applied to many other things including locations, vehicles and more. The difficult part is managing the barcodes in a simple-to-use manner. The K1000 series of Kace Appliances have the ability to get you started in simple barcode asset management right out of the box.

Resolution:
The IT Asset Management tab of the KACE Management Appliance contains the ability to record any type of asset you wish so there is no reason a barcode could not be one of them.

Once a barcode asset is created you can give it fields that the asset will contain. The Name text field will be there by default and is the only thing which can be needed. Having an attachment field for a JPG of the barcode can be helpful if you find the need to see it, print it, or scan it directly from the screen.

Once the Barcode Asset is created, a third party barcode creator will be necessary to create the barcode itself as well as printing a barcode out to apply it to an item.

When creating the barcode asset in the KACE Appliance, the two fields you made available will appear. Once you place the cursor in the Name field of the asset you may use a USB connected barcode scanner attached to your computer to read the barcode and enter the data into the field. You can also now browse to a JPG of the barcode on your computer to attach a picture of it to the asset.

Hit Save.

Now the barcode asset is created and there is a thumbnail of the picture which you can expand by clicking on it. Once clicked, it is usually large enough for any basic USB-to-Computer attached barcode reader to scan right from the screen.

Associating the barcode to another asset in the KACE Appliance:

Once the barcode is created, you can apply it to other assets for tracking. This can be done in a few different methods depending on the method of the institutions choice.
One method is to have a barcode asset for every location and have every device in that location have the same barcode, showing which location they belong to. For example, a school may have a barcode at the door of a lab and they would like to be able to scan the barcode to see a list of devices assigned to the lab. If one is missing or there are any extra, they can make adjustments accordingly.
Another method is for each device to have their very own barcode. This method can be used to pinpoint specific information if there are more fields created in the barcode asset type.
Taking the first example, let’s show how the assets can tie together. Let’s say a barcode belongs to an individual and everything that individual is supplied has that same barcode. An asset field can be added to the User asset type called Barcode, the field type will be Asset Barcode, and we will check the Allow Multiple checkbox to ensure that a link to the barcode asset will show. Then we hit save.

If the Barcode Asset field is in one of the first 5 asset fields, then it will show on the User asset list.

Choose a user that currently does not have a barcode asset associated to them and hit the Edit link to choose which barcode to associate.

Then select save.

Now the barcode is available as a clickable link. By clicking on the link, you will be able to see the barcode information itself as well as all other items you have associated that barcode to throughout all assets.

Because the Related Assets section will have clickable links, you may now click on any of the other related assets to see more information about that item.

Now that you have a list of barcode assets, they are all easily found in the database via the reporting tool or by utilizing the search section in the upper right of the asset manager.


There are many best practices for using barcodes in many different institutions. By utilizing the KACE Appliance Asset Management solution you can start managing and keeping track of your physical assets via barcode in an easy-to-use basic manner.

For more information regarding the KACE 1000 Series appliance click here.

For more information regarding the Asset Management capabilities of the KACE 1000 Series Appliance click here .

View comments (5)

KACE K1000: How to enable debug logs on the KBOX Client 

    Summary: This article will give you information on how to enable debug logs on 5.1 and newer agents
    Symptoms: When logs need to be gathered to troubleshoot managed installation, scripting issues, replication, and patching
    Cause: Issues when deploying managed installations, scripting, patching, replication shares, etc
    Steps to resolve issue:

In addition to the standard logging, there are some additional debug logs that can be enabled on a K1000 client machine:

Version 5.3

Windows

In 5.3 agents (and up) enabling debugging is much easier. Here are the steps:
Method 1: If the agent is not connecting to the kbox or if you want to do it manually

  •   Stop the Dell Kace Agent service
  •   Edit the amp.conf file by adding a line debug=true
  •   Start the service again

Method 2: If the agent is still connecting to the kbox then:

  •   Locate the script called K1000 Agent Debug Log Enable(Windows)
  •   Select specific machines as a target
  •   Schedule the script or, for a small group of PCs, use Run Now

Method 3: At the agent

  •   Open a command prompt to c:\program files\dell\kace  (note:32bit program files)
  •   Run amptools.exe debug=true

Mac OSX

  •   Edit  /Library/Application\ Support/Dell/KACE/data and add a new line: debug=true
  •   Restart the service with:

                     sudo /Library/Application Support/Dell/KACE/bin stop
       and then
                     sudo /Library/Application Support/Dell/KACE/bin start

  •   The log files at /Library/Application\Support/Dell/KACE/data will now have debug info


Version 5.1

In 5.1.31311 agents (and up) enabling debugging is much easier. Here are the steps:

Method 1: If the agent is not connecting to the kbox or if you want to do it

  •   Stop the KBOX SMMP Management Service
  •   Edit the smmp.conf file by adding a line debug=true
  •   Start the KBOX SMMP Management Service

Method 2: If the agent is still connecting to the kbox then:

  •   Locate the sript called KBOX Agent Debug Log Enable
  •   Select specific machines as a target
  •   Schedule the script or, for a small group of PCs, use Run Now

Method 3: If the agent is at 5.1.33668 and up then:

  •    Open a command prompt to c:\program files\kace\kbox
  •    Run ampreset.exe debug=true


Version 5.0 and lower

  •  KBOX Management Service (Windows) - enable debug logging on the KBOX Management Service for detailed information on script execution and to troubleshoot script scheduling issues. (This service does not exist in 5.x and up)
  •  KBOX Client - enable debug logging on the KBOX client to troubleshoot machine inventory, managed installs and file synchronizations
  •  KBOX SMMP Service - Available in 4.0 only. enable debug logging on the windows KBOX client to troubleshoot the on-demand rrunning of Desktop Alerts, Run-Now scripts, and Patching. (Mac: Alerts and patching | Linux and Solaris: alerts only)


For Patching Debugging see this this FAQ


Windows Debugging

You should send all recently modified files to support.  If you're on 5.1 or lower the files are located in in the c:\program files\kace\kbox.  If you're on 5.3 and on a Windows Vista or 7 system the files will be in c:\programdata\dell\kace.  A 5.3 system that's on Windows XP will have the files in C:\Documents and Settings\All Users\Dell\KACE

Windows:

  • KBOT_LOG.txt
  • debug.log
  • SMMP.log

        1. To enable debug logging for the KBOX Management Service, stop the KBOX management service and edit the file:

         C:\Program Files\KACE\KBOX\config.xml

        and change the value of the debugLoggingEnabled flag to read:

            <debugLoggingEnabled>true</debugLoggingEnabled>

Now restart the KBOX Management service. This will cause KBOXManagementService to log additional debugging information to the file KBOT_LOG.txt

2. To enable the K1000 Client debug log, create an empty file with the name

             C:\Program Files\KACE\KBOX\KBCLIENT_DEBUG

        This will cause K1000 Client to log debug information to a file in the same directory named

           debug.log

The K1000 Client debug log file documents the details of gathering machine inventory, executing custom inventory rules, and outputs the managed installs and file synchronizations to be run based on interaction with the KACE K1000 appliance. Should an installation fail, it is possible to duplicate the issue using the same command found in the debug.log file and run locally on the client machine. If there are any errors they can be tested and investigated on the client machine.

3. Logging on the SMMP Service

New to 4.x the SMMP service can be debugged by adding the following to the c:\program files\kace\kbox\SMMP.conf file

debug=true

This will generate more debugging information about patching, run now script, and alert messages in the SMMP.log file.

Tips:

  •   If you cannot get to a machine directly then perhaps you can enable debugging through hidden admin shares (i.e. c$) and restart services remotely use sc.exe
  •   If you still cannot get to the machine then you can try to enable debug logs remotely with this FAQ


OS X Debugging

Mac/Unix:

  • debug_agent.log
  • agent.log

1. Logging on the Management Service

  •  Open Terminal from the Applications/Utilities folder.
  •  Type sudo touch /var/kace/kagentd/debug_agent.tag, and then press ENTER
  •  Type sudo /Library/KBOXAgent/Home/bin/kagentctl stop, and then press ENTER.
  •  Type sudo /Library/KBOXAgent/Home/bin/kagentctl start, and then press ENTER. The debug_agent.log file contains debug logs.
  •  To Turn off logging simply delete the deubg_agent.tag file

2. Logging on the SMMP Service

  •  edit /var/kace/SMMP/SMMP.conf and add a new line: debug=true
  •  Restart the service with:

sudo /Library/KBOXAgent/Home/bin/SMMPctl stop

and then

sudo /Library/KBOXAgent/Home/bin/SMMPctl start

        The agent.log file will now have debug info

Linux Debugging
1. Logging on the Management Service

  •   Open the command line interface.
  •    Type sudo touch /var/kace/kagentd/debug_agent.tag, and then press ENTER.
  •    Type sudo /etc/rc.d/init.d/kagentctl stop, and then press ENTER.
  •    Type sudo /etc/rc.d/init.d/kagentctl start, and then press ENTER. The debug_agent.log file contains debug logs.

2. Logging on the SMMP Service

  •   edit /var/kace/SMMP/SMMP.conf and add a new line: debug=true
  •   Restart the service with:

            sudo /Library/KBOXAgent/Home/bin/SMMPctl stop

and then

            sudo /Library/KBOXAgent/Home/bin/SMMPctl start

  • The agent.log file will now have debug info

Solaris Debugging
1. Logging on the Management Service

  •   Open the command line interface.
  •   Type sudo touch /var/kace/kagentd/debug_agent.tag, and then press ENTER.
  •   Type sudo /etc/init.d/kagentctl stop, and then press ENTER.
  •   Type sudo /etc/init.d/kagentctl start, and then press ENTER. The debug_agent.log file contains debug logs.

2. Logging on the SMMP Service

  •   edit /var/kace/SMMP/SMMP.conf and add a new line: debug=true
  •   Restart the service with:

            sudo /Library/KBOXAgent/Home/bin/SMMPctl stop

and then

            sudo /Library/KBOXAgent/Home/bin/SMMPctl start

  •   The agent.log file will now have debug info
View comments (2)

KACE K1000: How to force a client check-in outside the normal run interval 

  • Summary: The K1000 Client normally checks in using the "Run Interval" schedule specified in the K1000 appliance Settings/Client Options tab on the server. For debugging and testing purposes, KACE provides ways that can be used to force a check-in outside this normal schedule.
  • Symptoms: The client isn't inventorying correctly or running a script, managed installation, patch, or replication doesn't provide the desired results
  • Cause: An issue with what's being ran and we need to identify what's the cause
  • Steps to resolve issue:

From the server you can click on the computer in the inventory list and then press the button 'Force Inventory Update'.

To force a checkin on the 5.1 Windows client, either browse using explorer to c:\program files\kace\kbox and double-click on KBScriptRunner.exe or launch the program from the command line:

C:\> C:\program files\kace\kbox\kbscriptrunner.exe
OS X: /Library/KBOXAgent/Home/bin/runallkbots
Linux: /Library/KBOXAgent/Home/bin/runallkbots
Solaris: /KACE/bin/runallkbots

Note that the KBScriptRunner.exe only forces a check-in (bypassing the “Run Interval”) but does not force an inventory if you have a non-zero Inventory Interval set on the server. There is no way to override the Inventory Interval from the client side. You may want to change the inventory interval to zero on the server while debugging/testing package deployments.

On a 5.3 client you will want to open up a command prompt and do the following:

c:> c:\program files\dell\kace\runkbot 4 0

Another way to force an inventory is to manually delete the machine record on the server between tests and then use KBScriptRunner to force a checkin. Since the machine record will be new, an inventory will happen. This approach doesn’t work if you’re manually applying labels to your machines, since you’ll lose the labels on the test machine each time you delete it. But it works nicely with filter labels which are dynamically reapplied.

View comments (2)

KACE K1000: Why doesn't my machine show up in KBOX Inventory after installing the KBOX 5.1 client? 

**Article is out of date now that 5.1 is not supported anymore

  • Summary: By default the K1000 client communicates with K1000 appliance using http: over port 80.   Assuming network connectivity is in place, the most common reason newly-installed K1000 clients fail to connect to the K1000 appliance during first-time setup is a problem resolving the default "KBOX" host name in DNS.  This is to be used with 5.1 clients.
  • Symptoms: Not being able to resolve the kbox hostname by DNS
  • Cause: An issue with DNS and the hostname
  • Steps to resolve issue:

Use the following steps to troubleshoot clients which fail to inventory:

  1. If you set up the K1000 appliance in your DNS using a host name other than the default "kbox", or need clients to reach the K1000 appliance by ip address instead of by DNS name, you must install the K1000 Client specifying the SERVER property. For example:

    Windows

    c:\>KInstallerSetup.exe -server=myk1000 -display_mode=silent
    
    or
    c:\>KInstallerSetup.exe -server=192.168.2.100 -display_mode=silent
    

    OS X

    /Library/KBOXAgent/Home/bin/setkbox mykbox
    
    or
    sudo sh -c 'KACE_SERVER=k1000name installer -pkg 
       /Volumes/Dell_KACE/AMPAgent.pkg -target /'
    

    Linux/Solaris

    /var/dell/kace/amp.conf
    
    or
    sudo KACE_SERVER=k1000name rpm -ivh ampagent-5.3.xxxx.i386.rpm
  2. To correct the server name for an already-installed client, edit the "ServerHost" value in:
    • Windows: C:\ProgramData\Dell\KACE\amp.conf
    • OS X: /Library/Application Support/Dell/KACE/data/kbot_config/yaml
    • Linux/Solaris: /var/KACE/kagentd/kbot_config.yaml
  3. Verify the K1000 appliance is pingable and reachable via a web browser at http://k1000
  4. Verify Internet Options are not set to use proxy, or proxy is excluded for the local network and/or K1000 appliance
  5. Verify no firewall or anti-spyware software is blocking communication between the K1000 appliance and any of client components, including:
    • KBOXManagementService.exe (AMPAgent.exe in version 5.2 and newer)
    • KBOXClient.exe
    • KUpdater.exe
    • kagentd (OS X/ Unix) (AMPAgent in version 5.2 and newer)
  6. Verify that the KBOXManagementService.exe(Windows) or the kagentd(OS X/ Unix) processes are running. The agent will show up as 'perl' in the OS X Activity Monitor. 

If after verifying these items, you are still unable to get the client to connect to the K1000 appliance, please contact KACE Support for further assistance

Be the first to comment
Showing 1 - 5 of 111 results

Top Contributors

Talk About K2000 post-imaging