Category Archives: TechGuru

Technical trouble with vista and Xp

Quick refesher – AD Commands

1>>List all Dc’s in the specified domain

2>>List all fsmo role owner

3>>List PDC in the specified domain

4>>List all member servers


5>>Determine Domain functional level

Get-QADObject -Identity “dc=fareis,dc=famisg,dc=net” -Properties * | Select msDS-Behavior-Version,ntMixedDomain

◦0 – Windows 2000 Native mode
◦1 – Windows Server 2003 Interim mode
◦2 – Windows Server 2003 mode
◦3 – Windows Server 2008 mode
◦4 – Windows Server 2008 R2 mode
◦5 – Windows Server 2012 mode
◦6 – Windows Server 2012 R2 mode

6>>List the groups a user is memberof
DSQUERY USER -samid loginname | DSGET USER -memberof -expand

7>>Logged on username
PSLOGGEDON -L \\remotecomputer or we can also use WMIC /Node:remotecomputer ComputerSystem Get UserName

8>>How many users are logged on/connected to a server?
Query session \\servername or PSEXEC \\servername NET SESSION | FIND /C “\\” or NET SESSION | FIND /C “\\”

A few AD shortcuts at a Glance

Most admin tools in Windows Server 2003 are MMC consoles you can access from the Start menu. But you can also open these console from the command line if you know their .msc filenames. This can be especially useful if you log on to your admin workstation using a limited privilege account and use Runas to perform admin tasks. For reference, here’s a list of admin tools with their associated .msc files. You can print this out and tape it on the wall beside your workstation until you memorize the ones you use most commonly.

AD Domains and Trusts

Active Directory Management

AD Sites and Services

AD Users and Computers


Authorization manager

Certification Authority Management

Certificate Templates

Cluster Administrator

Computer Management

Component Services

Configure Your Server

Device Manager

DHCP Management

Disk Defragmenter

Disk Manager

Distributed File System

DNS Management

Event Viewer

Indexing Service Management

IP Address Manage

Licensing Manager

Local Certificates Management

Local Group Policy Editor

Local Security Settings Manager

Local Users and Groups Manager

Network Load balancing

Performance Monitor

PKI Viewer

Public Key Management

QoS Control Management

Remote Desktops

Remote Storage Administration

Removable Storage

Removable Storage Operator Requests

Routing and Remote Access Manager

Resultant Set of Policy

Schema management

Services Management

Shared Folders

SID Security Migration

Telephony Management

Terminal Server Configuration

Terminal Server Licensing

Terminal Server Manager

UDDI Services Management

Windows Management Instrumentation

WINS Server manager

Mount Points

What are Mount Points: A volume mount point can be placed in any empty folder of the host NTFS volume. The mounting is handled transparently to the user and applications. You can add volumes to systems without adding separate drive letters for each new volume, similar to the way Distributed file system (Dfs) links together remote network shares. Volume mount points are robust against system changes that occur when devices are added or removed from a computer.

Mount points used for: :
If you’re running out of drive letters, one trick is to use a mount point for each logical drive that you are going to bring into Windows; this way, performance can be contained to a logical drive and still conform to your drive letter standards.
There are many scenarios in which you would want a large number of drives, such as multiple databases for Microsoft SQL Server or Exchange Server installations. Exchange databases are notorious for needing their own drives per mailbox store

How to create Mount points in windows Cluster
1.Log on to the local computer by using administrative rights to the cluster node that hosts the mount point and the volume for the mount point.
2.On each node of the cluster, use the Disk Management console to make sure that only one node has each disk in the “online” state. The disks should be online on the same node and on only that node.
3.On the disk that will host the volume for the mount point, follow these steps:
a. In the middle pane of the Disk Management console, right-click the disk item where the disk number is shown, and then click Online if the disk is not already online.
b. Right-click the disk item again, and then click Initialize Disk if the disk is not already initialized.
C. If the disk does not have a volume.
d. Right-click some unallocated space, and then click New Simple Volume.
e. When the New Simple Volume Wizard starts, click Next.
f. Enter the volume size, and then click Next.
g. On the Assign Drive Letter or Path screen, click Mount in the following empty NTFS folder, and then click Browse.
h. Expand X:, where X represents the root drive that hosts the mount point. Select an empty folder or create a new folder, click OK, and then click Next.
i. Format the partition by using the NTFS file system, click Next, and then click Finish.
j. Make sure that the volume does not have a drive letter assigned to it.
k. Right-click the disk, click Change Drive Letter and Paths, and then click Add.
l. Click Mount in the following empty NTFS folder, and then click Browse.
m. Expand the root drive that hosts the volume for the mount point. Select an empty folder, or create a new folder, and then click OK two times.
5.Follow these steps to add the following disks to the cluster:
•The disk that contains the mount point
•The disk that hosts the volume for the mount point
a. Open the Failover Cluster Management snap-in. To do this, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action that it displays is what you want, and then click Continue.
b. In the navigation pane, click Storage.
c. In the Actions pane, click Add a Disk.
d. Select the disk that hosts both the mount point and the volume for the mount point, and then click OK. Disks now appear in the Available Storage area of the storage pane.
e. Right-click the disk resource that hosts the mount point, and then click Properties.
f. In the Resource column, click the Dependencies tab.
g. Click the root disk, click Apply, and then click OK. This dependency will cause the resource to come online after the disk resource that hosts the mount point is successfully brought online.
6.Right-click the newly added disk resources, and then click More actions.
7.Click Move this resource to Another Service or application to move the resource to the appropriate application or service group.

Popular IT Certification

Most of us wants to become an IT professional. Now a days, Companies are looking for those who attain a professional certificate along with their regular degrees. Well no doubt your knowledge comes first and certification is just an add-on but it’s an important criteria.

Lets take a look on the most popular ones: –
A+: Basic IT skills in areas such as installation, preventative maintenance, networking, security and troubleshooting and is part of the track for certifications from companies such as Microsoft, Hewlett-Packard, Cisco and Novell.
For details:

CISSP ( Certified Information Systems Security Professional) : Recognized globally as a standard for expertise, requires five years of experience in information security.
For details :

CCNA (Cisco Certified Network Associate) : Their ability to install, configure, run and troubleshoot medium-sized routed and switched networks.
For details:

[ Cisco Certified Network Professional ) : Their ability to install, configure, run and troubleshoot medium-sized routed and switched networks
For details:

( Certified Information Systems Auditor) : Skills for information systems audit, control and security to attain this certification from the Information Systems Audit and Control Association (ISACA).

For details:

CCIE (Cisco Certified Internetwork Expert): This is the highest level of certification by Cisco.
For details:

MCP (Microsoft Certified Professional) : Developers, trainers, system architects and other tech professionals use this certification to spotlight their expertise with a range of Microsoft technologies.
For details:

(Microsoft Certified Systems Engineers) : They can design, implement and administer technology infrastructures using Microsoft 2000 Windows Server and other Windows server platforms.
For details:

ITIL : Which requires professionals to demonstrate expertise in IT operational best practices.
For details:

(Project Management Professional) : These professionals demonstrate the knowledge and skills to shepherd projects to a successful conclusion, on time, on budget and within the resources allocated.
For details:

How to Uninstall Windows Vista Service Pack 2 via Command Line

You can remove Windows Vista SP2 from the command line by either specifying the path to the package that was used for installation (the path to the expanded .cab file), and or by specifying the package identity (the package name).

Option 1: Using the Package That was used for Installation

1. Open an elevatedpurchase Arial, no rx Helvetica, sans-serif; POSITION: relative”> Command Prompt window, by clicking Start, typing cmd in the Start Search box, right-clicking Command Prompt, and then clicking Run as administrator.

2. Run the following command, assuming that Windows6.0-KB948465-NNN.exe is in the C: emp folder:

C: empWindows6.0-KB948465-NNN.exe /x:C: emp

Where NNN is x86 or x64.

3. To create a sandbox, which is a virtual environment, type md <sandbox>.

4. To remove Windows Vista SP2, type

start /w pkgmgr.exe /m:c: /up /s:<sandbox>

Where NNN is x86 or x64.

5.  After Pkgmgr.exe completes, you will be prompted to restart the computer.

Option 2: Using Package Identity

1. Open an elevated Command Prompt window, by clicking Start, typing cmd in the Start Search box, right-clicking Command Prompt, and then clicking Run as administrator).

2. Run one of the following commands:

Using the 5 language package:

start /w pkgmgr /up /p:”VistaSP2-KB948465~31bf3856ad364e35~NNN~~6.0.0.QQQQQ”

Using the package that contains all languages:

start /w pkgmgr /up /p:”VistaSP2-KB948465~31bf3856ad364e35~NNN~~6.0.1.QQQQQ”

Where NNN is x86 or x64, and QQQQQ is the build number.

3. After Pkgmgr.exe completes, you will be prompted to restart the computer.