There’s a mystery about early Exchange 2010 deployments: despite the much-publicized removal of single instance storage, sizes of Exchange 2010 databases have not increased. The same message has trickling back from all quarters, as businesses go live: after moving mailboxes, database sizes in Exchange 2010 are roughly the same as they were in Exchange 2007.
In a previous article I mentioned how to create users and computers in active directory, the first stage of testing the PST Importer (and ESA). The next step is to go to Exchange and create mailboxes to the users that we just created and for further comfortable management, add access permissions to them where needed.
Since I started deploying more and more Windows Server 2008 R2 virtual machines I have noticed an issue that the standard VMware Tools Display Driver has with Windows Server 2008, 2008 R2 and seemingly Vista too. It seems to occur at random times; you’ll definitely know when it strikes, as your VM’s console will completely freeze up on you.
Normal network activity to and from the VM seems function normally so the underlying OS is obviously fine to continue working. You can even connect via RDP to the VM and use it that way if you wish. However lacking a console session to the VM is not exactly very useful. A restart of the VM will sort it out temporarily, but again this is not very helpful as the issue will undoubtedly occur again. Here are my tips to counter this unpleasant isssue.
If you currently allow your end-users to manage distribution group membership in a previous version of Exchange, you may be interested to know that like many things, the process for enabling this is completely different in Exchange 2010. This is because distribution group membership management permissions are now delegated through Role Based Access Control (RBAC).
