Shortcuts thru a DNS

Hello,

Using a shortcut on the old machine to point to the new machine’s QuickBooks folder will likely cause an additional hop in data transfer. Here’s why a shortcut essentially acts as a reference, not a direct connection. When users access the shortcut, their request still goes through the old server before reaching the new one, adding an unnecessary middle step. This can create a bottleneck, especially since you’re aiming for better performance.

If speed is a priority and it sounds like it is it would be best to re-map the network drives for all 25 users to connect directly to the new server. Yes, it’s more upfront work, but it ensures that users access the new server directly, eliminating latency caused by routing through the old machine. It will also simplify troubleshooting in the future, as you won’t have to deal with complex shortcut setups.

To make the transition smoother:
1. Schedule downtime. Coordinate a specific time to make the switch, ideally when fewer users are active.
2. Update one workstation at a time. Start with a small group to ensure everything runs smoothly, then scale up.
3. Use a script for re-mapping drives. If your users are on Windows, you can use a batch file or PowerShell script to update their mapped drives automatically, saving time and effort.

While shortcuts might seem like a quick fix, the potential slowdown and added complexity make direct mapping the better long-term solution.

Hope this helps