Archive for March, 2011

You have probably noticed that Windows Server 2003 has a new feature that requests a shutdown reason each time you restart the server. This feature is called the Shutdown Event Tracker.

You might choose to disable this feature to avoid the hassle of typing in a reason each time you restart.

To disable this feature, you can perform the following steps:

1. Click Start, click Run, and type gpedit.msc and press Enter.

2. Expand the Computer Configuration and then Administrative Templates objects. Click on the System object. In the right-hand pane you’ll see several settings appear.

3. Locate and double-click that Display Shutdown Event Tracker setting. The Display Shutdown Event Tracker Properties dialog box opens.

4. Click the Disabled radio button to disable the Shutdown Event Tracker. Click OK. Close the Group Policy Editor console. Now when you shut down this server, you won’t be asked to enter a reason.

 

Advertisements

Robocopy Command

Posted: March 25, 2011 in Bios, Commands
Tags: ,

To run the Robocopy command you need to be in any of the two Servers.

Then open the command prompt and run the below command:

robocopy “\\source servername\Parent Foldername\Foldername” “\\destination server name\Parent Foldername\Foldername” /e /r:20

 

 

 

The LDAP is a standardized protocol used by clients to look up information in a directory. An LDAP-aware directory service (such as Active Directory) indexes all the attributes of all the objects stored in the directory and publishes them. LDAP-aware clients can query the server in a wide variety of ways.

 

Every object in Active Directory is an instance of a class defined in the Active Directory

schema. Each class has attributes that ensure unique identification of every object in

the directory. To accomplish this, Active Directory relies on a naming convention that

lets objects be stored logically and accessed by clients by a standardized method. Both

users and applications are affected by the naming conventions that a directory uses. To

locate a network resource, you’ll need to know its name or one of its properties. Active

Directory supports several types of names for the different formats that can access

Active Directory.

 

These names include:

■ Relative Distinguished Names

■ Distinguished Names

■ User Principal Names

■ Canonical Names

 

Virtual private networking (VPN) provides a way of making a secured, private connection from the client to the server over a public network such as the Internet. Unlike dial-up networking, in which a connection is made directly between client and server, a VPN connection is logical and tunneled through another type of connection. Typically, a remote user would connect to an Internet service provider (ISP) using a form of dial-up networking (particularly good for users with high-speed connections).

The Routing And Remote Access server would also be connected to the Internet (probably via a persistent, or permanent, connection) and would be configured to accept VPN connections. Once the client is connected to the Internet, it then establishes a VPN connection over that dial-up connection to the Routing and Remote Access server.

 

Automatic Private IP Addressing

 

Automatic Private IP Addressing (APIPA) is a feature introduced with Windows 2000; it is also included in Windows XP and Windows Server 2003.

 

APIPA allows a computer that is configured to obtain an automatic IP address to assign itself an address from a private range should no DHCP server be available. APIPA assigns addresses in the range 169.254.0.1 through 169.254.255.255—a range reserved by Microsoft for just this purpose.

 

APIPA is really designed for small networks that don’t use a DHCP server. APIPA allows computers running Windows 2000, Windows Server 2003, or Windows XP to plug into a network and recognize one another with little configuration necessary. If your network uses a DHCP server and you see that a client has been assigned an address in the APIPA range, it means the client could not locate a DHCP server.

 

Routing is the process of moving information along a path from a source to a destination.

On a TCP/IP network, the source and destination are called hosts and the information is broken apart into small packets that are transmitted between these hosts. The IP handles the routing of all these packets for the network.

 

Remember that a protocol such as TCP or UDP hands down a packet of data to the IP protocol for transmission to a remote host. IP must determine where the packet goes.

First, it compares the network ID of the local host with the network ID of the destination host identified in the packet. If the two network IDs match, the two hosts are on the same network segment and the packet can be sent directly to the destination host.

 

If IP determines that the network IDs of the local host and the remote host do not match, that means that the two hosts are on different network segments and the packet cannot be sent directly. Instead, IP must send the packet to a gateway, which is a router connecting one network segment to another. When this gateway receives the packet, its IP protocol goes through the process of comparing network IDs to determine the best place to send the packet. If the destination host is on one of the network segments to which the gateway is directly connected, the gateway can forward the packet straight to the destination host. Otherwise, the gateway forwards the packet on to another gateway, and then perhaps another, until the packet finally reaches its destination. Each time a packet crosses a gateway that is referred to as a hop. For example, if a packet must cross three routers to reach its destination that is considered three hops.

 

Usually, the source host is configured with the IP address of a default gateway, a router to which all packets are sent if the destination host is not found on the same network segment. Routers (and all devices with IP installed, for that matter) are able to consult routing tables that are stored in the router’s memory. A routing table holds information on preferred routes for various network IDs. This way, the router can determine the best gateway to which to send a packet based on the network ID of the packet’s destination host. There are two ways in which a router can build its routing table:

 

Static A static router has a routing table that is constructed and updated manually.

In other words, someone must actually access the routing table to create

routes the router can use.

 

Dynamic A dynamic router builds and updates its own routing table as it finds

appropriate routes. When it finds shorter routes, it favors those over longer routes.

Most important, dynamic routers can also share their information with other

routers on the network. Almost all the routers in use today are dynamic routers—

manual routers are just too much work. Dynamic routers use one of two common

routing protocols: Routing Information Protocol (RIP) and Open Shortest Path First

(OSPF).

 

Installing Dell OpenManage 5.x on ESX 3.X

Note: ESX 3.5 systems, Patch ESX350-200802412-BG need to be installed prior to the OpenManage Installation. This patch addresses an issue related to event reporting in Dell OMSS. This patch may be downloaded from http://www.vmware.com/download/vi/vi3_patches_35.html. For further details, refer to http://kb.vmware.com/kb/1003459.

 

Dell OpenManage Package from support.dell.com

 

Use the following steps to download Dell OpenManage:

 

1. Go to http://support.dell.com

 

2. Select “Drivers and Downloads”

 

3. Select the appropriate server model (example: PowerEdge 2950) or enter the Service Tag of the server

 

4. For “Operating System,” select “Red Hat Enterprise Linux 4”

 

5. For “Category,” select “Systems Management”

 

6. Click on “Dell OpenManage Server Administrator Managed Node” to download a tar package for Server Administrator.

 

7. If the version of Dell OpenManage you require is not the latest release, click on “Other Versions” to find previous releases

 

The following are the steps to install OpenManage 5.x on ESX 3.x:

 

1. Log on with administrator privileges (root) to the Service Console.

 

2. Make sure there is at least 512MB of free disk space in the /root partition of ESX Server service console. This can be verified by running the df –lh command in the service console.

 

3. Use the following steps to install OpenManage Server Administrator:

 

Copy the file to ESX using WINSCP to

 

# /etc/tmp/update

Create an Update folder under /etc/tmp

 

Unzip the file

$ tar -zxvf OM_5.1_ManNode_LIN_A00.tar.gz

 

where OM_5.1_ManNode_LIN_A00.tar.gz is the file downloaded from http://support.dell.com

 

4. Install OpenManage by executing the installation script and following the onscreen instructions:

# ./setup.sh

 

a. If you are installing OpenManage on a Dell PowerEdge 1855, PowerEdge 1955, or on a system that does not have a Dell Remote Access Card (DRAC), use the following command:

 

$ ./srvadmin-install.sh –b –w -s

 

b. If you are installing Dell OpenManage on a PowerEdge M600, M605, or a server with DRAC, use the following command:

 

$ ./srvadmin-install.sh –b –w –r -s The options used in the OpenManage installation script expand as: b: Base install of OpenManage Server Administrator w: Web interface for OpenManage Server Administrator r: Dell Remote Access Controller (DRAC) services s: OpenManage Storage Management (OMSM)

 

5. To start the OpenManage services without rebooting the system, execute the following command:

$ srvadmin-services.sh start

 

 

6 To access the ESX server using an OpenManage Web Administrative console, open the ports used by OpenManage using the following commands:

 

$ esxcfg-firewall -o 1311,tcp,in,OpenManageRequest

 

 

To check the Dell Open manage

 

https://esxip:1311

 

 

Enable mode: Used to view the switch configuration, port status and basic stuffs.

COMMAND: enable

IDENTIFICATION: >

 

Config mode: Higher lever mode to view advanced features, configure the device.  It is the mode from where all other modes can be entered.

COMMAND: configure

IDENTIFICATION: #

 

Interface mode:  used for configuring the interface

COMMAND: interface <ifname>

IDENTIFICATION: (config-if)#

 

BASIC COMMANDS:

Step 1) Set hostname

# configure

(Config)# hostname <name>

 

Step2) configure management ip

(Config)# interface vlan 1

(config-if)# ip address <ip add> <mask>

 

Step3) configure the username & password for Level 15

Config)# username <uname> password <pwd> level 15

 

Step4) configure default gateway

Config)# ip default-gateway <gatewayip>

 

Step5) configure http access

Config)# ip http authentication local

 

Step6) configure telnet, ssh and console password

Config)# line console

Config-line)# password <pwd>

 

Config)# line  telnet

Config-line)# password <pwd>

 

Config)# line ssh

Config-line) password <pwd>

 

Step7) Setup VLAN

Config)# vlan database

Config-vlan)# vlan 250

Config

 

Cisco ASA5505 Firewall overview

Cisco ASA5505 firewall is a small box with the following layout:

It has eight Ethernet ports marked 0 to 7 and one Console port marked blue.

–  Connect the Console port to the local server or any computer from which you will configure the box: the Console      cable must be connected to Serial port of the computer. Note: it is needed for configuration only; later this    connection can be removed.

–  Port 0 of the ASA must be attached to Internet Provider’s equipment: connect it to the ISP modem.

–  Port 2 of the ASA must be attached to the local Ethernet switch.

–  Connect the Server and computers to the Ethernet switch.

 

CONFIGURATION

In order to configure the firewall, you will need a configuration template (not included in this document, supplied as a separate file). Follow the instructions inside the configuration template in order to adjust it to the profile of your site and use the following configuration sequence:

–  Log in to the server or a computer that was connected to ASA box;

–  Open up the HyperTerminal program (Start à Programs à Accessories à Communications). Set up a new connection to COM1 port.

–  Clear any existing configuration from the firewall using the following set of commands:

Devicename> enable

Devicename# config terminal

Devicename(config)# clear configure all

Devicename(config)# write memory

–  While in configuration mode, copy-paste the configuration file that you prepared earlier.

–  Save the configuration of the firewall:

Devicename(config)# write memory

 

Having this done, your firewall is set up for operation. Verify if your internet are working.

 

 

To search Particular set of File Types in a large set of Folders or in a drive, Instead of Windows Search which take long time usually, You can Run a Command which gives you the Log File with the Details of the File name, Location, Drive, space consumed.

To Proceed to Search the files:

1. Open Command Prompt

2. Get to Root Directory (i.e The Drive name in which you want to search)

3. Run the Command “dir /b /n /s *.wma,*.mp3,*.mp4,*.avi,*.mpg,*.mov,*.jpg,*.bmp >C:\ drivespace.txt”

 

You can search any kind of file by editing the above command, I have shown the command to search the Media and Photo files.

The Part (>c:\drivespace.txt) : here you can mention the file name and the path to save the file after execution.