winBoot/i

How easy is winBoot/i to install and configure?

winBoot/i installs on your Windows server, the system copy tool copies the local boot volume from a client to an iSCSI target. This entire process can be done in as little as 10-15 minutes. At next boot of the client it will boot directly from iSCSI storage.

There is no need to open the client machine unless you want to physically remove the hard drive. winBoot/i does not access the local hard drive, it can be left as is, formatted or removed for security reasons or recycling.

Top of page...

What is a shared boot volume?

A shared boot volume enables multiple winBoot/i clients to optionally boot from a single HD image residing on an iSCSI target. Shared boot volumes are read-only. Write requests are cached to RAM on the local winBoot/i client, and the cache is flushed on shutdown / reboot. This serves as a way to maintain a pristine configuration that can withstand user changes, downloads or viruses.

Top of page...

Can I PXE boot to an iSCSI target from within a virtual machine from VMware or Microsoft?

Yes, you can use winBoot/i to network boot VMware and Microsoft virtual machines from an iSCSI target. HBA-equipped systems hosting virtual machines generally do not allow sharing (or virtualization) of the HBA-capability within the vm environment. We recommend using our Managed Boot Agent on Disk (MBAoD) for VMs to PXE-enable the virtual NIC within the virtual machine.

Top of page...

Where do the OS and applications run in the winBoot/i client environment?

The operating system and all end user applications are run on the client machine providing a true "thick" client – without the requirement for a hard drive.

Top of page...

Do I need additional management software?

You can continue to use the system administration tools you are already using for backups, managing user accounts and other admin tasks.

Top of page...

Will winBoot/i work over a Wide Area Network (WAN)?

winBoot/i can be used in a WAN such that the iSCSI storage can be located over a WAN, but the server where winBoot/i is installed must be on your LAN. This is a limitation of the PXE specification which is used to network boot the OS. Keep in mind that performance over a WAN may not provide acceptable results.

Top of page...

Which iSCSI targets does winBoot/i support?

Click here for a list of iSCSI targets that have been verified with winBoot/i.

Top of page...

Can the Microsoft iSCSI Initiator be used with winBoot/i?

Yes, winBoot/i installs the Microsoft iSCSI Initiator SAN Boot Version.

Top of page...

How can I try winBoot/i?

Please click here to arrange an evaluation.

Top of page...

What are the requirements?

winBoot/i Service:

Windows Server 2000 / 2003, Windows 2000 Professional or Windows XP Professional (winBoot/i Server is 32-bit only)
DHCP Server (Microsoft’s recommended)
Capable of supporting DHCP option tags if using the emBoot PXE service on the same server as Microsoft DHCP)

Clients:

Microsoft iSCSI boot-capable software initiator
Client system capable of meeting minimum Microsoft requirements for Windows 2003 Server 32-bit / x64, Service Pack 1
PXE 2.x compliant network adapter

Top of page...

Is there a special discount for educational uses?

Yes. Please contact sales for educational pricing.

Send an email to sales@emboot.com or phone +1.905.629.0200

Top of page...

How much does winBoot/i cost?

Please contact sales for pricing.

Send an email to sales@emboot.com or phone +1.905.629.0200

Top of page...

How do I get additional support?

Send an email to support@emboot.com

Visit the Support Forum

Or phone +1.905.629.0200

Top of page...