Lacerte Updates - Limiting the Number of States
As an MSP (IT), I manage the Lacerte setup for one of my clients. I have some questions on how the number of states affect the update process. Through the years as they managed it themselves they defaulted to installing all states and options (whatever they were licensed for), which is most everything. I suspect they only tax prep on a small percentage of the states, probably under ten. Currently Lacerte is setup as a network installation in Azure. I am aware of the Intuit KBs on the best way to handle multi-user setups and update processing, and I have tried to follow them the best way possible. I have disabled update notifications in Primary Options, and it seems it has to be set in each tax type. Sometime users will tell me they still get notified about the updates...that might be a stray setting in their User Options that I will have to check. According to the info provided in those Intuit KBs, if Disable Notifications is set correctly, they should not be receiving these notifications.
My goal is to attempt to process updates on a schedule rather than at random whenever they get notified, which again shouldn’t be happening. Anyhow my questions:
- Would limiting the installation to only the necessary states they tax prep for:
- Decrease the number of updates they might need to apply
- Decrease the time it takes to process the update
- If the answer is yes, is there any issue with limiting the number of states modules installed going forward, leaving 2025 and previous years as they are?
- It is my understanding that when an update become available, they are prevented in performing some functions like eFiling until the update is applied. I am hoping to get the process refined:
- Having them queue up the eFiling until the next morning.
- Apply the updates that evening before, after hours when all users are out of the system.
- This would eliminate the mid-day disruptions forcing all users to get out in order to apply the updates.
I appreciate any feedback.
LThibx
