10 Best Practices for a Successful Customer Solution Engagement


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS 10 Best Practices for a Successful Customer Solution Engagement
# 1  
Old 03-17-2010
10 Best Practices for a Successful Customer Solution Engagement

This paper discusses 10 key areas that frequently are not handled correctly and lead to customer dissatisfaction during customer solution engagements, and it provides recommendations for successfully handling them.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Shell Script to prompt customer for name etc

reposting How do I create a shell script called 'custinfo' to prompt a customer to enter and display back the following: name, age, address, phone number, product, price range. Thanks (1 Reply)
Discussion started by: SQLScript
1 Replies

2. UNIX for Dummies Questions & Answers

identify a customer under a UNIX server

Like many UNIX users, there is a small team that is connected to UNIX (under the same UNIX user) via putty from a Windows PC. Is there a way, once under UNIX, to know the address of the originating computer or anything that can differentiate initial users ? (7 Replies)
Discussion started by: popescu1954
7 Replies

3. HP-UX

Customer support engineer

Hi All, I need the help to deploy or implement HP MC service guard 2 node cluster step by step procedure is any1 who can help me to send me the step by step procedure. Thanks and Regards Jahangir (12 Replies)
Discussion started by: Jahangir
12 Replies
Login or Register to Ask a Question
compver(4)							   File Formats 							compver(4)

NAME
compver - compatible versions file DESCRIPTION
compver is an ASCII file used to specify previous versions of the associated package which are upward compatible. It is created by a pack- age developer. Each line of the file specifies a previous version of the associated package with which the current version is backward compatible. Since some packages may require installation of a specific version of another software package, compatibility information is extremely cru- cial. Consider, for example, a package called "A" which requires version "1.0" of application "B" as a prerequisite for installation. If the customer installing "A" has a newer version of "B" (version 1.3), the compver file for "B" must indicate that "1.3" is compatible with version "1.0" in order for the customer to install package "A". EXAMPLES
Example 1: Sample compver file. A sample compver file is shown below: Version 1.3 Version 1.0 SEE ALSO
pkginfo(4) Application Packaging Developer's Guide NOTES
The comparison of the version string disregards white space and tabs. It is performed on a word-by-word basis. Thus, "Version 1.3" and "Version 1.3" would be considered the same. The entries in the compver file must match the values assigned to the VERSION parameter in the pkginfo(4) files. SunOS 5.10 4 Oct 1996 compver(4)