All posts tagged Microsoft

Exchange 2010 RC

Microsoft has released Exchange 2010 Release Candidate today. The release candidate is available as VHD and as installable version. The release candidate can be installed on both Windows 2008 and Windows 2008 R2. With this Exchange 2010 will be the only version of Exchange which is supported to run on Windows 2008 R2 for now. Several sources report that Exchange 2007 will not be supported on Windows  2008 R2, even when service pack 2 will be available.

When you already installed the Exchange 2010 beta version you can simply upgrade it to the RC. Besides this Exchange 2010 can be installed in an existing Exchange 2007 or Exchange 2003 environment. In the case of Exchange 2007 you will need to install Exchange 2007 service pack 2 first, this will be available later this month.

When you are getting curious you can download Exchange 2010 RC from the site below.



Microsoft is working very hard on UM solutions, OCS is one of those products. On OCSblogs you can find a collection of interessting blogs about OCS.


Technet Edge

During surfing I discovered this site. The site contains a lot of nice movies with interviews with people from Microsoft about various products one of them is the new OCS which will be launched in february.


Microsoft has release version 1.0 of the Exchange System Manager for Windows Vista. With this tool you can manage your Exchange 2003 server from a Vista machine. There are a few restrictions in the software, belof a few of them:

  • SMTP current session node is not supported (SMTPadmin.dll cannot be registered).
  • NNTP property view is not supported (NNTPadmin.dll cannot be registered).
  • Installing Exchange System Manager on the same computer as Microsoft Office Outlook is not supported, because MAPI CDO cannot be installed.
  • You may encounter the following issues during uninstall:
    • If Exchange System Manager is open during the uninstall process, Microsoft Management Console (MMC) is likely to crash. To resolve this, manually close the Exchange System Manager.
    • If the MAPI CDO package was uninstalled manually before uninstalling the Exchange System Manager, a runtime error may appear. This error can be ignored and the uninstall process will complete successfully.
  • Would you like to have this tool, then use the link below to download it.


    In this tutorial we will have a look which steps are needed to implement an Edge Transport server in an Exchange 2007 environment.

    Installing the Edge Transport server is not very hard and configuring it is not a lot of work. We could start with the setup which will tell us which prerequisites are needed. If you would like to prevent this then download and install the following software before you start the setup:

    The Active Directory Application Mode (ADAM) will let the Edge Transport server check the Active Dire tory if a user exists and if not block the e-mail.

    During the setup we choose the option Custom Exchange Server Installation with this option we can choose that we only install the Edge Transport Server on this server. When we click on next we will get the following screen:

    Here we only select the Edge Transport Server Role and click on the next button

    Exchange will first run some tests: it will check if all necessary software is installed and the system meets the systemrequirements. As you can see this is not the case in my situation. I am trying to install the Edge Transport server on a 32-bit OS. This is not supported by Microsoft, in this case it doesn’t matter because we run it in a test environment. If installing it in a production environment install it on a server with a 64-bit OS. When clicking on install we continue with the installation.

    When the installation is finished we can start the Exchange Management Console, this will look like the screenshot below:

    You can see that a few tabs are the same as on the Hub Transport Server. These tabs are empty at this moment but will be filled automatically during the configuration.

    Because the Edge Transport Server and Hub Transport Server not know of eachother we first need to export the Edge Subscription and then import it on the Hub Transport Server. This can be done with the following command: New-EdgeSubscription by executing it with the correct parameters a XML file is created which can be imported on the Hub Transport Server.

    The following command will create a file in the root of C.

    new-EdgeSubscription -filename “c:\Edgeexport.xml”

    When you would like to put it in a directory first create the directory before executing the command.

    The next step is to import the Edge Subscription on the Hub Transport server. Please keep in mind that this needs to be done within a few hours, else you can’t subscribe the Edge to the Hub Transport. To do this we go via the Organization Configuration to the Hub Transport Server and select the tab Edge Subscriptions. Then select New Edge Subscription from the right menu or click somewhere in the white space of the tab with the right mouse button and select the option. When you have done this a wizard will be started.

    Via browse select the file just created and select the correct AD Site.  When you did this click on New. The option to create a new send connector on the Hub Transport Server is on by default. This connector will be configured to only send mail to the internet via the Edge Transport Server.

    When the file is imported and the connector is created you will get a warning. The Hub Transport Server and Edge Transport Server need to communicate via port 50636.

    After completing this the Hub Transport server is ready for synchronisation with the Edge Transport Server. But first we need to configure some things on the Edge Transport Server before we can really start the synchronisation.

    First we need to create a new SMTP Receive Connector on the Edge Transport Server. This can be done via the Exchange Management Console. When we start it we need to go via Organization configuration to the Edge Transport Server and select the tab Receive connectors. By selecting the option New SMTP Receive Connector from the right side of the screen we will get a wizard. Within the wizard we will seect the option to create a connector of the type Internal. When we have done this we click on next, you will get the following screen:

    Here we fill in the IP-address of the Hub Transport Server with a subnet mask of, this will only allow this IP-address. When we click on next we get a short summary and after pushing the button new the connector is created.

    Now we did all preparations it’s time to start the Edge Synchronisation, this can be done via the following command Start-EdgeSynchronization

    When everything is configured OK we will see that both tasks have the status Success. When you go back to the Exchange Management Console you can see that somethings are imported.

    The accepted domains are added to the Edge Transport Server and 2 new Send Connectors are created.

    When we now go back to the Hub Transport Server you will see that also there 2 new Send Connectors are created.

    One connector is used for traffic to the internet, this will be send to the Edge Transport Server. The other connector is used for receiving mail from the Edge Transport Server.

    Now the only things that are needed to be configured are the rules for the different agents. This will fall out of this scope of this tutorial but are described in an earlier tutorial Install Anti-spam Agents on the Hub Transport server

    Besides that users can whipe there smartphone/pda within the OWA administrator have the ActiveSync Web Administration tool. This tool is completely web-based and makes it possible for adminstrators to:

    • View a list of all devices that are being used by any user
    • Select/De-select devices to be remotely erased
    • View the status of pending remote erase requests for each device
    • View a transaction log that indicates which administrators have issued remote erase commands, in addition to the devices those commands pertained to


    As you may already know a lot of funtions from Exchange 2007 are using certificates. Microsoft has released a tool a while ago which can check certificates that are used for certificate based authentication for ActivSync. I just found it while surfing the internet en thought maybe it’s nice so that’s why I published it on my site. You can download the tool via the link below:


    During my visit on the forum I found a question on how you can see which user has an ActiveSync device attached to their profile. Quite a good question I thought and I decided to search on Technet and Google. There is a Powershell command which can give you an overview of the users who have attached an ActivSync device to their profile:

    Get-CASMailbox | where {$_.HasActiveSyncDevicePartnership} | select Name

    During some searching on the forums, I read a lot of messages about problems after installing the last rollup packs for Exchange. Rollup pack 3 for Exchange 2007 SP1 as wel as rollup pack 7 for Exchange 2007 RTM can cause problems. Microsoft has admitted that there are issues with it and has released some solutions to solve this issues. Have a look at the following site to find out how to solve it.


    Outlook Web Access

    It’s time for a new tutorial, this one goes about Outlook Web Access. In this tutorial I will discuss allthe possibilities that you can configure including some certificate things. I’ve seen there where some typo’s in some English tutorials sorry for that, I think I wanted to translate them to fast 😉 I will soon fix all the errors on it, sorry for the inconvenience.