Skip to main content

LAB 365

Search This Blog

Pages

Home
EWS & Powershell Basics
GraphAPI using Powershell
MicrosoftTeams
Exchange 2016
Exchange Interview Questions
About

Posts

Understanding the Authenticated Received Chain (ARC).

December 29, 2021

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Understanding the SPF, DKIM and DMARC

December 24, 2021

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

[Powershell script]-Get Message sent statistics from a mailbox in office 365

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Configure the expiration policy for Office 365 groups

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

[Powershell script Graph Api] Fetch sign-in logs of legacy applications which are using basic authentication to connect to Exchange online in office 365.

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

[Powershell Script] - Office 365 MFA method report

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Install ADFS on Azure VM step by step

August 10, 2019

ADFS

+

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Get the free third party SSL certificate and convert to pfx

August 09, 2019

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Publish OWA using Azure Application Proxy

Azure App Proxy

+

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

msExchRemoteRecipientType

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Sunil Chauhan: I have around 14 years of IT experience, and expertise in Exchange Server, Azure AD, ADFS, PIM, AIP, Exchange online Protection.

Pages

GraphAPI using Powershell
Exchange Interview Questions
Office 365 Interview Questions
Home
MicrosoftTeams
Download
About
Exchange 2016
EWS & Powershell Basics

Popular Posts

Moving PAM (Primary Active Manager) using PowerShell

Sometime PAM moves over to a different Server or on a node in DR AD Site, and you wish to move it back to Node in Primary Site, you can follow the below steps to verify the same and then move over the PAM back to a node you wish. There are different ways to check which node holds the PAM in your DAG, we can check the same using Exchange Management Shell , Failover Cluster Manager , or FailoverClusters Powershell Module . To check the Same using the Exchange Management Shell run the below command. Get-DatabaseAvailabilityGroup –Status | FL Check the Attribute “PrimaryActiveManager” this will show the node holds the PAM role. The other way is to open the “Failover Cluster Manager”, Once the Cluster Manager is opened, connect to DAG, if you are opening it on the Exchange Sever in the same DAG use the option Cluster on this server. Node Mentioned on “Current Host Server” is the one Holding the PAM Role. The Other way is to check it through the Powershell FailoverClusters Module , Follow th

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

Powered by Blogger