Voila, no more Files panel! But, but, I want to hide the other things… Here’s the result when the CCDA is next launched: So what if we were to add a visible key under FilesPanel, like so? Also notice that our CCDA screenshot above is missing its Apps panel (which is good for labs!)… A clue. Now look at the AppsPanel key and notice it has a visible key, that’s set to false. This disables the panel’s functionality but leaves it visible. Let’s have a look at ServiceConfig.xml again, focusing on the FilesPanel key:
DISABLE ADOBE CREATIVE CLOUD TRIAL
Wouldn’t it be better to just remove that panel altogether? Ignorance is bliss, right? It turns out, through some trial and error, that you can. Telling folks they don’t have access to something because IT said so is a surefire way to annoy them and generate lots of questions.
If we leave it ticked to disable file syncing (which you might want to do for computers that shared by many people, to help performance), users are greeted with this in the Files panel of the CCDA: But I want to hide the thing…
You’ll find there’s more to this once you scratch beneath the surface…įast forward to 2019 with the advent of Shared Device Licensing, and we have this option when we’re creating a package in the Admin Console: So do read that if this is something you’re encountering for the first time. This is especially interesting if you wanted to have a bit more control over what’s shown or hidden post-deployment (because sometimes we change our minds).īen Toms goes into the gory details here.
DISABLE ADOBE CREATIVE CLOUD WINDOWS
On macOS it lives in /Library/Application Support/Adobe/OOBE/Configs/ and on Windows it’s in C:\Program Files (x86)\Common Files\Adobe\OOBE\Configs\. If you’ve ever deployed the Adobe Creative Cloud Desktop App (CCDA) or any Adobe application that uses it, you might have come across this little nugget.
0 kommentar(er)
