Notifications
Clear all
Topic starter
Just a heads up to everyone, but there's a new KB from Microsoft that looks like it is breaking Centricity. This KB was pushed out late yesterday or early today and is a branch off of one or both of the confirmed KB's that will break any Centricity installation.
The two KB's that GE confirmed would effect any installation of Centricity are below:
KB3161608 & KB3161606
The new KB that is causing issues is listed below:
KB3172605
We have already had problems with this breaking the Centricity application completely across multiple clinics in our environment. This seems to affect both Citrix and fat-client machines, since both of ours were affected. After removing the KB in question, Centricity was able to start without any issues.
If you run a controlled SUS, it might be a good idea to go ahead and block this one for now. There may not be an actual problem with this update, but it affected multiple different locations in our environment today. After speaking with the affected users, the conclusion was that they went to lunch and updated their PC's and came back to a broken Centricity.
Hope this helps some others. Luckily we caught it quickly.
Posted : August 3, 2016 11:11 am
Just curious- had you applied the previous workaround- updating the server.xml file on the jboss?
Thank you for sharing!
Posted : August 3, 2016 12:12 pm
Topic starter
Initially before the workaround was posted, we blocked the two KB's via WSUS. We did not see any impact to any users during that time frame. Once the workaround was posted, we figured that we might as well apply it just to be extra sure. Again, this is just a possible break with this new KB and could have just been an isolated issue on our end. However, when 17 users at 4 different clinics start calling with the same issue after updating windows, it becomes a little more than just a guess.
Our initial debugging process was fairly simple. Locate the recently applied updates, uninstall them one by one and check if CPS was able to launch. Documenting each update and checking it off the list. Luckily the first computer we touched was a fat client with only 4 possible updates to sift through. This made things a little easier to pinpoint which KB was the troublemaker.
Posted : August 3, 2016 1:40 pm
We for one had already made the server.xml changes to TLS and do NOT have a problem with this MS KB in our terminal server environment.
Steve
Posted : August 4, 2016 2:26 am
The same jboss fix for the other two updates should work for that one.
Posted : August 4, 2016 7:09 am
I posed last week concerning this issue. Luckily, only 1 workstation had the update applied. I performed the jboss server.xml tweak and worked with flying colors. In fact, according to the official GE page, they suggest applying this regardless of whether you're currently having issues or not, as this could be problematic again in the future.
Posted : August 8, 2016 4:03 am
Just thought I'd add to this that I updated my test server with windows updates Friday and did not apply any of the 3 mentioned (2 by GE and 1 in this post) and it broke anyways. I did apply the work around and it resolved the issue. I would agree applying the work around as a preventative measure is probably a good idea since it may not be isolated to the 2 KB's GE notified us about. I put in a ticket but not sure they will modify any customer notifications.
Posted : August 10, 2016 11:01 am
Yeah I think you're right, JRyan. I'm sure there are a handful of updates that provide problematic, plus more to come. Just goes to show why GE is recommending admins apply the fix regardless if currently having issues or not.
Posted : August 11, 2016 2:31 am
