Virtualizing a server halp
#1
Elite Member
Thread Starter
iTrader: (6)
Join Date: Sep 2007
Location: CA
Posts: 2,016
Total Cats: 13
Virtualizing a server halp
I have old 32 bit dental software called Dolphin. It’s served me well for many years. I’d like to keep using it. I understand it is not hipaa compliant.
It is the Dolphin server and workstation installation disk. Is it possible to install win8.1 and virtualize windows server 2008 (32bit) and install Dolphin server on it? I have 3 workstations that need to connect to the Dolphin server.
If so, how do you set up the networking to get it to work? I may hand it over to a pro but would like to screw around with it. Thanks
It is the Dolphin server and workstation installation disk. Is it possible to install win8.1 and virtualize windows server 2008 (32bit) and install Dolphin server on it? I have 3 workstations that need to connect to the Dolphin server.
If so, how do you set up the networking to get it to work? I may hand it over to a pro but would like to screw around with it. Thanks
#2
I don't know what "Dolphin" is but in theory, I dont' see why your plan won't work. I would use Windows 10 over 8.1 but virtualization Windows Server 2008 using Hyper-V isn't an issue. When you select the network interface within hyper-v choose "External Switch". This should put the VM on the same network as whatever computer it resides on. Also, make sure you change the settings for the Windows Server 2008 VM so that one of the "IDE Controllers" is set to your physical cd drive.
#4
Only 1 ethernet cable is required.
You mentioned "workstation installation disk", i'm assuming this is a physical cd with your "dolphin" installation software on it. If so, you will need to configure the VM (windows server 2008) to use your dvd drive so that it can see the dvd.
https://social.technet.microsoft.com...inserverhyperv
You mentioned "workstation installation disk", i'm assuming this is a physical cd with your "dolphin" installation software on it. If so, you will need to configure the VM (windows server 2008) to use your dvd drive so that it can see the dvd.
https://social.technet.microsoft.com...inserverhyperv
#8
Elite Member
iTrader: (13)
Join Date: Dec 2006
Location: Taos, New mexico
Posts: 6,612
Total Cats: 567
I'd spin up a new machine running linux of some flavor, Ubuntu is super easy now days. Then install VirtualBox (free and easy to install through ubuntu software manager), and run your server OS of choice there.
This would keep resources nice and low on the host machine. Windows running windows in virtualization is pretty bloat (if you ask me).
This would keep resources nice and low on the host machine. Windows running windows in virtualization is pretty bloat (if you ask me).
#9
Disagreed with fireindc. Ubuntu is just adding another layer of crap to understand for a non-techy without much benefit. The major slowdown from virtual machines comes from emulation, but...
Dell T20.. E3-1225 cpu?So it's pre-sandybridge, but does support vt-x. Virtualization will run about as well as it can under windows or linux. Just make sure it's enabled in the bios.
(edit: actually it is a sandybridge, but an LGA1155).
Dell T20.. E3-1225 cpu?
(edit: actually it is a sandybridge, but an LGA1155).
#10
Elite Member
Thread Starter
iTrader: (6)
Join Date: Sep 2007
Location: CA
Posts: 2,016
Total Cats: 13
Ubuntu is way over my head. Thanks for the suggestion though.
So which flavor of Windows (Win 8.1, Win10, or Server 2012 R2) would be easier and perform better to virtualize Server 2008 through hyperv?
Or which flavor of Windows would be best for Virtualbox?
So which flavor of Windows (Win 8.1, Win10, or Server 2012 R2) would be easier and perform better to virtualize Server 2008 through hyperv?
Or which flavor of Windows would be best for Virtualbox?
#13
What is your end goal here? Are you wanting to keep a current old server intact and move it to new hardware, or are you wanting to install it fresh on something else?
The below assumes a fresh install is wanted:
Couple of things:
1.) A 64-bit host OS can host a 32-bit Virtual Machine. Your host doesn't have to also be 32-bit.
2.) Hyper-V is superior to Virtualbox. Hyper-V is a free feature you can enable in Windows Server. Your 2012 R2 box should be compatible. The only thing you may have to verify is that Virtualization features are turned on in your system BIOS.
What I would do is install Hyper-V services on your 2012 R2 or later server.
Open Hyper-v Manager, go into Virtual Switch Manager and setup an External switch.
Click radio button for External Network, choose your NIC that you use, and then check the box for Allow management operating system to share this network adapter.
Download a copy of Windows Server 2008 as an ISO, or you have a disc you can use that instead. In Hyper-V Manager, choose New -> Virtual machine and go through the setup wizard. Give it an appropriate amount of RAM, but you'll be capped at 4GB for a 32-bit OS. If asked, do a Generation 1 VM. On the Configure Networking section, pick the Virtual switch you created above. When it gets to the screen asking you how you want to setup an OS, choose from the ISO you downloaded or the physical DVD drive of the server to use a disc. (Side note: I realize your software is already not HIPAA compliant, but Server 2008 OS's go out of main support in about a month from now, so keep that in mind).
Create the VM, start it, and go through the Windows setup process. From there, setup your software.
The below assumes a fresh install is wanted:
Couple of things:
1.) A 64-bit host OS can host a 32-bit Virtual Machine. Your host doesn't have to also be 32-bit.
2.) Hyper-V is superior to Virtualbox. Hyper-V is a free feature you can enable in Windows Server. Your 2012 R2 box should be compatible. The only thing you may have to verify is that Virtualization features are turned on in your system BIOS.
What I would do is install Hyper-V services on your 2012 R2 or later server.
Open Hyper-v Manager, go into Virtual Switch Manager and setup an External switch.
Click radio button for External Network, choose your NIC that you use, and then check the box for Allow management operating system to share this network adapter.
Download a copy of Windows Server 2008 as an ISO, or you have a disc you can use that instead. In Hyper-V Manager, choose New -> Virtual machine and go through the setup wizard. Give it an appropriate amount of RAM, but you'll be capped at 4GB for a 32-bit OS. If asked, do a Generation 1 VM. On the Configure Networking section, pick the Virtual switch you created above. When it gets to the screen asking you how you want to setup an OS, choose from the ISO you downloaded or the physical DVD drive of the server to use a disc. (Side note: I realize your software is already not HIPAA compliant, but Server 2008 OS's go out of main support in about a month from now, so keep that in mind).
Create the VM, start it, and go through the Windows setup process. From there, setup your software.
#14
If you want to move a current old OS to a newer box, you can do a "P2V" (Physical to Virtual) conversion using a free utility from Sysinternals.
https://docs.microsoft.com/en-us/sys...loads/disk2vhd
You would still create a new Virtual Machine like outlined above, but instead of creating new VHD files, you'll use the Sysinternals Disk2VHD utility to convert your running server into VHD files that you can attach to your new VM in Hyper-V.
https://docs.microsoft.com/en-us/sys...loads/disk2vhd
You would still create a new Virtual Machine like outlined above, but instead of creating new VHD files, you'll use the Sysinternals Disk2VHD utility to convert your running server into VHD files that you can attach to your new VM in Hyper-V.
#16
HIPAA Compliance is all or nothing. Funny I saw this thread I"m certified in this foolery and manage a MSP IT company specific for the dental field. As of Jan 10 of this year or so only Server 2012 and newer are HIPAA compliant. Doesn't matter if your server 2008 is ritualized or not. Also DO NOT run Windows 8.1. It's garbage and if your already making the moves then upgrade to Windows 10. You'lll notice that most software vendors in dental field won't even touch a Windows 8.1 computer.
#17
Elite Member
Thread Starter
iTrader: (6)
Join Date: Sep 2007
Location: CA
Posts: 2,016
Total Cats: 13
I'm having a hell of a time getting this updated to SQL2005 (or even SQL2000 no less). I've tried every combination. Any advice on what I'm doing wrong?
What I currently have:
When I try to install SQL 2005 Std Edition, I get this:
What I currently have:
When I try to install SQL 2005 Std Edition, I get this:
Thread
Thread Starter
Forum
Replies
Last Post
blaen99
Gaming
38
09-24-2012 02:25 AM