Copying
the DNS database from one server to another is accomplished through a
process known as a zone transfer. Zone transfers are required for any
non-Active Directory-integrated zone that has more than one name server
responsible for the contents of that zone. The mechanism for zone
transfers varies, however, depending on the version of DNS. Zone
transfers are always pulled by the secondary servers from the primary
servers.
| ||||||||||||||||||||||||||||||||||||
1.
|
Launch Server Manager on the DNS server with the primary zone.
| |||||||||||||||||||||||||||||||||||
2.
|
Expand the Roles, DNS Server, DNS nodes, and then select the server name.
| |||||||||||||||||||||||||||||||||||
3.
|
Select the Forward Lookup Zones node.
| |||||||||||||||||||||||||||||||||||
4.
|
Right-click the name of the zone and choose Properties.
| |||||||||||||||||||||||||||||||||||
5.
|
Choose the Zone Transfers tab.
| |||||||||||||||||||||||||||||||||||
6.
|
Check Allow Zone Transfers and select Only to the Following Servers.
| |||||||||||||||||||||||||||||||||||
7.
|
Click
Edit, type in the IP address of the server that will receive the
update, and press Enter. The server will be validated, as shown in Figure 1.
Because the server is not yet an authoritative server for the zone, the
error message “The server with this IP address is not authoritative for
the required zone” appears. This will be done in the next section. The
error can be safely ignored. Click OK to save.
Figure 1. Setting up zone transfer servers. | |||||||||||||||||||||||||||||||||||
8.
| ||||||||||||||||||||||||||||||||||||
9.
|
Click OK to save the changes.
| |||||||||||||||||||||||||||||||||||
1.
|
Launch Server Manager.
| |||||||||||||||||||||||||||||||||||
2.
|
Expand the Roles, DNS Server, DNS nodes, and then select the server name.
| |||||||||||||||||||||||||||||||||||
3.
|
Select the Forward Lookup Zones node.
| |||||||||||||||||||||||||||||||||||
4.
|
Select Action, New Zone.
| |||||||||||||||||||||||||||||||||||
5.
|
Click Next on the Welcome page.
| |||||||||||||||||||||||||||||||||||
6.
|
Select
Secondary Zone from the list of zone types. Secondary zones cannot be
AD-integrated and the options will be grayed out. Click Next to
continue.
| |||||||||||||||||||||||||||||||||||
7.
|
Type in the name of the zone that will be created (this should match the primary zone name), and click Next to continue.
| |||||||||||||||||||||||||||||||||||
8.
|
Type
in the IP address of the server or servers from which the zone records
will be transferred. Press Enter for each server entered, and they will
be validated. Click Next to continue.
| |||||||||||||||||||||||||||||||||||
9.
|
16 Jan 2012
Windows Server 2008 : Domain Name System and IPv6 - Performing Zone Transfers
15 Jan 2012
How to install Vmware Vsphere Hypervisor (ESXi 4.1.0) onto a USB stick.
Want to have a portable ESXi on a stick? Here's how to do it.
Purpose
To demonstrate how to install Vmware Vsphere Hypervisor (ESXi 4.1.0) on a USB stick.
We'll be covering two different methods to accomplish the task.
- Install by writing the Vsphere Hypervisor (ESXi 4.1.0) image onto a USB Stick.
- Install by using the native installer.
Required
Method 1
1. The install ISO image from Vmware:2. A USB Stick with at least 900MB of space.
3. RMPrepUSB
An extremely handy tool that makes partitioning, installing grub4dos, and boot preparation simple.
4. Winrar:
Method 2
1. The install ISO from Vmware:2. A USB Stick with at least 900MB of space.
Installation
Method 1
The basic idea is to extract the ESXi image from the Vmware Vsphere Hypervisor (ESXi 4.1.0) install ISO and write it to the USB Stick using RMPrepUSB.Extract Image
Open the ISO image, VMware-VMvisor-Installer-4.1.0-260247.x86_64.iso with Winrarand find "imagedd.bz2" and open it up.
Once you've opened "imagedd.bz2" extract "imagedd" from it.
Write Image onto USB Stick
Plug in the USB Stick and then open RMPrepUSB.The only things we need to concern ourselves with are the white box at the top that lists all detected drives, and the blue button, File -> USB.
Make sure to select the correct drive from the white box.
Next, click on File -> USB button.
Select All Files from the drop-down and select "imagedd" and click Open
Several Prompts will appear, keep the defaults and click OK for each one.
This is your last chance to verify that you have selected the correct image/drive.
*Make sure you have the correct drive selected or you can potentially overwrite the wrong USB Stick/Hard drive*
When you've verified click OK.
Now we're done writing the image onto the USB Stick.
You now have a bootable USB Stick with Vmware Vsphere Hypervisor (ESXi 4.1.0) installed.
Method 2
The process is to select the USB Stick as the install device in the Vmware Vsphere Hypervisor (ESXi 4.1.0) installer.Begin Regular Install of ESXi
With the USB Stick plugged in, boot the server/virtual machine from the Vmware Vsphere Hypervisor (ESXi 4.1.0) install media.Select Proper Install drive
Proceed through the screens until you get to the Select a Disk screen.*Be absolutley certain that you select the proper device as to not overwrite the internal hard drive if you have one.*
Proceed through the installation.
Congratulations, you now have a bootable and portable Vmware Vsphere Hypervisor (ESXi 4.1.0) install on a USB Stick!
by Jose Rodriguez http://www.virtualgeekhub.net/content/how-install-vmware-vsphere-hypervisor-esxi-410-usb-stick
5 Jan 2012
Convert from thick-provisioned disk to thin and vice versa on ESXi 4.1
Thin to thick (easy :-): within the vSphre client open datastore browser and right click on vmdk file you want to convert to think and select Inflate.
Thick to thin (a little bit "pro")
- Connect to host via SSH and use the below syntax:
1. Shutdown the VM so that we can get exlusive access to the virtual disk.
2. Log into your ESX host using SSH and cd into the VM directory that contains your virtual disk.
3. Run vmkfstools –i srcDisk -d thin dstDisk
4. Edit the settings of VM and remove the existing drive srcDisk. Add a new hard drive and choose the existing drive option then browse to your new thin dstDisk
5. Boot the VM and enjoy.
Note: Dont forget to go back to ESXi host remove the old .vmdk and -flat.vmdk files once you are sure that your VM is operating normally off the thin disk.
Thick to thin (a little bit "pro")
- Connect to host via SSH and use the below syntax:
1. Shutdown the VM so that we can get exlusive access to the virtual disk.
2. Log into your ESX host using SSH and cd into the VM directory that contains your virtual disk.
3. Run vmkfstools –i srcDisk -d thin dstDisk
4. Edit the settings of VM and remove the existing drive srcDisk. Add a new hard drive and choose the existing drive option then browse to your new thin dstDisk
5. Boot the VM and enjoy.
Note: Dont forget to go back to ESXi host remove the old .vmdk and -flat.vmdk files once you are sure that your VM is operating normally off the thin disk.
Subscribe to:
Posts (Atom)