I am hoping someone can shed some light on this. So, I have an application that that i am trying deploy to a test computer before.
Posted by1 year ago
Archived
I wish I never started, but I am looking at deploying SAP GUI 7.5 on behalf of our SAP team. They don't have much experience with this (and I have no SAP experince), so there is a lot of re-inventing the wheel going on.
To make a long story shorter, from what I have learnt over the past few weeks, rolling out isn't straight forward at all, and we need to use .ini files, which are currently placed in the c:windows folder (I though MS stopped recommending that practice with Windows 95?) to store the connection details.
So I have made an 'installation server', and created a 'package' consisting of SAP GUI 7.5 (without the Outlook add-in, which failed to install), and Business Explorer.
The problem is, because we can't use 'landscapeUI' format connection files (due to the version of SAP on the backend?), we need to use the legacy .ini files. I can't use the existing set supplied by the SAP team beacuse they are full of pointers to the local profile on the local PC. Running saplogon.exe with the /ini_file switch doesn't seem to create the saplogon.ini file (I have tried a local path and a server path). If I look on the 'properties' page of the package, I can see a variable called 'sapgui.landscapefromatenabled' which is set to 1, but I can't modify it. if I go to 'package configuration', it just is not listed.
So, any suggestions on how to get the package to use/create the .ini files?
While I am here, are there any issues with trying to run SAP GUI (the client, or the tools) on Windows 10?
8 comments