Skip to main content

LAB 365

Search This Blog

Get Report on Inbox Rules set to forward or redirect emails

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

This script will generate report in CSV for the rules currently setup to forward or redirect messages.

Powershell powershell tips

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '2'.

Some time back I had this error coming in my lab setup and cluster service on 2 nodes in DAG wouldn’t start, I followed the steps mentioned below to fix the issue. The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '2'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data. To fix the issue. Open the Command prompt as an administration and run the below command. Cluster Node ServerName /ForceCleanup And then run the below CMD on Exchange Powershell to re-add the node

Newly created user is not showing up in the Global Address List or Offline Address Book

The newly created user mailbox is not found in the (Global Address List) GAL Reason: This issue occurs when the "showInAddressBook" attribute is not populated on user Object. Requirement: ActiveDirectory Powershell Module or the Active Directory Administrative Center. Solutions: To fix the issue populate the showInAddressBook attribute Fix using the Active Directory Powershell Module You can verify if the "showInAddressBook" attribute is populated using the following CMD. Get-ADUser newuser -Properties * | fl showInAddressBook You will see a value like below if the attribute is populated. CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=domain,DC=com If the result does not return anything, then the attribute is required to be populated. Copy the attributes from the existing user who is showing in the GAL. $Addres

Database failed to mount after reaching configured maximum database size

Failed to mount database "DB01". Error: An Active Manager operation failed. Error: The database action failed. Error: Database 'DB01' on server 'Exch01' cannot be mounted due to a previous error: At '3/14/2019 9:41:57 AM' database copy 'DB01' on this server exceeded the configured maximum database size and service recovery was not attempted. Please increase the value of this registry key on the server hosting the active database copy before attempting to mount this database. You may encounter this error on the Exchange Database if you are running Exchange Server on Standard edition and database size has reached the 1 TB. To fix this issue you need to create the following registry entry on the exchange server for the database which we want to increase the database size limit. "Database Size Limit in GB" The REG_DWORD needs to be created in the database GUID folder container, Get the database GUID using the following CMD. (Get-

Powered by Blogger