Now that we have made the packages available on the network the next step is the deployment itself.
As mentioned, the default installation commands are available in the package properties.

Pre-requisites commands (examples)

KB 907417:
Primary Interop:
Primaryinterop03O2003PIA.MSI /q /l* c:interopoff03.log
Visual J#:
VJSharpinstall.exe /Q

Package Command line installation via Sccm/Sms

Sap installation from the network:
Sap update from the network (synchronizes the installation (whatever package) with the patched server
Sap Uninstall (just in case)
\serversharesapSapgui710SetupNwSapSetup.exe /NODLG /Uninstall /Product=”SAPGUI710″
Upgrading version 640 to version 710
Note that the installation command will take care of removing version 640 of SAP and will install the latest version in one shot.
You do not need to specifically uninstall it first.

Other Scripts that might be useful

If you deployed BW and need to fix the sap plugin path after installation, here is a vbscript to do so:
Set shell=createobject(“”)
Shell.RegWrite Regpath,”C:Program FilesCommon FilesSAP SharedBW”,”REG_SZ”
In order to disable all updates for clients that do not have local admin priviledges:
Set WSshell=createobject(“”)
WSShell.RegWrite “HKEY_LOCAL_MACHINESOFTWARESAPSAPsetupSAPstartAutoUpdateSAPLogon.exeupdatemode”,”ForceOff”
To copy over a customized saplogon.ini
Set WshShell = CreateObject( “WScript.Shell” )
Set Fso = CreateObject(“Scripting.Filesystemobject”)
filesource = “\serversharesapsaplogonsaplogon.ini”
filesource2 = “c:windowssaplogon.ini”
fso.Copyfile filesource, filetarget, True
Set wshshell = nothing
set fso = nothing
If you deploy the packages accross various sites, you will need to update the Sms package once you have created the SAP packages
and made the necessary changes.