I have EFS running in a Windows Server 2003 R2 domain environment. Certificate services is working correctly and is issuing certificates to users that can be used for file encryption and smart card logon. The Basic EFS, User and Smart Card logon templates have been disabled and a new single template created.
EFS on Vista workstations works correctly. The users certificates are roaming between workstations and files can be encrypted on the local machine - the correct recover agents are added to the files.
However, when a user attempts to encrypt a file stored on a Windows Server 2003 server the encryption fails with the error message - "the window cannot act on the sent message". If I allow EFS to create a self signed certificate for the user then the encryption works - but this obviously isn't usefull.
So the question is - why can't the file servers locate a users certifcate which is stored in AD in order to encrypt the file?