I would love to see this software shrivel up and croak. I would be much happier administering a 100% Microsoft Office world (not that I *love* Microsoft's software, but at least it works most of the time!).
It is such a pain to administer, seems to have
no mind toward network security, and their technical support is so abysmal and expensive as to defy logic. Well, to be fair, I should mention that this is only the case when Corel's Technical Support team is actually
taking support calls: we always seem to call when they are having their "team meeting" and the entire company huddles in some room somewhere and they don't even accept support calls (yes, this occurs during business hours...and I think it's monthly!!!). Regardlesss, we do work extensively with WordPerfect, and administer and push it out successfully to remote sytems using unattended install/option scripts to set it up on machines where the users have no administrator rights. This has, in general, worked well for us.
We actually saw this problem in 9 and 10
both. Also, 9 and version 10 (before SP1) liked chewing up documents created in 8 and spitting them out into corrupt files. Document corruption went from a "1% of the time" kind of a thing to a "20% of the time kinda thing." What a mess. Version 8 was too unstable on Win2k and up, so we dumped it with great haste in favor of 10.
There are several things which may work, so here are a few ideas (some of which are Corel's, not mine ):
1. [Editor's Choice]
Dump WordPerfect and go to MS Office. There. Problem solved.
![[2thumbsup] [2thumbsup] [2thumbsup]](/data/assets/smilies/2thumbsup.gif)
If this is not feasible (as, unfortunately, it was not for us
![[thumbsdown] [thumbsdown] [thumbsdown]](/data/assets/smilies/thumbsdown.gif)
), see #2.
2.
Change your entire network security paradigm and make all of your users full administrators. ![[3eyes] [3eyes] [3eyes]](/data/assets/smilies/3eyes.gif)
This is always Corel's initial suggestion (one of my personal favorites...I'm sure
their network admins would disagree with this approach as much as most of us would!) Alternatively, have them log out of the domain session, and have them log in as local administrators, giving them full license to screw their PC's up even more. Presto! Either way, the template problem is solved. This does actually address the problem, and may be suitable for some situations. Of course, if things were this simple for most people, this thread wouldn't exist! If this sort of solution would have you pacing the floor at night worried about what you may encounter back at the office, read on.
3.
Find out which keys/files need what security changes and apply them locally on the PC. The trick here is...
What keys, what files, and what security? We actually have asked Corel numerous times to tell us which keys/files need what access adjusted on the local PC, and it usually takes days or weeks to get an answer. When the answer comes, it's usually "We don't know...have you tried making your users full administrators?". Very productive use of a support incident (which is expensive). If you do not feel like changing your network security, see below. However, I'm sure this would work if someone could produce/discover that elusive file/key information, this solution would be somewhat workable, if clumsy.
4.
Blame Microsoft, it's their fault, because they made the operating system secure and it "messes up" [
that's a technical term, kids]
our software. Yet another helpful tip actually given many times by Corel (for this and many other problems we have experienced). But if blame assignment isn't your bag, continue to option #5.
5.
Upgrade to WordPerfect Office Suite 10. Clearly this is not feasible or economic in many situations. Suite 9 was so plagued with problems when running on Windows 2k and greater that this is still the de facto response most of the techs will give. It took 4 (count 'em ...
FOUR) service packs just to get this POS to run on the Win2k kernel in a manner that their tech support would field calls. Any other version of 9 or earlier suites were not supported. Regardless, the upgrade is fairly inexpensive (right around $90 or so, as I recall, assuming no Paradox/Pro configuration is needed). If it is, I think it may add $40-60 or so (can't really remember). However, if you upgrade to 10, you're not necessarily out of the woods as this is the version where we had this problem most frequently. You may still want to read #6.
6.
Make sure that, once WordPerfect is installed, it is not opened by the administrator prior to establishing the Default User profile. Typically, most administrators make changes to the initial/default user template on a deployed or new PC using the User Profiles utility in Win2k/XP. If WordPerfect is opened by an administrator, and that profile being used to subsequently copy over the Default User profile, everything explodes. This was a huge problem for us, since WordPerfect needs the CD/installation source files the first time a given user runs it (which is problematic and clumsy). We tried to set it up so that the default profile already had what it needed to use the software, but this, in turn, brought over security issues that translate into the dreaded "cannot initialize templates" issue. If this fails, try #7.
7. We have had some success with this last approach as well. Our experience was on Version 10, but I have a hunch it may work on 9 also. It is somewhat labor intensive as it must be done at each machine and can take quite a while depending on its speed and other factors.
a. Close all apps, and have the instatllation source (whether network or CD or what-have-you) handy.
b. Access
%UserProfile%\Application Data\Corel and rename it, something like corel.old or something should suffice (it can be deleted now or later, but just keep it in case something goes wrong or user customizations perhaps contained in the template/*.wpt file may be needed later).
c. Then, being still logged in as the user (with no administrator rights), rename
\\HKey_Local_Machine\Software\Corel to something else in the registry. If you do not know what the registry is, I suggest you first do some reading on it...screwing up what you do in there can completely FUBAR your system!!!
d. If the Default User profile was set up to include an already launched installation, this needs to be scrapped also. Either re-work the Default User profile by renaming (or, preferably, deleting) these files there as well, or start over on a new machine with a "virgin" Default User profile.
e. Launch WordPerfect again. This should invoke the configuration process again, pulling settings from both the Default User profile
and the installation source files. Again, be sure to have whatever source was initially used handy or this process will stop halfway and you¡¦ll have to back out
That typically does it for us. If it does work, you can then go back to the other keys/folders and pull whatever settings you may need. If settings are unimportant, or you already moved them, or you are anal retentive (like me), it is not a problem at this point to delete the renamed folders. On the other hand, it does not seem to mess anything up to leave them on the PC renamed. If you think that sounds fun, just wait until you have to migrate settings from 8 to 9/10. It's a hoot!
Also, if you are trying to figure out how much fun it will be to visit every stinking PC in your entire company/enterprise with the stupid CD in order to do this, I strongly encourage you to try using a Network installation instead. That way, when a user runs WordPerfect for the first time, the CD is not needed and no prompt is give--it just intelligently pulls the files it needs from the original installation location.
To be fair, I will give Corel partial kudos for at least employing Windows Installer technology in version 10 (at least, I can't remember for 9 and before), which means that (in theory, anyway) it can be remotely administered and installed from a central location on a network. This can be used to install WordPerfect to all PC's with whatever components/options you want (though it still needs to be done using a system account or administrator account). One caveat however--if you are using Paradox in your build, test this approach and take Paradox for a test run after installing before going hog wild with the rollout. As I recall there are some post-install updates that must be run on Paradox
just to get it to run...though these may not have been peculiar to the Network installation method. This even worked surprisingly well in version 8 back in the days of Windows98. Oh, would that things were so simple again...
Hopefully this spares somebody the toils of dealing with the foolish cat-and-mouse games we had to go through to get this to work here. This was frustrating some of us to the point of tears at points. Good luck! (no, I'm not bitter!)
Dallas S. Kelsey, III
DKelsey-at-CHGLaw-dot-com
Cox, Hodgman, & Giarmarco, P.C.
Troy MI 48084