Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


danialbulloch last won the day on September 27 2018

danialbulloch had the most liked content!

Community Reputation

5 Neutral

Recent Profile Visitors

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

  1. danialbulloch

    RMM Security Best Practices

    Periodic checks in the entire ConnectWise suite of the following is a good idea: Plugins or extensions that are no longer needed, or could be replaced with a simple script User accounts left active API keys Service accounts That the CW products are up-to-date
  2. danialbulloch

    Simple Website Content Checking Monitor

    I would expect custom ports to work exactly like you did it. The error it returned suggest DNS resolution was failing. Make sure that that address properly resolves.
  3. danialbulloch

    Desktop Shortcut

    If all users need the same shortcut, I recommend putting it on the public user's desktop instead, which would give it to all users that log into the system. It might also be better suited for a GPO, which has very good per-user control.
  4. danialbulloch

    Run Process as Logged in User

    You want Console Shell. See @Gavsto's blog post here: https://gavsto.com/running-programs-scripts-as-a-logged-in-user-in-a-labtech-automate-script/
  5. danialbulloch

    Offline Domain Join

    @spilgram Sorry I didn't reply, I don't think I saw your comment here. Open the computer screen and check the "Scripts" and "Commands" sub screens. In "Commands" be mindful of the "Execute script" commands, that's where the magic happens.
  6. danialbulloch

    Bitlocker Enablement Script

    Part of my new computer setup script, here's my bitlocker enabler. It enables bitlocker, throws the key in an EDF(You will probably want to rename it), and emails the tech that ran the script if for some reason it doesn't get a bitlocker key. Pretty simple, really. I recommend also looking at the following to make sure you are capturing bitlocker keys, even on machines manually enabled. TNE - Enable Bitlocker on C.xml
  7. danialbulloch

    Automate Database Maintenance Thread

    I just thought of something else that would be nice to regularly run. Something to clean up tickets in labtech. We use CWM, so cleaning up tickets that have been closed and already synced to CWM would probably be smart. Anyone have an sql command for that?
  8. danialbulloch

    Offline Domain Join

    Basically it just goes up by one. I have a client level EDF that is a computer counter. Every time the script is ran, it takes the counter up by 1. It uses that to number. All of our clients are assigned a 2-4 letter short code, so the name is like TEST-100. Very easy to take the client short code and put it together with the EDF to get the new name. However, there is a trick that I had to do. There is an issue if the script is ran on multiple computers for the same client at the same time, they will collide and end up giving the same name to the same client. To get around that, I check to see if that instance of the script is the oldest running copy for a given client, ensuring that it can't be stepped on, and once one finishes the next one will go. Attached is that piece of code. I'll probably make another post for my computer name script, but because it uses EDFs, it isn't completely self contained.
  9. danialbulloch

    Offline Domain Join

    No problem. Glad it is helping others. Between that and a computer naming script, I sped up my computer deployments by about 15 minutes per machine. A big savings on scale.
  10. danialbulloch

    Store Bitlocker Recovery Key In Labtech?

    To expand, what you want to do is create a scheduled script to run on all Windows workstations. There is already a group for that. The script should run that powershell, and store the results in an EDF. More information about EDFs can be found here: https://dbeta.com/2018/05/21/EDFsAndYou
  11. danialbulloch

    Automate Database Maintenance Thread

    Those are interesting. > - Purge informational eventlogs > 24 hours, excluding specific sources that we use for monitoring Event logs are certainly a large consumer. We use LT's event log limiter, is there a reason to do it custom? > - Delete closed tickets and associated ticketdata if >7 days old (tickets synced to Manage)  I need to look at doing the same. Our ticket database is huge. > - Remove roles that are no longer detected I'd be interested to see what you are doing here. Are you removing Automate roles that don't have any members? That's not a terrible idea to keep the roles interface cleaned up, it is quite messy for us. > - Delete drives from the drives table where missing=1 > - Delete drive space alert monitors for any drives not present in the drives table Those sound like good ways to get reporting cleaned up. You can give way more accurate information when there aren't a bunch of old usb driving hanging around. > - Reset hotfixes that have been marked as pushed, but have not installed  I guess that makes Automate attempt a reinstall?
  12. I'm just wondering what everyone does on a nightly/weekly/monthly basis to maintain their LT database. I know the slackbot recommends running "truncate table windowsupdateetlfiles;" nightly if you are having problems with your windowsupdateetlfiles table getting bloated. I'd be interested to know what others are doing to keep their server clean, or perhaps move data around to better places. I figured the best way to handle that is to run an Automate script against the Automate server.
  13. danialbulloch

    Offline Domain Join

    First of all, thanks @Gavsto and @DarrenWhite99 for helping me get the join file moved from the PDC to the joining computer. With that out of the way, attached is my script to join a computer that is not in the network of the domain. If you run it on any computer in a client, it will find the primary DC of that client, create an offline domain join file, move it over to the workstation, and finally join that workstation to the domain. It only works on computers that are currently in the workgroup "WORKGROUP" as a safety feature to make sure it doesn't run on anything it should. The computer does not need to be in the same network as the DC, but it can be, so this can be used for any instance where you want to join a computer to a domain. It does not allow you to log in with any domain credentials unless the computer can reach the DC. Offline caching of credentials, as far as I can tell, is not something that can be done. One improvement that I am probably not going to do any time soon is running an MD5 has on the source and destination files to ensure the file copy went exactly right, but it is probably a good idea. TNE - Offline Domain Join.xml
  14. It was requested that I post this here for future reference. I created a monitor and script to look for and resolve the issue of having Domain Users in workstation's local "Administrators" group. This was standard practice in my company before I worked here, and the techs were slow to change. We don't do it anymore, but there are a lot of machines that give way too much access. As a result I created this monitor. Go into a group of agents you want it to apply to, I recommend Agent Type> Windows Desktop and Windows Laptop. Go to Computers>Remote Monitors and click "Add". You want "Monitor results of an Executable". The executable is "cmd.exe" and the arguments are /C "net localgroup administrators". I wouldn't recommend setting any type of alert, and it is probably safe to do it once a day, as this shouldn't change much. Give it a good name, mine is "Domain Users as Local Admin". As for the script, it is just a one liner. Function: LabTech Command Command: 2 Parameter: CMD!!!/C "CD /D "%windir%\system32" && net localgroup Administrators /Delete "%domain%\Domain Users"" That's it. Someone with a little more time than me would probably make it check for domain users as admins first, then after attempting to remove it check to see if it actually removed, but I haven't got to it yet.
  15. danialbulloch

    Monitoring RAID (Dell/HP)

    Dell server hardware monitoring is covered extensively in this thread: viewtopic.php?f=8&t=2916 Considerably less detailed HP monitoring is covered in this thread: viewtopic.php?f=8&t=2945