revisionuserinit

SilverlightDeploymentGuideMicrosoftCorporationPublished:September2007Authors:DavidTesarEditor:PeterPuszkiewiczAbstractThisguidehelpsyoutoplanandcarryoutacorporatedeploymentofSilverlight.
Theguidedescribesthesystemrequirementsanddeploymentmethods,aswellasthetechniquestomaintainandsupportSilverlightafterdeployment.
TheinformationcontainedinthisdocumentrepresentsthecurrentviewofMicrosoftCorporationontheissuesdiscussedasofthedateofpublication.
BecauseMicrosoftmustrespondtochangingmarketconditions,itshouldnotbeinterpretedtobeacommitmentonthepartofMicrosoft,andMicrosoftcannotguaranteetheaccuracyofanyinformationpresentedafterthedateofpublication.
Thisdocumentisforinformationalpurposesonly.
MICROSOFTMAKESNOWARRANTIES,EXPRESS,IMPLIEDORSTATUTORY,ASTOTHEINFORMATIONINTHISDOCUMENT.
Complyingwithallapplicablecopyrightlawsistheresponsibilityoftheuser.
Withoutlimitingtherightsundercopyright,nopartofthisdocumentmaybereproduced,storedinorintroducedintoaretrievalsystem,ortransmittedinanyformorbyanymeans(electronic,mechanical,photocopying,recordingorotherwise),orforanypurpose,withouttheexpresswrittenpermissionofMicrosoft.
Microsoftmayhavepatents,patentapplications,trademarks,copyrightsorotherintellectualpropertyrightscoveringsubjectmatterinthisdocument.
ExceptasexpresslyprovidedinanywrittenlicenseagreementfromMicrosoft,thefurnishingofthisdocumentdoesnotgiveyouanylicensetothesepatents,trademarks,copyrightsorotherintellectualproperty.
Unlessotherwisenoted,theexamplecompanies,organizations,products,domainnames,e-mailaddresses,logos,people,placesandeventsdepictedhereinarefictitious,andnoassociationwithanyrealcompany,organization,product,domainname,e-mailaddress,logo,person,placeoreventisintendedorshouldbeinferred.
2007MicrosoftCorporation.
Allrightsreserved.
Microsoft,Windows,WindowsVista,WindowsServer,Silverlight,InternetExplorer,WindowsMedia,SharePoint,andActiveDirectoryareeitherregisteredtrademarksortrademarksofMicrosoftCorporationintheUnitedStatesand/orothercountries.
ContentsSilverlightDeploymentGuide1Abstract1Contents3SilverlightDeploymentGuide5Silverlightvalueproposition5HowtodeploySilverlight5Part1:PreparingforDeployment7PlanningtheSilverlightDeployment7SystemrequirementsforSilverlight7Selectyourdeploymentmethod8SettingUpandAdministeringaPilotProgram9ConductingLabTesting9Planningthepilotprogram9Part2:DeployingSilverlight10ManualInstalloptionsforSilverlight10SelectingtherightversionofSilverlight10InstallationSwitches11UsingGroupPolicytoInstallSilverlight11GroupPolicyScriptsExtensionOverview11Assigningcomputerstartupscripts12ExampleScript13DeployingComputerStartupScripts14Specifyingmaximumtimeforstartupscriptstorun15UsingSMStoInstallSilverlight16Overview:AutomatingthedeploymentofSilverlight16PreparingtoautomaticallydeploySilverlight16Step1:CreatinganSMSpackageforSilverlight16Step2:SelectingtheSMSdistributionservers18Step3:CreatingandrunningajobtodistributetheSMSpackage18Theinstallationprocess19Part3:MaintainingandSupportingSilverlight19ManagingSilverlightSettingsThroughGroupPolicy20GroupPolicyoverview20UsingAdministrativeTemplatesettingstomanageSilverlight20ADMandADMXfiletemplatesettings21Registry-basedSilverlightpolicysettings24Modifyingregistry-basedSilverlightpolicysettings25KeepingSilverlightUpdated25AutomaticUpdates25Softwareupdatemethods26SystemsManagementServer26GroupPolicySoftwareInstallation26WindowsServerUpdateServices(WSUS)27ScriptedorManual27Troubleshooting27Silverlightinstallationanduninstallation27SilverlightInstallprocessfails27UnabletouninstallSilverlight28DisablingSilverlightadd-oninInternetExplorer729SilverlightDeploymentGuideTheSilverlightDeploymentGuidedocumentstheoptionsandprocessesinvolvedindeployingSilverlight1.
0touser'scomputersthatarerunningMicrosoftWindowsXPwithServicePack2(SP2),WindowsServer2003,orWindowsVistainanetworkenvironment.
SilverlightalsoinstallsonAppleMacOSX,butAppledeploymentsareoutsideofthescopeofthisdocument.
TolearnmoreaboutSilverlight,gotohttp://www.
microsoft.
com/silverlight.
ThisguideshouldbeusedduringtheplanningphaseofyourSilverlightdeploymentproject.
Theinformationprovideskeypointsofguidanceforadeploymentproject.
Itisnotintendedasastep-by-stepguide,andnotallofthestepsdescribedinthisguidearenecessaryfordeployingSilverlightineveryenvironment.
SilverlightvaluepropositionSilverlightdeliversthenextgenerationofMicrosoft.
NET–basedmediaexperiencesandrichinteractiveapplicationsforinternetbrowsers.
SilverlightcomplimentsotherMicrosoftproductssuchasASP.
NET,WindowsServerandWindowsMediatodeliverunprecedentedcrossbrowser,crossplatformrichinteractivewebapplicationexperiences.
SilverlightarchitectureisconsistentwithWeb2.
0paradigmsanditenablesenterprisewebdeveloperstoextendtheirskillsanddeliverbetterexperiences.
ThefollowingarebenefitsofdeployingSilverlightinanenterprise:CompatibilitywithSilverlight-enabledwebsitesAbilitytoofferandconsumemediaaspartofthewebexperienceonWindowsandMacintoshoperatingsystemsSimpleintegrationwithexistingWebtechnologiesandassetssuchasASP.
NETandSharePointservicesBetteruserexperienceforwebapplicationwithoutdeploymentconsiderationsFormoreinformationonwhyyoushoulduseSilverlight,pleasevisit:http://www.
microsoft.
com/silverlight/andclickon"WhySilverlight".
HowtodeploySilverlightTheprocessofdeployingSilverlighttoyourorganization'susers'computersisorganizedinthisdeploymentguideasfollows:StepPagePlanthedeploymentPart1:PreparingforDeploymentPlanningtheSilverlightDeploymentdetailshowtoplanyourdeploymentprocessesandstrategies.
TestthedeploymentstrategySettingUpandAdministeringaPilotProgramdescribesthetestingprocessforSilverlightdeployment.
DeploySilverlightPart2:DeployingSilverlightManualInstalloptionsforSilverlightfocusesonhowtoeffectivelyusesharedfolders,Web,ande-mailprocedurestodeploySilverlight.
Italsodetailstheswitchesfortheinstallationexecutablefile.
UsingGroupPolicytoInstallSilverlightdetailstheprocedurestodeploySilverlightusingGroupPolicy.
UsingSMStoInstallSilverlightexploresmethodsforusingMicrosoftSystemManagementServer(SMS)todeploySilverlight.
MaintainSilverlightinyourenvironmentPart3:MaintainingandSupportingSilverlightManagingSettingsThroughGroupPolicydescribeshowtomanageSilverlightintheActiveDirectoryservicesenvironmentbyusingGroupPolicy.
KeepingSilverlightUpdatedreviewssystemmanagement,automaticupdate,andothertoolstodeployupdatedversionsofSilverlighttoyourusers'computers.
TroubleshootinghelpsyoutroubleshootSilverlightinstallation,GroupPolicysettings,andfeaturesinyourcorporateenvironment.
Part1:PreparingforDeploymentPart1oftheSilverlightDeploymentGuidedescribeshowtodeploySilverlighttoyourorganization.
Itincludesinformationaboutplanningforthedeploymentandperformingasuccessfulpilotprogram.
PlanningtheSilverlightDeploymentdetailshowtoplanyourdeploymentprocessesandstrategies.
SettingUpandAdministeringaPilotProgramdiscusseshowtoprepareyourusersforSilverlightthroughatrainingprogramanddescribesthetestingprocessforSilverlightdeployment.
PlanningtheSilverlightDeploymentToinstallSilverlightsuccessfully,youmustcarefullyplanyourdeploymentprocessesandstrategies.
Thissectionofthedeploymentguidecontainsinformationabouthowtoevaluateandplanyourdeployment,including:1.
Evaluatingusers'computersforcompatibilitywithSilverlightSystemRequirementsforSilverlight2.
IdentifyingyourdeploymentmethodSelectYourDeploymentMethodSystemrequirementsforSilverlightThetablebelowliststheminimumrequirementsyourcomputerneedstorunSilverlight.
Silverlightwillinstallonthe32-bitor64-biteditionsofanyversionofeitherWindowsXPrunningServicePack2(SP2),WindowsServer2003,orWindowsVista.
SilverlightalsoinstallsonAppleMacOSX,butAppledeploymentsareoutsideofthescopeofthisdocument.
Silverlightwillnotinstalliftheoperatingsystemorbrowserisnotsupported.
SilverlightmayinstallifsomeoftheotherminimumrecommendationsarenotmetalthoughtheSilverlightfunctionalitywillbesignificantlyreducedorpossiblynon-operational.
Windows-basedPCRequirementsComputer/processorIntelPentiumIII450-megahertz(MHz)orfaster,equivalentprocessorOperatingsystemWindowsXPwithSP2Windows2003ServerWindowsVistaMemory128MBBrowser(mustbethisrevisionorlater)MicrosoftInternetExplorer6or7,MozillaFirefox1.
5.
0.
8,orFirefox2.
0.
xMacintoshComputerRequirementsComputer/processorPowerPCG3500-megahertz(MHz)orfasterprocessorORIntelCoreDuo1.
83-gigahertz(GHz)orfasterprocessorOperatingsystemAppleMacOSX10.
4.
8orhigherMemory(onlyforIntelProcessor)128MBBrowser(mustbethisrevisionorlater)Firefox1.
5.
0.
8,Firefox2.
0.
x,andAppleSafari2.
0.
4SelectyourdeploymentmethodThemethodyouselectforyourorganization'sdeploymentwilldependonyourexistinginfrastructure,securityrequirements,anduserlocation.
YoucanusevariousmethodstodistributeSilverlighttoyourusers.
YoucanautomateinstallationsofSilverlightwithpreselectedsettingssothatnouseractionisrequired,oryoucanallowusersseetheinstallationprocessonthescreen.
Youmightwanttouseadditionaltoolsaspartofthedeploymentprocess.
ConsiderthefollowingapplicationsandhowyoucanusethemtosupportyourdeploymentofSilverlight:MicrosoftSystemsManagementServercanhelpyouautomatealarge-scaledeploymentofSilverlightbydistributingandinstallingSilverlightonyourusers'computers.
Thisautomatedinstallationrequiresnointerventionfromyouoryourusers.
Youcancreateapackagedefinition(.
sms)filethatdefineshowSilverlightisinstalledonusers'computers.
Thenyoucancreateajobtodistributeyourpackagetousers'computers.
FormoreinformationaboutincorporatingSMSintoyourdeploymentprocess,seeUsingSMStoInstallSilverlightinthisdeploymentguide.
GroupPolicyisidealtodeploySilverlightinsmalltomediumsizedorganizationsorwhereitisnotbeingdeployedtoalargenumberofuserssimultaneously.
GrouppolicyallowsflexibilitytodistributeSilverlighttoindividualorgroupsofusersandcomputersaswellasspecificOUs.
Formoreinformationaboutincorporatinggrouppolicyinyourdeploymentprocess,seeUsingGroupPolicytoInstallSilverlightinthisdeploymentguide.
ManualOptionsexistinthissectiontolightlyassistdeploymentsinanenvironmentnotusinggrouppolicyorSMS–suchasenvironmentsusing3rdpartysoftwaredeploymenttools.
Installfileselectionandinstallationswitchesarecoveredhere.
SettingUpandAdministeringaPilotProgramBeforeyoudeploySilverlighttoyourusers,testyourinstallationofSilverlightinalab,andthenconductthepilotprogramwithalimitednumberofparticipantstorefineyourdeploymentconfigurationsandstrategies.
Thisprocesswillhelpyouvalidateyourdeploymentplanandensurethatyouarereadyforfull-scaledeployment.
ConductingLabTestingInstallSilverlightonthelabcomputersinthesamewaythatyouplantoinstallSilverlightonyourusers'computers.
Insomecases,thismightmeansettingupthenetworkinstallationlocationontheserverandtheninstallingSilverlightonthelabcomputersfromtheserver.
Automatingyourinstallationisanimportantstepinreducingthecostofmigration.
Youcanchoosetoruntheinstallationprocessfromstarttofinishwithoutuserintervention.
YoucanalsoinstallSilverlightfromtheserversothatyoudonotneedtoconfigureindividualcomputers.
Completeanyautomationworkinthelabbeforeyouconductthepilotprogram.
AfteryouinstallSilverlightonthelabcomputers,verifythatthesoftwarerunscorrectlybyvisitingthewebsitehttp://www.
microsoft.
com/silverlight/.
ThesitewilltransitiontoananimationthatnotifiesyouthatSilverlightwasinstalledcorrectly.
Ifdesired,testinternalorexternalWebsitesthatarecriticaltothebusinessthatwillbeaccessedwithyourbrowser.
Duringthetestingprocess,maintainarecordofallissues.
Theserecordswillhelpyoudesignsolutionstocorrecttheissuesyouencountered.
Thenverifyeachsolutionbyusingthesametestingprocessinthelab.
Ifyourunintoproblems,seeTroubleshootinginPart3ofthisdeploymentguide.
Thissectionprovidesinformationaboutcommonlyreportedissuesandsolutionstrategies.
PlanningthepilotprogramAfteryoutestthedeploymentprocessinthelab,planyourpilotprogram.
Thisprogramprovidesascaled-downversionofthefinaldeployment.
Thegoalofthepilotprogramistofurthertestandrefinedeploymentstrategiesandconfigurationsineverydayuseamongalimitedgroupofusers.
Toplanthepilotprogram,completethefollowingtasks:Selectappropriatepilotgroupparticipants,andpreparethemforthepilotprogram.
Selectgroupsthatrepresentthediversityofyourcomputerusers.
Ifyourorganizationincludeslargeusergroupsorgroupswithvariouscomputingenvironmentsorrequirements,youmightneedtoselectseveralpilotgroups.
Createadocumentordatabasetotrackyourprogressandrecordissuesthatmightrequirefurtheraction.
Part2:DeployingSilverlightAfterplanningandtesting,thefinalstepinthedeploymentprocessisrollingoutyourinstallationofSilverlighttoyourusers.
Part2oftheSilverlightDeploymentGuidedescribestheprocessesthatareusedtodeploySilverlight.
ManualInstalloptionsforSilverlightprovidessomebasicinformationabouttheinstallfileselection,installationswitches,andMSI/MSPextractiontoassistdeploymentsinanenvironmentnotusinggrouppolicyorSMS.
UsingGroupPolicytoInstallSilverlightdetailstheprocedurestodeploySilverlightusingGroupPolicy.
UsingSMStoInstallSilverlightexploresmethodsforusingMicrosoftSystemManagementServer(SMS)todeploySilverlight.
ManualInstalloptionsforSilverlightThissectionprovidesbasicinformationfordeployingSilverlightbyprovidingfileversioninformation,installationswitches,andMSIextraction.
DeployingSilverlightthroughSMSorgrouppolicycanbeperformedsilentlywithoutuserinterventionandisexplainedlaterinthisdocument.
ThissectionmaybeusefulforcompanieswhodonothaveanActiveDirectoryinfrastructureorSMSandutilizeaseparatemeansforsoftwaredistributioninthecompanyordesiretodeploySilverlighttoAppleclients.
SelectingtherightversionofSilverlightSilverlightisavailableforWindowsXP,WindowsServer2003,WindowsVista,andAppleMacOSX10.
4.
ThefollowingtableliststheoperatingsystemssupportedbySilverlight,alongwiththeSetupfilenameforeach.
OperatingsystemFilenameWindowsXPSP2,WindowsServer2003orWindowsVistaSilverlight.
1.
0.
exeAppleMacOSXSilverlight.
1.
0.
dmgAllversionsofSilverlightcanbedownloadedfromtheSilverlightWebsiteathttp://www.
microsoft.
com/silverlight/downloads.
aspxInstallationSwitchesTheSilverlightinstallexecutablefilehasanumberofdifferentswitchestocustomizetheinstallation.
Thesyntaxofthesetupfileisasfollows:Silverlight.
1.
0beta.
exe/q=quietinstall.
ThisinstallsSilverlightwithoutseeingtheGUI.
/qu=quietuninstall.
ThisuninstallsSilverlightwithoutseeingtheGUI.
UsingGroupPolicytoInstallSilverlightGrouppolicyisidealtodeploySilverlightinsmalltomediumsizedorganizationsorwhenitisnotbeingdeployedtoalargenumberofuserssimultaneously.
Forlargeorganizations,SilverlightisbestdeployedusingSMSoranotherthird-partysoftwaredistributiontool.
AlimitationofthegrouppolicydeploymentmethodisthatitappliesonlytoMicrosoftoperatingsystems,ignoringAppleoperatingsystemclients.
GroupPolicyScriptsExtensionOverviewTheGroupPolicyinfrastructureincludesaScriptsextensionthatconsistsofthefollowingcomponents:AMicrosoftManagementConsole(MMC)server-sideextensionoftheGroupPolicyObjectEditorMMCsnap-inthatisusedforadministeringandconfiguringscripts.
TheadministratorusesthescriptsextensiontospecifyscriptspolicysettingsinaGroupPolicyobject(GPO),andthenlinkstheGPOtothesite,domain,ororganizationalunittowhichtheadministratorwantstoassignthescripts.
TheGroupPolicyObjectEditorsnap-inincludestwoextensionsforscriptdeployment:Scripts(Startup/Shutdown).
Administratorsusethisextensiontospecifyscriptsthatrunwhenthecomputerstartsuporshutsdown.
ThesescriptsrunasLocalSystem.
Scripts(Startup/Shutdown)islocatedundertheComputerConfiguration\WindowsSettingsnodeofGroupPolicyObjectEditor.
Scripts(Logon/Logoff).
Administratorsusethisextensiontospecifyscriptsthatrunwhentheuserlogsonorlogsoffthecomputer.
ThesescriptsrunasUser,notasAdministrator.
Scripts(Logon/Logoff)islocatedundertheUserConfiguration\WindowsSettingsnodeofGroupPolicyObjectEditor.
Aclient-sideextension,whichisadynamic-linklibrary(DLL)ontheclientcomputerthatinteractswiththeGroupPolicyinfrastructureandimplementsGroupPolicyscriptsontheclientcomputer.
AseparateprocesscalledUserinit.
exerunsthescripts.
FormoreinformationaboutGroupPolicyScriptsextensions,seetheScriptsExtensionTechnicalReferenceoftheWindowsServer2003GroupPolicyTechnicalReferenceontheMicrosoftTechNetWebsite.
ForinformationaboutWindowsScriptHost,seeWindowsScriptHostontheMSDNWebsite.
Important:GroupPolicyprovidestheabilitytoaffectconfigurationsacrosshundredsandeventhousandsofcomputersinanorganization.
Therefore,itiscriticalthatyourigorouslytestallnewGroupPolicyconfigurationsordeploymentsinanon-productionenvironmentbeforeyoumovethemintoyourproductionenvironment.
FordetailedinformationaboutstagingGroupPolicydeployments,seeStagingGroupPolicyDeploymentsintheDesigningaManagedEnvironmentbookoftheMicrosoftWindowsServer2003DeploymentKit.
Bydefault,thesystemletscombinedsetsofscriptsrunforupto600seconds(10minutes)only.
Administratorscanuseapolicysettingtoadjustthisintervaltoensurethestartupscriptcompletesrunning.
TheMaximumwaittimeforGroupPolicyscriptspolicysettingspecifieshowlongthesystemwaitsforscriptsappliedbyGroupPolicytorun.
Thissettinglimitsthetotaltimeallowedforalllogon,startup,andshutdownscriptsappliedbyGroupPolicytofinishrunning.
AswithanyGroupPolicydeployment,youmustfullytestyourstartupscriptsinastagingenvironmentbeforedeployingthemtoyourproductionenvironment.
TestingwillhelpyoudeterminethevaluetousefortheMaximumwaittimeforGroupPolicyscriptspolicyforyourparticularnetworkenvironment.
Settingthisvaluetoolowmaycausetheinstalltoterminateprematurely.
Therearefactorsthatmayaffectthisvalue,suchasnetworkspeed,clientcomputerhardware,andotherscriptsrunningontheclientcomputer.
Byfullytestingthispolicysettingyoucandeterminetheappropriatevaluetouseforyourspecificenvironment.
TheMaximumwaittimeforGroupPolicyscriptspolicysettingisavailableintheComputerConfiguration\AdministrativeTemplates\System\ScriptsfolderinGroupPolicyObjectEditor.
Forinformationaboutconfiguringthispolicysetting,seeSpecifyingmaximumtimeforstartupscriptstorun.
AssigningcomputerstartupscriptsStartupscriptsrunasLocalSystemandhavethefullrightsrequiredtorunasLocalSystem.
Note:ThefollowingproceduresassumeyouhavealreadyinstalledGPMC.
YoucandownloadGPMCfromtheMicrosoftDownloadCentersite.
SeeDownloadGroupPolicyManagementConsole(GPMC)formoreinformation.
IfyouareusingWindowsVista,GPMCisintegratedintotheoperatingsystem.
YoumustbeloggedonasamemberoftheDomainAdministratorssecuritygroup,theEnterpriseAdministratorssecuritygroup,ortheGroupPolicyCreatorOwnerssecuritygrouptocompletetheseprocedures.
ThefollowingsectionsprovideasamplescriptandinstructionsforinstallingSilverlight.
SampleScriptRequirements:ThetargetcomputermustberunningWindowsXP,WindowsServer2003,orWindowsVista.
ARead-onlynetworksharecontainingtheSilverlight.
exeinstallerARead-writenetworkshareforstoringcentralizedlogfilesExampleScriptsetlocalREMREMEnvironmentcustomizationbeginshere.
Modifyvariablesbelow.
REMREMSetDeployServertoanetwork-accessiblelocationcontainingtheSilverlightinstallersetDeployServer=\\server\share\SilverlightREMSetInstallerNametothenameofyourcopyoftheSilverlightinstallersetInstallerName=Silverlight.
1.
0.
exeREMSetLogLocationtoacentraldirectorytocollectlogfiles.
SetLogLocation=\\server\share\SilverlightLogsREMREMDeploymentcodebeginshere.
Donotmodifyanythingbelowthisline.
REMregqueryHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlightif%errorlevel%==1(gotoDeploySilverlight)else(gotoEnd)REMIf1returned,theproductwasnotfound.
Runsetuphere.
:DeploySilverlightstart/wait%DeployServer%\%InstallerName%echo%date%%time%Setupendedwitherrorcode%errorlevel%.
>>%LogLocation%\%computername%.
txtREMIf0orotherwasreturned,theproductwasfoundoranothererroroccurred.
Donothing.
:EndEndlocalInthisexample,scriptlogginginformationiswrittentocomputername.
txtfile.
Areturncodeof0inthelogfileindicatesthattheinstallationcompletedsuccessfully.
FormoreinformationaboutothererrorcodesforWindowsInstallerprocessesforSilverlightproducts,seetheWindowsInstallerErrorCodeReferenceontheMicrosoftDeveloperNetworkwebsiteandthetroubleshootingsectionofthisdeploymentguide.
DeployingComputerStartupScriptsTosetupscriptsonthedomaincontrollerCopythescriptanddependentfilestotheNetlogonsharedfolderoranothersharedfolderonthedomaincontrollerfromwhichyouwantthescripttorun.
Note:ThetargetcomputeraccountneedsReadpermissiontotheSilverlightsourcefileslocation,andReadandWritepermissionstothelogfilelocation.
Thelogfilecanbestoredonthelocalcomputer.
Toassigncomputerstartupscripts1.
ClickStart,clickControlPanel,clickAdministrativeTools,andclickGroupPolicyManagement.
2.
Intheconsoletree,double-clickGroupPolicyObjectsintheforestanddomainthatcontainstheGroupPolicyobject(GPO)thatyouwanttoedit.
ThisislocatedinForestname/Domains/Domainname/GroupPolicyObjects.
3.
Right-clicktheGPOyouwanttousetoassignscriptsandclickEdit.
ThisopenstheGroupPolicyObjectEditorconsole.
4.
InGroupPolicyObjectEditor,intheconsoletree,clickScripts(Startup/Shutdown).
ThisislocatedintheComputerConfiguration\WindowsSettingsnode.
5.
Inthedetailspane,double-clickStartup.
6.
IntheStartupPropertiesdialogbox,clickAdd.
7.
IntheAddaScriptdialogbox,dothefollowing:InScriptName,typethepathtothescript,orclickBrowsetosearchforthescriptfileintheNetlogonsharedfolderonthedomaincontroller.
InScriptParameters,typetheparametersyouwanttouseasyouwouldtypethemonthecommandline.
Forexample,ifyourscriptincludedparameterscalled//logo(displaybanner)and//I(interactivemode),type://logo//I.
8.
IntheStartupPropertiesdialogbox,specifytheoptionsyouwanttouse.
Thefollowingoptionsareavailable:StartupScriptsforGroupPolicyobject.
ListsallthescriptsthatarecurrentlyassignedtotheselectedGroupPolicyobject.
Ifyouassignmultiplescripts,thescriptsareprocessedintheorderthatyouspecify.
Tomoveascriptupinthelist,selectthescriptandclickUp.
Tomoveascriptdowninthelist,selectthescriptandclickDown.
Add.
OpenstheAddaScriptdialogbox,whereyoucanspecifyadditionalscriptstouse.
Edit.
OpenstheEditScriptdialogbox,whereyoucanmodifyscriptinformation,suchasnameandparameters.
Remove.
RemovestheselectedscriptfromtheStartupScriptslist.
ShowFiles.
DisplaysthescriptfilesthatarestoredintheselectedGroupPolicyobject.
SpecifyingmaximumtimeforstartupscriptstorunTosetthemaximumtimeforstartupscriptstorunClickStart,clickControlPanel,clickAdministrativeTools,andclickGroupPolicyManagement.
Intheconsoletree,double-clickGroupPolicyObjectsintheforestanddomainthatcontainstheGroupPolicyobject(GPO)thatyouwanttoedit.
ThisislocatedinForestname/Domains/Domainname/GroupPolicyObjects.
Right-clicktheGPOyouwanttousetoassignscriptsandclickEdit.
ThisopenstheGroupPolicyObjectEditorconsole.
InGroupPolicyObjectEditor,intheconsoletree,navigatetoComputerConfiguration\AdministrativeTemplates\System\Scripts.
Onthedetailspane(leftsideoftheconsole),double-clicktheMaximumwaittimeforGroupPolicyscriptspolicysetting,clickEnabled,enterthevalueyouwanttouseintheSecondsscroll-downbox,andthenclickOK.
Important:Makesureyoufullyteststartupscriptsinastaging,non-productionenvironmentbeforeyoudeploythemtoyourproductionenvironment.
UsingSMStoInstallSilverlightOverview:AutomatingthedeploymentofSilverlightUsingMicrosoftSystemsManagementServer(SMS)toautomateyourdeploymentcanhelpeliminatedesktopvisitsandhumanerrorbyelectronicallydistributingyourSilverlightpackageoverthenetworkfromacentrallocationtousers'computers.
Youcanchoosethegroupofusers'computersonwhichyouwanttoautomaticallyinstallthepackageandthedatesandtimeswhenyouwanttheinstallationtooccur.
Thisflexibilitycanhelpyouavoidnetworkcongestionandensurethatthedeploymentoccursafterusershavehadsufficienttimetoreceivetrainingandpreparefortheinstallation.
SMSinstallstheSilverlightsoftwarewithoutrequiringuserinteraction(silentinstall),anditcaninstallthesoftwarewithadministrativecredentialsevenifauserwithoutadministrativecredentialsisloggedonbyrunninginthecontextoftheSYSTEMaccount.
UsersdonotneedtologontoserversorcomputersthatarebasedonMicrosoftWindowsNTtoperformupdates.
ThismakesSMSidealforoff-hoursdistributionordistributiontosecurity-enabledservers.
SMSprovidesstatusreportssothatyouknowwhenthesoftwarehasbeensuccessfullyinstalled.
FormoreinformationaboutSMS,pleaseseetheproductdocumentationat:http://www.
microsoft.
com/technet/sms/PreparingtoautomaticallydeploySilverlightStep1:CreatinganSMSpackageforSilverlightCompletethefollowingstepstocreatetheSMSpackage(thisistheactualpackagethatSMSusesfordistribution).
CreateanSMSpackageforSilverlight1.
ToopentheSMSAdministratorConsole,clickStart,pointtoAllPrograms,pointtoSystemsManagementServer,andthenclickSMSAdministratorConsole.
2.
Intheleftpane,expandSiteDatabase.
3.
Right-clickPackages,clickNew,andthenclickPackage.
4.
ClicktheGeneraltab,andtypethenameofthepackage,itsversion,itspublisher,itslanguage,andadescriptivecomment.
(TheonlyrequiredvalueonthistabisName.
)6.
ClicktheDataSourcetab.
7.
OntheDataSourcetab,selecttheThisPackageContainsSourceFilescheckbox.
8.
UnderSourceDirectory,clickSettoopentheSetSourceDirectorydialog.
9.
TypethepathtotheSilverlightSetupfiles,orclickBrowsetolocatethedirectory.
ClickOKtoreturntotheDataSourcetab.
10.
ClicktheDistributionSettingstab.
Selectyourpreferredpriorityandsender.
11.
ClickOKtocreatethepackage.
EverySMSpackagemustincludeatleastoneprogramtodefinethecommandlineparameterstousewhenrunningtheSetup.
Somepackageswillhavemultipleprograms.
Createaprogram1.
ToopentheSMSAdministratorConsole,clickStart,pointtoAllPrograms,pointtoSystemsManagementServer,andthenclickSMSAdministratorConsole.
2.
Intheleftpane,expandSiteDatabase,expandPackages,andthenexpandyourSilverlightpackage.
3.
Right-clickPrograms,clickNew,andthenclickProgram.
4.
IntheGeneraltab,enteradescriptivenamefortheprogram.
5.
InCommandline,entertheexactcommandlinetobeusedwhenthisprogramisrun.
Mostdeploymentswilluseoneofthefollowingcommandlines.
Seetheinstallationswitchessectionformoreinformation.
Silverlight.
1.
0.
exeSilverlight.
1.
0.
exe/q(SilentInstall-recommended)6.
IntheRundrop-downlist,selecttheNormaloptiontodeterminehowtheSetupwindowwillbedisplayedwhentheprogramisrun.
7.
IntheAfterrunningdrop-downlist,selecttheoptionthatdescribestheactiontotakeaftertheprogramhascompleted.
Therecommendedsettingis"NoActionRequired".
8.
ClicktheRequirementstab.
EntertheinformationfortheSilverlightsoftwarerequirementsthatapplytothisprogram.
Usethedrop-downliststodeterminehowmuchdiskspaceshouldbeavailableforthesetup(10MB),themaximumamountoftimetolettheprogramrun(3minutes),andtheoperatingsystemsthataresupportedbythisprogram.
ThiscanbedeterminedbyexaminingtheMicrosoftSilverlightSystemRequirementspage.
9.
ClicktheEnvironmenttab.
IntheProgramcanrundrop-downlist,selectWhetherornotauserisloggedon.
ThiswillinstallSilverlightasmandatoryandsilent.
10.
UnderRunmode,clicktheoptionthatdescribestherequireduserpermissionlevelandchooseRunwithadministrativerights.
11.
ClicktheAdvancedtab.
UnderWhenthisprogramisassignedtoacomputer,selectRunonceforthecomputer.
12.
ClickOKtosavetheprogram.
Step2:SelectingtheSMSdistributionserversYourSMSdistributionserversarethedistributionpointsforyourSMSpackage.
SMScopiesallthefilesfromthepackagesourcefoldertoafolderonyourSMSdistributionservers.
SetuprunsfromtheseSMSdistributionserverstosupporttheusersonyournetwork.
ToselecttheSMSdistributionservers1.
OntheSMSAdministratorConsole,intheleftpaneunderPackages,right-clicktheSMSpackagethatyoudesignatedforSilverlight,andthenclickDistributionpoints.
2.
OntheNewDistributionPointsWizardwelcomepage,clickNext.
3.
OntheCopyPackagepage,selectyourdistributionserversfromtheDistributionpointslist,andthenclickFinish.
Step3:CreatingandrunningajobtodistributetheSMSpackageAfteryoucreatetheSMSpackageforSilverlight,youmustcreateajobtodistributeit.
Thisjobincludes:Thelistofusers'computersthatwillreceivetheSMSpackageforSilverlight.
ThisisdefinedinSMSasacollection.
EverycomputerinacollectionwillreceiveanadvertisementfortheSMSjobwhenitisassigned.
Thescheduleforrunningthepackage.
Anadvertisementforthepackage,whichwillbesenttotheusers'computers.
TocreateandrunajobtodistributetheSMSpackage1.
OntheSMSAdministratorConsole,intheleftpane,expandSiteDatabase.
2.
Right-clickAdvertisements,pointtoNew,andthenclickAdvertisement.
3.
IntheAdvertisementPropertiesdialogbox,selectvaluesforthefollowingfields:Name.
Thenameforthejob.
Comment.
Adescriptionofthepackage.
Thisfieldisoptional.
Package.
TheSMSpackageforSilverlightthatyoucreatedinStep1:CreatinganSMSpackageforSilverlightearlierinthissection.
Program.
TheSilverlightexecutablefile,whichispartofthepackagethatyoubuiltinStep1:CreatinganSMSpackageforSilverlightearlierinthissection.
Collection.
Providethenameyoudesireforthecollectiontowhichyouwanttodeploythepackage,suchas"Silverlight".
4.
ClicktheScheduletab,andthenselectthedatesandtimeswhenyouwantthepackagetorun.
Ifyouwanttomandatoryforcethepackageinstallation,specifythedateandtimeofinstallationunder"mandatoryassignments".
5.
ClicktheAdvancedClienttab,andthenfor"Whenadistributionpointisavailablelocally",select"RunProgramfromaDistributionPoint"&for"Whennodistributionpointisavailablelocally",select"DownloadProgramfromaremotedistributionpoint"Whenthejobruns,youcanviewitbyclickingAdvertisedProgramsintheWindowsControlPanel.
Thejobalsocreatesanerrorlogfile(Iesmswrap.
mif),whichislocatedinthe\Windows\Tempfolder.
Youcanperformasearchfor*.
miftolocatethefile.
TheinstallationprocessAtthescheduleddateandtime,SMSsendsthepackagetothespecifiedusers'computers.
Whenthesecomputersrecognizethatthepackageisavailable,theinstallationprocessbegins.
SilverlightSetupperformsthefollowingtasks:Pre-requisitecheck(seeInstallationRequirementsinthisdocument)Ensurealaterversionisn'tinstalledUninstallpreviouslyinstalledversionifpresentInstalltheproductWriteSilverlightregistrykeysCreatefilesin%ProgramFiles%\MicrosoftSilverlight\Part3:MaintainingandSupportingSilverlightPart3oftheSilverlightDeploymentGuidedescribestheprocessesusedtomaintainandsupportSilverlightinyourorganizationafteryourinitialdeployment.
ManagingBrowserSettingsThroughGroupPolicydescribeshowtomanageSilverlightandadministersystempoliciesandrestrictionsinyourActiveDirectoryenvironmentbyusingGroupPolicyAdministrativeTemplatesandtheSilverlightMaintenanceextension.
KeepingSilverlightUpdatedreviewssystemmanagement,automaticupdate,andothertoolstodeployupdatedversionsofSilverlighttoyourusers'computers.
TroubleshootinghelpsyoutroubleshootSilverlightpackages,Silverlightinstallation,andGroupPolicysettingsinyourcorporateenvironment.
ManagingSilverlightSettingsThroughGroupPolicyIfyouuseanActiveDirectoryenvironmenttoadministerthecomputersinyournetwork,GroupPolicyprovidesacomprehensivesetofpolicysettingstomanageSilverlightafteryouhavedeployedittoyourusers'computers.
YoucanusetheAdministrativeTemplatepolicysettingstoestablishandlockregistry-basedpoliciesforSilverlightoptions.
GroupPolicyoverviewGroupPolicyisacollectionofsettingsthatareusedtodefineandmanageconfigurationsforgroupsofusersandcomputersinanActiveDirectoryenvironment.
GroupPolicyenablesyoutodefineaSilverlightconfigurationandothersoftwareandsystemconfigurationsaspartofGroupPolicyobjects(GPOs).
TheGPOsarelinkedtohierarchicalActiveDirectorycontainerssuchassites,domains,ororganizationalunits.
TheyenableyoutomanageyourSilverlightandothersystemconfigurationsformultipleusersonanycomputerthatisjoinedtothedomain.
NoteYoumustbeamemberoftheAdministratorsgrouptoworkwithGPOs.
FormoreinformationaboutGroupPolicy,see:WindowsServer2003GroupPolicy(http://go.
microsoft.
com/fwlink/LinkId=56544)ManagingWindowsXPServicePack2FeaturesUsingGroupPolicy(http://go.
microsoft.
com/fwlink/LinkId=55587)GroupPolicyFrequentlyAskedQuestions(http://go.
microsoft.
com/fwlink/LinkId=59182)GroupPolicySettingsReferenceforWindowsVista(http://go.
microsoft.
com/fwlink/LinkId=54020)ImplementingCommonDesktopManagementScenarioswiththeGroupPolicyManagementConsole(http://go.
microsoft.
com/fwlink/LinkId=75316)WindowsVistaSecurityGuide(http://go.
microsoft.
com/fwlink/LinkId=74028)UsingAdministrativeTemplatesettingstomanageSilverlightThissectiondescribeshowtouseregistry-basedAdministrativeTemplatepolicysettingsinGroupPolicytomanageSilverlightonusers'computersthatarerunningWindowsServer2003,WindowsXPwithSP2,orWindowsVista.
ForanoverviewoftheconceptsandarchitectureoftheAdministrativeTemplates,seehttp://go.
microsoft.
com/fwlink/LinkID=29910.
ImportantTheSilverlightcontrol'sAutomaticUpdatepolicycanbesetper-userorper-machine.
Ifanadministratorsetsaper-machinesetting,thenthisoverridestheper-usersetting.
WerecommendthatyoumanageSilverlightbyusingtheAdministrativeTemplatesettingsinGroupPolicywheneverpossiblebecausethesesettingsarealwayswrittentoasecureper-machinekeyintheregistry.
ThismeansthatuserscannotchangesettingsbyusingtheSilverlightuserinterfaceorbymodifyingtheper-userupdatemoderegistrykey.
ADMandADMXfiletemplatesettingsThetextbelowcanbeusedtocreateanADMorADMXfileforSilverlightsettings.
FormoreinformationabouthowtocreateanduseADMorADMXfiles,seethearticles:HowtocreatecustomadministrativetemplatesinWindows2000http://support.
microsoft.
com/kb/323639ManagingGroupPolicyADMXFilesStep-by-StepGuideHowtocreateaCentralStoreforGroupPolicyAdministrativeTemplatesinWindowVistahttp://support.
microsoft.
com/kb/929841ADMfile:CLASSMACHINECATEGORY!
!
SL_PARAMSKEYNAME"HKEY_LOCAL_MACHINE\Software\Microsoft\Silverlight\"POLICY!
!
SET_AUPDATEEXPLAIN!
!
AUPDATE_HELPPART!
!
AUpdateBoxDROPDOWNLISTNOSORTREQUIREDVALUENAMEUpdateModeITEMLISTNAME!
!
AutomaticVALUE"0"NAME!
!
PromptVALUE"1"NAME!
!
DisableVALUE"2"DEFAULTENDITEMLISTENDPARTENDPOLICYENDCATEGORY[strings]SL_PARAMS="Silverlight"SET_AUPDATE="ChangeAutomaticUpdateBehavior"AUPDATE_HELP="Whenthispolicyisenabled,itwillcontroltheSilverlightcontrol'sautomaticupdatebehavior.
Ifthepolicyisdisabled,itwillnotchangethedefaultbehaviorandthecontrolwillupdateautomaticallyovertheinternet.
TheSilverlightcontrol'sautomaticupdatemechanismisindependentofboththeWindowsUpdateandMicrosoftUpdatemechanisms.
Silverlightcanbeconfiguredtouseoneofthreeautomaticupdatemodes:\n\nAutomatic-Automaticallydetects,downloads,andinstallsupdates\nPromptforupdates-Detectswhenanupdateisavailableandpromptsifyouwouldliketodownloadandinstalltheupdate\nTurnoffautoupdates-Doesnotcheckfororautomaticallydownloadupdates.
ThisoptionshouldbeusedinmostcorporateenvironmentsifyouareusingSMS,,softwareupdateservices(SUS),oranotherenterprisesoftwaremanagementsolution.
"AUpdateBox="UpdateMode:"Automatic="Automaticallydownload"Prompt="Promptforupdates"Disable="Turnoffautoupdates"ADMXfile:012ADMLfile:enternamehereenterdescriptionhereSilverlightChangeAutomaticUpdateBehaviorWhenthispolicyisenabled,itwillcontroltheSilverlightcontrol'sautomaticupdatebehavior.
Ifthepolicyisdisabled,itwillnotchangethedefaultbehaviorandthecontrolwillupdateautomaticallyovertheinternet.
TheSilverlightcontrol'sautomaticupdatemechanismisindependentofboththeWindowsUpdateandMicrosoftUpdatemechanisms.
Silverlightcanbeconfiguredtouseoneofthreeautomaticupdatemodes:\n\nAutomatic-Automaticallydetects,downloads,andinstallsupdates\nPromptforupdates-Detectswhenanupdateisavailableandpromptsifyouwouldliketodownloadandinstalltheupdate\nTurnoffautoupdates-Doesnotcheckfororautomaticallydownloadupdates.
ThisoptionshouldbeusedinmostcorporateenvironmentsifyouareusingSMS,,softwareupdateservices(SUS),oranotherenterprisesoftwaremanagementsolution.
UpdateMode:AutomaticallydownloadPromptforupdatesTurnoffautoupdatesUpdateSetting:Registry-basedSilverlightpolicysettingsTheSilverlightcontrol'sautomaticupdatemechanismisindependentofboththeWindowsUpdateandMicrosoftUpdatemechanisms.
Silverlightcanbeconfiguredtouseoneofthreeautomaticupdatemodes:AutoUpdates-Automaticallydetects,downloads,andinstallsupdates.
Thisisthedefaultsettingafteraninstall.
TheclientwillattempttorequestfilesfromMicrosoftatmostonetimeperdaytodetectifthereisanewerversionoftheSilverlightclient.
Ifthereisanewerversion,itwillautomaticallydownloadandinstalltheupdatewithoutanyuserinterventionrequired.
PromptedUpdates-Detectswhenanupdateisavailableandpromptsifyouwouldliketodownloadandinstalltheupdate.
ThisusesthesamedetectionlocationandscheduleastheAutoUpdatesoption.
NoUpdates-Doesnotcheckfororautomaticallydownloadupdates.
ThisoptionshouldbeusedinmostcorporateenvironmentsifyouareusingSMS,softwareupdateservices(SUS),oranotherenterprisesoftwaremanagementsolution.
IfusingtheSilverlightupdateryouwillneedtogivetheclientcomputeraccesstothefollowingdomains:go.
microsoft.
comsilverlight.
dlservice.
microsoft.
comrs.
update.
microsoft.
comslupdate.
dlservice.
microsoft.
comwww.
microsoft.
comThesesettingsareavailableinthecustomADMorADMXfileyoucreatedasreferencedabove.
Theregistrysettingthattheadministrativetemplatefilescontainis:Keypath:HKEY_LOCAL_MACHINE\Software\Microsoft\Silverlight\ValueName:UpdateModeValueType:DWORDValidValues:AutoUpdates0x00000000PromptedUpdates0x00000001NoUpdates0x00000002YoucanlocatethissettinginthefollowingpolicypathforyourGPOs:CategoryDescriptionComputerConfiguration\AdministrativeTemplates\SilverlightContainssettingstoenableordisablestandardSilverlightconfigurations.
Modifyingregistry-basedSilverlightpolicysettingsYoucanmodifytheSilverlightpolicysettingsthatapplytoindividualcomputers.
Tomodifyregistry-basedSilverlightpolicysettings1.
OpenGroupPolicyObjectEditorbyusingoneofthemethodsdescribedintheGroupPolicyproductdocumentation(http://go.
microsoft.
com/fwlink/linkid=67717).
ThemethodyouusewilldependontheGPOthatyouwanttomanage.
OnewaytoopenGroupPolicyObjectEditoristoclickStart,clickRun,andthenenterGpedit.
msc.
2.
Double-clickPolicy,andthendouble-clickComputerConfiguration.
3.
Double-clickAdministrativeTemplates,double-clickWindowsComponents,andthendouble-clickSilverlight.
4.
Intheleftpane,clickthecategoryyouwanttoworkwith,andthenintherightpane,double-clicktheitemthatyouwanttoedit.
5.
ClicktheSettingtab,andthenconfigurethepolicysetting.
TypicalchoicesforasettingareNotConfigured,Enabled,orDisabled.
Somesettingsrequireyoutomakeadditionalselectionsorenteradditionalinformation.
KeepingSilverlightUpdatedAfteryoudeploySilverlightinyourcorporatenetwork,youcanusethefollowingtoolstodistributeupdatedversionsofSilverlighttoyourusers'computers:AutomaticUpdates.
TheSilverlightcontrolincludesanautomaticupdatefeaturewhichwillautomaticallyinstallupdatesonmachinesrunningWindowsoperatingsystem.
TodisableAutomaticUpdatesofSilverlight,seetheadministrativesettingssectionabove.
SoftwareUpdateMethods.
UsesystemupdatemanagementtoolssuchasSystemsManagementServerorthesoftwaredistributioncapabilitiesinGroupPolicytoupdateSilverlightonusers'computers.
AutomaticUpdatesYoucanconfigureSilverlighttoautomaticallyupdateitselfwhileitisinuse.
Everytwenty-fourhours,theversionofSilverlightthatisinstalledonyourusers'browsercomparesitselfagainstthemostcurrentSilverlightversionthatisavailablefordownload.
Iftheversiononthewebisnewerthantheversiononusers'computersthenSilverlightwillautomaticallyupdateitself.
OnWindowsoperatingsystems,thedefaultfunctionalityistoautomaticallyfind,download,andinstallupdates.
Thecontrolcanbeconfiguredtoprompttheuserbeforedownloadingandinstallingupdates.
Alternatively,automaticupdatescanbedisabledasdescribedintheadministrativesettingssectionabove.
NoteYourusersmusthavelocaladministrativeprivilegesontheircomputerstoinstallanupdatedversionofSilverlightonWindowsXPand2003.
However,updatescanbeinstalledtodisablenon-adminpatchingonWindowsVistayoumustusetheDisableLUAPatchingpolicyasdescribedhere:http://msdn2.
microsoft.
com/en-us/library/aa368302.
aspx.
NoteYourusersmusthaveinternetaccesstofindanddownloadupdatesthroughtheSilverlightupdater.
ByusingtheAdministrativeTemplatespolicysettingAutomaticallycheckforSilverlightupdates,youcandisableautomaticchecksforSilverlightupdates.
FormoreinformationaboutchangingtheAutomaticUpdatesettings,seeManagingSilverlightSettingsThroughGroupPolicy.
SoftwareupdatemethodsIfyoualreadymanagesoftwaredistributionandupdatesonyournetworkbyusingSystemsManagementServer(SMS)orGroupPolicySoftwareInstallation,youcanusethesetoolsforongoingdeploymentsofSilverlight.
NoteIfanyoftheseoptionsareused,thebuilt-inautomaticupdatemethodshouldbedisabledasreferencedintheRegistry-basedSilverlightpolicysettingssection.
SystemsManagementServerSMSisadedicated,flexiblesystemtouseforupdatesandsoftwaredeployment.
Itprovidesrobustfeaturestofacilitatescheduling,managing,andreportingforyourSilverlightdistributionsinlarge-scalecorporateenvironments.
FormoreinformationaboutusingSMSforthedistributionofSilverlight,seeUsingSMStoInstallSilverlightinthisdeploymentguide.
SecurityUpdatesforSilverlightwillalsobeavailablethroughtheInventoryToolforMicrosoftUpdates.
Tohelpcustomersdeterminetheupdatecomplianceofmanagedsystem.
ThistoolprovidesintegrationwithupdatesofferedbyWindowsUpdateandMicrosoftUpdate.
FormoreinformationonthistoolseetheSMS2003InventoryToolforMicrosoftUpdatespage.
GroupPolicySoftwareInstallationTheGroupPolicySoftwareInstallationextensionleveragestheWindowsInstallerservicethatispartoftheWindowsoperatingsystem.
Basedonyourinstructions,WindowsInstallerinstalls,repairs,andremovessoftwarein.
msifiles.
TheSilverlightSetupfileisanexecutable(.
exe)file.
Therefore,youmustusean.
msipackagingtooltopackageSilverlightforGroupPolicydeployment.
FormoreinformationabouttheSoftwareInstallationextensionofGroupPolicy,seehttp://go.
microsoft.
com/fwlink/LinkId=83294.
WindowsServerUpdateServices(WSUS)IfyouuseWSUS2.
0SP1orlater,youcancentrallymanagethedistributionofSilverlightupdatestocomputersonyourcorporatenetworkthatarerunning:WindowsServer2003withSP1WindowsXPwithSP2WindowsVistaFormoreinformationaboutusingWSUS,seehttp://go.
microsoft.
com/fwlink/LinkId=45140.
ScriptedorManualIfSMS,WSUS,orGrouppolicyisnotavailableinyourenvironment,itispossibletofollowthemanualprocessyouchoseforyourinitialdeploymentexceptutilizethe/qswitchfortheinstallationexecutablefile.
Byusingthisswitch,itwillallowasilentupgradeofSilverlight.
FormoreinformationaboutthemanualmethodsofdeploymentandinstallationswitchesforSilverlight,seeManualInstalloptionsforSilverlightinthisdeploymentguide.
TroubleshootingThissectionofthedeploymentguideprovidesinformationabouttroubleshootingthedeploymentofSilverlightinacorporateenvironment.
Troubleshootingtopicsarecategorizedintothefollowingareas:SilverlightinstallationanduninstallationDisabilingSilverlightinIE7SilverlightinstallationanduninstallationFollowingarewaystohelpyoutroubleshootinstallinganduninstallingSilverlightonyourusers'computers.
SilverlightInstallprocessfailsIftheinstallfails,youcantroubleshooterrorsbyusingtheSetuplogfiles:SilverlightMSI####.
txt-MSIengineSilverlightUI####.
txt-UIwrapperontopofMSIEachinstallationcreatesalogfile,whichcollectsinformationaboutthatparticularinstallation.
IfaSilverlightlogfilealreadyexists,setuprenamestheexistinglogasa.
bakfileandcreatesanewlogfile.
Whenyoudotheinstall(GUIorcommandline)oruninstallwiththe/quoption,thelogfilesarecreatedinthefolderassociatedwiththe%TEMP%variable(typically,theC:\Windows\Tempfolder).
Thefilesdocumenttheentireprocessfromthemomenttheexestartsrunninguntiltheinstallationoruninstalliscomplete.
TheUIwrapperlogcanbeusefulfortroubleshootinginstallationfailures.
Duringmostinstallationscenariosthislogwillcontainareturncodefortheinstallation.
Thereturncodecanbeusedtodeterminewhetheraninstallationerroroccurredandtogainmoreinformationabouttheerror.
ThereturncodewillbewrittennearthebottomoftheSilverlightUI####.
txtfileandwillbeprecededbythetext"Processreturningcode".
ReturnCodeMeaning0Installationwascompletedsuccessfully1508Installationwascompletedsuccessfully.
However,usersofthemachinemustrestarttheirbrowserinstancestoapplythesechanges.
OtherAninstallationerrorhasoccurred.
TolearnmoreabouttheerroryoushouldvisittheinformationpageforthiserrorbyappendingthereturncodetothefollowingURL:http://go.
microsoft.
com/fwlink/LinkID=87096&errorID=Example:IfyourUIlogfileincludesthelineProcessreturningcode3010Thenyoushouldvisithttp://go.
microsoft.
com/fwlink/LinkID=87096&errorID=3010UnabletouninstallSilverlightInmostcases,youcanuninstallSilverlightonyourusers'computersthatarerunningWindowsXPwithSP2orWindowsServer2003withSP1byusingtheAddorRemoveProgramstoolinControlPanelorinWindowsVistabygoingintoProgramsandFeaturesinControlPanel.
IfyoucannotuseAddorRemoveProgramsorProgramsandFeaturesinControlPaneltouninstallSilverlight,theuninstallinformationmightnotbeonthecomputer.
Re-installthecontroltoreplacetheuninstallinformationandthentryuninstallingagain.
DisablingSilverlightadd-oninInternetExplorer7ToisolatebrowserissuesthatmightberelatedtotheSilverlightadd-on,youcanselectivelydisabletheadd-oninInternetExplorer7.
Todisableabrowseradd-onClicktheToolsmenu,clickManageAdd-ons,andthenclickEnableorDisableAdd-ons.
Changethe"Show"Drop-downboxto"Add-onsthathavebeenusedbyInternetExplorer"ClickAgControlClass,clickDisable,andthenclickOK.
Alternatively,youcanturnoffalladd-onstemporarilyinInternetExplorer7bystartinginNoadd-onsmode.
TostartInternetExplorer7inNoadd-onsmode1.
ClickStart,clickAllPrograms,andthenclickAccessories.
2.
ClickSystemTools,andthenclickInternetExplorer(NoAdd-ons).
NoteYoucanalsostartInternetExplorerwithoutadd-onsbyright-clickingtheInternetExplorericononthedesktopandthenclickingStartWithoutAdd-ons.
OrstartInternetExplorerwithnoadd-onsortoolbarsbyrunningthecommandiexplore.
exe-extoff.