Hi,

I created an executable using the NwSapSetupAdmin.exe and added in the after install script to copy the saplogon.ini file from the CustomerFiles folder within the install. 

Now it successfully installs and puts the correct saplogon.ini file in the correct folder when i install it locally through the exe that was created from the package. However when i upload this exe to the Dell Kace and try to deploy it, the program is installed but the saplogon.ini file is not the correct one and is just the default.

 

Anyways to fix this?

 

Thanks

Answer Summary:
I got it working now. The script was working but wouldn't overwrite an existing saplogon.ini file. I didn't want it to do that so its good. I have a basic saplogon.ini with some default connections that i wanted passed on a fresh install and now its doing that.
Cancel
1 Comment   [ + ] Show Comment

Comments

  • Doesn't that file get copied to the user's profile? If I'm right, then it will of course have been copied to the profile of the local System account. I don't know anything about how KBoxes work to advise you but in your shoes, I'd simply build an MSI containing the INI and deploy that after the main deployment. Make sure that either the second MSI checks that SAPGui is installed or that the KBox does.
Please log in to comment

Answers

2

I always thought that SAPLOGON.INI was one of those files you just didn't inlcude in your package - like TNSNAMES.ORA for Oracle.

Because of the potential need to change the file regularly, there are mechanisms to place for both to redirect the client to a network location that holds the file, making it much easier to update the file - which is the method I've always used.

This would remove the need to package an update to the file, and the messing about with populating it into user profiles in this case.

I believe that you can add an environment variable 'SAP_LOGON_INI_FILE' to point to the UNC path where your saplogon.ini (and sapshortcut.ini if required) is located.

SAP_LOGON_INI_FILE=\\<servername>\<sharename>\saplogon.ini

Hope that helps,

Dunnpy

 

Answered 07/11/2013 by: dunnpy
Red Belt

  • I got it working now.
    The script was working but wouldn't overwrite an existing saplogon.ini file. I didn't want it to do that so its good.
    I have a basic saplogon.ini with some default connections that i wanted passed on a fresh install and now its doing that.

    Thanks for the help!
Please log in to comment
Answer this question or Comment on this question for clarity