User Profile
SteveDMSFT
MicrosoftJoined Feb 07, 2018
User Widgets
Recent Discussions
AVD now supports Azure Compute Gallery custom images with Trusted Launch enabled
Azure Virtual Desktop now supports provisioning Trusted Launch virtual machines with custom images stored in an Azure Compute Gallery. Trusted Launch protects against advanced and persistent attack techniques by combining technologies which can be independently enabled, such as Secure Boot and a virtual Trusted Platform Module (vTPM. Key benefits of Trusted Launch virtual machines are: • Protect against the installation of malware-based rootkits and bootkits with Secure Boot. • Provide your VM with its own dedicated Trusted Platform Module instance with a TPM 2.0 compliant vTPM. • Protect Windows kernel-mode processes against injection and execution of malicious or unverified code with Hypervisor Code Integrity. • Isolate and protect secrets so that only privileged system software can access them with Windows Defender Credential Guard. Please review the Trusted Launch and Azure Compute Gallery documentation for more information on those capabilities.5.6KViews0likes1CommentAnnouncing General Availability of FSLogix 2201 (2.9.8111.53415)
Today we are announcing the General Availability of FSLogix 2201. Updates include improvements to login and logoff times, cloud cache performance improvements, and 30+ accessibility updates. Download Location https://aka.ms/fslogix_download Installation notes This release can be installed over previous versions of FSLogix. Installation Instructions: Install FSLogix Agent - FSLogix | Microsoft Docs Changes • Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. • The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. • Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. • Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. • FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value. • Over 30 accessibility related updates have been made to the FSLogix installer and App Rules Editor. • A Windows event now records when a machine locks a container disk with a message that looks like "This machine '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]." This event is generated from the METADATA file created in the user's profile directory. This file can be ignored, but not deleted. • Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was ignored in some cases. • Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail. • Fixed an issue where FSLogix did not properly handle logoff events if Profile or ODFC containers were disabled during the session or per-user/per-group filters were applied mid-session that excluded the user from the feature. Now FSLogix logoff related events will always occur based off the FSLogix settings applied at login. • FSLogix will no longer attempt to reattach a container disk when the user session is locked. • Fixed an issue that caused the FSLogix service to crash when reattaching container disks. • Fixed a Cloud Cache issue that caused IO failures if the session host's storage block size was smaller than a cloud provider's block size. For optimal performance, we recommend the session host disk hosting the CCD proxy directory has a physical block size greater than or equal to the CCD storage provider with the largest block size. • Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) was not handled properly and would eventually fail. • Reduced the chance for a Cloud Cache container disk corruption if a provider is experiencing connection issues. • Resolved an issue where temporary rule files were not deleted if rule compilation failed. • Previously, the Application masking folder was only created for the user who ran the installer. With this update, the rules folder is created when the Rules editor is launched. • Resolved an interoperability issue with large OneDrive file downloads that was causing some operations to fail. • Fixed an issue where per-user and per-group settings did not apply if the Profile or ODFC container was not enabled for all users. • Resolved an issue where the Office container session configuration was not cleaned up if a profile fails to load. • Fixed an issue where HKCU App Masking rules leveraging wildcards would fail to apply. • Fixed an issue that caused some sessions configured with an ODFC container to fail to login. • Resolved an issue where the App Rules editor would crash if no assignments were configured. Resources FSLogix documentation: https://aka.ms/fslogix Download Location: https://aka.ms/fslogix_download37KViews4likes76CommentsRe: Announcing General Availability of FSLogix 2201 (2.9.8111.53415)
Ryand32 can you clarify why you need concurrent connections with Cloud Cache? The two things are not related and you're actually missing out on significant improvements to Cloud Cache by not upgrading - and exposing yourself to a security vulnerability that we patched in cloud cache. Concurrent connections only apply to a niche scenario where a single user must be able to have multiple WINDOWS sessions simultaneously on the same session host. Most customers do not need or want the same customer to have multiple Windows sessions on the same VM. They might allow multiple Citrix or VMware sessions - but all those sessions, by default, share a single Windows session. That said, we only removed the concurrent setting from FSLogix because the setting is already available as an RDS policy. If you wish to allow users to launch multiple sessions then you'll find the setting in "Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections". From there, set "Restrict Remote Desktop Services user to a single Remote Desktop Services session" to "Disabled".5.9KViews0likes48CommentsThe FSLogix 2201 Public Preview is now available
FSLogix 2201 Public Preview Update 1 has been published to address the issue outlined below. Please read details here. FSLogix 2201 is now available in Public Preview. This public preview is not recommended for production workloads. Please leverage your standard Microsoft support channels to report issues with this public preview release. ISSUE IDENTIFIED IN THIS PUBLIC PREVIEW RELEASE: We discovered an issue with the 2201 public preview that is impacting customers with session hosts configured to allow users to have more than one Windows session per user per host. In those situations, only that user's first session to a host will connect. Additional connections for that user to that host will fail to login. Your environment is impacted by this bug if you have the "Restrict Remote Desktop Services users to a single Remote Desktop Services Session" group policy set to disabled or the HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services\fSingleSessionPerUser regkey value is set to 0. We recommend impacted customers not install this public preview or revert back to the current generally available release. We are validating a fix for the issue and will publish an update to the public preview when it is available. Customers not impacted by this issue can continue validating this public preview release. Preview Details You can sign up here to participate in the Public Preview: https://aka.ms/fslogix/preview This release can be installed over all existing versions of FSLogix or you can perform a fresh install without a pre-existing FSLogix version. Here's what's new in this release: Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value. Over 30 accessibility related updates have been made to the FSLogix installer and App Rules Editor. A Windows event now records when a machine locks a container disk with a message that looks like "This machine '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]." Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was sometimes ignored. Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail. FSLogix will no longer attempt to reattach a container disk when the user session is locked. Fixed an issue that caused the FSLogix service to crash when reattaching container disks. Fixed a Cloud Cache issue that caused IO failures if the session host's storage blocksize was smaller than a cloud provider's. For optimal performance, we recommend the session host disk hosting the CCD proxy directory has a physical block size greater than or equal to the CCD storage provider with the largest blocksize size. Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) was not handled properly and would eventually fail. Reduced the chance for a Cloud Cache container disk corruption if a provider is experiencing connection issues. Resolved an issue where temporary rule files were not deleted if rule compilation failed. Previously, the Application masking folder was only created for the user who ran the installer. With this update, the rules folder is created when the Rules editor is launched. Resolved an interoperability issue with large OneDrive file downloads that was causing some operations to fail. Fixed an issue where per-user and per-group settings did not apply if the Profile or ODFC container was not enabled for all users. Resolved an issue where the Office container session configuration was not cleaned up if a profile fails to load. Fixed an issue where HKCU App Masking rules leveraging wildcards would fail to apply. Fixed an issue where FSLogix did not properly handle logoff events if Profile or ODFC containers were disabled during the session or per-user/per-group filters were applied mid-session that excluded the user from the feature. Now FSLogix logoff related events will always occur if FSLogix loaded a container for the user. Fixed an issue that caused some sessions configured with an ODFC container to fail to login. Resolved an issue where the rule editor would crash if there were no assignments configured.41KViews4likes81CommentsRe: The FSLogix 2201 Public Preview is now available
Thanks vara93. Gonzalo is a support engineer, not a developer, and is responding to an issue not related to this public preview. We are aware of existing black screen issues and are working on them. However, you indicated a new issue in this public preview. If you're referring to the older issue and not something new then please open a support ticket.4.2KViews0likes2CommentsFSLogix 2201 Public Preview Update 1 is now available
Hi Everyone, We've just released FSLogix 2201 Public Preview Update 1 to address the previously announced issue impacting customers who allow users to have multiple Windows sessions per session host. To recap the resolved issue, customers who allow users to login to multiple Windows sessions per host encountered a bug that allowed the first user session to connect, but additional session launches failed. With this update, additional sessions will no longer fail. Your environment was impacted if you have the "Restrict Remote Desktop Services users to a single Remote Desktop Services Session" group policy set to disabled or the HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services\fSingleSessionPerUser regkey value is set to 0. Preview Details NOTE: Existing public preview participants do not need to sign up again. A new download link will be sent to the provided email address. You can sign up here to participate in the Public Preview here: https://aka.ms/fslogix/preview This release can be installed over all existing versions of FSLogix or you can perform a fresh install without a pre-existing FSLogix version. Here's a complete list of updates in the 2201 Public Prevew: Update 1 Changes Resolved an issue in the initial 2201 Public Preview release that prevented additional connections for environments configured to allow users to have more than one Windows session per host. Previously Announced Changes Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value. Over 30 accessibility related updates have been made to the FSLogix installer and App Rules Editor. A Windows event now records when a machine locks a container disk with a message that looks like "This machine '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]." Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was sometimes ignored. Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail. FSLogix will no longer attempt to reattach a container disk when the user session is locked. Fixed an issue that caused the FSLogix service to crash when reattaching container disks. Fixed a Cloud Cache issue that caused IO failures if the session host's storage blocksize was smaller than a cloud provider's. For optimal performance, we recommend the session host disk hosting the CCD proxy directory has a physical block size greater than or equal to the CCD storage provider with the largest blocksize size. Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) was not handled properly and would eventually fail. Reduced the chance for a Cloud Cache container disk corruption if a provider is experiencing connection issues. Resolved an issue where temporary rule files were not deleted if rule compilation failed. Previously, the Application masking folder was only created for the user who ran the installer. With this update, the rules folder is created when the Rules editor is launched. Resolved an interoperability issue with large OneDrive file downloads that was causing some operations to fail. Fixed an issue where per-user and per-group settings did not apply if the Profile or ODFC container was not enabled for all users. Resolved an issue where the Office container session configuration was not cleaned up if a profile fails to load. Fixed an issue where HKCU App Masking rules leveraging wildcards would fail to apply. Fixed an issue where FSLogix did not properly handle logoff events if Profile or ODFC containers were disabled during the session or per-user/per-group filters were applied mid-session that excluded the user from the feature. Now FSLogix logoff related events will always occur if FSLogix loaded a container for the user. Fixed an issue that caused some sessions configured with an ODFC container to fail to login. Resolved an issue where the rule editor would crash if there were no assignments configured.5.5KViews0likes9CommentsRe: The FSLogix 2201 Public Preview is now available
That thread is long and loaded with incorrect info so I can't say what's been fixed. The thread starts with the suggestion that FSLogix is locking Credentials folders, but FSLogix only applies locks to the VHD/x containers. Something else is causing those locks. The thread also mentions the refCount issue, but that's incorrectly correlated with this issue. The refCount key value mentioned in that thread can be updated by MANY activities not related to FSLogix and FSLogix does not manipulate that value directly. The 2201 public preview implements a fix that cleans up the refCount value when it is left in an incorrect state. To be clear, FSLogix is not putting it in a bad state but that incorrect value is causing issues for FSLogix. For reference, that bad refCount value was also causing issues with non-FSLogix Windows profiles and we implemented the same fix in FSLogix.18KViews0likes0CommentsRe: The FSLogix 2201 Public Preview is now available
We're not tracking an issue with log redirection. What are you seeing? Some customers have issues with log redirection because they apply the redirection via group policy or some other means that applies the redirection AFTER the FSLogix service starts. The reg key needs to be applied before the service starts. Also, you should consider using the FSLogix event logs instead of the log files.18KViews0likes1CommentRe: The FSLogix 2201 Public Preview is now available
We revised that bullet to be more clear. This is related to a specific cache folder and you should not see an impact. That said, please test the public preview and let us know if you see any issues. Let me know if you need clarification: The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update.19KViews2likes0CommentsPUBLIC PREVIEW: FSLogix Release 2105 is now available in Public Preview
New Public Preview: FSLogix Release 2105 (2.9.7802.10873) Please note this public preview will not install on Windows 7 due to a certificate signing issue that is expected to be resolved by a future Windows update. While participating in this public preview, please use your standard method to obtain support. Please fill out this form to participate and receive the link to download this update: https://aka.ms/fslogix/preview Full release notes: This is a PUBLIC PREVEW release NOTE: A certificate signing update in Windows 7 currently prevents this release from being installed on Windows 7. An upcoming Windows 7 update is expected resolve this issue. Applies to: All supported Windows OS versions To participate in the public preview please sign up here: https://aka.ms/fslogix/preview Installation notes: Will upgrade over any previous release. Changes: Various updates were made to improve login time. Fixed an issue where users could fail to login if a VHD network location was unavailable. You can now increase the size of an existing VHD(x) by updating the SizeinMB setting. The RefreshUserPolicy setting can now be managed via group policy template (ADMX). The Installed Version of FSLogix is now written to the registry (HKLM:Software\FSLogix\Apps:InstallVersion). Fixed an issue where Type4 printer drivers worked after initial configuration, but not subsequent sessions. Orphaned/corrupt NST files are now cleaned up along with OST files. Resolved a Cloud Cache bug where a second machine accessing the RW disk gets permanently locked out. Fixed an issue compiling AppMasking rules with a destination in HKCU. Fix an issue where FSLogix could cause a deadlock and prevent user connections. Fixed various issues that could crash the FSLogix service. Resolved an issue causing frxshell to not launch on non-English systems Resources: FSLogix documentation: https://aka.ms/fslogix Microsoft Q&A Site: https://docs.microsoft.com/en-us/answers/topics/windows-server-fslogix.html Open a support ticket: https://social.msdn.microsoft.com/Forums/en-US/14ea5f6f-760b-4ad2-83cf-23c3cbc1bcc4/how-to-open-an-fslogix-support-request?forum=FSLogixindex.php/knowledge-base8.6KViews3likes0CommentsRe: Sync isn't available for this account
Just to follow up on this, my issues went away. My problems were caused by having a work and personal account with the same email address. Microsoft no longer supports that and won't let users create work and personal accounts from the same email. I was able to sync after I changed my personal email to an outlook.com address. So in short, I had 3 accounts: 1) Microsoft employee "work account" 2) My own O365 "work account" 3) A personal account with the same address as #2. I flipped my personal to something@outlook.com and sync started working.25KViews1like1Comment
