Manage Email Signatures Centrally - For All Users

robert doku

I work for an organisation which is worried about the use of an administrator's account for the deployment of emailSignature to OWA mailboxes. Surely, a service account can be used to provide the same support required where divulging an administrator's password is not required? I know for a fact this method is employed to give Blackberry users "Received As" properties to their mailboxes. Is this feasible in emailSignature?

Bjarne Mess · Posted: Sun Apr 06, 2008 6:47 pm Post subject:

Yes, that would do. We don't recommend to save the admin password anywhere, and creating a system account or similar with the limited priviledges would be acceptable.

Good luck
Bjarne

robert doku · Posted: Sun Apr 20, 2008 6:17 pm Post subject: Deploying signowa

I'm a bit confused here; I thought you have to pass the login details of an elevated account to the registry in other to deploy signowa. Is that not compromising security?
_________________
RobD

Robert Silkensen · Quite a regular Joined: 17 Apr 2008 Posts: 16 Location: VA

I agree. Storing a vaild account and (text) password in the registry is a security hole just waiting to be found.

Anyway to encrypt it?

sbscaggs · Just popping in Joined: 12 May 2008 Posts: 4

Did we ever get an answer to this? I have a problem putting a plain text password in the registry and am wanting to know a way around this.

Thanks

Jakob Christensen · Posted: Fri May 23, 2008 11:02 am Post subject:

Instead of putting domain, username, and password in the registry, you can use the "Run as" feature of scheduled tasks. If user credentials are not found in the registry, signOWA will connect using the "Run as" user instead using Kerberos or NTLM.

The "Run as" user must have "Receive as" rights on the mail store as usual.