P2V of SBS 2003 Premium

i'm upgrading network infrastructure of charity. have couple of physical boxes (a poweredge 2800 & 2900). 2900 virtual server host dynamics crm 4 installation.

i've moved 4 guest os machines virtual server hyper-v without issues , indeed able use disk2vhd virtualize crm host , running vm on hyper-v. in all, a painless experience.

the machine running hyper-v on poweredge r710 64gb of ram , 4 nics. i'm little lost in nics configuration of the virtual network manager section of server (although think have configured correctly talking each other , domain should be). if go sconfig on hyper-v box , choose (8) network settings there 1 network adapter listed (192.168.16.29 - statically assigned me within excluded range in dhcp). have 2 nics attached network 1 appears getting address allocated (was planning on using other nic that's been connected manage server). can confirm how should setup it's causing confusion , i'm wary of 'messing' setup if it's working expected. network standared sbs domain setup hyper-v machine sits within it's own workgroup , not attached domain (thought best others may have opinions).

the other issue have sbs2003 premium box charity using. planning on migrating sbs2011 standard within next couple of weeks we're looking move sbs2003 box vm. we've done disk2vhd , went weekend. did few tests , worked ok long testing internally domain - problem is...the sbs box has isa 2004 sp2 installed , dual nic configuration.

the lan side nic has standard 192.168.16.2 ip address other nic (wan) has static ip assigned isp (84.19.***.***). have 1 virtual network setup on hyper-v @ moment , i'm not sure if need 1 wan nic @ - if fire sbs vm (after powering down physical machine) lan nic connects fine wan nic sits disconnected though it's been configured same ip details physical machines wan nic.

do need configure second virtual network nic @ , connect physical cable port? i'm aware we're looking move setup single nic install on sbs2011 box seperate firewall (possibly draytek 2920 or similar - again open suggestions) sitting @ the edge but in order allow full migration testing need sbs2003 virtualized , running right if that's possible.

i know there's lot here (and i'm jumping around fair amount) suggestions has more welcome.

thanx

this quite detailed issue , can see have spent lot of time on trying across.  let me try explain.  extremely useful if share schematic.

in hyper-v have 3 options nic installed on system.

you can leave nic unconfigured , host server can access network on interface.  best option management networks.

you can assign nic exclusive access hyper-v creating new network in hyper-v virtual networks not ticking allow host operating system... tickbox.  ig have lots of cards have sounds option.

finally can create virtuak network , tick afore mentioned box.  virtual switch created , copy of nic created using virtual nic driver , shown hyper-v server.

in scenerio suggest following:

1. use nic 1 management interface , give static ip address.  use configure server etc.
2. configure second dedicated virtual network , use internal lan communications on internal network range.
3. configure third dedicated virtual network , use external isa communications on public network range.

cabling wise nic 1 , nic 2 should connected internal infrastructure.
nic 3 connected internet connection only.

going forward have decent firewall router (2820).  configure thourough set of firewall rules block standard traffic , ditch isa configuration.

Windows Server  >  Hyper-V