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

Cabraghman last won the day on September 9

Cabraghman had the most liked content!

Community Reputation

1 Neutral

My Information

  • Agent Count
    1500+
  1. This is what CW Support told us to do - seemed to help. Hello Colin, Thanks for contacting ConnectWise Automate. I see that you are having an issue where your agents are showing MSE as being the antivirus installed instead of Webroot. To fix this, you will want to do the following : 1. Go to System > Configuration > Dashboard > Config > Configuration > Virus Scan 2. Select MSE from the list and click the "Export Selected" button 3. Save the file where you can access it later 4. Select MSE from the list again, right click it and click Delete 5. Once MSE has been deleted, go to System > General > Import > SQL File 6. Select that file from step 4 and click OK 7. Click OK on the prompt that follows What the above steps does is it moves the virus scanner to the bottom of the list so it won't be detected first. You can perform the same steps on any virus scanner you want to move to the bottom of the list. Once the above steps have been completed, wait 24 hours and see if the agents detect Webroot. Please let me know if you have any further questions or concerns. Thanks again for contacting ConnectWise Automate and have a great day, -Nick P Technical Support Analyst Need immediate assistance?
  2. Have a look here - you hav to purchase but very reasonable https://squattingdog.net/labtech-warrantylookerupper/
  3. https://squattingdog.net/labtech-plugin-red-flag/
  4. Mtthew, I have an Excel sheet that runs a SQL query to do this (see screenshot attached) - happy to post here - although its using Warranty Master info - do you have that? C
  5. This is what support told us This certainly is an issue and I have an explanation. The icon for ignite is slightly bigger (50x50) where the icons are normally smaller (40x40). This is causing the ignite icon to show 'fine' but pushing all other icons out of alignment. They are actually there just not really visible. This issue has been brought up to our development team but as the legacy computer management screen is in fact legacy no new escalations will be sent up for this. As it is the legacy view will no longer be available once version 12 releases. The workaround is to deny access to the ignite tab by restricting permissions. This will allow the other icons to not be improperly formatted but I would not consider it an acceptable workaround. And so, that is the resolution to your concern. I understand if you are not thrilled with the answer I have provided and I would encourage you to get used to how the new computer management tiles work. Please reply back if you have further questions or concerns on this topic.
  6. Try running it as the administrator account to see if it starts then try it while logged in as you
  7. Try running it as the administrator account to see if it starts then try it while logged in as you
  8. Steve, I just had a chat session with LT Support and they said its Ok to use provided I understand that the old UI is being phased out and if a problem exists in the leagacy UI but not in the new UI that problwm won't be support - which is fair enough. Ticket#8426406. C
  9. Cubert, I would be interested in being an early tester - we are doing about 300 daily backups with various packages - mostly Altaro and some home grown scripts - we are doing what you are doing trhrough a combination of Excel, SQL and sweat.
  10. Installed . flicked the switch but not getting any results - any thoughts?
  11. We had this and it was caused by me forgetting to "unblock" the file under file properties.
  12. Is it safe to upgrade over top of 1.0.1.42?
  13. I had similar and someone else in the forums suggested checking "unblock" via file properties - that sorted it for us.
  14. Just in case this helps with Win7 machines. We found the presence of KB3004394 was causing serious issues so removed it and it sorted quite a number of Win7 machines. We then installed (Dec 2015) WUA Patch KB3112343 and things are working well. Still a few machines that need work though.
  15. The reason I purchased was my way of saying thank you to Cubert for all the contributions he has made - I use a number of his products, I used Patch Remedy when it was free - it helped me address various patching issues - still have lots to do though.
×
×
  • Create New...