Hi there, we're trying to stop users using the "save password" feature because it causes them to lockout their accounts after they have a password reset. I have worked out how to do this using InstEd to transform the .msi, but i want to create a 2x client policy because it's more elegant. I've got it working, however there seems to be a massive caveat. The only setting i want to control is "save password". The rest of the settings can be whatever the user wants. However, it seems if i create a policy it then overrides ALL connection settings (even though I didn't specify any changes to the other settings), and then also greys out the option to edit their connection properties. What i want to do is simply stop them using the "save password" feature; but i need them to be able to still control all other elements of the connection properties. For example, Doug upstairs was unable to control how his 2x client behaved in relation to desktop spanning, because i had a policy set in order to control the "save password" feature. As a result i have had to disable client policies entirely until this is resolved. Am i doing something wrong?
I think we would be interested in doing something like this as well. We want to enforce that URL's get redirected to the local client instead of through our Terminal Server.
