Let me add to this forum to save the agony for someone else. We migrated to AD and had most of our member servers set to "Change primary DNS suffix when membership changes", which brought about this issue. We didn't take that into account during our AD migration. We didn't have any glitches with the name changes except Crystal Enterprise. I had two instances of Crystal that ceased to function because of the name change. I struggled for a day or two looking for the answer and following the Crystal procedure just wouldn't work, so I ended up reinstalling because the application that depended on it didn't have issues with a reinstall. Later on, we changed the server name back because we have a different primary DNS system and I ran into the same issue. Same result happened....I needed to reinstall because this server was picky about the Crystal services...for some reason just changing the name didn't work and neither did removing all the Crystal services and reinstalling them. The other server I had was more important, so instead of reinstalling, we now have a whole bunch of services installed, but only half are running and those are the ones with the correct computer name. We will be moving this system back to the old name, so we're going to go through this again. For that instance, we were able to remove the Crystal services and add them back in according to the procedure and not lose anything. It just isn't very clean though. Hopefully it will not blow up on us like the last time since we will be anticipating the results from a name change. My advice is to test this a little more than usual to ensure functionality, because I was seeing mixed results depending on what version of Crystal you have and how it's set up.
Hope this helps someone......