- Open Windows PowerShell and run the following command to install the Remote Tools Administration Pack.
- Install-WindowsFeature RSAT-ADDS & Install-WindowsFeature ADLDS
- Run the following command to install the required Windows components.
- Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
- Our first part of the Exchange 2016 installation is to perform the Schema update. This step is irreversible;
- While logged on as a domain user that’s a member of the Enterprise Admins and Schema Admins, launch an elevated command prompt
- Execute setup.exe with the following switches to prepare the Active Directory schema:
- setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
- Next prepare Active Directory. This will prepare the Configuration Container of our Active Directory forest, upgrading the AD objects that support the Exchange Organization. We’ll perform this preparation using the following command.
- exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Our final step to prepare Active Directory is to run the domain preparation.
- exe /PrepareDomain /IAcceptExchangeServerLicenseTerms
- Start Exchange 2016 Setup by double-clicking Setup.exe.
On the License Agreement page, review the terms. If you agree to the terms, select I accept the terms in the license agreement, and then click next.
On the Recommended Settings page, select whether you want to enable or disable the Exchange Error resolution and feedback feature. The option will either enable or disable automatically check for resolutions for any errors that occurs while the setup is running and sends Microsoft feedback. Click Next to proceed.
On the Server Role Selection page, choose what server role you want to install. Whether to install the Mailbox role, Management Tools or Edge Server role on the server. For this lab Mailbox server role will be selected. Note that Edge and Mailbox cannot collocate on the same server and Management Tools will be installed by default when you chose the Mailbox role. If any Windows prerequisites are needed for the setup, select the automatically install Windows Server roles and features that are required to install Exchange Server. Click Next to proceed.
On Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If unsuccessful, perform the required tasks and click back, and Next to run the Readiness check again. If successful, click Install to proceed
Once the setup completes installing all the components, the Setup Completed page will be displayed. Select Finish.
Coexistence of Exchange 2016 with earlier versions of Exchange Server:
- Exchange 2007 and earlier versions : Not supported
- Exchange 2010: Supported with Update Rollup 11 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers.
- Exchange 2013: Supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.
- Mixed Exchange 2010 and Exchange 2013 organization: Supported with the following minimum versions of Exchange like Update Rollup 11 Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers, Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.
- All domain controllers in the forest need to be running one of the following :
- Windows Server 2008 Standard, Enterprise, or Datacenter
- Windows Server 2008 R2 Datacenter RTM or later
- Windows Server 2008 R2 Standard or Enterprise
- Windows Server 2012 Standard or Datacenter
- Windows Server 2012 R2 Standard or Datacenter
- The Active Directory forest functionality level needs to be at Windows Server 2008 or higher.
- We should not install exchange server on any of the domain controller server.
Other things to keep in mind:
- We cannot install two exchange servers on the same server.
- Services related to SQL server should be in stopped, before proceeding.
- The Simple Mail Transfer Protocol (SMTP) service is installed on this computer. This must be removed before Setup can continue.
- If you are migrating, FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 object should be in disabled mode.
- Active Directory Forest Functional level in the organization must be upgraded to Windows Server 2008 or later (currently in 2003)
- Install .Net framework 4.5.2 Click here to download
- Install Microsoft Unified Communications Managed API Core Runtime, version 4.0. Click Here
- Exchange 2016 setup will be available here.
View: Our HTML lives as a tiny template to be rendered as a View, and we use a Controller to connect the two, driving Model and View value changes.
Modules: Every application in Angular is created using modules. A module can have dependencies of other modules, or be a single module all by itself. These modules act as containers for different sections of an application, making code more reusable and testable. To create a module, we hit the global angular Object, the framework’s namespace, and use the module method.
- Setters: means we are creating a new module, while creating it we can import the other modules as well. In the  we have to add the other modules.
- Getters: For creating the directives, controllers etc… We have to use the existing modules.
HTML Bootstrapping: To declare where our application sits in the DOM, typically the <html> element, we need to bind an ng-app attribute with the value of our module. This tells Angular where to bootstrap our application.
$Scope vs $rootScope: $scope is limited to that a particular controller, While rootscope will be accessed to its child and parent controllers. Parent $rootScope value will be updated with the child $rootScope value.
Controllers: An Angular Controller allows us to interact with a View and Model, it’s the place where presentational logic can take place to keep the UI bindings in sync with the Model. A Controller’s purpose is to drive Model and View changes, in Angular it’s a meeting place between our business logic and our presentational logic.