jaeoz.blogg.se

1. #INSTALL SILVERLIGHT ON XP HOW TO#
2. #INSTALL SILVERLIGHT ON XP INSTALL#
3. #INSTALL SILVERLIGHT ON XP UPDATE#
4. #INSTALL SILVERLIGHT ON XP CODE#

#INSTALL SILVERLIGHT ON XP CODE#

I right click on the Microsoft Code Signing PCA certificate and export it. Then I expand down to Trusted Publishers, Certificates I select Computer account, Local computer, Finish, OK

Now I need to export the client certificate. Creates a certificate and creates a registry key. This is the screen that throws off end users as they think the web console is not working and something need to be configured on the backend.įirst I click configure and download the SilverlightClientConfiguration.exe. My next challenge is the Web Console Configuration Required screen. Silverlight_圆4.exe /q or Silverlight.exe /q To do an unattended installed, the command(s) you need.

#INSTALL SILVERLIGHT ON XP INSTALL#

I recommend creating a SCCM package or login script to push the install out to the clients that need it. There are multiple ways to automate this install. The first page users are presented with is to install Microsoft Silverlight Automate Install of Microsoft Silverlight

#INSTALL SILVERLIGHT ON XP HOW TO#

Here are my sample GPOs with instructions on how to install them. This will remove the configuration screens and the end user can access the SCOM web console easily. To fix this we can automate the configuration process. Users see the “Web Console Configuration Required” screen and are often confused as to what do to. SCOM 2012 has extra steps that an end user has to take to get the web console to work. It was is a great way to give these users quick access to view the SCOM console so they can get more information about an alert they have received. The web console is often used for one-off application owners or IT staff that are not regularly using SCOM. If they are not present, you can just create them as a new “DWORD”.I have worked with a few customers that are annoyed with the user configuration required to use the new Silverlight SCOM web console.

#INSTALL SILVERLIGHT ON XP UPDATE#

Give these a value of “0” to completely disable the automatic update of Silverlight. The two items are located in the following key: We need to add/update two registry values to disable this feature. But this paragraph will tell you something that you need to know if you don’t want your users to manually update Silverlight. Well, to be honest, this isn’t really a third way to install. Msiexec /i silverlight.msi /update Silverlight.msp ALLUSERS=2 /qn /LiV %temp%\Silverlight5.log The third way Then we can install the new version by running the following command: The command that should be used is the following: When done, you can delete all files except the *.msi and *.msp file.īefore we can do a silent installation of Silverlight, we need to uninstall the old version that is installed on the client. The *.msp file is located in the “silverlight.7z” file, so go ahead and extract the file to same folder as the other files. To do this, run the following command in a elevated command prompt: The first thing is to extract the content of the *.exe file. The second way is to use the *.msi file and the *.msp file that is included in the downloaded *.exe file. In this case the complete install string would be: I would recommend using this method when the application is installed with a TS through SCCM since applications has a tendency to fail for no apparent reason. The most common way, and the easiest way is to use the *.exe file directly. If you need the 32-bit exe, you need to download it from a computer running a 32-bit OS. Note: If you are running a 64-bit OS, the file will be the one for 64-bit. The first thing we need is the exe for Silverlight that can be found here: Another application that is common in almost all environments is Silverlight, so in this post I will show you how to install Silverlight silently in three ways.