Skip to main content
kentw31957778
kentw31957778
Inspiring
January 16, 2017
Answered

CC for Enterprise, Mac, Serialized, How to Disable "Sign in" Prompt When Starting Apps?

  • January 16, 2017
  • 4 replies
  • 5295 views

I'm new to Adobe CC Licensing. Trying to deploy CC in several labs full of Macs. The fourth lab prompts the user to sign in (the app that does the prompting seems to be Adobe Application Manager).

These labs did have CC 2015; in two of them I completely reimaged the machines (using Dell/Quest KACE) with a fresh CC2017-bearing Mac image; they seem to work fine. Another lab I uninstalled the 2015 apps first, as best as I could (there doesn't seem to be a good way to uninstall CC - all I could find was to uninstall each app individually, then use the Adobe Cleaner), and then used a package (built using the packager (another complication that seems unnecessary to me)) to install all the CC2017 apps; this lab seems to work fine. The fourth lab, to save time (I need the labs working by start of classes tomorrow), I just installed the 2017 package alongside the existing 2015 package. It's in this lab I get the sign-in prompt.

So I uninstalled all of 2015, and all of 2017, and used the cleaner, then reinstalled the 2017 package. Still I'm asked for the sign-in.

I do not need my students confused by this Adobe Application Manager opening up and prompting them to sign in when they open up something like Photoshop or InDesign. I've been trying everything I can find on the web to solve this issue, with no joy, and I'm quite frustrated. Hopefully someone on this forum can guide me to a solution.

Thanks!

--

Kent

    This topic has been closed for replies.
    Correct answer kentw31957778

    Glad to hear that you have made progress. If you want to send me your case number via private message I can investigate further, from your description it doesn't sound like your case should have been closed.


    My process above worked on the lab machines in one lab, but not on the Teacher's Station machine. But the following process did:

    - Run any Adobe uninstallers available.

    - Run the Adobe Cleaner Tool.

    - Drop into a Terminal as root and manually scour the system for any references to Adobe (there were a lot left over - you'd think the Cleaner Tool would be more robust) and remove them. (particularly in places like /Library/Launch*; /System/Library/Launch*; /System/Library/User Template/English.lproj/Library/Launch*; ~/Library/Launch*; /Applications; /Applications/Utilities; /Library/Application Support)

    - Reboot

    - Reinstall the CC package again (I used the same one I had been using, without the Desktop app)

    Very labor intensive and time-consuming. It would have been FAR preferable if Adobe, who presumably knows how their own software works, would have simply provided a one-step fix to completely remove the cursed Desktop app.

    A thorough FAIL on the part of Adobe, in my view. No need to investigate further; my Adobe rep was in town last week, and when he couldn't solve the problem, he's the one that started the ticket for me, and when I informed him they had closed the ticket, he offered to have it reopened, but by that time I was so close to having it solved myself that I just didn't want to bother with Adobe's tech support any more, figuring that'd be more painful than just finishing the job myself. Thank you for the offer, though.

    4 replies

    alisterblack
    alisterblack
    Inspiring
    January 24, 2017

    What you see in the second screen is not the Creative Cloud Desktop App, but rather Core Components: "Core Components is always selected, and you cannot deselect it. This option deploys the common licensing infrastructure to client machines." Create packages with Serial number licenses

    kentw31957778
    kentw31957778Author
    Inspiring
    January 24, 2017

    Okay, that's good to know. (It seems to me that naming it "Creative Cloud Core Components" would cause less confusion. Or better, don't even show it as an option since it isn't one.)

    However, as good as it is to know this detail, it doesn't get me any closer to getting rid of the "Sign in" nag-screen.

    alisterblack
    alisterblack
    Inspiring
    January 24, 2017

    At this stage I recommend gathering logs and contacting support.

    Please use the log collector tool: Log Collector Tool

    To contact support please use one of the following options.

    Creative Cloud for Enterprise - from the Admin Console go to the support tab to open a case. Phone and chat options are also available here.

    Creative Cloud for Teams - from the CCT Admin Console go to the Help tab for chat and phone options.

    Alternatively please Contact Customer Care

    JohnBNO
    JohnBNO
    Inspiring
    January 19, 2017

    We have the same issue as well with Mac OSX  and Windows. We don't have the manpower to fix this issue by ones and twos, etc.

    alisterblack
    alisterblack
    Inspiring
    January 20, 2017

    Hi, JohnBNO are you using a serial number?

    JohnBNO
    JohnBNO
    Inspiring
    January 20, 2017

    Yes, license serial number deployment. The user is not required to log on with an Adobe ID to use the software but the popup to logon persists at boot up.

    alisterblack
    alisterblack
    Inspiring
    January 17, 2017

    Try this, then run the serialization file again. You can also run the Cleaner Tool again to clean up licensing information.

    The opm.db file contains cached user login information and deleting this file is a useful troubleshooting step. Once deleted a fresh file will be automatically created when you launch Creative Cloud and log back in

    .

    • Close the Creative Cloud application.
    • Navigate to the OOBE folder.
      Windows: [System drive]:\Users\[user name]\AppData\Local\Adobe\OOBE
      Mac OS: /Users/[user name]/Library/Application Support/Adobe/OOBE folder
    • Delete the opm.db file.
    • Launch Creative Cloud.

    kentw31957778
    kentw31957778Author
    Inspiring
    January 18, 2017

    I moved the opm.db file to the Trash.

    I then tried to Empty the Trash, but couldn't as "the file is in use".

    So I logged out and logged back in, and the opm.db file had been recreated.

    I moved that one to the Trash.

    I then started Photoshop.

    Same problem - I'm prompted to log in.

    So I moved the opm.db file to the Trash again.
    Then I rebooted (and the Finder window opened to where I had left it).
    The opm.db file was recreated as I watched, before I touched the computer.
    I then started Photoshop.Same problem - I'm prompted to log in.

    So I moved the opm.db file to the Trash again.

    Then I rebooted (and the Finder window opened to where I had left it).

    The opm.db file was recreated as I watched, before I touched the computer.

    I emptied the Trash.

    Then I ran the serializer.

    Then I started Photoshop.

    Same problem - I'm prompted to log in.

    alisterblack
    alisterblack
    Inspiring
    January 19, 2017

    Yes, the OPM.db will recreate itself, this is the file that contains the licensing details. The point of deleting it is in case of any corruption.

    At this point I would advise to follow the same process as for the other machines, remove all Adobe apps from the machine, run the cleaner and then deploy a serialized package.

    alisterblack
    alisterblack
    Inspiring
    January 17, 2017

    Using the packager you can create a license file for your serial number and apply that to the machine.

    Creative Adobe Creative Cloud license package

    kentw31957778
    kentw31957778Author
    Inspiring
    January 17, 2017

    I've done that. Twice.

    --

    Kent

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