34 C
Dubai
Wednesday, April 30, 2025
Home Blog Page 39

Opening Shared calendars via Various Channels

Lets see opening shared calendars via various channels

  • Outlook Web Access
  • Microsoft Outlook
  • Outlook Mobile App

In Outlook Web Access

Left Site Bottom of your Screen . Choose Calendar Icon

image

Once you open it. Click on Import calendar.

image

Click on Add Calendar from Directory

image

Opening Shared Mailbox Calendars via Outlook

image

image

Opening Shared Calendars via Outlook App iOS

image

Choose the Calendar

image

You can see the listed Calendar

image

Finding the Azure AD Connect server in the forest

What if customer doesn’t know where the Azure AD Connect server is deployed .

Find the MSOL Account on Users Container in Active Directory.

image

Copy the Description of the Account – you can find the Azure AD Connect Server Deployed on.

Account created by the Windows Azure Active Directory Sync tool with installation identifier ‘f9be57f6eab24e6b22222e69a’ running on computer ‘AD-CONNECT-SERVER01’ configured to synchronize to tenant ‘

azure365pro.onmicrosoft.com’. This account must have directory replication permissions in the local Active Directory and write permission on certain attributes to enable Hybrid Deployment.

if Server is moved recently and if they use the default Azure AD Service Account

You can login to Microsoft 365 Admin Center

Health – Directory Sync Status – Directory Sync Service Account may help on the server name

 

 

Migrate CA From 2008 R2 to Windows 2016

Microsoft Certificate Authority becomes a key server if its integrated to Critical Services like Meraki,Skype for Business, RADIUS Servers ,and any cert based applications signed by domain authority.If its a virtual infrastructure. I usually take a clone of these servers to test the same. Just to make sure all going to be ok .As once you export the Certificate with keys you got to remove the Server Role and Reboot. And I feel comfortable if it imports ok on the clones. As there is kind of no go back. you can always promote the server back and Install the certificate authority as a backup plan .   please note that during this period . you cannot re issue or renew or revoke the certificate.

  • Backup Certificate Authority.
  • Backup Certificate Authority Registry.
  • Backup Custom Files if modified.
  • Uninstall Certificate authority and Domain controller
  • Install Certificate authority Server with Same name or different Name.
  • Restore Certificate authority
  • Restore Certificate authority Registry  (Retains the old Certificate authority Name even if the server name is different)

Backup Certificate Authority – Database, Log Files, and Private Key

Open Certification Authority

In the Certificate authority  console, right-click your CA in the left pane, select All Tasks ,select Backup CA.

image

In the Certification Authority Backup Wizard, click Next on the welcome screen.

On the Items to Back Up screen, check Private key and CA certificate and Certificate database and certificate database log.

image

Click Browse to the Back up to this location, select an empty folder to store the backup files, and click Next to continue.

Choose a Password and Confirm Password to protect the private key and CA certificate. Click Next to continue.

image

Click Finish – Completing the Certification Authority Backup Wizard

image

Open cmd Run as administrator.

net stop certsvc and press Enter to make sure the CA cannot issue certificates.

Backup / Export the Registry.

Registry key from here: HKLM\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration

image

if you have any custom templates

Certificate Templates: Open the PowerShell command prompt with run as administrator, run the below mentioned command
certutil.exe –catemplates > “c:\CA2008R2\templates.txt”

If you have a customized CAPolicy.inf then copy it from %systemroot% directory.

In my case , As below.
image

Uninstall Root CA using Server Manager and Dcpromo to demote the Domain controller

image

if you want to retain the same name of the server. wait for the active directory to replicate in all sites else force the Active Directory Replication.

Rename the server, change the IP and remove the server from the domain.

Now login to the new server.

Install New Root CA server on the Private Key Wizard. DO NOT CREATE NEW PRIVATE KEY> Import the existing private key.

Type the password for the file when prompted, then confirm it.
Give the same name as old Root CA . if you wish to have a different Server name. it will still work . But when you import the registry the Old CA Name will be retained.

image

Now Configuration Succeeded without any issues.

image

Restore the Root CA backup

Open Certification Authority.

In the CA console, right-click your new CA in the left pane, select All Tasks from the menu and then Restore CA.

If you are prompted to stop the Active Directory Certificate Service, click OK continue.

In the Certification Authority Restore Wizard, click Next on the welcome screen.

On the Items to Restore screen, check Private key and CA certificate and Certificate database and certificate database log.

Click Browse to the backup copied location to restore from this location. Give one level up than backup location where the backup files are located, click OK in the Browse for Folder window and then Next to continue in the wizard. Click Finish

You should now be prompted to restart the AD CS service. Click Yes to confirm the operation.

 

open cmd prompt as administrator

net stop certsvc

-Double click on the copied registry file. When prompted click yes to update the registry.

Typical installation . Will not have templates neither custom .inf file. you can safely skip the below step. if you haven’t done any customization.

 

Restore Template if you had exported .
On the PowerShell, run the below command This command will add the DirectoryEmailReplication template in AD to the list of CA templates, if it doesn’t already exist. You can get a list of the templates by opening the catemplates.txt file saved as part of the backup procedure.

certutil -setcatemplates +DirectoryEmailReplication.

Restore Policy INF:  If we found a customized CAPolicy.inf then copy it to %systemroot% directory

 

Restart the Certificate Authority Server.

Azure Virtual Network (VNet) Peering UAE to Central US

VNET Peering connects networks seamlessly within and across regions. Local and Global Peering pricing differs region to region.

Lets Connect the Virtual Network from UAE North to Central US

UAE North Virtual Machine – 10.1.1.4 255.255.255.0 10.1.1.1

Central US Virtual Machine – 10.0.0.4 255.255.255.0 10.0.0.1

image

Lets do peering between this two Virtual Machines. Go to Virtual Networks.

image
Go to Peering _ Add

image

Add Peering

image

Click OK.

image

image

Now Both Virtual Machines can be communicated with no restriction. (All ports are opened by Default)

VNET Peering Pricing

https://azure.microsoft.com/en-us/pricing/details/virtual-network/

image

Only Android Phones getting Cert Error from Load Balancer

Bypassing load balancer seems to be no error. and iOS devices and Outlook seems to connect without any issues.

digicert never had any such issue.

Error : There’s a missing intermediate certificate in the certificate chain.

 

image

Logged into the device to check for root certificate to make sure.

Clicked on Settings

Security and location

Encryption and Credentials

and Trusted Credentials.

 

Got the intermediate Certificate  from the vendor site.

https://globalsign.ssllabs.com/

and placed in KEMP Load balancer in my case.

image

and now Android devices connected without any issues.

Moving NPS from Windows 2008 to Windows 2016

Install Network Policy and Access services otherwise called as RADIUS Server. Install the specific role in the new server.

now login to the existing server. Export the existing configuration configuration.

netsh nps export filename="c:\users\usernname\Desktop\NPS.xml" exportPSK=YES

image

Now login to the new server and import the NPS.xml

if you see any un supported rules . You have to remove them from the old system. Export again and import back to the new server.If you need those un supported rules you need to manually recreate them.

in my case i got three unsupported legacy rules which was created to use a legacy system and it wasn’t exist anymore. so i just deleted those rules and exported and imported back again.

netsh nps import filename="c:\users\usernname\Desktop\NPS.xml"

image

Now open NPS , Network Policy Server and Click on Register Server in Active Directory.

Now New Network Policy Server is up and running with the same configuration.

image

× How can I help you?