Skip navigation
Paul Cossey
Currently Being Moderated

CS6 Design and Web Premium asking for Adobe ID sign in

Jan 9, 2013 3:12 AM

Tags: #cs6 #deployment #creative_suite_6 #adobe_application_manager_enterprise_edition #macintosh_serialization #enterprise_deployment #aamee3.1

Hi

 

We're a Univerisity and have a site licence for CS6. I created an install package for our mac's using the Enterprise Application Manager. It's been working fine for the last term, but now all of a sudden CS6 is asking for an Adobe ID to be entered.

 

Adobe ID.png

 

Has anyone else had this issue?

 
Replies
  • Currently Being Moderated
    Jan 9, 2013 7:45 AM   in reply to Paul Cossey

    It is normal. Adobe CS6 requires an Adobe ID to register it. (My company and I came to CS6 quite late so I cannot answer the question if CS6 was ever possible without an Adobe ID, though my brief search on the web suggests that CS6 always had an Adobe ID requirement).

     

    My suggestion is for your University to create a generic Adobe ID (for example, "university_name_CS6@adobe.com") and plug that in all your Adobe CS6 installations so that your university can track your licenses with that Adobe ID.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 9, 2013 8:39 AM   in reply to Paul Cossey

    My mistake. I overlooked that this was an Adobe package.

    One other clue is the fact that the Adobe ID is giving you 32,000+ days before it will stop working. Quite lenient, don't you think?

     

    Are you using AAMEE 3.1 (as opposed to 3.0)?

    Is the Adobe package separate from or is it baked into the master image?

     

    So far, the only relevant URLs I have located are:

    https://groups.google.com/forum/?fromgroups=#!topic/macenterprise/u4Js kwVrLrk

    http://blogs.adobe.com/oobe/2012/06/imaging-cs6-attack-of-the-clones.h tml

     

    Maybe something in there will lead you down the right path.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 9, 2013 11:11 AM   in reply to SeanAlexander

    We are getting reports of Mac users being prompted for Adobe ID as well...all installs were done using AAMEE 3.1 generated packages.

     

    Did something break at the Adobe end?

     

    Don

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 9, 2013 11:32 AM   in reply to Paul Cossey

    Paul Cossey wrote:

     

    Hi

     

    We're a Univerisity and have a site licence for CS6. I created an install package for our mac's using the Enterprise Application Manager. It's been working fine for the last term, but now all of a sudden CS6 is asking for an Adobe ID to be entered.

     

    Adobe ID.png

     

    Has anyone else had this issue?

     

    Hi Paul,

     

    Does that really read "32767 days"?

     

     

    Don

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 9, 2013 3:05 PM   in reply to Paul Cossey

    Hello. We are currently investigating this issue. Clearly there is a licensing issue. Can you confirm which version of AAMEE the install package was created with? Do you still have that package?

     

    In the meantime, my guidance is to use the command line tool APTEE to un-serialize and then serialize.  Using the serialization executable from AAMEE 3.1 should also resolve the issue. I have multiple confirmations that either method should resolve the issue.

     

    We'll respond to this issue with more details once we get to the root of the issue. So sorry for the inconvenience on this!

     

    Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 12:52 AM   in reply to Paul Cossey

    Hi Paul,

     

    We are looking into this issue, but we needed some help from your end:

     

    • Are you seeing this after fresh installation.
    • Were you able to run the software and ran into this issue after a while.
    • Which product were you using when you encountered this issue.
    • Can you please mail me the logs (oobelib.log and amt3.log  from /tmp) and details on priyjain[at]adobe[dot]com, this will help us to drill down the issue.

     

    -Priyank

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 4:06 AM   in reply to Jody Rodgers

    I had this issue on a windows environment. We worked around this by creating a serialization file which ran on start up. dont know if this helps

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 6:21 AM   in reply to MHSTECHS

    MHSTECHS,

     

    Did you have this exact issue, where it displays 32767 days? I'm trying to get an answer as to whether this issue affects Windows clients too.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 6:44 AM   in reply to timothy-sutton

    Yes it had that exact amount of days.

     

    We created a normal installation package and installed it onto the machine in which we would clone. On every client PC we have a serialization file located at :

     

    "c:\Program Files\Adobe\CS6Serialization\adobeserialization.exe"

     

    This is then executed by a batch file containing this:

     

    "c:\Program Files\Adobe\CS6Serialization\adobeserialization.exe" --tool=VolumeSerialize

     

    which runs each time a pc is booted (we put a shortcut in the stat menu startup folder).

     

    We didnt like the way it was done, but it was the only work around we could find and calling the Adobe help desk didnt bare any fruit.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 6:51 AM   in reply to MHSTECHS

    Thanks MHSTECHS. Is there a specific reason why you're doing this every time the PC is booted? As far as I understand, the fix is to run the serialization executable built with AAMEE 3.1, but this should only be needed once.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 7:12 AM   in reply to timothy-sutton

    Apparently when you install cs6 on a PC with an older version of AAMEE its bound to that PC and will not clone. If you do clone it, it is without any serializaiton. They did say this feature was removed with 3.1, but it may be worth trying the serialize just to see if it helps.

     

    I built the current package we use with an older version of AAMEE (i think 2.1). Originally I was under the impression that the serialize would only need to be run once per machine but we started getting errors like the one above and some of them claiming their trial period had finished.This was the only way to get it to work. Come to think of it im still waiting for a call back from adobe on this issue

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 1:32 AM   in reply to Jody Rodgers

    Is there any time frame on when Adobe will release an official patch?

     

    We deployed CS6 Master Collection and Design Standard using AAMEE 3.0 and are also having the "Sign in Required" problem.

     

    I'd like to wait for an official patch so that we're sure that this issue won't happen again in the future.

     

    David

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 4:50 AM   in reply to dvdborn_

    Create a new serialization key using AAMEE 3.1.x, push to your users.

     

    Karl Gibson posted a GUI app solution using Platypus for deploying the key, not a very enterprise friendly solution but it gives everyone a way to deploy (albeit by double-click).

     

    http://forums.adobe.com/servlet/JiveServlet/downloadBody/2352-102-1-24 04/AAMEE%20-%20Serialization%20for%20the%20Mac%20Platform%5B1%5D.pdf

     

    A savvy admin will wrap the script and XML files that AAMEE 3.1.x produces in a PKG for silent deployment.

     

    Don

     

    #WhistlingRainDropsKeepFallingOnMyHead

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 4:13 AM   in reply to dvdborn_

    dvdborn_ wrote:

     

    Is there any time frame on when Adobe will release an official patch?

     

    We deployed CS6 Master Collection and Design Standard using AAMEE 3.0 and are also having the "Sign in Required" problem.

     

    I'd like to wait for an official patch so that we're sure that this issue won't happen again in the future.

     

    David

    The problem is with the AAMEE 3.0.x tool, a date bug tosses up a spurious Adobe ID prompt, entering credentials doesn't fix the problem...see my other post on this thread.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 4:14 AM   in reply to timothy-sutton

    timothy-sutton wrote:

     

    Thanks MHSTECHS. Is there a specific reason why you're doing this every time the PC is booted? As far as I understand, the fix is to run the serialization executable built with AAMEE 3.1, but this should only be needed once.

     

    Yep.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 6:55 AM   in reply to Don Montalvo

    My two-cents clarification is that, while it only needs to be once, if something wipes the Adobe apps (like a hard crash), then the two-step process of installing AAMEE 3.0 packages, plus the AAMEE 3.1 serialization executable, will be needed again.

     

    If a person has the time, I would recommend just redoing the package in AAMEE 3.1 so that flaw is no longer there.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2013 6:23 AM   in reply to Don Montalvo

    Thanks for the link to the PDF with the solution.

    I wasn't aware that this was made available.

     

    David

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2013 7:00 AM   in reply to Jody Rodgers

    Jody, can you answer to staze's comment about it seeming to not work when there is not a user logged in?

     

    http://managingosx.wordpress.com/2013/01/09/adobe-cs6-serialization-fu n/#comment-12573

     

    Karl's PDF is simply an example that requires user interaction while logged in. Many of us manage fleets of machines that are not kept logged in as a user and we'd actually like to address this proactively rather than whack-a-mole as complaints start pouring in.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2013 8:29 AM   in reply to timothy-sutton

    We've been seeing this problem for a week or so now with Photoshop CS6. Three or four users out of ~100 are seeing it daily (more or less).

     

    Nothing has fixed it for more than a day.

     

    We've tried:

     

    1) Uninstalling and reinstalling the product. The installer package was originally created with AAMEE 3.0.

     

    2) Using AAMEE 3.1 to create a serialization executable and "re-serializing" the product.

     

    3) Uninstalling the product and reinstalling it using a new installer package generated with AAMEE 3.1

     

    All of these get the user up and running for a short while, but the issue inevitibly returns.

     

    This is beyond frustrating for the affected users, and has consumed a fair number of man-hours here as we attempt to remedy the situation. We're currently telling people to _not_ use Photoshop CS6.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2013 8:45 AM   in reply to GregNeagle

    GregNeagle wrote:

     

    We've been seeing this problem for a week or so now with Photoshop CS6. Three or four users out of ~100 are seeing it daily (more or less).

     

    Nothing has fixed it for more than a day.

     

    We've tried:

     

    1) Uninstalling and reinstalling the product. The installer package was originally created with AAMEE 3.0.

     

    2) Using AAMEE 3.1 to create a serialization executable and "re-serializing" the product.

     

    3) Uninstalling the product and reinstalling it using a new installer package generated with AAMEE 3.1

     

    All of these get the user up and running for a short while, but the issue inevitibly returns.

     

    This is beyond frustrating for the affected users, and has consumed a fair number of man-hours here as we attempt to remedy the situation. We're currently telling people to _not_ use Photoshop CS6.

     

    Greg,

     

    Thanks for the heads up..I just got a call back from two depts, one running Design Standard and one running Production Premium...both say users are running fine at the moment.

     

    I let them know the fix might not be permanent, and if necessary we may get On Site Support to manually install the suite(s)...not exactly the enterprise approach but we may be stuck unless Jody/Karl's team(s) can come back with a fix...

     

    Don

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2013 11:34 AM   in reply to dvdborn_

    dvdborn_ wrote:

     

    Thanks for the link to the PDF with the solution.

    I wasn't aware that this was made available.

     

    David

     

    It's actually a how-to-serialize PDF from early 2012...and it's not really usable in enterprise as you have to double-click a GUI app, as opposed to wrapping the script and xml in a PKG for silent deployment.

     

    We just got word from two Production Premium, confirming Greg Neagle's findings, they're getting the prompt again.

     

    I know the Adobe elves are cranking away on a fix for this issue, I wish I could send them ether-beers...

     

    Don

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2013 12:00 PM   in reply to Paul Cossey

    We've been seeing this issue pop up in our sudent labs at Penn State. It's been effecting over 700 lab computers and an untold number of faculty and staff machines. From what I hear, AAMEE 3.1 doesn't fix the issue so we've just been re-serailizing the suite every night.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2013 12:20 PM   in reply to rzm102

    Please post to @Adobe_ITToolkit on Twitter...let Adobe know how many users are effected.

     

    https://twitter.com/Adobe_ITToolkit

     

    Jody/Karl are burning the midnight oil on this one...the more Adobe hears how our users are effected, the more leverage Jody/Karl will get to devote more resources on a fix.

     

    Don

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 17, 2013 2:31 PM   in reply to Paul Cossey

    Could we all just ask Adobe to stop.  To stop broken license activation tools and processes, and their Adobe ID requirement.  There is no excuse for legally licensed customers to have to put up with Adobe's failed activation processes.  We should not have to be asking Adobe to fix this and we should not have to be dealing with "personally" assigned or "shared" Adobe ID accounts. Is Activating, Deactivation, and Obstructing Business Efficiency part of Adobe's core products and services these days? 

     

    Adobe should NEVER block their products from working for people and organizations that actually paid to license them. They will lose more money from customers walking away, than from the theft this process is suppose to prevent.

     

    I will be working with my wife, a photographer, to find Adobe CS6 and Light Room 4 (She will go back to iMatch maybe) alternatives when she next needs to upgrade. She will be happy with any brand of quality product as long as it actually works when she needs it to; it does not have to be Adobe.  She is a photographer, not a IT specialist or Adobe Photoshop fanatic.  She has no need for Adobe's Activation, Deactiation service even though she was forced to pay for to get Photoshop, etc.

     

    Really, you are actually making customers pay for the work you put into your activation processes, then screwing over when it fails them.  The theives don't care.

     

    Good by.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2013 6:48 PM   in reply to Paul Cossey

    The following Adobe OOBE blog post addressees this issue:

    http://blogs.adobe.com/oobe/2013/01/32767-days-left-but-whos-counting. html

     

    Thanks to Paul Cossey and the others who reported this and helped work with Adobe to identify and resolve this issue for the IT community.

     

    Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 20, 2013 12:21 PM   in reply to DavidS.001

    DavidS.001 wrote:

     

    Adobe should NEVER block their products from working for people and organizations that actually paid to license them.

     

    I'm sure lost productivity amounted to many dollars for companies that are heavy Creative Suite users.

     

    With that said. I'm hoping Adobe revisits their license managment model, if for no other reason than to prevent this kind of issue from ever impacting enterprise environments again.

     

    This Adobe ID fiasco should go onto the books as Adobe's "Newtown" so we can get much needed changes - let's hope Adobe's eyes are open now, and let's hope we get a formal commitment from Adobe so we can expect PKG installers that adhere to Apple Software Delivery guidelines.

     

    Kudos to Jody and his team...and my hat is off to Adobe in the hope that they'll understand and step forward...

     

    Don

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2013 1:08 AM   in reply to Don Montalvo

    I'm not seeing any mention that the core of the issue was related to AAMEE 3.0 created packages, but rather to the Photoshop CS6 13.0.2 and 13.0.3 updates.

     

    Does this mean that we can continue to savely use our AAMEE 3.0 created packages if we apply the official fix?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2013 7:39 AM   in reply to dvdborn_

    The issue is not born out of the fact that the package was created with AAMEE 3.0 rather that there was a problem with the 13.0.2 & 13.0.3 patches correct. However that said we would always advise using the latest version of AAMEE to create packages and also AAMEE 3.1 can be used to create an update package which would contain the 13.0.4 patch that we suggest applying to affected machines.

     

     

    Cheers

    Karl Gibson | Product Manager | Enerprise IT Tools

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2013 3:28 AM   in reply to K Gibson

    Thanks Karl forgotten about making an updater package in AAMEE

     

    RUM doesnt like the update even after copyng it manually to my AUSST server and sorting permissions out.

     

    It shows up when i manually run the updater from the mac tool bar at the top.

     

    Is there any way the run the Adobe Application Manager in Updater mode via terminal?

     

    I want to be able to get aroung the problem by offereing it as a point and click solution for the existing users by using JAMFs Self Service

     

    (AdobePhotoshopCS6Support-13.0/13.0.4)

    01/22/13 11:09:32:637 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  |  |

    01/22/13 11:09:32:637 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | *** Downloading (AdobePhotoshopCS6Support-13.0/13.0.4) ...

    01/22/13 11:09:46:842 | [ERROR] |  | AAMEE | Utilities | RemoteUpdateManager |  | | UpdaterCore failed for DownloadUpdates errorCode(207) curRefId(AdobePhotoshopCS6Support-13.0/13.0.4) errorCodeString(U43M1D207)

    01/22/13 11:09:46:842 | [ERROR] |  | AAMEE | Utilities | RemoteUpdateManager |  |  | *** Failed to download (AdobePhotoshopCS6Support-13.0/13.0.4) ...

    01/22/13 11:09:46:842 | [ERROR] |  | AAMEE | Utilities | RemoteUpdateManager |  |  | Some Updates failed to download ...

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | **************************************************

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  |  | Starting UpdaterCore InstallUpdates...

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  |  | No new Updates to be installed ...

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | **************************************************

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  |  | Following Updates failed to Download :

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  |  |           (AdobePhotoshopCS6Support-13.0/13.0.4)

    01/22/13 11:09:46:842 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | **************************************************

    01/22/13 11:09:46:915 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | ##################################################

    01/22/13 11:09:46:915 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | Ending the RemoteUpdateManager Return Code (2)

    01/22/13 11:09:46:916 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | ##################################################

    01/22/13 11:09:46:916 | [INFO] |  | AAMEE | Utilities | RemoteUpdateManager |  | | #################################################

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 21, 2013 2:52 AM   in reply to kimpton

    That is part of the Adobe update changes, and as you mentioned during the first time you used it is not included, and now the Adobe release new updates, so it all covers and requires those previously installed and newly installed Adobe CS6 to add their Adobe ID, this is normal and just part of security measures. In fact we have the same issue and even asked my friend that is working at web design gold coast, he told me same thing.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2013 12:54 PM   in reply to K Gibson

    Hi Karl,


    I am in a similar situation as OP, except I am fully Patched to 13.0.4 and still experiencing the issue.  Any updates on this?  I have also posted on http://blogs.adobe.com/oobe/2013/01/32767-days-left-but-whos-counting. html#comment-4849

     

    "I just packaged an unattended CS6 Master Collection trial install for iOS and am still getting prompted to sign in once I run the Serialization Utility. Both the package and the serialization were created using AAMMEE 3.1, and all components are fully updated and patched to latest versions. (For Example Photoshop 13.0.4)"

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points