This Computer has not reported status yet

On 31 Jul, 17:02, DaveMills <DaveMi...@newsgroup.nospam> wrote:
> Looks to me like the client is not talking to the server at all. Since you have
> editing all the server name and ip addresses you may have edited out the cause
> of the problem. Quite often the problem is because of an incorrect server
> specification in the GPO, an extra dot or some other simple error like a
> trailing \
> It also looks like the WSUS client is trying to use a proxy. Is the bypass IP
> mask correct.
>
> The client has not updated to WSUS 3
>
>
>
>
>
> On Thu, 31 Jul 2008 03:22:18 -0700 (PDT), jwc...@gmail.com wrote:
> >On Jul 31, 11:15 am, jwc...@gmail.com wrote:
> >> On Jul 30, 10:35 pm, "Lawrence Garvin" <ons...@postalias.news> wrote:
>
> >> > "jeps" <j...@discussions.microsoft.com> wrote in message
>
> >> >news:5EBC6056-B9AD-49B8-85EE-BC67D6FBB255@microsoft.com...
>
> >> > >I have the same problem "has not reported status yet". I have search all
> >> > >the
> >> > > froums and no one has an answer. IS there an answer from Microsoft?
>
> >> > "Has not reported status yet" generally means that something is broken on
> >> > the client side.
>
> >> > Next step is to inspect the WindowsUpdate.log for error messages that
> >> > provide additional details.
>
> >> > --
> >> > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> >> > Senior Data Architect, APQC, Houston, Texas
> >> > Microsoft MVP - Software Distribution (2005-2008)
>
> >> > MS WSUS Website:http://www.microsoft.com/wsus
> >> > My Websites:http://www.onsitechsolutions.com;htt...hsolutions.com
> >> > My MVP Profile:http://mvp.support.microsoft.com/pro...awrence.Garvin
>
> >> HEreis the log
>
> >> 2008-07-31 10:28:21+0100 1176 4a8 PT: Using serverID {3DA21691-
> >> E39D-4DA6-8A4B-B43877BCB1B7}
> >> 2008-07-31 10:28:21+0100 1176 4a8 Failedto obtain cached cookie with
> >> hr = 80248008.
> >> 2008-07-31 10:28:21+0100 1176 4a8 Failedto upload events with hr =
> >> 80248008.
> >> 2008-07-31 10:33:21+0100 3252 63c Out ofproc datastore is shutting
> >> down
> >> 2008-07-31 10:33:22+0100 3252 63c Out ofproc datastore is now
> >> inactive
> >> 2008-07-31 10:38:21+0100 1176 bf4 Successfully opened event cache file
> >> at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
> >> DA9354B01DE5}.bin for reading.
> >> 2008-07-31 10:38:21+0100 132 404 Trying to make out of proc datastore
> >> active
> >> 2008-07-31 10:38:22+0100 132 404 Out of proc datastore is now active
> >> 2008-07-31 10:38:22+0100 1176 bf4 PT: Using serverID {3DA21691-
> >> E39D-4DA6-8A4B-B43877BCB1B7}
> >> 2008-07-31 10:38:22+0100 1176 bf4 Failedto obtain cached cookie with
> >> hr = 80248008.
> >> 2008-07-31 10:38:22+0100 1176 bf4 Failedto upload events with hr =
> >> 80248008.
> >> 2008-07-31 10:40:10+0100 1176 49c Service received connect
> >> notification
> >> 2008-07-31 10:40:10+0100 1176 cc8 AU received event of 3
> >> 2008-07-31 10:40:18+0100 1176 49c Service received disconnect
> >> notification
> >> 2008-07-31 10:40:18+0100 1176 cc8 AU received event of 3
> >> 2008-07-31 10:40:18+0100 1176 49c Service received connect
> >> notification
> >> 2008-07-31 10:40:18+0100 1176 cc8 AU received event of 3
> >> 2008-07-31 10:40:19+0100 1176 49c Service received logon notification
> >> 2008-07-31 10:40:19+0100 1176 cc8 AU received event of 3
> >> 2008-07-31 10:40:53+0100 3376 808 CreateObject for
> >> Microsoft.Update.AgentInfo failed: error 0x800401f3
> >> 2008-07-31 10:40:53+0100 1176 544 WU client succeeds
> >> CClientCallRecorder::EnumerateService
> >> 2008-07-31 10:45:53+0100 132 404 Out of proc datastore is shutting
> >> down
> >> 2008-07-31 10:45:54+0100 132 404 Out of proc datastore is now
> >> inactive
> >> 2008-07-31 10:48:22+0100 1176 77c Successfully opened event cache file
> >> at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
> >> DA9354B01DE5}.bin for reading.
> >> 2008-07-31 10:48:22+0100 2096 4ac Tryingto make out of proc datastore
> >> active
> >> 2008-07-31 10:48:22+0100 2096 4ac Out ofproc datastore is now active
> >> 2008-07-31 10:48:22+0100 1176 77c PT: Using serverID {3DA21691-
> >> E39D-4DA6-8A4B-B43877BCB1B7}
> >> 2008-07-31 10:48:22+0100 1176 77c Failedto obtain cached cookie with
> >> hr = 80248008.
> >> 2008-07-31 10:48:22+0100 1176 77c Failedto upload events with hr =
> >> 80248008.
> >> 2008-07-31 10:53:22+0100 2096 4ac Out ofproc datastore is shutting
> >> down
> >> 2008-07-31 10:53:24+0100 2096 4ac Out ofproc datastore is now
> >> inactive
> >> 2008-07-31 10:58:22+0100 1176 77c Successfully opened event cache file
> >> at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
> >> DA9354B01DE5}.bin for reading.
> >> 2008-07-31 10:58:23+0100 3688 ddc Tryingto make out of proc datastore
> >> active
> >> 2008-07-31 10:58:23+0100 3688 ddc Out ofproc datastore is now active
> >> 2008-07-31 10:58:23+0100 1176 77c PT: Using serverID {3DA21691-
> >> E39D-4DA6-8A4B-B43877BCB1B7}
> >> 2008-07-31 10:58:23+0100 1176 77c Failedto obtain cached cookie with
> >> hr = 80248008.
> >> 2008-07-31 10:58:23+0100 1176 77c Failedto upload events with hr =
> >> 80248008.
> >> 2008-07-31 11:03:23+0100 3688 ddc Out ofproc datastore is shutting
> >> down
> >> 2008-07-31 11:03:24+0100 3688 ddc Out ofproc datastore is now
> >> inactive
> >> 2008-07-31 11:08:23+0100 1176 da4 Successfully opened event cache file
> >> at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
> >> DA9354B01DE5}.bin for reading.
> >> 2008-07-31 11:08:23+0100 4060 ab4 Tryingto make out of proc datastore
> >> active
> >> 2008-07-31 11:08:24+0100 4060 ab4 Out ofproc datastore is now active
> >> 2008-07-31 11:08:24+0100 1176 da4 PT: Using serverID {3DA21691-
> >> E39D-4DA6-8A4B-B43877BCB1B7}
> >> 2008-07-31 11:08:24+0100 1176 da4 Failedto obtain cached cookie with
> >> hr = 80248008.
> >> 2008-07-31 11:08:24+0100 1176 da4 Failedto upload events with hr =
> >> 80248008.
>
> >> here is Client Diag
> >> WSUS Client Diagnostics Tool
>
> >> Checking Machine State
> >> Checking for admin rights to run tool . . . . . . . . .. PASS
> >> Automatic Updates Service is running. . . . . . . . . .. PASS
> >> Background Intelligent Transfer Service is running. . .. PASS
> >> Wuaueng.dll version 5.4.3790.5512 . . . . . . . . . . .. PASS
> >> This version is WSUS 2.0
>
> >> Checking AU Settings
> >> AU Option is 3 : Notify Prior to Install. . . . . . . .. PASS
> >> Option is from Policy settings
>
> >> Checking Proxy Configuration
> >> Checking for winhttp local machine Proxy settings . . .. PASS
> >> Winhttp local machine access type
> >> <Using Proxy>
> >> Winhttp local machine Proxy
> >> xxxxxxxx
> >> Winhttp local machine ProxyBypass
> >> :8080
> >> Checking User IE Proxy settings . . . . . . . . . . . .. PASS
> >> User IE Proxy
> >> http=192.xxx.x.xx:8080;https=192.xxx.x..xx:
> >> 8080;ftp=192.xxx.x.
> >> 8080;gopher=192.xxx.x.xx:8080
> >> User IE ProxyByPass
> >> 192.168.0.*;<local>
> >> User IE AutoConfig URL Proxy . . . . .. . . . NONE
> >> User IE AutoDetect
> >> AutoDetect not in use
>
> >> Checking Connection to WSUS/SUS Server
> >> WUServer =http://xxxxxxx
> >> WUStatusServer =http://xxxxxx
> >> UseWuServer is enabled. . . . . . . . . . . . . . . . .. PASS
> >> Connection to server. . . . . . . . . . . . . . . . . .. PASS
> >> SelfUpdate folder is present. . . . . . . . . . . . . .. PASS- Hide quoted text -
>
> >> - Show quoted text -
>
> >The Client Diag show Wuaueng.dll version
> >5.4.3790.5512 . . . . . . . . . . . PASS
> > This version is WSUS 2.0
>
> >IS this coreect but I am using WSUS3.0
>
> >Jeremy
>
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that don't.- Hide quoted text -
>
> - Show quoted text -

Dear Dave

You can see they are all passes. The clients are showing up in the
WSUS as orange traiagles and red circles. SO they must be touching
base with WSUS.
The setup is WSUS 3 is runnig on a Windows 2003 Server Sp2. The Proxy
server is on the same server.

Thansk
Jeremy

jwchoo@gmail.com wrote:

>>> Checking Proxy Configuration
>>> Checking for winhttp local machine Proxy settings . . . PASS
>>> Winhttp local machine access type
>>> <Using Proxy>
>>> Winhttp local machine Proxy
>>> xxxxxxxx
>>> Winhttp local machine ProxyBypass
>>> :8080

> The Wsus is also the proxy server. But isn't the proxy being by passed
> for local networks.

The ProxyBypass setting has nothing in it but :8080. I'm no expert in Winhttp
proxy settings, but that certainly doesn't look right if you're expecting it to
bypass the local network.

It would help if you could post the actual output. But perhaps if you look at
these settings, particularly if you compare them to one on a machine that is
working, the problem may be obvious.

... you realise the Winhttp settings are distinct from the user settings? For
everything to work properly, both have to be set correctly, but the Winhttp
settings are the ones relevant to the errors appearing in the log.

Harry.

--
Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174

On Thu, 31 Jul 2008 16:21:46 -0700 (PDT), jwchoo@gmail.com wrote:


>> - Show quoted text -
>
>Dear Dave
>
>You can see they are all passes. The clients are showing up in the
>WSUS as orange traiagles and red circles. SO they must be touching
>base with WSUS.
>The setup is WSUS 3 is runnig on a Windows 2003 Server Sp2. The Proxy
>server is on the same server.
Will the Proxy server know that it should not forward HTTP requests to itself to
the Internet?
>
>Thansk
>Jeremy
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

On Thu, 31 Jul 2008 16:11:02 -0700 (PDT), jwchoo@gmail.com wrote:

>On 31 Jul, 21:16, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz>
>wrote:
>> jwc...@gmail.com wrote:
>> > Checking Proxy Configuration
>> > Checking for winhttp local machine Proxy settings . . . PASS
>> > Winhttp local machine access type
>> > <Using Proxy>
>> > Winhttp local machine Proxy
>> > xxxxxxxx
>> > Winhttp local machine ProxyBypass
>> > :8080
>>
>> Given these settings, the WUA will be trying to access the WSUS server via the
>> proxy. Might the proxy be blocking access?

If you are thinking of the IE setting "Bypass Proxy Server for local addresses"
then you need to be aware that "local" means addresses without a ".", i.e.
192.168.1.2 is NOT local because it has a dot.
>>
>> Harry.
>>
>> --
>> Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174
>
>Hi Harry
>The Wsus is also the proxy server. But isn't the proxy being by passed
>for local networks. All the clients are showing up with the orange
>triangle except for 2 showing the red round symbol with a cross when
>hightlighted it says not reported status for 289 or more days and 189
>or more days respectively. So they must be able to contact the wsus. I
>do not understand why the proxy is blocking access.
>
>Jeremy
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

On 1 Aug, 04:14, DaveMills <DaveMi...@newsgroup.nospam> wrote:
> On Thu, 31 Jul 2008 16:11:02 -0700 (PDT), jwc...@gmail.com wrote:
> >On 31 Jul, 21:16, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz>
> >wrote:
> >> jwc...@gmail.com wrote:
> >> > Checking Proxy Configuration
> >> > Checking for winhttp local machine Proxy settings . .. . PASS
> >> > Winhttp local machine access type
> >> > <Using Proxy>
> >> > Winhttp local machine Proxy
> >> > xxxxxxxx
> >> > Winhttp local machine ProxyBypass
> >> > :8080
>
> >> Given these settings, the WUA will be trying to access the WSUS servervia the
> >> proxy. Might the proxy be blocking access?
>
> If you are thinking of the IE setting "Bypass Proxy Server for local addresses"
> then you need to be aware that "local" means addresses without a ".", i.e..
> 192.168.1.2 is NOT local because it has a dot.
>
> >> Harry.
>
> >> --
> >> Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174
>
> >Hi Harry
> >The Wsus is also the proxy server. But isn't the proxy being by passed
> >for local networks. All the clients are showing up with the orange
> >triangle except for 2 showing the red round symbol with a cross when
> >hightlighted it says not reported status for 289 or more days and 189
> >or more days respectively. So they must be able to contact the wsus. I
> >do not understand why the proxy is blocking access.
>
> >Jeremy
>
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that don't.

I have run test below and passed test. There is conectivity to WSUS.

To check network connectivity on the WSUS client computer

1. Click Start, and then click Run.

2. In the Open box, type iexplore and then press ENTER

3. In the Internet Explorer Address bar, type:

http://WSUSServerName/iuident.cab

where WSUS server name is the name of your WSUS server. Ensure that
you are prompted to download or open Iuident.cab. This verifies
network connectivity from the WSUS client and the availability of the
Iuident.cab file on the WSUS server.

Jeremy

Try resetting the winhttp proxy setting to those of IE using

cfgproxy -u

On Fri, 1 Aug 2008 17:49:28 -0700 (PDT), jwchoo@gmail.com wrote:

>>
>> --
>> Dave Mills
>> There are 10 type of people, those that understand binary and those that don't.
>
>I have run test below and passed test. There is conectivity to WSUS.
>
>To check network connectivity on the WSUS client computer
>
> 1. Click Start, and then click Run.
>
>2. In the Open box, type iexplore and then press ENTER
>
>3. In the Internet Explorer Address bar, type:
>
>http://WSUSServerName/iuident.cab
>
>where WSUS server name is the name of your WSUS server. Ensure that
>you are prompted to download or open Iuident.cab. This verifies
>network connectivity from the WSUS client and the availability of the
>Iuident.cab file on the WSUS server.
>
>Jeremy
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

jwchoo@gmail.com wrote:

> I have run test below and passed test. There is conectivity to WSUS.

This only tests connectivity in *your* context. It doesn't test connectivity in
the *WinHttp* context, which has different proxy settings configured per your
earlier post.

Dave's suggestion sounds like your best bet.

Harry.

--
Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174

Hi All,

NOTE 1
~~~~~
I have had this problem and been at it for nearly three weeks,. MS has found
that there was a problem with a DDL in WSUS. Go to
http://support.microsoft.com/kb/954960. There you will find a hotfix that
replaces dll file
%ProgramFiles%\Update
Services\WebServices\ClientWebService\bin\Microsoft.UpdateServices.WebServices.Client.Dll.
Click the Version tab. The file version is 3.1.6001.66 is the new version.

NOTE 2
~~~~~
The clientdiag.exe tool does not work on a Windows x64 computer. To fix this
add the following subkey

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

The tool will now work and allow you to troubleshoot any problems.

I tried all the recommendations in this post and many others. None worked
but this hotfix which was released only 5 days ago did the trick.




--
Joseph Rinaldi
Clarius Group Ltd


"Harry Johnston [MVP]" wrote:

> jwchoo@gmail.com wrote:
>
> > I have run test below and passed test. There is conectivity to WSUS.
>
> This only tests connectivity in *your* context. It doesn't test connectivity in
> the *WinHttp* context, which has different proxy settings configured per your
> earlier post.
>
> Dave's suggestion sounds like your best bet.
>
> Harry.
>
> --
> Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174
>

Joseph Rinaldi wrote:

> NOTE 1
> ~~~~~
> I have had this problem and been at it for nearly three weeks,. MS has found
> that there was a problem with a DDL in WSUS. Go to
> http://support.microsoft.com/kb/954960.

This isn't the same problem that jwchoo has.

Harry.

--
Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174

Hi Harry,

Are you sure? The problem I was getting was that a few computers were
appearing in WSUS but getting "This computer has not reported status yet".
It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and
then they all started to work.

jwchoo,

Can you please try the hotfix and see if it works for you?

Joseph Rinaldi

--
Joseph Rinaldi
Clarius Group Ltd


"Harry Johnston [MVP]" wrote:

> Joseph Rinaldi wrote:
>
> > NOTE 1
> > ~~~~~
> > I have had this problem and been at it for nearly three weeks,. MS has found
> > that there was a problem with a DDL in WSUS. Go to
> > http://support.microsoft.com/kb/954960.
>
> This isn't the same problem that jwchoo has.
>
> Harry.
>
> --
> Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174
>

Joseph Rinaldi wrote:

> Are you sure?

Yes. The superficial symptoms may be the same, but jwchoo's Windows Update log
shows no evidence of the problem you were having - it's failing at an earlier
point in the process.

> jwchoo,
>
> Can you please try the hotfix and see if it works for you?

Well, it won't do any harm, assuming he is running WSUS 3 service pack 1.

Harry.

--
Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174

On Aug 5, 11:03 pm, Joseph Rinaldi
<JosephRina...@discussions.microsoft.com> wrote:
> Hi Harry,
>
> Are you sure? The problem I was getting was that a few computers were
> appearing in WSUS but getting "This computer has not reported status yet"..
> It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and
> then they all started to work.
>
> jwchoo,
>
> Can you please try the hotfix and see if it works for you?
>
> Joseph Rinaldi
>
> --
> Joseph Rinaldi
> Clarius Group Ltd
>
>
>
> "Harry Johnston [MVP]" wrote:
> > Joseph Rinaldi wrote:
>
> > > NOTE 1
> > > ~~~~~
> > > I have had this problem and been at it for nearly three weeks,. MS has found
> > > that there was a problem with a DDL in WSUS. Go to
> > >http://support.microsoft.com/kb/954960.
>
> > This isn't the same problem that jwchoo has.
>
> > Harry.
>
> > --
> > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174-Hide quoted text -
>
> - Show quoted text -

Hi Joseph/Harry/David

I am happy to report I have got it working. Clients are reporting and
getting updates. The only issue now is they are not populating the
WSUS Computer Groups as in GP OUs. I followed instructions from
http://kbalertz.com/920659/Microsoft...c-updates.aspx.
To summarise what I have done:-
1. check the correct level of permission, ISUR_IISserver user for all
the relevant folders. and anonynous user is checked on the Default
Website.
2. IP address is Unassign for Default website

Thank for all the help
Jeremy

On Aug 8, 12:03 am, jwc...@gmail.com wrote:
> On Aug 5, 11:03 pm, Joseph Rinaldi
>
>
>
>
>
> <JosephRina...@discussions.microsoft.com> wrote:
> > Hi Harry,
>
> > Are you sure? The problem I was getting was that a few computers were
> > appearing in WSUS but getting "This computer has not reported status yet".
> > It had been ongoing for about 3 weeks. I installed the hotfix KB954960,and
> > then they all started to work.
>
> > jwchoo,
>
> > Can you please try the hotfix and see if it works for you?
>
> > Joseph Rinaldi
>
> > --
> > Joseph Rinaldi
> > Clarius Group Ltd
>
> > "Harry Johnston [MVP]" wrote:
> > > Joseph Rinaldi wrote:
>
> > > > NOTE 1
> > > > ~~~~~
> > > > I have had this problem and been at it for nearly three weeks,. MS has found
> > > > that there was a problem with a DDL in WSUS. Go to
> > > >http://support.microsoft.com/kb/954960.
>
> > > This isn't the same problem that jwchoo has.
>
> > > Harry.
>
> > > --
> > > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174-Hide quoted text -
>
> > - Show quoted text -
>
> Hi Joseph/Harry/David
>
> I am happy to report I have got it working. Clients are reporting and
> getting updates. The only issue now is they are not populating the
> WSUS Computer Groups as in GP OUs. I followed instructions fromhttp://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S....
> To summarise what I have done:-
> 1. check the correct level of permission, ISUR_IISserver user for all
> the relevant folders. and anonynous user is checked on the Default
> Website.
> 2. IP address is Unassign for Default website
>
> Thank for all the help
> Jeremy- Hide quoted text -
>
> - Show quoted text -

I also started WHTTP web proxy service. I am not sure it is necessary.

Jeremy

On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwchoo@gmail.com wrote:


>I am happy to report I have got it working. Clients are reporting and
>getting updates. The only issue now is they are not populating the
>WSUS Computer Groups as in GP OUs.
Two possibilities:
1) The client is not being told which group to use in the GPO or the spelling of
the group does not match that is WSUS console.
2) The WSUS server is not set to use Client Side Targeting.


> I followed instructions from
>http://kbalertz.com/920659/Microsoft...c-updates.aspx.
>To summarise what I have done:-
>1. check the correct level of permission, ISUR_IISserver user for all
>the relevant folders. and anonynous user is checked on the Default
>Website.
>2. IP address is Unassign for Default website
>
>Thank for all the help
>Jeremy
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

On Aug 8, 5:08 am, DaveMills <DaveMi...@newsgroup.nospam> wrote:
> On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote:
> >I am happy to report I have got it working. Clients are reporting and
> >getting updates. The only issue now is they are not populating the
> >WSUS Computer Groups as in GP OUs.
>
> Two possibilities:
> 1) The client is not being told which group to use in the GPO or the spelling of
> the group does not match that is WSUS console.
> 2) The WSUS server is not set to use Client Side Targeting.
>
> > I followed instructions from
> >http://kbalertz.com/920659/Microsoft...ate-Services-S.....
> >To summarise what I have done:-
> >1. check the correct level of permission, ISUR_IISserver user for all
> >the relevant folders. and anonynous user is checked on the Default
> >Website.
> >2. IP address is Unassign for Default website
>
> >Thank for all the help
> >Jeremy
>
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that don't.

Dave

I have Client side targeting setup. The OUs are nested like
1. Client systems\XP\Workstations
2. Client systems\XP\Laptops

How do I name them in GP ?

Jeremy