Once the Installation GUI comes up, I'm going to customize my installation. Desktops are nice to look at from time to time.

It's completely unneeded, but whatever. I want it.

So customize your installation and select "Server with GUI" else select "File and Print Server" for basic file share functionality in a CLI.

Select Done.

Select your partitioning, the basics are fine. Click into and then click done.

Lastly click "Begin Installation"

Set your Root password and follow the onscreen guides. Create additional users if you need them. (Which you should. No one should use the root account for everything)

@aaronstuder said in Building Out XenServer 6.5 with USB Boot and Software RAID 10:

Confirmed Working 😄

Awesome, thanks.

@DustinB3403 said:

OK Chris Up Vote this if it's right. 🙂

If the user of the Windows VM is at the hardware device that is running the VM. Generally a type 2 hypervisor, such as VirtualBox, a retail key is acceptable. but so is SA and VDA.

If the users are remotely accessing the VM, then SA or VDA are required. (one or the other)

There are *caveats to this statement. But generally correct.
*You can license Windows VDA for a device to run the VM locally, but only if that device has a Windows 7 Pro version or better. Otherwise, yes you can use a full retail license of Windows to run locally on the device OR Windows SA.

@scottalanmiller Seems like more has happened with Hyper-V in the last 12 months, than it ever has in development. I'll be excited to see what happens in the next few years, especially with RemoteFX and VDI (setting up some Raspberry Pi 2's from Amazon for $70, and Raspberry Thin PC download). Tried it out over this last spring in a VMware Horizon View environment, and all I can say is wow. That install has pretty much every remote protocol. You can harden the client by locking out the docks/settings/etc once you're all done setting it up. Not perfect, but nearly there.

What would be the point of content if no one can figure out how to read the site 😉

So many things use snapshots under the hood, space can grow and shrink pretty rapidly in confusing ways.

How did this go?

@Dashrender said:

Is linux better than it was, sure, is it as good for non techies as Windows, possible I suppose as I haven't installed Mint in ... ever.

I've tried testing this before and I've never seen any non-techie feel that Windows was better. Literally, never. I've only seen experienced Windows users that did not want to switch. Starting from scratch, Linux has always been found to be easier in the few "greenfield" tests that I've ever seen.

@JaredBusch said:

Great to see you got it working @shybrsky.
I did noticed the simple MS Paint screen capture and edit. I would recommend that you look into Greenshot for performing screen captures and simple editing. It works a treat and can even integrate to imgur for you.

noted bud..and thanks

How did this project go?

@dafyre said:

Best way I've heard it described is that when you enable Hyper-V on a Windows Server, your Windows Server Core (or GUI) becomes the Linux equivalent of Dom 0

And exactly like installing Xen onto Linux, Xen inserts itself as a "shim" under Linux and then reboots, booting into Xen instead of Linux. HyperV is identical, inserting itself as shim under Windows, rebooting and booting into HyperV instead of Windows.

HyperV is modeled identically after Xen.

@Dashrender said:

I've already told Scott I would love to see one of the first major projects on the new NTG lab be to setup a ZT network.

I like this idea. We could use the ZT Network for the NTG lab as a management network or something.

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

I can see doing RAID 6 if you can afford the performance penalty.

Which you would assume that you can if you can wait for a distant node to write as well.

By distant, you mean local, as in the same rack?

Yes, distant meaning outside of the chassis connected over a slow Ethernet link.

@scottalanmiller I think of Snapshots as a quick point-in-time view... if something breaks, I can restore that snapshot in mere seconds, and I'm good to go.

If I have to pull a full image from a backup, it could take minutes - hours to restore that backup...

I would recommend looking at StarWind SA for example.
That solution fits your requirements perfectly, it will also provide you with HA storage that will ensure the business continuity.
As for support, they offer a single point of contact no matter what issue you face, plus the system will be shipped to your site fully preconfigured and pretested.

@flomer said:

OK, I guess I could try and test it if I have the time soon 😉

Did you get a chance to test?

Apparently he is not the only one with confusion around this...

http://community.spiceworks.com/topic/1186383-unable-to-join-esxi-host-to-the-domain-no-suitable-fqdn

What perfect timing!

@scottalanmiller Yeah... I know..

It was just never bothered with. .. 😞

I'm making a snapshot right now using NAUBackup of my VM's before running the upgrades. As ya never know if something will get broken.

This is a maintenance release. The following items were fixed and/or added:

VMM: fixed an issue with Windows 10 guest kernel debugging over the network for Hyper-V paravirtualized VMs
VMM: fixed a bug which prevented reading the saved state of the 'PATM' unit from VirtualBox 4.3.x (bug #14512)
GUI: changed default OS type for Windows from Windows XP to Windows 7
GUI: added another pre-defined guest screen resolution (bug #14384)
GUI: fixed update check which was broken due to changing the location of the root certificates (bug #13096)
GUI: fixed issues with synchronization of Caps lock / Num lock / Scroll lock on Windows hosts (bug #14302)
GUI: don't crash during VM shutdown if 2D video acceleration and 3D support are enabled (Mac OS X hosts only)
GUI: several seamless fixes for certain X11 window managers, also when used in multi-screen setups
GUI: Log window size, position and cursor-position fixes
Audio: fixed playing leftover/deprecated audio samples
Audio: fixed playing audio after suspending the host (5.0 regression; Linux hosts using the ALSA backend)
Audio: fixed playing short audio samples which were chopped off formerly
Audio: fixed distortions on OS X when the sample rate of the guest stream and host device don't match
Storage: fixed raw disk access and flat VMDK image access which would be always opened readonly (5.0.2 regression; bugs #14425, #14461)
Storage: fixed initial encryption of VDI images after they were compacted (bug #14496)
VGA: fix for certain graphics modes (bug #14516)
NAT: don't freeze while the VM is paused if the network attachment mode is changed from/to NAT with activated port forwarding
OVF: fixed duplicate USB controller entries in exported OVA/OVF (bug #14462)
Shared Folders: fixed a path separator issue (bug #14434)
Drag and drop: fixed crashes on OS X hosts when doing host-to-guest transfers
VBoxManage: another attempt to not deny changing the network adapter type at VM runtime (5.0 regression; bug #14308)
VBoxManage: fixed broken guestcontrol <VM-Name> list command (5.0 regression)
VBoxManage: fixed broken Guest Control stdout/stderr output (5.0 regression)
Mac OS X hosts: fixed remaining problems with activated SMAP (Broadwell and later; bug #14412)
Mac OS X hosts: fixed broken 3D support (5.0.2 regression; bug #14476)
Linux hosts: Linux 4.2 fix
Linux hosts: don't crash on older Linux distributions if the DBus service isn't running (bug #14543)
Windows hosts: fixed the VERR_LDR_MISMATCH_NATIVE error message (bug #14420)
Windows hosts: fix for Windows 10 build 10525 and later (bug #14502)
Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437)
Windows hosts: prevent intermittent host network disconnects during VM start/shutdown with bridged networking (bug #14500)
Windows Additions: fixed the call to the memory allocation function (bug #14415)
Linux Additions: be more forgiving if the compilation of the vboxvideo module fails (bug #14547)
X11 Additions: fixed a number of small issues with dynamic resizing and full-screen and seamless modes.

Understanding the difference between a good risk decision, and getting lucky....

Youtube Video