-
1. Re: Using mms.cfg In The Enterprise
RyanSchauer Sep 5, 2013 12:11 PM (in response to Jason-AU)My solution was as follows:
1. In SCCM 2012, I created an application for flash player based on the MSI deployment.
2. Created a second deployment type that executes a .CMD file with the following batch code in it (set dependency pointing to the Flash MSI completing successfully as well):
- REM In case folders don't exist, create them
MD %WINDIR%\System32\Macromed\Flash
MD %WINDIR%\SysWow64\Macromed\Flash
- REM Delete existing completion files
Del %WINDIR%\System32\Macromed\Flash\Complete.flag
Del %WINDIR%\SysWow64\Macromed\Flash\Complete.flag - REM Copy System32 CFG file and then copy the complete flag
Copy /y %~dp0mms.cfg %WINDIR%\System32\Macromed\Flash
Copy /y %~dp0Complete.flag %WINDIR%\System32\Macromed\Flash - REM Copy SysWow64 CFG file and then copy the complete flag
Copy /y %~dp0mms.cfg %WINDIR%\SysWow64\Macromed\Flash
Copy /y %~dp0Complete.flag %WINDIR%\SysWow64\Macromed\Flash
Note: Completion.flag is merely a text file that gives me an easy way to know if the script finished running or not. I check for it's existence in both locations to consider the process complete.
This has worked for me. The only hangup I had was that I set the MSI verification on the filename of the OCX that the installer puts in the System32 and SysWow64 folders not realizing that the filename is backwards from what I expected. System32 has the "Flash64..." file and SysWow64 has the "Flash32..." file. Goofy, I know.
Hope this helps.
- REM In case folders don't exist, create them
