Jump to content

Recommended Posts

This thread is meant to be an overview for each individual Version 12+ patch. We know that all patches are not created equal and there are some patches that we should avoid like the plague (I'm looking at you 11.18/12.0). The top post will be consistently updated with known bugs/issues for each patch, so you should know at a glance if you feel comfortable upgrading or holding out for the next patch.

Blue = Must install ASAP (unless skipping to a newer patch)
Green = Stable Patch
Orange = Relatively Stable Patch
Red = Unstable Patch

Official ConnectWise Automate Patch Notes for all released patches can be found here

 

Patch 2020.11 (20.0.11.373)
Benefits/Features:

  • Security Upgrade - X-Frame-Origins and Content Security Policy

Known Bugs/Issues:

  •  

 

Patch 2020.10 (20.0.10.342)
Benefits/Features:

  • Web CC - Users can now create and edit Microsoft update policies from the Web Control Center.

Known Bugs/Issues:



  •  

Patch 2020.9 (20.0.9.310)
**note: This patch was pulled a few days after release, but has since been re-released
Benefits/Features:

  • Web CC - MFA is now optional for Contacts

Known Bugs/Issues:

  •  



Patch 2020.8 (20.0.8.278)
Benefits/Features:

  • The SSO Account column has been added to the User Management screen to display which SSO account a user belongs to.
  • MFA for the legacy Web Control Center (WCC2)

Known Bugs/Issues:

  •  

 

Patch 2020.7 (20.0.7.251)
**Attention: Please follow this Pre-Patch guide BEFORE updating to 2020.7 to help ensure that your agents will check in after updating**
Benefits/Features:

  • Very important security updates

Known Bugs/Issues:

  • If you're still having issues with agents checking in, then follow this Post-Patch guide to help remediate the issue.



Patch 2020.6 (20.0.6.201)
Benefits/Features:

  • Web CC - Link and unlink SSO users, Check Patch Approval Policies, Script grid and improved scrip scheduler
  • Core - Network Probe has additional logic to clean up devices based on MAC address, Fixed issues with Probe that prevent the probe wizard from running

Known Bugs/Issues:

  • This patch was released very late (06/25), partially due to the emergency HF releases two weeks prior



Patch 2020.5 (20.0.5.172)
Benefits/Features:

  • Patching enhancements
  • Web CC - Displaying script priority, schedule scripts on network devices, User Management ported to web.
  • SSO in the Thick Client

Known Bugs/Issues:

  • Confirmed issue with the Network Probe not working properly in 2020.5

 

Patch 2020.4 (20.0.4.141)
Benefits/Features:

  • Web CC - Several script scheduling updates (Delete, edit, change priority of scheduled scripts)

Known Bugs/Issues:

  •  

 

Patch 2020.3 (20.0.3.112)
Benefits/Features:

  • Web CC - Scheduled scripts now have "high priority" when running. Maintenance mode can now be set
  • Logging - Added some additional logging features. Control now prompts to give a reason for remoting into a machine

Known Bugs/Issues:

  •  

 

Patch 2020.2 (20.0.2.81)
Benefits/Features:

  • Web CC - Scripts can now be scheduled in the Web CC instead of only being able to run on demand
  • Office 365 option added to the Dashboard ahead of the forced Azure security changes and "app registration." (see more info about it here)
  • Control Center will no longer leave rogue windows open when the CC is closed. All Automate related windows will be closed when the CC itself is closed.

Known Bugs/Issues:

  •  


Patch 2020.1 (20.0.1.51)
Benefits/Features:

  • Mandatory MFA - Users Must Have an Email Address Defined (Email address is now a required field for all users)
  • Automate has retired the legacy Report Manager and Crystal Reports as of December 31, 2019.

Known Bugs/Issues:


  •  
Edited by bigdog09
Patch 2020.11 release
  • Like 6
  • Thanks 5
Link to post
Share on other sites
  • Replies 244
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

This thread is meant to be an overview for each individual Version 12+ patch. We know that all patches are not created equal and there are some patches that we should avoid like the plague (I'm lookin

Confirmed the issue is still present in 2019.2

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

Posted Images

For Patch 5, I pushed an issue up to dev which has now been determined as a Known issue, however, it is not listed on the known issues page yet.

My Ticket: KNOWN ISSUE: Ticket #10149848 regarding " Upgrading v12P04 to v12P05, Installer Stuck on rewrite_amd65.msi /qn /norestart(10120711)

If you already have URL Rewrite Installed on your IIS, then you will not experience the below issue:

Basically when running the Patch 5 update, if you don't have URL Rewrite installed for IIS, the patch attempts to do this for you but appears to use the wrong MSI flags for quiet, norestart, so in the middle of installing the patch you will get an MSI Help Popup and the patching will not continue until you click on ok of this window. There is another step in the patching process where you will get the same pop up. Clicking through both of these MSI Help popups the upgrade seems to complete properly with the exception of the new Web Control Center, it won't install/display if IIS doesn't have URL Rewrite Installed. Minor issue but thought I would share with the community.

 

Edit: 
image.png.2db404ffd31e3e9eb6c4ff59fe002b8a.png

Edited by dpltadmin
Supposedly the issue is fixed.
Link to post
Share on other sites

Wasn't that a problem before? Like Patch 4? Or earlier? It would trigger an unexpected server restart if you had a restart pending and the feature could not be enabled until after a reboot. As I recall, the reboot mid-upgrade really messed things up for admins.. I'm surprised Patch 5 would include the same (or a very similar) mistake.

Link to post
Share on other sites
17 hours ago, DarrenWhite99 said:

Wasn't that a problem before? Like Patch 4? Or earlier? It would trigger an unexpected server restart if you had a restart pending and the feature could not be enabled until after a reboot. As I recall, the reboot mid-upgrade really messed things up for admins.. I'm surprised Patch 5 would include the same (or a very similar) mistake.

If it was, I don't recall experiencing that.

On my dev server I went from v11p19 -> v12p01 -> v12p04.

When I did the upgrades, my server wasn't pending a reboot.

Link to post
Share on other sites

Found what I was thinking of. From https://university.connectwise.com/university/pageview.aspx?short_name=patch-release-notes

For March/Patch 4:
Ticket #9643521: Resolved an issue that caused the Automation server to be dependant on the presence of the IIS component in order to successfully patch.

As I recall, there was a step in the patch where if an IIS pre-requisite was not already installed, when it installed with was triggering a restart and borking installs.

 

 

Link to post
Share on other sites
  • 1 month later...
On 6/12/2018 at 11:41 AM, skyper said:

Patch 6,

anyone with this popup ?

Every Agent/Device has this popup saying: Errorin in loading Cliet Tab: Table 0 cannot be found

image.png.7055faf89f010f67c50237159de8e6d9.png

 

Yes, we are also having these issues, not all of the time though, and yes indeed since Patch 6

Link to post
Share on other sites
On 6/12/2018 at 5:41 AM, skyper said:

Patch 6,

anyone with this popup ?

Every Agent/Device has this popup saying: Errorin in loading Cliet Tab: Table 0 cannot be found

image.png.7055faf89f010f67c50237159de8e6d9.png

 

Have you updated to build 361? Just asking because the agent in your image is not a 361 build. There was a rebuild of Patch 6 (.361). I'd first try that, of course, if you haven't. 

Link to post
Share on other sites
On 6/12/2018 at 10:41 AM, skyper said:

Patch 6,

anyone with this popup ?

Every Agent/Device has this popup saying: Errorin in loading Cliet Tab: Table 0 cannot be found

image.png.7055faf89f010f67c50237159de8e6d9.png

 

Did you manage to get anywhere with this error? I've been getting it since the upgrade. Installed the latest patch last weekend with no difference.

Link to post
Share on other sites

Similar issue here.

Installed v12.0.361 on Friday night (updated from v12 p5).

Super Admins don't get these errors,  but everyone else gets it for each Computer Management window. If the tech opens additional Computer Management screens within the same window, then there is no error. The Computer Management screen still seems to load properly.

I contact support and was told:

Quote

this issue is trending, it is related to the Standards and Health plugin, dev is working on a fix. Currently the only work around is to disable the Standards and Health plugin

1764048350_Error-ComputerScreen-6-25-18.png.5365a8e5be0864f75226bd2d4d7d4563.png

Link to post
Share on other sites
On 6/25/2018 at 4:08 PM, toril said:

Similar issue here.

Installed v12.0.361 on Friday night (updated from v12 p5).

Super Admins don't get these errors,  but everyone else gets it for each Computer Management window. If the tech opens additional Computer Management screens within the same window, then there is no error. The Computer Management screen still seems to load properly.

I contact support and was told:

1764048350_Error-ComputerScreen-6-25-18.png.5365a8e5be0864f75226bd2d4d7d4563.png

That explains why I am not aware of this. 

Link to post
Share on other sites
  • 2 weeks later...

Patch 7 has gone through a few different reworks because of issues, so it's still in beta. When a patch is touched up that many times it's difficult to tell if that means it's going to be a solid patch because it's been thoroughly tested or another patch to skip because it's inherently buggy. 

I think the ETA is around the end of this month. A few of the guys are crazy enough to roll it out into production when it's released, so we'll find out soon enough if it's going to be worth it. 

  • Sad 1
Link to post
Share on other sites

There is currently an issue with the July Microsoft updates that will cause issues with the update process.  The result is that certain services will not stop and start.  Microsoft has already released hotfixes for Server 2008 R2, 2012 R2, and 2016.  However they skipped 2012 (which we are currently on) so we had to uninstall the July updates, reboot, and then reapply Patch 7.

Link to post
Share on other sites

We're seeing an issue with the Control Center under Patch 7 where the body portion of the navigation interface perpetually refreshes or if it does eventually "finish" it shows no results.  So you can bring up the scripts tree and see all the folders, but when choosing a folder it appears empty.  Same with browsing client computers/contacts/network devices/etc. I initially thought this was due to leaving the CC open over-night/for a long period of time but it just happened again today while actively working in there.

Reloading system cache or browsing different elements doesn't resolve the problem.  Restarting the Control Center is the only way I've found to get normal functionality back.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...