Sage 100

Our client is on Sage 100 Advanced v2023 6-7 different added 3-party applications.  Their IT Team is moving the backend platform from VMWare to Hyper-V.  The team is asking if we expect that to be problematic related to Sage 100 and Licensing.  The Server Name is not changing.  My gut reaction is that this will have no impact to the user of Sage 100.  Am I correct?  Has anyone done this, and what is your experience? 

*Changing Hardware Infrastructure

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Taking the whole Sage server image and moving it to new hardware / host, with the same servername, same domain, same IP address... I don't see any reason for there to be problems.

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

@Kevin Moyes That was my gut feeling.  But I wanted to confirm with someone.  Thank You!

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 09-26-2024 19:05
From: Kevin Moyes
Subject: Impact of chancing hardware Infrastructure

Taking the whole Sage server image and moving it to new hardware / host, with the same servername, same domain, same IP address... I don't see any reason for there to be problems.

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

What is changing in the hardware infrastructure?  There are known Sage 100 performance issues using Hyper-V and Windows Server 2019.

Per KB 223924250030079

If running Sage 100 on Windows 2019 Server in Hyper-V Environment try one of the steps below:
Option I:
Disable RSC for IPv4 traffic on the workstation client using PowerShell: Disable-NetAdapterRsc -Name
$nic -IPv4
Option II:
1. Check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch | Select *RSC*
2. Disable a Hyper-V vSwitch's RSC in full using PowerShell:
Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE
NOTE: This will not impact existing vSwitch connections

Also, I believe the notes below are from @Alnoor Cassim:

·        Start the Hyper-V Manager and:

o   Under Hardware / Memory category UNCHECK Enable Dynamic Memory. This works poorly for all ERP applications. Instead set the Startup RAM to the highest amount of RAM you planned to allocate for the Sage VM

o   Allocate additional Startup RAM and Processors as needed.

o   Low priority option: Consider converting the Hyper-V VM from Generation 1 to Generation 2 after making appropriate backups. This is a time consuming process that can take 2  - 4 hrs. This has more functional value for supporting new types of virtual disks for future VMs you spin up than for performance.

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

I had a client do something similar and we did not experience any issues.  Thanks @Doug Higgs for the additional information.

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

Original Message:
Sent: 09-26-2024 20:03
From: Doug Higgs
Subject: Impact of chancing hardware Infrastructure

What is changing in the hardware infrastructure?  There are known Sage 100 performance issues using Hyper-V and Windows Server 2019.

Per KB 223924250030079

If running Sage 100 on Windows 2019 Server in Hyper-V Environment try one of the steps below:
Option I:
Disable RSC for IPv4 traffic on the workstation client using PowerShell: Disable-NetAdapterRsc -Name
$nic -IPv4
Option II:
1. Check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch | Select *RSC*
2. Disable a Hyper-V vSwitch's RSC in full using PowerShell:
Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE
NOTE: This will not impact existing vSwitch connections

Also, I believe the notes below are from @Alnoor Cassim:

·        Start the Hyper-V Manager and:

o   Under Hardware / Memory category UNCHECK Enable Dynamic Memory. This works poorly for all ERP applications. Instead set the Startup RAM to the highest amount of RAM you planned to allocate for the Sage VM

o   Allocate additional Startup RAM and Processors as needed.

o   Low priority option: Consider converting the Hyper-V VM from Generation 1 to Generation 2 after making appropriate backups. This is a time consuming process that can take 2  - 4 hrs. This has more functional value for supporting new types of virtual disks for future VMs you spin up than for performance.

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