4- How to rename Exchange 2013 Data-base from Exchange Management Shell Renaming Exchange 2013 data-base is to use Exchange Management Shell. Run Exchange Management Shell as Administrator
Create User Mailbox Exchange 2013, Creating a new mailbox for the existing active directory user, various mail attributes are added to the user’s object in Active Directory. If you delete a mailbox from the Exchange server, the user associates with the mailbox is also delete from the active directory.
1- Open the Exchange Admin center > select recipient > click mailboxes > click add and then select user mailbox option.
2- Select an Existing user and then click browse. (This means, the mailbox will be created for the user account which is already in active directory. If you want to create a mailbox for the user account that is not in the active directory then, choose a new user and start filling all the boxes. We are creating a user account in active directory)
3- Select the user for whom you want to create a mailbox, then click ok.
Send Connector Exchange 2013, By default once you install Exchange 2013 it doesn’t have a send connector, only receive connectors. To be ready to send outbound emails to other domains you would like a send connector.
Send Connector Exchange 2013
1- Login into Exchange admin center > click mail flow > click send connectors to click the + icon to feature a replacement send connector.
2- Type a name for the connector and select the Internet as the Type and click next.
3- Leave the default options on the network settings page and click next.
4- Under Address space click the + icon
5- In the Full Qualified Domain Name dialogue box type * and click save.
6- Create a new send connector, so click next.
7- Under the Source server then click the + icon.
8- Highlight your Exchange server, click the add button and then then click ok.
9- Click finish.
10- Now you can see a new Default Internet Connector created under send connectors. One final configuration change we need to make is to add the FQDN for the connector. Highlight the connector and then click the edit icon.
11- From the left side menu click scoping, scroll to the bottom, enter the FQDN for your mail server and then save.
Virtual Directories Configure External and Internal URL in Microsoft Exchange Server 2013.
Virtual Directories Exchange 2013
Open Exchange Admin Center.
1- Select Servers > Virtual Directory and then select the External Access Domain settings button.
2- On the configure external access domain then click the add + button.
3- Select the Exchange 2013 server(s) you wish to configure external URLs on, Then click Add button, once you have all the required servers then click ok.
In my Labe, I will be able to just be configuring Exch2013-1 but you’ll select as many servers as you wish.
4- Enter the domain name you wish to use externally. In my case I want our external users to go to mail.xpertstec.com, then click Save.
5- This may take some time. Once complete so click close.
ECP Virtual DirectoryExchange 2013
Set-ECPVirtualDirectory
Set-ECPVirtualDirectory –Identity “ECP (default web site)” -ExternalURL “https://mail.xpertstec.com/ECP” Set-ECPVirtualDirectory –Identity “ECP (default web site)” -InternalURL https://mail.xpertstec.com/ECP”
Exchange Admin Center 2013 > select Servers > select Virtual Directories > select ecp (Default Web Site) and then click edit pin button.
Select the General tab, type Internal & External URL and then click save.
OWA Virtual Directory Exchange 2013
Set-OwaVirtualDirectory
Set-OWAVirtualDirectory –Identity “OWA (default web site)” -ExternalURL “https://mail.xpertstec.com/OWA”
Set-OWAVirtualDirectory –Identity “OWA (default web site)” -InternalURL “https://mail.xpertstec.com/OWA”
Exchange Admin Center 2013 > select Servers > select Virtual Directories > Select owa (Default Web Site) and then click the edit pin button.
Select the General tab, type Internal & External URL and then click Save.
ACTIVESYNC Virtual Directory.
Set-ActiveSyncVirtualDirectory
Set-ActiveSyncVirtualDirectory –Identity “Microsoft-Server-ActiveSync (default web site)” -ExternalURL “https://mail.xpertstec.com/Microsoft-Server-ActiveSync”
Set-ActiveSyncVirtualDirectory –Identity “Microsoft-Server-ActiveSync (default web site)” -InternalURL https://mail.xpertstec.com/Microsoft-Server-ActiveSync
Admin Center 2013 > select Servers > select Virtual Directories > Select Microsoft Server ActiveSync (Default Web Site) and then click edit pin button.
Select the General tab, type Internal & External URL and then click Save.
OAB Virtual Directory
Set-OABVirtualDirectory
Set-OABVirtualDirectory –Identity “OAB (default web site)” -ExternalURL “https://mail.xpertstec.com/OAB”
Set-OABVirtualDirectory –Identity “OAB (default web site)” -InternalURL “https://mail.xpertstec.com/OAB”
Exchange Admin Center 2013 > select Servers > seelct Virtual Directories > So, select owb (Default Web Site) and then click edit pin button.
Type Internal & External URL and then click on Save.
EWS Virtual Directory.
Set-WebServicesVirtualDirectory
Set-WebServicesVirtualDirectory –Identity “EWS (default web site)” -ExternalUrl “https://mail.xpertstec.com/ews/exchange.asmx”
Set-WebServicesVirtualDirectory –Identity “EWS (default web site)” -InternalUrl “https://mail.xpertstec.com/ews/exchange.asmx”
Exchange Admin Center 2013 > select Servers > select Virtual Directories > Select ews (Default Web Site) and then click edit pin button.
Select the General tab, type Internal & External URL and then click on Save.
POWERSHELL Virtual Directory.
Exchange Admin Center 2013 > select Servers > to select Virtual Directories > Select PowerShell (Default Web Site) and then click the edit button.
Select the General tab, type Internal & External URL and then click on Save.
Exchange Admin Center 2013 > select Servers > select Servers > Select Exchange server (EXCH2013-1) and then click the edit pin button.
Select Outlook Anywhere tab, type Internal & External URL and then click on Save.
AUTODISCOVER
Set-AutodiscoverVirtualDirectory Set-ClientAccessServer -Identity Exch2013-1 -AutoDiscoverServiceInternalUri https://autodiscover.xpertstec.com/Autodiscover/Autodiscover.xml To view the changes type Get-ClientAccessServer | FL AutoDiscoverServiceInternalUri Not enabled as default. Please note that the autodiscover should be set as an A-record in your DNS. Also, note that you simply don’t provide an URL for this. Set-AutodiscoverVirtualDirectory -Identity ‘autodiscover (default Web site)’
MAPI/HTTP
Not enabled as default. Requires Exchange 2013 SP1. Clients must be Outlook 2013 or newer. Fallback is OutlookAnywhere for older clients. Set-MapiVirtualDirectory -Identity “mapi (Default Web Site)” -InternalUrl “https://mail.xpertstec.com/mapi” -IISAuthenticationMethods NTLM,Negotiate After fixing the VirtualDirectory you would like to enable it: Set-OrganizationConfig -MapiHttpEnabled $true
In this blog, I will solve active directory domain configuration error “Verification of prerequisites” for Domain Controller promotion failed…..
Verification of prerequisites
1- In the Server Manager dashboard and select the tools tab and then choose Computer Management.
2- Under the Computer management expands Local Users and Groups. So select Users and right click on the administrator account and then select Set Password.
3- So click on Proceed.
4- Then type the administrator account password and click ok and ok.
5- Now open the windows PowerShell
Type cd\ press enter
and then type net user administrator /passwordreq:yes and hit enter.
The command completed successfully.
6- Now click on Rerun perquisites check.
7- All prerequisite checks passed successfully and click Install.
Active Directory Migration – In this blog, we’ll move the roles on our Server2008 (Windows Server 2008 R2 SP1) AD server to Server2019 (new Windows Server 2019 Standard).
Before proceeding to migrate an Active Directory from Windows Server 2008 R2 to Windows Server 2019, you want to first install Windows Server 2019 on a replacement machine which can then be promoted to Active Directory Server 2019.
The next step is to configure the IP and the DNS Addresses on the new server.
Windows Server 2008
R2
Windows Server 2019
Computer Name: Server2008 Server2019
Domain Name:
xpertstec.local
IP Address (Static): 10.0.0.20
10.0.0.22
Subnet Mask:
255.255.255.0 255.255.255.0
Default Gateway: 10.0.0.1 10.0.0.1
Preferred DNS Server: 10.0.0.20 10.0.0.20
Active Directory Migration 2008
1- First, let’s have a glance at my environment. we have a domain controller xpertstec.local which is installed on Windows Server 2008 R2.
Raise the Forest Functional Levels and Domain Functional Levels in Windows Server 2008 R2.
2- Click Start and select Administrative Tools and then Active Directory Domains and Trusts.
3- Right click on Active Directory Domains and Trusts and choose Raise Forest Functional Level.
4- Select an available forest functional level “Windows Server 2008 R2 and click Raise.
5- Now click on OK.
6- The forest functional level was raised successfully so click on ok.
Now Raising the Function Level of the Domain
7- Right click on the Domain name (xpertstec.local) and click Raise Domain Functional Level.
8- It has already got raised the Domain Functional Level to Windows Server 2008 R2 so click on close.
9- Now type the Netdom query fsmo command to check which server has installed FSMO roles.
10- DNS Manager.
Active Directory Migration Steps
Join Windows Server 2019 to an Active Directory Domain.
How to Join Windows Server 2019 to an Active Directory Domain, Click here
Now sign in Windows Server 2019 with the domain administrator account.
Create Additional Domain Controller (ADC) In Windows Server 2019
How to Create Additional Domain Controller (ADC) In Windows Server 2019 so Click here
11- Now have a look at my active directory Domain Controllers Server2008. We can now see that our server Server2019 is in the domain role.
Transferring the Flexible Single
Master Operations (FSMO) Role
I have a Windows Server 2008 Domain Controller (server2008) and have a further Windows Server 2019 domain controller (Server2019). To finish the migration. We’d like to transfer 5 FSMO roles to the new domain controller.
Schema Master
Domain Naming Master
PDC
RID pool manager
Infrastructure Master
12- To find which server is currently holding FSMO then run the following command. netdom query fsmo
The FSMO roles are currently with the Windows Server 2008 R2 Active Directory domain controller (server2008)
Using Active Directory Schema snap-in to transfer the Schema Master role 13- Open Command Prompt in administrative mode and type regsvr32 schmmgmt.dll and then click on ok.
Operations Master Roles Tranfer
14- On the Server2019 server, open Active Directory Users and Computers, right click domain xpertstec.local and then click Operations Masters.
15- On the Operations Masters, Select the RID tab and select the Change button.
16- Now click Yes.
17- The operations master role was successfully transferred so click ok.
18- Now you can verify that Operation master now transferred to our new Server Server2019.xpertstec.local
19- On the Operations Masters, select the PDC tab and then click the change button.
20- Now click Yes.
21- The operations master role was successfully transferred, then click ok.
22- Now you can verify that Operation master now transferred to our new Server Server2019.xpertstec.local
23- On the Operations Masters, select the Infrastructure tab and click on change button.
24- Then click Yes.
25- The operations master role was successfully transferred, then click ok.
26- Now you can verify that Operation master now transferred to our new Server Server2019.xpertstec.local
27- Open Server Manager and select Tools and then click Active Directory Domains and Trusts.
28- Right click on Active Directory Domains and Trusts and then select change active directory domain controller.
29- Select this Domain Controller or AD LDS Instance and click on the domain controller that you want to be the schema master role and then click ok.
Transfer Domain Master Role
30- Right click Active Directory Domains and Trusts and then select Operations Master.
31- Now click on Change
32- then click Yes.
33- The operations master was successfully transferred then click ok.
34- Confirmed the domain naming operation master role and click on Close.
35- Now we need to move our Schema Master role, so we need to register the schmmgmt.dll open command prompt and run the command below.
Regsvr32.exe C: \ windows \ system32 \ schmmgmt.dll
The process was completed successfully so click on ok.
36- Open Microsoft Management Console mmc type mmc and then hit enter.
Console
37- Select the File tab and then select Add/Remove Snap-in.
38- From the left side, under Available Snap-ins, Select Active Directory Schema, click Add button and then click ok.
39- Right click Active Directory Schema, and then select Change Active Directory Domain Controller.
40- Select this Domain Controller or AD LDS Instance, click on the domain controller that you want to be the schema master role and then click on ok.
41- Now click OK.
42- In the console1, right click Active Directory Schema (Server2019.xpertstec.local) and then select Operations Master.
43- Select the Change button.
44- then click Yes.
45- The active directory schema Operations Master successfully transferred then click ok.
46- Now confirm your current schema master which is Server2019 and then click Close.
47- Now run the Netdom query fsmo command, so we can now see that our roles have been moved to our Windows Server 2019 Additional Domain Controller.
48- Now change the DNS address of our additional Domain Controller server to be the IP address of our Windows Server 2019 Domain Controller server.
After completing Active Directory Migration, Now the ultimate step is to get rid of (uninstalling) server2008 Active Directory domain controller.
Remove Active Directory Domain Controller 2008
49- Open command prompt Type dcpromo and then hit Enter.
50- Click Next.
51- The Active Directory domain controller has the global catalog service, make sure your primary DC also has the service enabled and click on ok.
52- Confirmed that the delete this domain, because this server is the last domain controller in the domain, is UNCHECKED and then click next.
53- Type a password for the new Administrator account on this server and click next.
54- Review the remove active directory domain services Summary and click Next.
55- Check the Reboot on completion box to restart the server after the service has been removed
56- After rebooting server2008 DC. Now log in with the local administrator account and then open Server Manager.
57- In Server Manager click Roles under Roles Summary and click Remove Roles.
