The details of the event scenario and the design points for Beginner Event #3 of the 2012 PowerShell Scripting Games can be found on the “Hey, Scripting Guys! Blog”. This was the toughest event out of the first three for me. I spent a lot of time researching how to check permissions because part of the first design point stated: "If you do not have permission off the root, create the nested folders where you have permissions". This was clarified in the comments section later during the day Read more [...]
The details of the event scenario and the design points for Beginner Event #2 of the 2012 PowerShell Scripting Games can be found on the “Hey, Scripting Guys! Blog”. Listed below are my notes about the requirements and design points: Find all services that are running and can be stopped. The command must work against remote computers. Use the simplest command that will work. You do not need to write a script. Return the results to the screen, not to a file. You may use aliases. I started Read more [...]
The details of the event scenario and the design points for Beginner Event #1 of the 2012 PowerShell Scripting Games can be found on the “Hey, Scripting Guys! Blog”. Listed below are my notes about the requirements and design points: Computers run Windows 7 and servers run Windows 2008 R2. They’re all in one domain. PowerShell remoting is enabled on all computers (both servers and desktops). Use PowerShell to retrieve the top ten processes based on the memory working set. There’s no Read more [...]
Since this is my first year entering the PowerShell Scripting Games, I’m only submitting scripts for the beginner events but I’m also taking a look at the advanced ones to get an idea of what kind of knowledge is needed for them. It’s not too late to join in on the fun. Make sure you read the requirements of each event carefully, create your script, test it, and think about it for a while before submitting it. I had four stars on the first Beginner Event: Another judge must have given me Read more [...]
Open Exchange Management Shell and execute the New-Mailbox cmdlet using the following example as a template:
The following cmdlet assigns full access for the mailbox to a group in Active Directory named “My Shared Mailbox Admins” which needs to exist in AD prior to executing this command:
New-Mailbox -Alias "MySharedMailbox" -Name "My Shared Mailbox" -Database "MAIL1\First Storage Group\Mailbox Database" -OrganizationalUnit "mikefrobbins.demo/My OU/Users/Mailbox" -Shared -UserPrincipalName "firstname.lastname@example.org"
This cmdlet allows members of the “My Shared Mailbox Admins” group in Active Directory to be able to send email from the "email@example.com" Read more [...]
Get-Mailbox -Identity "My Shared Mailbox" | Add-MailboxPermission -User "My Shared Mailbox Admins" -AccessRights "FullAccess"