Bear with me a moment while I grumble and I'll get to YEC for 10.0.
Great Plains isn't what it used to be. That's both good and bad I suppose.
It is good that all workstations should be on the same SP version to be able to log into a company. This saves many significant issues popping up as most are well aware. Workstations used to always be out of sync and a lot of the time the resolution would be "Apply this patch like all the rest of the workstations. etc."
However it is frustrating when you only need to apply the year end update for payroll. In times past you could put the cnk file only on the payroll persons workstation and they'd be good to go. It's a major effort now to apply any service pack. It almost feels like people are being pushed into a Citrix/Hosted or Terminal Server model. There are major advantages of only having to apply SP's once at a central location. I know you can have the SP automatically apply the next time a user logs into the system but that is mostly just a huge pain none the less.
Ok, 10.0 year end update. Here are a few things I've come across while going through the year end update. Most are pretty user specific but here they are none the less.
- All people must be out of the system. Sounds like a no brainer but we spent several mins troubleshooting why the system tables wouldn't update then found some people had snuck into the system. (Hopefully Mike's head doesn't hurt too bad from hitting it repeatedly on the desk in front of him.)
- To install the update make sure the installation of GP is at least the first recommended release of 10.0. Had one client on 10.0.465 which is a beta release of 10.0. Who knows how they got that one installed. Kept getting this erorr when trying to apply the update. Applied 10.0 Feature pack 1 which includes SP3 (1.5 gb download so don't do this with a 56k modem), applied the update and they were good to go.
- You can run the update from a client workstation. Don't need to be at the server. Kind of counter intuitive but it works. After corrupting GP on the server during resolution of #1 we got the update to go on a client workstation. (Thanks to Jamie Nelson on this one).
- Plan for several minutes per database. I've timed several updates and it seems like it runs around the 20 min range per database. This is true when the databases are pre SP3. Not sure if it's quicker if SP3 is already applied. (Anyone know this?)
- You must run the year end wage file before applying 2009 tax tables. Duh.
- You can't run a 2009 payroll before running the year end wage file. Duh again. ha.
- User gets kicked out of GP when running payroll reports after applying update. Recreated reports.dic as it was corrupted in the process. So....make sure you backup reports.dic, forms.dic, dynamics and company databases etc. The process looks like it actually exports then imports the reports as part of the update so that could easily cause issues.
Here's a few other Year end update comments from Christina Phillips on her blog.
Victoria Yudin still has a great post on Year end close resources.