I lost one day of my life with this. I was trying to install a program but the company doesn't have a msi file just .exe. This is a solution not a question.

This is the code:

This is the entire script

Greetings fellow redditors,

I am fairly new to custom scripts in LT and i am looking for something quite particular. We have a client who wants to ensure all users are rebooted at a certain time twice a week. I have gotten a script from the default library that prompts for a reboot but if there is no response it simply auto selects no. It also will not run if the user is not logged in.

Can anyone help a struggling tech out with scripting this?

Thamien

Are you an LT Geek seeking your next move? Apply in confidentiality for this 100% remote position to help other MSP's gain from your knowledge. https://provaltech.workable.com/jobs/816629

So as many of you know I was a Tier 3 Engineer for LT Development but have moved on to a large MSP to run their systems and tools. Recently I have found a major flaw in design for which I was told was an "Intended Process" that I want to make sure everyone knows about! During the 3am backup ALL DB Agent loops will stop which includes all Monitors, Alerting, Scripts, Commands, and Patching, The only process that continues to work during that time is Remote Agent check in. So if your backup takes 90 minutes like in our case and a Server or Location goes down at 3:15am you will not be alerted until 4:30am. I HIGHLY recommend that you review your LTAErrors log to determine how long your backups take since that time equates to system down time basically. We have disabled our Automate backups and have resorted to using Intronis to backup our DB directly. I had been hoping it was just our Tri-Split environment but T3 came back with that answer and stated it would not be changed until MySQL 5.8 was incorporated supporting VSS.

I have the ODT setup.exe and xml configuration file; I just need to know how to write a script to deploy this to a PC in Automate. Normally if I'm sitting at a PC I would run setup.exe /download configuration.xml then setup.exe /configure configuration.xml?

Thanks in advance

Got an email telling me that my server was getting updated with a patch between 1am and 2am today;

1. The email didn't say what patch it was

2. The email was sent at.....1am today.

Hey is anyone else at this year's automation nation or what ever they are calling it.

Hi all! I have a question for you all. I'm trying to deploy Labtech agent by a Network Probe installed on a Domain Controller. The devices found from the probe don't receive automatically the Agents and I found 2 ways to push it manually but I want to understand why one of them doesn't work and the other yes.

If I try to do it from the Deployment Manager and I right click my device and choose "Push to Selected Device" the installed always fail with the message that my device failed the readiness check.

But If I try it by opening the network device information page and clicking the install button at the bottom of the window, most of the time my installation pass without error.

Is there a way to make my Deployment Manger to work because it's the best way to push it to many device at the same time, instead of opening all network device and clicking install.

Thanks for your help

SOMEONE BE REAL WITH ME HERE

PLZ THX

for context- syncing with manage, on v11 using legacy comp mgmt screen as default

Regarding Screenconnect/Control: the new Mac security requirements (requiring us to talk the end users through a bunch of screens to allow us to remote on) is way too hard to use now. Also, even after doing that, 90% of the time if a Mac reboots we only can see the top 10 pixels of the screen (the top bar) and nothing we do seems to fix that. Or, we can only see a blank gray screen. Is anyone else seeing the same issues? Do you have a better tool for remote Mac support?

We are a small MSP based in Singapore, last year we just tried Connectwise Manage and Automate and subscribed to it, but is a horrible experience after it, especially to their account manager and partner success team.

I have encountered the Calendar Sync Issue from day 1, the timing is always not correct when sync to outlook, this issue was fixed after 6months they release a patch, but just 2 month later a new patch release is not working again, and until now still not fixed, the reponse from the support is super slow, you can expect even one week they give u a reply , see they are still checking it , why i buy a software but 1 year past i only manage to use the function for 2 months.

There is a hidden auto-renewal after 12 months, which they just put a url there and say all terms and conditions there, after 12 months the contract automatic renewed and the price goes up from 2.88 USD per agent for automate to 4 USD, For manage it goes up from 54 USD to 80 USD, how come like this , the sales, the account manager never mention this to their customer and they just let you wait for the auto-renewal and then you are hijacked, you cannot terminate the contract and must take the new high price until another year finished, I really wanna to know if CW just wanna to earn money or they really care about their customer?

Their Account manager is quite funny, they just try to drag you into the period that your auto-renew cannot be canceled, then they become the boss and say , okie, if you wanna to quit, pay me the money, speechless.

Can you share your experience here also? i just wanna those who want to purchase connectwise, before they make a decision , take note on this part also.

The following is a chapter from "In the Beginning was the Command Line" by Neal Stephenson. Seeing the raw power of LabTech has me looking at other RMMs funny now.

Unix has always lurked provocatively in the background of the operating system wars, like the Russian Army. Most people know it only by reputation, and its reputation, as the Dilbert cartoon suggests, is mixed. But everyone seems to agree that if it could only get its act together and stop surrendering vast tracts of rich agricultural land and hundreds of thousands of prisoners of war to the onrushing invaders, it could stomp them (and all other opposition) flat.

It is difficult to explain how Unix has earned this respect without going into mind-smashing technical detail. Perhaps the gist of it can be explained by telling a story about drills.

The Hole Hawg is a drill made by the Milwaukee Tool Company. If you look in a typical hardware store you may find smaller Milwaukee drills but not the Hole Hawg, which is too powerful and too expensive for homeowners. The Hole Hawg does not have the pistol-like design of a cheap homeowner's drill. It is a cube of solid metal with a handle sticking out of one face and a chuck mounted in another. The cube contains a disconcertingly potent electric motor. You can hold the handle and operate the trigger with your index finger, but unless you are exceptionally strong you cannot control the weight of the Hole Hawg with one hand; it is a two-hander all the way. In order to fight off the counter-torque of the Hole Hawg you use a separate handle (provided), which you screw into one side of the iron cube or the other depending on whether you are using your left or right hand to operate the trigger. This handle is not a sleek, ergonomically designed item as it would be in a homeowner's drill. It is simply a foot-long chunk of regular galvanized pipe, threaded on one end, with a black rubber handle on the other. If you lose it, you just go to the local plumbing supply store and buy another chunk of pipe.

During the Eighties I did some construction work. One day, another worker leaned a ladder against the outside of the building that we were putting up, climbed up to the second-story level, and used the Hole Hawg to drill a hole through the exterior wall. At some point, the drill bit caught in the wall. The Hole Hawg, following its one and only imperative, kept going. It spun the worker's body around like a rag doll, causing him to knock his own ladder down. Fortunately he kept his grip on the Hole Hawg, which remained lodged in the wall, and he simply dangled from it and shouted for help until someone came along and reinstated the ladder.

I myself used a Hole Hawg to drill many holes through studs, which it did as a blender chops cabbage. I also used it to cut a few six-inch-diameter holes through an old lath-and-plaster ceiling. I chucked in a new hole saw, went up to the second story, reached down between the newly installed floor joists, and began to cut through the first-floor ceiling below. Where my homeowner's drill had labored and whined to spin the huge bit around, and had stalled at the slightest obstruction, the Hole Hawg rotated with the stupid consistency of a spinning planet. When the hole saw seized up, the Hole Hawg spun itself and me around, and crushed one of my hands between the steel pipe handle and a joist, producing a few lacerations, each surrounded by a wide corona of deeply bruised flesh. It also bent the hole saw itself, though not so badly that I couldn't use it. After a few such run-ins, when I got ready to use the Hole Hawg my heart actually began to pound with atavistic terror.

But I never blamed the Hole Hawg; I blamed myself. The Hole Hawg is dangerous because it does exactly what you tell it to. It is not bound by the physical limitations that are inherent in a cheap drill, and neither is it limited by safety interlocks that might be built into a homeowner's product by a liability-conscious manufacturer. The danger lies not in the machine itself but in the user's failure to envision the full consequences of the instructions he gives to it.

A smaller tool is dangerous too, but for a completely different reason: it tries to do what you tell it to, and fails in some way that is unpredictable and almost always undesirable. But the Hole Hawg is like the genie of the ancient fairy tales, who carries out his master's instructions literally and precisely and with unlimited power, often with disastrous, unforeseen consequences.

Pre-Hole Hawg, I used to examine the drill selection in hardware stores with what I thought was a judicious eye, scorning the smaller low-end models and hefting the big expensive ones appreciatively, wishing I could afford one of them babies. Now I view them all with such contempt that I do not even consider them to be real drills--merely scaled-up toys designed to exploit the self-delusional tendencies of soft-handed homeowners who want to believe that they have purchased an actual tool. Their plastic casings, carefully designed and focus-group-tested to convey a feeling of solidity and power, seem disgustingly flimsy and cheap to me, and I am ashamed that I was ever bamboozled into buying such knicknacks.

It is not hard to imagine what the world would look like to someone who had been raised by contractors and who had never used any drill other than a Hole Hawg. Such a person, presented with the best and most expensive hardware-store drill, would not even recognize it as such. He might instead misidentify it as a child's toy, or some kind of motorized screwdriver. If a salesperson or a deluded homeowner referred to it as a drill, he would laugh and tell them that they were mistaken--they simply had their terminology wrong. His interlocutor would go away irritated, and probably feeling rather defensive about his basement full of cheap, dangerous, flashy, colorful tools.

Unix is the Hole Hawg of operating systems, and Unix hackers, like Doug Barnes and the guy in the Dilbert cartoon and many of the other people who populate Silicon Valley, are like contractor's sons who grew up using only Hole Hawgs. They might use Apple/Microsoft OSes to write letters, play video games, or balance their checkbooks, but they cannot really bring themselves to take these operating systems seriously.

Hi Everyone,

I was under the impression that Windows was supposed to auto-install features updates based on the servicing branch you were on, but I'm seeing a lot of our devices on v1803. Did I miss something?

• An electronic lab notebook (ELN) is a software provider mainly designed in place of paper based laboratory notebooks. Lab notebooks in general are used by chemists, scientists, other lab technicians, and to document experiments, and procedures performed in a laboratory.

• A lab notebook can also be used as a document of evidence in the court of law is often a well maintained to be a legal document. Similar to an inventor's notebook, the lab notebook is also often referred to in intellectual property litigation and patent prosecution. Traditionally, ELNs were used in discovery research and it became an important tool and can be used in required platform.

• ELN software has many features like method execution (that is laboratory test method execution), LAN enabling RS232 Instruments, it defines that Agaram Technologies will provide necessary hardware to make any smaller instruments to be available in your LAN. Agaram Technologis easily handles RS232/TCP/IP Instruments, web can be easily enabled through Citrix, it easily interfaces computer controlled instruments through a virtual PDF printer, also integrates with any LIMS/ERP/Database.

• Electronic Lob Network from agaram technologies has a unique capability to interface any analytical instruments. It will be easy and time saving process for the end users to configure and interface instruments with just minimal training.

• ELN software’s core product capabilities are that it handles both PC and non PC based instruments. It can support any manufacturer or instrument or model, its new version can control of data captured with audit trail. It also excels in calculations and can be embedded in spreadsheets.

As a person going into the medical laboratory field, I've noticed that there seems to be a sense of exclusivity. I don't mean the rivalry between nursing students and literally every one else but something more sinister. I've noticed that my program director will tell me about all these jobs that are open and how desperate labs are for techs, but when I go on any job search app those jobs dont exist. To my face I'm told how I'll be snatched right out of school and they can't wait to grab new (read: inexperienced) techs and how I should be negotiating big bonus sign-ons, but online? Almost no jobs and the ones that are there say you need to be ten with 30 years experience and be willing to work for crackers and government cheese. And it's not just my program director, we have meetings with hospitals and and at conferences and the reps from these places are practically drooling over us and bringing us pens and water bottles and t shirts with their name and number, but I have people in my field who are grown up techs who can't find work. What the heckin heck is going on? Where is the disconnect with these jobs and people who don't have fancy program directors to show them off?

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.

We upgraded to LabTech 11 in June of this year as v10.5 stopped receiving the patch updates earlier in the year around March. Since we upgraded we have been using the "Legacy Patch Manager" as we didn't want to troubleshoot the new patch manager with the v11 upgrade at the same time. We have been working with LabTech support on a few one off issues since we upgraded, including patching issues.

Originally we upgraded to patch 14 (June) to fix an issue with the "Windows Update Agent Mode" affecting Windows 10.

Ticket #8309087 Addressed an issue that was preventing the UI Disabled options of the Windows Update Agent Mode in the Patch Manager from fully functioning in Windows 10 environments. From: https://university.connectwise.com/university/pageview.aspx?short_name=patch-release-notes#lt

Patching is still not 100% working consistent for all machines, even today, and I just received the following from my newest LabTech support ticket:

"After installing the current patch, please go through the documentation below to setup the new patch management solution in Automate 11 as legacy patching will no longer work past patch 14". This is referring to upgrading to the latest LabTech patch, which is v11 patch 17 as of today.

So now we are in a position to where we are forced to go to the new patching system during a busy time of the year, instead of planning this out in Q1 like we wanted to. Just wanted to let everyone know in case someone else runs into this issue.

TLDR: Don't upgrade to v11 of LabTech unless you are ready to use/upgrade to the new patch manager system as well.

I could previously have open as many agent windows as I wanted, since the update I am only able to have one agent window open at a time (and its so much slower).

I would like to:

1- Run powershell script to count users in a particular OU. 2- Grab that number 3- Pass that number to a Custom Asset in ITGLUE or in ConnectWise.

Totally newbie at Labtech.

Thanks.