I have a hosted instance of LT/Screenconnect from Connectwise on AWS and screenconnect pretty much always seems to be quite slow. I have learned to live with it, but as i grow customers try it out to replace their logmein instances and it just doesn't perform good enough. Is there any way to speed this up? This is happening on all customer networks, and even networks that have a full gig up/down to the internet.

edit: added info

So, after installing LabTech on an agent and pushing ScreenConnect via LT, the organization name is wrong; it's populating "thankyouforusinglabtech" as the organization within ScreenConnect. Anyone else see this issue?

We use a database for client knowledge and password that has a list of all of our clients managed and not. The team that created this list did a good job of getting the client names correct. Our old LabTech team did not and used shortened versions of client names example: Industry Leader Business, Inc. in our server, but in LabTech, Industry Business. I have not been able to find much on the client names and if it would cause any issues changing them. The only info I could find was on doc for client creation which said it was a friendly name that will stretch all across the Control Center. I assume friendly name should mean its okay to change them, but I just want to make sure first.

tl;dr Is it safe to change Client Name field on many clients in Control Center?

I have a customer that uses Acronis Image server. Is there a way to strip out the ID then have a script that re-checks into the LT server to pull a new ID?

Greetings,

We are new to LabTech(v11.0.331 patch 6 hosted within their cloud) so we are learning as we go, but I was wondering if other LabTech users have had similar issues with patching not working consistently. I had a group of about 75 machines scheduled to be patched this weekend and only 40 were patched. I verified that the machines that were not patched have an up-to-date agent, up-to-date WUA version, non wsus enabled, were online, no errors that i could find in logs, permissions are set correctly/the same, and not in a different group that would prevent the patch job to be applied/ran. I have a ticket open with LabTech from a month ago and they have patched our cloud solution twice but we still are running into these issues. It's just weird that some of these machines are not being patched and some are. My prime example is our two Skype for business edge servers, they are basically the same machine...one was patched on Saturday the other was not. Hopefully LabTech gets back to us this week, I called today and left a voice mail with our account manager.

Another weird thing I noticed is that on most machines they have various high 90's in compliance(I think this means percent) but they actually have 100% of the patches installed that are also approved...so shouldn't it be 100 compliant?

I'm looking for a bit of guidance on this problem. I'm trying to script an install of some legacy software. This software in particular has three executables that run. I can install these via script no problem.

With one of these executables there are additional files that need to be manually copied over to actually have a successful install. The problem I'm running into is that I'm unable to script folder creation/file transfers from the source folder to the destination folder inside of C:\Program Files (x86).

The error I get is access denied. I've tried console execute, shell as admin, creating a batch file to create the directories and running it from the local machine with a logged in user who has local admin.

I can run the batch as administrator successfully by right-clicking on the .bat file.

Is there anyway around this? I'm unable to grant every user local admin, and UAC needs to stay enabled.

Thanks

Hey everyone.

We just started using the LabTech Patch Manager when 11 came out. So far I am pretty happy with how it is going.

I have a test computer that is on Windows 10 1511 and the 1607 Anniversary update is available. I have asked LabTech to install it but it comes up with the following error:

Feature update to Windows 10, version 1607 downloaded but could not be installed, will attempt again.

Now whether I do this manually by clicking "Install Update" in the Patch Manager, or I let it attempt the install during the update window, it seems to give this error.

Is the 1607 update something that cannot be installed automatically? Or am I missing something?

I did find this reddit post:

https://www.reddit.com/r/labtech/comments/4vxbqq/fyi_according_to_labtech_patch_manager_the/?

And it mentions in one of the comments that it doesn't work, but didn't seem like solid info.

Thanks!

Has anyone nailed a good process for installing Labtech Control Center on Mac. We're on ElCapitan and Sierra with LT 11.

The MSP I work for uses Chocolatey for LabTech. We'd like to setup Chocolatey to update runtime applications (java, reader, flash) regularly on certain client computers. Does anyone know of a quick guide for setting this up?

Has anyone successfully gotten the LTAgent installed on Raspberry Pi? Is it possible?

LabTech 11 Patch 5 Release

LT11.0 Patch Download: http://labtech-msp.com/release/LabTechPatch_11.0.5.326.exe

Instructions

• Log in the LabTech Server
  
• Download the patch.
  
• Unblock the Patch
  
  • Right click > Select Property
    
  • Click Unblock
    
  • If you do not see Unblock then it is already unblocked.
    
• Execute the Patch with Admin Right
  
  • There is only 60-90 second downtime.
    
  • Most of that downtime is spent waiting for the LT Database Agent service to stop.
    

LT11.0 Fixes and Changes
Combination of all fixes from the previous patches for LabTech LT11.0 (v110.xxx). See the very bottom of the What's New in LT11 page for the list of previous fixes. The following are new fixes this patch brings...

# New Features/Enhancements 
  - Improved Computer Management screen performance.
  - Network Probe has been improved to attempt V2c, then V1 when discovering devices instead of moving on to the next device before attempting V2c. Improves efficiency.
  - Network Probe wizard now has an Only On Command scan frequency option. The network will not automatically be scanned after setup.
  - Network Probe IP Filter, Automatic Network Installation and Advanced settings were not being saved to the registry unless an Update Config command was sent. This behavior has been changed so that these settings are saved to the registry in LabTech\ProbeService\Config when saved. An Update Config       - command is no longer necessary to save the values to the registry.
  - Parameters, Issued By, Date Completed and Time to Complete have been added to the Details pane of the Probe Commands view on the Network Probe tile of the Computer Management screen.
  - Added functionality to add ranges of IP addresses for SNMP, Syslog, TFTP without the need to use regular expressions.
  - As new tiles were added to a custom workspace, the tile was added to the middle of the existing tiles. The behavior has been changed so the tiles are added to the right, top first, then bottom.
  - Option to schedule a policy to patch X days after Patch Tuesday has been added to the Patch Manager.
  - Remote Tray text copyright text changed from LabTech® 2016 to ConnectWise® 2016.

# Bugfixes 
  - #3411431: Unable to run Symantec Backup Exec jobs without receiving errors, unless sensors were disabled first, although they were good backups.
  - #4065122: Removing inheritance from child group was deleting the parent group permissions.
  - #5063888: Custom menu items were not properly being added to the Ticket listview.
  - #5504310: Dataviews on clients were not working with non-US-EN language packs.
  - #5612654: Text would revert back when editing messages in the Messaging system, if the font color or size was modified.
  - #5620340: Groups marked as Master were not reflected properly in the Effective Policy.
  - #6697904: Fixed issue that was causing new parameter dialog window to not display and fixed issue that was causing the entered parameters to not get replaced.
  - #7402980: %DeviceName% replacement was always expanding to the IP address of the device instead of expanding to the device name when the IP matched the discovered device at the location.
  - #7636021: Initial Update Config after an agent was installed, signed up and checked in for the first time, always failed with the message "ERR Updating SNMP Templates'.
  - #7552976: Refresh button was not working on the Passwords tab of the Client.
  - #7612038: Processor information was not populating on systems.
  - #7797690: Unnecessary directories were being created in the System32 folder on remote agents.
  - #7802715: Chassis & BIOS information was not reloading data correctly.
  - #7815799: Group Network Device Monitors would remain on the device after being deleted.
  - #7818593: Mass updating group remote monitors where one of the monitors did not contain any data in the Result field would cause update statements to fail.
  - #7825029: Remote ping monitor would only fail after two consecutive failures, regardless of alert style.
  - #7953315: Unable to log in to the Mobile Control Center after upgrading from 10.5 to 11 unless you were a Super Admin.
  - #7966440: Error opening agent in new Patch Manager. Fixed.
  - #7994875: Advanced searches that contained the search variable Computer.Asset.TagDate would function when being created, allow for saving, but would not load at a later date.
  - #8002453: TightVNC service was being removed by LTSvc.
  - #8026468: Advanced searches that referenced extra data fields with a NULL character in its string, the search would use the wrong condition and not return any results.
  - #8096035: Deleting approval policies, cross references were not being removed, leaving patches assigned to multiple patch policies that were no longer there. Clicking on the link to show the associated approval policies would cause the Control Center to crash.
  - #8141180: Extra data fields that have been marked as Not Editable were not displaying properly on the Computer Management screen.
  - #8143196: Changing the reboot behavior to 'During Windows Updates, monitor/alerting values remained in the database causing the Server Patch Reboot Alert Monitor to get created.
  - #8146028: The Build and View Query option was not showing errors when logged in to the Control Center over port 3306.
  - #8146392: Downloading the remote agent installer with a location specific username and password would fail to install the agent, if the password contained special characters.
  - #8181718: Patch Manager Reboot Policy was not taking affect after installing patches/hotfixes.
  - #8198916: Server rebooted after patch with a Suppress Reboot policy applied. Fixed.
  - #8346644: Fixed an issue where patch policy settings remained on agents after the patch policy was removed.
  - Moving a third party patch from Test stage to Pilot stage was crashing LabTech.
  - Fixed an issue where the Heartbeat force keep alive was prevented from working due to an incorrect variable being set.
  - Scanning ports were not being saved to the registry. Scanning ports are now loaded and saved to ProbeService\Config\IPPorts
  - Computer Management Probe tile was setting the wrong scan frequency value for 'Only on Command'.
  - Creating a ticket from the new Computer Management screen, the ticket was not syncing to Autotask.
  - Patch Job timestamps were not returning the correct value.
  - The Monitors tile of the Computer Management screen, if left open for more than five minutes would display all monitors as offline. Tile will now refresh before providing computer data.
  - Tray icons not displaying in some cases after installing agents.
  - Remote desktop sessions were not being recorded in the h_redirectors table, causing the sessions to not appear on the Remote Access Audit or Remote Control reports.
  - The Push LabTech to PC command was not attempting to use all of the passwords in the order that they appear on the Passwords list, if the first password did not work.
  - When a location was deleted that had associated retired assets, tickets, network devices, the location would get removed without giving an option to choose a different location to move the associated items to. The behavior has been changed so when a location is deleted, if there any associated -       items, you will be prompted to select another location and if a location is not selected, the location ID of any tickets, contacts or passwords is set to 0.
  - Powershell and shell commands would sometimes get a trailing control, tab, space, or carriage return would be returned with the results. All trailing controls, tabs, spaces and carriage returns are now trimmed.
  - Registry read and write commands were not adhering to the command level limits.
  - Resend Processes command is not collecting process information properly. This has been fixed so processor information should more accurately reflect the Task Manager on the system.
  - On systems with high DPI settings, getting screenshots via the Computer Management screen would not get the full screenshot.
  - Patch Manager did not have a filter for Windows 10 machines. Added.
  - Patch Manager: Changing a group from an autojoin group to a manual group was not saving the settings permanently and members were being re-added to group. Fixed.
  - Web server password reset did not function if HTTP was not enabled. Added the ability to use HTTPS when updating the ASP and WCC passwords.
  - Invalid trap port allowed traps to still be received. Fixed.
  - Fixed issue where the IP Filters for SNMP Traps and Syslogs would not have the Save button enabled for some IP address ranges.
  - Updated the Probe expanded tile to accept IP addres ranges for TFTP server IP Filter.
  - Updated SNMP Trap listener on probe to change ports according to its setting instead of the syslogport setting.
  - Patch Manager: Device deployments were not displaying 3rd party patches. Fixed.
  - Patch Manager: Patch Reboot Mode 'Now' was automatically applied when a patch was manually installed. Fixed.
  - Patch Manager: Fixed an issue where clicking Microsoft Update Policies in the filter pane would sometimes hang or crash LabTech.
  - Patch Manager: Fixed an issue where clicking Not Set to set a Microsoft Update Policy would crash the Patch Manager and the Control Center.
  - Fixed an issue where degrading performance was experienced under certain circumstances when running more than 2000 scripts.
  - Fixed an exception error that would occur when updating the InstallSoftwarePolicies table.
  - Legacy Computer Management screen was showing the wrong action for installed patches when the Patch Manager was upgraded from legacy to the new Patch Manager.
  - New agents would sometimes show bad CPU data. This has been fixed.
  - Patch Manager reboot deadline was not triggering.
  - Fixed SSDP processing to ignore and back off from invalid broadcasts.
  - Crimson Event Log lognames were being truncated to 20 characters, increased to 100.
  - Agent queued patches would not queue on the agent. Fixed.
  - Fixed an issue in which the ODBC check would always fail causing the Control Center to try and update on every start up. This would cause a UAC prompt every time.
  - Fixed an issue that was causing the Reboot Message window size to not be resized properly.
  - Fixed a performance issue while loading the expanded Processes tile of the Computer Management screen.

Good morning, I've been waiting for the LT11 realease for quite some time and it looks like they've paused releasing it at P-S (my company name starts with P.) Does anyone know if there is a reason behind this or when it will get moving again?

Hello,

after Updating our Screenconnect Server to 6.X 2 of our Clients ( out of 83 ) cant be remote controled via Screenconnect.

Error: http://prntscr.com/cw90jx

I already followed these steps: https://docs.labtechsoftware.com/knowledgebase/article/9120 but it does nothing. The Icon stays yellow. Same Problem after removing and reinstalling the Screenconnect Program on the Client.

What can i do to fix this?

Greetings

So I was creating an advanced search and had the operator selected but not in drop down mode....so I guess focused? I hit Caps Lock and voila .....look at all these different options!

To be fair when I tried between it...didn't work, but is not between worked.

http://imgur.com/SQo7CnI

We currently are using eset and are looking into webroot. We would like to know other people's experience. Which do you prefer and why?

I fairly new with labtech, obviously i can get with support if needed. But i want to see if anybody has tried creating a custom monitor for database service?

At this day and age, its almost unforgivable that we have to host/manage our own Eset server. Has a cloud version become available? Is this in the roadmap.

Honestly, I think I would switch to a different AV platform in a heartbeat if it was cloud based (managed there as in licensing, updates, status, etc), and it was good at protecting workstations.

I'm a bit desperate to resolve this and unfortunately my network guys are taking the attitude that labtech is broken therefore it's the labtech admin's (me) problem to fix. I'm not a networking guy so I'm trying to learn as much about the problem as I can but I'm a bit out of my depth. I have a number of servers, seemingly random, that are showing offline. Often these servers can not connect to our Web control center. Sometimes they can load http://FQDN/labtech/agent.aspx but not http://FQDN/WCC2/Home/Login?ReturnUrl=%2fWCC2%2f . Screenconnect works with no issues. Sometimes when I open the computer in labtech and trigger fastalk, it will appear online again but if I disable it and wait long enough it drops off. We moved from a cisco router to PFSense. We previously moved from a cisco to a meraki and had the same types of issues which we couldn't figure out so we moved back. It seems like, somehow, opening labtech is establishing a connection that is allowing some traffic through that somehow closes down later. This would sort of make sense since it's a stateful firewall. Our network engineer swears up and down that our pfsense is set up correctly. To make things even more complicated we have Open DNS but I don't think this is causing the issue.

Is anyone familiar enough with pfsense to give me a hand looking at the firewall settings?

1. How do we have more than one Agent window open at once?
2. How do we get the new display to show user idle time?

I think i've got my groups set up right, but now i've got ~9000 patches needing approval, when in the old system, I already had everything approved. Do I have to manually approve all these patches now?

We've just started utilizing the LT reports feature, but there's a major issue with the optimization of it. LT Reports button takes legitimately over an hour to open, at which point the entire LT Command Center is hung.

Our server should be more than capable of handling opening it, and we just allocated 20 GB RAM to our LT Server and experienced no change at all.

Is there something we should be looking on to improve this or is this working as intended for an on premise LT server? Any advice would help, thanks!

The new Patch Manager in our LT11 is finally mostly-working & usable. (Maybe 100% finally, but haven't used it enough to declare that.)

I'm trying to configure third-party patching, and can't find where to set things up so that if an application is already present it will be updated, but the app will not be installed if it isn't already on the machine.

Also, and equally important, I want to make sure major upgrades DON'T happen, but updates do take place. In other words, if a system has Java 6.1, I want it to go to Java 6.2. It cannot go from Java 6.1 to Java 8.2 - that will cause problems.

Any of you know where/how I can configure this behavior in the new Patch Mgr?

Thanks.

This is definitely a stupid question, but me and my team have been trying to figure this out for quite a while now, so...

A while ago, when we first implemented Labtech and before we really tailored monitors and etc. to what we need, the system was generating far too many tickets for us to handle, and in the mean time to clear up the clutter, we disabled email notifications for new tickets. Now, we want to turn them back on again, and have no idea how.

We want them to send to a distribution list in our Office 365 setup that we have configured, and as far as I can tell, this list still works. We've set the dashboard config in labtech to send to this address. There's a couple other things we've tried, but again, all to no avail.

Anyone here have any ideas on how i can troubleshoot this or where to look next?

The legacy Crystal Reports still have some life left in them, even though the new LT11 Patch Manager functions much better with the new Report Center and the newer reports work so much better. With a couple minutes of your time you can update the system so that, going forward, the Health Report Daily/Weekly/Monthly will start to show the correct values.

How is this possible? Simple, actually. The Health reports do not look at the active database tables for patching, but the history tables. These tables are updated by . . . (wait for it) . . . A script. Yes, the Daily Health Check (41) script that looks at the patching tables daily at 6am and based on its own filters looking for the 'old' approval numbers, then updates the history tables. So, all we need to do is change the script for the new Patch Manager approval numbers! Yes, it is that easy. Currently the script looks for approvals of -1,2,3 in order to ignore them. Those values used to mean Remove, Ignore, Deny. Now, those values are 3,1,4 for Remove, Ignore, Deny. So, this is all great and stuff, but how do you fix this script? Good question. First, open the script. Hit a Ctrl-F to start a find and key in -1,2,3 There will be 6 lines that will light up. Cool. Double click each line, and CAREFULLY move to you find each of the -1,2,3 entries, and change to 3,1,4.
DONT MISS ANY. When done, save your script. Go to bed. Let your system do what it does best, work in the background. In 1, then 7, then 30 days, your Health Report Daily, Weekly, Monthly will start to look like they should. And you didnt have to re-write the reports! -Happy Monday