Deploying Sap to client computers consists of two main parts: the first one is installing a Sap Network Component

Installing the Network Sap Server

The Sap Server but can be just a Network Share, so you don’t need to dedicate a server for this. To give you an idea of space requirements,
a simple network install of SAP 710 without additional products takes less than 900 MB (down from 1.2 GB for Sap 640).
Follow the Sap Front-End installation Guide and you will end up with a network share that contains all you need
to deploy SAP to your clients.
Once you have the share available, you need to choose which components you want to deploy.
Launch \serversharesapgui710setupNwSapSetupAdmin.exe and choose New Package (see par 3.6 on how to create Packages)
The first time you launch the executable get a .Net error message stating that SapsetupAdmin needs .Net Configuration in order to continue.
In order to solve the problem, the updated version of the installation proposes you to run a Caspol command in order to Trust the executables
in the path you selected.
Make sure you connect to your share via a UNC path at all times, otherwise you could get other prompts when connecting
via different Drive letters ! The former version of the install explains you how to do this manually. Following the steps should get rid of the problem
(note that you will need to apply the changes to each workstation from where you will need to administer your Sap install server,
but not on the client workstations).

Create and customize an installation Package

Once connected with the administration tool, you create packages which are ‘links’ to the components that you want to install.
This allows you to customize different packages to different target collections, while keeping only one source.
This means that when you patch the server, all packages will use the updated source, and computers having received the package
can ‘synchronize’ with the network share to get the patches applied if needed.
You could compare this to creating a MST file for an MSI package. You can add and remove packages or make changes to the MST
without impacting the original sources or other packages.
In order to apply patches to your network installation, connect with the admin tool, choose Patch Server and point to
the executable containing the patches required.
Once you have ‘built’ the package you can customize the application. Click on Packages, Configure Packages.
Here you can change the application defaults like installation path, etc via the Configure Parameters menu.
You could also use Script Events to apply settings at install time.

One thing that I do here is disable updates for the users. In the ‘On End Install’ tab, insert this script:

NwEngine.Shell.SetRegValue “HKLMSOFTWARESAPSAPsetupSAPstartAutoUpdateSAPLogon.exeUpdateMode”, “REG_SZ”, “ForceOff”

This will disable the automatic updates for the client. This is required if your client does not have admin priviledges on the computer and / or
if you want to control when Sap updates are being synchronized on the client (this allows you to test the patches before deployment to your collections).


Now you are -nearly- ready to deploy the package to your collection. You can test the deployment manually by launching the
application that appears on the Properties tab of your package. It should look like this:

\servershareinstallsapsapgui710SetupNwSapSetup.exe /Silent /Package=”SAPR3″

BW Prerequisites and Patch for Excel Plugin

If you plan to deploy Business Warehouse you will need to deploy pre-requisites to the client computers first.

.Net Framework 2.0

Primary Interop for Office 2003 (we didn’t test BW with Office 2007 yet)
KB 907417
Visual J#

One additional fix that we had to apply in order to have the Excel Plugin launch properly is to add this line in the Script Events ‘On end Install tab’

NwEngine.Shell.SetRegValue “HKLMSOFTWAREClassesSAP.BusinessExplorer.Analyzerpath”, “REG_SZ”, “C:Program FilesCommon FilesSAP SharedBW”

This problem only occured on some machines but the workaround ensures that all machines can use it without problem.

Now we are ready to install the packages via SMS / SCCM. This will be the second part of this post.