Comments (1)

When you have a new installation of Exchange 2010 Server and you want to move all mailboxes, including all hidden Mailboxen (Arbitration) from the default database store to a database that you created. Here is how i did it.

When you try to delete the default database you will get this message:

The Database is not empty, even though it does look empty if you do a get-mailbox for the specific database:

get-mailbox -Database "Mailbox Database 1905367170"

There is a switch that you should use if you want to see all mailboxes, even the “hidden” Arbitration mailboxes:

get-mailbox -Database "Mailbox Database 1905367170" –Arbitration

This gives a different result.

As you can se the database is n’t as empty as we first thought. To move these mailboxes to the new database you can easily pipe the result of the get-mailbox command and create new move requests for all Arbitration mailboxes:

get-mailbox -Database "Mailbox Database 1905367170" -Arbitration | New-MoveRequest –TargetDatabase "MailboxDatabase1"

Related posts

• No related posts.

Comments (1)

One of the new features of Exchange 2010 is DAG Database Availability Group. The Customer were i work now wants Exchange 2010 in a dag cluster because they have a datacenter for failback.
Because i going to implement Exchange 2010 at the customer i created a test setup.

Configuration:

Server 1 – HYPERVDC-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.90
Roles: Active Directory / Hyper-V

Server 2 – CHEK10-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.91
Roles: Exchange 2010 HT / CAS

Server 3 – CHEK10-02
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.92
Roles: Exchange 2010 HT / CAS

Server 4 – DAGEK10-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.93
Roles: Exchange 2010 MBX

Server 5 – DAGEK10-02
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.94
Roles: Exchange 2010 MBX

Creating the DAG

Groupname: DAG01
Witness Server: CHKEK10-01 (Microsoft says use one of the CAS or Hub Servers. You cannot use a DAG Server! If you want use a non Exchange 2010 server you must at the Exchange Trusted Subsystem group at the local administrators group.
Witness Directory: C:\DAG01

Add a MB server to a DAG

Setting a IP address on a Database Availability Group

With the following command you can set the DAG Database Availability Group an IP address. Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 192.168.150.96

Related posts

• No related posts.

Comments (1)

The Exchange team has released Update Rollup 4 for Exchange Server 2010 RTM (KB 982639)

KB 982639 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out starting with 5 improvements we made to prevent crashes in very unique scenarios.

• KB 980852 The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
• KB 979801 An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
• KB 980364 The Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
• KB 980353 A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
• KB 979790 An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox

We corrected a few replication issues some of you encountered.

• KB 980149 The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
• KB 981961 Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
• KB 979921 You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server

Important:
Microsoft Update does not detect Update rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG).

Download Rollup 4 for Exchange 2010 HERE

Related posts

• No related posts.

Comments (1)

When you want to use the Client Access Array function from Exchange 2010. You have to options.
1. Use the NLB function in Windows. Check this article that i blogged: Configuring NLB for Exchange 2010 for Cas load balancing.
2. When you have 2 physical load balancers in combination with a DAG cluster.

I haven’t any pre-Created CAS arrays in my hyper-v.local domain. But you would to check of there is any pre-created CAS Arrays. Run the command below. if you didn’t create a CAS Array before, you will get nothing .

Get-ClientAccessArray

Then you should create new Client Access Array. Run below Cmdlet in Exchange Management Console

New-ClientAccessArray –Name “CasArray1” –Fqdn casarray.hyper-v.local -Site “Default-First-Site-Name”


Now we have finished creating a CAS array. Then we must associate databases with this CAS Array.
Use below CMDLet to add mailbox database to CAS array. We can attach all mailbox databases at once as shown as shown  below

Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “casarray.hyper-v.local”

Related posts

• No related posts.

Comments (0)

Exchange Server 2010 Service Pack 1 Beta is available now. It incorporates a number of feature updates including: archiving and discovery enhancements, a faster Outlook Web App (OWA), upgraded mobility features, and several improvements in the management UI. In short it helps you achieve new levels of reliability and performance by delivering features that help to simplify your administration, protect your communications, and delight your customers by meeting their demands for greater business mobility.

Microsoft Download Center Link is here and direct downloadable exe file link is available below.

File Name: Exchange2010-SP1-Beta-x64.exe
Version: 14.01.0180.002
Date Published: 6/5/2010
Language: English
Download Size: 532.5 MB

Related posts

• No related posts.

Comments (0)

Exchange’s dependence on the Client Access Server (CAS) role has increased dramatically in Exchange 2010.  This is because, in Exchange 2010, on-network Outlook MAPI connectivity now connects to a mailbox through the CAS role via the RPC Client Access Service.  As a result, high availability of the CAS role is crucial since any failure of CAS could affect Outlook client connectivity.  For smaller implementations or those where the limitations of native Windows Network Load Balancing (NLB) are not a major problem

You need two or more Exchange 2010 servers (each with two NICs) with the CAS role installed have been deployed, you are ready to start configuring NLB to provide high availability and load balancing.  First, you must allocate a dedicated private IP address and create an associated A record in DNS for the NLB cluster. 

This IP address and name are what clients will connect to and against which the ClientAccessArray will be created.  In this blog post, I will use 192.168.150.95 and casarray.hyper-v.local
To simplify the management of your NLB cluster members, I recommend that you name each NIC’s network connection so that it is easy to understand what function the NIC serves.  For example, as depicted below, I have named the connections “LAN” (used for communication with clients and servers on the network) and “NLB” (used for internal NLB heartbeat).  This process should be repeated on all NLB cluster members.

IP configuration:
Server 1:
LAN:
IP: 192.168.150.90
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1

Server 2:
LAN:
IP: 192.168.150.91
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1

Configuring NLB – First Member

On each NLB cluster member, NLB must be installed.  With Windows 2008 R2, this can be completed simply by running the command “ServerManagerCmd -i NLB” via a command prompt.  Once NLB has been installed, launch the Network Load Balancing Manager to continue the configuration process.

To create your new cluster, you can right-click Network Load Balancing Clusters or simply click Cluster, New.  In the New Cluster wizard, enter the name of the first server in the NLB cluster (for example, CHEK10-01) and click Connect.  This will display the available NICs on the server, at which point the NLB NIC should be chosen before clicking Next.

Since this is the first member of the NLB cluster, you can leave the all of the Host Parameters at their default values, as depicted below.  Please note that the Priority value should be configured as 1 for the first member.

Next we must configure the IP address and subnet mask of the NLB cluster, which is the IP address for which we created a DNS A record at the very beginning of this process.  In this example, this would be 192.168.150.95 and 255.255.255.0, respectively.

For the Cluster Parameters, we want to enter the FQDN of the DNS A record we created at the very beginning of this process (casarray.hyper-v.local).  In addition, Unicast should be selected as the desired clustered operation mode.

I lieve the Port Rules how they are and end with Finish

Let the NLB cluster converge with its first member and you should eventually see the cluster report success.

Now you can proceed with adding your second cluster member.

Configuring NLB – Second/Subsequent Member

After the configuration of the NLB cluster itself and the first NLB cluster member has been completed, you are ready to add additional members.  Provided that NLB has been installed, you can simply right-click on your NLB cluster in the Network Load Balancing Manager and click Add Host To Cluster.

Enter the name of the second NLB cluster member, for example CHEK10-02, and click Connect.  Be sure to choose the NLB LAN NIC and click Next.

On the Host Parameters screen, ensure that the Priority is set to 2 (or as appropriate, depending on how many cluster members you have) and click Next.

Confirm that your port rules are accurate and, if they are, click Finish to add your second NLB cluster member.

Let the NLB cluster converge with the new member and, eventually, it should report success.

At this point, you have an NLB cluster with two members!

Next configure CASARRAY.

Related posts

• No related posts.

Comments (1)

Some times you want to hide a Distribution Group from de Global Address List (GAL).
In Exchange 2010 this is a simple thing
1. Open the properties from the Distribution Group.

2. Go to the Tab Advanced

3. Set V by Hide group from Exchange address list

Related posts

• No related posts.

Comments (0)

The Microsoft’s current documentation you’ll still need to shutdown your guest OS. First up, unless your Guest OS is also R2, you’ll need to install the hotfix noted above. However, rather than having to note the cluster’s MAC address, you’ll simply need to change the Hyper-V guest settings to enable MAC Spoofing on the NIC which you configured for NLB:

Related posts

• XP Domain users modify rechten c drive (0)
• XP client geeft Deployment & Inventory error in SCE 2007 (0)
• Windows XP Client download geen updates van SCE 2007 Error 0×80244019 (0)
• Windows Server Backup Applications Grijs VSS snapin Exchange 2007 SP2. (0)
• Windows Server 2008 R2 Beta Reviewers Guide (0)

Comments (0)

If you open de Exchange Management Shell and you run the following powershell command:
Get-ExchangeServer | fl name,edition,admindisplayversion you get the Build Number from your Exchange 2007 Servers

Exchange Server 2010

Related posts

• FREE eBook: The SysAdmin Handbook (0)
• Windows 2008 R2, Hyper V2, Exchange 2010, MDT Video’s (0)
• Weekend Nieuws (0)
• SP2 voor Exchange 2007 wordt vrijgegeven in het derde kwartaal dit jaar (0)
• Installeren Exchange 2010 in Exchange 2007 domain met Coexistence (0)

Comments (0)

Exchange Team announced that SP1 for Exchange 2010 is coming with a lot new features

I highlighted the things with I like from the coming update. It’s a whole list but i thing with this update is Exchange 2010 SP1 the best version ever!!!

A list of al new things in Exchange 2010 SP1:

Archiving:
- Personal Archive to a different mailbox database from their primary mailbox
- You can import historical e-mail data from .PST files, directly into Exchange
- delegate access to a user’s Personal Archive
- SP1 updates the Exchange Management Console with new tools to create Retention Policy Tags
- support access to a user’s Personal Archive with Outlook 2007 Coming with A update

Outlook Web App
- Delete, mark as read, and categorize operations running asynchronously, these actions feel instantaneous to the user
- Attaching a very large file, will not block the rest of the OWA experience
- Sharing calendars to anonymous viewers via the web if you enable this.
- OWA themes back
- Reading pane can be placed on the bottom or the right side

Mobile:
- Support for send-as
- Support for notifying the user if their device has been placed on block or quarantine by their admin
- Full implementation of conversation view
- To sync only unique parts of messages.
- Setting up mobile device to access mail via POP/IMAP/SMTP, information is available in OWA.

New Management UI
- Create/configure Retention Tags + Retention Policies in EMC
- Configure Transport Rules in ECP
- Configure Journal Rules in ECP
- Configure MailTips in ECP
- Provision and configure the Personal Archive in ECP
- Configure Litigation Hold in ECP & EMC
- Configure Allow/Block/Quarantine mobile device policies in ECP
- RBAC role management in ECP
- Configure Database Availability Group (DAG) IP Addresses and Alternate Witness Server in EMC
- Recursive public folder settings management (including permissions) in EMC

Read the whole article at HERE.

Related posts

• FREE eBook: The SysAdmin Handbook (0)
• Exchange Tools (0)
• Eisen om Exchange 2010 te kunnen installeren (1)
• Windows 2008 R2, Hyper V2, Exchange 2010, MDT Video’s (0)
• Rollup 8 voor Exchange 2007 SP1 (0)