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

bigdog09 last won the day on January 14

bigdog09 had the most liked content!

Community Reputation

37 Excellent

My Information

  • Location
    Missouri
  • Agent Count
    2000 - 3000 Agents

Recent Profile Visitors

686 profile views
  1. I think so. I think it calls the same command that's sent when you right click on the Control icon and select "disable" from the computer management screen. If it works from there, then it should work from the script too... but I'll verify that and get back with you.
  2. That's actually already baked into CWA in a script called Offboarding Maintenance > Agent > Offboarding
  3. Sorry for the spam on this back page, but I feel like this is the best way to keep the front page clean. The front page will have links to lead them directly to the year they are looking for. With that being said, it's 2020 and the 2020.1 patch has officially dropped as of yesterday (with a bit of confusion around it). I've heard some good and bad chatter about this patch, so it's more helpful than ever to post any problems that you might run into. Thanks guys!
  4. 2019: Patch 2019.12 (19.0.12.333) Benefits/Features: New Web Health Dashboard Scripting "Running" tab actually works now Known Bugs/Issues: Patch 2019.11 (19.0.11.307) Benefits/Features: Failed login lockout added More scripting visibility in the Web Several color coding changes Known Bugs/Issues: Support Session Viewer loading issues (source) Patch 2019.10 (19.0.10.275) Benefits/Features: Added Web functionality - More Pods/Fly-outs, Tool menu added including Command prompt, Create Companies, manage extensions Outlook and Backup tabs removed (as promised for several months) Known Bugs/Issues: Solution Center is not updating properly (workaround) Patch 2019.9 (19.0.9.250) Benefits/Features: Again - adding more Web CC features AND ConnectWise Now updates Known Bugs/Issues: Patch 2019.8 (19.0.8.225) Benefits/Features: A lot of Web CC updates - It's almost like they want the Web CC to replace the thick client /s Known Bugs/Issues: If you have this patch installed, then please make sure that you're on version 19.0.8.225. There is a major bug in the agent uninstaller that you really don't want to be on the wrong side of in version .224. (source) Patch 2019.7 (19.0.7.203) Benefits/Features: No major QoL improvements or changes. Several minor tweaks and bug fixes Known Bugs/Issues: Patch 2019.6 (19.0.6.161) Benefits/Features: Port 3306 has officially been removed. Known Bugs/Issues: Patch 2019.5 (19.0.5.138) Benefits/Features: Command Prompt/Powershell window access added to the Web CC. You can also toggle between running commands as system and as admin. ConnectWise Single Sign On is now live. Known Bugs/Issues: Patch 2019.4 (19.0.4.110) Benefits/Features: The Control plugin's issues from the previous patch has been resolved allegedly Several Web CC updates (definitely worth checking out the official release notes) Known Bugs/Issues: Patch 2019.3 (19.0.3.78) Benefits/Features: LDAP is finally here! (The old LDAP sync is like Jar Jar Binks, yes it existed but you're better off thinking it didn't) Known Bugs/Issues: Some are reporting an issue installing new CW Control agents via Automate after upgrading to this patch. (source) (fix) Patch 2019.2 (19.0.2.58) Benefits/Features: This patch includes one of the most important features you can ask for... a server that will still be alive in a month. Known Bugs/Issues: Please consider all non major bugs posted here as secondary. You *must* upgrade to 2019.2 or at least install the hotfix for your current patch (12p11, 12p12, 2019.1) Non SuperAdmins having login issues after changing their passwords. Introduced in 12p12, but still a problem in 2019.2 (source) Patch 2019.1 (19.0.1.38) Benefits/Features: New Versioning - This change was put in place to further mirror the rest of the ConnectWise Suite. To upgrade to this patch you must currently have a v12 patch installed. You should not attempt to upgrade from v11 or older without first moving to any of the patches listed here (preferably v12 patch 12) Known Bugs/Issues: 19.0.1.35 was the original version released to the masses, but a newer version was pushed out shortly after. If you're installing or have installed this patch be sure that it ends in .38 not .35 .36 or .37 Seems like there might be a problem with the new network probe on this patch. (source + workaround)
  5. 2018: Patch 12.12 (12.0.12.497) Benefits/Features: XP/2003 resurrected (if you are upgrading from patch 11, then you might need to reinstall the agent on these machines) You should really look into upgrading or dropping these machines. Time is not in your favor. Known Bugs/Issues: Non SuperAdmins having login issues after changing their passwords. (source) Patch 12.11 (12.0.11.475) ***PLEASE READ BEFORE UPGRADING*** Server 2003 and XP machines will no longer be supported starting with this Patch. Tread carefully. All Agents must have .Net 3.5 installed prior to the update for the Watchdog Service (even if a newer version is currently installed) Benefits/Features: More updates to the Web CC and Gen 2 Probe Several bug fixes that have been plaguing CWA for awhile (including Opening the wrong Control session) Known Bugs/Issues: Server 2003 and XP machines will no longer be supported starting with this Patch. All Agents must have .Net 3.5 installed prior to the update for the Watchdog Service (even if a newer version is currently installed) Pulled and re-released by Connectwise Patch 12.10 (12.0.10.451) (This is the first patch with heavily mixed reviews. The consensus seems to be that you should definitely update to this patch and deal with the potential CPU problems) Benefits/Features: The refresher bug has officially been patched. Reason enough to update to Patch 10 The Network Map is here! (and more importantly the Gen2 Probe) Thanks @MartynKeigher for all of your team's hard work getting this in place. (Click here to view several helpful Probe related links including a FAQ guide written by Martyn himself.) Known Bugs/Issues: Several people are reporting CPU problems which either manifests in MySQL or IIS Introduced a bug with the FileUpload script step. Will encounter a timeout when a parenthesis is present in the source/destination path/file name. (source) Patch 12.9 (12.0.9.428) Benefits/Features: Nothing special, just a laundry list of bug fixes Known Bugs/Issues: Refreshing (token timeout) bug was not patched, but rumors point towards a fix in patch 10 Patch 12.8 (12.0.8.404) Benefits/Features: Auth Anvil has returned (for you noobs that don't have Duo with YubiKeys 😉) Known Bugs/Issues: CC periodically fails to refresh forcing you to close and relaunch the CC (carryover from Patch 6) Patch 12.7 (12.0.7.385) Benefits/Features: More Web Control Center upgrades Script Editor hotkeys - Ctrl + Left/Right to move between words and Alt + Up/Down to move between script steps Known Bugs/Issues: CC periodically fails to refresh forcing you to close and relaunch the CC (carryover from Patch 6) Potential navigation tree errors (i.e. script folders populate, but the scripts themselves do not). Closing and Reopening the CC seems to be the only workaround. (source) Patch 12.6 (12.0.6.361) Benefits/Features: New Web Control Center improvements Known Bugs/Issues: CC periodically fails to refresh forcing you to close and relaunch the CC Several errors reported. Client and Agent windows are broken for some people. (source1) (source2) Do not install unless you need to be on this specific build Patch 12.5 (12.0.5.327) Benefits/Features: Web Client Installation - The Web Control Center has officially been moved into Production Known Bugs/Issues: Uses the wrong MSI flags when upgrading to Patch 5 if URL Rewrite wasn't installed prior to updating. (source) Patch 12.4 (12.0.4.312) Benefits/Features: More Patch Manager improvement for Windows 10 Machines Rest API config improvements SNMP improvements (small improvements to a BIG problem) Known Bugs/Issues: Control Center crashes seem to most prevalent in this version of Automate Patch 12.3 (12.0.3.294) Benefits/Features: Patch Manager improvements for Windows 10 (1703 or later) Remote/Offline monitor improvements Known Bugs/Issues: Patch 12.2 (12.0.2.269) Benefits/Features: Patch Manager improvements (Follows the Approve/Deny tables more effectively, improved 3rd party logging) Known Bugs/Issues: Script timeouts when running a large scripts or a bulk amount of scripts Report Center exception errors seem to be at their peak Patch 12.1 (12.0.1.256) NOTE: This is the minimum patch for updating from Automate 11 Patch 19 Benefits/Features: The first stable Version 12 patch More Maintenance Mode options Better Plugin sorting Known Bugs/Issues: Patch 12.0 (12.0.0.240) NOTE: You can only upgrade to this version from Automate 11 Patch 18 or older Benefits/Features: What's new in Automate 12 Known Bugs/Issues: There are significant issues with Remote Monitoring. This is a re-skin of Automate 11 Patch 18 which was one of the least stable patches of 11. Unless you have a legitimate reason for this specific version, then please consider at least upgrading to Patch 1
  6. That's the thing about IT. There's always a handful of ways to fix the same problem.
  7. @Tarek Salem I know it's not much help replying months after the fact, but maybe this will help the next person struggling with the same issue. It really shouldn't matter what order switches are put in place... but apparently it does. The fix for the issue you're running into is to simply move /Quiet closer to the front of the argument. Here is what mine looks like: `c:\windows10upgrade\@Installer_exe@ /Auto Upgrade /Quiet /Compat IgnoreWarning /migratedrivers all /dynamicupdate disable /showoobe none /copylogs %ltsvcdir%\packages\Windows10UpgradeLogs` /Quiet by the last switch in the imported version above and I had the same issue you did... by moving it near the front the script started working flawless. Another helpful tip - This script actually works on Windows 10 too. It compares the current OS to the @Win10Version@ variable that's manually set and if your W10 machine doesn't match then it will go through the same process and upgrade it to whatever version you want.
  8. @SteveYates Thanks for the info. Patch installation errors seems to be completely random. Most of the time it's because people forget to unblock the patch before running it, but even if you do all of the steps correctly, it can still fail like you witnessed. The good news is that simply rerunning it usually works. I'm also going to keep using this thread for all patches moving forward. I'll just copy and paste the the last couple of years in a reply and then link to it from the front page instead of displaying all of it up in a cluttered mess.
  9. No major known issues thus far. I think it officially gets a green light. Props to the CW dev team this year. It's been a very interesting year for CWA patching. The Cert (time bomb) issue and the uninstalling System32 when uninstalling Automate bugs were pretty huge issues, but they were quickly resolved and handled well. Outside of that, this was a pretty solid year. It's actually been the most stable year since they moved to the monthly update method.
  10. Patch 12 added to the front page As always please post any problems and issues that you have as well as the solution/workaround if you find it. Thanks to all who contribute!
  11. Thanks for the update @dpltadmin I've added it to the front page and linked your comment as the source. That being said I'm still greenlighting Patch 11 because it seems to be relatively stable for most users.
  12. Solution Center is apparently not updating on Patch 10 (haven't heard any word on if it's fixed in Patch 11) Solution: 1. Log into Automate server and stop both Labtech Solutions Center Service and the Monitor service below it. 2. Extract the contents of the zip (provided below) 3. Delete SCService.exe and SCServiceMon.exe from C:\Program Files\LabTech\ and paste in the new ones 4. Delete SCClient folder from %AppData%\Local\ 5. Restart the Services and Automate then open Solutions Center. *Disclaimer - The zip was provided by a technician on the Slack channel. You are responsible for vetting the contents of any file you put on your Automate server. I know this is safe, but you should never take someone's word when it comes to security. Run these steps at your own risk (even though they are the exact steps provided by CW support) SCServiceMon.zip
  13. Sorry I was out all last week when it was released. Added the patch to the front page. As always let me know if you run into any issues.
  14. @maxgruv Honestly it's pretty arbitrary. Unless there is good reason to deem it "unstable," then after 2-3 weeks I'll poll the Slack channel to make sure I didn't miss anything and then mark it accordingly.
  15. We're also a Kaseya turned Automate crew, but we pulled the trigger way back in 2012. No regrets. Automate is not without it's flaws, but I truly believe that it's the best product on the market currently. About a year ago there was a poll where hundreds if not thousands of MSP employees gave their opinion on their current RMM. Automate blew every other product out of the water, except for pricing and "vendor support" because their support is horribly lacking (though better than they get credit for). I'll see if I can find those poll results for you.
×
×
  • Create New...