Windows XP From A to Z
http://www.kellys-korner-xp.com/xp_abc.htm
Memorise
Configure RPC Over Https on single Server
How to setup a wireless connection
In this tutorial we will show you how to connect to a wireless network using Windows Vista. As you will see by yourself this is a pretty simple procedure. You don’t have to be a computer genius to connect to a wireless network. All you have to do is follow these simple steps:
First, go to “Start Menu” -> “Control Panel” -> “Network and Internet”.
Now… go to “Network and Sharing Center” and select “Connect to a network”, like it is shown in the above screenshot.
Choose “Show All” and hit the refresh button. If you find active network connections, select the one you want, click on “Connect” and don’t forget to check the option that says “Start this connection automatically”. If you check this option, Windows Vista will connect automatically to the selected network every time you log in.
If no networks are found, you can manually enter all network settings. This is how you do it:
In the “Connect to a network” window, click on “Set up a connection or network”, like shown in the above screenshot. Select “Manually connect to a wireless network” and press the “Next” button.
First, enter the “Network name”. In some cases the network name is identical to the name of the router – for example, my router is a Linksys, so the name of the network is Linksys.
Choose the security type and the encryption you use on your network. Now type the security key and check the option “Start this connection automatically”.
Click the “Next” button, then click “Connect to…” and that should be all. You successfully configured a connection to a wireless network.
Transferring the FSMO Roles via Ntdsutil
To transfer the FSMO roles by using the Ntdsutil utility, follow these steps:
These steps works for transferring roles from Windows Server 2008 to Windows Server 2012.
- Log on to a Windows 2000 Server-based or Windows Server 2003-based member computer or domain controller that is located in the forest where FSMO roles are being transferred. We recommend that you log on to the domain controller that you are assigning FSMO roles to. The logged-on user should be a member of the Enterprise Administrators group to transfer Schema master or Domain naming master roles, or a member of the Domain Administrators group of the domain where the PDC emulator, RID master and the Infrastructure master roles are being transferred.
- Click Start, click Run, type ntdsutil in the Open box, and then click OK.
- Type roles, and then press ENTER.Note To see a list of available commands at any one of the prompts in the Ntdsutil utility, type ?, and then press ENTER.
- Type connections, and then press ENTER.
- Type connect to server servername, and then press ENTER, where servername is the name of the domain controller you want to assign the FSMO role to.
- At the server connections prompt, type q, and then press ENTER.
- Type transfer role, where role is the role that you want to transfer. For a list of roles that you can transfer, type ? at thefsmo maintenance prompt, and then press ENTER, or see the list of roles at the start of this article. For example, to transfer the RID master role, type transfer rid master. The one exception is for the PDC emulator role, whose syntax istransfer pdc, not transfer pdc emulator.
- At the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility.
Transferring the FSMO Roles via Ntdsutil
To transfer the FSMO roles from the Ntdsutil command:
Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.
-
On any domain controller, click Start, click Run, type Ntdsutil in the Open box, and then click OK.
-
Type roles, and then press ENTER.
Note: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER.
-
Type connections, and then press ENTER.
-
Type connect to server <servername>, where <servername> is the name of the server you want to use, and then press ENTER.
-
At the server connections: prompt, type q, and then press ENTER again.
-
Type transfer <role>. where <role> is the role you want to transfer.
For example, to transfer the RID Master role, you would type transfer rid master:
In short once you have connected to server you want to move and you are in fsmo maintenace prompt use the list below
Transfer domain naming master <br /><br />
or, I think for server 2012 you need to use
Transfer naming master <br /><br />Transfer infrastructure master <br /><br />
Transfer PDC <br /><br />
Transfer RID master <br /><br />
Transfer schema master
-
You will receive a warning window asking if you want to perform the transfer. Click on Yes.
-
After you transfer the roles, type q and press ENTER until you quit Ntdsutil.exe.
-
Restart the server and make sure you update your backup
Preparing your Active Directory for Exchange 2007
When implementing Microsoft Exchange Server 2003 in your Active Directory you had to perform an setup /ForestPrep and setup /DomainPrep. With Microsoft Exchange Server 2007 things get a little more complicating since you now have to perform four steps:
- setup /PrepareLegacyExchangePermissions
- setup /PrepareSchema
- setup /PrepareAD
- setup /PrepareDomain or setup /PrepareAllDomains
The last two steps bear a certain resemblance with the ForestPrep and DomainPrep command, where the first two are definitely new. Here’s what they do:
PrepareLegacyExchangePermissions
The setup /PrepareLegacyExchangePermissions command must be run if you have any servers running Microsoft Exchange Server 2003 or Microsoft Exchange 2000 Server and you must run it logged in as a member of the Enterprise Admins group.
Essentially, you must run the setup /PrepareLegacyExchangePermissions command so that the Exchange 2003 or Exchange 2000 Recipient Update Service functions correctly after you update the Active Directory schema for Exchange 2007, because of the new Exchange-Information property set. Here‘s a detailed description of the changes made by setup /PrepareLegacyExchangePermissions.
If you’re about to run the PrepareSchema step you might skip this step, because the setup /PrepareSchema command can do it for you. If you add a new domain to your forest and you want to install Exchange Server 2003 or Exchange 2000 Server in this domain, or if users in this domain will log on to mailboxes on Exchange Server 2003 or Exchange 2000 Server servers in other domains, you must run setup /PrepareLegacyExchangePermissions again after you run Exchange Server 2003 or Exchange 2000 Server DomainPrep.
PrepareSchema
The setup /PrepareSchema command performs the Schema Updates needed by Microsoft Exchange Server 2007. Here‘s a list of all the changes made by this command in a vanilla Active Directory schema. Of course you can extract more information from the ldf files that are used by the setup program. You must run at is a member of the Enterprise Admins and as a member of the Schema Admins group and you must run this command on a computer that is in the same domain and the same Active Directory site as the schema master.
PrepareAD
The setup /PrepareAD command configures global Exchange objects in Active Directory, creates the Exchange Universal Security Groups (Exchange Organization Administrators, Exchange Recipient Administrators, Exchange View-Only Administrators, Exchange Servers and Exchange2003Interop) in the root domain, and prepares the current domain.
You have to be a member of the Enterprise Admins group to successfully perform this command. If you have existing Exchange Server 2003 servers you also have to be a member of the Exchange Organization Administrators group.
If you haven’t performed the PrepareSchema step the PrepareAD command can make these changes. When your also performing the PrepareAD command with an account that is a member of the Schema Admins group is can perform the PrepareLegacyExchangePermissions command as well.
PrepareDomain
The setup /PrepareDomain, setup /PrepareDomain:Domainname and setup /PrepareAllDomains commands all prepare domains other than the domain where your Schema Master is located. The difference between the commands is the scope in which they operate. You have to be a member of the Enterprise Admins group or you must be a member of the Domain Admins group in any domain that you will prepare.
Conclusion
The system requirements for Microsoft Exchange Server 2007 prohibit you from performing an in-place upgrade of existing Exchange servers. There is also no direct upgrade path to it for servers running Microsoft Exchange Server 5.5 or Microsoft Windows Small Business Server 2000. Companies with Microsoft Exchange 2000 Server on Microsoft Windows 2000 Domain Controllers face an overcomplicated migration scenario.
There are four steps to prepare your Active Directory for Microsoft Exchange Server 2007. In a simple Active Directory configuration (where you only have one domain in one forest) you only have to perform the setup /PrepareAD command and perform it with an account that is member of the Enterprise Admins and the Schema Admins group. (assuming members of the Enterprise Admins group are also members of the Domain Admins group, which is default)
ARP cache in windows
To flush/Delete the ARP cache in windows Vista/XP/2003/2000 follow this procedure
Click on Start—>Run—> type the following command click ok
netsh interface ip delete arpcache
Dynamic ARP cache entries update persist for 2-20 minutes depending on the system.
Windows 2003 Server = 10 minutes
Windows 2000 professional/Server = 10 minutes
Windows XP = 2 minutes
Solaris = 5 minutes
Delete IP address using arp command
arp -d <ip address>
Example
arp -d 10.1.1.2
Display arp table
arp -a
Add static entry to ARP table
arp -s <ip address> <mac address>
Example
arp -s 157.55.85.212 00-aa-00-62-c6-09
Linux Network commands
My friend wanted to know how to change or convert DHCP network configuration to static configuration. After initial installation, he wanted to change network settings. Further, his system is w/o GUI system aka X Windows. Here is quick way to accomplish the same:
Your main network configuration file is /etc/network/interfaces
Desired new sample settings:
=> Host IP address 192.168.1.100
=> Netmask: 255.255.255.0
=> Network ID: 192.168.1.0
=> Broadcast IP: 192.168.1.255
=> Gateway/Router IP: 192.168.1.254
=> DNS Server: 192.168.1.254
Open network configuration file
$ sudo vi /etc/network/interfacesOR$ sudo nano /etc/network/interfaces
Find and remove dhcp entry:
iface eth0 inet dhcp
Append new network settings:
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
Save and close the file. Restart the network:
$ sudo /etc/init.d/networking restart
Task: Define new DNS servers
Open /etc/resolv.conf file
$ sudo vi /etc/resolv.conf
You need to remove old DNS server assigned by DHCP server:
search myisp.com
nameserver 192.168.1.254
nameserver 202.54.1.20
nameserver 202.54.1.30
Save and close the file.
Task: Test DNS server
$ host cyberciti.biz
Network command line cheat sheet
You can also use commands to change settings. Please note that these settings are temporary and not the permanent. Use above method to make network changes permanent or GUI tool as described below.
Task: Display network interface information
$ ifconfig
Task: Take down network interface eth0 / take a network interface down
$ sudo ifconfig eth0 downOR $ sudo ifdown eth0
Task: Bring a network interface eth0 up
$ sudo ifconfig eth0 upOR$ sudo ifup eth0
Task: Change IP address and netmask from command line
Activate network interface eth0 with a new IP (192.168.1.50) / netmask:
$ sudo ifconfig eth0 192.168.1.50 netmask 255.255.255.0 up
Task: Display the routing table
$ /sbin/route OR$ /sbin/route -n
Output:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localnet * 255.255.255.0 U 0 0 0 ra0 172.16.114.0 * 255.255.255.0 U 0 0 0 eth0 172.16.236.0 * 255.255.255.0 U 0 0 0 eth1 default 192.168.1.254 0.0.0.0 UG 0 0 0 ra0
Task: Add a new gateway
$ sudo route add default gw 172.16.236.0
Task: Display current active Internet connections (servers and established connection)
$ netstat -nat
Task: Display open ports
$ sudo netstat -tulpOR$ sudo netstat -tulpn
Task: Display network interfaces stats (RX/TX etc)
$ netstat -i
Task: Display output for active/established connections only
$ netstat -e
$ netstat -te
$ netstat -tue
Where,
- -t : TCP connections
- -u : UDP connections
- -e : Established
Task: Test network connectivity
Send ICMP ECHO_REQUEST to network hosts, routers, servers etc with ping command. This verifies connectivity exists between local host and remote network system:
$ ping router
$ ping 192.168.1.254
$ ping cyberciti.biz
See simple Linux system monitoring with ping command and scripts for more information.
Task: Use GUI (Graphical Configuration) network Tool
If you are new, use GUI configuration tool, type the following command at terminal:
$ network-admin &
Above command is Ubuntu’s GUI for configuring network connections tool.
Final tip – Learn how find out more information about commands
A man page is your best friend when you wanted to learn more about particular command or syntax. For example, read detailed information about ifconfig and netstat command:
$ man ifconfig
$ man netstat
Just get a short help with all command options by appending –help option to each command:
$ netstat --help
Find out what command is used for particular task by searching the short descriptions and manual page names for the keyword:
$ man -k 'delete directory'
$ apropos -s 1 remove
Display short descriptions of a command:
$ whatis rm
$ whatis netstat
Reset Administrator Password on iLO
http://blog.netnerds.net/2006/04/ribcl-reset-administrator-password-on-ilo/
RIBCL: Reset Administrator Password on iLO
Filed under: Quick Code, Security — Written by Chrissy on Wednesday, April 26th, 2006 @ 4:57 am
Last night I got locked out of my Compaq DL360’s iLO. I searched the web to find how to reset the Administrator password and read that, for the most part, I’d have to be at the console. Bah! My servers are in San Jose and I’m up here in San Francisco, I didn’t want to make a trip just to reset my passwords. I continued to look around the web for a solution and found that I could reset the Administrator password (or even add another user with admin privs) using Compaq’s Remote Insight Board Command Language. Apparently, if you are processing RIBCL commands through your given operating sytem so long as you have the rights to login to the server. I logged in as my Windows Domain Admin and performed the following steps (Linux users, you can download the RPM for HPONCFG):
1. I installed SNMP because it was a preprequesite for HP Insight Management Agents.
2. I dowloaded and installed the HP Insight Management Agents.
3. I then downloaded HP Lights-Out Online Configuration Utility.
4. I ran into NTVDM errors trying to run the file so I just used WinRAR to extract the contents into C:\hp\ilo. I also extracted the zip file contained within the initial archive.
5. I then downloaded the HP Lights-Out XML Scripting Sample for Windows (Linux users can download the files in tgz format here or here.) extracted it and found the file I was looking for —
Administrator_reset_pw.xml
<ribcl VERSION=”2.0″>
<login USER_LOGIN=”Administrator” PASSWORD=”boguspassword”>
<user_INFO MODE=”write”>
<mod_USER USER_LOGIN=”Administrator”>
<password value=”newpass”/>
</mod_USER>
</user_INFO>
</login>
</ribcl>
6. Using notepad, I opened up the sample file and modified it slightly. Initially, I just removed the LOGIN and ran the file but HPONCFG gave me a syntax error. I then added it back and gave the Administrator a bogus password. Apparently, the LOGIN line is required for syntax reasons but it is not actually processed.
7. Next, I opened a command line and changed directories to C:\hp\ilo and typed the following:
HPONCFG.exe /f Administrator_reset_pw.xml /l log.txt > output.txt
8. I opened up Firefox, navigated to my iLO machine and viola! I was able to login as Administrator.
If changing Administrator’s password seems too scary, you can also add another user with administrator privileges. You can then login as that user and change the Administrator password via the web console. Use the following code, suited to your liking:
add_user.xml
<ribcl version=”2.0″>
<login USER_LOGIN=”Administrator” PASSWORD=”boguspass”>
<user_INFO MODE=”write” >
<add_USER
USER_NAME=”Chrissy”
USER_LOGIN=”Chrissy”
PASSWORD=”mynewpass”>
<reset_SERVER_PRIV value = “Y” />
<admin_PRIV value = “Y” />
</add_USER>
</user_INFO>
</login>
</ribcl>
Here’s a zip of just hponcfg.exe, add_user.xml, and Administrator_reset_pwd.xml. Since it’s an exe with no apparent supporting files, y ou may be able to just use that.
I see quite a few people have hit this page..if you found it useful, please let me know! If not, drop me a note and I’ll see how I can help.
Build your Own NAS
Here’s my build your own NAS cookboook:
1) Get a Celeron 430 processor, around £50
2) Get a Gigbyte GA-945GCMX-S2 motherboard, around £55
3) Get 512MB of DDR2 memory, about £15
4) Get a 64MB or more USB memory stick. You might have these lying around, you can probably get one for a few bucks or free somewhere.
5) Get a case and power supply. I got a CoolerMaster Elite 330 for £40 and it has a lot of drive bays.
6) Get as many hard disks as you want.
7) Put the system together, hook up a CD-ROM drive (just borrow one).
8) Download and burn FreeNAS onto a CD
9) Boot the FreeNAS CD
10) Insert USB stick
11) Follow the FreeNAS menu to install the OS on the USB stick
12) Turn off the machine and remove the CD-ROM, put in
13) Plug in the network, turn on the machine, and use the menu to set the IP address
14) From another computer on the network, you can access the FreeNAS machine with your web browser, and you’re on your way.
Configure the WSUS Server
Configure the WSUS Server and Create Computer Groups for Computers
Next, you configure WSUS for synchronization and approving updates by using the Administrator Console interface and then modifying Group Policy settings in Active Directory.
Modify Synchronization Settings
In this section you synchronize your server with the Microsoft Windows Update servers.
Procedure UM.5: To configure the WSUS server
| 1. | Open up the Windows Server Update Services Deployment Guide downloaded in Install WSUS. | ||||||||||||||||||
| 2. | From the Table of Contents, navigate to Configure the WSUS Server to learn about the process of configuring WSUS. | ||||||||||||||||||
| 3. | Perform the following procedures:
|
Create a Group Policy for Update Management
This procedure allows you to use Group Policy to manage software updates.
First, add the WSUS Group Policy.
Procedure UM.6: To add the Windows Server Update Services Group Policy
| 1. | Log on to AD01 using an account that is a member of the Domain Administrators group. |
| 2. | Click Start, click Administrative Tools, and then click Group Policy Management. |
| 3. | Expand Domains, and then expand your domain (for example, fabrikam.com). |
| 4. | Expand Group Policy Objects. |
| 5. | Right-click Group Policy Objects, and then select New. |
| 6. | Type a name for the GPO (for example, Windows Server Update Services), and then click OK. |
Import the Security Template into the New GPO
You will need the WUAU.adm file that describes the new policy settings for the Automatic Updates client. WUAU.adm is automatically installed into the %windir%\inf folder when you install Automatic Updates.
Procedure UM.7: To import the security template into the new GPO
| 1. | Right-click the newly created Windows Server Update Services GPO, and then click Edit. | ||||||||
| 2. | From the Deploying Microsoft Windows Server Update Services document, perform the steps from the Update and Configure the Automatic Updates Client Compoment section to configure the following procedures:
|
||||||||
| 3. | Close the Group Policy Object Editor. |
Apply the GPO to an Active Directory OU
Finally, apply the Windows Server Update Services settings to all domain servers by linking the GPO to the Servers OU. Once all servers obtain the policy information from the domain controller, they will then check for and install updates from WSUS01 based on the configurations.
Procedure UM.8: To apply the GPO to the Servers OU
| 1. | Open the Group Policy Management Console. |
| 2. | Expand Domains, and then expand your domain (for example, fabrikam.com). |
| 3. | Expand Group Policy Objects. |
| 4. | Click the previously created Windows Server Update Services GPO, and then drag it onto the Servers OU, to which it should be linked. |
| 5. | In the Group Policy Management dialog box, click OK to confirm the creation of the GPO link. |
| 6. | Click the previously created Windows Server Update Services GPO and drag it onto the Domain Controllers OU, to which it should be linked. |
| 7. | In the Group Policy Management dialog box, click OK to confirm the creation of the GPO link. |