Installation notes:

Will upgrade over any previous release

 

Changes

- A number of changes to increase performance and robustness for CCD. Internal ID# 1685, #1965, #1973, #1845, #1828, 1958

- A number of changes were made to improve security. Internal ID# 1821, #1811, #1822, #1805, #1804, #1808, #1812

- Incorrect Log Entry WindowsSearchModule did not start. Internal ID# 1920

- Teams configuration added to ADMX. Internal ID# 1878

- Added Retry on Disk Open when creating a new VHD. Internal ID# 1919

- Changes made to preserve HKLM\Software\FSLogix\Logging key during uninstall / install. Internal ID# 1871

- Change made to delete a new VHD if it is not successfully created through format. Internal ID# 1918

- Added functionality to replace windows shell with Frxshell (which only allows the user to log off) if there is an error attaching the VHD. This prevents a user from reverting to a local profile resulting in potential loss of data. Internal ID# 1949, #1378

- Correct issue with Blue Screen when .Frx file is removed from Rules directory. Internal ID #1801

- Resolved an issue where a user logoff would never occur when using Cloud Cache, and losing a connection to a file store. Internal ID# 1855

- Improved behavior when an attempt is made to mount a VHD and the volume is offline. Internal ID #1840

- GPO added to add WriteCacheDirectory. Internal ID# 1957

- Corrected an issue where IPs, reported through ICA, were incorrect. Internal ID# 1429

- Corrected an issue where Retry Count could be ignored. Internal ID# 1879

- Resolved an issue where users would be incorrectly blocked when PreventLoginWithFailure is set. Internal ID# 1984

- ADMX entry added for IncludeOutlookPersonalization. Internal ID# 1884

- A "Profile Logoff" event was added to the event log. Internal ID# 2014

- An issue was resolved which could cause Single User Search to not work. This issue was introduced in the 2.9.5 release. Internal ID# 2013

- ADMX Template updated to resolve an issue with Volume re-attach retry count. Internal ID# 1400

- ReportingURL registry key was removed from the default installation. Internal ID# 1896

- Resolved issue where, under rare circumstances and extreme (unlikely) load, logon could become unresponsive. This has not been reported in actual production use. Internal ID# 1693

- Added UseShortNameCacheFallback to frxdrvvt. Opt Out value turn ff changes made for #1693 above.

- Corrected an issue where Last write access time is updated incorrectly when OneDrive 'hydrates' a file. Internal ID# 1995

- Resolved an issue where CCD may not complete logon if Profile Type is set to 3. Internal ID# 2029

- Default for LockedRetryCount changed to 12 for both Profile Container and ODFC. Internal ID# 1983

- Optional functionality added to automatically remove previous OST files from VHD if a new OST files is created. Internal ID# 1758

- Resolved an issue where a VHD over 4GB may become corrupt when using CCD. Internal ID# 1960

- Product functionality changed so that default behavior is now the same as DisableRegistryLocalRedirect = 1 previously. Internal ID# 1976

- 2017 C++ redistribuatable components are now distributed and required

 

 

Please note that you will not receive any further email notifications for this topic unless you subscribe into it. 

 

OneDrive for Business and FSLogix best practices

Introduction

Microsoft OneDrive is one of the most popular products in the Microsoft Office 365 offering. As such, there are lots of customers that want to use OneDrive in their hosted digital workspace. Popular platforms to enable these hosted digital workspaces are Citrix ( XenApp / XenDesktop ), Microsoft RDS, VMware Horizon View, Amazon Workspaces, etc.

Problem

Due to OneDrive’s dependence on a local cache, the full version of OneDrive that synchronizes files from the cloud to the users’ desktops requires a persistent desktop. As with other applications that depend on a cache, OneDrive does not perform well in non-persistent desktop environments because the cache would have to be downloaded each time a user logged in. Placing the cache on a network share is impractical, and can result in extremely poor performance not just as desktops, but also on the network and file server. Plus, since OneDrive can also sync data stored in SharePoint, the impact on usability is even greater.

Microsoft’s only viable option for affected users/desktops is the online experience of OneDrive – meaning that the customer has to use a browser to access their files. This user experience is very different from when the OneDrive for Business is installed locally on physical PCs, laptops, Surface devices, or persistent VDI desktops. Unfortunately that means users either have to download/upload their files each time they use them, or they have to use the browser versions of Office applications, which increases the difference in user experience between persistent and non-persistent platforms.

FSLogix allows customers to offer the same OneDrive for Business experience on their non-persistent digital workspace as they would on their persistent desktops such as physical PCs, laptops or Surface devices – without any compromise in the user experience or OneDrive for Business or SharePoint functionality.

 

Read the full article here

New Release: FSLogix Apps 2.9 (2.9.6755.61370)

This is a GENERAL release

Applies to:
All supported Windows OS versions (Windows 7 and later, Server and Client 32 and 64 bit)


Installation notes:
Will upgrade over any previous release.

Changes:
- Full support for Files On Demand feature of OneDrive
- Now redirect the OneDrive temporary cache location (C:\OneDriveTemp) into the Profile and O365 VHD container.
- Fixed an issue where the user logoff would hang
- FSLogix Service (frxsvc.exe) crash fix
- Fix issue where the EULA would keep prompting with OneNote
- Fixed Java redirection when a proxy pack or deployJava.js is used
- Fixed "Full VHD(X) Allocation" setting in ADMX/ADML files

deviceTRUST 18.1 released

We are very proud and excited to release our new deviceTRUST version 18.1. This release includes many new features and capabilities that give our customers even more ways to increase and simplify their context-based security and user experience. 

More and more companies are planning to use cloud providers for the provision of a Desktop-as-a-Service. For this reason deviceTRUST now supports Amazon WorkSpaces with all product features and functions. This gives today’s customers the future security for tomorrow's technologies.

Our deviceTRUST Client for Windows has been significantly simplified and can now be installed for the user via a download link with just a few clicks. In addition, the client now includes an auto-update function that can be controlled centrally by corporate policy. This does not require any further user interaction. 

The transmission of device properties within the deviceTRUST protocol is now additionally encrypted end-to-end to further increase data security, providing an additional layer on top of the security provided by the underlying remoting protocols.

Contextual Group Policies within the virtual session can be set based on the context of the endpoint. For example, the screen saver settings within the virtual session can be defined based on the settings of the screen saver on the endpoint on Logon, Reconnect and during session runtime.

More detailed information can be found on our website.

This is a GENERAL release

Applies to:
All supported Windows OS versions (Windows 7 and later, Server and Client 32 and 64 bit)


Installation notes:
Will upgrade over any previous release.

Changes:
• Attempting to use FSLogix Single-User Search Roaming (Type 1) with Citrix Application Layering results in an error. This issue occurs because Citrix Application Layering does not allow renaming of certain files and folders. FSLogix changed their agent to not require renaming of any folders or files in order for Search Roaming to work.
• An issue with first time OneDrive installation has been resolved. The issue occurred when OneDrive was installed for the first time, and OneDrive syncing began. The FSLogix agent would not redirect the OneDrive files to the VHD/X container until the user logged off and then back on again. The FSLogix agent has been enhanced to detect that OneDrive is being installed, and now immediately begins redirecting the OneDrive files to the VHD/X.
• Improved handling of index corruption when using multi-user search roaming
• Fixed an issue where Office Activation would sometimes fail when using FSLogix Office 365 Containers

Joomla3 Appliance - Powered by TurnKey Linux