For more information about the process of deploying Sap 7 with a server installation, see my previous post:
SAP 710
Some changes:
First thing first, if you use Windows 7 to try to install the server via NwCreateInstServer,
you will need to run the command with elevated priviledges otherwise you will get an error
straight at decompression time… Just open an elevated command prompt and run the command from there.
The sap server install follows the same process as version 710.
Note that the registry path for SAP.BusinessExplorer.Analyzer seems to be correct now, so no need
to patch it via script after install.
If you want to deploy a customized saplogon.ini at install time, just create a folder at the root of
your installation files named ‘custom’ and place your saplogon.ini file there.
(note that the documentation specifies the folder must be named CustomerFiles but this is not correct !) .
This file will replace any existing saplogon.ini, so if you want to keep some customizations for specific users,
you will have to make a backup first. (this could be made via a custom sap script or any other tool you are
comfortable with).
Note also that user path to saplogon.ini has changed. The saplogon will first be copied to the machine path,
%Windir%, then will be copied over to the user directory, %APPDATA%\\SAPCommon (see note 1409494
for more information).
You could alternatively use a dedicated network saplogon.ini and point your clients to it
via the /Ini_file switch (see note 1426178).
Pre-requisites seem to be the same as before, ie the latest visual J#, and the Pias for your version of Office
Note that the Primary Interop for Office 2010 will only be shipped at RTM time (very soon indeed).*
Also, Net Framework 2 should now be readily available on most computers now.
I made tests with both version 640 and 710 and the install of v720 upgrades both versions without apparent problem.
There is a way to install updates automatically when the server gets patched. This might be a good thing, depending on your environment.
As I can use Sccm to deploy the updates when i want, i choose not to use this service. One effect of auto-updates is that it becomes more difficult to test the updates on some computers before deploying on the whole user base, but you might have a look at it if you don’t have a dedicated management platform for your clients.
* Note that at RTM, Office 2010 installs by default the Primary Interop Assemblies (Pias).