Hi,
I cannot seem to get the signature box working in Outlook when using GWSMO account. Using another profile in Outlook, signatures work with no issue. In the GWSMO account, you cannot create new signatures, edit signatures, see the list of current signatures, or set the default signature for new or reply emails. However, you can select the signature manually.
I'm sure this used to work as I did it previously; however, I have set up a new Window profile, and those settings have not transferred.
How can I setup a default signature for new/reply emails?
Cheers
Hmm, perhaps this is a Google issue - https://callthatgirl.biz/gwsmo-signatures-not-working/
I am also seeing some users with this issue today.
I am browsing around to see if this is becoming a widespread issue.
I've seen this issue on 3 computers starting 4/10/23 for new employees using Outlook with GWSMO tool. Hope there is a fix soon.
I'm also seeing the same issue. I contacted support and they told me "The product engineering team is already aware about this issue and as per their response, many users have reported this same issue recently. So the team is trying to reproduce the issue in their environment. They are actively working on it."
FWIW, I was moving a Windows profile and had access to the old profile where the GWSMO account was set up correctly, albeit you couldn't modify the signature settings. However, I was able to export some registry keys and re-import them into the new profile. I do not think that creating these keys from scratch will be a thing, though.
For info, check out this cross-post at MS - https://learn.microsoft.com/en-us/answers/questions/1215092/how-can-i-enable-new-reply-signatures-th...
Same issue with Outlook 2016, 19 and 21 using gwsmo
There are more reports from our clients too. Seems like a widespread issue. Support says they are working on a fix
Same issue here. GWSMO v4.3.53.00 with Microsoft Outlook Version 2302 (Build 16227.20258) on Windows 11 and we have several end-user report that they are unable to create or edit their email signatures within Outlook.
All,
If you check out the link posted previously (https://callthatgirl.biz/gwsmo-signatures-not-working/), Lisa has received a workaround from Google which involves adding a registry key:
HKCU\Software\Microsoft\Office\16.0\Outlook\Setup /v disableRoamingSignaturesTemporaryToggle /t REG_DWORD /d 1
Add the key `DisableRoamingSignaturesTemporaryToggle` as a DWORD, with the value of `1`, then restart Outlook.
Unfortunately, if you have other Outlook profiles, I think this key will affect those too, which may not be what you want.
@swinster Yes this is the solution that is given currently.
@swinster I recommend you to mark this post from you as the solution such that others will get to know that it is resolved
@ajojose33333344 I do not think marking this as resolved is correct, as it breaks other things in Outlook. I suspect Google will continue working on a proper fix rather than this temporary workaround. Once that is released, we can add it here and mark it as the solution.
Thanks for the workaround !! adding the "DisableRoamingSignaturesTemporaryToggle" worked !!
This worked perfectly! Thank you! * i saw that link but disregarded it as it looked like a plug for the business page lol.
If you have multiple google profiles in outlook desktop, the signatures still are not populating correctly in one of my profiles. I set the profile signature by default and then the next time I send an email still not working. Also the correct reply email isn't working either.
It appears Google made some changes to how they code signatures for these profiles in C:\Users\xxxxx\AppData\Roaming\Microsoft\Signatures. The problem is if you have two default google apps profiles in outlook the signatures are conflicting with each other, and outlook doesn't know which one to choose, this is a result of Google or Microsoft's new way to name the signature. We really need a fix from these companies. This is very painful!!
Is there a resolution yet??
Hi,
Some of our users have this exact issue or though we are not looking to use a workaround. So out of curiosity, did google ever find a real solution?
I did not see any recent updates with this fix yet.