codingChris

Filtering Exchange PowerShell Locally

As an Exchange developer, it’s quite possible you’ve run across this error message:

Assignment statements are not allowed in restricted language mode or a Data section.

Or you’ve possibly seen this one:

Script block literals are not allowed in restricted language mode or a Data section.

While it’s quite easy to change the PSLanguageMode to FullLanguage instead of RestrictedLanguage it may be that you can’t do that for one reason or another.  Here’s a small method I put together for filtering the results locally.  Use your discretion about the size of your resultsets to bring back.

public IEnumerable<PSObject> ApplyPSFilter(IEnumerable psData, ScriptBlock scriptBlock)
{
    using (var ps = System.Management.Automation.PowerShell.Create())
    {
	    ps.AddCommand("Where-Object");
	    ps.AddParameter("FilterScript", scriptBlock);

	    return ps.Invoke(psData);
    }
}

Creating Exchange 2013 Mailbox in C#

Holy moly it’s been a long time since I posted.  Here’s a quick code snippet on using C# to create a mailbox to hopefully kick a string of posts off.  This creates an AD account for the user unlike my previous article on creating a mailbox in Exchange 2010.  And since I listed a gotcha in that article, I’ll leave a tip in this one after the code. 😀

var psc = new PSCommand();

psc.AddCommand("New-Mailbox");
psc.AddParameter("Name", newUser.UserName);
psc.AddParameter("UserPrincipalName", upn);
psc.AddParameter("Alias", upn);
psc.AddParameter("PrimarySmtpAddress", string.Format("{0}@{1}", newUser.UserName, domainName).ToLower());
psc.AddParameter("OrganizationalUnit", domainDn);
psc.AddParameter("SamAccountName", samAccount);
psc.AddParameter("Password", _ps.CreateSecurePassword("mysupersecretpassword"));
psc.AddParameter("DomainController", domainController);

PowerShell ps = PowerShell.Create();
ps.Commands = psc;

try
{
    var result = ps.Invoke();
    if (!ps.HadErrors)
    {
        Console.WriteLine("Congrats! User created successfully");
    }
}
catch (RemoteException ex)
{
   //Error conditions here...
}

Easy enough.  Now for the tip.  If you specify the PrimarySmtpAddress it will automatically set the EmailAddressPolicyEnabled value to false.  So leave that parameter out if it’s important for your org.

Creating Exchange 2010 Mailboxes in C#

Wow, it’s been a while! I had full intentions of creating regular posts but that kind of slipped away. So I’ll make this one fairly short and just highlight the basics of creating an Exchange 2010 mailbox via remote code. Nothing fancy, but I will highlight one gotcha that I encountered when updating our user creation code after we migrated from Exchange 2003. Keep in mind that Exchange 2010 is built on Powershell and as such, all of connections and manipulation must be done through it.

First, we want to add our usings…

using System.Management.Automation;
using System.Management.Automation.Remoting;
using System.Management.Automation.Runspaces;

Next, we’re going to create the PSCredential, the WSManConnectionInfo, and the Runspace. We’ll then create a powershell command, invoke the powershell with the command and cross our fingers. 😀

PSCredential newCred = (PSCredential)null;
WSManConnectionInfo connectionInfo = new WSManConnectionInfo(new Uri("http://exchangeserver01.my.domain/powershell?serializationLevel=Full"), 
    "http://schemas.microsoft.com/powershell/Microsoft.Exchange", newCred);
connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Kerberos;
Runspace runspace = RunspaceFactory.CreateRunspace(connectionInfo);
PowerShell powershell = PowerShell.Create();
                        
PSCommand command = new PSCommand();
command.AddCommand("Enable-Mailbox");
command.AddParameter("Identity", user.Guid.ToString());
command.AddParameter("Alias", user.UserName);
command.AddParameter("DomainController", ConnectingServer);
powershell.Commands = command;

try
{
    runspace.Open();
    powershell.Runspace = runspace;
    Collection results = powershell.Invoke();
}
catch (Exception ex)
{
    string er = ex.InnerException.ToString();
}
finally
{
    runspace.Dispose();
    runspace = null;

    powershell.Dispose();
    powershell = null;
                    
}

Now, a couple of things to note…

1) My gotcha…You don’t find a lot of information about creating a PSCredential using the credentials of the currently logged in user. Even the MSDN documentation only shows one constructor where you pass in a username and password. After searching around, some trial and error, I finally found this post detailing creating the PSCredential using Windows Authentication with no username or password supplied. Supplying credentials isn’t a problem, but as we log the account creations, and we didn’t have this issue when creating boxes in 2003, I wanted as seamless transition as possible. So this code just replaced the old code and my other Admins had no idea anything was different.

2) Accounts for my users need to be created at one of many different sites, and many times it’s not a site I’m currently at. So, the account is created on the ‘local to them’ server so they can immediately login and not need to wait for replication. Because of this, Exchange needs to know what server holds the account. If you don’t need this functionality, you can remove the DomainController command parameter above.

3) It is important to properly dispose of the runspace and powershell objects. Make sure this is done.