Adobe Premier Elements 4.0 - Suppressing registration
Is there any way to suppress the registration window that pops up when the app is invoked in a machine after a fresh installation?
If the 'Do not register' option is selected, the pop up will not come again as the info gets stored in the path C:\Program Files\Common Files\Adobe\Adobe PCD\cache\cache.db. But if we supply this file along with the msi, it will create problems when other adobe apps are installed to the same machine.
So i need another workaround. Can anyone please tell me how i can suppress the pop up... thanks in advance
If the 'Do not register' option is selected, the pop up will not come again as the info gets stored in the path C:\Program Files\Common Files\Adobe\Adobe PCD\cache\cache.db. But if we supply this file along with the msi, it will create problems when other adobe apps are installed to the same machine.
So i need another workaround. Can anyone please tell me how i can suppress the pop up... thanks in advance
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
WayneB
16 years ago
Unfortunately couldn't open the db file. Did a lot of searching though to do this.
The way the flexnet licensing works in this case is that the db files are appended to, for each Adobe app installed. (I hope they haven't changed this in this latest version which we no doubt will get to soon).
When the app is launched it checks the application.xml file in the Program Files\Adobe\adobeapp\AMT for valid registration, then checks the caps.db in the Program Files\Common Files\Adobe dir for all the Adobe registered apps installed. Then the flexnet service updates the pcd.db and the cache.db files. So the application.xml file is bundled in with the Adobe app. Our cache.db, pcd.db, caps.db and adobe_00080000_tsf.data files are bundled in with the Custom_Licensing package which we updated as each Adobe app comes by us when we have to contend with this method of licensing.
We have a vm with all our licensed Adobe apps (2 suites plus a couple of other Adobe products) and once we got the licensing sorted we just update the image.
The addons for the suites is usually our most time consuming part; as this is bloatware to the max.
You can see the licensing sequence in the alm.log in the %temp% dir when logged in as admin. It will succeed when it finds a valid registered product, fun to watch [8|].
So make sure your clean machine has all the Adobe apps registered and grab those files.
Regards
Wayne
The way the flexnet licensing works in this case is that the db files are appended to, for each Adobe app installed. (I hope they haven't changed this in this latest version which we no doubt will get to soon).
When the app is launched it checks the application.xml file in the Program Files\Adobe\adobeapp\AMT for valid registration, then checks the caps.db in the Program Files\Common Files\Adobe dir for all the Adobe registered apps installed. Then the flexnet service updates the pcd.db and the cache.db files. So the application.xml file is bundled in with the Adobe app. Our cache.db, pcd.db, caps.db and adobe_00080000_tsf.data files are bundled in with the Custom_Licensing package which we updated as each Adobe app comes by us when we have to contend with this method of licensing.
We have a vm with all our licensed Adobe apps (2 suites plus a couple of other Adobe products) and once we got the licensing sorted we just update the image.
The addons for the suites is usually our most time consuming part; as this is bloatware to the max.
You can see the licensing sequence in the alm.log in the %temp% dir when logged in as admin. It will succeed when it finds a valid registered product, fun to watch [8|].
So make sure your clean machine has all the Adobe apps registered and grab those files.
Regards
Wayne
Posted by:
WayneB
16 years ago
We have a separate licensing msi which we install separately to accompany our Adobe app.
In this msi we keep the cache.db, pcd.db, caps.db and adobe_00080000_tsf.data files. Each time we roll out a new Adobe suite or app we grab the updated versions of these files from our vanilla registered install (and many Adpbe free gifts - not) and replace the files in our Adobe Licensing msi.
The application.xml file is included into our Adobe app (must be the registered xml file from the vanilla install).
We have almost all the Adobe apps that use this method of registration covered.
Hope this helps
Regards Wayne
In this msi we keep the cache.db, pcd.db, caps.db and adobe_00080000_tsf.data files. Each time we roll out a new Adobe suite or app we grab the updated versions of these files from our vanilla registered install (and many Adpbe free gifts - not) and replace the files in our Adobe Licensing msi.
The application.xml file is included into our Adobe app (must be the registered xml file from the vanilla install).
We have almost all the Adobe apps that use this method of registration covered.
Hope this helps
Regards Wayne
Posted by:
vabraham
16 years ago
Thanks Wayne... but will the updated .db file contain all the information required for all the apps (old and new). Won't there be a clash when a number of apps are installed in the same machine. I had the issue with Photoshop Elements 6.0 and Premier Elements 4.0.
Also, is there any way we can edit the db file....?
Also, is there any way we can edit the db file....?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.