Skip to main content
M
MattDB
Participant
October 27, 2023
Question

macOS: Unable to Restrict Access to CC Desktop Application App Panel

  • October 27, 2023
  • 1 reply
  • 1920 views

I'm trying to restrict access to the App Panel in the CC Desktop App on student lab machines, but have been unable to do so recently. The target computers are running macOS 13.6. As a test, I've created a new managed package in the Admin Console that includes just the CC Desktop App, configured with the options to hide access to the app panel. However, after the installation, the app panel remains freely accessible. I've verified that the ServiceConfig.xml file is getting installed along with the app and that it does contain the correct key values needed for restricting the App Panel. I've been able to recreate this issue on newly restored or imaged computers with nothing but just the Adobe CC Desktop app installed. Everything seems to work as expected when installing managaged packages created the same way for our Windows devices. It's as if the current version of the Adobe CC Desktop app for macOS is just ignoring the ServiceConfig.xml file altogether. Has anyone else experienced this issue?

 

Steps to reproduce:

Hardware: Apple Silicon based Mac running clean install of macOS 13.6

1. Create a new macOS (Universal) managed package in the Admin Console

2. Add the Creative Cloud Destkop Application (6.0.0) to the package

3. Deselect "Enable Self-Service Install" under options

4. Create package. 

5. Install package on the target computer.

6. Launch Adobe Creative Cloud Destkop Application and verify whether App Panel is restrcited.

    This topic has been closed for replies.

    1 reply

    rpandita
    rpandita
    Inspiring
    October 30, 2023

    Hi MattDB

     

    Can you please share the service config file here?

     

    Regards

    Rohit Pandita

    R
    rstaselbeta
    Inspiring
    November 1, 2023

    I'm seeing exact same behavior. We have lab users (which are on SDL) installing 2024 apps and breaking all our attempts to keep labs standardized across campus. 

     

    Here's our ServiceConfig.xml

    <config><panel><name>AppsPanel</name><visible>false</visible></panel><panel><name>FilesPanel</name><masked>true</masked></panel><panel><name>MarketPanel</name><masked>true</masked></panel><feature><name>SelfServeInstalls</name><enabled>false</enabled></feature><feature><name>BrowserBasedAuthentication</name><enabled>false</enabled></feature><feature><name>SelfServePluginsInstall</name><enabled>false</enabled></feature><feature><name>AppsAutoUpdate</name><enabled>false</enabled></feature><feature><name>AdobeFallbackForAUSST</name><enabled>false</enabled></feature><feature><name>AppsCategories</name><enabled>false</enabled><data><categories><category>beta-apps</category></categories></data></feature></config>

    R
    rstaselbeta
    Inspiring
    November 1, 2023

    does not appear to be hardware or OS linked. I just tested on an Intel mac running 12.6.9. Appears that CC 6.0.0 is just ignoring these settings. =/ Windows CC app seems to behave as expected and disables self service install. 

    Tangential: how about the CC app just used a standard plist so we could manage these settings via a config profile instead of this pseudo XML... Why does Adobe make this so obnoxious? we end up having to write custom checks to see what these values are set to instead of just using built in OS level functionality to force it. Same with windows side... heaven forbid it was just registry settings that could be set via GPO, Intune, etc... instead we have the same crap. 

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices