Jump to content

vRickE

Members
  • Posts

    109
  • Joined

  • Last visited

  • Days Won

    1

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We would like to dynamically manage the Start Menu Layout for our users based on OS or Applications they have entitled using DEM. If I try to use registry imports, It looks like DEM is not able to import the configuration to HKCU\Software\Policies\Microsoft\Windows\Explorer\ even though on the logs says it is successful and neither will accept the ADMX/L template and it says is not compatible. Has anyone managed to configure this with DEM or is this one of those we need to handle with GPO?
  2. How does this look like when you disable the parent VM or use Mode B?
  3. Export a log bundle from the UAG and look at the log called esmanager.log look for entries related to samlsso. It might give you the UAG side of the story. I am too dealing with some issues with Dell Thin OS, but mine started after upgrading to UAG 2312 and using the ThinOS 2405 with client 2312 SDK version which is what they say to use now. If I roll back to the client non-SDK version, it works fine. But checking the thin OS logs I see the same event you are seeing, and the users get an error You are not Entitled to use the system!
  4. I am working on an environment where we have this combination, and we are due to update the certificates soon. When I updated the certificate on the lab environment it broke SAML authentication with an error 401 right after the authentication. Upon inspecting the UAG and ADFS logs it seems like when the Relaying Party trust was configured from the file downloaded from the UAG, it included the old certificate in the signature. I am newish to SAML and ADFS, but is the expectation, any way to avoid? Or is my cert replacement going to have an additional level of pain to it?
  5. I have seen issues like this with writable and the new teams. AppVolumes 2312.2 is supposed to fix these issues. https://docs.omnissa.com/bundle/AppVolumesReleaseNotesV2312.2/page/AppVolumes-ReleaseNotes.html “new Microsoft Teams” application fails to launch when Profile-only or UIA+profile Writable Volume is attached to the agent computer. NOTE: When this issue occurs, no error message is displayed by the application. [AVA-23756]
×
×
  • Create New...