I just found a bug in my lab environment and wanted to share the information with you. My lab environment is a small environment that consists of one domain controller (Windows 2008 R2) and two Exchange 2013 RTM servers (based on Windows 2012 Server), these holds both the Mailbox and the CAS role. I found
I’ve updated a script that was intended for installing prerequisites for Exchange 2010 that were released by a couple of peoples (Anderson Patricio, Pat Richard and Bhargav Shukla). This script have now been updated and applies to Exchange 2013. It will help you with installing all prerequisites (features) plus the FilterPack(s) and the Unified Communications
Published: 2013-02-25 Updated: – Version: 1.0 This script was developed because there was a need to configure every Shared Mailbox with a office value. In Exchange the value is called “Office” while in Active Directory this value is called “physicalDeliveryOfficeName”. The script is retrieving all shared mailboxes where the office value isn’t populated and creates
I suppose you already have, but if you haven’t read my previous parts in this Exchange 2013 serie, have a look at the links below. Part 1: Complete guide of how to perform the installation Part 2: How to do the Basic configuration This part will include details on how the configuration could be made
If you haven’t read it already, I did post a complete guide for installing Exchange 2013, it can be found here. That was part 1, now it’s time for part 2. Which of course is the configuration of the server setup. We have lots of changes between how you configured Exchange 2007/2010 and 2013. First
Since Exchange Server 2013 beta was released yesterday I’m glad to announce that my first installation is done and here’s a complete walkthrough. My setup is basic, using one server as domain controller, Windows 2008 R2. Initially for Exchange I’m using 3 servers, 1 server for the CAS role and 2 servers for the Mailbox
Wrote a basic PowerShell script that searches all computers listed in the clients.txt file. Saving the pst files into the destination path. For each computer, a folder is created with the corresponding computer name so that the PST files is collected per client. Before the PST Capture Tool was released I wrote a post about
Published: 2012-01-25 Updated: – Version: 1.0 A time ago I was developing a PowerShell script for finding all PST files on a drive and copying them to a folder. Type in a drive that should be searched and the UNC path to save them on The script have been tested and verified on Exchange 2010
I was getting an error when connecting to the Exchange Organization. This is documented by Quest and is a bug and there is an official workaround until next release of QMS (hopefully). The “KB” at Quest’s place is named “SOL67917″. This error is happening when trying to connect to an Exchange 2010 Organization without
Published: 2010-12-16 Updated: – Version: 1.0 Background Information I hope you will find this article helpful and interesting to read. I just want to mention to everyone that’s reading this article, it’s not any type of best practice, it’s just a sample of how it could be installed and configured in a Lab environment.
