(Case No: SVY-817-92683)Ģ0074 Installing Deep Freeze on workstations in some circumstances results in slow login when in a Frozen state. (Case No: OWZ-638-83495)ġ9676 The workstation column width in the Enterprise console may revert to zero after it has been moved. (Case No: ZME-498-42392, NES-367-79748, XQL-319-44460, YAE-971-22805)ġ8513 Installation of Deep Freeze workstation fails if user login name contains double byte characters. (Case No: TRV-310-98644)ġ2491 Deep Freeze console columns may show wrong status or the console may show error messages when connected remotely through LogMeIn or RDP session. (Case No: EGF-242-16878)ġ2344 Deep Freeze console does not sort IP Address column correctly. BSOD occurs on reboot on Windows 8 and higher computers with single or multiple NTFS Storage Spaces. KBP-466-59587)ġ1387 NTFS Storage Spaces not supported. ESK-568-54530, MMR-516-77876)ģ6010 Resolved an issue where workstations were randomly disappearing from the master console and remote consoles after updating to the latest Deep Freeze Enterprise version. UZN-971-68888, UCK-583-96692-1)ģ4781 Resolved an issue where Deep Freeze workstations could not boot Frozen when Windows Update system history had permanent entries with Staged status. TWX-508-88232)ģ3350 Resolved an issue with being unable to install on-premise Deep Freeze Enterprise after uninstalling Deep Freeze Cloud Agent and vice versa. UFN-737-75949)ģ1754 Resolved an issue with being unable to lock the mouse/keyboard on a Lenovo Touchpad laptop. Faronics has since decided to drop official support for this operating system due to functionality issues.Ģ8484 Resolved an issue where Windows 10 workstations randomly hung when Deep Freeze was in Frozen state while an older Windows Xbox driver is installed.ģ1618 Resolved an issue where rebooting Deep Freeze to Frozen status from RDP resulted in Deep Freeze rebooting to Frozen & Locked status. Windows To Go End of Support: Microsoft dropped support for Windows To Go from Windows 1903 onwards.Deep Freeze 8.63 supports Windows 11, which has been extensively tested without any known issues detected.Workaround/Solution: Disable NLA in the connection properties in Royal TS under Advanced. Possible cause: This can be caused by NLA, or can occur when connected to non-domain joined machines from an Azure AD (MS365) joined machine Message: An authentication error has ocurred (Code: 0x80004005). Workaround/Solution: Restart the Windows Audio Service on the remote machine or disable Audio Redirection. Possible cause: Windows Audio Service is not responding. Issue: RDP Sessions sometimes stuck in an infinite loading loop Workaround/Solution: Disable the logon message. Possible cause: After installing Windows 8.1 update, a connection can fail when an RD gateway server is used and a logon message is configured. Return Code (Disconnect Reason) = 50331677 You may also need to disable the requirement for NLA on the server you want to connect to (in the System Properties -> Remote). Possible cause: When using RDP through a Cisco ASA (SSL VPN) device, NLA can cause connectivity issues. Return Code (Disconnect Reason) = 4: An internal error has occurred.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |