C windows syswow64 macromed flash flashplayerupdateservice exe

Компания Adobe, идя навстречу администраторам и пользователям, начиная с версии 11.2 внедрила функцию автоматического обновления Adobe Flash Player. Казалось бы, это отличная новость, но чтобы заставить автообновление работать в реальных условиях необходимо приложить ряд усилий. Идея с автоматизацией обновления Flash плеера заключается в том, что компьютеры должны автоматически обновлять версию Flash Player до актуальной без необходимости предоставления пользователям расширенных прав. Кроме того, если на компьютере запущен браузер, то flash будет обновлен только после того, как браузер будет закрыт.

Как же все это работает?

Автоматическое обновление работает следующим образом:

• На компьютере должна быть установлена версия Adobe Flash не ниже 11.2.x
• При установке создается новое задание планировщика, которое запускается ежедневно, проверяющее наличие обновлений. Задание планировщика запускается с правами системы (SYSTEM). Если найдено новое обновление, оно скачивается, удаляется старая версию Flash и ставится новая.
• Если компьютер не имеет доступа к интернету, задание запускается раз в час, проверяя наличие подключения к интернету.
• Если запущена старая версия флеша (открыт браузер), то обновление запускается только после его закрытия.

Картинка с сайта: winitpro.ru

Некоторые детали

Задание планировщика:

• Называется ‘Adobe Flash Player Updater’
• Запускается от SYSTEM
• Запускает приложение C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe
• Настроено на ежедневый запуск, с последующим перезапуском каждый час до момента обнаружения соединения с интернетом

Установщик создает отдельную службу:

• Имя службы ‘AdobeFlashPlayerUpdateSvc’ (Adobe Flash Player Update Service)
• Тип запуска – ручной (Manual)
• Запускается с правами системы
• Исполняемый файл =C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

В корпоративной среде использование автоматическое обновления Flash Player вызывает ряд проблем, наиболее распространенной из которых является проблема использования прокси-сервера (по этому поводу на форумах очень много дискуссий). Проблема в том, что задание автоматического обновления с сервера Adobe запускается с правами SYSTEM, который ничего не знает о наличии прокси сервера в сети, его адресе и номере порта (подробнее о настройке системного проски в Windows здесь). И даже если с помощью утилиты proxycfg.exe измените настройки прокси-сервера, то если прокси сервер настроен на авторизацию по учетным записям, то в этом случае автоматическое обновление работать не будет.

Отключение автоматического обновления Adobe Flash Player

Автоматическое обновление Flash Player можно отключить. Для этого нам нужно создать и настроить параметр в специальном файле mms.cfg. Т.к. начиная с Adobe Flash 11 данный пакет поставляется в двух реализациях 32-битной и 64-битной, то данный файл может находится в разных каталогах:

• В 32-битной Windows: %systemroot%\System32\Macromed\Flash
• В 64-битной Windows 32битный Flash: %systemroot%\SysWOW64\Macromed\Flash
• В 64-битной Windows 64битный Flash: %systemroot%\System32\Macromed\Flash

Определяем версию Windows и Flash и переходим в соответствующий каталог. Создадим в нем файл MMS.CFG в кодировке UTF-8, содержащий одну строку: AutoUpdateDisable=1.

Тем самым мы отключим автоматическое обновление Flash Player-а, и никакие всплывающие сообщения о необходимости обновить Flash появляться не будут (не забудьте перезапустить флеш). Для проверки отключения обновления идём Пуск — Панель управления — Flash-плеер — вкладка «Дополнительно». Если вы всё сделали правильно, то строка «Никогда не проверять обновления» должна стать неактивной.

Отключить автоматическое обновление Flash можно и с помощью групповой политики, скопировав файл MMS.CFG на нужные компьютеры с помощью vbs скрипта. Для этого создадим файл, отключающий обновление флеша по указанной выше методике и разместим его в сетевом каталоге. Далее назначим выполнение следующего logon-скрипта на целевые компьютеры:

Set obFSO = CreateObject("Scripting.FileSystemObject")

strNetworkFlashPath = \\srv1\Share\Adobe Flash\mms.cfg"

strLocalFlashPath = "C:\WINDOWS\System32\Macromed\Flash\mms.cfg"

If obFSO.FolderExists ("C:\WINDOWS\System32\Macromed\Flash") Then

obFSO.CopyFile strNetworkFlashPath, strLocalFlashPath, True

End If

Set obFSO = Nothing

Данный скрипт проверяет наличие каталога C:\WINDOWS\System32\Macromed\Flash и копирует файл mms.cfg из сетевой шары.

Как вариант, отключить обновление Flash Player можно и с помощью GP Preferences, создав задание на копирование файла (Computer Configuration -> Preferences -> Windows Settings -> Files).

Описал еще один интересный аспект касательный Flash Player, заключающейся в сложности ручного удалением файлов Flash-а.

Ok, here are the steps I’m doing to reproduce it :

1. My test computer is now clean of any version of Flash Player, i’ve also deleted C:\Windows\SysWOW64\Macromed\Flash and C:\Windows\System32\Macromed\Flash folders, and registry key HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia
2. I’ve disable Kaspersky Endpoint Security 10 antivirus,
3. Manually install install_flash_player_16_active_x.msi, everything is ok (file, service, task,…)
   

   Картинка с сайта: community.adobe.com

4. I create mms.cfg file under C:\Windows\SysWOW64\Macromed\Flash with these parameters
   SilentAutoUpdateEnable=1
   AutoUpdateDisable=0
   SilentAutoUpdateServerDomain=srvsus01.hopital-saint-joseph.fr
   SilentAutoUpdateVerboseLogging=1
5. Our Background Update Server is on a IIS web server, anonymous access on,
   

   Картинка с сайта: community.adobe.com

6. I start the update task manually, and same problem .exe disappear after a while (3mn)
   

   Картинка с сайта: community.adobe.com

7. Here is the complete FlashInstall.log

=O====== M/16.0.0.305 2016-09-20+12-38-03.396 ========

0000 00000010 «C:\Users\ADMINI~1\AppData\Local\Temp\InstallAX_16_0_0_305.exe» -install -msi

0001 00001036 Software\Macromedia\FlashPlayer\SafeVersions/16.0 2

0002 00001036 Software\Macromedia\FlashPlayerActiveX/PlayerPath 2

0003 00000011 1

0004 00000020 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0005 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player ActiveX/ 2

0006 00000013

0007 00000015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe

0008 00000016 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.dll

0009 00000023 C:\WINDOWS\SysWOW64\Macromed\Flash\activex.vch

0010 00000019 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0011 00000021 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

0012 00000012

=X====== M/16.0.0.305 2016-09-20+12-38-06.516 ========

2016-9-20+12-53-54.100 [info] 1628 srvsus01.hopital-saint-joseph.fr

2016-9-20+12-53-54.100 [info] 1629 srvsus01.hopital-saint-joseph.fr

2016-9-20+12-53-54.101 [info] 1614

2016-9-20+12-53-54.101 [info] 1615

2016-9-20+12-53-54.101 [info] 1618

2016-9-20+12-53-54.102 [info] 1619 1063

2016-9-20+12-53-54.119 [info] 1628 srvsus01.hopital-saint-joseph.fr

2016-9-20+12-53-54.120 [info] 1629 srvsus01.hopital-saint-joseph.fr

2016-9-20+12-53-54.120 [info] 1614

2016-9-20+12-53-54.120 [info] 1615

2016-9-20+12-53-54.120 [info] 1618

2016-9-20+12-53-54.121 [info] 1604

2016-9-20+12-53-54.121 [info] 1608

2016-9-20+12-53-54.126 [info] 1631 /pub/flashplayer/update/current/sau/currentmajor.xml

2016-9-20+12-53-54.242 [info] 1630 /pub/flashplayer/update/current/sau/22/xml/version.xml

2016-9-20+12-53-54.243 [info] 1632

2016-9-20+12-53-54.243 [info] 1632

2016-9-20+12-53-54.244 [info] 1630 /pub/flashplayer/update/current/sau/22/xml/patch.xml

2016-9-20+12-53-54.245 [warning] 1445

2016-9-20+12-53-54.245 [info] 1632

2016-9-20+12-53-54.245 [info] 1600

2016-9-20+12-53-55.192 [info] 1602

2016-9-20+12-53-55.192 [info] 1609

2016-9-20+12-53-55.192 [info] 1612

2016-9-20+12-53-55.193 [info] 1620

=O====== M/16.0.0.305 2016-09-20+12-53-56.780 ========

0000 00000010 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe -uninstall activex -msi

0001 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player ActiveX/ 2

0002 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0003 00000018

0004 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0005 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.dll 5

0006 00000018

0007 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.dll 5

0008 00001037 Software\Microsoft\Windows\CurrentVersion\RunOnce/FlashPlayerUpdate 2

0009 00001037 Software\Macromedia\FlashPlayerActiveX/ 2

0010 00001037 Software\Macromedia\FlashPlayer/SwfInstall 2

0011 00001037 Software\Microsoft\Code Store Database\Distribution Units\{D27CDB6E-AE6D-11CF-96B8-444553540000}/ 2

0012 00001021

0013 00001036 Software\Macromedia\FlashPlayerActiveX/PlayerPath 2

0014 00001036 Software\Macromedia\FlashPlayerPlugin/PlayerPath 2

0015 00001036 Software\Macromedia\FlashPlayerPepper/PlayerPath 2

0016 00001036 Software\Macromedia\FlashPlayerActiveX/PlayerPath 2

0017 00001036 Software\Macromedia\FlashPlayerPlugin/PlayerPath 2

0018 00001036 Software\Macromedia\FlashPlayerPepper/PlayerPath 2

0019 00001037 Software\Microsoft\Windows\CurrentVersion\Control Panel\Extended Properties\System.ControlPanel.Category/C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl 2

0020 00001036 Software\Macromedia\FlashPlayerActiveX/PlayerPath 2

0021 00001036 Software\Macromedia\FlashPlayerPlugin/PlayerPath 2

0022 00001036 Software\Macromedia\FlashPlayerPepper/PlayerPath 2

0023 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.dll 5

0024 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.dll 5

0025 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0026 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0027 00000011 1

0028 00000012

=X====== M/16.0.0.305 2016-09-20+12-53-57.383 ========

=O====== M/23.0.0.162 2016-09-20+12-53-55.435 ========

0000 00000044

0001 00000045

0002 00000010 FlashPlayerInstaller.exe -install -iv 9

0003 00001036 Software\Macromedia\FlashPlayer\SafeVersions/23.0 2

0004 00000011 1

0005 00000020 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0006 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player ActiveX/ 2

0007 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0008 00001045 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0009 00001015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_305_ActiveX.exe 5

0010 00001037 SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\\FlashUtil32_16_0_0_305_ActiveX.exe/ 2

0011 00000013

0012 00000015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_23_0_0_162_ActiveX.exe

0013 00000016 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_23_0_0_162_ActiveX.dll

0014 00000023 C:\WINDOWS\SysWOW64\Macromed\Flash\activex.vch

0015 00000019 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0016 00000021 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

0017 00001031 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe:5

=X====== M/23.0.0.162 2016-09-20+12-54-01.711 ========

The genuine FlashPlayerUpdateService.exe file is a software component of Adobe Flash Player by .
FlashPlayerUpdateService.exe is an executable file that belongs to Adobe Flash Player, a freeware software program used for viewing audio and video created on the Adobe Flash platform. This process runs the update module for the Adobe Flash Player. This is not a critical Windows component and should be removed if known to cause problems.

The Adobe Flash Player was originally developed by FutureWave and released in 1996. The player currently has a very large user base with more than 90% penetration on internet connected personal computers. Adobe Flash Player comes in a plugin version for Internet browsers in order to support Internet Flash media in various formats such as XML, JSON, AMF, SWF, MP3, FLV, PNG, JPEG, and GIF.

Adobe Systems Incorporated is an American software giant that develops software products for web design, video editing, web hosting, image editing, servers, as well as formats such as Flash and PDF. The company was established in 1982 by Charles Geschke and John Warnockin and is currently headquartered in San Jose, California.

FlashPlayerUpdateService stands for Adobe Flash Player Update Service

The .exe extension on a filename indicates an executable file. Executable files may, in some cases, harm your computer. Therefore, please read below to decide for yourself whether the FlashPlayerUpdateService.exe on your computer is a Trojan that you should remove, or whether it is a file belonging to the Windows operating system or to a trusted application.

Click to Run a Free Scan for FlashPlayerUpdateService.exe related errors

FlashPlayerUpdateService.exe file information

Картинка с сайта: www.file.net

The process known as Adobe® Flash® Player Update Service (version 32.0 r0, 31.0 r0, 11.6 r602, 17.0 r0, 16.0 r0, 21.0 r0, 11.2 r202, 22.0 r0, 26.0 r0, 11.3 r300, 27.0 r0, 29.0 r0, 11.8 r800, 23.0 r0, …) or Windows Calculator belongs to software Adobe Flash Player Update Service or Rainmeter or Microsoft Windows Operating System by Adobe Systems (www.adobe.com) or Adobe (www.adobe.com) or Microsoft (www.microsoft.com).

Description: FlashPlayerUpdateService.exe is not essential for the Windows OS and causes relatively few problems. FlashPlayerUpdateService.exe is located in a subfolder of C:\Windows—common is C:\Windows\SysWOW64\Macromed\Flash\.
Known file sizes on Windows 10/11/7 are 335,416 bytes (36% of all occurrences), 335,872 bytes and 15 more variants.  

The FlashPlayerUpdateService.exe file is not a Windows core file. The file is digitally signed. The app is launched periodically by the Windows Task Scheduler.
Therefore the technical security rating is 16% dangerous; however you should also read the user reviews.

Recommended: Identify FlashPlayerUpdateService.exe related errors

If FlashPlayerUpdateService.exe is located in a subfolder of C:\Windows\System32, the security rating is 22% dangerous. The file size is 335,416 bytes (22% of all occurrences), 163,328 bytes and 14 more variants.
The FlashPlayerUpdateService.exe file is not a Windows core file. The file is digitally signed. The program is not visible.

If FlashPlayerUpdateService.exe is located in a subfolder of the user’s profile folder, the security rating is 24% dangerous. The file size is 169,472 bytes (33% of all occurrences), 258,048 bytes or 776,192 bytes.
The program has a visible window. The software starts upon Windows startup (see Registry key: TaskScheduler, Run, MACHINE\Run).
FlashPlayerUpdateService.exe is not a Windows core file. There is no file information.

Important: Some malware camouflages itself as FlashPlayerUpdateService.exe, particularly when located in the C:\Windows or C:\Windows\System32 folder, for example WS.Reputation.1 (detected by Symantec), and Trojan.Generic.13138297 (detected by BitDefender). Therefore, you should check the FlashPlayerUpdateService.exe process on your PC to see if it is a threat. We recommend Security Task Manager for verifying your computer’s security. This was one of the Top Download Picks of The Washington Post and PC World.

Best practices for resolving FlashPlayerUpdateService issues

A clean and tidy computer is the key requirement for avoiding problems with FlashPlayerUpdateService. This means running a scan for malware, cleaning your hard drive using 1cleanmgr and 2sfc /scannow, 3uninstalling programs that you no longer need, checking for Autostart programs (using 4msconfig) and enabling Windows’ 5Automatic Update. Always remember to perform periodic backups, or at least to set restore points.

Should you experience an actual problem, try to recall the last thing you did, or the last thing you installed before the problem appeared for the first time. Use the 6resmon command to identify the processes that are causing your problem. Even for serious problems, rather than reinstalling Windows, you are better off repairing of your installation or, for Windows 8 and later versions, executing the 7DISM.exe /Online /Cleanup-image /Restorehealth command. This allows you to repair the operating system without losing data.

To help you analyze the FlashPlayerUpdateService.exe process on your computer, the following programs have proven to be helpful: ASecurity Task Manager displays all running Windows tasks, including embedded hidden processes, such as keyboard and browser monitoring or Autostart entries. A unique security risk rating indicates the likelihood of the process being potential spyware, malware or a Trojan. BMalwarebytes Anti-Malware detects and removes sleeping spyware, adware, Trojans, keyloggers, malware and trackers from your hard drive.

Other processes

osd.exe ctsvccda.exe caudiofilteragent64.exe FlashPlayerUpdateService.exe pwdrvio.sys beservice.exe rtkaudioservice64.exe oxhelper.exe isahelperservice.exe coupons.dll wtgservice.exe [all]

Adobe have come to the mercy of IT administrators by introducing an auto updating feature for Flash Player. This is excellent news but now we need to get it to work in the real world

With the below configuration the end device should be able to automatically update without granting users extra permissions. The service can automatically update the files without user intervention and even if a browser window is open, it will update as soon as the browser is closed.

How does it work?

A simple breakdown of how the new auto-updating system works is:

1. Install Adobe Flash 11.2.x on a PC – this version contains the logic for the auto-updater.
2. The install process creates a Scheduled Task that executes daily and checks for an update. This task is run as the SYSTEM account.
3. If a new update is found, it downloads it, uninstalls the old version and installs the new version.
   If the PC is not online at the time of running the scheduled task, it will run every hour for 24 hours until it gets internet access.
4. If a browser is open at the time – the old version of Flash is used, and when the browser is reopened it will load the new browser plug-in.

More detailed information:

• The Scheduled Task has the following properties:
• Task name is ‘Adobe Flash Player Updater’
• Run as SYSTEM
• Trigger = C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe
• Schedule to run Daily – After triggered, will repeat every hour for 1 day until internet connectivity available

• The installation creates a service with the following properties:
• Service Name is ‘AdobeFlashPlayerUpdateSvc’ (Adobe Flash Player Update Service)
• Manual startup
• Runs as Local System Account
• Path to execute = C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe
• A good resource to read the Overview of how the Background Updater works:
  Introducing Adobe Flash Player Background Updater for Windows
  http://www.adobe.com/devnet/flashplayer/articles/background-updater-windows.html

Problems in the enterprise

There are several problems at hand when it comes to the enterprise, some with a workaround but others that will hopefully be addressed with future updates.

Proxy server support

This has been asked for quite a bit on the forums. The underlying problem is that the SYSTEM account that is trying to access the internet does not know of proxy servers in your environment, in particular it does not know the proxy address or port number.
This configuration can be hard coded on a client using proxycfg.exe. The problem with this method is that if its a laptop that may connect to wifi outside the business, some internet access (where the system account is used) may not work.

My method of deploying Flash in the enterprise

There are several sections that we need to individually configure to get it all to work, and at the end they should all work together to give us the end result of auto-updating clients in the enterprise.

Deploying the client

Deploying the client in the enterprise is relatively straight forward and I have covered it in the a previous article:|

Adobe Flash 11 Deployment via GPO
https://ivan.dretvic.com/2011/10/adobe-flash-11-deployment-via-gpo/

A couple of points while deploying the client to help you:

• Adobe Flash Player client needs to be version 11.2.202.228 or higher to support the auto-updating feature
• The GPO deployment can be an update to previous Flash versions

Pushing out mms.cfg configuration file to clients

Adobe provide specifications for an configuration file that configures Adobe Flash player. The user settings are set either within the browser or through the Windows Control Panel. The computer settings are set through the mms.cfg file. This configuration file overrides any user settings that are set in thefile and applies to the computer.

The details  about the mms.cfg file are below:

Screenshot of file on a Windows 7 32-Bit machine:

As you can see its a simple 3 liner cfg file that needs to be created\copied in the corresponding folder to force your desired configuration.

What I do is use Group Policy Preferences to copy a file from the network (I have saved to the GPO source location eg. \\Domain.local\DFS\Install\AdobeFlash\mms.cfg) to the client destination.

Note: I have attached a sample mms.cfg file which is included in the package at the bottom of this article.

Here is an article that specifically details how to deploy the files to your client computers:

How to deploy mms.cfg config file to your Adobe Flash Player clients?
https://ivan.dretvic.com/2012/05/how-to-deploy-mms-cfg-config-file-to-your-adobe-flash-player-clients/

Hosting Flash Update files internally (web server)

This part is required for any organisation who want to overcome the following scenarios:

• Internal network gains internet access via Proxy Server – Computer system accounts are not aware of proxy server configurations
• Bandwidth concerns – do not want hundreds/thousands of users from downloading the latest version of Flash on the same day (even if it is staggered)

What we will have at the end of this is an internal web server which hosts the files for your clients to access, a DNS entry with a common name to access the files, and a scheduled task which runs a script to download the latest files every day (directly from the Adobe download site).

At the bottom of this article is the source files for the script, and the exe tools required for it to work. You will need these tools before you begin this section:

1. Download the source files from the bottom of this article called GetFlashUpdateVerXXX.zip and extract the contents to a working directory. I extracted mine to C:\FlashUpdate but any similar location is suitable (avoid using the IIS published folder directory)

Build your web server (IIS in my case)

Don’t think this is doom and gloom – its pretty straight forward and does not require a lot of configuration. I have not concentrated on security as is hosted internally and not published to the internet.

Find a suitable server that you already have in your environment that does not use any web service (in

particular does not use port 80 or 443 for any communication). Note: Its not hard to migrate this to another server if you follow my steps again, install IIS using these steps:

1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. In Add or Remove Programs, click Add/Remove Windows Components.
3. In the Windows Components Wizard, under Components, select Application Server.
4. Click Next.
5. After the wizard completes the installation, click Finish

Install SSL Certificate

An SSL certificate is required for this to work. I have an SSL certificate that I installed, and an internal CA would work well for this exercise. If you do not have an internal CA, or a means of attaining a valid certificate I recommend generating your own self-signed certificate. To do this use the following:

1. Navigate to your working directory: c:\FlashUpdate from within command prompt
2. Enter the following command to generate and register your new certificate:
   [code]selfssl.exe /N:CN=flashupdate.contoso.com /K:1024 /V:900 /S:1 /P:443 /T[/code]

   To break this down:

   • /T Adds the self-signed certificate to “Trusted Certificates” list. The local browser will trust the self-signed certificate if this flag is specified.
   • /N:cn Specifies the common name of the certificate. The computer name is used if not  specified.
   • /K:key size Specifies the key length. Default is 1024.
   • /V:validity days Specifies the validity of the certificate. Default is 7 days.
   • /S:site id       Specifies the id of the site. Default is 1 (Default Site).
   • /P:port          Specifies the SSL port. Default is 443.
3. Navigate to https://flashupdate.contoso.com and validate that a certificate is installed (even if not trusted by that machine

Configure DNS

1. Configure DNS to point to a friendly name using a new CNAME record. I personally used flashupdate.contoso.com which directed to my actual server SYDAPP01.contoso.com.
2. Test the new URL internally. It should work straight away with a basic IIS config and will display a basic page like below:

Configuring the automatic downloads script

1. Go to the source files you downloaded earlier.
2. Edit the batch file (getflashupdate.bat) with appropriate details under the Configuration section only. I have provided adequate instructions within the script.
   Here is the script if you want to view it online:
   [code lang=”bat” collapse=”true”]@ECHO OFF
   REM ================== About Script ======================
   REM        Author:    Ivan Dretvic
   REM        Email:    [email protected]
   REM        URL:    http://ivan.dretvich.com
   REM        Date:    09/05/2012
   REM        Ver:    1.0
   REM
   REM        REFERENCES:
   REM        -wget.exe used for fetching files from internet
   REM            http://www.gnu.org/software/wget/manual/wget.html
   REM        -Bulk of this script was written by Tyrone Wyatt of www.cloudportal.org
   REM             Thank you for saving me from writing the script.
   REM         -All Adobe information in this script was attained from the Flash Player Administrators Guide
   REM             http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/flash_player_11_2_admin_guide.pdf
   REM ======================================================

   REM ================= Script Config ======================
   REM TITLE
   REM         Used to identify script name within the rest of script. Useful if using multiple instances of script for different sites in organisation.
   REM        Default setting is:
   REM            set TITLE=flash-update
   set TITLE=flash-update

   REM LOG
   REM        The LOG option is the name and location of the log file.
   REM            This field must be populated otherwise the script will fail. Removal of  «>> %LOG% 2>&1» in the rest of the script would be necessary
   REM            to not produce log file. (not recommended)
   REM        Default setting is:
   REM            set LOG=./%TITLE%.log
   set LOG=./%TITLE%.log

   REM SOURCE
   REM         The SOURCE option is the mirror on which you would like to download the flash files from.
   REM        Default setting is:
   REM            set SOURCE=http://fpdownload2.macromedia.com
   set SOURCE=http://fpdownload2.macromedia.com

   REM DESTINATION
   REM        The DESTINATION option is where you would like your downloaded files to go. If you will be testing package before updating the
   REM        masses, you must change the destination to not be in the default published IIS folder. If you did not configure IIS, and would like
   REM        the update to propogate to all users please leave the default settings.
   REM        Default setting is:
   REM            set DESTINATION=C:\inetpub\wwwroot
   set DESTINATION=C:\inetpub\wwwroot

   REM VERSION
   REM        The VERSION option is the current major version of Flash Player. (Eg. for Flash Player 11.2, the major version is 11).
   REM        When it comes to the major version changing, please investigate any changes that Adobe have made to their software and update system.
   REM        Default setting is:
   REM            set VERSION=11
   set VERSION=11

   REM HTTP_PROXY
   REM        The Proxy settings for wget to use. This is an optional parameter that can be ommited if you run as a configured users context.
   REM        It is recommended to configure this field if you do use a proxy server.
   REM            Note: the required string here is: http:\\<<PROXYSERVERNAME>>:<<PORTNUMBER>>
   REM        Default setting is:
   REM            set HTTP_PROXY=http://proxy.contoso.com:8080
   set HTTP_PROXY=http://proxy.contoso.com:8080

   REM ================= Script Core ========================
   REM    This is the guts of the script. Please dont modify this section of the script unless its to improve it, in which case please let me know.
   echo =O====== %date% %time% ======== >> %LOG% 2>&1
   if exist %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml (
   echo Folders Exist. Skipping destination folder structure creation. >> %LOG% 2>&1
   ) else (
   echo Creating destination folder structure. >> %LOG% 2>&1
   mkdir %DESTINATION%\pub >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer\update >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer\update\current >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer\update\current\sau >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION% >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml >> %LOG% 2>&1
   mkdir %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install >> %LOG% 2>&1
   )

   echo Downloading files… >> %LOG% 2>&1
   wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/xml/version.xml -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\xml\version.xml >> %LOG% 2>&1
   wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_ax_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_ax_sgn.z >> %LOG% 2>&1
   wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_pl_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_pl_sgn.z >> %LOG% 2>&1
   wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_64_ax_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_64_ax_sgn.z >> %LOG% 2>&1
   wget.exe -nv %SOURCE%/pub/flashplayer/update/current/sau/%VERSION%/install/install_all_win_64_pl_sgn.z -O %DESTINATION%\pub\flashplayer\update\current\sau\%VERSION%\install\install_all_win_64_pl_sgn.z >> %LOG% 2>&1
   echo Script complete! See log file for more infomation %LOG%
   echo =X====== %date% %time% ======== >> %LOG% 2>&1
   echo. >> %LOG% 2>&1

   REM ================= Script End =========================
   [/code]

3. Once your document is saved you are ready to schedule a task to run Daily. Ill assume the script is located at C:\FlashUpdate\GetFlashUpdate.bat and you are saving it directly to your IIS folder.
4. Create the scheduled task to execute “C:\FlashUpdate\GetFlashUpdate.bat”, with user credentials (that has access to Proxy server), to run once a day. All other settings can be left as default.
5. Right click on your new scheduled task and run it.
6. Open IIS Manager, expand the server name, then expand the folder Web Sites. Right click on Default Web Sites and click Open.
7. Here you should see 2 files (iisstar.htm and pageerror.gif) and a folder called PUB. Navigate through the folder and make sure you see all 5 files have been downloaded by the script.Further information on file names can be found under Background updates from an internal server, Page 10 http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/flash_player_11_2_admin_guide.pdf

Conclusion

You are done. If your clients are running a version of Flash greater than 11.2.202.228 the auto-updating should update your clients as expected. If you want to force the updates on a client to test, you can:

• run the scheduled task (as administrator because the task is a system task)
• execute C:\WINDOWS\system32\Macromed\Flash\FlashPlayerUpdateService.exe

Please let me know if i have been vague or inconsistent/inaccurate in any way so I can update it.

References

• Source files used to configure this solution
  GetFlashUpdateVer1.0
• How to Install IIS on Windows Server 2003
  http://technet.microsoft.com/en-us/library/aa998483%28v=exchg.65%29.aspx
• Adobe Flash Player Administration Guide for Flash Player 11.2
  http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html
• Introducing Adobe Flash Player Background Updater for Windows
  http://www.adobe.com/devnet/flashplayer/articles/background-updater-windows.html