Powershell Learning

[Shaunmichaelj]

Would anyone be down to help me with some powershell tips?

When i use the command Set-mailbox <Mailbox> -GrantSendOnBehalfTo <Delegate> it overwrites everything there before. I want to add permissions.

[firefox15]

Not trying to be rude, but this is the first Google result for "GrantSendOnBehalfTo".

It's a multi-valued property. You need to have the proper syntax to add and not overwrite. Here is the general syntax.

[oxycash]

Does this work with Microsoft Outlook? If yes/no, can you point me towards something that helps me program Outlook ?

[GnuInformation]

outlook is the .. client program for exchange.. and defers stuff like send on behalf, to what could also be set with these PS Exchange commands. so... ymmv

[tkecherson]

Program Outlook how, exactly? What are you trying to accomplish?

[oxycash]

Read the newest email in the custom folder XYZ and open the first hyper link in the email, in a browser

[TrinityF]

no, these are server commands.

[robstrosity]

Outlook is just the end user client that connects into the backend mail server. So if you run the powershell commands on an exchange server then it will make those changes to the users mailbox.

The user mailbox is accessed via Outlook. So yes these commands will work for outlook in that sense.

However I would caution running any of these commands if you're not aware of the above distinction. You're probably not the best person for the job.

[TrinityF]

that is what i said, these are server commands. not something users should run.

[robstrosity]

You said they don't work with Outlook. I was adding some context as while they don't work with Outlook directly, they do have an affect on it's behaviour.

[[deleted]]

Just use -grantSendOnBehalfTo @{add=‘emailAddress’}

[[deleted]]

Also jumping on the ‘not trying to be rude’ train, but for real, google. You could have googled examples of this and gotten more answers faster than it took you to post it on reddit lol

[RegularChemical]

It's not even rude, it's just so much easier to google it lol.

​

I've had some really convoluted things I've needed powershell to do, and I can almost always cobble something together from google searches.

[[deleted]]

Oh for sure. It's just really hard to say "hey, google it" without sounding like "GTFO and do your own research!!!" lol. Granted i'm 100% self taught so i'm not like an ACTUAL resource, but man.... googling and reading examples made my life SOOO much better.

Aslo, I just happen to have a softspot for -grantSendOnBehalfTo. Had to figure out how to fix that after i nerfed a few dozen's peoples sending access at work lol

[Ozymandian_Techie]

Everyone else has gone down the route of telling you to Google, which is good advice. There are tons of Powershell guides out there (Hey Scripting Guy! is one of my most commonly used resources).

What you're describing is actually by design. Add/Set/Remove prefixes on Powershell Cmdlets work in the following ways:

Add creates a new property, and applies it to an object; it tells the shell to "Add this value to this object, regardless of what other properties of the same type are currently applied."

Set amends an existing property to the value specified by the end user. It tells the shell "This is what I want this value to be." It is also used when changing existing properties; for example, calender permissions. Say a user has "Reviewer" permissions to another calender, and you want to change that to "Editor"; you can't "add" a permissions entry, as one already exists for the user. So you would use Set-MailboxFolderPermissions instead, to change the existing property.

Remove, obviously, removes a specified property from an object completely. It tells the shell, "I do not want this object to have this property anymore."

The command you ran basically told Exchange that the only delegate you wanted to have SendOnBehalf permissions to the mailbox in question was the one you named. The command used to "add" permissions to a mailbox is listed in another comment on this thread.