Posts tagged PowerShell
Exchange Management IP for Orchestrator 2012 released today!
0Today I released my Exchange Management IP for Orchestrator 2012. It is currently available for download at the Microsoft Technet Galleries: GET IT HERE
This integration pack is an addition on the already available Exchange Mail and Exchange calendering integration packs. This IP will allow you to automate all (or at least most of them) Exchange (2010) related management tasks. For example:
- Adding and removing mailbox permissions
- Changing the Quota of a mailbox.
- Mailbox database and DAG management.
All activities are aware of your Exchange environment. There is no need to select a specific server. A server is automatically selected based on availability. There is also no need to install the Exchange Management Console or Powershell cmdlets. All activities use remote Powershell to connect to your Exchange environment.

Documentation is included in the ZIP file which explains most of the features including input parameters and published data. Integration with Microsoft System Center 2012 Service Manager is possible.
If you would like to have features added please drop me a line. Also you can follow me on twitter (@Bart_Inovativ) to receive updates on my development work and more System Center stuff.
Enjoy!
Features for the Exchange 2010 IP for Orchestrator 2012
0I am currently working on a new or extended Orchestrator 2012 integration pack for Exchange Server 2010.First (test) release will hopefully be released next friday (april 27th). It will include the following activities:
| Enable-Mailbox |
| New-Mailbox |
| Delete-Mailbox |
| Disable-Mailbox |
| New-AcceptedDomain |
| Remove-AcceptedDomain |
| New-ReceiveConnector |
| Remove-ReceiveConnector |
| New-SendConnector |
| Remove-SendConnector |
| New-DistrubtionGroup |
| Remove-DitritibutionGroup |
| New-ClientAccessArray |
| Remove-ClientAccessArray |
| New-DatabaseAvailabilityGroup |
| Remove-DatabaseAvailabilityGroup |
| New-MailboxDatabase |
| Remove-MailboxDatabase |
Current release schedule:
- First beta (0.1): April 27th
- Second beta with additional features (0.2): May 7th
- Release Candidate with bug fixes (0.5): May 20th
- Final first release (1.0): May 27th
If you would like to see additional features for this integration pack or want to take part of the testing phase please let me know @twitter (https://twitter.com/#!/Bart_Inovativ)
Exchange Powershell: How to import accepted domains from CSV file
0During migration projects a lot of customers asks me how to import all accepted domains the easy way. The script I provide below is very basic but it will save you a lot of time.
But first create a CSV file with on the first line AcceptedDomains. Insert all your accepted domains on seperate lines starting from the second line.
$File = Read-Host "Please enter location and filename of the CSV file (example: D:TempAcceptedDomain.CSV)"
# Reading of all lines within the specified CSV file.
$list = Import-Csv $File
foreach($entry in $list) {
# Reading the AcceptedDomain variable from the CSV file.
$AcceptedDomain = $entry.AcceptedDomain
# Running the powershell command for creation of all Accepted Domains.
New-AcceptedDomain -Name $AcceptedDomain -DomainName $AcceptedDomain
}
Exchange 2010: Remotely create a mailbox
1I have created an script which will remotely enables a users mailbox.
# This powershell script creates a remote mailbox.
# Created by Bart Timmermans
$Server = Read-Host "(Please enter the hostname of your Exchange 2010 Server)"
$User = Read-Host "Please enter the username (domainuser)"
$ServerFull = "HTTP://" + $Server + "/Powershell"
# Start session to remote Exchange 2010 server.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $ServerFull -Authentication Kerberos
Import-PSSession $Session
# Create new mailbox
Enable-Mailbox -identity $User
Exchange 2010 – Move-Mailbox maxthread removed…use New-MoveReQuest
0One of my favorite Exchange 2007 powershell migration cmdlets was the move-mailbox cmdlet in conjunction with the maxthreat parameter. Microsoft has removed the move-mailbox command from Exchange Server 2010. The new command is New-MoveRequest. A lot of people on the internet are complaining because there is no maxthread option when using the New-MoveRequest cmdlet.
The complete move process within Exchange 2010 has changed. The New-MoveRequest can move 5 mailboxes at the same time while Exchange 2007 without the maxthread option only moves one mailbox at a time. If you are responsible for the migration of mailboxes from Exchange 2003 or 2007 to 2010 you would definitely want a solution to move more mailboxes at the same time.
You should update the following file: MSExchangeMailboxReplication.exe.config. This file can be found within the bin folder of your Exchange installation path.
Use the following procedure to improve the performance of you migration/move commands:
- Make a backup of MSExchangeMailboxReplication.exe.config.
- Open notepad and edit the MSExchangeMailboxReplication.exe.config file.
- Change the MaxActiveMovesPerSourceMDB entry to 25.
- Change the MaxActiveMovesPerTargetMDB entry to 25.
- Change the MaxActiveMovesPerTargetServer entry to 25.
- Save the file.
- Restart the Microsoft Exchange Mailbox Replication service.
That should be it. If you have any questions regarding this article please feel free to contact me.
SharePoint 2010: STSADM and PowerShell
0
Source: Gary Lapointe’s blog
I found a nice article about SharePoint 2010 STSADM and PowerShell. This is a must read for everyone.
Finally, the NDA is lifted and we can openly talk about SharePoint 2010! There’s so many cool things to talk about it’s hard to decide where to begin, but as the focus of my blog has generally been on STSADM then I suppose that’s a good place to start. The first thing we should do is load the new SharePoint 4.0 Management Console which can be found under the Administrative Tools section of the start menu:

This new console window is actually just a PowerShell console which pre-loads the SharePoint PowerShell Snap-in.
SharePoint 2010: PSConfig and PowerShell
0
Source: Gary Lapointe’s blog
I found a nice article from Gary Lapointe (MVP) about SharePoint 2010 PowerShell.
If you’ve ever done a scripted install of SharePoint 2007 then you are familiar with how to script the initial farm creation using psconfig.exe. Unfortunately psconfig is still with us in SharePoint 2010 but we do have some PowerShell cmdlets which replace certain psconfig commands. At present, Beta 1 that is, there are several cmdlets that are not fully functional thus requiring us to use the psconfig equivalent – but hopefully those will be resolved with RTM.
Before we look at how to use PowerShell lets refresh our memories by looking at an install script for SharePoint 2007. I usually have two scripts, one for the first server and a second script for additional servers – here’s the first script (I’ve omitted the variable declarations):
Mastering PowerShell free e-book
0![]()
Want to know everything about PowerShell? Download a free e-book (567 pages) on PowerShell.com.
For more information click here.
To download the e-book click here.
PowerShell for Failover Clustering: Finding the Drive Letter
0Source: Microsoft’s Failover and Network Load Balancing Cluster Team.
Hi cluster scripting fans,
I often find myself looking for the drive letter(s) for a physical disk resource in a PowerShell console/script. After a bit of investigation, here is a way to do that using Cluster WMI through PowerShell:
$DiskResourceName = “Cluster Disk 2″ $DiskResource = gwmi MSCluster_Resource -Namespace root/mscluster | ?{ $_.Name -eq $DiskResourceName } $Disk = gwmi -Namespace root/mscluster -Query “Associators of {$DiskResource} Where ResultClass=MSCluster_Disk” $Partition = gwmi -Namespace root/mscluster -Query “Associators of {$Disk} Where ResultClass=MSCluster_DiskPartition” (more…)



