Problems with machines exiting maintenance mode for customers running Cloud / Cloud Connector
Posted by Adam Zilliax on 16 March 2018 10:14 AM
UPDATE : FRIDAY MARCH 16, 2018 @ 3:30PM Pacific Time|
Our Developers have pushed some additional fixes to the cloud that should resolve the rest of the machines having this issue. The fix may take up to 12 hrs for a machine to pick up the change and reboot out of the maintenance mode. Machines may require a manual reboot back into a frozen state to fully resolve this issue.
If you have machines that need to be recovered immediately we have pushed a updated patch for this issue that can be run manually on the systems affected using any remote control utility, or any utility that can push a file and execute it on a remote machine. This includes the Push and Launch function of the Deep Freeze Enterprise Console. This utility can be downloaded here;
If you need further assistance please feel free to reach out to us regarding this issue.
UPDATE : FRIDAY MARCH 16, 2018 @ 1:55PM Pacific Time
Our developers are continuing to review this issue and to investigate some additional reports that where not resolved with the initial fix. We will continue to update the status here as more infromaton is provided. Again if you are having any issues please reach out to firstname.lastname@example.org to update us on the status of your issue.
UPDATE : FRIDAY MARCH 16, 2018 @ 12:48PM Pacific Time
Our developers have pushed a updated file to our Cloud Services to address this issue, rebooting your computer(s) should end the maintenance tasks that are stuck. Machines may need to be set to a Frozen State through an additional reboot to return the machine to to the protected state.
Again, if you are still having issues please give the support team a shout to let us know at email@example.com
We have been made aware of some customers experiencing problems where machines are not exiting the Deep Freeze Cloud Maintenance tasks.
Our developers are looking into the data collected by our customers and will be providing further updates shortly. If you are seeing this issue please reach out and contact the Faronics support team so that we can open up a support ticket to track this issue and reach out directly once the issue is resolved. The team can be reached at firstname.lastname@example.org.