One issue with the trustedsignon functionality is that it does not seem very secure. A Peregrine KB document, number "S7N-002-1FNS" actually describes one method (and alludes to another one) on how the ServiceCenter security can be reached when trustedsignon is enabled. Basically the problem lies with what can happen if either:
1. a users domain login is not present in SC
2. a user creates a local login for a username that is a ServiceCenter administrator (such as "falcon")
Of above, scenario 1 is described in that document, and scenario 2 is referred to at the end of the document.
The document also states that an SCR (number 22443) has been issued on this defect, and that it is fixed in SC version 5.0.1 and later. However, when I tested this on SC5.1.1.0 running on my W2K laptop, I was able to login to SC without entering the password I had earlier set for falcon.
You might want to check this for yourself, and if you get the same results as I did, contact Peregrine before using this functionality. What I did to bypass the login screen:
1. add the trustedsignon parameter to sc.ini
2. start the SC service
3. login as an administrator and make sure that the administrator login has a password set
4. logout of SC (leave the service running)
5. go to e.g. the Control Panel and add a new local user to the system
NOTE 1: the username must correspond to the login of the administrator mentioned in step 3
NOTE 2: leave the password blank
5. right-click on the shortcut pointing to the SC client, and select "Properties"
6. select the "Shortcut" tab and tick the box "Run as a different user". Click OK.
8. launch the SC client. When W2K asks under which user do you want to run this program, enter the credentials of the user created in step 5.
best regards,
Jarmo