Exchange 2010

Open ADSI-Edit and got to configuration

Navigate to this path:

CN=Configuration,DC=DOMAIN,DC=LOCAL

CN=Services

CN=Microsoft Exchange

CN=EXCHANGE_ORG

CN=Administrative Groups

CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

CN=Databases

CN=PUBLIC_FOLDER_DATABASE

Now you can delete the PF-Database you want to get rid off.

Exchange 2007

Open ADSI-Edit and got to configuration

Navigate to this path:

CN=Configuration,DC=DOMAIN,DC=LOCAL

CN=Services

CN=Microsoft Exchange

CN=EXCHANGE_ORG

CN=Administrative Groups

CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

CN=Servers

CN=SERVERNAME

CN=InformationStore

CN=STORAGE_GROUP

CN=PUBLIC_FOLDER_DATABASE

Now you can delete the PF-Database you want to get rid off.

Exchange 2003

Open ADSI-Edit and got to configuration

Navigate to this path:

CN=Configuration,DC=DOMAIN,DC=LOCAL

CN=Services

CN=Microsoft Exchange

CN=EXCHANGE_ORG

CN=Administrative Groups

CN=First administrative Group

CN=Servers

CN=SERVERNAME

CN=InformationStore

CN=STORAGE_GROUP

CN=PUBLIC_FOLDER_DATABASE

Now you can delete the PF-Database you want to get rid off.

Thank you,

Mukut-

When you try to expand public folder management console you get an error as given below:

No existing ‘PublicFolder’ matches the following Identity. ‘\’.  Make sure that you specified the correct ‘PublicFolder’ Identity and that you have the necessary permissions to view ‘PublicFolder’

Cause:

This issue can occur if the admin account is missing values for below attributes.

• HomeMDB
• HomeMTA
• LegacyExchangeDN

Solution:

1)      Open Adsiedit.msc

2)      Connect to “Default Naming Content”

3)      Browse the admin account.

4)      Right click on the admin account and go to property.

5)      Set values for above attributes.

6)      That must take care of the issue. 

Important: Additionally, creating a mailbox for the admin account will take care of the issue. However if you don't wanna create a mailbox for your admin account, you have to perform above steps. 

Thank you,

Mukut-

I was recently working with one of my customer and he had issues while performing discovery search.

He was typically getting a 404 error while performing search.

Customer was trying to perform a query and export data to a .pst.  

Error as given below:

Digging more into it and found customer was using a custom IIS site.

Custom IIS site was missing EWS virtual directory.

Note: EWS needs a unique IP address assigned and loop back IP must be remove. Don’t remove loop back IP from backend and default site.

1. We created a EWS VDir for custom site and assigned a unique IP address and removed loop back IP address from the VDir.: 
   

New-WebServicesVirtualDirectory -WebSiteName CustomSitename

1. Changed the VDir path to the custom location/path as they required for the custom IIS site.
2. Verify WebServicesVirtualDirectory InternalURL is assigned for each Vdir.
3. Set auto discovery URL for custom IIS site.
4. Recycle AppPool for auto discovery.
5. It must take care of the issue.

Disclaimer: Please make sure we are not making any changes in the default and backend site.

Apply to Exchange 2013.

Thank you,

Mukut-

Customer wanted to enable all AD accounts and reconnect all mailboxes. At the time we tried reconnecting the mailbox manually using GUI it could not identify the matching user.

If we reset Exchange attribute for one user and try connecting the mailbox it works fine. However connecting 1800+ users manually is time consuming and it’s a huge task.

Plan of action to follow:

1. List all disconnected mailbox and their alias.
2. List all disabled AD account for disconnected mailbox and enabling them.
3. Reset Exchange attribute for all users.
4. Connect their mailbox back.

Note: Below tasks has to be in sequence. 

 Important: We need to be sure that none of the user has same display names. Otherwise its gonna be an issue while reconnecting the mailbox. Therefore we can list their alias and perform the task.

 1)       Export all disconnected mailbox list into csv for DB01

Listing all disconnected mailbox list:

Get-MailboxStatistics -database "DB01” | Get-Mailbox | ?{$_.Database -eq $null}| Export-Csv 'C:\Reconnecting Mailbox\db01.csv'

Listing these users with their alias/Import users from csv:

$all = Import-Csv 'C:\Reconnecting Mailbox\db01.csv'

$all | select DisplayName,Alias

$all | select DisplayName,Alias | Export-Csv 'C:\Reconnecting Mailbox\onlyalias.csv'

$alias = Import-Csv 'C:\Reconnecting Mailbox\onlyalias.csv'

$alias

2)       Listing all disabled AD accounts:

Get-MailboxStatistics -Database "DB01" |?{$_.DisconnectReason -eq "Disabled"}| Export-CSV "C:\AD.csv"

a)       Import-Module ActiveDirectory

b)       List alias for these users:

$all = Import-CSV "C:\AD.csv"

$n=$all | select Displayname

foreach($m in $n)

{

Get-User $m.DisplayName

}

 Enabling AD account for users located in different OUs however exported the list of users from mailbox database "DB01”:

Step1:

$g=@()

foreach($m in $n)

{

$g+= Get-User $m.DisplayName

}

Step2:

$g | %{Enable-Adaccount -Identity $_.Name

}

  3)       Remove Exchange attributes using RemoveExchangeattributes.ps1 for all impacted users:

Script can be obtained from: https://gallery.technet.microsoft.com/office/Remove-Exchange-Attributes-3b39b2de  

foreach($user in $alias)

{

$enteruser = $user.Alias

$enteruser=$user.alias

.\RemoveExchangeattributes.ps1

}

4)       Connect all users using below script:  

Connect all users after listing alias after importing saved csv/mailbox names (Steps are given in step 1):

 foreach($user in $alias)

{

connect-mailbox $user.DisplayName -user ("csxtlab\"+$user.Alias) -Database "DB01”

}

 Disclaimer: Please make the necessary changes as per your requirement. And highly recommended to test/verify each loop of the scripts before trying it in the production.  

Thank you,

Mukut-

Right-click the Exchange Administrative Group (FYDIBOHF23SPDLT) and choose New -> Public Folders Container.

Now simply drag the Public Folders tree from the Exchange Server 2003 administrative group to the Exchange Server 2007 or 2010 administrative group.

Thank you,

Mukut-

Most of the time we disable these mail enabled PF and delete the object in ADUC and re-enable them.

In case of thousands of PF it’s really hard to perform these steps for each and every mail enabled PF.

Ideally we will be performing below task:

1)       Export list for mail enabled PF.

2)       Disable all mail enabled PF.

3)       Deleted ADCU object for the PF.

4)       Re-enable mail enable PF.

1)            Export list for mail enabled PF:

Get-PublicFolder -recurse -resultsize unlimited | WHERE { $_.MailEnabled -eq $true } | export-csv  C:\PFtest2.csv

2)            Disable all mail enabled PF:

Get-PublicFolder -recurse -resultsize unlimited | WHERE { $_.MailEnabled -eq $true } | Disable-MailPublicFolder -Confirm:$false

3)            Deleted ADCU object for the PF:

a)       Open ADUC: Dsa.msc

b)       View advanced features

c)       Select “Microsoft Exchange System Object”

d)       Delete all ADUC objects for mail enabled PF.

4)            Re-enable mail enable PF:

Run below script:

$a=import-csv C:\PFtest2.csv

foreach($pf in $a){

Enable-MailPublicFolder -Identity $pf.Identity

}

Impotent: Please make the necessary changes as per your requirement.

Thanks,

Mukut-

--------------------------------------------------------
Microsoft Exchange Warning
--------------------------------------------------------
The following warning(s) were reported while loading topology information:

get-PublicFolderDatabase
Completed

Warning:
Object EX01\First Storage Group\Public Folder Database has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
PublicFolderHierarchy is mandatory.

Warning:
PublicFolderHierarchy is mandatory.

--------------------------------------------------------
OK
--------------------------------------------------------

Trying to mount the Public folder database gets you the following eror:

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Public Folder Database'.

Public Folder Database
Failed
Error:
Exchange is unable to mount the database that you specified. Specified database: EX01\First Storage Group\Public Folder Database; Error code: MapiExceptionADPropertyError: Unable to mount database. (hr=0x80004005, ec=2418)

--------------------------------------------------------
OK
--------------------------------------------------------

When trying to delete the public folder database:

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
The public folder database 'Public Folder Database' cannot be deleted.

Public Folder Database
Failed
Error:
The critical property 'PublicFolderHierarchy' is missing in the PublicFolderDatabase object EX01\First Storage Group\Public Folder Database'.

--------------------------------------------------------
OK
--------------------------------------------------------

This all happens after you deleted the "First administrative group" in ADSIedit (which you should not have done!) after a migration to Exchange 2007 or 2010. If these are the only problems you are facing be happy. To resolve it perform the following actions:

1. Open ADSIedit.exe.

2. Right click on Exchange Administrative Group (FYDIBOHF23SPDLT)
3. Select New Object.
4. Select msExchPublicFolderTreeContainer for the class and click Next
5. Enter the following for the value: Folder Hierarchies, click Next
6. Click Finish

Create Public Folder Tree Object

1. Right click CN=Folder Hierarchies -> New Object
2. Selected msExchPFTree for the class
3. For the value we entered, "Public Folders" and clicked next
4. Clicked on the "More Attributes" button, selected msExchPFTreeType and set the value to 1.

Note: This is very important that this value is set to a value of 1 as this tells Exchange that this is a MAPI Tree
5. Click Ok and then finish


Populate msExchOwningPFTreeBL attribute object of the PF Stores in the organization

1. Get properties of the newly created "Public Folders" Tree object in ADSIEdit.
2. Copy the distinguishedname value to the clipboard and then click cancel.
3. Browse to CN=Public Folders Database,CN=First Storage Group,CN=InformationStore CN="Sever Name:,CN=Servers,CN=Exchange Administative Group,CN=Administrative Groups,CN=ORG Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=COM
4. In the properties of the "Public Folder Database", Edit the msExchOwningPFtree attribute and paste the content copied to the clipboard in Step2
5. Restart the Information Store Service.

*Important*

If you read the comments you'll see that Tim had a bit of an issue that was very similar to what was described here but not quite like it. Martina on the technet social helped him to resolve his issue by suggesting to check the msExchOwningPFTree attribute in ADSIedit! Have a look at the thread for the full details

Thank you,

Mukut-

So it is highly recommended to not clear/delete/move Windows Installer Cache from default location. Because these caches has an associated registry key on the server and its hard to determine and correct each and every missing .msi cache.

Now, if you think we can clean the reg key to avoid failure during action such as uninstall, repair, or update on a product. However that will cause more issues than you may expect and you will have to rebuild the server/box. 

The only way we can fix this is by copying all missing .msi caches from setup media or healthy server and place it in the installer directory. Challenges are to re-associate these caches with registry.

There is no easy way to re-associate these caches with registry and it would not be wrong saying its equal to impossible.  Because you wont be able to identify all missing or required caches and each time we fix one .msi cache it may through an error for another .msi cache. Fixing .msi caches one by one will be time consuming and time will depend on the count of missing .msi cache. Finally you will take a decision of rebuilding the server/box and performing recover server. Recover server will be a time consuming task.

Summarizing, If files are missing from the Windows Installer Cache, you will have to rebuild the operating system and reinstall applications.

Third-party recovery: Some third-party entities claim to be able to rebuild or repair the Windows Installer cache. For legal and supportability reasons we cannot recommend or endorse any of these entities. If you use such third-party products and recommendations you do so at your own risk.

If you have backups for your system prior to the file deletions here are some options:

• System RestorePoints available only on Client operating systems.
• Restoreable System State Backup.
• Disaster recovery methods that can restore the full system state backup
• Reinstall the operating system and all applications.

Full system state restores are required. It is not possible for example to replace only the missing files from a previous backups.

Thanks,

Mukut-

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Identity db-archive | FL

RunspaceId:           8ffefaf9-1e9e-4834-9f39-f1fddadae1cb

Identity:                  DB-Archive\DAG10MBX02

Name:                     DB-Archive\DAG10MBX02

DatabaseName:     DB-Archive

Status:                    FailedAndSuspended

MailboxServer:       DAG10MBX02

ActiveDatabaseCopy:             dag10mbx01

ActivationSuspended:           False

ActionInitiator:       Service

ErrorMessage:       The Microsoft Exchange Replication service encountered an unexpected error in log re

                                   play for database 'DB-Archive\DAG10MBX02'. Error MapiExceptionTooManyMountedDatabase

                                   s: Unable to mount database. (hr=0x8004060e, ec=-2147219954)

ErrorEventId:          4057

ExtendedErrorInfo:

SuspendComment: The database copy was automatically suspended due to failure item processing. At '7/

                                9/2014 12:51:58 PM' the copy of database 'DB-Archive' on this server wasn't able to

                                operate because the number of mailbox database copies on this server exceeds the sup

                                 ported limit. Recovery was not attempted.

SinglePageRestore               : 0

ContentIndexState                : Failed

ContentIndexErrorMessage : Catalog is dismounted externally for database {58ecc424-151c-40f7-9720-8e09e7c1dbe0}

CopyQueueLength                : 1

Now generally speaking you would do a suspend-mailboxdatabasecopy -id "mailboxdatabase\servername" followed by an update-mailboxdatabasecopy -id " " -DeleteExistingFiles which would update the passive copy and resume the Storage Group Copy. Yet once in a while you'll run in to a case where this won't work as the gap is to large for Exchange to cover. In that case you'll have to perform the highly regarded "manual reseeding procedure"! This is somewhat disruptive for your users and risky unless you keep your head in the situation.

These would be the steps you follow:

Option 1:

1. Suspend the database copy
2. Go to the passive node and remove all the database and log files (fun yet?)
3. Dismount the database from Exchange
4. Go to the log files folder on the active node and move them all to a different folder
5. Now copy the EDB file from the active node to the passive node
6. Mount the database once this is completed
7. Resume the storage group copy

Option 2:

1. Get the GUID of the database: get-Mailboxdatabase –Identity Databasename | FT name,*GUID*
2. Navigate to the following registry path on the target server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\ContentIndex\CatalogHealth\{DatabaseGUID}
3. Look for below string keys:

• State: Exclude
• ErrorCode: CatalogDismountedExternally
• TimeStamp: 2014-07-02 14:52:14Z (depending on the last failure/updated time)

1. Changes these value as given below:

• State: Recommended
• ErrorCode: “Success” or leave it blank
• TimeStamp: 2014-07-02 14:52:14Z (depending on the last failure/updated time)

1. Initiate seeding/update of the database update-mailboxdatabasecopy -id " " –DeleteExistingFiles
2. This must resolve the issue.

All in all this should get your copy back in order. Not exactly the way you'd want to (without down time) but it gets the job done.

Ps: You can refer following article as well: https://blogs.technet.com/b/timmcmic/archive/2012/12/04/exchange-2010-adding-database-copies-to-databases-with-a-single-copy-results-in-copy-status-failed-after-seeding-is-completed.aspx 

Thanks,

Mukut-

You can find Microsoft product lifecycle in bellow link/URL:

https://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=exchange+server+2010+&Filter=FilterSP&spdate=3

Thank you,

Mukut-