Public bug reported: [Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed folders. adsysctl expects the folders to be title cased (e.g. Machine), but they are uppercase (e.g. MACHINE). This prevents any GPOs from being applied. This is a common occurence with GPOs created by Microsoft, like the Default Domain Policy. [Test Plan] * Mark the Default Domain Policy as active for the client. * Restart and/or manually sync the client machine. * Observe the log message indicating that parsing the GPO failed: Policy "Default Domain Policy" doesn't have any policy for class "user" open /var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol: no such file or directory [Where problems could occur] * Fixing this bug will allow adsys to parse, and possibly fail when applying policies from an uppercase path, whereas before it silently ignored them. Fixes for these potential bugs have also been submitted. [Other Info] The issue was initially reported on GitHub: https://github.com/ubuntu/adsys/issues/346 ** Affects: adsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982330 Title: Cannot apply policies from uppercase class path like "MACHINE" Status in adsys package in Ubuntu: New Bug description: [Impact] ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed folders. adsysctl expects the folders to be title cased (e.g. Machine), but they are uppercase (e.g. MACHINE). This prevents any GPOs from being applied. This is a common occurence with GPOs created by Microsoft, like the Default Domain Policy. [Test Plan] * Mark the Default Domain Policy as active for the client. * Restart and/or manually sync the client machine. * Observe the log message indicating that parsing the GPO failed: Policy "Default Domain Policy" doesn't have any policy for class "user" open /var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol: no such file or directory [Where problems could occur] * Fixing this bug will allow adsys to parse, and possibly fail when applying policies from an uppercase path, whereas before it silently ignored them. Fixes for these potential bugs have also been submitted. [Other Info] The issue was initially reported on GitHub: https://github.com/ubuntu/adsys/issues/346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp