Ivan's cloud and security blog
Microsoft Azure, Microsoft 365, Defender ATP, security, DevOps and scripting
A colleague of mine asked if i could make a handy screen capture tool available to our users. I said ‘Sure – piece of cake!’. Well it was for the most part, aside from the installer loading the website post install.
I will document how i successfully completed the deployment of this software to users who opted to install it via Software Catalog website.
Welcome to Part 2 of my series of Deploying Java 7 JRE – Deep Dive!
Hopefully my first article, Deploying Java 7 JRE – Deep Dive! (Part 1) has helped you understand the history behind what Java have been doing over the past year and how all these changes will affect you. This part will cover the steps to successfully overcome the deployment of Java in an enterprise. So lets get into it!
We have all had troubles with Java and quite frankly its been a challenge to keep up with all the changes. Between Java 7 Update 10 through to update 45 there have been changes in features and functions that affect how IT administrators deploy the software in an enterprise, let alone general software functionality (wont be covering that). I think the best outcome of all of this is Oracle’s commitment to supporting enterprise deployments of Java.
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.
You have just downloaded the Adobe Flash Player distributable, created an mms.cfg configure file and you want to push it out to your network. You might be scratching your head on how to do this if you don’t have an enterprise software deployment solution?
Don’t worry – there is no need for that – all you need is Group Policy Preferences to push out your mms.cfg config file to your clients!
At last Adobe have come to the party and released Adobe Flash 11 that comes as 32-Bit and the long awaited 64-Bit versions. This is great news to me because I can now try to use IE 64-Bit browser as my main browser.
Now we have to understand how to deploy Flash 11 using Group Policy for both 32 and 64 bit versions to your clients in a manageable way. This guide will be about deploying Adobe Flash ActiveX version, however the plug-in version would work just the same.
There is a new article which covers the auto-updating aspect of Adobe Flash for enterprise. Read it here:
https://ivan.dretvic.com/2012/05/deploying-adobe-flash-player-11-2-with-auto-updating-in-an-enterprise/
This article has been superseded by a new article that includes Adobe Flash 11 (including 32Bit and 64Bit deployments)
https://ivan.dretvic.com/2011/10/adobe-flash-11-deployment-via-gpo/
So we need to update Adobe Flash for our users…again. With all the security vulnerabilities this one I like to keep on top of as much as I can even though it slips from time to time. Below is a quick summary of how I deploy Adobe Flash using Group Policy.
In brief i will document:
So i come across this every now and then where i have a machine that successfully had the software installed, but through an automatic update or user removing it the software needs to be reinstalled. Wouldnt it be great to be able to just push out the GPO to that user again? Well you cant exactly… If you redeploy a GPO software from GPMC it will force a reinstall for everyone. Below are the steps you need to do.