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

Community Reputation

0 Neutral

My Information

  • Agent Count
    1500 - 2000 Agents

Recent Profile Visitors

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

  1. https://www.plugins4automate.com/collections/free-plugins/products/announce-maintenance
  2. HI Folks, I am a little confused - Automate comes with Ignite and tons of monitors and all that stuff but it comes with all the Managed 8 x 5 / 24 / 7 bits too So you start working with Automate consultancy and they say no don't use that create your own because we update Ignite all the time..... So at this point I am starting to scratch my head surely tweaking their Ignite is the way to go and just makes my life a lot easier than having to rebuild all of Ignite and just ignoring what they did. Anybody any thoughts? Michael
  3. Cheers KKerezman, Funny I remember doing the same thing with Sophos you had to do a registry fiddle with the Sophos Server to make it an MSP server but support had no clue about it. It baffles me why these big vendors did not jump on the MSP model it should be so easy to jump back and forth and manage thousands of end points - general thoughts we got from Sophos HQ was they didnt see the MSP world as a big market I guess bread and butter for a long time was the renewals for large corporate. We went with Eset in the end I have used Webroot and while it was a good addition to another AV I just don't believe it is as complete a product as a full AV product, there was always a thought in my head that it was a large marketing machine with an empty shell that sells for little money which we MSP's love. Cheers
  4. Hi Avdlaan, Yeah I am aware you still need them perhaps my wording was not clear (or wrong) - however running BC / DR and backups in Azure is a doddle plus you can monitor / patch and get performance stats all from within the one console. Makes life a ton easier - plus it is only cheaper if you already have the infrastructure in which case I would agree but if you don't have the virtual hosts with redundant storage and multiple switches and firewalls and backup internet lines etc etc then firing up a server in Azure or equivalent is a ton easier.
  5. Hi dfleisch Thanks for the response - it frustrates a little that we have to go to a non official channel such as mspgeek to get a technical response from Automate but anyway. Azure is a no brainer unfortunately for most MSPs as we get credits for being a partner and more often than not we are selling it - equally buying our own tin in my view is old hat and not a good way to do business - you have to manage the hardware / manage the DR / BC / backups - monitor hardware monitor internet lines / have failover firewalls and switches or you go to the cloud and forget all about it. With regards to the MS V Amazon debate cause this is what this is really about MS came back with this (part of the response) "Thank you for sharing the information. Your software vendor’s DBA team is right when he mentioned “Amazon's EC2 instances that use EBS Optimized volumes are going to run about 3200 IOPS on that test”. However, this is due to the burst mode for General Purpose (gp2) storage type for EBS where IOPS is the size of the volume (you configure during creation in GiB) * 3, with minimum of 100 IOPS and max of 10K IOPS. But due to burst mode, every gp2 volume regardless of size starts with 5.4 million I/O credits at 3000 IOPS which used in full capacity will last you about 30 minutes. Workload will continue to see very good IOPS as long as credits are replenished faster than they are consumed. But if IOPS credit is used up, then it will be slow. Here is the doc for your reference https://aws.amazon.com/blogs/database/understanding-burst-vs-baseline-performance-with-amazon-rds-and-gp2/. On the other hand, if you go with the storage option of EBS, you can actually configure how much IOPS you want in your VM but will have additional price. " My question to you avoiding all of the stuff above is with regard to the block sizes 16 vs higher is this a Mysql issue or how automate is written - for example if we increase the block size on the diskspd command to 5m we are fine. Equally on each Azure VM we have a temp drive which has higher IOPS than premium SSD but is obviously not persistant can MySql temp logs be utilised there to speed up the system. Also if the RAM is sufficient can the DB not be loaded fully into RAM - what are the drawbacks / potential issues to this? Forgive me if these seem lame or potentially dumb questions but as the only response to date from Automate has been "computer says no" and "Azure is not suitable" I need to come up with some sort of a plan as to how to move forward and equally the number of partners I know running Automate on Azure may need further information than "you should have gone with AWS". Thanks Michael
  6. Hi folks Just curious We are currently using Symantec but looking to move and considering eset due to plugin with automate. Am wondering if people would recommend it or would look at something else like webroot or bitdefender or sophos or other. Cheers Michael
  7. Thats great thanks tlphipps we are getting between 5 and 20 MiB/s with that command. The battle with CW begins.
  8. tlphipps do you think with Managed Premium SSD you need the storage spaces? We had two managed Premium SSD - C was 127GB and D was 1TB - We contacted Microsoft and they ran diskspd and they were getting 125 Mib/s whereas when Connectwise ran their command they got 15 - 20 mib/s. MS said CW command was not suitable for cloud / virtual disks. Stuck between a rock and hard place CW won't proceed with install and MS say nothing wrong my gut says there is nothing wrong and with 24GB Ram and max 1500 agents I just can't see it being an issue. CW Command is - diskspd.exe -c10G -t4 -si16K -b16K -d30 -L -o1 -w100 -D -Sh c:\temp\testfile.dat
  9. Hi Folks, We are trying to deploy Automate to Azure - will have max 1500 agents for the next year or two we built a DS12 with managed premium SSD. Automate came along to do the install and said disk performance is not good enough for Automate. They are running a diskspd command - we went to Microsoft and they say that command is not valid for Azure they ran their command and we are getting as expected performance. Anybody any thoughts on this I see tlphipps is running 5000 agents on Azure without an issue. All seems mad to me Cheers Michael
×
×
  • Create New...