Creating the DB23 to GBS Lead – the GBS8200 comes with a lead which can be soldered straight to a the pins of the DB23 connector – the Wiring diagram below shows you which wires need to be connected – Yellow and Brown are not used in this setup and can be removed by pressing in to the rectangle tab and pulling the wire out.
The 680 ohm resistor is soldered inline on the grey wire and heat-shrink is applied to keep it protected
GBS8200 + ESP8266 (Optional but recommended)
If you build the optional GBS Control unit, the ESP8266 joins on to the GBS8200 like the following pictures and gives you finer control (via. a webpage) and better picture output whilst using the GBS8200
in Solarwinds SAM I was getting this error when trying to check for a running Process using Solarwinds Agents + WMI
After a bit of digging I found that on the computer in question, Opening windows Performance Monitor would give the error
Unable to add these counters:
\Memory\Available MBytes \Memory\% Committed Bytes In Use \Memory\Cache Faults/sec \Memory\Cache Faults/sec \PhysicalDisk(*)\%Idle Time \PhysicalDisk(*)\Avg. Disk Queue Length \Network Interface(*)\Bytes Total/sec”
Open CMD as administrator CD C:\Windows\System32 lodctr /r CD C:\Windows\SysWOW64 lodctf /r lodctf /q This will query the Performance Metrics library’s installed on the machine Copy this list in a notepad and check for items that are disabled For each disabled entry you will need to run the command lodctr /e:<providername>
Once done you should be able to use your monitor in Solarwinds
To use the Java Client (Not tested as I don’t have Java) – you need to select connect with Java SSH client. Set the Private key path as the location you saved you key pair and tick Store in browser cache. Then hit Launch SSH Client Accept the terms for everything, Press Next a few times. When the MindTerm screen opens, hit “Enter”
Setup Teamspeak 3 server on Ubuntu 18.04
Run the following via SSH to upgrade your Distro sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade
Next create a user to run Teamspeak using the following command sudo adduser --disabled-login teamspeak sudo su teamspeak cd /home/teamspeak
Run the following commands to: Download Teamspeak, extract it and tidy up. wget https://files.teamspeak-services.com/releases/server/3.9.0/teamspeak3-server_linux_amd64-3.9.0.tar.bz2 tar xvfj teamspeak3-server_linux_amd64-3.9.0.tar.bz2 cd teamspeak3-server_linux_amd64 cp * -R /home/teamspeak cd .. rm -r teamspeak3-server_linux_amd64 rm teamspeak3-server_linux_amd64-3.9.0.tar.bz2 touch .ts3server_license_accepted
Next start the TS3 Server with the following command ./ts3server_startscript.sh start It should start up – copy out the text that spits out as it will contain your access token and Server Query admin account details – Don’t lose it!
Press Enter to return to the command prompt Finally stop the server and Exit the Teamspeak user with the following commands ./ts3server_startscript.sh stop exit
Now we will create a restart script using systemd to restart it on boot. Run the below command (This should open a blank pape) sudo nano /lib/systemd/system/ts3server.service
Copy the below and paste it:
[Unit] Description=Teamspeak Service Wants=network.target
I’ve been working on a system to deploy a Master Windows 10 image from MDT to remote sites that have no direct LAN to LAN connection. And also update the Asset Registry at the same time.
MDT / WDS / PXE Server
The MDT / WDS / PXE server is hosted on the HQ LAN, this can only PXE / Litetouch computers on the same LAN.
SyncThingSyncTrayzor makes it possible to share the DeploymentShare which hosts the MDT image with other sites by making a receive only sync on the remote file servers. Setup the DeploymentShare$ on the remote site as you would be on the local LAN and install Deployment Workbench / ADK for completeness.
This gives the Option to use the LiteTouch script to upgrade computers remotely
SnipeIT + API
SnipeIT is a free open source application for asset management – by itself it’s a manual process to enter assets and track them. It does have an API to use however which allows you to automate this process.
Marksman creates a new asset in SnipeIT from the local computer details but cannot update an asset already in the system.
Recon (Created by me but unreleased as of yet) updates the asset details in SnipeIT from the local computer details.
This can be run as a one off, inside the Litetouch process (So when a computer is imaged the asset details are automatically put in to SnipeIT).
Logmein One2Many allows you to run an exe file on all controlled computers, so putting in Marksman and Recon you can update your computer asset database with one click.