Skip to main content

Installing BigFix (Tivoli) Linux Agent on Ubuntu 16.04

This post is for my own sanity, and will explain how I went ahead and got Linux Server (Ubuntu 16.04.1) reporting in my BigFix Server.

Installation of the Client:
1. Create a directory - mkdir /etc/opt/BESClient
2. Download the associated file for your Linux Client from here.
3. Install the deb file using dpkg -i
4. Copy the Masthead from your BigFix Server over to the Linux Server and rename it:

wget http://:port/masthead/masthead.afxm
cp masthead.afxm /etc/opt/BESClient/actionsite.afxm

5. Start the service - /etc/init.d/besclient start

 Using built-in QnA functionality:
One of the biggest things that I did notice/like is that it does have the ability to use either graphical QnA if you have a graphic version instead, or CLI QnA, I'm still learning some of the Linux Relevancy and how it works, but its pretty much the same as what you use within Windows:


1. Create a file called runqna and open it with your favorite text editor, entering the below code:

#!/bin/sh
BESClientConfigPath=/var/opt/BESClient/besclient.config
export BESClientConfigPath
export LIBPATH=/opt/BESClient/bin
/opt/BESClient/bin/qna

2. Make it executable - chmod a+x runqna
3. Then run the script - ./runqna

  
Labels:

Comments

Post a Comment

Popular posts from this blog

How to setup a Host-Check for Fortigate SSL VPN

This document outlines how to setup a host-check for a Fortigate SSL VPN (Web only): config vpn ssl web portal edit "portalname" set web-mode enable set host-check custom set host-check-policy "Microsoft-Windows-Firewall" set os-check-enable set ip-pools "PoolName" set split-tunneling disable set page-layout double-column set theme orange config os-check-list "windows-7" set action check-up-to-date set latest-patch-level 1 end  config vpn ssl web host-check-software edit "Microsoft-Windows-Firewall" config check-item-list edit 1 set target "HKLM\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile:EnableFirewall==1" set type registry next edit 2 set target "HKLM\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile:EnableFirewall==1" set type registry next edit 3 set target "HKLM\\SYSTEM\\CurrentControlSet\\S...
3 comments
Read more

Implementing 802.1X - Windows 2012R2 + Cisco 4500 Switches

Implementing 802.1X Using Windows Server 2012R2 & Cisco 4500 Series Switches Overview: This document is to outline how the configuration between Windows Server 2012 R2’s NPS Services and Cisco 4500 Series switches has been implemented. High Level Diagram:   Requirements: Windows Server 2012 R2 with NPS Server installed Windows Server 2012 R2 with CA Services Windows AD Environment Cisco 4500 Series Switches Windows 7-10 Clients to connect NPS Configuration: 1. This assumes the above requirement that the NPS Service has already been installed on Windows Server 2012 R2 2. Disable all existing Policies under Connection Request Policies and Network Policies as you will be making your own, except one that states “Catch All” with the below parameters: 3. You will then need to add in a new Radius Client to have Policies built around. Friendly Name will be used going forward for the Policies for referencing the document. 4. Once completed...
Post a Comment
Read more

OVA/OVF Templates and Older Versions of VMware ESXI

Recently ran into this issue which I feel is something that I should document, as it provides some additional details onto how to configure or modify an existing .ova or .ovf file which is the standard deployment template for ESXI/VMware. Here was the issue: - ESXI 5.5 - OVA required hardware type 8. Gave an error of  " Unsupported hardware version - vmx-8" when testing. Based on everything I was reading, it isn't supported. So using the ovftool which can be found on VMware's Website ( here ) you can basically extract out the ova/ovf file into a directory, and then use it to modify the VMX file and then put it all back together. Steps: 1. Download the application and install it. 2. Go to the directory where the ovftool is stored via cmd line (Typically C:\Programs Files\Vmware\ect..) 3. Issue the following command: ovftool 4. Then modify the .vmx file so that it contains now the hardware ID of 7 (or whatever you need set for your release). 5. Then issu...
1 comment
Read more