mirror of
https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git
synced 2026-04-26 10:45:52 +03:00
[GH-ISSUE #53] MsalToken problem on windows 10 and 11 computers #18
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Set-OutlookSignatures-Set-OutlookSignatures#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dakolta on GitHub (Sep 6, 2022).
Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/53
Originally assigned to: @dakolta on GitHub.
We are replacing computers and are running the script on new computers and are getting the following error:
I have attached a verbose output from one of the computers:
SetSig.txt
@GruberMarkus commented on GitHub (Sep 7, 2022):
This is not a bug, but wrong usage of the script as the script is executed in the SYSTEM account context:
Set-OutlookSignatures must run in the security context of the user who shall receive a signature, as stated in the 'Requirements' section in the 'README' file:
@dakolta commented on GitHub (Sep 7, 2022):
Yea are using a scheduled task to start a vbscript as the usr, this is happening on other computers with no issues. I just ran the vbscript from the command prompt as the user and have the same error.

And here is the result:
Here is the verbose file:
SetSig.txt
Here is the vbscript:
I should also mention, there is no prompt happening for logon when the script runs on these 2 computers. On one of the computers I reverted back to 3.2.1 and ran the script and got the same result.
Here is the verbose output:
SetSig3.2.1.txt
@GruberMarkus commented on GitHub (Sep 7, 2022):
I can't help you with VBS, that was just too long ago.
If the very same script runs fine on previously installed computers but fails on newly installed computers with supposedly identical versions and configuration, the problem maybe is not the script but the computer configuration.
Run the attached alpha version with the '-verbose' parameter and share the output. It should give us more information if and where authenthication fails.
Set-OutlookSignatures.ps1.txt
@dakolta commented on GitHub (Sep 7, 2022):
Just so you know, I found the issue.
The problem happens when Google Chrome is set to the default browser and allow-insecure-localhost is not enabled.
Setting Edge as the default browser fixes the issue, don't know if you want to add in a check for the default browser or not.