Sage 100

I must move Sage 100 over to a new server. The Sage 100 version is staying the same on the new server. The old and new servers are not on the same domain and the SQL server databases are different. I have tried this several diverse ways to do this install and because the old SQL server cannot talk to the new SQL server because they are not on the same domain and hit a roadblock and cannot finish the parallel migration wizard because it stops when it cannot verify the connection between the two servers. I was informed by Sage the old SQL server must be able to talk to the new SQL server but neither IT group is going to adjust these provisions because they are not on the same domain. I am not strong in SQL and only know how to do the basic stuff backups and restores.  I do not understand which set of directions I need to follow when from the Knowledge Base if it's two different servers and SQL server databases. Every person at Sage gives me a separate set of instructions to follow to get this completed. I'm at my wits end and feel defeated at this point. Is the merge method for Sage 100 Premium going to help me in this situation? Please help!

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

We recently had to migrate a customer without having direct access to the source server. 
The quick and dirty process that worked for us is this. 
Disclaimer: I'm not sure if this is a supported way of moving Sage Premium, but we got it to work.

- Install Sage 100 Premium (Same Year/Edition/PU) on the new server <-- Important.
- Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation)
- Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM)
- Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless

These are just the major steps, but the general process should work.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

You mentioned re-associate MAS_USER and MAS_REPORTS would I do this inside of Sage? I see the folders in the old MAS90 installation. 


------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

Original Message:
Sent: 07-23-2022 02:44
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

We recently had to migrate a customer without having direct access to the source server.
The quick and dirty process that worked for us is this.
Disclaimer: I'm not sure if this is a supported way of moving Sage Premium, but we got it to work.

- Install Sage 100 Premium (Same Year/Edition/PU) on the new server <-- Important.
- Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation)
- Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM)
- Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless

These are just the major steps, but the general process should work.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

Yes after the installation, you would need to bring in a BAK of both MAS_SYSTEM and MAS_XXX and restore them replacing the existing MAS_SYSTEM. 

Ultimately you still need to end up with only one MAS_SYSTEM DB. 

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

Original Message:
Sent: 07-23-2022 08:01
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Question - so when I do the Sage 100 install again I want it to create it's own mas_system in SQL? Then detach that mas_system database and then restore the original mas_system and company codes in SQL from the old server?

You mentioned re-associate MAS_USER and MAS_REPORTS would I do this inside of Sage?

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-23-2022 02:44
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

We recently had to migrate a customer without having direct access to the source server.
The quick and dirty process that worked for us is this.
Disclaimer: I'm not sure if this is a supported way of moving Sage Premium, but we got it to work.

- Install Sage 100 Premium (Same Year/Edition/PU) on the new server <-- Important.
- Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation)
- Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM)
- Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless

These are just the major steps, but the general process should work.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |

Thank you George! This worked!

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

Original Message:
Sent: 07-23-2022 10:50
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Yes after the installation, you would need to bring in a BAK of both MAS_SYSTEM and MAS_XXX and restore them replacing the existing MAS_SYSTEM. 

Ultimately you still need to end up with only one MAS_SYSTEM DB. 

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------


Original Message:
Sent: 07-23-2022 08:01
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Question - so when I do the Sage 100 install again I want it to create it's own mas_system in SQL? Then detach that mas_system database and then restore the original mas_system and company codes in SQL from the old server?

You mentioned re-associate MAS_USER and MAS_REPORTS would I do this inside of Sage?

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-23-2022 02:44
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

We recently had to migrate a customer without having direct access to the source server.
The quick and dirty process that worked for us is this.
Disclaimer: I'm not sure if this is a supported way of moving Sage Premium, but we got it to work.

- Install Sage 100 Premium (Same Year/Edition/PU) on the new server <-- Important.
- Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation)
- Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM)
- Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless

These are just the major steps, but the general process should work.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |

Great to hear Shannon! 
Sounds like you're back on track :) 

Cheers!

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

Original Message:
Sent: 07-23-2022 14:30
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Thank you George! This worked!

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-23-2022 10:50
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Yes after the installation, you would need to bring in a BAK of both MAS_SYSTEM and MAS_XXX and restore them replacing the existing MAS_SYSTEM. 

Ultimately you still need to end up with only one MAS_SYSTEM DB. 

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-23-2022 08:01
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Question - so when I do the Sage 100 install again I want it to create it's own mas_system in SQL? Then detach that mas_system database and then restore the original mas_system and company codes in SQL from the old server?

You mentioned re-associate MAS_USER and MAS_REPORTS would I do this inside of Sage?

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-23-2022 02:44
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

We recently had to migrate a customer without having direct access to the source server.
The quick and dirty process that worked for us is this.
Disclaimer: I'm not sure if this is a supported way of moving Sage Premium, but we got it to work.

- Install Sage 100 Premium (Same Year/Edition/PU) on the new server <-- Important.
- Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation)
- Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM)
- Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless

These are just the major steps, but the general process should work.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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

Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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

Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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

Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Not wanting to put words in someone else's mouth, but yes.  (Think about it, you need forms, customized panels, all the system stuff that is not in SQL tables like ALE files...).

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

Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Yes.  I understand.  I am concerned about files that have path, drive letters, or server names that may have changed.

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

Original Message:
Sent: 07-25-2022 13:18
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Not wanting to put words in someone else's mouth, but yes.  (Think about it, you need forms, customized panels, all the system stuff that is not in SQL tables like ALE files...).

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


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

That is the "fun" part.  The SQL Settings utility can help with a new SQL server / instance, but everything else you'd be handling manually (like Paperless paths).

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

Original Message:
Sent: 07-25-2022 13:31
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Yes.  I understand.  I am concerned about files that have path, drive letters, or server names that may have changed.

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


Original Message:
Sent: 07-25-2022 13:18
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Not wanting to put words in someone else's mouth, but yes.  (Think about it, you need forms, customized panels, all the system stuff that is not in SQL tables like ALE files...).

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


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Doug, you're correct. 
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely. 

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname. 

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration). 

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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

Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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

Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Along those lines, I know it has been mentioned from time to time but:

How about making the need to install the service for Sagecrm OPTIONAL - for when we don't know the windows passwords....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------

Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

YES!!!!!!!!!!!!!!!!!!!!!!!!!

------------------------------
Beth Bowers
Mom to Peanut, ChiChi, Canton, Cagney and Daisy (I miss you, Sammy)
Tennessee Software Solutions
(269) 358-0989
------------------------------

Original Message:
Sent: 07-25-2022 16:46
From: Jeff Fiddelman
Subject: Sage 100 Premium move to brand new server on different domain

Along those lines, I know it has been mentioned from time to time but:

How about making the need to install the service for Sagecrm OPTIONAL - for when we don't know the windows passwords....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

If I don’t have a user and password just add a local user and set the password in computer management. But I totally agree that it would be nice to skip the SAGECRM integration.

---------------------------------
Jim Woodhead
DSD Business Systems
619-990-3946
---------------------------------



Original Message:
Sent: 07-25-2022
From: Beth Bowers
Subject: RE: Sage 100 Premium move to brand new server on different domain

YES!!!!!!!!!!!!!!!!!!!!!!!!!

------------------------------
Beth Bowers
Mom to Peanut, ChiChi, Canton, Cagney and Daisy (I miss you, Sammy)
Tennessee Software Solutions
(269) 358-0989
------------------------------


Original Message:
Sent: 07-25-2022 16:46
From: Jeff Fiddelman
Subject: Sage 100 Premium move to brand new server on different domain

Along those lines, I know it has been mentioned from time to time but:

How about making the need to install the service for Sagecrm OPTIONAL - for when we don't know the windows passwords....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Tomorrow's Sage Roundtable webinar is a great way to hear from / communicate directly with the Dev team, and so is MOTM.  Support is what it is... that is not the path to any long term improvements in the product.
(I started an email chain with Elliott P. in March about Premium upgrade issues, and he says they are looking at making changes... no guarantees, but the more voices are singing the same song, the more likely they will hear us).

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

Original Message:
Sent: 07-26-2022 19:47
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Thank you @Kevin Moyes, I will be there! ​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

Original Message:
Sent: 07-26-2022 19:57
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Tomorrow's Sage Roundtable webinar is a great way to hear from / communicate directly with the Dev team, and so is MOTM.  Support is what it is... that is not the path to any long term improvements in the product.
(I started an email chain with Elliott P. in March about Premium upgrade issues, and he says they are looking at making changes... no guarantees, but the more voices are singing the same song, the more likely they will hear us).

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


Original Message:
Sent: 07-26-2022 19:47
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

I have another question on moving premium 2020 to a new server and new version of SQL.  Customer needs to also upgrade premium version to 2022 on the new server and it's on a different domain. I just need someone to review if I have my steps correct:

1.  Install Sage 100 Premium (Same Year/Edition/PU) on the new server.
2. Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation).
3.  Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM).
4. Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless.
5. Install a newer version of Sage 100 Premium (2022) on new server.
6. Install another version of SQL that supports Sage 100 Premuim 2022.
7. Run the parallel migration tool from within v2022 to upgrade the software.

Is this the best practice to do a premium upgrade or is there a better recommendation?

@Kevin Moyes @George Khairallah​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------

Original Message:
Sent: 07-27-2022 07:33
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Thank you @Kevin Moyes, I will be there! ​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-26-2022 19:57
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Tomorrow's Sage Roundtable webinar is a great way to hear from / communicate directly with the Dev team, and so is MOTM.  Support is what it is... that is not the path to any long term improvements in the product.
(I started an email chain with Elliott P. in March about Premium upgrade issues, and he says they are looking at making changes... no guarantees, but the more voices are singing the same song, the more likely they will hear us).

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


Original Message:
Sent: 07-26-2022 19:47
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

@Shannon Stanley I would rely more on @Kevin Moyes and others' guidance regarding the "best practice" aspect.
My description of this process is what works best for us, especially when we have no direct network access to the source Sage 100 installation.

With that said, I just want to clarify that point #5 in your list refers to a new and DIFFERENT server on the same network as the one you just moved.

In other words, in the new environment you will need 2 distinct servers: One to move into the same domain, and the second to perform the parallel migration (upgrade to 2022) on.

It might work if you install the first server on its own SQL instance name, but we have found that the parallel migration will complain if the SQL server instance is the same on both the source and the target.
It's also cleaner to have a separate server, if you have that advantage to spin up a temporary one.

Cheers,​​​

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

Original Message:
Sent: 09-29-2022 13:43
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

I have another question on moving premium 2020 to a new server and new version of SQL.  Customer needs to also upgrade premium version to 2022 on the new server and it's on a different domain. I just need someone to review if I have my steps correct:

1.  Install Sage 100 Premium (Same Year/Edition/PU) on the new server.
2. Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation).
3.  Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM).
4. Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless.
5. Install a newer version of Sage 100 Premium (2022) on new server.
6. Install another version of SQL that supports Sage 100 Premuim 2022.
7. Run the parallel migration tool from within v2022 to upgrade the software.

Is this the best practice to do a premium upgrade or is there a better recommendation?

@Kevin Moyes @George Khairallah​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-27-2022 07:33
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Thank you @Kevin Moyes, I will be there! ​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-26-2022 19:57
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Tomorrow's Sage Roundtable webinar is a great way to hear from / communicate directly with the Dev team, and so is MOTM.  Support is what it is... that is not the path to any long term improvements in the product.
(I started an email chain with Elliott P. in March about Premium upgrade issues, and he says they are looking at making changes... no guarantees, but the more voices are singing the same song, the more likely they will hear us).

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


Original Message:
Sent: 07-26-2022 19:47
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Best practice: whatever works.
My plan "A" is to get a working connection between servers, because that is how the migration program is designed to work.  If they are on the same physical network, a regular migration may be possible (even with a domain change), but you have to do a lot of fiddling with service accounts (and potentially Windows credentials manager).
If plan "A" doesn't work, then you have to figure out how to get the source system running in a way you can get the upgrade migration done.  Clone, temp server, using the new server for both... whatever works with the skill of customer IT.

Always do a test migration with odd situations, to give you time for troubleshooting without being under the pressure of a Live upgrade in progress.

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

Original Message:
Sent: 09-29-2022 13:43
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

I have another question on moving premium 2020 to a new server and new version of SQL.  Customer needs to also upgrade premium version to 2022 on the new server and it's on a different domain. I just need someone to review if I have my steps correct:

1.  Install Sage 100 Premium (Same Year/Edition/PU) on the new server.
2. Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation).
3.  Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM).
4. Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless.
5. Install a newer version of Sage 100 Premium (2022) on new server.
6. Install another version of SQL that supports Sage 100 Premuim 2022.
7. Run the parallel migration tool from within v2022 to upgrade the software.

Is this the best practice to do a premium upgrade or is there a better recommendation?

@Kevin Moyes @George Khairallah​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-27-2022 07:33
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Thank you @Kevin Moyes, I will be there! ​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-26-2022 19:57
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Tomorrow's Sage Roundtable webinar is a great way to hear from / communicate directly with the Dev team, and so is MOTM.  Support is what it is... that is not the path to any long term improvements in the product.
(I started an email chain with Elliott P. in March about Premium upgrade issues, and he says they are looking at making changes... no guarantees, but the more voices are singing the same song, the more likely they will hear us).

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


Original Message:
Sent: 07-26-2022 19:47
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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

Steps 5 & 6 are out of order - you need the SQL instance before installing Sage 100

------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
------------------------------

Original Message:
Sent: 09-29-2022 13:43
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

I have another question on moving premium 2020 to a new server and new version of SQL.  Customer needs to also upgrade premium version to 2022 on the new server and it's on a different domain. I just need someone to review if I have my steps correct:

1.  Install Sage 100 Premium (Same Year/Edition/PU) on the new server.
2. Copy MAS90 source from the old server to the new server (Replace the MAS90 on the new installation).
3.  Restore MAS_SYSTEM and all the MAS_XXX to the new server (Replace MAS_SYSTEM).
4. Adjust the database owner, and re-associate the MAS_USER, MAS_REPORTS, reconfigure/relink paperless.
5. Install a newer version of Sage 100 Premium (2022) on new server.
6. Install another version of SQL that supports Sage 100 Premuim 2022.
7. Run the parallel migration tool from within v2022 to upgrade the software.

Is this the best practice to do a premium upgrade or is there a better recommendation?

@Kevin Moyes @George Khairallah​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC
------------------------------


Original Message:
Sent: 07-27-2022 07:33
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

Thank you @Kevin Moyes, I will be there! ​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-26-2022 19:57
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Tomorrow's Sage Roundtable webinar is a great way to hear from / communicate directly with the Dev team, and so is MOTM.  Support is what it is... that is not the path to any long term improvements in the product.
(I started an email chain with Elliott P. in March about Premium upgrade issues, and he says they are looking at making changes... no guarantees, but the more voices are singing the same song, the more likely they will hear us).

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


Original Message:
Sent: 07-26-2022 19:47
From: Shannon Stanley
Subject: Sage 100 Premium move to brand new server on different domain

@Kevin Moyes how do go about getting this information to the dev team if support just wants to push it back to the consultant and basically tells them.....you need to hire a DBA to help you. It's not a DBA issue and I voiced my opinion that you cannot run parallel migration utility if two servers are on different domains if they cannot talk to one another? I was basically told I should have the IT groups open the security to both of these servers so I could finish out the parallel migration. In our world that is never going to happen. I would have been dead in the water without the help from the community at 90Minds.​​​

------------------------------
Shannon Stanley
Sage 100 Consultant
Ardent Consulting LLC


Original Message:
Sent: 07-25-2022 16:34
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

I see this as the biggest benefit of direct access to the Sage dev. team.  They don't have as much real-world experience as we do, so if we can share the headaches that we have to deal with (which don't necessarily make it from support to the developers), it's a win-win.

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


Original Message:
Sent: 07-25-2022 15:19
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

I love this method @George Khairallah !  I don;t understand the reasoning for the Sage way of migrating Premium.  If we had do use the Sage way then there would not be a way to recover if a server fails other than a bare metal restore which can have its own set of issues even if the hardware is exactly the same configuration.
​

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


Original Message:
Sent: 07-25-2022 15:13
From: George Khairallah
Subject: Sage 100 Premium move to brand new server on different domain

Doug, you're correct.
The idea is to have an initial installation first with the exact PU, to have all the base files in their locations.

Then copying the MAS90 folder, which will include the MAS_SYSTEM and MAS_XXX + the corresponding BAK files, will bring everything nicely.

Obviously, there are some adjustments as it relates to the Paperless office relinking and some other small items.
From our experience, we didn't run into any trouble due to the change in the server hostname.

Relatively speaking, this method seemed way simpler than the Sage Merge document and allowed us for a full offline move (not migration).

At this point, when we have customers coming from outside where we can't have direct access to their local instance, we are suggesting an "Initial Move" per the process above, then build a second server and do their upgrade on that, then decommission the first server. This will make both servers exist in the same environment allowing for a proper Sage 100 Premium Upgrade.

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |


Original Message:
Sent: 07-25-2022 12:54
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

Does George mean copy the mas90 folder from the source location over the top of the generic mas90 folder that gets installed?

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


Original Message:
Sent: 07-25-2022 12:43
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

SQL permissions.
MAS90 folder copy... and update paths if the Sage server's name / paths are not the same as the original.  Basically: what George referenced above.

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


Original Message:
Sent: 07-25-2022 12:13
From: Doug Higgs
Subject: Sage 100 Premium move to brand new server on different domain

What happens if a server crashes and Sage 100 needs to be restored immediately on a new server?  My understanding is you install SQL server, install Sage 100 programs, set up the service, open the ports, then restore the MAS_SYSTEM and the MAS_XXX databases.  What's missing?

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


Original Message:
Sent: 07-25-2022 11:36
From: Kevin Moyes
Subject: Sage 100 Premium move to brand new server on different domain

Glad it worked out!
(This is something I've asked Sage to make easier... Elliott seemed receptive to making changes, but feel free to nudge him during the Developer call).
A technique I made work a couple times: set up each SQL service to run under a user account (use the SQL tool for changing the service account).  Then use Windows Credentials Manager to give that user account access to admin credentials for the other server.  I can't remember if I needed to use the BAK files using this method... but was able to get it to work somehow using WCM.

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