My Blogs

Before Windows Server 2012, patching for cluster server was very tedious job - move all the resource to a different node, stop the cluster service & install the patch to this node. After completion of one node, repeat the same for other nodes. It creates huge service outage. From Windows Server 2012, Cluster Aware Update is introduced which automated patch update process for Failover Cluster nodes & minimize the service outage.   Task performed by CAU : ·            Cluster role is moved to another node. By default, CAU selects the node which runs least roles to install the patch first. ·            The node where patch being installed, put into “Maintenance mode”. ·            Install the patch   & restart the node, if required. ·            Being the node “Out of Maintenance mode”. ·            Restore the Cluster Role. ·            Proceed for the next node   CAU run in two different modes : §    Remote-updating Mode : Update co-ordinator runs at t

After deployment of the  WSUS  server in the  network , we used to face two problems: 1 . The  client PC/Server is not getting registered into WSUS. 2.Event after registration, update agent has not been installed, hence no update received from WSUS. 1.a. Check Group Policy properly. Note that the policy is applied to Computer OU. Run  GPResult /R  command from  Command prompt Administrative mode . Remember to mention port number – 8530 ( http://W2012-WSUS:8530 ,  W2012-WSUS – Hostname of WSUS Server ) when you configure GPO.                                       Pix-01: GPO Settings for WSUS Clients                                   Pix-02: Intranet Microsoft Update Service location 1.b. Run  wuauclt.exe / detectnow  - register the client directly into WSUS’s respective container. After successful registration, clients would visible in the  WSUS  console. You can also check further from the  client’s  registry.                              Pix-03: