Since last few months there has been yellow alert from Microsoft Team on the Enforcement of SHA1 Certificates. Not only Microsoft team but also the other certificate provider and browsers too. Although most of the public SSL has already using SHA2 or we say SHA256, still there might be some private certificate with SHA1. Hence
Email has become the Business-Critical application on any of the enterprise. And to secure such infrastructure, there arises a challenge for everyone. If we go with the history of the Microsoft Exchange, since Exchange 2013 Microsoft has enhanced its security feature for the inflow and outflow of the emails. One of the feature for the
On Exchange server, configuring virtual directory might be pain sometime. A simple misconfiguration of Virtual directory might be the worst nightmare and create login loop, because I had this few days back. While configuring additional CAS server after few changes done on the Virtual directory, my OWA/ECP page start to go on loop whenever I
Role Based Access Control (RBAC) is one of the most useful feature on Exchange 2016 or Exchange Online. Although RBAC has been there since Exchange 2007, It has been more enhanced and flexible on Exchange 2016. In Exchange 2007, the server permissions model applied only to the administrators who managed the Exchange 2007 infrastructure. In
Another important part of the exchange server is to configure the certificate. Certificate makes the web-based mail access secure as well authenticated and this part is quite recommended on the enterprise level, if we check from the Exchange 2013 all the console is browser based. To configure the certificate on the Exchange server it requires
This is one of the most customizing part of the Exchange Server, whether it be 2007 or 2010 or 2013 or 2016. Any version we install we always change this portions… so why??? Would be the question. Virtual Directory links you with your Exchange server portal, and you don’t like it to be ‘EXGServer.pdhewaju.com.np‘ or
Let’s get to the Installation procedure, it has been almost week that I have been blogging about the Exchange server 2016. Before Installing Exchange 2016, I would like to get back to my Perquisites of exchange server. Specifically, on Hardware part, it might be varying but yet at least we need this one.
Here in this blog we are discussing about the Exchange Server 2016 Architecture, unlikely the older version of Exchange server, Exchange 2016 is quite different. As described on our previous blog, On Exchange 2016 Architecture has been modified and that Single BOX is accumulated with CAS, HUB Transport and Mailbox know as Mailbox Role and
Microsoft Has released Exchange 2016 recently and we all are eager to see what’s new on Exchange 2016. But, before installing the Exchange 2016 there are few requirements that we need to know about it. Like Operating system, co-existence of system, supported client, .net framework etc. Here I will be elaborating what are the required
