[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_row admin_label=”row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text admin_label=”Text” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]
July 8th, 2021 Update
Due to the problems found with Microsoft Patch that was released on June 6th, our rolling deployment has been paused until the patch is re-released correctly. This is to limit the number of emergency patch cycle we have to run. In the meantime, we are rolling out a mitigation to the vulnerability that does not require a reboot. We do not expect any side-affects from our testing however as always please reach out to our support desk if you are having a problem.
July 7th, 2021 Update
PLEASE NOTE: Emergency maintenance is required ASAP to patch your systems and keep them secure.
As the patch is installed, end-users will be prompted to reboot their machines. If this is not done within 24 hours, the user will be prompted again and then a restart may be forced (with a 10-minute delay for users to save their work).
Servers will patch and reboot after hours.
[/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section]
