Author: Ashish Kumar Singh

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 change the thick or thin provisioning of a virtual disk

Posted on Updated on


Caution: Before following these procedures, it is highly recommended that you have a valid backup of the virtual machine and enough space to convert the virtual machine’s disk(s) from thin to thick.

To change the provisioning of a virtual machine base disk from thin to thick from the Datastore Browser:

  1. Power off the virtual machine.
  2. In vSphere Client, right-click the virtual machine in the inventory.
  3. Click Edit Settings to display the Virtual Machine Properties dialog box.
  4. Click the Hardware tab and select the appropriate hard disk in the Hardware list.Note: The Disk Provisioning Type section on the right displays either Thin Provision or Thick Provision. If the disk provision type is Thick, disk provisioning has already taken place. In this case, the disk provisioning is Thin.
  5. Click Cancel to exit out of Virtual Machine Properties dialog box.
  6. Click the Summary tab of the virtual machine.
  7. Under Resources, right-click the datastore where the virtual machine resides and click Browse Datastore.
  8. Double-click the virtual machine folder to display the .vmdk file.
  9. Right-click the .vmdk file, and click Inflate. The Inflate option converts the disk to thick provisioned.
  10. Reload the .vmx file. For more information see Reloading a vmx file without removing the virtual machine from inventory (1026043).

Notes:

  • If the Inflate option is grayed out, this indicates that the virtual machine is not powered off or that it is not thin provisioned.
  • There should be no snapshots and the conversion is performed on the base disk.

To convert a virtual machine base disk from thick to thin provisioning by changing the datastore and using offline virtual machine migration:

Note: This process requires more than one datastore. If only a single datastore exists, you can clone the virtual machine to a destination machine with thin provisioned disks instead of migrating.

  1. Power off the virtual machine.
  2. Right-click the virtual machine, and click Migrate.
  3. Click Change datastore.
  4. Click Next, and select a datastore that is not the same as the current datastore.
  5. From the dropdown, select the Thin Provision virtual disk format.
  6. Click Next, then Finish. You can monitor the progress of the conversion in the Tasks and Events view in vCenter Server.

Follow the below steps to do Storage vMotion from vSphere Webclient for vSphere 5.5:

  1. Right-click the virtual machine and select Migrate.
    1. To locate a virtual machine, select a datacenter, folder, cluster, resource pool, host, or vApp.
    2. Click the Related Objects tab and click Virtual Machines.
  2. Select Change datastore and click Next.
  3. Select “Thin Provision” for the virtual machine’s disks and click Next
  4. Select a virtual machine storage policy from the VM Storage Policy drop-down menu, click Next
  5. Select the datastore location where you want to store the virtual machine files and click Next.
  6. Review the information on the Review Selections page and click Finish.

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

DCICN Exam – Cisco Data Center Networking (640-911) details and Study Guide

Posted on Updated on


The 640-911 DCICN “Introducing Cisco Data Center Networking” is one of the exams associated with the CCNA® Data Center certification. This 90-minute 65−75 questions exam tests a candidate’s knowledge of networking concepts for the Data Center environment, based on Nexus-OS. You will learn fundamental information on how a Data Center network works; and how to configure virtualization in the network, addressing schemes, troubleshooting and configuration skills. Candidates can prepare for this exam by taking the course 640-911 DCICN, “Introducing Cisco Data Center Networking”.

The following topics are general guidelines for the content likely to be included on the exam. However, other related topics may also appear on any specific delivery of the exam. In order to better reflect the contents of the exam and for clarity purposes, the guidelines below may change at any time without notice.

Download Complete List of Topics in PDF format

The Study/Learn tabs for the 640-911 DCICN Exam page.

DCICN Exam Topics Duration Learn
More
Media
Type
Access Now
Describe how a network worksHide Titles
Preparing for your CCNA Data Center Certifications Studies 00:43:00 Watch Now
Internetworking Basics 29 pages View Now
Understanding the TCP/IP Internet Layer 00:25:00 Watch Now
Cisco NX-OS Command Line Introduction Series CLN Premium Content
01:29:42 Subscribe Now
Cisco NX-OS Advanced Features Series CLN Premium Content
01:13:40 Subscribe Now
NX-OS and Cisco Nexus Switching: Next-Generation Data Center Architectures 480 pages Buy Now
Configure, verify and troubleshoot a switch with VLANs
and interswitch communicationHide Titles
Ethernet Technologies 46 pages View Now
Introduction to LAN Protocols 9 pages View Now
Understanding VLANS by Understanding MAC Table Operation 4 pages View Now
Calculating an 802.1d Spanning-Tree Topology 20 pages View Now
Implement an IP addressing scheme and IP Services to meet network
requirements in a medium-size Enterprise branch office network
IPAddressingGuide 1 page View Now
IP Addressing and Subnetting for New Users 12 pages View Now
Binary Game Varies Play Now
Subnet Game Varies Play Now
Subnet Troubleshooting Game Varies Play Now
IP Routing – Introduction Varies Watch Now
Configure, verify, and troubleshoot basic router operation
and routing on Cisco devicesHide Titles
Routing Basics 11 pages View Now
IP Routing – Introduction Varies Watch Now
Introducing EIGRP 00:22:00 Watch Now
Introducing the OSPF Protocol 00:23:00 Watch Now
Nexus 7000 Series Data Sheet 8 pages View Now
Nexus Licensing 44 pages View Now

Keyboard or mouse do not work in a hosted virtual machine

Posted on Updated on


To troubleshoot a misbehaving mouse or keyboard:
  1. Confirm that the virtual machine guest window currently has focus by clicking into the virtual machine’s console window. Keyboard or mouse input is only directed to the virtual machine when it has focus or is in full-screen mode.
  2. If your mouse is slow to respond or if it is working erratically, change the optimization settings. For more information, see Mouse movement is not smooth in a hosted virtual machine (1033416).
  3. If you are using a wireless mouse or keyboard, ensure that you have not connected it to the virtual machine by removing and re-adding the USB Controller from the virtual machine. For more information, see the Workstation Help topic Add a USB Controller to a Virtual Machine.
  4. Restart your host computer.
  5. For Windows hosts, use the Windows System Configuration (msconfig) utility to eliminate software and processes as possible causes. For more information, see Using the Windows System Configuration utility (1004010).
  6. For Linux hosts, start Linux in a mode that disables start daemons (typically run level 2; if your host lacks this, you may need to start in single-user mode). For more information, see Changing Linux run levels (1004015) or your operating system documentation.
    Note: These next steps require a second mouse/keyboard. For more information, see Connecting a second mouse or keyboard directly to a hosted virtual machine (1033435).
  7. Look for non-Microsoft, non-VMware mouse/keyboard drivers or software installed in the virtual machine, and remove them.
  8. Re-install VMware Tools. For details, see Overview of VMware Tools (340).