Microsoft Dynamics GP uses an ODBC connection for database access and the server name from this connection is used in the password encryption algorithm. This means if you need to migrate Dynamics GP to another server for any reason, such as a migration or SQL Server failover for disaster recovery, every single user will need their password to be reset. For implementations of Dynamics GP with a low user count this isn't too much of a burden, but I've dealt with clients who have over 250 users in Dynamics GP which makes resetting all passwords, even when using a GP macro, a chore not to be undertaken lightly.
It is possible, however, to avoid resetting all passwords by creating and using a DNS CNAME alias in place of the server in the ODBC connection.
Passwords still need to be reset when the CNAME alias is introduced to the system, but it removes the requirement to reset them in future when GP is moved between...