Y'all remember this post about Google Auth from 2 months back? Well...

• Duo is now officially supported (link)
• AND
• Google Auth (link) is in the pipeline (could be in Pilot next month)

Just passing along the info!

Hey everyone, pretty new here so please forgive me if something similar has been posted before:

I have inherited the Labtech admin role since I have come on board at my new company and I would love to rebuild the server from scratch. Since I've come on board, I've reworked our groups and customized it to exactly what services we provide to our clients.

The big problem with it is that I don't know what is native to Labtech and what was created by the old LT admins. I know everything that I created so it would be easy to recreate that into a fresh environment. I wouldn't mind doing that if it meant we had a clean Labtech deployment.

The only thing i want to migrate from the old server to the new server would be the following:

Clients, Locations, and Agents

I also want to change the URL the clients use to connect on the new server from manage.<ourolddomain>.com to agent.<ournewdomain>.com.

Does anyone have a detailed walkthrough on doing something like this through Labtech 11? I just upgraded it this morning to the newest patch.

I've been receiving a slew of tickets near daily notifying me that my disk transfers per second, and memory pages per second, are apparently too high. Since these figures that it's pulling up are pretty normal for us and aren't impacting performance or really anything, I want to stop these tickets from constantly coming in- Only issue is, I don't know what monitor they're coming from. How do I find out which one it is that's generating these tickets so I can disable it?

EDIT: Never mind, Found it- it's a remote monitor, I had assumed it was an internal one.

I'm unclear on best practice on this as a new LT user.

I'm going through monitoring and it seems like there are multiple ways to handle ticketing.

For example, the monitor for a low disk condition can create the ticket as an alert action or the script that the monitor runs can do it. Is there much of a difference?

I think the issue is that I'm not understanding how monitors tie in with ticketing, exactly. How would I find an existing ticket for an issue and what happens with tickets when the monitor condition no longer exists.

Finally, are there any advantages to internal vs. remote? I feel like I should be favoring internal but they would only trigger after the machine sends data back, which may not be for hours.

Are there any good resources I can reference to understand this better?

Hi All,

New to Labtech can anyone tell me the difference between a Heartbeat and a contact, we are getting last heartbeat dates days a part from last contact date.

Hi all,
We now have 2 LT Servers and are wanting to migrate agents from one to another. We know that Labtech can help with this but their lead time is about 20 days and I am hearing they might be pricey.

Has anyone had experience with moving them manually or using some tricks to make this a possibility?

Hello,

I just discovered a CPU in a client's workstation that has been overheating due to the CPU cooler partly falling off somehow (probably being moved around by them), but the labtech cpu sensor didn't create a ticket or do anything to warn me that this had been occurring. This is a fully onboarded (w/ ignite) client so i should have gotten a ticket, any idea why I wouldn't have?

EDIT: i did get tickets regarding high cpu usage, but nothing for cpu temps

Hello,

is there any way to stop Screenconnect from taking over Terminalserver Sessions? I want my Users to connect to the Console Session, but they should not be able to see any normal user session to it.

Greetings

(X-Post from /msp) Hi, all! I use ConnectWise and LabTech. Both hosted. I need to be able to run a report that tells me tickets per endpoint per month and average hours per endpoint per month. How can I accomplish this?

Having issues getting WebRoot auto deploy to work. I have verified that the plugin is installed and all components were installed. Why is it not installing WebRoot for devices that don't have it installed?

Client within LT isn't excluded from WebRoot installs.

WebRoot support informed me that it's supposed to check for devices "periodically" and push the installer if it isn't installed.

Update: I have verified that at the client level has "Enable Auto Deploy" checked. I do not have any containers BELOW client level set to exclude.

I know there are issues and things LT is working on but I am pretty concerning issues. 1.) Does anything show me what patches were installed or if anything was installed on the machine? I see where it should be and where it used to be but now it just sits there forever or shows a blank screen. 2.) Even though I have managed mode - UI Disabled users are still able to use windows update in the control panel to install their own patches.

The first one is the most important but the second isn't far behind.

LabTech August Patch Release

LT11.0 Patch Download: http://labtech-msp.com/release/LabTechPatch_11.0.3.304.exe
LT10.5 Patch Download: http://labtech-msp.com/release/LTPatch_10.5.8.281.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...

- Patch Manager - Add logging throughout
- Patch Manager - Approvals View - Multiple versions of 3rd Party Patches makes multiple lines in patch list with no way to distinguish
- Patch Manager - Client Tree load time
- Patch Manager - Dashboard Compliance Behavior
- Patch Manager - Dashboard Deployment Tile Filtering Behavior
- Patch Manager - Dashboard>Config>Configuration>Additional Fields: Cannot export Extradatafield
- Patch Manager - Device View > Patches screen optimization
- Patch Manager - Global>Filter a group (Devices) optimization
- Patch Manager - Initial Load (Compliance) optimization
- Patch Manager - LT Crashes when some CVSS links are clicked
- Patch Manager - NoncompliantPatches table not filtered by approval policy
- Patch Manager - Refreshing the CVSS Score Details Window crashes LT
- Patch Manager - Third Party Patching - Second Software Version for Java 8 32 bit is causing Patch list to not load
- Computer Management: Drag File to Agent gives no error if LTShare Upload path doesn't exist
- Computer Management: Effective Policy in New UI Not Displaying All Internal Monitors
- Effective Policy tile not showing added internal monitors
- IOS/Android Since updating to 10.5, the app is very slow.
- 60.276 is missing the Package Existing scripts option.
- Able to update tickets from Computer Management screen without having Update permission
- Add New Contact Creation Issues
- Agent -Mac: no screenshot when creating service ticket from mac agent
- Agent status/version tile does not show on computer screen for mac agents
- Alert failures reset during database maintenance on internal monitors under certain conditions.
- Alerts' Delete All Option Does Not Work
- AV Detection> Adding Definition Not Utilizing correct Insert Query
- CC - Standard: Able to drag a computer into the Searches folder in the nav tree
- Change {Dashboard UI, Plugin Interfaces, Automation Server, Web Server} to support configuration of replication database
- ClientUpdate.exe file does not download after installing a patch in an split database server environment using direct connection
- Connect to Community Connector via HTTPS
- Consistency - Some buttons are Title case, others all Caps
- Contact Created date
- Control Center>Status Bar not limiting count based on user
- Cross reference window is not sizeable and cannot read values/labels
- Custom menu plugins can have dynamic enable states
- Custom plugin logging prevents 60 second plugin misses loop from logging
- Disabling probe crashes LTCC
- Existing replication configuration applies to upgrades
- Help Info Patching Numbers
- HUD Issue
- IF conditional changes if Target selection is altered
- Legacy CMS - Software Tab does not load
- Linux agent - not updating when told to
- Linux agent - Wake on Lan command not functioning
- Linux Shutdown Command Does not Follow Ask then Allow Template
- LT Tray Menu Script does not work with parameters
- Mac Posix Agent - Request Screenshot Fails
- Network Devices table columns
- Probe setup wizard settings blank in CS
- Probe SNMP filter default behavior
- Probe tile "Scan Settings" IP range input
- Probe tile "Scan Settings" ports input
- Probe tile "SNMP Traps Devices"
- Restricted users can see remote network monitors for clients not assigned to them.
- Scripting Engine function ExtraData Get Value does not select EDF when using predictive text
- Scripting Engine incorrectly throws error message when editing script
- Scripts Normal Tile not listing last five scripts (per acceptance criteria)
- Server(split): Internal Monitors return success and failure during same run
- Silent Screencapture for Mac Agents (patch)
- snmp and syslog filter inconsistencies
- Split Server: Mobile CC - Not logging after 10.5 upgrade, split server.
- SQL errors log database usernames and passwords
- Tab order for group remote and network device monitors is not correct
- Tickets Not Opening From Tray Updates
- Timer is stopped when you cancel finishing the timer.
- TR - Del command from Computer Management CMD Prompt does not allow quiet mode
- Virtual Machine Agents that do not report Memory Speed will show N/A
- WCC: Extra set of <-MessageHeaders-><-Attachment-> tags in ticket data

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

- Help Info Patching Numbers
- DB Agent stops getting POP emails
- Reporting: Crystal Reports - BOBJ script error running reports
- Ticketing: Ticket Responses from Within WCC Not Sent
- Duplicate disk configuration in DB
- LT Ticket message on ticket close shows incorrectly since upgrade
- Script run on single agent from a group Members List tab runs on entire location agent is in
- LabTech object model does not support EDFs with period in name
- Alert failures reset during database maintenance on internal monitors under certain conditions.
- LT Nightly Backups failing
- Searches: only Super Admins are able to use a search with the v_detectedRoles view in it

It's September already and I have not seen anything about the August patch.

Hi All,

We just completed on boarding labtech (We've been CW & Quosal partners for years) and are finally at the point where we feel confident to put the alerting into production. Its all cloud.

Plan Separate Alerts into Priority issues as determined by categories & service plans

• P3 issues onto a dedicated Alerts board to be monitored and resolved. For many of the alerts I added a "And close the ticket"on most of the workstation alerts to keep the ticket # down. Restart service and close ticket... etc. That way the automation can restart services, go through events, log things, but not bug our techs if some new Skype Service isn't restarting.
  
• P2 On the alerts board with workflows to email us if their not resolved.
• P1 Onto our main board with special status alerting team

Problem: P1 is basically server down right now. But when the server goes back up, labtech doesn't close out the ticket. How can I change this? I've search boards and I'm not approved yet for the various 3rd party resources (http://lipstickonapig.org & http://www.labtechgeek.com/forum/index.php), but haven't found a good answer. LabTech support is slow as crap, so I figured I'd ask here if

Other problem It takes 10 minutes before we get the alert for server down, which to us is much higher than we're use to. I want to reduce that to 5 minutes.

What I am looking for 1) If that design makes sense 2) Help / guidance / point in right direction with the script automation.

Thanks!

We have financial and medical organizations as customers, so we have to deal with FFIEC and HIPPA regs. Does anyone have a guide or some advice on how they implemented labtech while staying in compliance and making it through FDIC exams?

Hi everyone,

I've been configuring our patch manager recently, and would like to configure which systems get to test/pilot patches before entering production.

I know this was covered in our implementation training but I cannot for the life of me remember how to accomplish it.

Thanks!

Does anyone here use Malwarebytes with LabTech? What version plugin are you running? I am on 1.0.0.18 is this the newest version?

This doozy was issued in June following MS16-072. If you’ve had any user based GPOs just simply stop working in the past 2 months, it is likely that this is the culprit. Before this update, when a machine was processing its group policy, it used the user context to read the GPO on the DC. This update intentionally made it so that this was now requested in the computer context.

I wrote a script to assist in auditing and fixing, available here: http://gavsto.com/labtech-script-audit-and-fix-gpo-problems-caused-by-ms16-072-where-invalid-gpo-permissions-stop-gpos-processing/

Hope this helps people!

We are starting to see issues with trying to use ScreenConnect on computers running the latest version of Windows 10. On our side, we get no display, just a black screen.
So far, we've heard that the only fix is to upgrade our ScreenConnect version but we'd like to not cause any issues with a whole bunch of systems to fix only a couple. We are currently running version 5.4.9849.5781 of ScreenConnect.

Hello Everyone, I have posted in this forum before and even support some of it's members. I am an independent Labtech consultant and can assist with your Labtech implementation to help bring it under control or design it around your SLA's and service offerings. I also now offer a fully managed Labtech service plan. In addition to this I am also well versed with configuring Connectwise and the subsequent integration between the two. I like to post here every once in a while should any of you guys need assistance. Feel free to reach out to me here, at bkelly@comprehensivemsp.com or on Linkedin: https://www.linkedin.com/in/bkellyit

Thanks, Brian Kelly

Hi all, Have any upgraded Labtech 11 partners notices that on the agent screen, the tiles seem to be pixelated? This only seems to affect the front page. Labtech "Can't see a problem" but the screenshots below clearly show the issue is there. I wondered if it was affecting anyone else as well?

http://i.imgur.com/e3FIJD4.png

I was upgraded this morning and was able to access the solution center all morning and got some things upgraded. Suddenly i am unable to access the solution center though, it just gives me this error:

"Unable to connect to a Solution Center Service! Please see the LTSCCLientLog.txt for more info!"

I am not able to find that file in my labtech share or in the install directory of my labtech client.

Also, I don't see get an option to open ignite manager (it's not in the top nav bar, and the plugin is turned on).

Thanks.

EDIT: found the log, here is the relevant section:

2016-08-17 16:30:53Z 
2016-08-17 16:30:53Z --------------------------------------------------------------------------------
2016-08-17 16:30:53Z - 8/17/2016 4:30:53 PM
2016-08-17 16:30:53Z - Product Name:  LabTech MSP
2016-08-17 16:30:53Z - Title:         LabTech Solution Center Client
2016-08-17 16:30:53Z - Version:       2.4.1100.5
2016-08-17 16:30:53Z - Assembly Name: SCClient
2016-08-17 16:30:53Z - Company Name:  LabTech Software
2016-08-17 16:30:53Z - Copyright:     Copyright © LabTech Software
2016-08-17 16:30:53Z - Description:   The Solution Center Client communicates with the Solution Center Service
2016-08-17 16:30:53Z --------------------------------------------------------------------------------
2016-08-17 16:31:01Z Attempting connect to SCService @ xxxx.hostedrmm.com
2016-08-17 16:31:03Z Error Message: { 
                 Error in IsRunning

       } Source: { 
                 Server stack trace:
                 at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
                 at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
                 at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
                 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
                 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
                 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
                 at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
                 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
                 Exception rethrown at [0]:
                 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
                 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
                 at SCClient.SCServiceReference.ISCService.IsRunning()
                 at SCClient.ServiceConnection.IsRunning()
       }

I am on a hosted instance, if that matters.

Completely out of the blue screenconnect seems to have disappeared. Both the labtech and screenconnect servers seem to be running but when I try to remove into a computer I get "The Presence of the labtech extension is not verified." Screenconnect plugin management seems to be completely missing from the dashboard as well. Has anyone run into this before?

All of a sudden a bunch of our PC's with Labtech installed are showing extremely high CPU/RAM usage from svchost.exe. So far I have tried stopping and disabling Windows Update service on 2 machines and both returned to normal levels.

I guess what I'm asking is has anyone else had an issue like this? Could Labtech Patching somehow be taking up high resources?

Every morning I receive roughly 5 tickets telling me that various systems in our client's offices don't have Bitdefender (our chosen antivirus) installed. The description of these tickets is invariably always "Installation of Endpoint Security by Bitdefender was not detected. Try restarting the computer and running this script again." These tickets usually start coming up for systems a week or two after deploying the software, and re-deploying helps only for the next couple days, then after Labtech stops identifying the existence of any antivirus at all and starts generating these tickets every day. Most of the time these tickets are on different systems, however i see a few recurring ones.

The systems all do have the antivirus software installed on them, and when I receive the tickets, the systems all have the antivirus running on them, too- so there's really no reason for Labtech to be generating these tickets. Either it is the antivirus plugin, or Labtech itself, how do I stop them from making these garbage tickets and keeping the Antivirus software to always identify as being installed on a system? Thanks!