Using Settings.sol to set Adobe Flash Settings
Posted on March 21st, 2010
When using Adobe Flash to access old content that was coded on previous versions, a message can appear stating that Flash has stopped a potentially unsafe operation. This message could also appear for content running from network shares. The message will be similar to:
If you select the ’settings’ options the web based Adobe Global Setting panel appears. This actually connects via the internet to a macromedia.com site.
It seems strange that you must connect to an external web site to change settings for a locally installed version of flash – hopefully Adobe will remove this nonsense in the future and release an adm template or something instead. Anyway, each client can set options within this Global Security Settings screen. In this can either the “always allow” option can be selected or a location can be added to the trust list.
Select to Edit Locations | Add location and paste in the value prompted by the gui as this is what was just denied. Or add any other location you want to trust:
Close this web site, relaunch the content and it should now work as expected and display the content without the pop-up warning message.
However, in a situation where multiple clients need to run this content it is inconvenient to ask the users to set this themselves or manually set it on thousands of desktops.
Instead the settings.sol file can be used.
Any of the settings chosen from the web page GUI will be set in the following file (for a WinXP profile)
%userprofile%\Application Data\Macromedia\Flash Player\macromedia.com\support\flashplayer\sys\settings.sol
So to resolve for everyone do the following:
- Logon as one user
- Set the relevant options in the web based GUI
- Copy the settings.sol file to a central location
- Set a logon scripts to copy this file into each users profile at logon
job done.
Tags: adobe, adobe flash player, always allow, flash, global security settings, potentially unsafe operation, settings manager, settings.sol, trust
Filed under Applications, Scripts/Reg | No Comments »
Profiling Adobe Acrobat Reader 9.2
Posted on October 21st, 2009
In order to profile Adobe Acrobat Reader 9.2 for Citrix streaming I did the following.
Stage 1 – Download source files
Download and install the Adobe Customization wizard 9
Download the distribution version of Acrobat reader 9.2. You need to register on the adobe site to get access to this download.
Extract the msi from the .exe that was downloaded by running the following
AdbeRdr920_en_US.exe” -nos_ne -nos_o”Extracted”
This will place the extracted files in the “Extracted” folder
Stage 2 – Create a customised installation
Open the customization wizard
Open the Reader msi (extracted above)
Select the options desired. I chose the following:
Supress display of EULA
Remove acrobat.com features
disbale all updates
disable help | Digital editions
Disable product improvement programs
Disable help | Purchase acrobat
Save the customisation MST file
Stage 3 – install
Create a .cmd file that contains the install string including the MST file. For example:
msiexec /i “acroread.msi” TRANSFORMS=”adobe_9_2_transform.MST”
Launch this .cmd file from the Citrix Streaming Profiler
Install as normal
Stage 4 – Add a pre-launch script
Even though the option to disable updates was selected during the customisation wizard, it is not disabled when streaming the app. The same applies to the customer improvment program.
The best way to remove these is to run a pre-launch script to set the reg keys to remove these options.
Create a .vbs script with the following contents
Set objWshShell = CreateObject(“WScript.Shell”)
objWshShell.RegWrite “HKLM\Software\Adobe\Adobe ARM\1.0\ARM\iCheck”, 0 ,”REG_DWORD”
objWshShell.RegWrite “HKCU\Software\Adobe\CommonFiles\Usage\Reader 9\OptIn”, 0 ,”REG_DWORD”Call this script as a pre-launch script within the streaming profiler.
..
Tags: 9.2, adobe, customer improvment program, profiler, reader, script, stream, streaming, updates
Filed under Citrix XenApp, Scripts/Reg | No Comments »