Hello,
After reading through July 2016 KB release notes, it does not mention anything about users being logged out of the system before applying the update. I would like to know what have your experiences been like when applying these updates while users are in the system.
Maybe I'm just a little paronoid about applying updates during business hours but maybe your comments can ease my concerns.
FYI-I have applied many KB updates in the past but with CPS having sooo many moving parts, I would like to be reassured.
Thanks,
Kenyon
don't remember if it is full or monthly.
if it isn't full you don't need to log people out of it, only when is full is recommended to log everyone out.
Thanks for your response. June KB was a full update and in the release notes it did state users must be logged out. I was expecting to see the same for the July-Incremental update, but I guess it only applies to Full updates.
A full KB update it may lock certain tables and people who would need access to those tables would be inconvenienced during that part of the update. For that reason t is best to do it after hours with nobody in the system. At least give them a heads up if there are minimal people in because words like always and never are dangerous words in IT.
Also, the documentation says to have a current verified backup before applying the update. That means that you will likely be spending some time doing a backup before starting the update. It would be preferable to have users out of the system in case you need to restore. I do mine on Saturday morning (at least 7 days after release). That way the Friday night backup has occurred and I don't have to wait for the 3.5 hours it takes for a backup just to do this update
I once had one of these updates go bad. It was after hours and the only thing support will do for you is help you restore from backup (.BAK file). There was a time when they didn't say anything about a backup but I was doing it anyway and I am glad I did.
Mike Zavolas
Tallahassee Neurological Clinic
Mike, I learn best by mistakes; so knowing what to expect from support, if something goes wrong, is important. Luckily for us, we have a SAN backup solution which backup our database a few times throughout the day...so a DB restore wouldn't be a problem. Hopefully we won't have any issues while applying KB updates in the future; but like you said, always & never are dangerous words in this profession.
The incremental updates can be installed during production the full updates need users out. Still with the incremental updates I always test in my test environment before applying live.