Forcing Signature in Outlook Desktop (don't allow changes)

[miketheferg]

I 'think' i read that this scripts intended design was to lock the signature settings for the users with this script in the youtube video. For me, it looks like it locks users out of making any changes in the Outlook desktop app signature settings right after the script runs, but after closing and reopening outlook or rebooting, they are able to update the signature. Have you seen this behavior? Is there any gpo or reg setting that can lock the signature settings down so changes can't be made?

[matesaakos]

Hello, I have noticed the same issue. The "First-Run" Reg key just reapears after a outlook reboot. Is this a new issue or is it something on my part? I am running the script manualy (to polish it) under a user. Any advice?

Edit: The problem is that new-Itemproperty -name ReplySignature and NewSignature does not hold in registry. After a reboot (outlook) these keys are removed.

Thanks in advance

[captainqwerty]

Hello, apologies on the delay here. I have only just recently got time again to look at my personal projects and I am back to working on this project.

I will look into this and see if I can understand what you mean.

Thank you.

[m-hanisch]

@captainqwerty @miketheferg This might be related to the Outlook Roaming signatures feature that needs to be disabled by registry editor. Microsoft says that the only way to disable roaming signatures for Outlook desktop, remains to apply a registry setting.

Moreover, you can "postpone" the feature until later by means of PowerShell:

Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater $true

Sources:

• Outlook roaming signatures
• Exchange Online Tenants can Postpone Roaming Signatures