This is an old revision of the document!
Table of Contents
Installing Windows from bootable USB Flash disk
Partition the USB Flash drive as needed
Use EaseUS partiotion manager: Free EaseUS Home Edition
In the command shell window, type diskpart and then press Enter.
- Type “list disk” and then press Enter. You should see an entry for each hard disk that is installed on the computer. You should also see an entry for the attached USB drive. Write down the disk number (for example, Disk 2) that represents the USB drive.
- Type “select disk <n>” (where <n> is the disk number you wrote down) and then press Enter.
- WARNING: Be sure you have identified the correct disk number of the USB drive. You are about to delete all files that are stored on the selected disk.
- Type “clean” and then press Enter.
- Type “create partition primary” and then press Enter.
- Type “select partition 1” and then press Enter.
- Type active and then press Enter.
- Do one of the following:
- Type “format fs=fat32 quick” and then press Enter.
- Type “format fs=ntfs quick” and then press Enter.
- Type “assign” and then press Enter.
- Type “exit” and then press Enter.
Installing Windows XP from USB FLASH drive
Note: The size of the FLASH disk must be ⇐4GB, it must be formatted with FAT16 for XP to install
- HP drive key boot utility, use it for formatting the USB FLASH drive, you can also make it bootable
- Use “nLite” to customize the XP installation, you can preconfigure pretty much anything
- Download the Windows Updates Downloader or WUD and download the SP and latest updates for XP, use the nLite to slipstream the updates and SPs into your installation
- Use PE to USB to transfer the iso image created by nLite to USB FLASH drive
- boot from USB FLASH drive and install windows XP.
- Win XP natively does not support SATA interface. There are two things that you can do:
- Some BIOSes support IDE emulation mode, install XP using this mode
- Add the appropriate driver into you windows installation using nLite
Installing Windows 7 from USB FLASH drive
The easiest and reliable tool to use is Windows 7 USB DVD download tool from Microsoft: Windows7-USB-DVD-tool.exe.
You can use USB FLASH drive > 4GB for installing Windows 7 using the Microsoft tool
Running Symantec SRD from USB
- Alternatively, use ZOTAC WinUSB Maker v1.1.exe from Majorgeeks
- this will also work for SanDisk Cruiser USB sticks that are recognized as fixed disk and not removable
How to change the Remote Desktop port in Windows XP
- RDP port default value is 3389
- Start Registry Editor.
- Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
- On the Edit menu, click Modify, and then click Decimal.
- Type the new port number, and then click OK.
- Quit Registry Editor.
- Open the newly assigned port in the Windows firewall for incoming traffic
Note When you try to connect to this computer by using the Remote Desktop connection, you must type the new port. 304304 (http://support.microsoft.com/kb/304304/ ) How to configure the Remote Desktop client to connect to a specific port when you use Windows XP
- To connect to port 3391 on a computer with IP address 10.10.10.1, type the following information: 10.10.10.1:3391
Howto enable ICMP ping response in Windows 7
To enable ICMP ping response in Windows 7 you need to add Windows Firewall rule:
- Control Panel –> System and security –> Windows Firewall –> Advanced settings –> Inbound rules –> New rule –> custom rule
- in Protocol and ports: Protocol: ICMPv4 on the same panel go to customize, choose “Specific ICMP types”, check the box “echo request”
- Using Windows Powershell
- Start → Search Windows Powershell, right click, run as Administrator
netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4 dir=in action=allow
Howto Export and import DHCP reservations from and to Windows DHCP server
Quickly Export and Import DHCP Reservations Windows 2008, Winows 2003 This simple process describes the how to migrate a DHCP reservation list without having to migrate the entire scope.
Export the DHCP reservations, from the Old server which is to be migrated using netsh:
netsh dhcp server [ip address] scope [scope address] dump>c:\temp\reservations.txt e.g. netsh dhcp server 172.20.2.33 scope 172.16.0.0 dump>c:\temp\reservations.txt
Edit the exported file in notepad 'reservations.txt' , Simply do a Find and Replace for the old DHCP server IP you ran the export on and change to the New DHCP server IP you are importing to and remove out everything else in the text file except for the reservations config section.
On the New DHCP server, make sure you create the new scope first, and ten just simply run the following command:
netsh exec C:\temp\reservations.txt
Setting up the NTP server on a domain controller
For USA use timservers from NTP pool project:
server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org server 2.north-america.pool.ntp.org server 3.north-america.pool.ntp.org
Configure External Time service on DC holding PDC emulator role Here we will have to make use of External Time Source ( Internet). To Accomplish this follow below steps.
- Open a Command Prompt.
- Type the following command to display the time difference between the local computer and a target computer, and then press ENTER:
w32tm /stripchart /computer: target /samples: n /dataonly
- target: Specifies the Domain Name System (DNS) name or IP address of the NTP server that you are comparing the local computer's time against, for example, time.windows.com.
- n: Specifies the number of time samples that will be returned from the target computer to test basic NTP communication.
- eg: w32tm /stripchart /computer:time.windows.com /samples:5 /dataonly
- Open User Datagram Protocol (UDP) port 123 for outgoing traffic if needed.
- Open UDP port 123 (or a different port that you have selected) for incoming NTP traffic.
- Type the following command to configure the PDC emulator, and then press ENTER:
w32tm /config /manualpeerlist: peers /syncfromflags:manual /reliable:yes /update
- where peers specifies the list of DNS names or IP addresses of the NTP time source that the PDC emulator synchronizes from. For example, you can specify time.windows.com. When specifying multiple peers, use a coma as the delimiter and enclose them in quotation marks.
- For example, to configure your PDC emulator to use the following list of time servers:
- 0.north-america.pool.ntp.org 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-america.pool.ntp.org
- Run the following command:
w32tm /config /manualpeerlist:"0.north-america.pool.ntp.org,1.north-america.pool.ntp.org,2.north-america.pool.ntp.org,3.north-america.pool.ntp.org" /reliable:yes /update
Verify the settings in the Windows registry:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type should be NTP
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags should be 5
- Note: If an authoritative time server that is configured to use an AnnounceFlag value of 0x5 does not synchronize with an upstream time server, a client server may not correctly synchronize with the authoritative time server when the time synchronization between the authoritative time server and the upstream time server resumes. Therefore, if you have a poor network connection or other concerns that may cause time synchronization failure of the authoritative server to an upstream server, set the AnnounceFlag value to 0xA instead of to 0x5.
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer Enabled = 1
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters NtpServer = 0.north-america.pool.ntp.org 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-america.pool.ntp.org
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval SpecialPollInterval = 900
- restart service:
- net stop w32time && net start w32time
- Verify that UDP Port 123 is open
- Some settings were not saved from the command line
- The priod was not saved correctly, even if the refistry, the resulting value was 512s.