Copy link to clipboard
Copied
already have a ticket open with Adobe but wanted to see in any one else was having this issue while I am waiting for Teir 2 to call me back.. note ** first level support seems really clueless to enterprise operations
Appears I made my OSX packages with the wrong serial number and they now have an expiration date of November 30th.. no big deal I Identify my serial number which has a 2020 expiration date and create a license package. Here is were I have a problem. I have applied the package, when I run the adobe expiration tool it still reports the same expiration date.. I no longer get the pop up warning in CC applications about the pending expiration, but I am not assuming that means they are good to go.
any thoughts/ideas?
thanks in advance
OK all, got it.. and kinda embarrassed it was so simple, but all of you should be equally ashamed .. jk
run the serialization from terminal as admin (the sudo prefix) , with the addition of the previously suggested removal first
example as to what I am going to do for deployment
copy the serialization folder to local of your choice to the local client, and then run
sudo /{directory}/RemoveSerialVolume
sudo /{directory}/AdobeSerialization
at which point you can confirm by the adobeExpireych
...Copy link to clipboard
Copied
Hi,
You can use the licensing tool in the Creative Cloud Packager to build a serialization file that you can use to roll out your new serial number.
You can use the same tool to remove the old serial number. If you omit this step the serial expiry tool will not pick up that you have re-serialized.
Copy link to clipboard
Copied
While I have not heard of that issue in the last 5 years, I did give it a try.. running the removal did not change the date the expiration tool was reporting... honestly the tool is pretty flakey, on my windows boxes its not even reporting a installed/expiring serial number so it wouldn't surprise me if it turned out the license is fine, and its just reporting back a bad date
Copy link to clipboard
Copied
I can confirm, like jpeters36, expirytool is not reporting the new license, even after removing volume serial first
on windows 10 1803 x64, I know the license is working, as Acrobat is not popping up asking to sign in to a named license; adobeexpirycheck reports there is 0 expiring license on the system
Copy link to clipboard
Copied
I am having the same issue
nothing in oobelib.log adobeexpirycheck still reporting the old license and I can't get the "Your license will expire Nov 30th 2018" box on launch to reappear under any circumstances; I have no idea if my install is licensed or not
Since the license reminder box seems to only pop up once per day, I can't even test on a known good machine
Any/all input on this issue is welcome, I'll report back with what I find out
Rolling these out named next year seems like it's gonna be a nightmare...
Copy link to clipboard
Copied
Agreed.. I have asked adobe reps and they have basically said there will be another webinar closer to release, and that they cant answer my questions as the planning of the named account for multi-user stations have yet to be finalized.. I even had one refer to the January roll out as more of a Beta to get feed back. Honestly if the solution is just one "generic" named account per entity that allows unlimited installs is sounds simple enough.. hoping they also consider this account should not be able to sync settings .. I can just imagine students and instructors with there own preferences screwing the setting up and it becoming an "IT" issue.
Copy link to clipboard
Copied
I already have an issue with students with home machines bringing in CC2019 files for CC2018 lab machines and I cannot help them.
Copy link to clipboard
Copied
update.. I am really frustrated with Adobe's Support.. after I tell them My availability, they have called me three days straight immediately after I get off.. then today they called and on my end they only let it ring twice, they update the ticket and I replied intermediately saying Im here please call back.. nothing
Maybe some of this more an issue with how they track tickets but this is getting stupid about to call my adobe rep and figure out what the hell I supposed to do to get the support we pay for.
Copy link to clipboard
Copied
OK all, got it.. and kinda embarrassed it was so simple, but all of you should be equally ashamed .. jk
run the serialization from terminal as admin (the sudo prefix) , with the addition of the previously suggested removal first
example as to what I am going to do for deployment
copy the serialization folder to local of your choice to the local client, and then run
sudo /{directory}/RemoveSerialVolume
sudo /{directory}/AdobeSerialization
at which point you can confirm by the adobeExpireycheck tool or by opening an adobe CC application
Thanks for the input.. I really hope Adobe Support improves but I wont hold my breath
Find more inspiration, events, and resources on the new Adobe Community
Explore Now