FSLOGIX 2210 breaks Office Activation ??

Meyer, Uwe 0 Reputation points
2023-01-26T13:43:01.53+00:00

Hi,

we use a Terminalserverfarm with Windows Server 2019, CVAD 2203 LTS and FSLOGIX.

 

Everything was going fine until we installed the latest version of FSLOGIX - the version 2210.

After that, when you start Office or Teams, the Microsoft login appears. After the access data has been entered here, the products work perfectly. But after logging out and logging back in, the MS login mask appears again when you start Team or Office. This was not the case with the old FSLOGIX versions.

After I then downgraded back to version 2.9.8228.50276, everything works fine again.

We use FSLOGIX with the ProfileContainer.

Does anyone happen to have the same problem? Or does someone know a solution?

Thank you for your support.

 

Regards

Uwe

FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
463 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 43,966 Reputation points
    2023-02-01T11:22:19.76+00:00

    Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query.

    It sounds like the issue you are experiencing is related to the interaction between FSLOGIX version 2210 and the Microsoft Office or Teams applications.

    FSLOGIX is a software package that provides profile and data virtualization for Microsoft Office 365, and it appears that the latest version (2210) is causing issues with the login process for these applications.

    Downgrading to version 2.9.8228.50276 is resolving the issue for you, which suggests that the problem is specific to version 2210.

    It's possible that the new version of FSLOGIX has a bug that is causing this issue, or that it has a change that is not compatible with the way that Office and Teams handle login.

    You can contact the FSLOGIX support team for more information or try to look for the release notes of the 2210 version to see if they have any related troubleshoot.

    Also, you can try to check if the problem is specific to your environment or if it is affecting other users or systems. If the problem is isolated to your environment, you can try to troubleshoot the specific settings and configurations that are causing the issue.

    Additionally, you can try to check if there's any missing prerequisites that is causing the issue.

    It's always important to test new software versions in a test environment before deploying them to production systems to avoid this kind of issues.

    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.