Friday, July 24, 2015

Installing Exchange 2016 on Windows 2012 R2 Server

 

We will install Exchange 2016 on Windows 2012 R2 in a single labeled Forest/domain. Installing Exchange 2016 is very similar task compared  to Exchange 2013.  Follow the  basic steps outlined here to install your first Exchange 2016 server.

Make sure you have completed the prerequisite work outlined here after completing the prerequisite task, you can execute setup from install directory to run setup and start the install.

 

image

Follow the install wizard, it is pretty straight forward install.

clip_image001

clip_image002

clip_image003

clip_image004

clip_image005

clip_image006

clip_image007

clip_image008

clip_image009

clip_image010

image

Now we will open  EAC ( Exchange Admin Center ) and the Exchange PowerShell

image

image

you many want to PIN the exchange related shortcuts to start menu for easy access

 

image

here is  EAC and EMS

image

if you release the look is for the EAC is same as Exchange 2013.

image

I will rename the database to db1

 

image

image

Oz Casey, Dedeal  ( MVP North America)
MCITP (EMA), MCITP (SA)
MCSE , M+, S+, MCDST
Security+, Project +, Server +

http://telnet25.wordpress.com/ (Blog)
http://smtp25.blogspot.com/ (Blog)

https://twitter.com/message_talk

 

 

 

Installing Exchange 2016 on premises , prerequisite Task.

 

We will install Exchange 2016 into new Forest/Domain. In case you have missed E2016 preview  here is download link to try it out. Exchange 2016 is another major road map release for the greatest messaging application ever existed.

Installing Exchange 2016 Active Directory must meet following requirements

AD functional level;

  • Windows 2008 and the Schema Master ( FSMO ) running on Windows 2008 or later version
  • Windows 2012 R2 is required for all Exchange 2016 Server roles and management tools.

Active Directory Preparation;

NET Framework 4.5.2 on the computer that will be used to prepare Active Directory.

Install Remote Tools Administration Pack by running below PowerShell command

Install-WindowsFeature RSAT-ADDS

clip_image001

Mailbox Role;

Copy and paste the code below onto PowerShell command window.

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

clip_image002

clip_image003

Reboot the server by typing below PowerShell and pressing enter

Shutdown -r -f -t 5

For EDGE Role

Installing EDGE ROLE

Install-WindowsFeature ADLDS

Now install ;

clip_image004

clip_image005

clip_image006

clip_image007

Now install Unified Communications Managed API 4.0

clip_image008

clip_image009

Now we are ready to perform Exchange 2016 install into new forest/domain.

Oz Casey, Dedeal  ( MVP North America)
MCITP (EMA), MCITP (SA)
MCSE , M+, S+, MCDST
Security+, Project +, Server +

http://telnet25.wordpress.com/ (Blog)
http://smtp25.blogspot.com/ (Blog)

https://twitter.com/message_talk

Tuesday, July 7, 2015

How to Configuring external time source on PDC and why

By default all computers part of a domain will sync their time from domain controller which holds the PDC FSMO role. If you wish to see which DC holds the FSMO roles, you can open PS or command prompt and type "netdom Query FSMO" and press enter.

image

PDC Domain controller is the default authoritative time source for the forest/domain.Only PDC in your environment should have the external time source to sync its time from. All other domain joined & connected computers, servers and domain controllers will sync their time from PDC Emulator.

Step#1 ( setting external time source )

w32tm /config /manualpeerlist:"time.windows.com,0x1" /syncfromflags:manual /reliable:yes /update

image[37]

Setting Multiple time source

w32tm.exe /config /manualpeerlist:”0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org 3.us.pool.ntp.org” /syncfromflags:manual /reliable:YES /update

Step#2  ( Updating configuration)

w32tm.exe /config /update

image

Step#3 ( restarting service ) 

Restart-Service w32time ( PowerShell)

image

Step#4 ( verify service is running )

Get-Service –Name W32time

image

Step#4 ( Verify the settings )

w32tm /query /configuration

image

w32tm /query /status

image

W32tm /tz

image

w32tm /query /peers

imagei

If for some reason you will need to revert back the changes you have done

Step#1
Back out the changes

w32tm.exe /config /syncfromflags:Domhier /reliable:NO /update

image

Step#2
Restart-Service w32time


Step#3 ( see the roll back changes)

w32tm /query /configuration

image

Oz Casey, Dedeal  ( MVP North America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

http://telnet25.wordpress.com/ (Blog)
http://smtp25.blogspot.com/ (Blog)

https://twitter.com/message_talk


Saturday, July 4, 2015

The IP address you have entered for this network adapter is already assigned to another adapter.

 

If you are having issues assigning IP address to NIC card on your server and receiving following error " The IP address you have entered for this network adapter is already assigned to another adapter…"

One of the possible reasons for the error is,  there is another hidden NIC which has the same TCP/IP settings you are trying to configure on  another NIC card TCP/IP properties on the same server.

To remediate the issue follow the simple steps listed below.

clip_image001

1.Click Start, open cmd.exe, and then press enter

clip_image002

2.Type "set devmgr_show_nonpresent_devices=1" , and then press enter

clip_image003

3.Type Start "devmgmt.msc", and then press ENTER.

clip_image004

4.Click View, and then click "Show Hidden Devices"

clip_image005

5.Expand the Network Adapters.

6.Right-click the  hidden network adapter, and then click Uninstall.

clip_image006

Oz Casey, Dedeal  ( MVP North America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)

Twitter: https://twitter.com/message_talk