Experience on a weekend, make me not sleep in the beginning of 2010...
an IBM old machine.
Windows Server 2003 SP1 unable to boot due to ntoskrnl.exe not found.
1 of 3 SCSI internal disk on RAID5 failure/defunct, mark with amber/orange led.
Boot server using ServeRAID Support CD, found that disk0 (first disk) is defunct/failure.
Luckily the other 2 disks in good condition.
Rebuild the disk0 with right click on it and select Rebuild. Takes 2-3 hours.
Rebuild success (Thanks God...), but since disk0 save the table of content of RAID5, we have to chkdsk the partitions.
Boot using Windows Server OS installation CD (in my case RAID controller detected by Windows Installer CD - no need to remastering to add specific driver if in your case this is required, you can use nlite. RAID controller driver can be found at ServeRAID CD).
Select Repair will give you command prompt. On drive c, do "dir" but error with message "bla..bla...drive enumerated bla bla..."
Googling and fould the next step to repair.
ckhdsk /r to all of the partition. Takes 1-2 hours on every partition (base on your disk size).
fixboot
fixmbr
reboot
Horeeeee.... server back online. But i have to restore the Domain Controller and many files which possibility corrupt, GPO blank :(
Database & Application Server which installed on that server back online.
Recommended : move the database & application server to another machine, change from RAID5 to RAID1 with 1 hotspare and reinstall OS.
Friday, January 22, 2010
Create / delete Windows Domain Controller
Create
Start --> Run --> dcpromo
Delete (Demote)
Start --> Run --> dcpromo /u
Start --> Run --> dcpromo
Delete (Demote)
Start --> Run --> dcpromo /u
Change the static IP address of a domain controller Win2003Svr
From http://technet.microsoft.com/en-us/library/cc758579(WS.10).aspx
Updated: March 2, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
This procedure includes changing all appropriate TCP/IP values, including preferred and alternate Domain Name System (DNS) servers, as well as Windows Internet Name Service (WINS) servers (if appropriate). Obtain these values from the design team.
Note
If you change the static IP address of a domain controller, you must also change related TCP/IP settings accordingly. This includes changing the TCP/IP settings for all client computers that rely on the domain controller for related services, such as DNS services. If the affected client computers are configured with static IP addresses, the procedures for changing them should be covered in the operating system help. As an example, see Change TCP/IP settings (http://go.microsoft.com/fwlink/?LinkId=130602). If a Dynamic Host Configuration Protocol (DHCP) server is used to distribute DNS server IP addresses, you may have to modify DHCP server options. For a list of options, see DHCP Options Supported by Clients (http://go.microsoft.com/fwlink/?LinkId=130603). For specific instructions about changing DHCP options, see Modify an option (http://go.microsoft.com/fwlink/?LinkId=130604).
Administrative Credentials
To change the static IP address of a domain controller
Log on locally (also known as interactively) to the system console of the domain controller whose IP address you want to change. If you are not able to log on to the domain controller by using the domain, you may have to start the domain controller in Directory Services Restore Mode (DSRM). For more information, see Restart the domain controller in Directory Services Restore Mode locally (http://go.microsoft.com/fwlink/?LinkId=140599).
Change IP address, Subnet Mask, Default Gateway, DNS Server like you ussually do on common Windows OS.
If this domain controller uses WINS servers, click Advanced and then, in the Advanced TCP/IP Settings dialog box, click the WINS tab.
Click OK to close the Internet Protocol (TCP/IP) Properties dialog box.
After you change the IP address of a domain controller, you should run the ipconfig /registerdns command to register the host record and dcdiag /fix command to ensure that service records are appropriately registered with DNS. For more information, see Dcdiag Overview and subordinate topics for additional information about the Dcdiag tool (http://go.microsoft.com/fwlink/?LinkId=130605).
Changing the IP settings of a server does not affect the share resources or shared permissions on that server, if the name resolution structure DNS and WINS settings are correctly configured. However, if network drives or passive connections (connections that are made manually from a command prompt or run line) are mapped using the IP address, an update is required. For example, if a client computer has G: drive mapped using the following command net use g: \\192.168.0.199\data and the IP address of the server that hosts the Data shared folder is changed from 192.168.0.199 to 192.168.1.200, the new G: drive mapping command should be changed to net use g: \\192.168.1.200\data. A better solution would be to ensure that DNS name resolution is working properly and to use the server name, as opposed to the IP address, in the command. For example, if the server name is DC1, the command to map a G: drive to the Data share on the server is net use g: \\dc1\data. It changes only if the server name changes; it is not affected if the IP address of the server changes.
----------------------------------
Updated: March 2, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
This procedure includes changing all appropriate TCP/IP values, including preferred and alternate Domain Name System (DNS) servers, as well as Windows Internet Name Service (WINS) servers (if appropriate). Obtain these values from the design team.
Note
If you change the static IP address of a domain controller, you must also change related TCP/IP settings accordingly. This includes changing the TCP/IP settings for all client computers that rely on the domain controller for related services, such as DNS services. If the affected client computers are configured with static IP addresses, the procedures for changing them should be covered in the operating system help. As an example, see Change TCP/IP settings (http://go.microsoft.com/fwlink/?LinkId=130602). If a Dynamic Host Configuration Protocol (DHCP) server is used to distribute DNS server IP addresses, you may have to modify DHCP server options. For a list of options, see DHCP Options Supported by Clients (http://go.microsoft.com/fwlink/?LinkId=130603). For specific instructions about changing DHCP options, see Modify an option (http://go.microsoft.com/fwlink/?LinkId=130604).
Administrative Credentials
To change the static IP address of a domain controller
Log on locally (also known as interactively) to the system console of the domain controller whose IP address you want to change. If you are not able to log on to the domain controller by using the domain, you may have to start the domain controller in Directory Services Restore Mode (DSRM). For more information, see Restart the domain controller in Directory Services Restore Mode locally (http://go.microsoft.com/fwlink/?LinkId=140599).
Change IP address, Subnet Mask, Default Gateway, DNS Server like you ussually do on common Windows OS.
If this domain controller uses WINS servers, click Advanced and then, in the Advanced TCP/IP Settings dialog box, click the WINS tab.
Click OK to close the Internet Protocol (TCP/IP) Properties dialog box.
After you change the IP address of a domain controller, you should run the ipconfig /registerdns command to register the host record and dcdiag /fix command to ensure that service records are appropriately registered with DNS. For more information, see Dcdiag Overview and subordinate topics for additional information about the Dcdiag tool (http://go.microsoft.com/fwlink/?LinkId=130605).
Changing the IP settings of a server does not affect the share resources or shared permissions on that server, if the name resolution structure DNS and WINS settings are correctly configured. However, if network drives or passive connections (connections that are made manually from a command prompt or run line) are mapped using the IP address, an update is required. For example, if a client computer has G: drive mapped using the following command net use g: \\192.168.0.199\data and the IP address of the server that hosts the Data shared folder is changed from 192.168.0.199 to 192.168.1.200, the new G: drive mapping command should be changed to net use g: \\192.168.1.200\data. A better solution would be to ensure that DNS name resolution is working properly and to use the server name, as opposed to the IP address, in the command. For example, if the server name is DC1, the command to map a G: drive to the Data share on the server is net use g: \\dc1\data. It changes only if the server name changes; it is not affected if the IP address of the server changes.
----------------------------------
Monday, January 11, 2010
PXE Boot
http://linux-sxs.org/internet_serving/pxeboot.html
http://www.ultimatedeployment.org
Ultimate Deployment Appliance
Welcome to the Ultimate Deployment Appliance Homepage.
What is the Ultimate Deployment Appliance?
Unattended OS installations (Windows, Linux, ESX, Solaris) over the network set-up in minutes!
Publish your favorite recovery/system maintenance tools over the network!
PXE Booting, Remote Installation Services, Kickstart, Jumpstart, Autoyast in a box!
When would you use this?
When you are trying to install a system that doesn't have a CDROM drive, but does have a network card (these days ultra-thin laptops and such don't have an optical drive)
When you have to install an operating system on different pieces of hardware.
When you have to install systems and want things to go automated and reproducible.
When you go to your friends house to fix his/her computer you want to be prepared. Instead of removing all that unwanted stuff you might as well start fresh. Bring your own system (laptop?), hook it up to the messed up system with a cross-cable and start re-install the system from scratch fully unattended. Head for the fridge...
When you need to do maintenance on your system without the need to carry around a stack of live CD's.
When you want to do this without paying lots of money for commercial products.
How Does it work?
Unattended Install The appliance mounts an iso file with a distribution of you favorite operating system and imports the necessary (network) boot-files. It creates a default configuration file for your automated installation and starts hosting the operating system distribution files for network booting.
System Tool Publishing Live CD's and other tools are imported entirely to the Ultimate Deployment appliance and are published for booting over the network trough PXE.
http://www.ultimatedeployment.org
Ultimate Deployment Appliance
Welcome to the Ultimate Deployment Appliance Homepage.
What is the Ultimate Deployment Appliance?
Unattended OS installations (Windows, Linux, ESX, Solaris) over the network set-up in minutes!
Publish your favorite recovery/system maintenance tools over the network!
PXE Booting, Remote Installation Services, Kickstart, Jumpstart, Autoyast in a box!
When would you use this?
When you are trying to install a system that doesn't have a CDROM drive, but does have a network card (these days ultra-thin laptops and such don't have an optical drive)
When you have to install an operating system on different pieces of hardware.
When you have to install systems and want things to go automated and reproducible.
When you go to your friends house to fix his/her computer you want to be prepared. Instead of removing all that unwanted stuff you might as well start fresh. Bring your own system (laptop?), hook it up to the messed up system with a cross-cable and start re-install the system from scratch fully unattended. Head for the fridge...
When you need to do maintenance on your system without the need to carry around a stack of live CD's.
When you want to do this without paying lots of money for commercial products.
How Does it work?
Unattended Install The appliance mounts an iso file with a distribution of you favorite operating system and imports the necessary (network) boot-files. It creates a default configuration file for your automated installation and starts hosting the operating system distribution files for network booting.
System Tool Publishing Live CD's and other tools are imported entirely to the Ultimate Deployment appliance and are published for booting over the network trough PXE.
Monday, January 4, 2010
Windows 2003 Server Network Adapter Teaming (Redundance / failover)
To Enable 2 or more NIC in a Windows 2003 Server Box for Fail Over or Redundancy should use Network Adapter Teaming.
The driver came from the NIC manufacturer.
Max 8 NIC in a team
Different manufacturer NIC ? not sure it can use for one team.
The driver came from the NIC manufacturer.
Max 8 NIC in a team
Different manufacturer NIC ? not sure it can use for one team.
Subscribe to:
Posts (Atom)