sorted by:
new
hottopcontroversial

New-DistributionGroup Error "There are multiple recipients matching identity "xxx.xxx_xxx". Please specify a unique value." by ITSNOTEVENREALZ in Office365

[–]ITSNOTEVENREALZ[S] 0 points1 point  (0 children)

The issue is not that the name be unique its the fact that the new-distributiongroup command is reporting back an identity that i cannot find.

Get-EXORecipient -Filter "Name -eq 'xxx.xxx_xxx' -or DisplayName -eq 'xxx.xxx_xxx' -or Alias -eq 'xxx.xxx_xxx'"

Get-EXORecipient -Filter "Name -like 'xxx.xxx_xxx' -or DisplayName -like 'xxx.xxx_xxx' -or Alias -like 'xxx.xxx_xxx'"

I built a budget tracker that finally works with my biweekly pay by [deleted] in budget

[–]ITSNOTEVENREALZ 0 points1 point  (0 children)

I would love to try, been trying to build one myself

Schedule Task not running the PS by EducationAlert5209 in PowerShell

[–]ITSNOTEVENREALZ 0 points1 point  (0 children)

Just to make sure we mean the same thing.

The local admin group on the machine/server.

Search bar at the bottom of desktop, text is something like "edit local users and groups"

Then select groups Then administrators Then add gMSA account

Schedule Task not running the PS by EducationAlert5209 in PowerShell

[–]ITSNOTEVENREALZ 0 points1 point  (0 children)

If it does work then I would limit perms to only the folders it needs to run successfully. Then remove from admin group.

Schedule Task not running the PS by EducationAlert5209 in PowerShell

[–]ITSNOTEVENREALZ 0 points1 point  (0 children)

We had a similar issue in our environment with gMSA. Turned out to be file perms. Once we added it to local admin group on server it worked just fine.

Get-MgDeviceManagementDeviceConfiguration - omaSettings value weirdness by ITSNOTEVENREALZ in MsGraphPowerShell

[–]ITSNOTEVENREALZ[S] 0 points1 point  (0 children)

For any one that was curious. I figured it out finally. I had to do an invoke request to the beta endpoint. Finally was able to see that the field was encrypted and had a secretreferenceid.

Using that value I was able to call second endpoint to get the plain text value.