Mark Minasi's Tech Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 940
Reply with quote  #1 
I know, 2003 is no longer supported by MS.
Don't mean its not used.
Spent 5 hours trying to get a 2003 dynamic disk to boot....finally get it working, because the guest isn't patched the right way the integration tools don't work.networks, ram 
so i can't network it- why oh why


FFS

I can run NT (and i do run some old servers on VMware) and test the DR plans.
regularly with no issue.

rename servers ,disks, ram management, migration, it stays up.

Who cares if the numbers are bigger.
If the basics don't to all we want, what use is 24TB RAM and 512 Cores.


__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 301
Reply with quote  #2 
What exactly is the problem Joe ? No LAN connectivity for the Win2003 VM on Hyper-V ?

Have you tried with a legacy network adapter ?
I have a WinXP and some Win2003+SP2 that runs on Hyper-V 2012 (no R2).  It works with the (non-legacy) Network Adapter.
Integration Services is version 6.2.9200.16384.

__________________
Pieter Demeulemeester
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 940
Reply with quote  #3 
It was many things.
3 weeks of working with VMware and then back to Hyper-V.
Soo many things that took too long.

Had to recover a 2003 Server, that had dynamic disks, wasn't patched, bad backup....

__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.