Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

zubz last won the day on August 29

zubz had the most liked content!

Community Reputation

4 Neutral

My Information

  • Agent Count

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We recently attempted to deploy automate on Citrix Xenapp servers in Azure and it completely rooted the machine. CPU high, server unresponsive, published apps unavailable. Has anyone had any success with deploying agents in Citrix Xenapp Azure?
  2. You sir are my hero!!! It's been 3 months trying to fix this problem and couldn't monitor a client sharepoint server. Connectwise unable to resolve... (they have not been able to resolve a lot of my issues recently) Thank you so much!
  3. Anyone having the problem where the deployment manager says "Device failed deployment readiness checks"? I've got the password set at: Location Probe Deployment Manager LTService Password doesn't have any special characters either. Not sure if anyone has run into this issue before? Seems to be happening accross all our gen2 probes.
  4. I have the same issue with one of our servers. I had labtech work on this for 3 days straight until they gave up and couldn't tell me what the issue was. Funily enough it only happens for one particular server for a client (Sharepoint server). We've tried all sorts of things - .net repair, av exclusions, copying registry from another working server etc etc. I'm at a loss and i've had a same issue since upgrading from 120.451. We also have this issue on some of our other servers now as well. We use Citrix MCS and use a script to remove MAC / ID / Password from registry before shutdown. This used to work for years but since upgrading from 120.451 it has now stopped. We have reinstall LT on these servers manually everytime we refresh the mcs clones. LT have not been helpfull at all in figuring this one out. Anyone else having this issue? or have had any luck getting this fixed?
  5. zubz

    My Dashing NOC / HUD

    I've been getting a bit of people messaging me about this - Just thought I'd add my "Hotness w /sound" widget. This widget allows me to play a sound when the counter changes. See the 3 widget files attached. Place these in the folder /opt/dashing/rmm_hud/widgets/hotnesswsound Place your Mp3 files in this folder: /opt/dashing/rmm_hud/assets/images/mp3/ (the ERB file refers to this directory as /assets/mp3 (the /assets is an alias to the images directory) in your /opt/dashing/rmm_hud/home.erb You can use the widget like this: <li data-row="1" data-col="4" data-sizex="1" data-sizey="1"> <div data-id="urgenttickets" data-view="Hotnesswsound" data-title="New Urgent Tickets" data-moreinfo="" data-valchangenotoksound="/assets/mp3/demonstrative.mp3" data-cool="0" data-warm="1"></div> </li> Adjust the cool and warm values for when you want the sound to be played. (mine plays a sound at 1 and every increase after that) When it's 0 it's green. I pull my urgent tickets from CW Manage. My jb file for urgent tickets looks like this: require 'tiny_tds' SCHEDULER.every '30s', :first_in => 0 do |job| client = TinyTds::Client.new(:username => 'xxxxx', :password => 'xxxxxx', :host => 'xxxxxx', :database => 'xxxxx', :port => '1433') rs = client.execute("Select s.Ticketnbr, s.status_description, s.company_name, s.Summary, s.date_entered_utc, s.minutes_waiting, s.Urgency from v_rpt_service s With (NOLOCK) JOIN sr_service_calculated sc With (NOLOCK) ON sc.SR_Service_RecID = s.TicketNbr WHERE s.board_name like 'Team%Support' and s.Closed_Flag = 0 and (s.date_responded_utc is null or s.status_description like 'New%') and sc.SLA_Status_text <> 'Waiting' and s.parent is null and s.Urgency like 'Priority 1%' Order by date_entered_utc desc") current_count = rs.count if rs.count > 0 resulttitle = rs.first['company_name'] lastupdate = "#" + rs.first['Ticketnbr'].to_s else resulttitle = "" lastupdate = "" end send_event('urgenttickets', { value: current_count, lasttitle: resulttitle, lastupdatevalue: lastupdate } ) client.close end You will have to change the "WHERE" clause if you're going to use the above as the Board,Urgency and statuses might be different to your Manage environment. Also you will need to setup a SQL user to your CW database and add details in the jb file. (You can setup a limited access read only user) (Sorry no API calls with DASHING) hotnesswsound.coffee hotnesswsound.html hotnesswsound.scss
  6. Does this work with 6.5+ of Connectwise Control? Do you need a signature for the plugin?
  7. We have something like this set up. We use connectwise templates that create tickets on a "Maintenance" board in a specific status. This status has a templated email that sends an email to the contact (set from the connectwise template) which basically lists the maitenance notification. We use the "srnextscheduledate and srnextscheduletime" tag in the template to show the date and time in the email that gets sent out. Because our maintenance schedules are regular we can use the template to generate a ticket on say 7 days before the first Saturday of every month which will set the schedule to the First Saturday of the month at 12aM to 5am. This ticket gets created on the maintenance board which is set to a specific status that emails the contact. We have different templates for different days (eg one template for Sunday one for Saturday and 2nd Saturday or 1st Saturday etc) We then reference these in the Company tab and it gets added as part of the onboarding. See below EDIT: It's a bit hard to to a time range using the CW templates as when you use the "srnextscheduletime" it only shows the Start time (not the end time) So you may need to play around with the template based on how you do maintenance eg is it always between a certain time for all your clients or would you only list the start time and then say "Maintenance will last for x hours" - that way you can use the "srnextscheduletime" inside the email if you're doing different start times for different clients.
  8. I found that the values in the following key: HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\ ConsentPromptBehaviorAdmin = 0 (User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode) EnableInstallerDetection = 0 (User Account Control: Detect application installations and prompt for elevation) EnableLUA = 1 (This setting will enable UAC) Set the above keys to have UAC enabled but allow you to bypass UAC on an Admin account. Sometimes there are things that will cause UAC to fail so I have a scriptlet that enables the built in administrator account - runs the specific command as that user using the Shell as User or process execute as user command then disables the account straight after. (The built in administrator account will always bypass UAC by default)
  9. zubz

    My Dashing NOC / HUD

    I guess the table is the least common one so I'll run through it here, If you've got Dashing installed (Linux setup - not plugin setup) I can help. The below assumes you have dashing installed on a Linux server and the MySQL connector for labtech already configured. There is a sticky on the dashing forum on how to set this up. First you need to install the table widget: dashing install 9c7cb3030f63ad10e517 I then did some customisations with the table widget to change the colours a little, you can adjust the colours however you want. Edit file widgets/table/table.scss Change the colours at the top to this: $background-color: #000000; $value-color: #fff; $title-color: rgba(255, 255, 255, 0.7); $label-color: #e2e2e2; $moreinfo-color: rgba(255, 255, 255, 0.7); $th-background-color: #7c7979; $tr-odd-background-color: #704c4c; $tr-even-background-color: #8e3737; $tr-hover-background-color: #858585; And then for the icing on the cake - I will share with you my rb job file (I named it jobs/drv.rb). If you understand mysql you can tweak the filters at the end however you want. The below excludes clients with audit plans and displays the following: - 5% or lower free space - 3GB or lower free space - Less than 10% and less than 5GB (this is to account for small drives) require_relative 'my_db.rb' SCHEDULER.every '60s', :first_in => 0 do |job| db = MyDb.conn sql = "SELECT * FROM ( SELECT clients.name AS clientname, computers.NAME AS computerslist, letter, volumename, size, free, ROUND((free/size)*100) AS Percentfree, free AS RemainGB FROM `v_drivesinternal` vr JOIN computers ON computers.computerid=vr.computerid JOIN v_extradatalocations ed ON computers.locationid=ed.locationid JOIN clients ON clients.clientid=computers.clientid WHERE computers.os LIKE '%server%' AND vr.missing=0 AND vr.model NOT LIKE '%Expansion%' AND ed.`Audit Plan` IN ('None','') )AS Results WHERE size <> 0 AND free <> 0 AND ( Percentfree < 6 OR RemainGB < 3 OR (PercentFree < 10 AND RemainGB < 5) ) ORDER BY RemainGB ASC LIMIT 9" results = db.query(sql) servers = results.map do |row| row = { cols: [ {class: 'left', value: row['clientname']}, {class: 'left',value: row['computerslist']}, {value: row['Letter']}, {value: row['RemainGB'].to_s + "(" + row['Percentfree'].to_s + "%)" } ] } end hrows = [ { cols: [ {class: 'left',value: 'Client'}, {class: 'left',value: 'Computer'},{value: 'Drive Letter'},{value: 'FreeSpace (MB)'} ] } ] send_event('drv', { hrows: hrows, rows: servers } ) In your /opt/dashing/rmm_hud/dashboards/home.erb - add the following: ( you can change the row/col ids if you like) ( My dashing is installed in /opt/dashing/rmm_hud/ ) <li data-row="2" data-col="1" data-sizex="2" data-sizey="1"> <div data-id="drv" data-view="Table" data-title="Drive Free Space Alerts" data-max="5"> </div> </li> Restart your dashing service and you should now see the table. You may need to customise the layout. sudo systemctl restart dashing.service I don't have time to go through the hotness customisations right now - but seriously PM me if you're interested.
  10. Thought I'd share my screen with everyone. It's pretty custom for our company however PM me if you would like any details on any of the widgets / setup below. I use the hotness widget but I added an additional section below the number which gives us the latest value from the sql query. The table widget I found online and customised it a little. edit: I followed this post for the base Ubuntu Install . See my posts below on how to setup the Table dash
  11. Having issues with tiny_tds... I've installs freetds but still getting compile errors. xxx@xxxx:/opt/dashing/rmm_hud# sudo apt-get install freetds-dev Reading package lists... Done Building dependency tree Reading state information... Done freetds-dev is already the newest version (0.91-6.1build1). The following packages were automatically installed and are no longer required: libcgmanager0 libnih-dbus1 mountall Use 'sudo apt autoremove' to remove them. 0 to upgrade, 0 to newly install, 0 to remove and 6 not to upgrade. xxx@xxx:/opt/dashing/rmm_hud# gem install tiny_tds Building native extensions. This could take a while... ERROR: Error installing tiny_tds: ERROR: Failed to build gem native extension. current directory: /var/lib/gems/2.3.0/gems/tiny_tds-1.0.4/ext/tiny_tds /usr/bin/ruby2.3 -r ./siteconf20160929-16521-5740vn.rb extconf.rb extconf.rb:14: warning: already initialized constant OpenSSL::SSL::VERIFY_PEER checking for sybfront.h... yes checking for sybdb.h... yes checking for tdsdbopen() in -lsybdb... yes checking for dbanydatecrack() in -lsybdb... no Downloading freetds-1.00.tar.bz2 (100%) Extracting freetds-1.00.tar.bz2 into tmp/x86_64-pc-linux-gnu/ports/freetds/1.00... OK Running git apply with /var/lib/gems/2.3.0/gems/tiny_tds-1.0.4/ports/patches/freetds/1.00/0001-mingw_missing_inet_pton.diff... OK Running 'configure' for freetds 1.00... OK Running 'compile' for freetds 1.00... OK Running 'install' for freetds 1.00... OK Activating freetds 1.00 (from /var/lib/gems/2.3.0/gems/tiny_tds-1.0.4/ports/x86_64-pc-linux-gnu)... checking for sybfront.h... yes checking for sybdb.h... yes checking for tdsdbopen() in -lsybdb... yes checking for dbanydatecrack() in -lsybdb... no ----- freetds is missing. Do you have FreeTDS 0.95.80 or higher installed? ----- *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/usr/bin/$(RUBY_BASE_NAME)2.3 --help --enable-lookup --disable-lookup --with-freetds-dir --without-freetds-dir --with-freetds-include --without-freetds-include=${freetds-dir}/include --with-freetds-lib --without-freetds-lib=${freetds-dir}/lib --with-sybdblib --without-sybdblib --with-sybdblib --without-sybdblib --enable-system-freetds --disable-system-freetds --enable-system-iconv --disable-system-iconv --enable-system-openssl --disable-system-openssl --enable-gnutls --disable-gnutls --enable-openssl --disable-openssl --with-freetds-dir --without-freetds-dir --with-freetds-include --without-freetds-include=${freetds-dir}/include --with-freetds-lib --without-freetds-lib=${freetds-dir}/lib --with-sybdblib --without-sybdblib --with-sybdblib --without-sybdblib To see why this extension failed to compile, please check the mkmf.log which can be found here: /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/tiny_tds-1.0.4/mkmf.log extconf failed, exit code 1 Any ideas?
  12. --- removed --- Posted in wrong thread
  13. Hey Cubert, How's this tracking along? I'd love to be part of the development and testing. We actively use a separate Icinga box so I'd be very very interested in testing this with you guys
  14. I ended up contacting LT support and they said that its due to the pushed flag not being cleared. I created a script that runs everyday to clear the pushed flag on patches that have failed. It still seems to happen every now and again but it generally resolves itself now on the next push attempt. Apparently labtech will only try to push a patch twice, and won't try again. This can have an affect on other agents as well if patches fail more than once. The tech said I just need to make sure the push failures are cleared to avoid the issue.
  • Create New...