Find the GPO name with GUID

If you run GPupdate /force command to update the Group policies in the GP clients, the results will display only GUID (Global Unique Identifier) of the GP which is failing to update. It will not show you the name of the GP. 

At that time, as a server admin, you should be able to find the GP name which is failing.

A.            Below PowerShell command will help you to find the GP name using its GUID.

1      1. Open PowerShell on Active Directory Server and type “Import-Module GroupPolicy”

2.       Get-GPO -Guid 31a09564-cd4a-4520-98fa-446a2af23b4b -Domain gmail.com

****Note: Here domain name would be your domain name where you are trying to apply the policies****

B.             We can get the GP name from Group Policy Management console as well. Below are the steps

1.       Open Group Policy Management console (GPMC.msc)

2.       Right click on domain name and click on Search, it will open a search box.

3.       Select “GUID” from the Dropdown and copy the GP GUID including {}. Click on Add

4.       Click on Search to search in Domain. You will see the GP name in search results. Below is one example.

\

Once you get the GP name, it is easier to identify the problem. 

How to Verify Authorized DNS servers for External Domain

Authorized DNS servers have the ability to Create\Modify\Delete DNS records for a Domain (Internal & External). If it is Internal Domain, Server Administrators can tell you the Authoritative DNS Server. If you would like to know for an External domain, go through the below steps.

1.       Open the URL https://www.whois.net/ Or http://www.whois.com/whois/

2.       Type the domain name for which you would like to know the DNS servers and click enter

3.       Search for the Name Servers list in the webpage after you entered the Domain name.

   

 Ex . DNS Name Servers for Gmail.com :

DHCP High Availability

DHCP High Availability:-

A highly available solution must account for all possible points of failure, including server failures, WAN link interruptions, and router failures. You can increase the fault tolerance and availability of your design by using one or more of the following, depending on your needs and hardware cost considerations:

• Split-scope configurations
• Clustered DHCP servers
• Using standby servers

Split-Scope Configurations:-

You can increase fault tolerance by splitting DHCP scopes between multiple DHCP servers. With a split-scope configuration, if one server becomes unavailable, the other server can take its place and continue to lease new IP addresses or renew existing clients.

Splitting DHCP scopes also helps to balance server loads.

When splitting the IP address pool of a scope between two servers, assign the same scope to both servers, and exclude opposite portions of the address range. You also need to make identical reservations at both DHCP servers, so that either server can assign the reserved IP address, ensuring that the intended device receives the address that is reserved for its use.

Clustered DHCP Servers:-

Windows Clustering can automatically detect the failure of an application or server and restart the application on or transfer the server role to an alternate server. Users experience only a brief break in service.

Windows Clustering creates a virtual DHCP server so that if one of the clustered nodes fails, the namespace and all of the services contained in that node are automatically transferred to a second node. No changes are visible to the client, which sees the same IP address for the clustered DHCP servers.

Standby Servers:-

A standby server and its scopes are not activated for use under normal conditions, and are activated by the administrator only when needed, such as when a DHCP server fails or is taken offline for an extended period of time. Standby servers require manual administration to ensure failover transition, and therefore might not be as effective as other failover methods, such as split scopes and clustered servers.

To use a standby configuration, configure an additional DHCP server to server as a backup if the primary server goes offline. You can either configure the standby server to be identical to your primary DHCP server or configure the standby server with unused scopes to temporarily replace the primary DHCP server.

Differences between Quick Format and Full Format

1. Quick Format: If you choose the Quick format option, format removes files from the partition, but does not scan the disk for bad sectors. Only use this option if your hard disk has been previously formatted and you are sure that your hard disk is not damaged.

2. Full format: When you choose to run a regular format on a volume, files are removed from the volume that you are formatting and the hard disk is scanned for bad sectors. The scan for bad sectors is responsible for the majority of the time that it takes to format a volume.

DHCP Rely Agent

DHCP Rely Agent:

If you have multiple subnets in your network, and do not have a DHCP server on every subnet, determine whether your current routers (Software\Hardware) relay DHCPmessages.

The DHCP relay agent relays DHCP message traffic between the DHCP-enabled clients on the local network and a remote DHCP server located on another physical network by using the IP address of the remote DHCP server.

How relay agents work

A relay agent relays DHCP messages which were broadcasted by NIC's on the network.

The following illustration shows how client C on Subnet 2 obtains a DHCP address lease from DHCP server 1 on Subnet 1.



1. Client C generated a broadcast message when it turned in the networ. It will use UDP protocal for this generation on the port 67 (the port number reserved and shared for DHCP server communication).

2. In this case DHCP relay agent willtake the broadcasted message from the network and check for the gateway in the DHCP message header. If it did not find any gateway information it will fill that with router IP and sent it to Subnet 1 where DHCP server is located.

3. When the DHCP server recives the message, it will check the gateway IP and will check the DHCP scope where the router IP has beed configured.

4. After that it will check the DHCP scope and will release an IP from the scope and will to the DHCP relay with the IP configuration.

5. Then, DHCP realy agent will send that informatino to the client and it will take DHCPREQUEST from the client and will send it to server.

6. Again, it will receive DHCPACK packet from the server and will forward that to the client.


 Configure the DHCP Relay Agent

•Add the DHCP Relay Agent
•Configure global DHCP Relay Agent properties
•Enable the DHCP Relay Agent on a router interface

Add the DHCP Relay Agent

1. Open Routing and Remote Access.
2. In the console tree, click General.
   Where?
   • Routing and Remote Access/server name/IP Routing/General
3. Right-click General, and then click New Routing Protocol.
4. In the Select Routing Protocol dialog box, click DHCP Relay Agent, and then click OK.

Configure global DHCP Relay Agent properties

1. Open Routing and Remote Access.
2. In the console tree, click DHCP Relay Agent.
   Where?
   • Routing and Remote Access/server name/IP Routing/DHCP Relay Agent
3. Right-click DHCP Relay Agent, and then click Properties.
4. On the General tab, in Server address, type the IP address of your DHCP server, and then click Add.
5. Repeat step 4 for each DHCP server you need to add, and then click OK.

Enable the DHCP Relay Agent on a router interface

1. Open Routing and Remote Access.
2. In the console tree, click DHCP Relay Agent.
   Where?
   • Routing and Remote Access/server name/IP Routing/DHCP Relay Agent
3. Right-click DHCP Relay Agent, and then click New Interface.
4. Click the interface you want to add, and then click OK.
5. In the DHCP Relay Properties dialog box, on the General tab, verify that the Relay DHCP packets check box is selected.
6. If needed, in Hop-count threshold and Boot threshold (seconds), click the arrows to modify the thresholds.

BlackBerry Perf. Counters missed on server

Performance of Any application we can observe using Performance counters on windows server. These counters will install while installing the application on the server. If we install active Directory on the server it will install performance counters too.

Most of the cases we will face Performace counters which are related to the BlackBerry on Windows server with 64 bit. While installing black berry application on the server it will install 32 bit counters on the server. If the server is with 32 bit we can see tha counters with out any issue. If it is 64 bit we will need to uninstall 32 bit counters and install 64 bit counters.

1. Un-installtion of 32 Bit counters:

Open CMD(Run as administrator) on the server and go to the path " C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\". After that type the below commands to unregister 64 bit counters.

Regsvr32 /U AgentPerfSession.dll and press ENTER
After go to the path "C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\BypassRouter" and type the below commands
Regsvr32 /U RouterPerfClient.dll and press ENTER
Regsvr32 /U RouterPerfSession.dll and press ENTER

This will complete the unregistration of 32 bit counters on the server. Then we need to install 64 counters.

Type cd "C:\Program Files" and press ENTER
Type mkdir "Research In Motion\BlackBerry Enterprise Server" and press ENTER
Type cd "C:\Program Files\Research In Motion\BlackBerry Enterprise Server\" and press ENTER
Copy AgentPerfSession.dll into this folder from the "[the extracted installer folder]\tools\WMI\x64\"
Copy AgentWMIPerf.mof into this folder from the "[the extracted installer folder]\tools\WMI\"
Type regsvr32 AgentPerfSession.dll and press ENTER
Type mofcomp.exe AgentWMIPerf.mof and press ENTER
Type mkdir BypassRouter and press ENTER
Type cd BypassRouter and press ENTER
Copy RouterPerfClient.dll and RouterPerfSession.dll into this folder from C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\BypassRouter"
Copy RouterClientPerf.mof and RouterSessionPerf.mof into this folder from C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\BypassRouter"
Type Regsvr32 RouterPerfClient.dll and press ENTER
Type Regsvr32 RouterPerfSession.dll and press ENTER
Type Mofcomp RouterClientPerf.mof and press ENTER
Type Mofcomp RouterSessionPerf.mof and press ENTER
Restart the computer
Launch the Performance Monitor using Start > Run > Perfmon /wmi

Active Directory Performance Counters Issue

Performance of Any application we can observe using Performance counters on windows server. These counters will install while installing the application on the server. If we install active Directory on the server it will install performance counters too.

Few cases we did not find the perf. counters on the servers. Most of the cases the issue withe enable or disable counters registry in registry keys. We have that option where we can enable/Disable performance counters in the registry keys. Registry path for the AD is as below:

HKLM\System\CurrentControlSet\Services\NTDS: in this registry we have one sub registry "DisablePerformanceCounters" key to enable or disable counters. If the value is set to 0 that means counters were enabled. We need to make sure that the value should be Zero to enable counters.

Once we done with the above registry we need reload the counters to Performance counters using the command "lodctr.exe /r" in Windows\System32 folder. Once we done with the loading counters we can see the counters in the performance counters.

To transfer these counters to WMI repository we need to use "WMIADAP.EXE /F" command. This ADAP (AutoDiscovery/AutoPurge) process will load the counters to WMI repository forcefully. Once we done with the above process we must restart the WMI service on the server. If you fail to restart the WMI service go for reboot and check.

Solution 2: If you are unable to find the above registry on the server we can export from any other Domain controller and import on the target server. These counters will differ based on the OS version of the server. We need to Import windows 2003 server AD registry keys to Windows 2003 server only. same for 2008 servers also.

Once you done with the above steps you will get missed performance counters on the server.