Skip to main content
T
TAB_RN
Inspiring
April 12, 2016
Question

How do I disable the Adobe ID login popup

  • April 12, 2016
  • 1 reply
  • 58169 views

Hi,

Im installing Acrobat Standard DC in our Citrix environment. I managed to create a prov.xml file and thats placed on the imaged server.

Everythign seems to work fine, except for one thing. We dont want our employees connecting to Cloud solutions and Sharepoint I disabled all these setting with Registry settings.

These options are no longer available on the start screen, and in any of the menus.

After about 30 second of having Acrobat open Im getting a "sign in with your Adobe ID" popup, which is driving me nuts.


Is there any possibillity to disable that splash screen?


Ive found a solution here:

Disable Adobe Sign-in - Acrobat DC - Super User

but since we dont use packaging for installing, this isnt a viable solution for me.

    This topic has been closed for replies.

    1 reply

    EnterpriseHelp
    EnterpriseHelp
    Inspiring
    April 12, 2016

    Did you activate and create the image as described here?: Common Deployment Options and Methods — Enterprise Administration Guide

    Ben

    T
    TAB_RNAuthor
    Inspiring
    April 13, 2016

    Yep, Acrobat has been activated and I've serialized the license via the prov.xml file.

    Its just the popup thats bugging me now.

    Ive also disabled all the other ways to sign-in to Adobe via registry settings described here:

    Online features — Acrobat Customization Wizard DC for Windows

    But still the popup remains.

    Its this popup, but it says "Acrobat Reader" in the title bar instead of "Creative Cloud":

    qdo9S.png

    T
    TAB_RNAuthor
    Inspiring
    May 24, 2016

    Hi  Technisch Applicatiebeheer,

    I hope your issue is resolved. If you still require help let us know.

    Regards,

    Tariq Dar.


    Hi,

    Well, it turned out the problem wasnt Acrobat itself, it was the PDApp that was installed to serialize the license. That kept generating the popup.

    So I did a full reinstall and decided to ignore the serialization, since testing proved that wasnt necessary in our environment.

    So I guess this can be marked as "fixed".

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