SAPGUI 7 Sap deployment and shortcuts
Hi,
I followed the SapFront End Installation guide to create a silent installlation package.
The clientdoes not like the shortcuts being separate in 2 folders under the star menu (Business Explorer- Front End) I looked at the SAPSetup Installation Tool and i could not find anywhere something that let me set where i want the shortcuts to be.
Is it hidden and does it exists? Otherwise, i will have to move them externally from the install process which is something i would like to avoid.
Thanks for your help,
I followed the SapFront End Installation guide to create a silent installlation package.
The clientdoes not like the shortcuts being separate in 2 folders under the star menu (Business Explorer- Front End) I looked at the SAPSetup Installation Tool and i could not find anywhere something that let me set where i want the shortcuts to be.
Is it hidden and does it exists? Otherwise, i will have to move them externally from the install process which is something i would like to avoid.
Thanks for your help,
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
ORIGINAL: unreal2meOr you could do 'the decent thing' and capture it to an MSI. Much more flexible...I know this app is a real clunker but, in the long run, an MSI will serve you better than faffing about with the vendor's install.
Is it hidden and does it exists? Otherwise, i will have to move them externally from the install process which is something i would like to avoid.
Posted by:
Lindeberg IT
15 years ago
I disagree:)
The number of .NET framework components in the package make it more than a hassle; besides, the reason for (re)packaging is to simplify desktopmanagement and reduce the TCO. Modifying the shortcuts can be done by the scriptevents in the Configure Package section of the Server Administration Tool. Here you can add a vbs script or even execute a configuration MSI you have made with the necessary changes
The number of .NET framework components in the package make it more than a hassle; besides, the reason for (re)packaging is to simplify desktopmanagement and reduce the TCO. Modifying the shortcuts can be done by the scriptevents in the Configure Package section of the Server Administration Tool. Here you can add a vbs script or even execute a configuration MSI you have made with the necessary changes
Posted by:
AngelD
15 years ago
Posted by:
My Name Is Earl
15 years ago
I never thought I'd say this but I actually like the SAP-7 designed installed method. It allows for patches, of which there are many, to be applied quickly to the base install and then deployed to the clients.
As far as I am aware (please correct me if I'm wrong), if you packaged SAP-7 as a MSI, you'd have to repackage the base SAP client AND any patches before removing / re-installing the whole thing. The SAP install process means we can just apply the patch to the base install we have on a server. Then force the advert to re-run on the PC's to start the SAP NWSETUP program which checks the base install on the server, recognises there is a difference and applies the updates.
As I said, I never thought I'd ever defend SAP on anything but in the case of their package / deployment system it just works.
As far as I am aware (please correct me if I'm wrong), if you packaged SAP-7 as a MSI, you'd have to repackage the base SAP client AND any patches before removing / re-installing the whole thing. The SAP install process means we can just apply the patch to the base install we have on a server. Then force the advert to re-run on the PC's to start the SAP NWSETUP program which checks the base install on the server, recognises there is a difference and applies the updates.
As I said, I never thought I'd ever defend SAP on anything but in the case of their package / deployment system it just works.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.