Posted by Keith Smith on September 26, 2006 at 09:08:27:
Recently converted a medium size company off Novell 6.1 and onto Windows 2003 Server R2. At the same time, converted Comet 2004 to Comet 2006. Initially, everything appeared to go over smoothly but as time went on (we're talking days here..) things just kept getting worse and worse in that clicking on Comet2006Workstation.exe or Comet.exe would either hang the PC or cause it to reboot. With a few exceptions, all client PC's are Windows 2000 SP4. The exceptions are XP. The way I installed it was to have the client PC's icon target and start from the server network directory. With Jim's help, discovered way to get things moving again by targeting and starting Comet from LOCAL directories on ALL client PC's. Though I'm appreciative the situation has calmed down and my client can run again with no glitches, this doesn't sound normal to me. Now upgrades are more complicated since I now must visit each PC to do it.. Thinking it was a CAL issue, I checked and 25 CALS were purchased with Windows 2003 Server... Can anyone help explain?? All the office suite software works just fine over the network... Hope this is enough details...