This section is taken from Henrik Walter Blog, he has excellent article series also showing DAG in much Details, links to his blog is fallows, Henrik has been good mentor to many of us, not only with technical aspect but also his professionalism in my opinion is top quality.
Before we can install the Exchange 2010 Server roles on the two Windows 2008 R2 servers, we must first make sure the required features and components have been installed. The following components should be installed on all Exchange 2010 server roles:
Now we are ready to move on with installing DAG. The configuration we are doing is very basic here. We will use ForeFront to achieve redundancy for OWA and Outlook anywhere later on, most likely on part 4, for now we will move on finishing the configuration of DAG. As reminder our goal is to bring two exchange 2010 servers in DAG configuration and make our messaging environment redundant, if one server goes down, the other server will pick up the production users. As you know DAG member can be added or taken out from DAG (Data Availability Group) any time. In very basic thinking the way DAG works is to assign active databases and passive databases to each DAG members. Renaming Databases to some sort of meaningful names seems to be the way to go. Remember Storage groups no longer exist in Exchange 2010 and logs are associating with each database.
***IF you go to ADUC you will see computer object called “DAG1” if you go to DNS you will see below A and PTR (if reverse zone exist), after creating the DAG group and assigning IP to it.***
*** We recommend that you use an Exchange 2010 Hub Transport server in the Active Directory site containing the DAG. This allows the witness server and directory to remain under the control of an Exchange administrator.***
*** If the witness server you specify isn’t an Exchange 2010 server, you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server prior to creating the DAG. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. ***
*** Hub Transport server that doesn’t have the Mailbox server role installed, and it will automatically create the default directory***
Creating DAG
Go to EMC Under organization configuration select
New Data Base Availability Group and fallow the simple wizard.
As you can see the Witness Server and Witness directory is not selected, DAG is configured with a witness server and witness directory, the DAG Wizard will search and locate the HTS server and create everything it needs automatically. (Witness Server = HTS server, Witness Directory will be on the HTS server also)
After upgrading the exchange server 2010 SP2 servers to SP3. Everything went well after 6hr 30 min SP3 finally installed successfully, however after the new update “Microsoft Exchange System Attendant Service” do not want to start.
While trying to start the service it threw an error at every time it failed. Error 14001: the application has failed to start because its side-by-side…
When you try to crate new mailbox database you get error below
——————————————————– Microsoft Exchange Error ——————————————————– Failed to mount database ‘MAILDB1’. MAILDB1 Failed Error: Couldn’t mount the database that you specified. Specified database: MAILDB1; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)
. [Database: MAILDB1, Server: MAIL-SRV-EXCH.mailleisureplc.com]. An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)
. [Database: MAILDB1, Server: MAIL-SRV-EXCH.mailleisureplc.com] An Active Manager operation failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)
. [Server: MAIL-SRV-EXCH.mailleisureplc.com] MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)
——————————————————– OK ——————————————————–
SOLUTION:
Microsoft notes that the issue is related to having conflicting Domain Controller and Global Catalogue Server entries. So do the following:
1. Open EMC and right-click on “Organization Configuration”. Choose “Modify Configuration Domain Controller”.
2. Specify the domain and the DC.
3. Open EMC and right-click on “Recipient Configuration”. Choose “Modify Recipient Scope”.
4. Specify the global catalog server. Make sure it is the same as the chosen DC.
During installation of the Mailbox Server a new Exchange Server 2010 Mailbox Database will be automatically created. After installation its best to make sure that this database is moved from the default location to an alternate location for recovery and performance reasons.
A new Public Folder database will also be automatically created on the new Mailbox Server. The hierarchy, which is the structure of all Public Folders will be automatically replicated between all Public Folder Databases in the entire organization. The content replication of the Public Folders will have to be configured manually though.
To replicate the Offline Address Book and Free/Busy folders from Exchange Server 2003 to Exchange Server 2010 open the Exchange System Manager on the Exchange Server 2003 server and navigate to the System Folders in the ‘Folders’ folder in the First Administrative Group Navigate to the first Offline Address Book folder, right click it and select “All Tasks…”. The next is to select “Manage Settings”.
If you want to toggle between the System Folders and the normal Public Folders, navigate to the Public Folders, right click the Public Folders and select “View System Folders” or “View Public Folders”.
Public folder replication
The “Manage Public Folder Settings wizard” will appear. Click Next on the Welcome page and select the “Modify lists of replica servers”. Follow the wizard and add the Exchange Server 2010 Mailbox Server role as a new replica. When finished, the folder and all its subfolders will be replicated to the Exchange Server 2010 Public Folder database. Repeat this step for the second Offline Address Book folder and the Schedule+ Free Busy folder.
Note: When the “Manage Settings” option is not available you can select “Properties” and select the replication tab to add the Exchange Server 2010 Public Folder Database.
Note: replication of public folders can take quite some time.
The (default) Public Folder that are located on the Exchange Server 2010 Mailbox Server should be replicated to the Exchange Server 2003 Mailbox Server. To accomplish this logon to the Exchange Server 2010 Mailbox Server, open the Exchange Management Console and navigate to the Tools node. Under the Tools node open the Public Folder Management Console.
Right click the Offline Address Book in the results pane, select Properties and click the Replication tab.
Add the Exchange Server 2003 Mailbox Server to the replica list, the contents will now be replicated to the Exchange Server 2003 Mailbox Server. Be aware that Public Folder replication is a low priority mechanism, so it takes some time before both Public Folder databases are in sync.
Repeat these steps for the Schedule+ Free/Busy folder.
Offline Address Book generation
Changing the Offline Address Book generation isn’t the most difficult part of a migration. Logon to the new Exchange 2010 Server and open the Exchange Management Console. In the navigation pane, navigate to the Organization Configuration and select the Mailbox option. In the results pane, select the Offline Address Book tab. Right here you’ll see that the ‘old’ 2003 Mailbox Server is the Offline Address Book generation server. Right click this server and select ‘Move…’. The Move Offline Address Book wizard will appear, use the Browse button to select the Exchange 2010 Mailbox Server Role as the new generation server. Click the Move button to finish the wizard. When finished click the Finish button.
$mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
if( $mountedMdb -ne $null )
{
$dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagementWkGuid;
$dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
if( $dmRoleGroup -ne $null )
{
Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
}
}
}
}
” was run: “Couldn’t mount the database that you specified. Specified database: Mailbox Database 0530853962; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database ‘Mailbox Database 0530853962’. Error: Could not find a part of the path ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0530853962’. [Database: Mailbox Database 0530853962, Server: MAIL-SRV-EXCH.mailleisureplc.com].”. Couldn’t mount the database that you specified. Specified database: Mailbox Database 0530853962; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database ‘Mailbox Database 0530853962’. Error: Could not find a part of the path ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0530853962’. [Database: Mailbox Database 0530853962, Server: MAIL-SRV-EXCH.mailleisureplc.com]. An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database ‘Mailbox Database 0530853962’. Error: Could not find a part of the path ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0530853962’. [Database: Mailbox Database 0530853962, Server: MAIL-SRV-EXCH.mailleisureplc.com] An Active Manager operation failed with a transient error. Please retry the operation. Error: An error occurred while preparing to mount database ‘Mailbox Database 0530853962’. Error: Could not find a part of the path ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0530853962’. [Server: MAIL-SRV-EXCH.mailleisureplc.com] An error occurred while preparing to mount database ‘Mailbox Database 0530853962’. Error: Could not find a part of the path ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0530853962’. Could not find a part of the path ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0530853962’. Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp Elapsed Time: 00:25:50 Finalizing Setup Cancelled
SOLUTION:
Check the output of ‘get-mailboxdatabase |fl’ and any events in event viewer. Does the folder exchange 2010 exists alongwith subfolders, if not can you create it manually
Make sure that all folders exist that are given with the error and re-created it by hand, then run the setup again this will complete the Mailbox role install. (THIS WORKED FOR ME)
In my error above the folder ‘Mailbox Database 0530853962’ didn’t exist in C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\ just created a new folder called ‘Mailbox Database 0530853962’ and re-run the installer for mailbox role install and that worked.
OR
1: Remove the Database from EMC and if you are not able to remove it than. 2: Go to Adsiedit.msc…>Configuration…>Services…>Microsoft Exchange…>ORG…>First Admin Group…>Exchange Admin Group…>Database…> Check the name “Mailbox Database 0530853962” and delete it. After deleting it from here open EMC and you should not get that error message.
Getting the error on Hub Transport Role installation step
Here are some points you need to check:
1. Check Manage auditing and security log Properties
Administative Tools > Local Security Policy > Local Policies > User Rights Assignment > Manage auditing and security
Exchance Servers.
2. Check Exchange Trusted Subsystem
1)Open Active Directory Users and Computers
2)Under domain name (For example contoso.com),navigate to the Builtin Container,on
the right hand side select the Administrator group,goto the properties
3)Click members tab and add Exchange Trusted Subsystem
4)Click ok twice
5)Reboot the Exchange server
6)Rerun the Exchange setup
3. Check IPv6 enable ?
To move offline address book generation using Exchange Management Console
Open the Exchange Management Console.
Expand Microsoft Exchange, expand Organization Configuration, and then select Mailbox.
In the results pane, click the Offline Address Book tab.
On the Offline Address Book tab, select the offline address book you want to move. In the action pane, click Move.
After the Move Offline Address Book Wizard appears, select the new server to host the offline address book generation by using the Browse button and then click Move.
To close the wizard, click Finish.
To use the Exchange Management Shell to move offline address book generation
Remove a public folder database from a Mailbox server
Step 1: Delete unnecessary public folders
Step 2: Move the public folder replicas to another server
Step 3: Associate mailbox databases with another default public folder database
Step 4: Remove the public folder database Note: If you successfully perform Step 1 through Step 4 and you receive an error message stating that the public folder database can’t be removed because it contains replicas, you may need to wait several hours for public folder replication to finish.
Verify that all public folders have been removed by running
Get-PublicFolderStatistics
To identify the public folder databases that are associated with all mailbox databases, run the following command
Get-MailboxDatabase | ft Name,PublicFolderDatabase
To move all public folder content from Server01 to Server02, run the following command:
To resolve this problem, open Task Manager, and then end the Powershell.exe process. The Powershell.exe process will restart immediately and then complete the uninstall operation.
You must move the data directory outside of your public root. (See advanced install settings)
This section describes how to install ownCloud on Windows with IIS.
It assumes that you have a vanilla, non-IIS enabled Windows machine – Windows 7 or Server 2008. After enabling IIS, the steps are essentially identical for Windows 7 and Windows Server 2008.
For installation, physical access or a remote desktop connection is required. You should leverage MySQL as the back end database for ownCloud. If you do not want to use MySQL, it is possible to use Postgres or SQLite instead. Microsoft SQL Server is not yet support.
Enabling SSL is not yet covered by this section.
If you make your desktop machine or server available outside your LAN, you must maintain it. Monitor the logs, manage the access, apply patches to avoid compromising the system at large.
There are 4 primary steps to the installation, and then a 5th step required for configuring everything to allow files larger than the default 2MB.
Install IIS with CGI support – enable IIS on your Windows machine.
Install PHP – Grab, download and install PHP.
Install MySQL – Setup the MySQL server manager and enable ownCloud to create an instance.
Install ownCloud – The whole reason we are here!
Configure upload sizes and timeouts to enable large file uploads – So that you can upload larger files.
Activate IIS with CGI Support
Windows 7
Go to Start –> Control Panel –> Programs.
Under Programs and Features, there is link titled Turn Windows Features on and Off. Click on it.
There is a box labeled Internet Information Services, expand it.
Expand World Wide Web Services and all the folders underneath.
Select the folders as illustrated in the picture below to get your IIS server up and running.
Windows Features required for ownCloud on Windows 7
You do not need an FTP server running, so you should tune that feature off for your server. You definitely need the IIS Management Console, as that is the easiest way to start, stop, restart you server, as well as where you change certificate options and manage items like file upload size. You must check the CGI box under Application Development Features, because CGI is how you enable PHP on IIS.
You have to turn off WebDAV publishing or the Windows WebDAV conflicts with the ownCloud WebDAV interface. This might already be turned off for you, just make sure it stays that way. The common HTTP features are the features you would expect from a web server. With the selections on this page, IIS will now serve up a web page for you.
Restart IIS by going to the IIS manager (Start –> IIS Manager). Select your website, and on the far right side is a section titled Manage Server. Make sure that the service is started, or click Start to start the services selected. Once this is complete, you should be able to go to a web browser and navigate to http://localhost`.
This should open the standard IIS 7 splash page, which is just a static image that says your web server is running. Assuming you were able to get the splash page, it is safe to say your web server is now up and running.
Windows Server 2008
Go to Start –> Control Panel –> Programs.
Under Programs and Features, there is link titled Turn Windows Features on and Off. Click on it.
This will bring up the Server Manager.
In the server manager, Click on Roles, and then click Add Roles.
Use the Add Roles Wizard to add the web server role.
Server roles required for ownCloud
Make sure that, at a minimum, the same boxes are checked in this wizard that are checked in the Windows 7 Section. For example, make sure that the CGI box is checked under Application Development Features, and that WebDAV Publishing is turned off. With Remote Desktop Sharing turned on, the detailed role service list looks like the figure “Role Services”.
Restart IIS by going to the IIS manager (Start –> IIS Manager).
Select your website, and on the far right side is a section titled Manage Server. Make sure that the service is started, or click “Start” to start the services selected.
Once this is complete, you should be able to go to a web browser and type “localhost”. This should open the standard IIS 7 splash page, which is just a static image that says your web server is running.Assuming you were able to get the splash page, it is safe to say your web server is now up and running. The next part of this “how to” installs PHP on the server.
Installing PHP
This part is also straightforward, but it is necessary to remind you that this is for IIS only.
Go to the following link and grab the PHP installer for version “VC9 Non Thread Safe” 32 or 64 bit based on your system. http://windows.php.net/download/
If you are using Apache, make sure you grab VC6 instead, lower on the page.
Once through that login, select the location that is closest to you geographically.
Run that install wizard once it is downloaded. Read the license agreement, agree, select an install directory.
Then select IIS FastCGI as the install server.
Take the default selections for the items to install, and click next. Then click install.
And, after a few minutes, PHP will be installed. On to MySQL.
Installing MySQL
This part installs MySQL on your Windows machine.
Point your browser to http://dev.mysql.com/downloads/ and download the latest community edition for your OS – the 32 or 64 bit version. Please download the MSI Installer as it will make life easier.
Once downloaded, install MySQL (5.5 at the time of writing). Select the Typical installation.
When that finishes, check the box to launch the MySQL Instance Configuration Wizard and click Finish.
Select a standard configuration, as this will be the only version of MySQL on this machine.
Select to install as a windows service, and Check the Launch the MySQL Server Automatically button.
Select the modify security settings box on the next page, and enter a password you will remember. You will need this password when you configure ownCloud.
Uncheck enable root access from remote machines” for security reasons.
Click execute, and wait while the instance is created and launched.
Click Finish when this is all complete.
Take particular note of your MySQL password, as the user name root and the password you select will be necessary alter on in the ownCloud installation. As an aside, this link is an excellent resource for questions on how to configure your MySQL instance, and also to configure PHP to work with MySQL. This, however, is not strictly necessary as much of this is handled when you download ownCloud.
It will arrive as a tar.bz2 file, and I recommend something like jZip for a free utility to unzip it.
Once you have the ownCloud directory unzipped and saved locally, copy it into your wwwroot directory (probablyc:inetpubwwwroot).
You cannot install directly into the directory wwwroot from jzip, as only the administrator can unzip into the wwwroot directory. If you save it in a different folder, and then move the files into wwwroot in Windows explorer, it works. This will install ownCloud locally in your root web directory. You can use a subdirectory called owncloud, or whatever you want – the www root, or something else.
It is now time to give write access to the ownCloud directory to the ownCloud server: Navigate your windows explorer over to inetpub/wwwroot/owncloud (or your installation directory if you selected something different).
Right click and select properties. Click on the security tab, and click the button “to change permissions, click edit”.
Select the “users” user from the list, and check the box “write”.
Apply these settings and close out.
Now open your browser and go to http://localhost/owncloud (or localhost if it is installed in the root www directory). This should bring up the ownCloud configuration page.
At this page, you enter your desired ownCloud user name and password for the administrator, and expand the little arrow.
Select MySQL as the database, and enter your MySQL database user name, password and desired instance name – use the user name and password you setup for MySQL earlier in step 3, and pick any name for the database instance.
The owncloud admin password and the MySQL password CANNOT be the same in any way.
Click next, and ownCloud should have you logged in as the admin user, and you can get started exploring ownCloud, creating other users and more!
Configuring ownCloud, PHP and IIS for Large File Uploads¶
Before going too nuts on ownCloud, it is important to do a couple of configuration changes to make this a useful service for you. You will probably want to increase the max upload size, for example. The default upload is set to 2MB, which is too small for even most MP3 files.
To do that, simply go into your PHP.ini file, which can be found in your C:Program Files (x86)PHP folder. In here, you will find a PHP.ini` file. Open this in a text editor, and look for a few key attributes to change:
upload_max_filesize – change this to something good, like 1G, and you will get to upload much larger files.
post_max_size – also change this size, and make it larger than the max upload size you chose, like 1G.
There are other changes you can make, such as the timeout duration for uploads, but for now you should be all set in the PHP.ini file.
Now you have to go back to IIS manager and make one last change to enable file uploads on the web server larger than 30MB.
Go to the start menu, and type iis manager.
Open IIS Manager Select the website you want enable to accept large file uploads.
In the main window in the middle double click on the icon Request filtering.
Once the window is opened you will see a bunch of tabs across the top of the far right,Select Edit Feature Settings and modify the Maximum allowed content length (bytes)
In here, you can change this to up to 4.1 GB.
This entry is in BYTES, not KB.
You should now have ownCloud configured and ready for use.
TROUBLESHOOTING
If you get error below:
ownCloud is NOT installed
download of ownCloud source file failed.
SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failedSSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Set this two options below to FALSE in the webinstaller php file (i.e: setup-owncloud.php):
Windows Features required for ownCloud on Windows 7
Server roles required for ownCloud