Server 2003 P2V Issues
-
@dustinb3403 It's running a specialty application for manufacturing that is also no longer made so upgrading it means about a 1.2 million dollar project and about 4-6 months of engineering work and 8 to 12 weeks of install and commissioning work.
This work because of this is now approved but I am just trying to get the system working again to be able to run production and meet orders until a new system is in place.
Most of this engineering will be done by me and my company bu the focus now is getting back in production.
-
@eleceng said in Server 2003 P2V Issues:
How can I get a 2003 key that I can activate? Would that be possible with a volume license? Or MSDN subscription?
I really don't have much knowledge of the visual studio and MSDN subscriptions.Technically a Visual Studio Subscription (formerly MSDN) will work BUT it's against the licensing. It only allows for test and development, not running production servers.
-
@eleceng said in Server 2003 P2V Issues:
@dustinb3403 It's running a specialty application for manufacturing that is also no longer made so upgrading it means about a 1.2 million dollar project and about 4-6 months of engineering work and 8 to 12 weeks of install and commissioning work.
More sunk cost fallacy, it cost to much to maintain the software, and now it cost even more to upgrade to the new stuff, so we'll just let our shit run forever until it dies, hoping it doesn't.
Yup. Case and point....
-
If the business had this system that was their bread and butter, that is going to cost so much money and time to ensure doesn't go offline, and they still let it happen.
Then this is entirely the businesses fault and stop supporting stupid fucking decisions..... like trying to get a 2003 Server to P2V and continue running it.
There was certainly virtualization options back 6 years ago, hell I moved 3 organizations to completely virtual within that time span...
-
Something not touched on here is back ups, are there any at all? If not then clearly this system wasn't at all important.
If it truly is so important now, what changed to lead up to this cluster fuck of a failed physical server 2003 still being present today?
I know I'm coming off as a dick, deal with it.
-
@dustinb3403 I don't disagree that they made a pile of bad decisions but that's nothing to do with me as I am a private contractor so I don't work for them or care to help them with their management issues as that's not what I get paid to do.
I was hired to find a temporary fix and start the upgrade process. The upgrade process has started and concurrently I am trying to get a temporary fix going so I can concentrate on the upgrade and get paid.
The poor management issues are their business quite frankly,
-
@pete-s if I can get it working I will find and buy a retail license or something. I will buy 50 if I can get it working.
Now that production is down money is no object and it's an open checkbook just trying to buy time.
My main concern is that even if I had a retail copy in hand it won't let me log in to do anything with the activation and that is where i am stuck.
-
@pete-s The server was from the DCS Manufacturer and nothing to be found about them on the internet. The power supply burned and is toast because we tried to have it fixed at an electronics repair shop.
-
@pete-s which of these would I want? https://visualstudio.microsoft.com/vs/pricing-details/
-
@dustinb3403 said in Server 2003 P2V Issues:
Something not touched on here is back ups, are there any at all? If not then clearly this system wasn't at all important.
If it truly is so important now, what changed to lead up to this cluster fuck of a failed physical server 2003 still being present today?
I know I'm coming off as a dick, deal with it.
Yes you're being a dick... As usual.... but you're actually right this time
-
I'm guessing that this is Server 2003 and not 2003 R2, which may explain why the reset command isn't working.
-
Rather than looking for the server manufacturer, it would likely make more sense to lookup the server motherboard model.
That could possibly get you some details on the types of power connections you'll need.
My guess is that this server is pre-2003, so late 90's maybe? You're probably using a P1 or P2 processor at best.
-
@eleceng said in Server 2003 P2V Issues:
@pete-s The server was from the DCS Manufacturer and nothing to be found about them on the internet. The power supply burned and is toast because we tried to have it fixed at an electronics repair shop.
All PC power supplies are actually the same. There is a set of standard voltages they supply +3.3V, 5V, 12V etc. So regardless of form factor they are the same. The specs are the ATX standard.
Some embedded systems run on a single voltage internally, like 12V, but it's usually very easy to spot that.
-
@eleceng said in Server 2003 P2V Issues:
@pete-s which of these would I want? https://visualstudio.microsoft.com/vs/pricing-details/
You can compare them here:
https://download.microsoft.com/download/1/5/4/15454442-CF17-47B9-A65D-DF84EF88511B/Visual_Studio_by_Subscription_Level.xlsxI would get the Visual Studio Professional Retail. It's $1200 I think.
-
@dustinb3403 said in Server 2003 P2V Issues:
Rather than looking for the server manufacturer, it would likely make more sense to lookup the server motherboard model.
That could possibly get you some details on the types of power connections you'll need.
My guess is that this server is pre-2003, so late 90's maybe? You're probably using a P1 or P2 processor at best.
yeah, I'd be looking at the power connector and seeing if you can get a PS that matches that, that's likely your fastest fix.
-
Have you tried logging in from the console, not an RDP session?
-
@eleceng Pic the server setup with the cover open, the motherboard, the motherboard's make and model, and the power supply make and model.
We've been building servers for eons. We may have a compatible PSU sitting in our bin or at least be able to indicate what to get from auction site(s).
As far as activation goes, does Safe Mode work?
EDIT: Boot the VM to Server 2003 .ISO --> Recover --> CMD --> slgmr /rearm [ENTER].
