Jump to content

kostam

Members
  • Content Count

    6
  • Joined

  • Last visited

  • Days Won

    1

kostam last won the day on February 2

kostam had the most liked content!

Community Reputation

2 Neutral

My Information

  • Agent Count
    750 - 1000 Agents

Recent Profile Visitors

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

  1. Thanks for the replies, everyone. Apologies, I seem to have given some incorrect information. In my initial post, I stated the DB size to be 50GB, but the actual size is 11.3GB. I was looking at the total amount of disk usage on the C drive. Interestingly, imurphy, without any changes being made, we're now seeing 24GB used by MySQL. One MySQL process in particular seems to be writing heavily to disk, which is: C:\ProgramData\MySQL\MySQL Server 5.6\data\ibdata1 Going into C:\ProgramData\MySQL\MySQL Server 5.6\data\labtech I can see the largest files seem to be eventlog IBD files, which seem to be continuously updating (currently at around 1.8GB) - which I suppose is normal. So given that the DB size is 11.3GB and memory used by MySQL is about double that - seems to line up with what you've said. I think I'll monitor over the next few days as the memory usage was definitely not this high on Thursday.
  2. Thanks Wesley We actually already have ScreenConnect on its own server / VM. So guessing it must be something else that's causing issues.
  3. Hi guys, We're looking to rebuild our Automate server, as we've been experiencing a number of performance issues in our current install, and I'm hoping for some advice. We don't currently monitor workstations, due to this causing severe performance issues to Automate when it hit around 1,500 deployed agents. As such, we're currently just monitoring servers, around 750~. As we do not know why Automate encounters performance issues with more agents and we would like to be able to manage workstations, we've decided to rebuild our server completely. The performance issues seemed to be related to the database. As more agents were deployed, the greater the database would grow and become slow, followed by completely freezing the Automate Control Centre application. The issues are very similar to what another user encountered here: Our current setup is as follows: Single server environment running Windows 2016 and MySQL, currently 750~ agents deployed Storage / HDD: Virtualized SCSI 135GB available, 50GB used by database Memory: 48GB available, 12GB in use with 8GB of that being used by MySQL Database: Largest table is eventlogs at 4.5GB, followed by other tables from less than 1.3GB I'm hoping to get some idea on the current setup other organizations have with their Automate servers and how their performance has been with an excess of 1,500 agents deployed. Thanks
  4. Hi guys, After setting up the appropriate patching group, searches, Microsoft Update polices, I'm encountering issues where the servers aren't actually being patched. Under the server > Patching > Patch Job > the job states the below: Patch Job Type: Microsoft Policy Patch Job Operation Type: N/A Patch Job Start Date: 23/02/2020 4:00:56 AM Patch Job Finish Date: 23/02/2020 4:00:56 AM Total Patch Job Duration: 0.00 seconds I'm assuming "Patch Job Operation Type: N/A" is a clue to the problem, but I'm unsure as to where it gathers information for that field from. Other servers where scheduled patching is working usually shows the operation type as "Install". Any help would be greatly appreciated
  5. With the help of a colleague, I got this working. That said, it's a bit of an out-of-the-box workaround. So as a bit of background, I've got my Automate script that kicks off a PowerShell script that does things, then upon running, it creates a ticket in Automate, which flows through to Manage. That worked fine, and I could add comments via the script as well, which would appear under the "Discussion" comments in Manage. But I needed a way to add internal comments / notes to Manage. I'd read about Email connector tags when first learning about Manage, but had forgotten all about them until a colleague sent me a link to the ConnectWise University page on them. Basically, using the tags in an email reply to a Manage ticket, you can do a number of things, including adding an internal comment using !!AddInternal: text here!! in the body of the email. Great find, I thought as I added the 'Send Email' function into my Automate script with the internal comment tags. But upon running the script, I found that it wasn't adding new comments to my existing ticket, but instead adding entirely new tickets. Upon a closer look, I saw that these new Manage tickets had strange ticket numbers in their 'Summary' field (which would read: "RE: Ticket#123456" - which is what I had intended as it is required by the tags to work - see the doco under Email Subject Line). I opened the same ticket in Automate and found that ticket number in the 'Summary' field was actually the Automate ticket number, not the Manage ticket number. My script was told to pass the %ticketid% variable into the 'Subject/Summary' field of the email/ticket, but since it was passing the Automate number instead of the Manage number, upon receiving the email, Manage had no idea what ticket number that was or what to do with it, so instead of adding a comment, it simply created a new ticket. That was annoying, and it took a while to work out a solution. Simply changing the 'Subject/Summary' field to the same Manage ticket ID wasn't an option, as I need to be able to deploy this script to different clients, on the fly. So I needed something that knew the Manage ticket ID and passed that into the same field, and once received, Manage would know what to do with it. It took me a little while to consider how I could grab this ID. I considered writing a Python script to grab the Manage ticket ID from the Manage server, but then how would I know which ID to grab? Then I realized that I could simply create a new Automate script, which grabs the Automate ticket ID (%tickekid%) from my original script and runs an SQL query on my Automate server, using that ticket ID to find the associated Manage ticket ID, followed by passing that value into a variable, and then kicking off the email to Manage. This worked. As I said, it's a bit of an out-of-the-box workaround. I'm sure someone will post a reply stating that you can simply make internal comments by doing X - which is much easier 😂 TL;DR: Using the email connector tags I could add internal comments to Manage tickets. However, I first needed to pass the correct ticket ID into the subject line of the email to Manage. Initially this was passing the Automate ID, but I needed the Manage ID. I made a separate script that kicked off an SQL query on my Automate server, querying the Automate ID, returning the Manage ID of the associated ticket. I then stuck that Manage ID into the subject of the ticket and bingo! Sorry about the wall of text. Maybe it'll help someone else.
  6. Hi everyone, I'm rather new to Automate, but over the last 2 months I've spent almost all my time learning it's functions. I'm currently at a stage where I have a script in Automate that creates a ticket, which then transfers over to Manage using the ConnectWise Manage plugin. Now, this works perfectly. I can even have the script make additional comments on the ticket, however, I'd like the script to make internal comments on the ticket too. At this stage, I can't figure out how to do this, or find out if it's even possible. The 'Ticket Comment' script step only creates a public facing comment which is visible to the client. There doesn't seem to be any option to make this an internal / private comment. I had a look at the 'Ticket Reading View' script step, noting the 'For Customer' part of the step which states "Hide internal Ticketing information", but when adding this to my preexisting script and changing the option to 'No', it does not resolve the issue (nor does 'Yes'). Can Automate create internal comments into Manage tickets via a script? Any help would be greatly appreciated. Thanks for taking the time to read this.
×
×
  • Create New...