Windows

Test Cluster Failures and Failover Policies

Posted on Updated on


 Test cluster failures and failover policies

 

Test group failover policy

To test group failover policy

  1. Open Cluster Administrator.
  2. In the console tree, double-click the Groups folder.
  3. In the details pane, click the group.
  4. On the File menu, click Properties.
  5. On the Failover tab, set the Threshold to 0, and then click OK.
  6. In the Cluster Administrator console tree, click the group.
  7. In the details pane, click a resource.
  8. On the File menu, click Properties.
  9. On the Advanced tab, select the Affect the group check box, if it is not already selected.
  10. On the Advanced tab, set the Threshold to 0, and then click OK.
  11. On the File menu, click Initiate Failure.

 

Test whether group resources can fail over

To test whether group resources can fail over

  1. Open Cluster Administrator.
  2. In the console tree, double-click the Groups folder.
  3. In the console tree, click a group.
  4. On the File menu, click Move Group.On a multinode cluster server, when using Move Group, select the node to move the group to.

    Make sure the Owner column in the details pane reflects a change of owner for all of the group’s dependencies.

 

Test private network failures

To test private network failures

  1. Open Cluster Administrator.
  2. Verify that there are at least two networks set up for internal cluster communication and determine which network has the highest priority for internal cluster communications.For more information, see “To change network priority for communication between nodes” in Related Topics. When you follow that procedure, Cluster Administrator will only list those networks that support internal cluster communication.
  3. If there are two or more internal networks, continue to step 4, otherwise stop here and do not continue.
  4. On one node, unplug the cable for the highest priority network identified above.
  5. In the console tree, click the cluster node and verify that the state of the node is still Up (that is, actively participating in all cluster operations).

  

Test node failure

To test node failure

  • Test node failure using one of the following four methods:
  • Stop the Cluster service on the node.This prevents clients from accessing cluster resources through that node. In this event, all resources owned by this node fail over to other nodes in the server cluster.
  • Turn off the power on the node.This tests the ability of the server cluster to fail over all the resources that were owned by the powered down node.
  • On one node, unplug the network cables for all networks enabled for intracluster communications.This test disables all intracluster network interfaces for the node and prevents the node from exchanging heartbeats with the Cluster Network Driver on the other active nodes. In this event, the Cluster service then initiates failover of the resources owned by the node to the other nodes in the server cluster.

  

Start Cluster Administrator in Microsoft Management Console

To start Cluster Administrator in Microsoft Management Console

  1. Open Computer Management.
  2. In the console tree, double-click to expand Services and Applications.
  3. Right-click Cluster, and then click

 

Pause a node

To pause a node

  1. Open Cluster Administrator.
  2. In the console tree, click the node.
  3. On the File menu, click Pause Node.

  

Resume a node

To resume a node

  1. Open Cluster Administrator.
  2. In the console tree, click the node.
  3. On the File menu, click Resume Node.

 

Stop the Cluster service

To stop the Cluster service

  1. Open Cluster Administrator.
  2. In the console tree, click the node.
  3. On the File menu, click Stop Cluster Service.

  

Start the Cluster service

To start the Cluster service

  1. Open Cluster Administrator.
  2. In the console tree, click the node.
  3. On the File menu, click Start Cluster Service.

 

Set the Cluster service to only start manually

To set the Cluster service to only start manually

  1. Open Computer Management.
  2. In the console tree, click Services.Where?
    • Computer Management/Services and Applications/Services
  3. In the details pane, click Cluster Service.
  4. On the Action menu, click Properties.
  5. In Startup type, select Manual, and then click OK.

 

Notes

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.
  • To open Cluster Administrator, click Start, click Control Panel, double-click Administrative Tools, and then double-click Cluster Administrator.

clusterrosourcemovement[1]

Windows Server 2008 R2 stuck in recovery mode after power failure

Posted on Updated on


If you cannot boot into Safe Mode either, I suggest restarting the computer, keeping pressing F8 and choosing the Last Known Good feature.

If the issue persists, please try methods below:

Method 1:

  1. Put the Windows Server 2008 R2 installation disc into the disc drive, and then start the computer.
  2. Press a key when the message indicating “Press any key to boot from CD or DVD …”. appears.
  3. Select a language, a time, a currency, and a keyboard or another input method, and then click Next.
  4. Click Repair your computer.
  5. Click the operating system that you want to repair, and then click Next.
  6. In the System Recovery Options dialog box, click Command Prompt.
  7. Type sfc /scannow, and then press ENTER.

Method 2:

  1. Put the Windows Server 2008 R2 installation disc in the disc drive, and then start the computer.
  2. Press any key when the message indicating “Press any key to boot from CD or DVD …”. appears.
  3. Select a language, time, currency, and a keyboard or another input method. Then click Next.
  4. Click Repair your computer.
  5. Click the operating system that you want to repair, and then click Next.
  6. In the System Recovery Options dialog box, click Command Prompt.
  7. Type Bootrec /RebuildBcd, and then press ENTER.

 Method 3:

  1. Put the Windows Server 2008 R2 installation disc into the disc drive, and then start the computer.
  2. Press a key when the message indicating “Press any key to boot from CD or DVD …”. appears.
  3. Select a language, a time, a currency, and a keyboard or another input method, and then click Next.
  4. Click Repair your computer.
  5. Click the operating system that you want to repair, and then click Next.
  6. In the System Recovery Options dialog box, click Command Prompt.
  7. Type BOOTREC /FIXMBR, and then press ENTER.
  8. Type BOOTREC /FIXBOOT, and then press ENTER.
  9. Type Drive:\boot\Bootsect.exe /NT60 All, and then press ENTER.

Note: In this command, Drive is the drive where the Windows Server 2008 R2 installation media is located.

How to use the Replication Monitor to Determine the Operations Master and Global Catalog Roles

Posted on Updated on


Let us see how to use the Active Directory Replication Monitor (ReplMon.exe) tool to determine the servers that hold the operations master roles in a forest as well as the domain controllers and global catalog servers for the forest. The five operations master roles that are defined in Active Directory are:

  • Schema master
  • Domain naming master
  • Relative identifier (RID) master
  • Primary domain controller (PDC) emulator
  • Infrastructure master

There is a very quick method to determine which servers in the forest hold these roles by using Active Directory Replication Monitor.

The Setup program that installs Active Directory Replication Monitor (and other useful support tools) is available on the Windows 2000 Server CD-ROM under the \Support\Tools\Setup.exe folder. When this tool is installed, you can start it if you click Start, point to Programs, click Support Tools, click Tools, and then click Active Directory Replication Monitor.

Determine the Operations Master Role Holders

  1. Start the Active Directory Replication Monitor tool.
  2. Right-click Monitored Servers, and then add one or more servers by using the wizard.
  3. Right-click the servers, and then click Properties.
  4. Click the FSMO Roles tab.
  5. The domain controllers that hold all operations master roles are now displayed under the “Owner” column.
  6. To test the connectivity to each of the operations master role holders, click Query to the right of each role.

Determine Global Catalog Servers

  1. Start the Active Directory Replication Monitor tool.
  2. Right-click Monitored Servers, and then add one or more servers by using the wizard.
  3. Right-click the servers, and then click Show Global Catalog Servers in Enterprise.

How to user DsQuery

Posted on Updated on


To find all the domain controllers in the forest with DN and RDN:

  • DsQuery Server -o rdn -Forest
  • DsQuery Server -Forest

To find all the domain controllers in a domain:

  • DsQuery Server -domain domain_name.com

To list all the domain controllers in a domain that are also Global Catalog Servers:

  • DsQuery Server -domain domain_name.com -isgc

To list the domain controller in the forest that holds the Schema FSMO:

  • DsQuery Server -Forest -hasfsmo schema

Note: Use the “>” to store the output to a text file. The below command will store all the domain controller names in AllDCs.txt.

  • DsQuery Server -Forest > AllDCs.txt

How to export dump from AD

Posted on Updated on


There are 2 commands available for this:

1. Go to Start -> Run ->cmd

Paste the command in the below format:

ldifde

ldifde -f Exportuser.ldf -s ADservername -d “CN=username,CN=Users,DC=xxx,DC=xxx,DC=xxx,DC=com”

csvde

csvde -m -f AccountName_mailboxes.txt -d “cn=ADusername,OU=Group Mailboxes,OU=Groups,DC=xxx,DC=xxx,DC=xxx,DC=com” -r “(&(objectClass=*)(mail=*))” -l objectClass,member,displayName,memberOf,proxyAddresses,legacyExchangeDN,title,telephoneNumber,facsimileTelephoneNumber,mobile,homephone,givenName,company,userPrincipalName,co,c,physicalDeliveryOfficeName,postalCode,sn,st,streetAddress,title,wWWHomePage,description,l,initials,info,sAMAccountName

To get a serial number remotely for any server/desktop/laptop

Posted on Updated on


Run this command:

wmic /node:[remote computer name] bios get serialnumber

Or, if you would like to output to a text file:

set myfile = [The full UNC path with filename e.g. \\server\share\filename.txt]

wmic /append:%myfile% /node:[remote computer name] bios get serialnumber

Just open the shell with Admin rights, and type:

Get-WmiObject -ComputerName [remote computer name] -Class Win32_BIOS

or the short version:

gwmi -comp [remote computer name] -cl win32_bios

wmic cpu get name,CurrentClockSpeed,MaxClockSpeed This command will tell you the system motherboard (that happen to be the name) and it’s UUID

wmic bios get name,serialnumber,version This will tells you the name if your BIOS, current version and it’s serial number if there is any.

wmic csproduct  Computer system product information from SMBIOS 

Installing ADSI edit in Windows Server 2003

Posted on Updated on


The ADSI (Active Directory ServiceInterfaces) editor is a management console that comes along with the Windows Server support tools. Using this you can edit each and every attribute of the objects present in your active directory database. The support tools for the Windows Server OS is present in the OS installation CD. It is located at [CDDRIVE]:\SUPPORT\TOOLS\SUPTOOLS.MSI
If you don’t have the OS CD you can download it from Microsoft
Download Windows Server 2003 Support Tools
After installation got to Start -> Run and type adsiedit.msc to get the ADSI edit console.
If you get an error message saying adsiedit.msc is not found you have to register the DLL file required for it manually.
To do this go to Start-> Run and type regsvr32 adsiedit.dll.

How to Enable Remote Logins in a Windows server

Posted on Updated on


Locate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\

fDenyTSConnections value is set to 1 by default to disable remote desktop; editing the value remotely to 0 will enable remote desktop

How to download Cleanwipe Utility

Posted on Updated on


To download the utility, open the following web page in a browser:
https://fileshare.symantec.com
Log in with the following information:

Login ID: cleanwipeutility
Password: CL3@nw!p3

Once you have downloaded the utility, please follow these instructions.

Note: The .zip file may be password protected.
Un-Zip Password: symantec