well, greetings people of the internet. Unki Joe here, Hunky Joe's Playhouse. Today, everything old is new again, or something along those lines. So, what the heck does that even mean, everything old is new again? Well, folks, I've got some older equipment here. As you all well know, one of those older pieces of enterprise-level equipment that I have is an IBM x3650 model 3 server. Now, I'm a Dell guy. I prefer Dells, but I have this IBM sitting around, and it's really not doing much of anything. I haven't really done anything with it since I did the multiple video cards using VMware, and that was fun. But I would like to, you know, put a newer, modern operating system on there and see how well it performs with this, you know, 12-year-old, 10-year-old equipment. Now, I was hoping I would be able to run VMware on here, but it's not going to happen. Yeah, VMware 7 is never going to run on equipment this old. The CPUs aren't

supported a lot of the hardware in here is not supported anymore. I could run Windows Server 2019 on here, and it would run just fine, and that would be my preferred way of doing things. But I like to live on the edge, so I thought this unit would be a perfect candidate for Windows Server 2022. So, I downloaded Windows Server 2022 from the Microsoft website, the evaluation version, and we're going to try and install it today on this IBM 3650 x3650 model 3. So, let's get that started right now, and there we go. Tools, go to session options, go to mouse relative, apply, okay, and then we should be able to come right here, start. It's been a while since I've used the IBM, and one thing I hate about the IBM is the RAID adapter on it. Um, yeah, I'm just not fond of it. Uh, the GUI in the BIOS, I'm not fond of. It's hard to understand how to make it work, but I think there is

a GUI that you can run for the controller once you get Windows loaded. And we'll worry about setting up RAID devices later. Right now, what I want to do is just try to get the install to run, see if we can install onto that 300-gig hard drive that's in there, spinning rust. Because I'm not going to spend the one benefit of this IBM. It has 16-bit PCI Express lanes, as opposed to 8-bit. Well, as two of them, but it's not real. This binge, this obsession I have with video cards and passing them through to virtual machines. I really don't have that desire anymore. So, all right. So, we're gonna try CD/DVD ROM. And there it goes. Now it's booting, or it's trying to. I need to. Yeah, I don't need this obsession to linger anymore with putting video cards into these units. I mean, let's put it this way. If I put a video card into this unit, then it makes perfect sense to run

windows as my operating system because at least part of windows could have access to that video card. And on the virtual machines, I don't care if they have access to the video card because I don't need them to use the video card for anything right now. This is a bare installation. I don't have any video cards in that IBM. I have a 300-gig SAS drive in there, and I've got four or five 146-gig SAS drives in there that I'll play around with later for an array. But today, the goal is just to get Windows Server 2022 loaded because it's ironic. I can't install VMware 7 on these units. It'll be interesting to see if I can install Windows Server onto it or what kind of trouble I'm gonna have. I know it'll run Windows Server 2019. All right, so far so good. I need to fix the mouse, make it absolute. There we go. Now we'll do next install now, and now we'll get to see if it's

actually going to see the hard drive without drivers. Hopefully, out of the box, Windows Server 2022 supports Windows Server 22 desktop experience because I like the GUI. I want the GUI, and if it won't install, drumroll custom. Yeah, see, it needs a storage driver. So, I put a different RAID controller in there. Well, SAS controller, static controller. So, I'm going to try that. Hopefully, it won't explode, and I don't know how it's going to come up on drive configuration, and I don't know how IBM is going to treat that card, whether it's a foreign invader. All right, so let's see if we're having any luck at all. Okay, Windows Server 2022. Oh my goodness, it sees the drives, or it sees some drives. Wow. So, it's seeing that as drive one. So, and it's seeing four other drives, or three other drives. So, what I probably need to do, it's working. I'll be damned. What I probably want to do, though, is shut down this unit and go with a single hard drive in here.

all right, so click on next, install now 2022, next. All right, so it sees it as drive zero, so I'm gonna do next. I'm just going to leave it in the hands of the installer and see what happens. Like, oh my god, there it goes. Well, we'll see if it starts copying the files to the install drive. Yep, there it goes. All right, so we'll let it run. All right, so here we go. We have some success and installed, so let's see if we can actually create a super secret password here and hopefully we put it in there correctly. Finish. We can probably exit the virtual media now, and it looks like, wow, success. Let's see if we can log in here. Let's start doing the updates. All right, should bring up server manager. So it's interesting that Microsoft is interested in. Now, this is in no way saying that Microsoft says, Oh yeah, go out and buy server 2022 and it'll work on these 12-year-old IBM servers. No, it's not what I'm saying. What I'm

saying is that the underlying operating system changes very little from version to version, whereas under VMware, going from six point whatever to seven, it was a huge change in the underlying core of the operating system. That's where Microsoft has the edge because it's Windows. It'll pretty much run on anything, even on old hardware. And depending on your circumstances and what roles that server's going to be doing, you know, you don't need that much power, to be honest with you. Now, if you're running a database server or you're running, you know, something that's doing a lot of calculations, yeah, you need it. But as you can see, pretty much out of the box, let's go to Device Manager. Actually, let's do it the proper way. Right-click here and go to Device Manager. And um, let's see what it's done. Um, yeah, there's a generic IPMI compliance device. It can't find a driver for. But other than that, um, yeah, it sees everything. And this is what I love about Windows. It just, it's kind of working out of the box. You

know even sees the Toshiba hard drive. So yeah, it's good. It's a good thing. So let me go out to the Ethernet controllers. Okay, because what I don't want to do, this is an IBM USB remote and this network device, and we're not going to need that. So I'm going to disable all these network adapters because I'm not using them right now. See no command line, and we'll rename this gigabit 1-1. And I wonder what IP address I want to give this server. So I think we're going to use 5.11. Let's just make sure here, do a command prompt, and let's make sure that that IP address is not being used for something else. And it doesn't appear to be. So we'll set this for 192.168.5. We'll set our gateway and our DNS server refresh. Let's go to status details 5.11. Okay, let's come here, let's refresh. Perfect Ethernet five. We're going to click on there, and we're going to disable.

so we don't need that one cool now one thing I wanted to see is this disk controller. Let's go to device manager and let's go to storage controller. Good, it sees that it is a SAS 2 2008 Falcon controller. So it is seeing it as the SAS controller. Now the next thing I want to do is come here to my time zone and change that to central time. And then the next thing I'm going to do is rename this server. I'll come up here and then go to change and we're going to call this IBM X 3650 - M3. It's the only one I have, so click on OK. And then, of course, we're going to need to restart. The next thing we're going to do is we're going to join the domain Monkey Joe's Playhouse. All right, so lunch is out of the way and I've rebooted the machine after renaming it. And now the next thing we're going to do is we're going to add it to the

unki joe's playhouse domain, uh, and then we're going to uh enable remote desktop as well so that I can get into this unit from my network without having to go through this imm module with ibm. And then the next step after that is going to be to put a video card in this thing and see if it'll how if it'll boot up still properly with a video card in there. So I'm going to go ahead and come over here to work group, click on that, click on change, and we're going to join the ujp.local. And then we'll enter the name with domain privileges or privileges that can add computers and users to the domain. And it's going to make us reboot again, and then we should be able to enable remote desktop. Actually, I can restart later. I'm going to go ahead and enable remote desktop as well and tell it okay and apply, and then we'll reboot. All right, so we've rebooted now. So now let's see if we can actually log in to the domain.

yep, sees it there. So let's enter our domain username and password. Now at this point, I think if memory serves me correct, this IBM has problems when there's not a problem. It's actually part of the design. When you put another video card in here, you lose the video capability on the IMM module. And I'd rather have that capability on the module than to lose it because I want to put a video card in here. This machine will be, I mean, it's got lots of cores and lots of RAM. Well, let's see. We'll see here once it pops up. Server Manager is going to pop up, and then we're going to close that, and then we're going to try to log in here remotely once we verify that that part of that is working. So we'll go over here to local servers. So there's the name of it. There's the domain. Should pop up here in a second. Good, and it's turned the firewall off. That's fine, and it's enabled remote desktop.

and it's at ip5.11. It knows it's on an IBM 3650 model three. It's got 60 gig of RAM, or I'm sorry, 50 gigabytes of RAM. It's that 300 gig hard drive in there. And uh, it has two E5620 CPUs in here. So let's turn off server manager from launching. Let's close server manager. Let's go over to task manager here. Let's just take a look at how many cores we have because I don't remember the CPU on this one. Okay, so we got two sockets, each with eight cores. So we got 16 logical processors. So this is a pretty underpowered server. It's only got an E5620. Let me go ahead and see if I can log in remotely to that server. So uh, that is uh, 5.11 I think we said. And we'll do more choices. We'll do UJP backslash Adama and our super secret password. And let's see how it does. Yes, and there we go boys and girls.

server 2022 is up. I'm connected by remote desktop. Let's see how it's doing performance-wise. It's got plenty of cpus in there and plenty of ram. So I'm going to add the hyper-v service to this ibm x3650, and it'll be interesting to see if it has the same problem I had with windows server 2019 when whenever you would add the hyper-v service and do your reboot, you wouldn't be able to get back on. You'd have to go back in through the imm adapter, reset the ip address in order for everything to work properly. So we'll find out. I'm going to use kerberos for the live migration permissions. We'll just leave the default install locations, click on install. So I'm gonna let this run and come back when it's time to change something. So the hyper-v service has been installed. So I'm going to go ahead and let it reboot, and then I'm going to log back in through this imm adapter, and then I'm going to probably have to

restart again, and then we'll try to log in by remote desktop. We'll see if the IP address on this has changed, so I'll come back when that screen shows something different. All right, so let me try to log on here through the IMM adapter, enter my super-secret password. All right, we'll see if it wants to reboot again. A lot of times, it'll come up after that install of Hyper-V and say I need to reboot one more time. Now, I'm going to go ahead and start Server Manager, even though I told it not to start. In this case, I want to see if that old bug rears, well, I call it a bug, it's actually an annoyance, and see if it changes the IP address again. And it looks like it has. Yeah, see, IPv4 address is signed by DHCP. So, we're going to come into here, and the first thing we're going to do is shorten the name of this NIC card because it really annoys me. So, we'll rename it. It'll be Gigabit 1-1-Vert.

for virtual. Okay, that'll help. And then come back here to properties, and we have to manually put our IP address back in. Yep, and it's gonna blow away our gateway again, I bet you. So, 192.168.511. Oh, that didn't work very well. Wow, again. Let's try it again. 192. Yes, 68.5.11. And it fills in the subnet. Don't worry about the gateway, because as soon as we save it, uh, 5.1 is our internal DNS, because as soon as we okay it here and okay there, it's going to change it again. So, we'll come back in one more time, and you'll see it should have lost the gateway, and it did. 254 is the gateway. Click OK. Click OK. Then let's refresh this screen, and then I should be able to get back in remotely. So, let's try that, and bingo, here we go. And there we go, back up and running. So, now what I need to do is get the... So, now we've got Hyper-V running. Uh, I go ahead and close Server.

manager. Uh, I'm also going to run Nine Night on here, uh, to get some applications installed, so we might as well do that now. And I'm gonna go ahead and put Chrome on here. We've already got Edge, so we should be good on there. I want to do Win FCP, Putty. I put all my normal utilities on here just in case I need them. Uh, we're gonna go ahead and put Handbrake on there because I like to run. I like to use Handbrake as a, uh, as a good way to, uh, work out the processors on these, uh, on these older servers. We're gonna put 7zip, and we'll go ahead and open it, let it install. And I like to put my little task manager up here so I can see. I mean, I paid for all those cores. I want to see them working, you know what I'm saying? Yeah, so you know VMware is great, XCP is great, Citrix XCP is great. Um, yeah, uh, Proxmox is great, uh, but I just keep

coming running back to Windows because the machine is so much more flexible when it's running Windows. I can run Linux on here if I need to, but I'd rather run Linux than a virtual machine that let it control the hardware. Just I like the interface of Windows. Come up under Windows Administrative Tools, and let's see, we want to do Hyper-V Manager, and we want to do, oh, let's see, the iSCSI initiator, and let's see what else on this. The rest I can get to through other ways, so yeah, we'll just put Hyper-V Manager here and iSCSI initiator here, and then we've got our nine nights installed. So let's see if we can go ahead and customize the taskbar. I want to use small icons and only combined with the taskbar is full. I don't need the task view. Let's see, hidden good toolbar is good. Now we'll go to Windows Update, and we'll start doing the updates. So as you can see, I've got quite a few pending updates, so I'm going to go ahead

and click on install now and let these run, and we'll come back when all the updates are done. So, that surprisingly went very well. Now, one of the problems I ran into, though, and I'm not real fond of the RAID controllers that IBM uses, their way they configure their RAID only on these LSI controllers, a little clutchy at best, and it's hard to get through the interface if you've never used it. So, and I don't use hardware RAID, I don't know very few people do anymore, and I wanted to be able to use storage spaces with these drives. So, I had an LSI controller lying around that having to be flashed into IT mode so that it just basically passes through the devices to the computer, and I put that into that unit, and I was able to create some storage spaces on those SAS drives I had had in that unit. So, next, I decided I wanted to try to put a video card back into that unit. Now, keep in mind, I've had video cards in

here before. In fact, this is one of the video cards I put in there. I was going to use this NVIDIA Quadro card that I've had about a year now. It's a Quadro K2000. You know, it's only a 75-watt card, so it'll go in a server with, you know, limited power supplies without you noticing. It doesn't have any of the little power connectors. Now, I've had this in that server before in conjunction with the GTX 650, and I ran them in VMware, and I passed them through to Windows virtual machines, and everything was fine. But I just like having a video card, even in a server operating system. It just gives me a little more flexibility. For example, mainly if I want to like have something to run Handbrake for a video through or something like that, something that requires a little more oomph than the CPUs can deliver, especially these CPUs. So, I put this card in, and it's nothing special. Now, keep in mind on this IBM when you

add another video card. You have to actually have this video card plugged into a monitor, and you lose the ability to use the video on your imm adapter, so you have to keep that in mind. One of the things I don't like, but it booted up into server 2022. I downloaded the drivers for this for Windows 10 because they're on Windows server drivers, loaded them, but I noticed it loaded the drivers and didn't give any error messages, but I couldn't see this card under task manager when I brought it up, nor could handbrake CD card to encode video in H.264 using the hardware encoder on there. So, it's I'm sure it's a driver issue. Windows server 2022 is just so new, and frankly, they're not going to do much to update the drivers on this little card to make it work. So, it was a success in loading Windows server 2022, and don't get me wrong, Windows server 2022 ran great because, you know, that's just

Windows, they're always backwards compatible. I mean, look, we're looking at 10, what, 12-year-old hardware here, still able to run Windows on it as my core operating system. And then I can run anything else I want to on top of it using Hyper-V. But I couldn't get the video card to work. Sad. So, going down the rabbit hole again, I just, so you know what I did, I went ahead and loaded Windows Server 2019 back onto this, to this monster IBM X 3650 Model 3. Put the video card in, loaded the drivers. Windows Task Manager was able to see the card and the drivers, no problems, easy peasy. I went to use HandBrake. I was able to tell HandBrake to encode using a hardware H.264 encoder and started encoding a video, a 33-gigabyte video Blu-ray down to 1080p using the N20, using MKV and H.264. And it got about a third of the way through, and the

server crashed, and the server has been crashing ever since then. Whether I put it through Handbrake or I let it sit for 10 or 15 minutes or something, so I have a feeling that something is going on with this IBM. So, I'm going to have to, uh, I put it aside for now. I've done this video on it just kind of like a proof of concept, but I'm having to put the IBM aside till I have some more time to look into it. I'm hoping I've got another system board just in case this one is bad, but it may be. This may be a sign from the internet beings, the internet gods, that it's time to retire that x3650 model 3. It's been a good server, but it is a little loud compared to the Dell. This video card will get some use in another server, so we're going to set the IBM aside for now, uh, and we're going to, uh, hopefully in the future, I can repair the thing or

see what's causing it to reboot all the time. So, there you go, folks. We hope you found the video entertaining and informative. As always, please hit the like button, leave your comments down in the comments section, subscribe if you're not already a subscriber, and hit that notification bell to be notified of any new videos when they come out. Donate if you're so inclined. We accept PayPal, Patreon, and the YouTube join functions right underneath every one of my videos. So, if you feel like you want to support the channel, that's one way of doing it. Thanks for coming to see us, and please don't forget, we'll see all of you on the other side. [Music] You

Server 2022 Install on the IBM X3650 Model 3

Server 2022 Install on the IBM X3650 Model 3