Note for Deep Freeze Cloud Connector Customers: An automatic Cloud Agent module update now resolves an issue where the Deep Freeze Service was not starting and Deep Freeze computers were not communicating with Deep Freeze Cloud. (Case No: HKN-952-83206, NLG-897-20755, ANJ-311-67397, VYL-377-67281)
↧
Update to the Deep Freeze Cloud Agent to resolve issues with machines not communicating / showing as online.
↧
Deep Freeze Install Error on Fall Creators Build
In light of the recent Fall Creators Update for Windows 10, some users may suddenly experience an error while attempting to install the Deep Freeze Enterprise Workstation client.
#01020000
Deep Freeze Enterprise could not be installed. The system will be restarted.
To bypass this issue, please ensure you are using the latest version of Deep Freeze.
Versions Affected:
#01020000
Deep Freeze Enterprise could not be installed. The system will be restarted.
To bypass this issue, please ensure you are using the latest version of Deep Freeze.
Versions Affected:
- Windows 10 Version 1709 (build 16299)
- Deep Freeze Enterprise 8.38 or earlier
- Deep Freeze Cloud/Standard 8.37 or earlier
↧
↧
Faronics Antivirus 4.13 Released
Faronics is happy to announce the release of Faronics Antivirus 4.13. This release fixes a couple of customer facing issues listed below;
- 22203 Resolved an issue where a locally disabled Firewall gets enabled automatically after around 15 minutes of workstation reboot.
- 22214 Resolved an issue where Active Protection disabled from policy gets enabled on workstation from Windows Security Center notification alert.
- 22694 Resolved an issue where the user was unable to update 32-bit definitions on Core server. (Case No: YGH-153-55361)
- 19981 Resolved an issue where the user was unable to white-list files due to THREATID missing under exceptions. (Case No: ACK-792-66923)
↧
Faronics Offices - Holiday Hours
The Faronics offices will be closed on December 25th in observance of the Christmas holiday. As well as on January 1st, in observance of New Years Day.
↧
Faronics Antivirus and the January 3rd patches for the Meltdown and Spectre vunlerabilties.
Updated - January 8, 2017 - Faronics has released a patch utility that can be used to apply this registry key using the remote launch functions of both Faronics Core and the Deep Freeze Enterprise Console. Details are here. Additionally we will begin rolling this change out to our cloud based customers automatically over the course of January 9th, meaning that cloud customers should not have any need to apply this patch manually.
On January 3 Microsoft released a security patch to help mitigate the Meltdown and Spectre vulnerabilities disclosed by a number of researchers. As part of these updates a requirement was introduced that requires antivirus vendors to validate their products against the patch before the patch will properly install on workstations.
Our QA team has been working to validate the patch and at this time we can confirm that there is no issue with the January 3rd patches to mitigate Meltdown and Specter and the latest releases of our Antivirus product. Customers needing to install the January 3rd update can at this time manually set the following registry key to allow the installation of this update;
Key = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD”
This can be manually configured or added using the .REG key located here;
https://faronics.digitalpigeon.com/msg/kCpvgPI4EeeZ0AYtQsGbAw/qlzRgFNGBnfXXlGLp73bCQ
Our developers are currently investigating to see if there are other ways that we can further automate this process and we will provide updates here as that information is made available. If you are in need of further assistance please reach out to the Faroncis support team for further help.
↧
↧
Trojan.Inject.BED Detections on Windows 10 Systems running Faronics Antivirus
Over the last several days we have been made aware of situations where customers are seeing our Antivirus Software reporting alerts from the Trojan.Inject.BED being detected on some systems running Faronics Antivirus. This is occurring due to a false positive that was occurring during memory scanning while specific common Windows applications where in use (PowerPoint and Excel being two examples) on Windows 10 systems.
In cases where false positive has occurred no files where quarantined and no disruptive action would have been taken on the system as a result of this false positive.
Updated definition files have been pushed to our update servers to address this issue at this time. We recommend that all customers update to the latest version of the definition files for Faronics Antivirus to avoid these false positives moving forward.
In cases where false positive has occurred no files where quarantined and no disruptive action would have been taken on the system as a result of this false positive.
Updated definition files have been pushed to our update servers to address this issue at this time. We recommend that all customers update to the latest version of the definition files for Faronics Antivirus to avoid these false positives moving forward.
↧
Problems with machines exiting maintenance mode for customers running Cloud / Cloud Connector
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;
http://bit.ly/2GzBrVy
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 support@faronics.com 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 support@faronics.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 support@faronics.com.
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;
http://bit.ly/2GzBrVy
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 support@faronics.com 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 support@faronics.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 support@faronics.com.
↧
Start-up Repair message after updating to Windows 10 Fall Creators Update
Product Affected: Deep Freeze Enterprise 8.51
Windows 10 Fall Creators Update 1709 (Build 16299)
We've identified that the upgrade to the 1709 makes some changes to the boot control configuration on the machine and allows these messages to be displayed when restarting the machine. We are working with Microsoft to resolve this issue completely. To prevent this screen in the meantime, you can apply the following command to your machines:
bcdedit /set {current} bootstatuspolicy ignoreallfailures
This can be deployed either through an elevated command prompt on a single machine, or deliver it via a batch script using the Deep Freeze Enterprise Console's "Push and Launch" feature to a group of machines.
Windows 10 Fall Creators Update 1709 (Build 16299)
We've identified that the upgrade to the 1709 makes some changes to the boot control configuration on the machine and allows these messages to be displayed when restarting the machine. We are working with Microsoft to resolve this issue completely. To prevent this screen in the meantime, you can apply the following command to your machines:
bcdedit /set {current} bootstatuspolicy ignoreallfailures
This can be deployed either through an elevated command prompt on a single machine, or deliver it via a batch script using the Deep Freeze Enterprise Console's "Push and Launch" feature to a group of machines.
↧
Deep Freeze Enterprise 8.52
Earlier today Deep Freeze Enterprise 8.52 was released to our customer base, however shortly after release an issue was exposed regarding the digital certificates used in the build. At this time we have recalled the 8.52 release and are working on updating the build to correct this issue.
Customers who have downloaded the 8.52 release should hold on installing until we have an updated build available. Customers who have already installed and are seeing issues with the build should contact Faronics Support for assistance in remediating the problem.
We apologize for the inconvenience and will continue to provided updates as they become available.
Customers who have downloaded the 8.52 release should hold on installing until we have an updated build available. Customers who have already installed and are seeing issues with the build should contact Faronics Support for assistance in remediating the problem.
We apologize for the inconvenience and will continue to provided updates as they become available.
↧
↧
Support for Spring Creators Update
Faronics has been testing Deep Freeze and our other products against the Insiders builds of Windows as they are being released. At this time we don’t have any specific issues with the Insiders builds that we are aware of.
That being said, our products have been caught by last-minute changes to Windows before the public release. Provided we don’t see any surprises, we hope to confirm support for the Spring Creators Update within a week of general availability. Once we have done our testing, we will update this post with any details and update our documentation.
↧
Deep Freeze 8.53 & Deep Freeze Mac 6.21 released.
Faronics is pleased to announce the release of two updated versions of Deep Freeze.
Deep Freeze 8.53 has been released to the public, this build has a number of bugfixes and other features included within including;
Please Note : This version does not yet support installation on APFS formatted volumes, and will require user consent to load kernel extensions (more information here).
The updated versions can be downloaded from our Faronics Labs portal (for customers in North America) or from Faronics Customer Centre (for customers internationally).
And as always if you have any issues or concerns please reach out to our support team (support@faronics.com) and let us know.
Deep Freeze 8.53 has been released to the public, this build has a number of bugfixes and other features included within including;
- 11231 Resolved an issue where Deep Freeze could not be installed on devices with an eMMC based hard drive.
- 21021 Resolved an issue where workstations were not exiting Deep Freeze Workstation Task.
- 21227 Resolved an issue where Deep Freeze Service crashes if there are too many port connections21566 Resolved an issue where, switching between multiple ports in Enterprise Console while workstations are reporting in, the workstations continuing to report to the wrong port after changing the active port.
- 21847 Resolved an issue where configuring custom security settings resulted in the workstation losing activation.
- 22067 Resolved an issue where installers for Deep Freeze Seed show wrong icon.
- 22177 Resolved an issue where the Deep Freeze Seed stops reporting after applying the update command from Deep Freeze Console.
- 22219 Resolved an issue where Remind me later option in the Deep Freeze Console upgrade notification does nothing.
- 22278 Resolved an issue where the Japanese translations for install/uninstall commands were incorrect.
- 22336 Resolved an issue where clicking the Remind Me Later button when prompted to install a downloaded Deep Freeze update had no effect.
- 22474 Resolved an issue where an incorrect warning message was shown when trying to install lower version of Deep Freeze Console.
- 22608 Resolved an issue where using a Combination Task from the scheduler creates a task out of order.
- 22644 Resolved an issue of BSOD when BitDefender Anti-Virus is installed.
- 23016 Resolved an issue where Deep Freeze Administrator shows “List index out of bounds” error.
- 23066 Resolved an issue where attempting to open a file when an .rdx or installer file was already open in the Configuration Administrator gave an error message.
- 23083 Resolved an issue where ThawSpaces got deleted on workstations when applying task through Update Workstation Task by importing an .rdx file where Delete during configuration update is enabled.
- 23113 Resolved an issue where using the Configuration Administrator in Windows 10 Fall Creators Update (64-bit) to repeatedly save then reload a configuration file would alter the available ThawSpaces.
- 23311 Resolved an issue where Deep Freeze Console reported an incorrect length of time thawed for workstations using versions of Deep Freeze below 8.50 under certain circumstances.
- 23583 Resolved an issue where Windows 10 system could not boot if secure boot was enabled.
Please Note : This version does not yet support installation on APFS formatted volumes, and will require user consent to load kernel extensions (more information here).
The updated versions can be downloaded from our Faronics Labs portal (for customers in North America) or from Faronics Customer Centre (for customers internationally).
And as always if you have any issues or concerns please reach out to our support team (support@faronics.com) and let us know.
↧
Product Activation Servers - Maintenance @ 2:00PM Pacific Time, Tuesday May 22, 2018
UPDATE: Activation servers are now all online and functioning properly.
Our product activation servers will be undergoing maintenance this afternoon (Tuesday May 22, 2018) at 2:00pm Pacific Time. During this time product activation requests will not be able to be processed either online or through a manual activation request.
Our team expects the maintenance to be finished and the Activation Servers to be back online no later than 8:00pm Pacific Time.
Workstations attempting to activate during this time may show a message indicating that they have failed to activate or that activation is pending in the Enterprise Console. Once the activation servers are back online systems will automatically attempt activation a second time.
Our product activation servers will be undergoing maintenance this afternoon (Tuesday May 22, 2018) at 2:00pm Pacific Time. During this time product activation requests will not be able to be processed either online or through a manual activation request.
Our team expects the maintenance to be finished and the Activation Servers to be back online no later than 8:00pm Pacific Time.
Workstations attempting to activate during this time may show a message indicating that they have failed to activate or that activation is pending in the Enterprise Console. Once the activation servers are back online systems will automatically attempt activation a second time.
↧
Deep Freeze Cloud Maintenance - Friday, May 25, 2018 06:00 PM to Saturday, May 26 08:00 PM Pacific Standard Time
Please be advised that Deep Freeze Cloud will be performing scheduled maintenance during the above time period. Deep Freeze Cloud will not be available during this period. Please plan accordingly. We apologize for inconvenience to you and your business.
↧
↧
Cloud Services Updates
Our operations team has informed us that some of our customers may experience issues with managing devices through our MDM solution today, they are working on addressing the issue and we anticipate a quick resolution to the problem.
Additionally some customers may see issues where the Deep Freeze Cloud Connector is disconnected from the customers Enterprise Console over the course of the weekend. The issue that caused this issue is resolved and if customers re-connect the Enterprise Console to the Deep Freeze Cloud they should see full resumption of services.
And finally we have released updated mobile applications for the Deep Freeze Cloud Services to address a couple of small issues, the most noticeable one being an issue where some customers may not be able to login to the Deep Freeze Cloud through the mobile application. Updating to the latest version of the Deep Freeze Administrator app will clear this issue up.
Additionally some customers may see issues where the Deep Freeze Cloud Connector is disconnected from the customers Enterprise Console over the course of the weekend. The issue that caused this issue is resolved and if customers re-connect the Enterprise Console to the Deep Freeze Cloud they should see full resumption of services.
And finally we have released updated mobile applications for the Deep Freeze Cloud Services to address a couple of small issues, the most noticeable one being an issue where some customers may not be able to login to the Deep Freeze Cloud through the mobile application. Updating to the latest version of the Deep Freeze Administrator app will clear this issue up.
↧
Deep Freeze 8.53 Standard Released
Faronics is happy to announce the release of Deep Freeze Standard 8.53
This release incorporates a number of fixes as listed here;
http://www.faronics.com/document-library/document/deep-freeze-standard-release-notes
Customers can download the updated release through our Faronics Labs or Faronics Customer Center (for international customers) portals.
This release incorporates a number of fixes as listed here;
http://www.faronics.com/document-library/document/deep-freeze-standard-release-notes
Customers can download the updated release through our Faronics Labs or Faronics Customer Center (for international customers) portals.
↧
Thawed computers in Deep Freeze Cloud
We discovered an issue today where computers with Deep Freeze Cloud installed might end up in Thawed State. The issue only affects customers that upgraded to version 8.53 approximately 30 days ago. Those computers are thawing on reboot because Deep Freeze believes that the license is no longer valid.
Our Engineers are diligently working to provide a solution that will address this issue. Once the solution is released to production, the update will automatically apply on a restart, during user login, or during the Cloud Agent heartbeat. If the computer is Thawed, you will need to send a Reboot Frozen command to the affected computer from your Deep Freeze Cloud console or Freeze it locally.
Stay tuned for an update on this post. Our sincere apologies for any inconvenience this may have caused.
Our Engineers are diligently working to provide a solution that will address this issue. Once the solution is released to production, the update will automatically apply on a restart, during user login, or during the Cloud Agent heartbeat. If the computer is Thawed, you will need to send a Reboot Frozen command to the affected computer from your Deep Freeze Cloud console or Freeze it locally.
Stay tuned for an update on this post. Our sincere apologies for any inconvenience this may have caused.
↧
Resolved : Issue where computers where thawed in the Deep Freeze Cloud
This morning a fix has been pushed to our production servers to address our previously reported issue where workstations could not be protected (frozen) using Deep Freeze Cloud. As previously mentioned this issue was due to our software incorrectly believing that the workstations license had expired on the client machine.
The update will automatically apply on a restart, during user login, or during the Cloud Agent heartbeat. If the computer is Thawed, you will need to send a Reboot Frozen command to the affected computer from your Deep Freeze Cloud console or Freeze it locally.
We apologize for the inconvenience and if there is anything that we can do to further assist you if you have been impacted please reach out and let our support team know - support@faronics.com or at 800-943-6422.
The update will automatically apply on a restart, during user login, or during the Cloud Agent heartbeat. If the computer is Thawed, you will need to send a Reboot Frozen command to the affected computer from your Deep Freeze Cloud console or Freeze it locally.
We apologize for the inconvenience and if there is anything that we can do to further assist you if you have been impacted please reach out and let our support team know - support@faronics.com or at 800-943-6422.
↧
↧
Issues enrolling iOS devices into Deep Freeze Cloud - Resolved
Update: 9:54pm Pacific Time Tuesday July 31, the issue has been resolved and users should now be able to enroll devices without issue. If you are still having problems please contact the support team (support@faronics.com)
Our operations team is currently investigating a reported issue where customers on one of the Deep Freeze Cloud servers are unable to enroll iOS devices into the platform.
As we get
Our operations team is currently investigating a reported issue where customers on one of the Deep Freeze Cloud servers are unable to enroll iOS devices into the platform.
As we get
↧
RESOLVED August 1, 2018 @ 1:18pm - Problems Enrolling iOS Devices in Deep Freeze MDM
Our operations team has let us know that some customers may be having issues with enrolling iOS devices into the Deep Freeze Cloud MDM. At this time the issue appears to be affecting customers logging into www1.deepfreeze.com.
If you are having issues please let the support team know (support@faronics.com) so that we can open a support ticket for you and update you on the status of this issue as we get more information back from our team.
If you are having issues please let the support team know (support@faronics.com) so that we can open a support ticket for you and update you on the status of this issue as we get more information back from our team.
↧
Update on Deep Freeze Mac and support for APFS
As our macOS users are aware Apple introduced a new file system with the release of macOS High Sierra and made it the default file system for several types of systems during the upgrade process. This has caused much difficulty for users of Deep Freeze since Deep Freeze did not support APFS at the time since it is a much different file system than what came before.
We are now nearing a point where we will be releasing a beta version of Deep Freeze Mac that will support APFS file
↧