Kyle, when we upgraded to version 6.x we launched a big awareness campain to our user community (3,000+) to download and install the 6.x client early (after we tested it against the 5.1.2 server).
We used BB messages to our Remedy user community as well as a message and URL on the home page. When it came time to upgrade the server we had maybe 90% of the active users on the 6.x client. It was much more difficult to get the the rest done. We went to far as to prevent them from logging in if they did not have the required client version. I believe there is an option in the server settings. I am planning the same thing with the 7.x client. Getting it out early before we move to a new server. Another issue I have run into, is the frequent updates of patches for clients. When your enterprise uses a software distribution system, you need to package the installer before it is made available to the users (via push or pull), but by the time you roll out the server, a new version/patch will be available. With the client installer ballooning from 20+ to 40+ to 100+ to 120 MBs and them not just having a simple patch installer or individual components available like they have for server, that is a major issue. Also, since they still do not use .msi packages, the installer cannot easily be packaged for some of the enterprise software distribution systems. I believe that most of the overhead in the client has to do with the Crystal Reports runtimme. I wish BMC would release a client without the Crystal functionality since we do not want our users to run reports from within the client anyway. That's what reporting portals and dedicated reporting servers are for. Rgds, Chris _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
