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.]]

danialbulloch last won the day on September 27 2018

danialbulloch had the most liked content!

Community Reputation

6 Neutral

Recent Profile Visitors

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

  1. Those would be "Remote Monitors". You can read more about them here: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/165/090/020
  2. Oh, I just noticed that that post didn't mention quotes inside of your block of powershell code. You have to escape all of your double quotes. Normally you do that by putting a \ before the quote. Or, if possible avoid using double quotes and only use single quotes.
  3. I don't know your backup setup exactly, but it sounds like a job for powershell and a monitor. You can use powershell to check the modified date of a folder or something, then a monitor using that powershell looking for a bad condition. https://gavsto.com/remote-monitor-series-finding-machines-where-bitlocker-is-not-protecting-drives/ Explains lightly how to do powershell remote monitors.
  4. 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
  5. 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.
  6. 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.
  7. 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/
  8. @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.
  9. 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
  10. 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?
  11. 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.
  12. 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.
  13. 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
  14. 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?
  15. 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.
×
×
  • Create New...