The Server parameter value is taken from the server name stored in $server .
# Set permissions on the folder
Add-PublicFolderClientPermission -Identity:$newFolder `
-User:$usermb.alias -AccessRights:Editor -Server:$server
Running the newuser - publicfolder.ps1 Script
Running newuser-publicfolder.ps1 is really quite simple: the name of the script followed by the
name of a mailbox - enabled user. The name supplied can be in the form of the full name encapsulated in
quotes, the alias, the user principal name, or even the user ??™ s Global Unique Identifier (GUID). This is
possible because the underlying Exchange Management Shell cmdlet used in the script accepts these
forms of identity.
As with any good script, newuser-publicfolder.ps1 incorporates some simple validation and error
control. The following examples demonstrate what happens when validation fails in preliminary testing
before any main script processing is attempted.
When no mailbox - enabled user identity is specified, this error message is generated:
[PS] C:\ > newuser-publicfolder.ps1
You must enter a mailbox enabled user account as input to this script.
When the mailbox - enabled user identity is either not mailbox - enabled or does not exist, this error
message is generated:
[PS] C:\ > newuser-publicfolder.
Pages:
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644