How to create a notification channel for Azure Service

 
Here I’m going to configure a monitoring widget which supported by Azure. For that, I have selected SQL Database and going to show how to configure monitoring rule to get the alert notification.
To configure monitoring rule, you can go into Settings > Monitoring > Alert Rule



The metrics that you can select is limited. But it covers the required monitoring service package. You can select the required metric from the list down




Then you can create the conditions that you need. This way you can fine tune your rule..

Threshold you can set as a percentage.
Finally you can set the Email alert and the Webhook.
Webhook is a notification service which is support HTTP or HTTPS alert notifications to other systems for post-processing or custom notifications.

Hope this will help you to get an idea about the Azure SQL service monitoring rules.

How to install Nano Server in Microsoft Azure

First, you need to log into Azure online portal (https://login.microsoftonline.com) and then you can follow the below mentioned steps to create your Nano server. If you don’t have an Azure account, then you can get a one month free trial. For that, follow this link https://azure.microsoft.com/en-us/account
To create a Nano VM, In the Windows Azure portal go in to
Virtual Machines > New
Then from the next windows you can select the from Gallery and go in to the Gallery.
Select the "Windows Server 2016 Core with Containers Tech Preview 4" Virtual Machine.

Give a Server name and select the Tire. In my case I'm going with Standard one. Then, Select Size and give a User name and the Password to the server.

Then Give a Cloud service, DNS name and if you want, you can change the Region.

Under Endpoints, you can give the ports which you want to open to the outside. This you can add later.

Select the configuration that you want to add in the initial configuration. Here I'm adding VM agent. You can add those third-party extensions later.

Ok Now you are done with the installation.

Next I’ll try to show the PowerShell Remoting on Nano Server.

How to Recover from (1722) RPC Server is Unavailable – Windows 2008

When you run repadmin /replsummary Command this will display the current status of the Domain Controllers.

Seems like there are a couple of DC’s are not replicating and need to check this one by one. In this situation you can see that couple of sites were not synced for more than 60 days.
This can be happened because of coupe of issue. I have listed a few of them that comes to mind. Hope when you are reading this, you will also take this as a check list and verify your environment before going for the deep troubleshooting
1. Changes have done to the network.
2. New firewall rules added.
3. Initially two paths(or VPN) were there to communicate with the branch network and suddenly one failed. 
4. New DNS Server added or new PDC added to the head office
5. Secondary Domain Controller was offline for couple of months.
6. VPN network is extremely slow and time to time connectivity issues also occurring.
If these kind of issues are there in the network then you should address those issues first. then can go deeper to the second level troubleshooting.
---------------------------------------------------------------------------------------------------------------------------------
Once you run repadmin /syncall command on one of that server you will get and information like below,

To troubleshoot the issue, First need to check whether this server is resolving the DNS.
Go to DNS setting and rite click on the Server name and go to Properties.

Check the Interfaces and the Forwarders. Under Interfaces you need to make sure the correct listing interface is configured and under forwarders need to add the correct DNS server which this server can resolve the FQDNs
     
Under interfaces, Sometime you will see couple of interfaces which is configured in the Server. Then you can select the correct listening interface by selecting the “Only the following IP address” Radio button.
Check whether the correct name servers are added.Go in to Forwarder Lookup Zone in DNS Manager. Right click on "Domainname.com" then select properties.

Under Name servers check whether the correct name server are there. If not add them

Under Forwarder check whether correct DNS Server is listed. If not add that and checked whether that IP address is resolving the FQDN

Once this done verify the startup value and service status for the is correct for the below mentioned Windows services.

Reference : https://support.microsoft.com/en-us/kb/2102154
Once this done you need to check the Correct Sites were added under site and services . This you need to check in PDC and the ADC.

You can right click on NTDSsettins and select New > Connection then add the correct Active Directory domain controller. Now new ADC connection was added.
Now you can run dcdiag /test:dns
The replication will take time and this will depend on the network connectivity. keep for couple of hours and restart the ADC and check the replication.
If you want to do the replication forcefully you can run,
repadmin /syncall /APed
If you still facing issues with the replication, you need to do a metadata cleanup on those two servers.

How to Move database in Exchange 2013

When the default installation of exchange server will create the Databases in same location. It's good to have those Databases and the Log file in separate drivers.

To do this you can follow below mentioned steps.

Initial database will be configured under Program Files> Microsoft > Exchange Server >  V15 > Mailbox

You can use Get-MailboxDatabase cmdlet to  view current list of databases.

 To view the location of any of those database you can  type, Get-MailboxDatabase -DatabaseName | FL Name,*Path*. 

For example, we want to view the location of Database named “Mailbox Database 0693451254”.

You can use, Get-MailboxDatabase “Mailbox Database 0693451254” | fl Name, *path*

To move the Mailbox database you can use below command, 

 Database will be moved to E: Drive and Log file will be moved to F: Drive

Move-Databasepath “Mailbox Database 0693451254″ -EdbFilepath “E:\Exchange_Database\Mailbox Database 0693451254.edb” -LogFolderpath “F:\Exchange_Archive”

Press "Y" and wait till this complete.

Once this done, you can see that this databases were move in to the locations that we have specified.

To verify the database locations, you can run the following command again.

Get-MailboxDatabase - Database 0693451254 | FL Name,*Path*

 Or else you can go in to Exchange admin Center> Server > Mailbox Database > General

NLB in Windows 2012 Step by step

 
Network Load Balancing clusters enable you to manage a group of independent servers as a single system for greater scalability, increased availability, and easier manageability. You can use Network Load Balancing to implement enterprise-wide scalable solutions for the delivery of Transmission Control Protocol/Internet Protocol (TCP/IP) based services and applications.Network Load Balancing as many advantages over other load balancing solutions that can introduce single points of failure or performance bottlenecks. Because there are no special hardware requirements for Network Load Balancing, you can use any industry standard compatible computer in a Network Load Balancing cluster.
1. First need to  Install the Windows NLB feature on all of the node (In my case two nodes) need to be added into the NLB.
Go in to Server manager > Manage >Add New Feature

 

2. Then you will get the below mentioned detail screen. click next to continue


3. Need to select Role-base or Feature-base installation. If you are doing this remotely from another server then you can select the second option.


4. Select the Server from the server pool


5. Next page, now you can select NLB feature and click next.


6.Add the features.


7. now you can see the confirmation window. read that and click next to proceed.
 

8. Once done, you will be able to logging to NLB wizard


9. Go in to “Network Load Balancing Manager” and right click and select "New Cluster"


10. Now you can give the primary Server Host IP address


11. Next window will ask for a cluster IP and the Name configuration.



12. Other Cluster parameter can be entered here.


13. Here you can configure the port rules.


14. Recommended way is to add the port rules and initial configuration you can keep all ports open. When you are commissioning then you can add the specific ports.


15. Once this done, you will see the firs node was added to the NLB cluster. now you need to configure the secondary node.


16. Follow the same steps mentioned above and give the secondary server IP address.


Here you can see that I have configured a another network card for HB.




Now you will see both the nodes are active.


If you want to change the Priority of those nodes you can select one node and change the priority.


Hope this will help you to configure NLB in Windows 2012 Server.