Hello all,
We currently use a classic SAP Frontend Installation Server to distribute SAPGUI to users, but to date it has resided on a multi-function server and we are now looking to migrate it to a dedicated server. We're not currently using logon scripts nor SMS to push the installations, as most users have got it installed at this point and it's easy enough to run the nwsapsetup command when someone gets a new workstation or a new employee is hired who needs the software.
So, my question is, what works best for automating the process of migrating all those existing SAPGUI installations to point to the new installation server location for patches, etc? If possible, I'd prefer to avoid adding it to a logon script. I had thought that I could add the new server location as an additional indexed server in the old server's configuration, as it seemed to me that then existing clients would pick up that a newer patch level was available in the new location and update from there, at which point the new location would be recorded in their registry. However, that appears to not work as I expected. I even tried updating the 'package revision level' on the old server to trigger a client update, which it did, but in the update it appears that the client didn't actually get the new indexed server location.
So, I'm still experimenting with this, but if anyone has a brilliant solution, I'd love to hear it. Otherwise, I may just have to tell all the users to manually run an update from the new server.
Regards,
Matt
