{"id":376,"date":"2013-07-27T15:38:38","date_gmt":"2013-07-27T20:38:38","guid":{"rendered":"http:\/\/www.bluemunkey.com\/?p=376"},"modified":"2018-12-30T07:46:47","modified_gmt":"2018-12-30T13:46:47","slug":"installing-adobe-flash-player-with-microsoft-sccm-2012","status":"publish","type":"post","link":"https:\/\/www.bluemunkey.com\/?p=376","title":{"rendered":"Installing Adobe Flash Player through Microsoft SCCM 2012"},"content":{"rendered":"

\"FlashAbout three weeks ago, I finally got around to installing and configuring Microsoft System Center Configuration Manager to manage approximately 200 computers on my workplace’s network. Its some great software and I’m kicking myself for not using it in the past. We’ve been able to quickly catch up on Windows and other updates through WSUS and SCUP\u00a0as well as gain intelligence on what’s going on on our desktops and more that we never had before. One of my favorite features is the “Software Center” and I’ve been working on creating applications for the most common software requests we get, as well as what we install standard on all of our desktops.<\/p>\n

After\u00a0scouring the Internet, I’ve gathered that most people are using the\u00a0EXE\u00a0package from Adobe to install the Flash Player and creating scripts and other files to disable the auto-update features and keep it silent. To me, this is a huge let down because an MSI install allows the use of the Application model in SCCM 2012 which greatly simplifies the uninstallation\/installation of new versions and the use of supercedence rules. After some digging around, testing, troubleshooting, and retesting, I think I’ve come up with a great way to use the MSI package instead of the EXE and still disable the auto-update features.<\/p>\n

 <\/p>\n

What you’ll need:<\/h3>\n

Microsoft ORCA from the Windows SDK
\nAdobe Flash Player MSI package
\nAdobe Flash Player EXE package (optional)<\/p>\n

 <\/p>\n

Here is\u00a0how I prepared the MSI:<\/h3>\n

Step 1:<\/strong> Obtain the necessary items from above.<\/p>\n

Step 2:<\/strong> Open the MSI package in ORCA.<\/p>\n

Step 3:<\/strong> Click Transform -> New Transform.<\/p>\n

Step 4:<\/strong> Choose the “CustomAction” table on the left.<\/p>\n

Step 5:<\/strong> Locate “NewCustomAction1” in the action column in the right panel and edit that row’s target to read “-install -msi -au 2”.<\/p>\n

Step 6:<\/strong> Click Transform -> Generate Transform and save the transform file.<\/p>\n

 <\/p>\n

Creating the application:<\/h3>\n

Step 1:<\/strong> Place the MSI package and your transform file in\u00a0the share on your server where you normally put applications. (ex: \\\\cfgserver\\Application Library\\Flash Player)<\/p>\n

Step 2:<\/strong> In SCCM Management Console\u00a0click on Software Library -> Application Management -> Applications -> Create Application.<\/p>\n

Step 3:<\/strong> Choose Automatic, Windows Installer,\u00a0then browse to your network share and select the MSI package. Click Next.<\/p>\n

Step 4:<\/strong> Click Next again and on the General Information Section, add any information you would like up top.\u00a0At the bottom, choose “Install for System.” In the installation program section add transform file information to the pre-filled command. Mine reads: msiexec \/i “install_flash_player_11_active_x.msi” \/qn \/t flashtransform.mst<\/p>\n

Step 5:<\/strong> Complete the wizard.<\/p>\n

 <\/p>\n

You can now deploy the Application to a collection and choose the settings you wish for the deployment. In my case, I deployed it to a collection of desktops, making it available instead of required.<\/p>\n

 <\/p>\n

Optional Steps:<\/h3>\n

I listed the EXE package above as an optional download. The reason for this is so we can assign a nice looking icon to the package when it shows up in the Software Center catalog. Again, not necessary, but polishes things up nicely.<\/p>\n

Step 1:<\/strong> Right click the Flash Player application you just created and click Properties.<\/p>\n

Step 2:<\/strong> On the Application Catalog tab, look at the bottom for Icon: and click the Browse button at the bottom right.<\/p>\n

Step 3:<\/strong> Navigate to the location of the EXE package (it can be anywhere). Erase “shell32” from the filename box and type in the filename of the EXE package. Click Open and select the icon from the package. Accept all the changes\u00a0and you are done! You can verify that auto-update has been disabled by looking in the Control Panel applet for Flash Player.<\/p>\n

 <\/p>\n

\"Software<\/a><\/p>\n

\"Flash<\/a><\/p>\n

Troubleshooting:<\/h3>\n

During my testing I found that on some desktops, the installation would fail. In my environment it came out to be caused by left-overs from old versions of Flash Player that were installed through group policy and the installers were deleted. Even uninstalling through Add\/Remove Programs and using the Adobe-supplied uninstall program would not fix the problem 100% of the time. If you get an install error,\u00a0there is\u00a0a simple fix. Just do the following:<\/p>\n

Step 1:<\/strong> Run the Adobe Flash Player uninstaller. Download at: http:\/\/helpx.adobe.com\/flash-player\/kb\/uninstall-flash-player-windows.html<\/a><\/p>\n

Step 2:<\/strong> Open regedit and browse to HKEY_CLASSES_ROOT\\Installer\\Features. Browse through each of the keys (folders) there reading the values listed in the right pane. If you see any values in a key referring to Flash Player, delete the entire key. Do the same thing for HKEY_CLASSES_ROOT\\Installer\\Products.<\/p>\n

Step 3:<\/strong> Retry the install and it should go through with no problems.<\/p>\n

I’ve also found this procedure fixes errors with Flash Player\u00a0updates delivered through WSUS and SCUP if you are using them.<\/p>\n\n

<\/div>","protected":false},"excerpt":{"rendered":"

About three weeks ago, I finally got around to installing and configuring Microsoft System Center Configuration Manager to manage approximately 200 computers on my workplace’s network. Its some great software […]<\/p>\n","protected":false},"author":1,"featured_media":381,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[35],"class_list":["post-376","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sysadmin","tag-sccm"],"_links":{"self":[{"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/posts\/376","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=376"}],"version-history":[{"count":24,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/posts\/376\/revisions"}],"predecessor-version":[{"id":507,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/posts\/376\/revisions\/507"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=\/wp\/v2\/media\/381"}],"wp:attachment":[{"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=376"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=376"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bluemunkey.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}