Remko Weijnen's Blog (Remko's Blog)

About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like

Archive for the ‘PowerShell’ Category

Construct AQS date range with PowerShell

imageFor a script I needed to create an AQS (Advanced Query Syntax) Query that contained a date range.

An example of such is a range is: date:11/05/04..11/10/04

However we need to account for regional settings where for example the data seperator and the order of day and month may be different.

In my example I wanted to match any data that is 30 days or older so let’s do this in PowerShell:


  • Filed under: PowerShell
  • Exchange Move Mailbox Experiences Part 3

    In Part 2 I showed some details about Mailbox Rule corruptions that can disturb Mailbox Moves.

    For this part the topic is Mailbox size, which can be an important factor in deciding which mailboxes you want to move first.

    In my case the mailbox size was important because we agreed to move smaller mailboxes during the day but larger mailboxes only outside working hours.

    For Exchange 2010 mailboxes it’s very easy to obtain the size using PowerShell.


    Remko Weijnen31334.87 MB (36,564,183 bytes

    But how can we get the Mailbox Size for Exchange 2003 mailboxes?



    Inline arrays in PowerShell

    imageSometimes I want to process a list of “things” easily in PowerShell where the list is not in an external file but in the script itself.

    Ideally this list would not be separated by e.g. a comma so it can be easily copy/pasted from external data sources.

    Something like this:


  • Filed under: PowerShell
  • I am currently creating a PowerShell script that creates a user with all needed Active Directory attributes, Exchange mailbox, (TS) Home- and Profile directories and so on.

    In such a script you can easily get failures because of Active Directory replication.


    Function below can be used to check if a given Username exists in Active Directory:

    Get smallest Exchange Database in PowerShell


    I needed to adapt some scripts that create a user with mailbox for Exchange 2010. The existing scripts had a hardcoded database for new mailboxes.

    I wanted the mailbox to be created in the smallest database, but how do we determine this?

    For Exchange 2010 this is fairly easy using PowerShell:

    Set Exchange Product Key with PowerShell


    By default Exchange 2007 and 2010 are installed in Trial mode so before going into production you need to enter the Product Key.

    The Exchange Management Console will warn you if one or more servers are still in trial mode:




    I am currently working on an Exchange migration from 2003 to 2010. For the implementation of a load balancing solution for the CAS/HUB servers I needed to set Static RPC Ports for the RPC Client Access Service and the Exchange Address Book Service.

    The procedure of changing these ports is described on the Technet Wiki: Configure Static RPC Ports on an Exchange 2010 Client Access Server

    Since I am lazy I decided to do this with a PowerShell script that would automatically do this for all CAS/HUB servers in my 2010 environment.


    AD Internals: Display RID Allocation Pools

    In my previous post I wrote about a problem I had with duplicate RID Allocation pools.

    But how do we get more insight into these RID Allocation pools?

    The DCDIAG tool can display this information per domain controleler using the following syntax

    Example output:

    DCDiag Ridmanager Test

    But where in Active Directory is this information stored and can we display it for all Domain Controllers at once for larger environments?


    SNAGHTML1ca684cToday I was testing the installation of Exchange 2010 in a VMWare sandbox environment. We created the sandbox to test migration from a 2003 AD and Exchange environment to 2008 R2 with Exchange 2010.

    We used a P2V to get real copies of the Active Directory and the AD upgrade to 2008 R2 was already tested.

    But during the Exchange installation in the sandbox I got the following error:

    The well-known object entry on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=zorg,DC=local points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.