Raymond,
Wow, you sure picked a winner as a newbie . I'll be honest, in working with our packaging experts for over 15 years of Acrobat packaging and deployments (4.5 was my first), I can honestly say that Acrobat, by far, is one of the most difficult pieces of software to package and deploy. Adobe has done wonderful work since 4.5 in making life much, much easier. But there are still a lot of 'gotcha's' that you have to be aware of.
Without deep analysis on your specific installation I can't make specific (fix this here) type suggestions. However, here are a few things to keep in mind that might be helpful.
-- Check your Document Cloud settings in 'Da Customizer (Acrobat Customization Wizard). You pretty much want to disable all the DC settings other than being able to participate in meetings and on-line events.
-- That Acrobat stores almost ALL settings under the HKCU registry hive. Meaning that the installation works best when it takes place under the user's ID.
-- Careful with the Adobe PDF printer settings. Bits are stored under:
- HKEY_CURRENT_USER\Printers\DevModePerUser
- HKEY_CURRENT_USER\Printers\DevModes2,
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Adobe PDF Port Monitor
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\Adobe PDF
if they are not kept in sync the printer can go haywire on you. You'll know that because it won't work and just about nothing will get it to work.
-- What we tend to do in situations where the installation is made under a global ID, but requires individual ID authentication is to create a .REG file that is applied after the user log's in. To build this, perform the install. Take a Reg snapshot, get Acrobat setup how you want it, take another Reg snapshot, create a delta and clean it up.
If none of the above work, check with your Adobe re-seller about obtaining an a license key that doesn't require 'phone home'. These are generally only available under CLP agreements. Keep in mind that this will flag your account to have a high likelihood of being audited at every contract renewal.
Lastly, keep in mind that everyone on the CITRIX environment that has access to Acrobat needs a license. Not just the folks that are slated to use it.
Final thoughts - don't be afraid to dig around in the registry, experiment, etc. And above all - don't hesitate to dig around on the Adobe's Acrobat Enterprise Deployment pages. A wealth of knowledge to be had
I hope this helps.
Doug