Dell I3 Windows 10

0 views

Skip to first unread message

Varinia Swicegood

unread,

Aug 3, 2024, 5:58:44 PM8/3/24

to ciafindcindi

Thank you. I came across a few posts that had 2016 and 2019 seems both OP had commented to update BIOS in order for it to work. Which I have done so as well as updating the 6/i firmware. I will give it a try later this week and report back

I have a R610 & R410 running Server 2019 but we changed the PERC RAID adapter as you may have issues finding drivers. Then also installation of OS is a real hassle. WE moved to ESXi then installed VMs. Note, the server is used for test & lab, not production.

I have never had any issues with using the Dell Windows based installers to install the Dell firmware updates under Windows Core/Hyper-V Server. Just download the update via another machine and copy it over or run it over the network.

If I had a 2012 license and needed to pay for a 2019, I am not sure that I would do that. Do you plan to keep the R710 beyond the extended support date of 2012? I think it goes end of extended supportnin 2023.

Confirming Dell PowerEdge R710 works flawlessly with Windows Server 2019. We have a couple of them running Hyper-V virtual machines on top of a core edition, and everything is managed using RSAT (in some cases) and Windows Admin Center -us/windows-server/windows-admin-center primarily. A step-by-step deployment guide can be found here -admin-center-for-windows-server-2019-getting-started . The recent versions have Device Manager already implemented, so installing and managing drivers is no longer an issue. Yet, as far as I remember, all the drivers were detected and downloaded automatically via Windows Update.

For everything else, or older servers, I create a folder called Software on the root of the C: drive for my core servers (which is almost all of them) and copy any installers there using the admin share.

In order to add network adapters to guest machines, you need to configure a virtual switch in Hyper-V first. The official guide covers the matter pretty excellent Create and configure a virtual switch with Hyper-V Microsoft Learn .

Since Windows Server 2019 and 2022 are very similar in terms of the codebase, I am pretty sure you can manually point the Device Manager wizard to the required INF files for previous Windows Server operating systems and it will work without issues. At least that approach is definitely worth trying.
Upgrading the RAID controller to H200 or H700 is a good Plan B option.

What I was wondering was if someone with H700 controller can start the inplace upgrade setup (initial check which reports if all is compatible). If all would be ok, only than I would upgrade the controller to H700.

Another option is to install SSD HDD in a caddy in place of the existing ODD to install the OS on it and get rid of the whole internal RAID controller and map the storage with iSCSI from a SAN since this will only be for backup. The internal SATA controller is only SATA2 but this should do the trick but not redundant solution. For redundancy to run at least mirrored drives we would need PCIe SATA controller card but again would need to look for what would work in this server.

I can say that it seems that out of the box there will be a multi-touch API, which is what you should find available in the Win 7 RC SDK linked in Tim J's answer. In addition WPF 4.0 will include multi-touch APIs and controls which it would seem that the Surface SDK 2.0 will extend/build upon.

The easiest option is to develop for Multi-Touch is with Silverlight on Win7. I have a small application developed in Silverlight on an HP TouchSmart with Win7 on it. -3-multi-touch-with-windows.htmlWhen the application runs you can make the Browser in Kiosk mode(Full Screen)But if you are looking for very advanced features outside Silverlight, then go ahead with Win7 SDK.