Jump to content

ErinC

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count
    Less than 100
  1. ErinC

    Windows Update 1903

    No problems with 1903 here, I've updated a bunch of our internal systems with no issues.
  2. Your script and EDF work brilliantly, many thanks for that Brenden, it's exactly what I was looking for.
  3. ErinC

    Automate to Manage ticketing

    Thanks for your replies guys. I'll dig into it a bit more and see what I can get working. We are indeed using Ignite and I suspect you may be correct Jacob in that changes may be reverted back when it's updated next. I will test and post something back here once I have a resolution, thanks again.
  4. Hi all, I recently enabled ticket/company sync from Automate to Manage (I'm still thinking of it as LabTech to ConnectWise hehe) Now I am faced with the task of trimming down the massive amount of tickets created in LT. We're getting a lot of tickets raised for TCP/UDP port monitoring. The trouble is that I don't wish to know about port monitors for Workstations, only Servers. The monitor is keyed to use the default auto-join search groups for ports. The problem is that I cannot modify these groups to say "only if OS is server" for example. The search group is "locked" and won't allow me to modify it. Can anyone tell me how I might easily adjust this to not monitor workstations? I just can't figure it out. thanks!
  5. I am assuming you mean reboots for patching and other maintenance? My requirements are perhaps not as restrictive as yours by the sound of it, but what I do is simply have some standards/templates defined (as few as possible) using patch policies and ignite settings, and I stick to it religiously. All our managed endpoints (95% of them lets say) are fitted into 3 different maintenance/patch settings this way. I generally create 3 x LT Locations (minimum) for each LT Client. These three are usually named Servers, Workstations and Laptops. Then I apply custom Ignite settings to each of these LT Locations. This sets the ignite group membership and I target patch policies/reboot policies at the ignite groups. This way I can patch laptops "anytime" with no forced reboot initially (then with time-restricted reboot messages/forced reboots later), Workstations on Thursday night with forced reboots, and Servers on a Sunday afternoon with forced reboots. Once I've setup a new client's location like this I rarely ever need to change anything in it again. I also schedule pop-up reminders (only for workstations patch Thursday) for clients users to make sure they leave their machines are powered on and that they power on other machines that may be turned off too. Clients like this visibility in my experience. Sometimes I do need to create a custom location for different requirements/uptime/patch reboot behaviour etc, but rarely. Like a "no patch" location etc. Once the locations are setup, then I simply move new endpoints into the correct location and they inherit the correct policies. This works well for us largely because most of our client's businesses are closed on Thursday nights and Sundays! I'm not sure if this is of any help to you whatsoever though...
  6. Thanks Cubert! I was looking for something like this and it works perfectly on our Automate12 cloud hosted server
  7. Many thanks to LTNinja for your work on this. (And to DarrenWhite for the monitor) I found the script failed to run on SBS2011 machines. I simply added an extra GOTO command in line 6 to send the script to the Server 2008 R2 section. Tested ok on SBS 2011 (not sure how this will affect SBS2008?) Edit: I'm a bit of a LT noob so couldn't see how to get the DataView working .. tips appreciated!
×