<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Massive update for SAPGUI in Additional Q&amp;A</title>
    <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540881#M106420</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I would suggest that you setup a server for the configuration files. it is easier to handle the ini files in case of massive roll-out &lt;/P&gt;&lt;P&gt;The steps are outlines in note SAP note &lt;A class="active_link" href="https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001426178"&gt;1426178&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;P&gt;SDN NW Clients Moderator&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Jun 2013 12:54:11 GMT</pubDate>
    <dc:creator>former_member194094</dc:creator>
    <dc:date>2013-06-12T12:54:11Z</dc:date>
    <item>
      <title>Massive update for SAPGUI</title>
      <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaq-p/9540878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We need to update the entries of our SAPGUI´s because the IP addresses of the server will be changed. How can we apply the massive change of the SAPLOGON.ini to over 1000 PC´s with some SAP tool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jun 2013 21:41:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaq-p/9540878</guid>
      <dc:creator>former_member153625</dc:creator>
      <dc:date>2013-06-11T21:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: Massive update for SAPGUI</title>
      <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540879#M106418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The most obvious tool would be to use the SAPgui Installation Server to distribute the changes and keep all your clients up-to-date automatically with the workstation update service. I've also seen people use Windows AD group policies to do it or a combination of both.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nelis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 06:12:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540879#M106418</guid>
      <dc:creator>nelis</dc:creator>
      <dc:date>2013-06-12T06:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: Massive update for SAPGUI</title>
      <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540880#M106419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt; It easy way to do in the VB Script, Just execute the script in the batch file&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;VB Script&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Find command enters&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;intLineFinder = InStr(strNextLine, "Old IP")&lt;/P&gt;&lt;P&gt;intLineFinder1 = InStr(strNextLine, "Old IP")&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Replace command&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;strNextLine = Replace(strNextLine,"(Old IP)","(New IP)")&lt;/P&gt;&lt;P&gt;_____________________________________________&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Const ForReading = 1&lt;/P&gt;&lt;P&gt;Const ForWriting = 2&lt;/P&gt;&lt;P&gt;Set oShell = CreateObject( "WScript.Shell" )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'Set the target file and backup directory.&lt;/P&gt;&lt;P&gt;'Note that I've used an environment variable here to ensure it works on all systems.&lt;/P&gt;&lt;P&gt;'&lt;/P&gt;&lt;P&gt;targfile=oShell.ExpandEnvironmentStrings("%SystemRoot%") + "\saplogon.ini"&lt;/P&gt;&lt;P&gt;backdir=oShell.ExpandEnvironmentStrings("%TEMP%") + "\"&lt;/P&gt;&lt;P&gt;Set objFSO = CreateObject("Scripting.FileSystemObject")&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'Make sure the file exists to prevent errors.&lt;/P&gt;&lt;P&gt;'&lt;/P&gt;&lt;P&gt;if objFSO.FileExists(targfile) then&lt;/P&gt;&lt;P&gt;'Copy it to the backup directory then open the file.&lt;/P&gt;&lt;P&gt;objFSO.CopyFile targfile, backdir, true&lt;/P&gt;&lt;P&gt;Set objTextFile = objFSO.OpenTextFile(targfile, ForReading)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'Read through each line of the file for the entry you want to set&lt;/P&gt;&lt;P&gt;'&lt;/P&gt;&lt;P&gt;Do Until objTextFile.AtEndOfStream&lt;/P&gt;&lt;P&gt;strNextLine = objTextFile.Readline&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;intLineFinder = InStr(strNextLine, "Old IP")&lt;/P&gt;&lt;P&gt;intLineFinder1 = InStr(strNextLine, "Old IP")&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If intLineFinder &amp;lt;&amp;gt; 0 Then&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'Set your new entry here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'&lt;/P&gt;&lt;P&gt;strNextLine = Replace(strNextLine,"Old IP","New IP")&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;End If&lt;/P&gt;&lt;P&gt;If intLineFinder1 &amp;lt;&amp;gt; 0 Then&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'Set your new entry here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'&lt;/P&gt;&lt;P&gt;strNextLine = Replace(strNextLine,"Old IP","New IP")&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;End If&lt;/P&gt;&lt;P&gt;strNewFile = strNewFile &amp;amp; strNextLine &amp;amp; vbCrLf&lt;/P&gt;&lt;P&gt;Loop&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;objTextFile.Close&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'Write the file with the new entry&lt;/P&gt;&lt;P&gt;'&lt;/P&gt;&lt;P&gt;Set objTextFile = objFSO.OpenTextFile(targfile, ForWriting)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;objTextFile.WriteLine strNewFile&lt;/P&gt;&lt;P&gt;objTextFile.Close&lt;/P&gt;&lt;P&gt;End If&lt;/P&gt;&lt;P&gt; __________________________________________________________________________&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Sriram&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 09:00:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540880#M106419</guid>
      <dc:creator>S_Sriram</dc:creator>
      <dc:date>2013-06-12T09:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: Massive update for SAPGUI</title>
      <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540881#M106420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I would suggest that you setup a server for the configuration files. it is easier to handle the ini files in case of massive roll-out &lt;/P&gt;&lt;P&gt;The steps are outlines in note SAP note &lt;A class="active_link" href="https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001426178"&gt;1426178&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;P&gt;SDN NW Clients Moderator&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 12:54:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540881#M106420</guid>
      <dc:creator>former_member194094</dc:creator>
      <dc:date>2013-06-12T12:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: Massive update for SAPGUI</title>
      <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540882#M106421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aldo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Installation Server is a great option.&amp;nbsp; Your Active Directory Administrators will want control.&amp;nbsp; We have uniqueue saplogon.ini files for regulating Business Unit access and Technical development.&amp;nbsp; Our solution leveraged a free tool called Autoit and built a wrapper for deploying just the saplogon.ini as it is changing constantly.&amp;nbsp; &lt;SPAN class="st"&gt;&lt;EM&gt;AutoIt&lt;/EM&gt; is a freeware BASIC-like scripting language designed for automating the Windows GUI and general purpose scripting.&lt;/SPAN&gt; (&lt;A href="http://www.autoitscript.com/site/autoit/"&gt;http://www.autoitscript.com/site/autoit/&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan Mead&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 17:38:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540882#M106421</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-06-12T17:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Massive update for SAPGUI</title>
      <link>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540883#M106422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another option is to have such a file stored on a central server. Then you only need to update the server and all clients will be "updated" at once.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note describing this feature&lt;/P&gt;&lt;P&gt;&lt;A href="https://service.sap.com/sap/support/notes/1426178" title="https://service.sap.com/sap/support/notes/1426178"&gt;https://service.sap.com/sap/support/notes/1426178&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 13:24:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/additional-q-a/massive-update-for-sapgui/qaa-p/9540883#M106422</guid>
      <dc:creator>fredrik_borlie</dc:creator>
      <dc:date>2013-06-24T13:24:15Z</dc:date>
    </item>
  </channel>
</rss>

