To successfully utilize Silverlight via a corporate network, there are four basic steps that will need to be followed.
First, you will need to plan the deployment, and after the planning phase, you will next need to test it. Once you have tested your deployment strategy, you will next need to deploy Silverlight on the network. The last and final step is to maintain Silverlight inside your environment.
This article will go over part one, which involves preparing for the actual deployment of Silverlight. To successfully install Silverlight, it is necessary for you to pay close attention to the processes and strategies you use for deployment.
You will first need to evaluate your computers in order to determine their compatibility with Silverlight. Because this media tool makes use of high fidelity, you will at least need to be using newer computers in order to make use of its features.
Once you are certain that your computers meet the compatibility requirements for Silverlight, you will next want to decide which method you want to use for deployment.
While Microsoft has not officially released their system requirements for Silverlight 2 on their site, many of those who have tested Silverlight have said that you will need to have the following minimum requirements in order to run it smoothly:
– Processor: Pentium III 450 Mhz
– Operating System: Windows XP, Vista, or 2003 Server
– RAM: 128 MB
While most newer computers today meet these system requirements, those who are using older models may run into problems when attempting to use Silverlight, so it is suggested upgrade your system if you do not meet these minimum requirements.
For MAC users, the system requirements are virtually similar to those that are listed above.
Now that we have gone through the system requirements necessary for effectively using Silverlight, let us next explore the deployment method that you will want to use.
There are a number of methods which can be used to deploy Silverlight over a corporate network, and the option that you choose should be dependent on the infrastructure which already exists, along with the location of the user.
You have the option of automating the installations of Silverlight via the settings which have been preselected, as doing so does not require any action on the part of the user.
It may also be a good idea to make use of multiple tools when it comes to deployment. One important application which can help you successfully deploy Silverlight over a network is Microsoft Systems Management Server.
Systems Management Server can assist you in automating the deployment of Silverlight through the distribution and installation of Silverlight on the users’ computers.
The good thing about using MSMS is that it does not require intervention from either you or the users. You can simply construct a .sms file that is responsible for defining how Silverlight will be placed on the users’ computers.
Silverlight Deployment Testing
One issue that needs to be taken into careful consideration is group policy. No matter whether you are a small to moderate sized organization, or even a global enterprise, having a group policy will provide you with the flexibility that is necessary for the distribution of Silverlight to large or small groups of users.
Prior to deploying Silverlight to users, it will be necessary for you to set up and process a pilot program. The good thing about Silverlight is that its installation can be tested in a lab prior to trying it out in the real world.
By using a limited number of individuals during this test, you will have the time to alter and enhance your deployment strategies. After the deployment plans have been validated, you will be sure that you are ready for total deployment.
When testing Silverlight in the lab environment, you will want to install it on the test computers in the same manner that you would install it on the computers of the users. In some situations, it may be necessary to set up the location for the network installation through the server, and then installing it on the lab computers via the server.
To lower the cost of migration, it would be a wise idea to automate the installation. You also have the option processing the installation from the beginning to the end without allowing the users to interfere.
If you choose to install Silverlight via the server, you will not have to worry about configuring the computers individually. The automation should be completed in the lab prior to carrying out the pilot program.
Once you have successfully installed Silverlight on the computers in your lab, you will next need to verify that the program runs properly, and to do this, you will want to visit this URL: http://www.microsoft.com/silverlight/.
The site will transform into an animation, and if this occurs, this means that Silverlight has been properly installed. If you so desire, you can also test both external and internal websites that are important to your business, and which will be frequently accessed by your browser.
As you test the installation, it is also important to make sure you keep a record of all the issues. The records will allow you to come up with solutions that can correct any problems which you encounter. As you encounter problems, you can test the solutions within the lab.
Once you have successfully tested deployment of Silverlight within the lab, you will next need to plan the pilot program.
The pilot program can basically be thought of as the scaled down version of the full deployment. The goal of the pilot program is to continue installation testing to continually refine deployment methods in standard use with a small number of users.
To properly use the pilot program, you will want to pick a small group of participants, and begin preparing them for the program.
Pick a group which correctly matches the diversity of your users. If your organization has a large group of users, who have various computing needs, then it may be necessary to have multiple pilot teams.
Once you have successfully put together your team, you will next need to generate a document or database which can be used to track the progress of the program, recording issues that may need to be addressed further.
Once the above issues have been successfully addressed, it will next be necessary for you to deploy Silverlight fully.
{mospagebreak title=Silverlight Deployment}
Silverlight Deployment
Once you have successfully tested Silverlight installation both in the lab and with the pilot program, it will next be necessary to begin full scale deployment.
There are three ways in which Silverlight can be installed, and these are
• Manual installation
• Group Policy Installation and
• SMS Installation.
Because Silverlight is available for Windows 2003 Server, Windows XP, and Windows Vista and Mac OS, it will be necessary to make sure you are installing the right version for your OS platform.
The executable file for the Silverlight installation has numerous switches that can be used to make a custom installation. Below is a description of syntax which can be used for the different versions:
Silverlight. 1.0beta.exe
/q = quiet install
With this syntax, Silverlight can be installed without visualizing the GUI.
/qu = quiet uninstall
Through this syntax, Silverlight can be uninstalled without the visualization of the GUI.
Silverlight Deployment Guide
Using SMS to Install Silverlight Overview: Automating the deployment of Silverlight. Using Microsoft Systems Management Server (SMS) to automate your deployment
Click here to download
In the next article, you will learn the three different methods that can be used for Silverlight installation, and the advantages and disadvantages that they have in relationship to each other.
