Um, nope, all that gives me is the server name, not the client PC connecting
to the server. This was the whole reason we tested on IIS 6.0, since the
attribute for cs-host is included (assumed this meant the PC that was
requesting). Both servers are member servers, not attached to a domain
(stuck in workgroup). I was wondering if it may be a function of DNS not
providing the correct PC name. We really want to move forward with this, as
we have 3,500 PC's that could really use the patch just in our division. We
just need a better tool to see what PC's are patched with what patch. How
do we get on the beta list for SUS 2.0?
"Chris Adams (MSFT)" <chrisad.RemoveThis@online.microsoft.com> wrote in message
news:O4aREgBlDHA.708@TK2MSFTNGP10.phx.gbl...
> Hello ~
>
> Yes, it is very possible. All you simply need to do is enable the
extended
> logging property for server name.
>
> In IIS Manager, right click the website and choose properties-
> On the Website tab, click Properties on Enable Logging
> Click Extended Properties
> Enable Server Name
>
> HTH,
>
>
> --
> ~Chris (MSFT)
> IIS Supportability Lead
>
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
> "pelizdr" <dpelizzari.RemoveThis@howmet.com> wrote in message
> news:%23SUQyOBlDHA.2268@TK2MSFTNGP12.phx.gbl...
> > Is there any way to modify IIS (in layman's terms) to capture the name
of
> > the PC getting updated, instead of using the IP address? We use DHCP,
so
> > the addresses change on a frequent basis, and capturing the IP is almost
> > pointless. We are running SUS server on Win2K Server and Win2K3 Web,
> > neither seems able to capture the PC name. Any help would be greatly
> > appreciated.
> >
> >
> >
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IIS logs capturing PC name