 All right. So we're going to get started with XCP NG server. Now, this is a version of Zen server and just for a little quick clarification. So Zen server is the open source project with the Zen hypervisor. XCP NG is a distribution of that run by the XCP NG team versus Citrix, which I've talked about before on this channel, is the other version of Zen. Now, good news is they're completely compatible. And for the most part, even all the commands are all the same. So if you're ever searching, you can also add the word Citrix Zen server. And as a version 7.4, because they're so similar, most all the commands are interchangeable. Actually, I'm not even sure which exceptions I could make it all of which ones aren't interchangeable. The one thing that's not interchangeable is with XCP NG, it's all open source versus to get some of these high end features like the Zen motion and other high end feature Citrix licenses, all of that. Even though it's something that's part of the open source project, when you get six searches version of it, its license versus XCP NG, it's full featured. So we're going to start with that one. And in case you're someone who followed my channel before and loaded Citrix Zen server, don't worry, you can just load XCP NG over the top of it. And it will bring in all the same files because the structure is the same. They have an upgrade path. And yes, I did call it an upgrade, even though you can go from same version to same version and eliminate all the Citrix side of it. Now the XCP NG center that we're going to talk about later, that is only compatible with XCP NG. And it does pull from the Citrix. The Citrix one will not work with XCP NG. So you're going to have to get a new Zen server, Zen center link for download. Now, as far as I know, it will work backwards with the Citrix one, but you can't use the Citrix one with this, but we'll cover that later. It's pretty straightforward. The good news is, if you have Zen Orchestra, if you're used to using that, we're going to talk about that a little bit. Zen Orchestra is also compatible with both. And you can actually have a mix of servers. You can have some Citrix and you can have those and they will work fine with Zen Orchestra. I do recommend though going all the way to XCP NG. Now I started with a really basic motherboard here. I had a pole. This is actually an old i7-870 16 gigs of RAM and a basic graphics card because it doesn't have onboard. I wanted to start with something really basic that you might have laying around older motherboard that will work with this important requirement though is that you have a processor, whether it's AMD or Intel, that supports virtualization. So you have to have the virtualization extensions in the processor, which a lot of modern processors, even this older one here, do have. It's been around for quite a while. Now, would I recommend this for a setup? No, but if you're building a home lab, this will get you started and you can start playing with it. Anything you produce here, the systems, the virtual machines that you create, you can easily transfer them over to a higher end machine. So it's kind of the fun thing if you get started here, but buy another server later. When you buy the other server, you can use the Zen motion just to pass them over. Now, I've done a video just on Zen motion to show how easy it is. And once again, I'll remind you, if you start out with an AMD machine and you move to an Intel machine, you won't be able to pass those VMs over live, but you can still pass them over in a shutdown state. So any of the learning you do on something basic where you get started will still apply to moving it or your knowledge base of getting it set up on another machine. Now, the other machine as well, if you do something like an R710, you're going to have a RAID array on that maybe, that's perfectly fine to use. This is not like FreeNAS where it has built-in RAID systems. You have to configure, if you wanted to have multiple hard drives on this, you would have to configure the RAID array in Linux. It's based on CentOS, both the Citrix and XCPNG versions. And you could use the commands to build your own RAID and storage arrays and manually do that. It's not something native to the system. But a lot of things, everything else besides that is the same as on this board is going to be on like a Dell R710 or any other commercial enterprise system that you may want, you know, HP ProLiant servers, Lenovo servers, whichever server you want to load it on. For compatibility, they are not going to specifically list every random motherboard. They just don't have the time for compatibility testing. But if you do look up compatibility, they do have certified Zen servers that you can Google. And those are ones that are like known and tested. We've actually tried Zen server on a variety of systems and I haven't found really anything it doesn't work with, as long as it's supported in CentOS. So let's go ahead and get started. Have my USB with XCPNG on there. Have a motherboard set to boot from USB. Single hard drive happened to have a old 300 gig Raptor drive laying around. We've got 16 gigs of RAM for this. Like I said, a video card. I got my pocket knife because I don't have a power button. So this is my pocket knife power button. Now the coffee's optional, but it's early in the morning. So I'm going to have coffee while we're doing this. So go ahead and stab it. Oh, I should probably have turned the power splanner. All right, now you stab the power button. And we get to watch it come to life right here. The installer is really straightforward. So the first screen says to install or upgrade press center key. If it finds a previous version of Citrix Zen server or even XCPNG, it will upgrade over the top of it. Let's go ahead and press center and start going on it. Select your keyboard layout. It does allow some options for special storage classes or advanced drivers set up. We're just going to hit okay. We don't have any of that. Accept the end user license agreement. It's going to find all the hard drives. Now what it will do is span hard drives. It uses LVM. And if you had multiple hard drives, you can span them. That's not the same as rating just so you know. It just will share the storage pool across all the hard drives you have plugged in. So if you're using a system that already has a predefined rate array, it will select that and that will take care of your rate. If not, as I talked, there's other ways you can do this by setting up the rate in Linux and then adding the storage pool. That's going to go outside the scope of this talk. Now I'm going to tab over here. Enable thin provisioning optimized for desktop virtualization. On LVM arrays, you can do thin provisioning and you can go ahead and Google real quick what that's about. But in short, you can say I have a 100 gig drive. It will allow me to allocate 100 gigs to it. But if it's only using 25 gigs, it only uses 25 gigs on the drive allowing me to allocate more to there. Hence, thin provisioning. You also notice that the SDB is the other device in here. That's what we're installing it from. And we don't want to install this on a thumb drive. You can. I believe it is possible. But if you set this up on a partition, it's only going to use a small piece for what they are referred to as DOM zero for the 300 gig drive. So a small portion will be dedicated to the operating system. The rest will be allocated towards send server storage. We'll live dangerously and skip verification of the media. We get to set our password here. We're going to go ahead and go with automatic via DHCP. But this is where you can set a static IP. Obviously, I highly recommend a static IP depending on your network environment or making sure you know what the assignments are for it. It also supports if you wanted to tie it to a VLAN that is supported in here. Now, please know there's only one network interface on this. And that's an important aspect of this, that there's only one network, because we're going to cover how the networking works with only one network card. So I'm assuming this is a getting started video, and you only have certain limitations. If you buy some commercial enterprise boxes, you'll find they have a whole array of network. We'll go ahead and call this. We'll rename it XCPNG YouTube. And I'm just tabbing through these. It also you can put D and we'll choose Detroit. Yes, just use normal MP. And then finally the install. The install goes relatively fast. All right, unless you have any supplemental packs, then just say no. Completing installation. And now it's complete. Hit OK. Now we have the boot screen. I still have a little bit of coffee left. Didn't take too long to solve. I fast forwarded parts of that because well, no one really wants to watch the bar go across. Now I will comment the error you see right here unable to init device MC log. I've seen that on a few of the systems we've tested it with. It doesn't seem to have any problems when I see that. It just does that. I like I said, I have not really dug into it, but it hasn't caused me any issues. And I've seen it even on some of the enterprise machines, but it's not absolutely consistent. That or it just passes by so fast. I don't always notice it. Right. So now we're at the management council. And you can look in to see what IP address it had. The networking settings, authentication, virtual machines that are running is pretty basic. And this allows you to log in. And we're going to log in from here. Because I mean, you can manage this from the command line, just so you know, if this is what you wanted to do and do everything command line driven and type in UUIDs and everything else, that is completely possible. It's complicated. It's goes wibbly on the scope of getting started. It's way easier to use either that orchestra or the XCPNG center. We're going to start with the XCPNG center because it's, you know, pretty easy to get going and set up. So we see the IP address is 192.1683.77. So we're going to go in my office and jump on it from there and show you how to get moving. Now I'll leave a link where you can get this, but this is the download for the XCPNG center 742.9 binary release. All you have to do is extract it and run it. It doesn't currently have an installer or at least the version I downloaded right now. They're working on it, but you just install it and then run the create a shortcut, which I'll just show you real quick on the desktop here to the XCPNG center. When you open it up, you're presented with this. Now I have my two other servers disconnected. You can have multiple servers. This is what allows things like send motion to be able to pass a machine between the different servers by connecting them all together. So we'll go ahead and type in an IP address 3.77, type in our password, and now it's connected. Now, if I were to connect the other ones, it would pull together all the storage and everything else to allow you to pass between there. That's why we're leaving these ones disconnected. Go ahead and make it full screen and move myself out of the way here. So from here, we can see that XCPNG, here's the, what they refer to as DOM zero using a certain amount of memory, the control domain, the rest is all free of our 16 gigs, which there's no virtual machines on there. Here's our storage, which we have the removable storage, which is for plugging in USB drives and doing backups. Here's the local storage. Now this is something about the way the local storage works. So we're going to go ahead and look at that 234 gigs total. So it's a 300 gig drive. And that's because part of it was used for the OS and saw the rest was sliced up for storage. So as you can see, it doesn't take much. I believe that's roughly 50 or 60 gigs is going to be allocated towards the server itself. So you can run it. It does do the partitioning, you know, a handy thing to load this is either a fast drive or an SSD, and then you can add other drives as your storage pools. So here's all the discs that are in here, which are none. These are all the virtual discs that are available. And I'll just connect this one real quick to show you when you look at the same thing on their storage, you can see the different virtual discs on there. Go ahead and disconnect this one again. So in order to get started with loading VMs, we're going to have to add some ISOs to this that we can boot off of. So we're going to go ahead and go to new storage because we start right with new VM. I'll just show you real quick. You can choose all these, but if we don't have an ISO to load it, well, that's going to be difficult then. So we're going to start with a start with new storage. We're going to start with you can do NFS ISO or Windows file sharing. So you could share the ISOs from your Windows computer. We'll just call this, you know, ISO library. Next, where does it go? You can do username and password here. I actually have an ISO library on FreeNAS, but like I said, this could be a Windows share as well. So it's slash slash 192.1683.4 slash ISO. I'm just copy and paste it here. You can see it working in Windows, creating storage repository. And here are all those ISOs I have in here. I have a PF Sense. I have Debian. I have an old version of Debian here. It really doesn't matter, whichever one you want to load. Here's a clone Zill is in here. Lots of other different things I've been playing with. CentOS, even FreeNAS, even though it's a 11.4 ISO. All you have to do is drop anything in the shared ISO library, and then you can build a virtual machine with it. So let's go ahead and create a new VM. So there's a wide variety of templates. These kind of get you a base for it. You can just say other miscellaneous. If you didn't want to choose any of the templates, we're going to go ahead and choose the Debian one here, but we do have lots of Windows, Windows servers, and no worries if you have something newer than what's even listed in here, even legacy stuff. You can customize the settings. These are just general templates. So we'll go ahead and choose Debian 9. Install from ISO. Now this is where you can just choose the list of ISOs that are in here. So we'll go ahead and choose this Debian 9 one. I know it's older, but I don't feel like stopping to go download a new version. Another option is though, without if you didn't use an ISO library, but you do have boot from network setup, that is completely possible to do that. Next, place it on this VM server. Now if I had these other ones attached, the list would come up for all the different servers that we had. CPU and memory. Now this is interesting because I know there's not that many virtual CPUs available in this system. It will let you over allocate. Don't do that because you'll have lots of problems. So we're just going to go ahead and give it two cores. Now you can choose if it's two sockets, one core or one socket with two cores. That's a personal preference. And there may be reasons going beyond the scope of this. You want to set up a very specific way, but it does give you the option that you want. One physical CPU is how it's presented to the underlying OS, or do you want two physical CPUs or multiple going there? For example, if we said we have a 16, do you want 16 sockets, eight sockets, or two sockets with eight cores? So just a couple of different options in there. And it does give you a warning when you want to see how many virtual versus physical. So I've gone over the number of cores and says it only has eight physical CPUs or eight cores in the terms of what we use. So you don't want to over allocate. You will get a warning. So we're going to go back to our original idea of two and one socket with two cores per socket. Memory. Let's give it a little more RAM than this. And these can be adjusted later. Let's give it a gig of RAM. Next, there's no GPUs in this. This does have certain GPUs. Go ahead and look up the compatibility us are supported and can be used in there. Storage. Let's edit this by default that wants to use local storage. Now, if we had multiple storage is attached, you could choose that. For example, I have iSCSI set up on my other ones, and it will choose the combination of storage. If you have multiple hard drives, you can choose all the different hard drives or different storage locations you have set up for this. We're going to have to edit this because 10 gigs is not enough. And we'll go ahead and make it 100 gigs. Then we'll go next. Networking. Now, we didn't do anything to the networking. There's only one networks. It's going to auto generate attached to network zero. And I'm actually going to show you how we can play around with that. Start VM automatically create now. And now it's created. There it is. They show up in the list here. We go over here to the council and it's on the graphical install. So we'll go ahead and run through the install. And you can see it's pretty straightforward. So while it's doing this and it's going to pull networking information, I'm going to show you how the networking works in here. So we're going to go here and we're going to look at the network. So it only has one network card. So this becomes very, very simple to do here at the bottom and we're going to go to configure. This is the management interface and it's attached to, well, the only network available on there. But if you had multiple network cards, this is where you could do things like attach a management interface there. And this is the interface that we connected to 192.163.77. This is also where I can statically assign and push the settings back over to our server. And if we had more network interfaces, we could add more IP addresses and tie more things to this. You can't mess with the management one while it's in use. If you want to use other things like an ice cozy network and things like that, you're going to need a different network card because it dedicates that one towards storage. Now, the ones dedicated to our storage means they can't have management on it and storage at the same time, but it does allow those storage networks to be attached to the VMs. So the bottom side of this essentially is your management interface network for the system. These are networks available at the top here that are for the VMs themselves. Let's go take a look at where this is at. Say, yes, and the VM is just loading right away back over here to the system to the networking. Now, this is where the networking works as well for extended network, bonded network, single server private network and external network. Single server private will do first, LAN of Zen server. And what I did here, as you may notice, please note the link status of none active and the NIC it's tied to. There is no NIC just like this one. They're actually the same type of network. What these do is these create networks that are not tied to anything. So we're going to have properties. They only exist on this server. So if I connect two machines and they both connect to this network, they can talk to each other, but they don't go outside the system. So picture an interface that is so to speak internally facing into the system, but has no options outside there. It can't escape. This is great for specialized network testing, maybe even some pen testing or virus testing. You can assign this. I use this for PF sense testing. An example would be I have the LAN side of PF sense facing this internally created NIC. Then I put all the other virtual machines on that same NIC. And then they all can talk to each other and are behind there without any public interfaces that can leave the machine and you can create your virtualized network. So PF sense can act as a virtualized firewall. And I've done this for a lot of testing automatically add this network to new virtual machines. That's the box that you see right here, the auto. And what that means is every time you add a virtual machine, it just defaults to adding it. And you can add a list of network adapters. This helps when you're trying to add a lot of virtual machines. Now other networks we can add are like the external network. We'll call it VLAN. And if you have a network that is VLAN aware and have proper smart switches configured, you can choose the VLAN ID and I'll attach it to this NIC. So NIC zero would be a trunk port with all the VLANs pushed to it. And then you can say this specifically this network interface only pulls VLAN 50 off of that trunk port. And that is actually how our system is set up and VLAN 50 is valid. So now any virtual machines attached to this become trunked to this one here. Now, like I said, I've had a few people tell me they don't support VLANs. It absolutely is supported. And then you can go back into Actually, we'll go ahead and continue. We'll let this go and go into your networking, add interface. And here's those interfaces, LAN of Zen, network zero or VLAN. And we can add a multiple interfaces. Or you can do properties on the existing one. I can't do it while the machine's running, unless it has a Zen server tools loaded and switch them. One of the servers running and it has Zen server tools, this actually allows you to go ahead and change out the network interface while the machine is live. And it works the same as unplugging unplugging a network cable. The machine doesn't lose the adapter. It just swaps out the status of where it's connected to when you swap it out, which is really handy. So this is going through and loading. Now a couple of things you can do right here is we can set this to scale. So it will scale with the size of the window. You can undock it. So it becomes its own window. We're going to go ahead and redock it. I can do full screen if I wanted. I can send the all control delay to this council here. Now, once it's got the Zen server tools loaded, this becomes not grayed out where it says open SSH council. That's where you can go in and SSH and or if it's a windows machine, it will open an RDP council there. So that's another option. So say no to this. Now up here is the we don't want the desktop environment. Load an SSH server and you can see this is going for being an older i7. This is installing quite fast and it's pulling the ISO from across the network. So it doesn't really affect performance that much. Booting isos across the network on there and having a network share with all your isos just becomes really convenient, especially if you're sharing it from a windows machine, your home machine, because you're getting started with this. And then all the isos automatically just show up here in this pulldown. So I can actually pull out the disk, which is a bad idea while it's installing, but that's where you can just hit eject and control that. Now here's where we can edit the memory. Here's where you see the storage for the virtual machine. Here's where you get all your performance statistics of what the virtual machine is doing. And this can all be customized. You can hit new graph, choose, you know, vCPU concurrency network receive. If you have multiple disks, it allows you to see all the multiple disks in here and get down to the detail. There's only a couple CPUs or you can edit existing ones. So edit graph and we'll put average CPU on here. You can also do things like tie together the network speeds at the same time into one graph. So you can consolidate these if you want, but by default it creates these couple of them here and they're separated. Now memory data, it has no memory data on the virtual machine until you load the Zen server tools and we'll cover real quick how to load them. Continue, choose the drive to load Grubon, installation complete, finishing installation and rebooting. And we're at the command line. Now this is fully working and ready to go. It's got there. Let's see if we can ping something. Yep, we've got network access. So now we have a fully running VM of Debian on here. Now let's talk about loading the tools down here at the bottom XCP NG tools. So it says guest tools.iso. We're going to go ahead and insert that. You can change DVDs while the system's running. You don't have to reboot it for that. And it's just like popping a CD-ROM in. Now this is going to vary by different Linux distributions, but we're going to go ahead and mount dev CD-ROM to media CD-ROM. Mounted read only media CD-ROM. Now obviously if this is Windows, this is easy. There's a setup.exe file that you can run, but we're going to go into the Linux directory and there is an install.sh. So we're going to head and run this installer. It figures out which one with things I need. We're going to say yes. And now we should reboot this virtual machine to have the utilities running. Now I just showed there was no, as soon as you start to utilities, it immediately will start showing the memory usage. But we're going to go ahead and like it says reboot. So it has all the utilities loaded and the service is loaded. Now it's not absolutely imperative you load the utilities, but they do help a lot. They help with the when you're doing snapshots of the virtual machines or any of the tuning, like the memory. Right here's the memory usage. And let's go over here now. It actually allows us things like changing the memory on the fly automatically allocate memory within this range. And you can set a range of memory. So you can dynamically allocate it and free up memory for other services. Obviously over allocation of memory is a problem. But if you have machines that you know will dynamically expand the contract, this is an option and it allows the system to do this because of the Zen server tools being loaded. This also helps with things like snapshots. So if we take a snapshot here, and we now have a snapshot of this virtual machine, here's where it is, here's where it is now. That helps with this because now it actually took kind of like the open file problem you have if you want to back up a machine. It gets behind the scenes when it has a Zen server tools and allows that type of snapshot to be created. Now from here, so let's go ahead and show the system. We rebooted it. So we took the snapshot before I created this file test. Let's show you how you can revert a snapshot. So here's where it's at. Here's where the system is now. Here's where it was. Now if you don't like this view, you can simply go to a list view. And we're going to go ahead and take another snapshot, the test file, take snapshot. So now we can view it this way or we can go back to the tree view and see the different places that the system is. So now we can go ahead and revert to this one just to show you how this works. Do we want to take a snapshot of before? When you're doing a lot of testing, this is really handy. We're not going to bother doing it, but now we're going to revert the VM which is going to force it to reboot. So back here look at our snapshots and now we have forked it and now we can continue on. So once it boots here we'll go look and we'll see that that file I created test is not there. No test file. But what if we wanted that one back? Well this one right here is after test. So now we can actually say we can even export this as an entire VM. We can also say new VM from Snapshot. Next, next. You can literally just say next and yes you're all this is going to default to everything else. Now this is important here. If it's going on the same storage pool, use storage level fast as clone. The reason that's important what it's going to do is create a VM based on that snapshot but it's going to have a base of the other VM. If you ever move this in our machine it automatically takes care of the separation. But what this is allowing us to do, and there's our other one here, it created it that fast on this old i7 machine. When we look at the storage available on here, local storage, we're not using all of the storage. So here's those snapshots and so far we're only using 3.8 gig of 234 right here. Now this is what's interesting about the thin provisioning. The 3.8 gigs is because each one of these machines even though I gave them larger hard drives are thin provisioned on this particular machine right here. And this one is a fork so to speak based on the other one. So you can see when we go back here after the test file it gives it the name. So now this one has there. There's no snapshots on this file. Here's the council for this because it's a clone. And there's that test file I created. So we forked it and moved it over. But what if you know because this is based off the other one what happens if I move it to another machine? No problem. We'll go ahead and connect to another machine real quick. If we wanted to move it we can just say migrate and it would migrate over. Because these are machines are not the same this is running different platform than this one. I can't do the forced live migration. I would have to do a shutdown migration. But at that point it would allow me to separate and move them to another machine. Go ahead and disconnect this one again. So now you've seen how to create the snapshots, move the snapshots, fork them and start another virtual machine. This allows you to do a lot of fun playing with the machines because then you can keep reverting them back as many times as you want. And especially when you're learning this is hugely important. So she want to back things up or move them around. Speaking of backing up, let's talk about how that works real quick. So if you wanted to back up one of these virtual machines. Revert to snapshot export to file. You can literally click on this and export an xva file. Save it to the desktop and it exports xva. So we're going to hit save. Okay, I do not have enough storage there. So I have to save it somewhere else. Let me go ahead and hit export to file. I believe I have a map network drive. I do. There we go. And we're going to go down here to notifications, events and you'll see it exporting. This keeps track of all the events and things that are happening in system. It's going to create this xva file. Now once you have an xva file, that is very easy. And I have a few videos that cover this. You can even do these from the command line. You can just type, you know, xv import and pull in an xva file, export xva file. Those are a complete copy of your virtual machine. There are tools you can use like xcp and g the to do this, or you can use Zen Orchestra to import and export entire xva files. That is the standard format by which this works for entire virtual machine. So if you want to just back up your virtual machine, this is easy way to do it. And there's import as well. So if you go to import, it supports xva and your standard OVA OVF file. So your open virtualization format. Oddly, it does not export to standard virtualization format, but it does import from them. So if you're using virtual box before switching to xcp and g, you can import those. Also, a lot of places provide virtual machines ready to go. I've had no problem importing these using the xcp Zen Center directly in it will take and ask a few questions that may not have exactly the same format that was used to create the OVF files. But if they were exported from virtual box, it imports them perfectly fine. Please note, sometimes you do have to change network settings on there. But there are always little tricks to doing that, because if the same network adapter isn't emulated, you may have to make some adjustments accordingly. Now once you're at this top level right here, now that we have a few things running, we're looking at this server, you can see here is each of the machines that are virtual machines running, how the memory is allocated. We can look at the storage status, the networking status, the actual NICS. Now, this is an important thing. This is networking as of how you're configuring the networks. This is where the NICS are. So this is the part where we can go ahead and there's not much really here, because there's no bonds or anything else. This is where you can create a bonded network, which is tying a few of them together for more speed. That includes 10 gigabits. So if you have some 10 gigabit cards in here, you can actually tie a few of them together to get 20 gigabits or however many you have in there. If there was any GPUs, and like I said, you can look up the compatibility, this is where you would get to that. This is the same console that you see on the system. So it actually gives us shell access right here, and we can type access console. And it's the same console we've seen running before, where it's just got the status and everything else. You can easily get to this local command shell reboot shutdown, show running VMs, show the disk storage repository. Here's a virtual machine, VMs running on this host. Escape escape, we'll get back out of this. Now SSH is enabled, so you can SSH into this machine as well. Back to our performance graph. Users. Now I have not done this and maybe one day I'll do a video on it. This actually has the ability to set up XTPNG with domain authentication, not something I've used Citrix charges extra for that as a license. But it's built in here. And like I said, right here's the general settings so you can see all the version details, which license you're on, and processors in there. And like I said, this is the core i7 at model 870 at 2.93 gigahertz. So it kind of gives you an idea how to get started with Zen server, how to get playing with it. It's not too difficult of a system to use and it's really slick, especially once you start having a lot of virtual machines or several servers connected and you want to orchestrate everything around. It's pretty fun to play with and once you have them all connected you can use this and we're going to go here to the top level now and you can see things across all the virtual machines. You can create searches, VM snapshots, VMs by network. This helps you manage things at scale. So one of my friends had used this for a hosting company where they think they had a few thousand servers and this allows you to quickly allocate and move those around. And you can also look for different so we're on infrastructure, we can look at objects. And what this is doing is pooling everything together because we're all joined, I can see all the different storages. I can see all the different templates that are in your custom templates. If you had some custom setups you can do this helps for quick deployment. You can create a series of templates to help you deploy something. So once you have something set up, if you're doing an orchestration of scale, you can go through and create a template that automatically has everything how you want it done. And an example that's going to be when you're over here and we'll go back to infrastructure, we'll go to this one here as a snapshot, save as a template. You can create that template so you have it pre-configured and you know every virtual machine you want deployed like that. You can build it as a template so you can quickly deploy it. Now the last thing I said I'd cover is how to load Zen Orchestra on here and there's two ways to do that. So Zen Orchestra does ask for your email address. If you are uncomfortable with that, feel free to use one of the many free email services and let them go there. They do ask that you register. So you can download it free here and it has an XVA file. Now like I had said the XVA files, you can actually use them from the command line. So what this actually does here bash-c curl-s http xoay.io slash deploy, it's going to download and run from the command line the actual XVA file right into the system and stream it in. So this is the script in case you want to know what it looks like. This is the XA to deploy that actually runs from right here. Let's go ahead and just run it from the command line. Copy, we're going to ssh into the server. I know you shouldn't run things from the command line that you copy and paste off of things, especially as root, but you know this is a YouTube demo. Run at your own risk. Welcome to the XOA auto deploy script. So IP address, DHCP, sure. Importing XOA VM, that was it. There's not another command that you have to run to make that work. So here is running through the export now. Let's get this out of the way behind us. Let's go back over to the system and here it is. Now the yellow means it's on its way, so we can go over here notifications. Actually he's probably already done. It's doing the import from the command line test not in the notifications, but it's downloading and setting this up and we'll just wait a few minutes and it'll be ready. All right, that's it. So now the Zen server is ready and we can just go to this IP address. We're going to copy the link and this is in there. It's admin at admin.net and admin password. So my bad. Net. Don't leave that at default. Now we're going to go ahead and hit add server. Fancy password, which in case you didn't know by the typing, it's one, two, three, four, five, six. You do have to check unauthorized certificates and hit connect and that's it. Now we can actually go to the dashboard and there's those DB and YouTube VMs and we're in here. Now I've done a few videos already on Zen Orchestra. This is the basic free version that does not have all of the features. Now, they're giving you the email address for the download. If you notice, I didn't have to give an email address, but that also means I don't get to just do the in-place upgrades with this. So if I want to do the in-place upgrades, I have to do that. I have to do that and I've done a video on the difference between Zen Orchestra free and Zen Orchestra the one you build yourself. It is open source, but if they build it for you, they have a fee for it. If you build it yourself and support it yourself and inside you on VM, you can. But that's all you have to do to get started and now you're running with Zen Server. So hopefully this is a good guide to get you started with this and playing with it and you can watch all my other videos in this series of the base. I will do a separate video on how to connect this to a free NAS with ICE because that's kind of an ideal way and something more enterprise you're going to see is with your storage server connected to your virtualization server. Now it's not just for Zen, this is something you're going to see in both Zen Server and in VM where a lot of other commercial systems do that. You have your server separate. So that'll be a separate video and look for that coming in the next week or so. Thanks for watching. If you liked this video, go ahead and click the thumbs up. Leave us some feedback below to let us know any details which you like and didn't like as well because we love hearing a feedback or if you just want to say thanks, leave a comment. If you wanted to be notified of new videos as they come out, go ahead and subscribe and the bell icon that lets YouTube know that you're interested in notifications. Hopefully they send them as we've learned with YouTube. Anyways, if you want to contract us for consulting services, you go ahead and hit launch systems.com and you can reach out to us for all the projects that we can do and help you. We work with a lot of small businesses, IT companies, even some large companies and you can farm different work out to us or just hire us as a consultant to help design your network. Also, if you want to help the channel in other ways, we have a Patreon. We have affiliate links. You'll find them in the description. You'll also find recommendations to other affiliate links and things you can sign up for on LawrenceSystems.com. Once again, thanks for watching and I'll see you in the next video.