Migrated ISA Server from physical to Hyper-V, setting new network adapter

Last night I made an Acronis True Image Echo Enterprise Server backup of an old laptop, which was running ISA Server 2006 for testing HTTP routing. With Acronis Universal Restore, I restored the system into a Hyper-V instance. For most part, things look well, except one big nag

Configuration Error
Description: The IP address specified for communication between this ISA Server computer (192.168.1.19) and other array members is not bound to a network adapter installed on this computer. The IP address specified for intra-array communication must be bound to a network adapter installed on the computer.

Since the physical Ethernet port on the laptop is obviously gone, I have to use the Hyper-V network adapter. So I need to tell ISA Server about this new adapter. Problem is, I cannot find where I can do this? Anybody?

I believe this error is due to the event

Event Type:   Error

Event Source: DCOM

Event Category:      None

Event ID:     10016

Date:         18/11/2008

Time:         08:36:44

User:         NT AUTHORITY\NETWORK SERVICE

Computer:     FOREFRONT

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{BA126AD1-2166-11D1-B1D0-00805FC1270E}

 to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20).  This security permission can be modified using the Component Services administrative tool.

After granting NETWORK SERVICE Local Activation permission to netman (Network Management Connection class), the DCOM error goes away and so does the ISA Server complaint. I do not know why the restoration brings about this error; was not there in the original machine.

Hmm,, don't know what are those errors about...

Somethings you need to do when u move virtual machines from virtual server to hyperv. Uninstall the Virtual Server equivalent to Integration Services in HyperV (too long ago liao, forgot the name) before you move.

Network cards, for ISA, use legacy. If you haven't figure out how to add the network cards, shut down ISA first. Got to virtual machine properties, add new hardware, select legacy network adapters. If u use the default adapters, your ISA will hang, because of some network stack incompatibility.

This ISA Server OS was running on a physical laptop; no VM Additions package used. In this new guest machine shell, i can use the VM Bus network adapter just fine. The legacy network adapter, which I used only for Acronis Universal Restore to obtain a network connection, is disabled in Windows.

Disabled? How come?

The VM Bus Network is known to caues problem, even in the new version of ISA... It is only fix in later build...

Because I got it to use the VM Bus Network Adapter. (is this not the recommended adapter when working with a Hyper-V guest?) I do witness any problems you mention, at least not yet. Since i wish to keep it as the same Single Network Adapter template, I disabled the legacy network adapter.

During restoration, Acronis Universal Restore does not recognise the VM Bus adapter, so the legacy adapter was needed for it to boot up and contact the remote shared folder where the backup TIB image was located.

It is actually better to use VM Bus Network Adapter, as it is faster. Just not for ISA 2006.