When creating a new mailbox database with the Exchange 2010 Management Console you may have noticed that the database and log paths are automatically populated.
This path comes from the value of the DataPath attribute on the Exchange Server object.
[PS] C:Admin>Get-ExchangeServer | fl name, *path* Name : EXCH2010-TEST DataPath : C:Program FilesMicrosoftExchange ServerV14Mailbox
Unfortunately this attribute is not exposed to modification via the Set-ExchangeServer cmdlet. However like all attributes it is stored in Active Directory. In this case it is the msExchDataPath attribute on the Exchange Server object, viewable in ADSIEdit.msc.
You can edit the attribute in ADSIEdit.msc and it will take effect immediately. The next time you run the New Mailbox Database wizard it will pre-populate the paths with the new value plus the name of the new database.
[PS] C:Admin>Get-ExchangeServer | fl name, *path* Name : EXCH2010-TEST DataPath : C:ExchData
If we don’t chose the path of the user mailbox where will be stored
I had cause to move a database from one server to another and had to use ADSIEdit to complete the path change.
After making the requisite changes to msExchEDBFile, msExchESEparamLogFilePath, msExchESEparamSystemPath, I had to also change, msExchMasterServerOrAvailabilityGroup, msExchOwningServer to reflect the new server name (all in the database properties).
Then changed the msExchMDBCopy class Object CN name to the new Exchange Server CN, and edit the msExchHostServerLink property accordingly.
If you were moving a database to a different server (presumably because of a failed server) then you should have been using the documented process for using database portability.
Thanks for this Paul – but is there an attribute you can set for the DB LOG path as well as for the DB? Can’t seem to find one in ADSIEdit for the server…
Thanks – Steve
To be honest I would not both with this any more. As an ADSIEdit change it would also very likely be unsupported.