Acrobat Standard XI, serializing a for inclusion of license in layer within unidesk

Question

We are a volume license holder for Adobe Acrobat. We are currently using a virtual desktop environment through unidesk, pushing virtual desktop views to thin clients.
We have created a script as a .bat file which uses the adobe_prtk command line tool to serialize, accept EULA, suppress registration, and suppress update checks. Please see below for the commands we run in the .bat:
c:\Adobe_Install_Tools\adobe_prtk.exe --tool=Serialize --leid=V6{}AcrobatStd-AS2-Win-GM --serial=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
c:\Adobe_Install_Tools\adobe_prtk.exe --tool=EULA --leid=V6{}AcrobatStd-AS2-Win-GM --eulasuppress --eulaaccept --locale=en_US c:\Adobe_Install_Tools\adobe_prtk.exe --tool=Register --leid=V6{}AcrobatStd-AS2-Win-GM --regsuppress=ss
c:\Adobe_Install_Tools\adobe_prtk.exe --tool=UpdateSuppress --leid=V6{}AcrobatStd-AS2-Win-GM
(I have ommitted our serial number for the purposes of this post)
This .bat file is run whenever a new desktop is created and given the acrobat program. When the new desktop is built and run for the first time, the .bat file runs and each command returns a "return code 0" for all four, which should indicate each was successful.
When an end user opens acrobat for the first time, the serial number entry window always appears. If the user clicks "quit", the window closes. Subsequently, the user is not prompted for the serial number again.
We would like to find a way to prevent the "enter serial number" window from appearing when the application is run for the first time so as to avoid cunfusion and dissatisfaction within our user pool.

Answer 1

We ultimately abandoned the command line adobe_prtk.exe via a .bat file method and switched to the Customization Wizard to modify the installer. We ran our acrobat install .exe which unpacked files into a directory. From there we could use the msi in the directory within the wizard to change the optons we wanted. We did an install on the setup machine in unidesk, opened the software on the install machine, then used this for our layer image...
When I deployed the new adobe unidesk layer created on to a thin client machine, we were able to get into the software with no updates/prompts/registration/etc.
I will note, this was BETTER than the command line tool. When we used the command line to suppress updates, the option to "check for updates" still appeared in the program as an option the end user was able to select. The application would not look for updates on its own, but the user could. After using the wizard to make the changes, the "check for updates" option is simply removed from the menu all together.
So if anyone else sees this thread and is attempting to do the same thing, skip the command line tool!