Posts

No Authentication after closing the primary Domain controller

 ISSUE: there are 3 domain controllers on the environment, one of them is the primary DC, when we try closing it, outlook can't authenticate with exchange server. an outlook prompt keeps appearing we want to test in case of update or outage that nothing could go wrong Cause: The Primary Domain Controller had all FSMO roles including PDC role which is responsible for authentication. Resolution: Before closing the DC, we transferred the PDC role to another Domain controller, then shutdown the primary one To do so please follow: Click Start, point to Administrative Tools, and then click  Active Directory Users and Computers. Right-click  Active Directory Users and Computers , and then click  Connect to Domain Controller (If you on another DC) . Do one of the following actions: In the  Enter the name of another domain controller  box, type the name of the domain controller that will be the new role holder, and then click OK. -or- In the  Or, select an available domain controller  list,
Post a Comment
Read more

Exchange setup error: the attribute () points to an invalid DN or a deleted object

 Issue: we closed the last exchange server on Prem, and run a script to delete the AD remnant, when we try to download Exchange Mangement tools we get the following error: The well-known object entry B:32:A1C2016C84D003458132789127B84:CN=Exchange Servers\0ADEL:b2360aad-5e45-40ae-a52a-22397689104a,CN=Deleted Objects,DC=contoso,DC=lab on the otherWellKnownObjects attribute in the container object CN=Configuration,DC=contoso,DC=lab  points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task. Cause: After deletion of ADSI remnants of exchange server, some attribute transferred to deleted object container but is still added to  otherWellKnownObjects  attribute. Solution: 1 . Log on a Domain Controller with Domain Admin permissions 2 . Run ldp.exe -- the LDAP GUI pops up 3 . Click on the Connection menu item and choose the "Connect" item . Leave everything as it is. DO NOT ENTER THE SERVER. Click OK The right side panel populates with domain info. 4 .
Post a Comment
Read more

Renew certificate error

 Issue: When we try to Renew the certificate and in the export certificate command we get error: A special RPC error has occurred on server E1901: The private key could not be exported as PKCS-12 could not be exported. Either no access was possible or the key cannot be exported. + CategoryInfo : InvalidArgument: (:) [Export-ExchangeCertificate], InvalidOperationException + FullyQualifiedErrorId : [Server=E1901,RequestId=6985d3ef-0907-4371-82c7-c3273b667433,TimeStamp=19.04.2024 14 23:22] [FailureCategory=Cmdlet-InvalidOperationException] 69D2698D,Microsoft.Exchange.Management.SystemConfigurat Cause: A certificate key was invalid. Resolution: A Rekey is requested for the certificate and it worked.
Post a Comment
Read more

Changes in Outlook shared calendar appointments are not accepted

  Issue: Changes in Outlook shared calendar appointments are not accepted, just the window close with no error but the changes are not set, also can't delete, but can add a new appointment. The user is having full access to the shared calendar. The issue is only in Outlook, not OWA. Cause: It is one of the known issues with the new shared Calendar Improvements: Known issues with Outlook Desktop Shared Calendar Improvements - Microsoft Support Workaround: Creating new profile will make it work for a couple of weeks. What we did is to deactivate the shared Calendar Improvements option and reactivate it again. How to enable and disable the Outlook calendar sharing updates - Microsoft Support
Post a Comment
Read more

Outlook on prem prompts for O365 Password

  Issue: In an Exchange on prem environment Outlook prompts for O365 Password trying to connect to exchange online or Office365. and is not connecting after that. Cause: Moder authentication was enabled Solution: First, we thought of postponing the O365 request, by adding registry Dword (ExcludeExplicitO365Endpoint) this will tell Outlook to postpone the O365 Autodiscover request to the last. 1- Open Registry Editor 2- Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Office\<x.0>\Outlook\AutoDiscover 3- 3- 3- Create new Dword : ExcludeExplicitO365Endpoint  value 1  but this didn't solve the issue  so we decided to disable Modern authentication 1- Open Registry Editor 2- Navigate to: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\<x.0>\Common\Identity   3- Create Dword: EnableADAL value 0 DisableAADWAM  value 1 DisableADALatopWAMOverride  value 1 then the Prompt stopped and outlook connected to On-prem Autodiscover 
Post a Comment
Read more

Can't find msexchHideFromAddressLists Attribute

  Issue: Can't find msexchHideFromAddressLists Attribute in ADSI edit or in AD users and computers to change it for the users. Cause: In the environment there is only Exchange online, no exchange on Prem and there never was, so the MSexch attributes are not there. Resolution: We downloaded the Exchange server prerequisites on another domain joined server as in here: Exchange Server prerequisites, Exchange 2019 system requirements, Exchange 2019 requirements | Microsoft Learn Downloaded Exchange server ISO from here: Exchange Server build numbers and release dates | Microsoft Learn Mount the ISO and then we run the command: <Virtual DVD drive letter>:\Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareSchema and the Attribute appeared.
Post a Comment
Read more

Calendar- Share option is not present in OWA or Outlook

Image
 Issue: Calendar sharing option is not available neither in OWA nor in Outlook, So can't share the calendar. Cause: After checking OWA we found that it looks different. Like in here:  Outlook Web App opens in the light version - Exchange | Microsoft Learn and as we checked this is the light version, but the customer didn't activate it and we can't undo the Light version option. it turns out to be the web browser version not compatible. Resolution: we tried to log in in a different computer with a higher windows version, OWA and Outlook worked fine. Other Information: If your Browser version is not the Problem, then you can revert to OWA normal version by: 1. In Outlook Web App, select  Options . 2. In the navigation pane on the left, select   Outlook Web App version , and then clear the   Use the Light Version of Outlook Web App   checkbox. 3. Select   Save   at the top of the page. 4.Sign out of Outlook Web App. The next time that the user signs in to Outlook Web App, the
Post a Comment
Read more