Sage 100

🎉 Calling All Sage 100 Wizards! 🧙‍♀️🧙‍♂️

We all have that one Sage 100 upgrade trick that makes us feel like absolute geniuses.
The shortcut... the checklist step… the "trust me, do this first" move we learned the hard way. 😅

We're putting together:

✨ Top 10 Consultant Tricks to Speed Up Sage 100 Upgrades For the 2026 90 Minds Conference✨

and we need YOUR go-to tip - big or small.

Think:

• That one folder you always back up
• The step you never skip before migrating data
• The trick that avoids the "unexpected" surprise screen
• A time-saver that shaves hours off testing

Please post your favorite upgrade hack.
No explanation needed - just share the trick.

Let's help each other look even more brilliant. 😄

In addition, would you like to help present these brilliant tricks?

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]
------------------------------

I owe this to @Jeff Schwenk - make a backup of the MAS90 folder after installation and before migration.  Usually I create the Role and User and then save it. Has saved my butt numerous times AND reinforced the idea the one time I forgot and then had the inevitable fatal migration.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989
------------------------------

For Premium you also want to backup the new install's MAS_System database, before attempting a migration (in addition to the MAS90 folder).  I usually do this after setting up the service, and pre-installing any enhancements, so it is easier to reset / retry after a failed migration attempt.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 10-29-2025 06:36
From: Beth Bowers
Subject: Tricks To Speed Up Sage 100 Upgrades

I owe this to @Jeff Schwenk - make a backup of the MAS90 folder after installation and before migration.  Usually I create the Role and User and then save it. Has saved my butt numerous times AND reinforced the idea the one time I forgot and then had the inevitable fatal migration.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989
------------------------------

This isn't a time saver, yet I consider it essential to an upgrade.  Immediately after the data conversion I print the following reports from the previous and new versions:  AR Aging, AP Aging, GL Detail, Inventory Valuation, Open PO, Open SO.  I compare the reports from the two versions to be sure they agree.  These reports become part of the documentation of the project.  

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

1. This is a duplicate - always backup \MAS90 - ESPECIALLY FOR PREMIUM WHICH CAN UNEXPECTEDLY HOSE YOUR DATA INCLUDING SYSTEM FILES
2. Create MASREG.INI and put that into your c:\ so you don't have to keep re-keying registration codes
3. Create a document called Worklog ( use whatever note taker you prefer ) - make notes in here on what you did each day and on what you need to still do - and then use AI to create summaries of what you accomplished , where you left off and what's next/left to do 
4. Create a cheat sheet with pictures on how to run workstation setup - give this to IT so they can run workstation setup - be sure to go over fixing paperless with file-run-pl_advancedoptions_ui

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

After you have done the final upgrade - create INSTLOCK.TXT and put it in the old systems \MAS90\HOME folder so that someone can't login and enter transactions unexpectedly.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

1. Go to the Windows Control Panel,
2. Select Add and Remove Programs,
3. Highlight the Sage Advisor Update and select Uninstall.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

So appreciative and excited about the responses.  Thank you, looking forward to more.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]
------------------------------

Ahead of time:

• Confirm the Sage 100 administrator password and/or be ready to use the admin pw workaround.
• Perform server analysis, address avail space, clean up as needed

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Original Message:
Sent: 10-30-2025 00:31
From: Michele Herzog
Subject: Tricks To Speed Up Sage 100 Upgrades

So appreciative and excited about the responses.  Thank you, looking forward to more.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]
------------------------------

You can add Firewall entries using a PowerShell script, just edit paths and ports.

Run PowerShell as an admin

 

# Open TCP port 1433 for SQL Server

New-NetFirewallRule -DisplayName "SQL Server (TCP 1433)" -Direction Inbound -LocalPort 1433 -Protocol TCP -Action Allow

 

# Open UDP port 1434 for SQL Server Browser Service

New-NetFirewallRule -DisplayName "SQL Server Browser (UDP 1434)" -Direction Inbound -LocalPort 1434 -Protocol UDP -Action Allow

 

#Open TCP port x for Sage 100 Service

New-NetFirewallRule -DisplayName "Sage 100 (TCP 0724)" -Direction Inbound -LocalPort 9724 -Protocol TCP -Action Allow

 

New-NetFirewallRule -DisplayName "Sage 100 Pvxwin32" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Home\pvxwin32.exe" `

-Action Allow `

-Profile Domain,Private,Public

 

New-NetFirewallRule -DisplayName "Sage 100 Pvxwin64" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Home\pvxwin64.exe" `

-Action Allow `

-Profile Domain,Private,Public

 

 

New-NetFirewallRule -DisplayName "Sage 100 Launch32" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Launcher\Launch32.exe" `

-Action Allow `

-Profile Domain,Private,Public

 

 

New-NetFirewallRule -DisplayName "Sage 100 Launch2016" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Launcher\Launch.2016.exe" `

-Action Allow `

-Profile Domain,Private,Public

------------------------------
Christine Kuhn
Consultant
RKL eSolutions, LLC
------------------------------

• We use SmartSheet template with just about every possible step listed and go through that in advance removing lines that don't apply Example: Remove all references to SQL Install if the upgrade is not Premium. 
• If it is Sage 100 Premium we always install 2 instances of SQL on the initial install.
  • instance 1 is Sage100
  • Instance 2 is Sage Upgrade
  • This saves from having to install the second one prior to upgrading
• We also use MASREG.INI on the C drive - BIG time saver if you need to install multiple versions or have to reinstall
• Have a port naming convention. we use 99 and the last 2 digits of the version (example 9925 if we are installing version 2025)
  • that saves having to look it up or figure it out when installing workstations later
• Put the Sage installation files in a folder close to the MAS90 folder for that version. 
  • or any consistent placement will pay off later.  
• Store paperless office document folders outside the MAS90 directory so they do not need moved on every install
  • I think everyone in 90 minds knows that by now but it is worth mentioning. 
• Copy ACTIVATE.PVX from base install to Term Server Client (if there is one) 
• After upgrading there will be new tasks/options added to role maintenance. Copy the "Administrator" or "all access" role BEFORE you click on all the empty boxes. 
  • You can show that copy without boxes checked to the client/user in charge of role maintenance. They can decide what roles need to be edited for access to the new tasks/options

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655
------------------------------

Original Message:
Sent: 10-30-2025 09:26
From: Christine Kuhn
Subject: Tricks To Speed Up Sage 100 Upgrades

You can add Firewall entries using a PowerShell script, just edit paths and ports.

Run PowerShell as an admin

 

# Open TCP port 1433 for SQL Server

New-NetFirewallRule -DisplayName "SQL Server (TCP 1433)" -Direction Inbound -LocalPort 1433 -Protocol TCP -Action Allow

 

# Open UDP port 1434 for SQL Server Browser Service

New-NetFirewallRule -DisplayName "SQL Server Browser (UDP 1434)" -Direction Inbound -LocalPort 1434 -Protocol UDP -Action Allow

 

#Open TCP port x for Sage 100 Service

New-NetFirewallRule -DisplayName "Sage 100 (TCP 0724)" -Direction Inbound -LocalPort 9724 -Protocol TCP -Action Allow

 

New-NetFirewallRule -DisplayName "Sage 100 Pvxwin32" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Home\pvxwin32.exe" `

-Action Allow `

-Profile Domain,Private,Public

 

New-NetFirewallRule -DisplayName "Sage 100 Pvxwin64" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Home\pvxwin64.exe" `

-Action Allow `

-Profile Domain,Private,Public

 

 

New-NetFirewallRule -DisplayName "Sage 100 Launch32" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Launcher\Launch32.exe" `

-Action Allow `

-Profile Domain,Private,Public

 

 

New-NetFirewallRule -DisplayName "Sage 100 Launch2016" `

-Direction Inbound `

-Program "C:\Sage\MAS90\Launcher\Launch.2016.exe" `

-Action Allow `

-Profile Domain,Private,Public

------------------------------
Christine Kuhn
Consultant
RKL eSolutions, LLC
------------------------------

I used to create one role = "Admin" and assign all access to that role. This stopped being a smart move when Sage also added some functionality options such as not prompting for DTR to the roles. What would happen is for smaller clients they'd all claim they needed to be Admin and add themselves. Then I'd invariably get the call a week later about how Sage suddenly wasn't prompting for the DTR and the upgrade must have broken it.

So now what I do is create one role - "Sage" and label it Sage Consultant. Only that role automatically gets access to everything.

When the client wants to have admin access I will give them all the access with "Admin"  but uncheck those options that change functionality such as  removing the check market from the right to "automatic DTR without prompting"

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

We generally go with three "special" roles for upgrades.  (I avoid "Admin" because it can refer to many different things).

AllAccess = our technical admin role.

AlmostAllAccess = customized version of AllAccess, for the highest level of access for business users.  (No posting from preview, no permission to delete / overwrite Live / Archive company codes...).

A pre-upgrade-version of "AllAccess####" for reference, so anything not checked in that role after the upgrade is new.

I also specifically advise clients to not assign "AllAccess..." type roles to Test companies, because of the system level access included those roles.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 10-30-2025 11:59
From: Wayne Schulz
Subject: Tricks To Speed Up Sage 100 Upgrades

I used to create one role = "Admin" and assign all access to that role. This stopped being a smart move when Sage also added some functionality options such as not prompting for DTR to the roles. What would happen is for smaller clients they'd all claim they needed to be Admin and add themselves. Then I'd invariably get the call a week later about how Sage suddenly wasn't prompting for the DTR and the upgrade must have broken it.

So now what I do is create one role - "Sage" and label it Sage Consultant. Only that role automatically gets access to everything.

When the client wants to have admin access I will give them all the access with "Admin"  but uncheck those options that change functionality such as  removing the check market from the right to "automatic DTR without prompting"

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

if you don't use @Wayne Schulz INSTLOCK.TXT tip, change the panel (or outline color for the old install (RED usually gets some attention). 

Depending on the time between the initial migration and the go-live, I just copy the MAS_xxx folder from the prior Sage to the new Sage and convert.  I also copy the PDF log tables for go-live.  And a server change is involved, I use @David Speck II utility for changing pdf paths.  And I never put the paperless folders at or below the MAS90 folder (For early installs, I did - Lesson learned). 

For new installations, I use Report Manager to create reports in the MAS_System\Reports folder (do this before users start printing so the various report tables don't use the default \MAS90\Reports).  This folder is where I modify the master Crystal templates.  I am not a fan of using the \MAS_xxx\reports folder for modifications.  Gets too messy for me.  By using MAS_System (or \MAS_xxx\reports folder), you eliminate the possibility of having a PU wipe out the mods if they are stored in  this folder.

Only install Crystal Designer on the server so that users can't click on the design button to create new forms in the MAS_xxx by accident.  Also, set permissions to not display the Designer button.

Send an email out to everyone with the "What's New URL" link.

@David Overholt, for port naming convention, I use Sage internal name (Version 7.4.x) in my number (9740, 9730, etc).

For workstation client installs, I insert full release name in the path to keep things tidy

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

Improving bottom lines for over 25 years!
------------------------------

Original Message:
Sent: 10-30-2025 11:59
From: Wayne Schulz
Subject: Tricks To Speed Up Sage 100 Upgrades

I used to create one role = "Admin" and assign all access to that role. This stopped being a smart move when Sage also added some functionality options such as not prompting for DTR to the roles. What would happen is for smaller clients they'd all claim they needed to be Admin and add themselves. Then I'd invariably get the call a week later about how Sage suddenly wasn't prompting for the DTR and the upgrade must have broken it.

So now what I do is create one role - "Sage" and label it Sage Consultant. Only that role automatically gets access to everything.

When the client wants to have admin access I will give them all the access with "Admin"  but uncheck those options that change functionality such as  removing the check market from the right to "automatic DTR without prompting"

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

Make sure IT has installed Windows updates prior to the install date.

If this is still relevant, have IT install  the appropriate .Net Framework ahead of time.

Make sure you have the Sage Administrator password of the old version.

------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
------------------------------

Original Message:
Sent: 10-30-2025 12:57
From: Jeff Schwenk
Subject: Tricks To Speed Up Sage 100 Upgrades

if you don't use @Wayne Schulz INSTLOCK.TXT tip, change the panel (or outline color for the old install (RED usually gets some attention). 

Depending on the time between the initial migration and the go-live, I just copy the MAS_xxx folder from the prior Sage to the new Sage and convert.  I also copy the PDF log tables for go-live.  And a server change is involved, I use @David Speck II utility for changing pdf paths.  And I never put the paperless folders at or below the MAS90 folder (For early installs, I did - Lesson learned). 

For new installations, I use Report Manager to create reports in the MAS_System\Reports folder (do this before users start printing so the various report tables don't use the default \MAS90\Reports).  This folder is where I modify the master Crystal templates.  I am not a fan of using the \MAS_xxx\reports folder for modifications.  Gets too messy for me.  By using MAS_System (or \MAS_xxx\reports folder), you eliminate the possibility of having a PU wipe out the mods if they are stored in  this folder.

Only install Crystal Designer on the server so that users can't click on the design button to create new forms in the MAS_xxx by accident.  Also, set permissions to not display the Designer button.

Send an email out to everyone with the "What's New URL" link.

@David Overholt, for port naming convention, I use Sage internal name (Version 7.4.x) in my number (9740, 9730, etc).

For workstation client installs, I insert full release name in the path to keep things tidy

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

Improving bottom lines for over 25 years!
------------------------------


Original Message:
Sent: 10-30-2025 11:59
From: Wayne Schulz
Subject: Tricks To Speed Up Sage 100 Upgrades

I used to create one role = "Admin" and assign all access to that role. This stopped being a smart move when Sage also added some functionality options such as not prompting for DTR to the roles. What would happen is for smaller clients they'd all claim they needed to be Admin and add themselves. Then I'd invariably get the call a week later about how Sage suddenly wasn't prompting for the DTR and the upgrade must have broken it.

So now what I do is create one role - "Sage" and label it Sage Consultant. Only that role automatically gets access to everything.

When the client wants to have admin access I will give them all the access with "Admin"  but uncheck those options that change functionality such as  removing the check market from the right to "automatic DTR without prompting"

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut

Probably a large number of people are already doing this - just an FYI for anyone who hasn't started/considered it.

For my upgrades I use Google Docs and one tab is "Work Log" where every time I do some work on the upgrade I write down exactly what I did. My customers tend to have all sorts of delays and changes and if I don't write down what I've done when I go to pick the work up in a week ( or a month ) I'll have no idea where I left off. This is also handy when you have multiple people working on an upgrade. And using Google Docs is pretty inexpensive and Gemini AI is typically an included capability.


That is tip number 1 - create a work log section in your upgrade documentation.

Then the second tip is use AI to adds to your documentation: 

I'm frequently using AI to tell me how to perform tasks on the server or with a Windows feature. After I've gotten the answer I tell AI "Please document this in a concise writeup for my notes" then I copy and paste into my work log. This (theoretically) makes going back to see what you did in past days/months much easier.

And as an added bonus if the client asks for a report of what you've done -- just copy and paste your work log and ask AI to create a summary where the level of detail can be adjusted based on where you are sending that report to -- ie a non-technical owner can get a very high level overview, while IT can get a more technical summary while the production manager who does double duty as the IT Administrator but isn't really technically advanced can get a step-by-step listing for their notes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

Not really a time-saver, but (re-)visiting various Module setup options could be beneficial, e.g. new S/O and P/O audit functionality as well as other existing data retention settings, which of course could contribute to using up a decent amount of space.

(@Jim Woodhead)

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Original Message:
Sent: 11-03-2025 11:18
From: Wayne Schulz
Subject: Tricks To Speed Up Sage 100 Upgrades

Probably a large number of people are already doing this - just an FYI for anyone who hasn't started/considered it.

For my upgrades I use Google Docs and one tab is "Work Log" where every time I do some work on the upgrade I write down exactly what I did. My customers tend to have all sorts of delays and changes and if I don't write down what I've done when I go to pick the work up in a week ( or a month ) I'll have no idea where I left off. This is also handy when you have multiple people working on an upgrade. And using Google Docs is pretty inexpensive and Gemini AI is typically an included capability.


That is tip number 1 - create a work log section in your upgrade documentation.

Then the second tip is use AI to adds to your documentation: 

I'm frequently using AI to tell me how to perform tasks on the server or with a Windows feature. After I've gotten the answer I tell AI "Please document this in a concise writeup for my notes" then I copy and paste into my work log. This (theoretically) makes going back to see what you did in past days/months much easier.

And as an added bonus if the client asks for a report of what you've done -- just copy and paste your work log and ask AI to create a summary where the level of detail can be adjusted based on where you are sending that report to -- ie a non-technical owner can get a very high level overview, while IT can get a more technical summary while the production manager who does double duty as the IT Administrator but isn't really technically advanced can get a step-by-step listing for their notes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------