I am trying to setup to Virtual PC's one running Win 2008 wich works great,
can set a static IP address using the Internal Network. When I install Win
2008 (32 bit) Server Core and set as Internal Network I get the 169.254.0.16
address. But if I set the network card to use my wireless I get a DHCP
address from my wireless router. So I'm thinking I need to install the
Integration Components for the network adapter, but I cannot get it
installed. I do not see the Integration Components on the Win 2008 CD and I
only see it listed under the Virtual PC directory which when I install just
rolls back the install.

Appreciate any help.

Thanks,
Dave

That is to be expected. From an internal network you can only see other
vms. You cannot see machines on the physical network. You need to use a
virtual network linked to a physical NIC in the host to see machines on your
LAN (and your DHCP server).

What do you want the vm to communicate with? If you want it to
communicate with other vms, give them all static IPs in the same IP subnet.
If you want it to communicate with physical machines, link it to a physical
NIC and let it get its IP config from DHCP.

Integration Components are for Hyper-V, not WVPC.


"Dave" <Dave@newsgroup> wrote in message
news:18967A57-B39E-4C6A-B213-D433FF9CB3B7@newsgroup

> I am trying to setup to Virtual PC's one running Win 2008 wich works
> great,
> can set a static IP address using the Internal Network. When I install
> Win
> 2008 (32 bit) Server Core and set as Internal Network I get the
> 169.254.0.16
> address. But if I set the network card to use my wireless I get a DHCP
> address from my wireless router. So I'm thinking I need to install the
> Integration Components for the network adapter, but I cannot get it
> installed. I do not see the Integration Components on the Win 2008 CD and
> I
> only see it listed under the Virtual PC directory which when I install
> just
> rolls back the install.
>
> Appreciate any help.
>
> Thanks,
> Dave

Thanks Bob. You're right of course. I think the problem is probably Server
Core in the vm. Clicking on the "Install Integration Components" will mount
the iso in the guest, but I am not sure that Core knows what to do with it.

Have you ever tried this? I gave up on Core during the beta! I can't cope
without the GUI.


"Robert Comer" <bobcomer-removeme-@newsgroup> wrote in message
news:4AB33DEF-EBAA-420B-B0E5-F6ADF0F11B4C@newsgroup

>> Integration Components are for Hyper-V, not WVPC.

>
> It's actually called "Integration Components" for WVPC too, though they
> are most certainly different than the Hyper-V ones...
>
> --
> Bob Comer
>
>
> "Bill Grant" <not.available@newsgroup> wrote in message
> news:eGVKHMT1KHA.260@newsgroup

>> That is to be expected. From an internal network you can only see other
>> vms. You cannot see machines on the physical network. You need to use a
>> virtual network linked to a physical NIC in the host to see machines on
>> your LAN (and your DHCP server).
>>
>> What do you want the vm to communicate with? If you want it to
>> communicate with other vms, give them all static IPs in the same IP
>> subnet. If you want it to communicate with physical machines, link it to
>> a physical NIC and let it get its IP config from DHCP.
>>
>> Integration Components are for Hyper-V, not WVPC.
>>
>>
>> "Dave" <Dave@newsgroup> wrote in message
>> news:18967A57-B39E-4C6A-B213-D433FF9CB3B7@newsgroup

>>> I am trying to setup to Virtual PC's one running Win 2008 wich works
>>> great,
>>> can set a static IP address using the Internal Network. When I install
>>> Win
>>> 2008 (32 bit) Server Core and set as Internal Network I get the
>>> 169.254.0.16
>>> address. But if I set the network card to use my wireless I get a DHCP
>>> address from my wireless router. So I'm thinking I need to install the
>>> Integration Components for the network adapter, but I cannot get it
>>> installed. I do not see the Integration Components on the Win 2008 CD
>>> and I
>>> only see it listed under the Virtual PC directory which when I install
>>> just
>>> rolls back the install.
>>>
>>> Appreciate any help.
>>>
>>> Thanks,
>>> Dave

>>

>You're right of course. I think the problem is probably Server Core in the

>vm. Clicking on the "Install Integration Components" will mount the iso in
>the guest, but I am not sure that Core knows what to do with it.

I don't think it has anything like autorun on core, so you'd have to start
it manually, but I could be mistaken. There's no synthetic NIC in WVPC so
the integration components wont help with any networking problem.

> Have you ever tried this? I gave up on Core during the beta! I can't
> cope without the GUI.

Nope, never tried it. The closest I've been was running the free hyper-V
Server for a bit. I much prefer a GUI myself!

--
Bob Comer

"Bill Grant" <not.available@newsgroup> wrote in message
news:#FYgDIU1KHA.5996@newsgroup

> Thanks Bob. You're right of course. I think the problem is probably
> Server Core in the vm. Clicking on the "Install Integration Components"
> will mount the iso in the guest, but I am not sure that Core knows what to
> do with it.
>
> Have you ever tried this? I gave up on Core during the beta! I can't
> cope without the GUI.
>
>
> "Robert Comer" <bobcomer-removeme-@newsgroup> wrote in message
> news:4AB33DEF-EBAA-420B-B0E5-F6ADF0F11B4C@newsgroup

>>> Integration Components are for Hyper-V, not WVPC.

>>
>> It's actually called "Integration Components" for WVPC too, though they
>> are most certainly different than the Hyper-V ones...
>>
>> --
>> Bob Comer
>>
>>
>> "Bill Grant" <not.available@newsgroup> wrote in message
>> news:eGVKHMT1KHA.260@newsgroup

>>> That is to be expected. From an internal network you can only see other
>>> vms. You cannot see machines on the physical network. You need to use a
>>> virtual network linked to a physical NIC in the host to see machines on
>>> your LAN (and your DHCP server).
>>>
>>> What do you want the vm to communicate with? If you want it to
>>> communicate with other vms, give them all static IPs in the same IP
>>> subnet. If you want it to communicate with physical machines, link it to
>>> a physical NIC and let it get its IP config from DHCP.
>>>
>>> Integration Components are for Hyper-V, not WVPC.
>>>
>>>
>>> "Dave" <Dave@newsgroup> wrote in message
>>> news:18967A57-B39E-4C6A-B213-D433FF9CB3B7@newsgroup
>>>> I am trying to setup to Virtual PC's one running Win 2008 wich works
>>>> great,
>>>> can set a static IP address using the Internal Network. When I install
>>>> Win
>>>> 2008 (32 bit) Server Core and set as Internal Network I get the
>>>> 169.254.0.16
>>>> address. But if I set the network card to use my wireless I get a DHCP
>>>> address from my wireless router. So I'm thinking I need to install the
>>>> Integration Components for the network adapter, but I cannot get it
>>>> installed. I do not see the Integration Components on the Win 2008 CD
>>>> and I
>>>> only see it listed under the Virtual PC directory which when I install
>>>> just
>>>> rolls back the install.
>>>>
>>>> Appreciate any help.
>>>>
>>>> Thanks,
>>>> Dave
>>>

"Robert Comer" <bobcomer-removeme-@newsgroup> wrote in message
news:E85AB714-BF96-4CA3-8D32-214ECA000ADA@newsgroup

>>You're right of course. I think the problem is probably Server Core in the
>>vm. Clicking on the "Install Integration Components" will mount the iso in
>>the guest, but I am not sure that Core knows what to do with it.

>
> I don't think it has anything like autorun on core, so you'd have to start
> it manually, but I could be mistaken. There's no synthetic NIC in WVPC so
> the integration components wont help with any networking problem.
>

>> Have you ever tried this? I gave up on Core during the beta! I can't
>> cope without the GUI.

>
> Nope, never tried it. The closest I've been was running the free hyper-V
> Server for a bit. I much prefer a GUI myself!
>
> --
> Bob Comer
>

Just a thought. It could be a UAC problem. Are you running as
administrator, Dave? Core can't send you a message to elevate!

"Bill Grant" <not.available@newsgroup> wrote in message
news:e6r6eDe1KHA.2156@newsgroup

>
>
> "Robert Comer" <bobcomer-removeme-@newsgroup> wrote in message
> news:E85AB714-BF96-4CA3-8D32-214ECA000ADA@newsgroup

>>>You're right of course. I think the problem is probably Server Core in
>>>the vm. Clicking on the "Install Integration Components" will mount the
>>>iso in the guest, but I am not sure that Core knows what to do with it.

>>
>> I don't think it has anything like autorun on core, so you'd have to
>> start it manually, but I could be mistaken. There's no synthetic NIC in
>> WVPC so the integration components wont help with any networking problem.
>>

>>> Have you ever tried this? I gave up on Core during the beta! I can't
>>> cope without the GUI.

>>
>> Nope, never tried it. The closest I've been was running the free hyper-V
>> Server for a bit. I much prefer a GUI myself!
>>
>> --
>> Bob Comer
>>

> Just a thought. It could be a UAC problem. Are you running as
> administrator, Dave? Core can't send you a message to elevate!
>
>

I had a bit of time to spare so I had a look at this. Yes, you have to
switch to the CD drive and run setup.exe. When you start the install of the
integration components it clearly spells out what OSs are supported. They
are XP SP3, Vista SP1 and Windows 7. No Server OS. I guess that is why it
rolls back in Server 2008.

> I had a bit of time to spare so I had a look at this. Yes, you have to

> switch to the CD drive and run setup.exe. When you start the install of
> the integration components it clearly spells out what OSs are supported.
> They are XP SP3, Vista SP1 and Windows 7. No Server OS. I guess that is
> why it rolls back in Server 2008.

Makes sense -- I wonder if the VPC2007 additions would install, that would
at least give you time sync and mouse integration.

--
Bob Comer


"Bill Grant" <not.available@newsgroup> wrote in message
news:egnIlAh1KHA.4560@newsgroup

>
>
> "Bill Grant" <not.available@newsgroup> wrote in message
> news:e6r6eDe1KHA.2156@newsgroup

>>
>>
>> "Robert Comer" <bobcomer-removeme-@newsgroup> wrote in message
>> news:E85AB714-BF96-4CA3-8D32-214ECA000ADA@newsgroup

>>>>You're right of course. I think the problem is probably Server Core in
>>>>the vm. Clicking on the "Install Integration Components" will mount the
>>>>iso in the guest, but I am not sure that Core knows what to do with it.
>>>
>>> I don't think it has anything like autorun on core, so you'd have to
>>> start it manually, but I could be mistaken. There's no synthetic NIC in
>>> WVPC so the integration components wont help with any networking
>>> problem.
>>>
>>>> Have you ever tried this? I gave up on Core during the beta! I can't
>>>> cope without the GUI.
>>>
>>> Nope, never tried it. The closest I've been was running the free
>>> hyper-V Server for a bit. I much prefer a GUI myself!
>>>
>>> --
>>> Bob Comer
>>>

>> Just a thought. It could be a UAC problem. Are you running as
>> administrator, Dave? Core can't send you a message to elevate!
>>
>>

> I had a bit of time to spare so I had a look at this. Yes, you have to
> switch to the CD drive and run setup.exe. When you start the install of
> the integration components it clearly spells out what OSs are supported.
> They are XP SP3, Vista SP1 and Windows 7. No Server OS. I guess that is
> why it rolls back in Server 2008.
>
>

"Robert Comer" <bobcomer-removeme-@newsgroup> wrote in message
news:7CBE1569-9B90-485D-BE94-7067EC0E3CD1@newsgroup

>> I had a bit of time to spare so I had a look at this. Yes, you have to
>> switch to the CD drive and run setup.exe. When you start the install of
>> the integration components it clearly spells out what OSs are supported.
>> They are XP SP3, Vista SP1 and Windows 7. No Server OS. I guess that is
>> why it rolls back in Server 2008.

>
> Makes sense -- I wonder if the VPC2007 additions would install, that would
> at least give you time sync and mouse integration.
>
> --
> Bob Comer
>
>

It is definitely something odd in Server Core. I installed a full version
of 2008 alongside using the same parameters and the ICs installed fine. On
Server Core they try to install then roll back and exit.