Sage 100

Client decided it was time to move away from Server OS 2012 R2.  So I installed v2023 on the new server and ran the Sage migration to bring in the existing 2023.  Straight forward and "easy".  Now I have twenty workstations to point to the new server.  Is there an EASY way to do this?  Change a line or two in a workstation config file?

Text below is from Sage KB.  IT might work.  I don't really want to add, I want to change....

Looking for ideas or a secret sauce process.

TIA

Adding a Server to Existing Workstation:

To add a server to an existing workstation, launch the Install Sage 100 Advanced ERP workstation program from the Sage 100 Advanced server installation folder and click Autorun.exe to run the program. Click Add on the Program Maintenance page and enter the server name, path, and port ID associated with the server you want to add. After Workstation is run, click Finish

You will find server name and Port # in the target field found in the Sage 100 Shortcut properties. 

You will also find Server name, port #, and ODBC Path in the SOTA.INI file found in the MAS90\Launcher directory on the LOCAL workstation folder. Look for the [Servers] and [Active Server} sections. I have changed server name and/or port number in both the shortcut and the .INI file when someone has accidentally typed one of them incorrectly during workstation setup. That has worked flawlessly. 

I have never tried changing all three to just to point to a new server location. In theory, if the version is exactly the same, it should work. But since I have never tried it, take that for what it is worth, I guess. 

Another option would be to use the steps you noted in your post to add a new instance. Doing that will add another line in the "Servers" section of the SOTA.INI file. Then you can just delete the line pointing to the old server. I have actually used that method before. I think you need to launch Sage 100 one time and select the new server path and it will repoint the target in the Shortcut. then edit the INI file.

------------------------------
David Overholt
DWD Technology Group
------------------------------

Thanks.  Very helpful

In my opinion Sage should have always had a utility so you did not have to go workstation to workstation uninstalling and re-installign workstations.

Epilogue - on a few workstations, I added a server, then deleted the old server when I was prompted as to which server to run.  That worked fine for me but created issues when the user started the next AM.  Sage does NOT install a new start icon program when adding a new server.  So it failed when user clicked on the Sage icon.  So I saved a working icon under Sage server folder and copied that to each workstation.  I then edited the sota,.ini file.  I did not copy the sota.ini file to each workstation folder as I was concerned that the sota.ini file might have settings specific to each workstation.  

I do agree with Wayne about the need to install the client.  Maybe that is a small print item in the road ahead.....for 2031!

Edit Add - Remember to change the server name on the ODBC tab in Setup Configuration under library master.  Will save you hours of tail chasing.............

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
------------------------------