We need to investigate where and how signature properties are stored in Microsoft Outlook, research and suggest options how to copy an Outlook signature to a new Outlook profile.
Outlook research and testing environment was as follows:
Outlook 2013 signatures are configured on the New Email - Signatures dialog. Start composing a new email using the New Email command on Outlook ribbon.
When new email window appears, click the Signature icon on the ribbon and use the Signatures... option.
Clicking the Signatures... icon in Outlook reveals the following options:
Our research showed that Outlook signatures are located in files in %APPDATA%\Microsoft\Signatures
As you can see, there are .htm, .txt, and .rtf files in there for each one.
When we create a new Outlook profile for a user, signature files are still in the above mentioned location, available for use in a new message (New Email - Signature command).
The problem is that in a new profile there is no default signature on a new message. User must specifically select a signature.
In other words, creating a brand new profile gets us no default signature on a new message. A client who ordered this research intended to create Outlook profiles programmatically in a way that user default signature is set. It is, therefore, important to determine how to do it.
Our research has shown that the profile attributes are stored in local registry. For example, for a profile named Outlook the key name is:
The last part in key name is a profile name. See https://support.microsoft.com/en-us/kb/2850989.
Which profile value is responsible for a default signature in a new message? The New Signature value in one of the registry keys for a MAPI profile, for example:
Value: New Signature
Value: Text containing the file name of the signature to use. For example, if you have a signature file named "Alternative signature" then the value may contain this text, and %APPDATA%\Microsoft\Signatures will also contain the following:
Copying an existing profile gets as a a copy of registry subset with New Signature value present. Therefore, when composing a new message in such profile we do have a default signature already.
If we want to use an already existing signature as a default signature on new messages, we can insert the New Signature value into the registry.
Another option is, apparently, inserting a MAPI property (not sure which one) for a new signature via die-hard MAPI method of profile manipulation.