Virtual PC & WSUS

I have a single test domain with one server PC setup with Windows 2003 &
Virtual PC 2007. Virutal PC is setup as a XP client. Everything went fine,
but at the time for the updates to give me the notification on the Virtual
PC XP client, it gave me that desired result on the 2003 Server and not on
the Virtual PC XP client.

Am I right in assuming that when setup in this manner it will run on the
physical unit but not the virtual XP client?

[[ Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]

Don wrote:
> I have a single test domain with one server PC setup with Windows 2003 &
> Virtual PC 2007. Virutal PC is setup as a XP client. Everything went fine,
> but at the time for the updates to give me the notification on the
> Virtual
> PC XP client, it gave me that desired result on the 2003 Server and not on
> the Virtual PC XP client.
>
> Am I right in assuming that when setup in this manner it will run on the
> physical unit but not the virtual XP client?

> Don wrote:
>> I have a single test domain with one server PC setup with Windows 2003 &
>> Virtual PC 2007. Virutal PC is setup as a XP client. Everything went
>> fine,
>> but at the time for the updates to give me the notification on the
>> Virtual
>> PC XP client, it gave me that desired result on the 2003 Server and not
>> on
>> the Virtual PC XP client.
>>
>> Am I right in assuming that when setup in this manner it will run on the
>> physical unit but not the virtual XP client?

That would be an incorrect assumption.

WSUS will work perfectly with a machine in a VM, just as it does with a
physical machine.

Unfortunately, your description is a bit confusing, so I'm not entirely able
to follow the configuration you're working with, or exactly what you're
referring to by "... it gave me that desired result"


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Are you sure? I've never seen the update client work with VPC
2004. I thought there was some kind of virtual NAT in the virtual
machine, which interfered with authentication and identification.

There are a couple of network things I can't get to work entirely
on XP in VPC 2004: svn, webdav, I assumed that Windows
Update/WSUS was just another.

(david)

"Lawrence Garvin (MVP)" <> wrote in message
news:...
>> Don wrote:
>>> I have a single test domain with one server PC setup with Windows 2003 &
>>> Virtual PC 2007. Virutal PC is setup as a XP client. Everything went
>>> fine,
>>> but at the time for the updates to give me the notification on the
>>> Virtual
>>> PC XP client, it gave me that desired result on the 2003 Server and not
>>> on
>>> the Virtual PC XP client.
>>>
>>> Am I right in assuming that when setup in this manner it will run on the
>>> physical unit but not the virtual XP client?
>
> That would be an incorrect assumption.
>
> WSUS will work perfectly with a machine in a VM, just as it does with a
> physical machine.
>
> Unfortunately, your description is a bit confusing, so I'm not entirely
> able to follow the configuration you're working with, or exactly what
> you're referring to by "... it gave me that desired result"
>
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"david" <> wrote in message
news:...
> Are you sure?

Yes.

> I've never seen the update client work with VPC 2004. I thought there was
> some kind of virtual NAT in the virtual
> machine, which interfered with authentication and identification

> There are a couple of network things I can't get to work entirely
> on XP in VPC 2004: svn, webdav, I assumed that Windows Update/WSUS was
> just another.

Well, if the networking in the Virtual PC environment is not configured
correctly to allow EXTERNAL access from the VMs, then a lot of things
probably aren't going to work.

Just like if you put the WSUS Server on the other side of a firewall or
router and didn't give a physical machine behind the router the proper
configurations to go through the firewall/router.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"external" access?

My VirtualPC 2004 XP instances can see the SBS file server/,
domain controller/exchange server, login, browse the internet
through the BSD firewall, send and receive IMAP mail in
Outlook Express. They are joined to the domain, so they are
listed in WSUS 2.x on SBS 2003, they just never report,
and never get updated.

There doesn't seem to be anything obvious wrong, but it's
just not working.

The domain login includes a Windows Update policy which
tells them to update daily at Noon, or they should update at
login or turnon (I can't remember which), if they aren't turned
on at Noon.

The host is updating correctly, as are all other workstations
on the network.

On the other hand, HTML authentication is failing for Web Folders
on the VPC. (Windows Authentication is working: I can
create web folders for the SBS server, but not for the BSD
server).

I haven't got a packet filter installed on the VPC or the SBS
server, and of course those packets don't show up on the host
packet filter because the VPC is inserted in the stack below it.

Any ideas?

(david)



"Lawrence Garvin [MVP]" <> wrote in message
news:%...
> "david" <> wrote in message
> news:...
>> Are you sure?
>
> Yes.
>
>> I've never seen the update client work with VPC 2004. I thought there was
>> some kind of virtual NAT in the virtual
>> machine, which interfered with authentication and identification
>
>> There are a couple of network things I can't get to work entirely
>> on XP in VPC 2004: svn, webdav, I assumed that Windows Update/WSUS was
>> just another.
>
> Well, if the networking in the Virtual PC environment is not configured
> correctly to allow EXTERNAL access from the VMs, then a lot of things
> probably aren't going to work.
>
> Just like if you put the WSUS Server on the other side of a firewall or
> router and didn't give a physical machine behind the router the proper
> configurations to go through the firewall/router.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

Postscript:

Virtual XP is SP2, with no updates, installed from CD.

Is there an Windows Patch required to make Windows Update
work with a current patched version of WSUS 2?

(david)

"david" <> wrote in message
news:...
> "external" access?
>
> My VirtualPC 2004 XP instances can see the SBS file server/,
> domain controller/exchange server, login, browse the internet
> through the BSD firewall, send and receive IMAP mail in
> Outlook Express. They are joined to the domain, so they are
> listed in WSUS 2.x on SBS 2003, they just never report,
> and never get updated.
>
> There doesn't seem to be anything obvious wrong, but it's
> just not working.
>
> The domain login includes a Windows Update policy which
> tells them to update daily at Noon, or they should update at
> login or turnon (I can't remember which), if they aren't turned
> on at Noon.
>
> The host is updating correctly, as are all other workstations
> on the network.
>
> On the other hand, HTML authentication is failing for Web Folders
> on the VPC. (Windows Authentication is working: I can
> create web folders for the SBS server, but not for the BSD
> server).
>
> I haven't got a packet filter installed on the VPC or the SBS
> server, and of course those packets don't show up on the host
> packet filter because the VPC is inserted in the stack below it.
>
> Any ideas?
>
> (david)
>
>
>
> "Lawrence Garvin [MVP]" <> wrote in message
> news:%...
>> "david" <> wrote in message
>> news:...
>>> Are you sure?
>>
>> Yes.
>>
>>> I've never seen the update client work with VPC 2004. I thought there
>>> was some kind of virtual NAT in the virtual
>>> machine, which interfered with authentication and identification
>>
>>> There are a couple of network things I can't get to work entirely
>>> on XP in VPC 2004: svn, webdav, I assumed that Windows Update/WSUS was
>>> just another.
>>
>> Well, if the networking in the Virtual PC environment is not configured
>> correctly to allow EXTERNAL access from the VMs, then a lot of things
>> probably aren't going to work.
>>
>> Just like if you put the WSUS Server on the other side of a firewall or
>> router and didn't give a physical machine behind the router the proper
>> configurations to go through the firewall/router.
>>
>>
>> --
>> Lawrence Garvin, M.S., MCITP:EA, MCDBA
>> Principal/CTO, Onsite Technology Solutions, Houston, Texas
>> Microsoft MVP - Software Distribution (2005-2009)
>>
>> MS WSUS Website: http://www.microsoft.com/wsus
>> My Websites: http://www.onsitechsolutions.com;
>> http://wsusinfo.onsitechsolutions.com
>> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>>
>
>

"david" <> wrote in message
news:...

> My VirtualPC 2004 XP instances can see the SBS file server/,
> domain controller/exchange server, login, browse the internet
> through the BSD firewall, send and receive IMAP mail in
> Outlook Express. They are joined to the domain, so they are
> listed in WSUS 2.x on SBS 2003, they just never report,
> and never get updated.

Then you have a =WUA= problem that has absolutely nothing to do with Virtual
PC!

You should troubleshoot this exactly like you would if this VM were a
physical PC.

Run the Client Diagnostic Tool; inspect the WindowsUpdate.log


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"david" <> wrote in message
news:%...

> Virtual XP is SP2, with no updates, installed from CD.
>
> Is there an Windows Patch required to make Windows Update
> work with a current patched version of WSUS 2?

The native XP SP2 installation will not update from a WSUS 2.0 server unless
the client first successfully performs a 'selfupdate' of the Windows Update
Agent to upgrade it from the v5.4 client that's packaged in XP SP2 to the
v5.8 client that's required for use with WSUS 2.0


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Way to go!

Downloaded and installed http://download.windowsupdate.com/v6/windows

Before I could turn around, the first update (windows installer) was ready.

Thanks everyone.

(david)

"Lawrence Garvin [MVP]" <> wrote in message
news:uJsy%...
> "david" <> wrote in message
> news:%...
>
>> Virtual XP is SP2, with no updates, installed from CD.
>>
>> Is there an Windows Patch required to make Windows Update
>> work with a current patched version of WSUS 2?
>
> The native XP SP2 installation will not update from a WSUS 2.0 server
> unless the client first successfully performs a 'selfupdate' of the
> Windows Update Agent to upgrade it from the v5.4 client that's packaged in
> XP SP2 to the v5.8 client that's required for use with WSUS 2.0
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>