-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hide output if Winget settings not existing #95
Conversation
I agree for the |
@@ -96,7 +96,7 @@ function Add-ScopeMachine { | |||
$ConfigFile = Get-Content -Path $SettingsPath | Where-Object { $_ -notmatch '//' } | ConvertFrom-Json | |||
} | |||
else { | |||
New-Item -Path $SettingsPath | |||
New-Item -Path $SettingsPath | Out-Null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would even go for:
New-Item -Path $SettingsPath -Force | Out-Null
It gets created! |
I would go for the |
Maybe disable Microsoft.VCLibs.140.00.UWPDesktop for server? |
Yes, probably! |
haha, you're welcome. Don't know why |
Same here, and on WSB the ..2.7 otherwise the user didn't have winger... |
Maybe you're right, on server no need to try to install |
Haven't got access to a 2022 yet, maybe it's different. |
...and after your cleanup etc. of WAU we can install/use it on our 2019 management servers too (after deploying the GPO without -InstallUserContext to them)! |
Why do you need the GPO to block user context? |
To avoid having multiple installations in SCCM |
Not sure to understand |
We install WAU via an application in SCCM. |
Ohhh, ok... got it. |
One ring to rule them all 👌 |
No description provided.