Error 80244019

I can't seem to get WSUS 3.1 to work.
I was working on it for months at the customer, but this is only once or
twice a month.
I finally installed SBS 2003 R2 on a spare box at home and have
duplicated the problem.
No computers show up in the WSUS console.
I think I have the GPO correct, at least the settings show up in the
server and XP box registry. I'm not sure if I did the linking correctly.
The first thing I see is around log line 30 (or so)
I added blank lines around it.
My searching for the 80244019 seems to point to IIS setup, but all the
links I read seemed to be OK.
I also do not know IIS so maybe I missed something.
I have WSUS 3.0 at the customer and 3.1 at home.
There was one link indicating a DNS problem, but the server can resolve
the servers name and the FQDN of the server.
I see the 404 error in the line also.
Any ideas where I am going wrong?

TIA
Rich W.


2009-09-13 18:15:02:765 1384 288 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0400) ===========
2009-09-13 18:15:02:812 1384 288 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-09-13 18:15:02:812 1384 288 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-09-13 18:15:02:765 1384 288 Service *************
2009-09-13 18:15:02:812 1384 288 Service ** START ** Service: Service
startup
2009-09-13 18:15:02:812 1384 288 Service *********
2009-09-13 18:15:14:359 1384 288 Agent * WU client version 7.2.6001.788
2009-09-13 18:15:14:406 1384 288 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-09-13 18:15:14:406 1384 288 Agent * Access type: No proxy
2009-09-13 18:15:14:484 1384 288 Agent * Network state: Connected
2009-09-13 18:16:04:303 1384 288 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-09-13 18:16:04:303 1384 288 Agent *********** Agent: Initializing
global settings cache ***********
2009-09-13 18:16:04:303 1384 288 Agent * WSUS server:
http://sbs03r2.testbox.local
2009-09-13 18:16:04:303 1384 288 Agent * WSUS status server:
http://sbs03r2.testbox.local
2009-09-13 18:16:04:303 1384 288 Agent * Target group: WSUS
2009-09-13 18:16:04:303 1384 288 Agent * Windows Update access
disabled: No
2009-09-13 18:16:04:319 1384 288 DnldMgr Download manager restoring 0
downloads
2009-09-13 18:16:04:616 1384 288 AU ########### AU: Initializing
Automatic Updates ###########
2009-09-13 18:16:04:694 1384 288 AU # WSUS server:
http://sbs03r2.testbox.local
2009-09-13 18:16:04:694 1384 288 AU # Detection frequency: 22
2009-09-13 18:16:04:694 1384 288 AU # Target group: WSUS
2009-09-13 18:16:04:694 1384 288 AU # Approval type: Pre-install
notify (Policy)
2009-09-13 18:16:04:694 1384 288 AU # Auto-install minor updates: Yes
(Policy)
2009-09-13 18:16:04:694 1384 288 AU # Will interact with non-admins
(Non-admins are elevated)
2009-09-13 18:16:04:912 1384 288 AU AU finished delayed initialization
2009-09-13 18:16:04:912 1384 288 Report *********** Report:
Initializing static reporting data ***********
2009-09-13 18:16:04:912 1384 288 Report * OS Version = 5.2.3790.1.0.131377
2009-09-13 18:16:05:662 1384 288 Report * Computer Brand = System
manufacturer
2009-09-13 18:16:05:662 1384 288 Report * Computer Model = P4V8X-MX
2009-09-13 18:16:05:756 1384 288 Report * Bios Revision = 080012
2009-09-13 18:16:05:756 1384 288 Report * Bios Name = Rev 1.00
2009-09-13 18:16:05:756 1384 288 Report * Bios Release Date =
2005-11-22T00:00:00
2009-09-13 18:16:05:756 1384 288 Report * Locale ID = 1033

2009-09-13 18:16:50:912 1384 d74 PT WARNING: GetConfig failure, error =
0x80244019, soap client error = 10, soap error code = 0, HTTP status
code = 404

2009-09-13 18:16:50:912 1384 d74 PT WARNING: PTError: 0x80244019
2009-09-13 18:16:50:912 1384 d74 PT WARNING: GetConfig_WithRecovery
failed: 0x80244019
2009-09-13 18:16:50:912 1384 d74 PT WARNING: RefreshConfig failed:
0x80244019
2009-09-13 18:16:50:912 1384 d74 PT WARNING: RefreshPTState failed:
0x80244019
2009-09-13 18:16:50:912 1384 d74 PT WARNING: PTError: 0x80244019
2009-09-13 18:16:50:943 1384 d74 Report WARNING: Reporter failed to
upload events with hr = 80244019.
2009-09-13 18:16:50:943 1384 d74 PT WARNING: GetConfig failure, error =
0x80244019, soap client error = 10, soap error code = 0, HTTP status
code = 404
2009-09-13 18:16:50:943 1384 d74 PT WARNING: PTError: 0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: GetConfig_WithRecovery
failed: 0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: RefreshConfig failed:
0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: RefreshPTState failed:
0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: PTError: 0x80244019
2009-09-13 18:16:50:943 1384 d74 Report WARNING: Reporter failed to
upload events with hr = 80244019.
2009-09-13 18:16:50:943 1384 d74 PT WARNING: GetConfig failure, error =
0x80244019, soap client error = 10, soap error code = 0, HTTP status
code = 404
2009-09-13 18:16:50:943 1384 d74 PT WARNING: PTError: 0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: GetConfig_WithRecovery
failed: 0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: RefreshConfig failed:
0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: RefreshPTState failed:
0x80244019
2009-09-13 18:16:50:943 1384 d74 PT WARNING: PTError: 0x80244019
2009-09-13 18:16:50:943 1384 d74 Report WARNING: Reporter failed to
upload events with hr = 80244019.

"Rich Wonneberger" <> wrote in message
news:...

Hi Rich...

There are a number of considerations to deploying WSUS in an SBS2003
environment.

First thing I'll do is direct you to two white papers you should be
intimately familiar with before attempting to deploy WSUS in an SBS2003
environment.

The first is the SBS team's answer to installing WSUS v3 on SBS2003.
http://www.microsoft.com/downloads/d...displaylang=en

The second is a paper I authored for the WSUS team discussing the same
scenarios.
http://download.microsoft.com/downlo...3_networks.doc


Along with that -- I would encourage you to first install WSUS v3 (and
preferably the SP2 release) on a standard edition Windows 2003 server, so
that you can see and learn how WSUS works in a simple environment, on the
platform it was designed for deployment on.

From there, you can then incorporate the various *variables* that are
present on an SBS2003 server, such as:
1. WSUS will always deploy to the alternate "WSUS Administration" website
(because WSS is on the Default Web Site).
2. SSL is enabled on the Default Web Site (to support Outlook Web Access).
3. Of particular note, the R2 Technologies installs WSUS v2 SP1, which means
you don't have a clean install of WSUS v3 on the SBS2003 R2 box -- you have
a convoluted upgrade of a heavily customized version of WSUS.
*** Unless you have some particular reason for installing the SBS R2
Technologies content, my recommendation is to not install it at all.
*** At a minimum you should manually uninstall WSUS2SP1 from the SBS2003R2
system, and confirm it has been completely removed from the platform
(including the custom MMC snap-in contained in the SBS Server Management
tool).
*** As of April, 2009, Windows Server 2003 =SP1= is no longer a supported
platform for any edition of Windows Server 2003, so you *must* install
Windows Server 2003 Service Pack 2 if you wish to obtain any updates for
the platform. (Updates released since April, 2009, will not detect as needed
on a Win2003SP1/SBS2003SP1/SBS2003R2
platform.)

In addition, since you're attempting to use the WSUS Server as the test
client, if you've created your own WSUS v3 GPO, you need to link it to the
"Domain Controllers" OU, which is where the SBS2003 server is located.

If you're attempting to use the R2 WSUS policies, you need to be aware that
those policy objects are heirarchical and incomplete, and the entire
R2/WSUS2 environment is based on a fair amount of "custom functionality"
built into the SBS Update Services custom service -- which includes
overriding some settings in those provided policy objects. Upgrading to
WSUSv3 on SBS2003R2 undoes (disables) that SBS Update Services custom
service, and makes those legacy R2 GPOs essentially dysfunctional.

The 0x80244019 error is an HTTP 404 error and it means the resource is not
available at the specified URL. On SBS2003 systems this most likely is
caused because the policy configured URL does not properly contain the port
suffix which is required on SBS2003 systems because WSUS is always installed
to the alternate v-root "WSUS Administration". The correct URL for a
WSUS-on-SBS environment is http://sbs_server_name:8530

So.. looking at this log. . .

> 2009-09-13 18:15:02:812 1384 288 Service *********
> 2009-09-13 18:15:14:359 1384 288 Agent * WU client version 7.2.6001.788

So we see from this that you've connected this test SBS server to Microsoft
Update at some point, as that's the only way to get the v7.2 client (unless
you manually deployed the WindowsUpdateAgent30-x86.exe package).


> 2009-09-13 18:16:04:303 1384 288 Agent * WSUS server:
> http://sbs03r2.testbox.local
> 2009-09-13 18:16:04:303 1384 288 Agent * WSUS status server:
> http://sbs03r2.testbox.local

And here we see the URL is missing the port 8530 suffix.
The correct URL should be http://sbs03r2.testbox.local:8530


> 2009-09-13 18:16:04:912 1384 288 Report * OS Version =
> 5.2.3790.1.0.131377

Confirmation that SP2 is not installed on this machine: v5.2.3790.1 is a
Windows Server 2003 SP1 build number.


> 2009-09-13 18:16:50:912 1384 d74 PT WARNING: GetConfig failure, error =
> 0x80244019, soap client error = 10, soap error code = 0, HTTP status code
> = 404

And this is an HTTP 404 error because the /ClientWebService cannot be
accessed in the Default Web Site of the SBS/WSUS server (due to the missing
port suffix on the configured URL).


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence,

Thank you for the 2 links, I will print them out tomorrow at work.

The reason I installed SBS 2003 R3 is I can not find SBS 2003 files from
Technet d-load. I thought it might be better to use SBS 2003 as that is
what the client is running.
I can install Server 2003 if you think it will get me on the right track.


See in line replies:


Lawrence Garvin [MVP] wrote:
> "Rich Wonneberger" <> wrote in message
> news:...
>
> Hi Rich...
>
> There are a number of considerations to deploying WSUS in an SBS2003
> environment.
>
> First thing I'll do is direct you to two white papers you should be
> intimately familiar with before attempting to deploy WSUS in an SBS2003
> environment.
>
> The first is the SBS team's answer to installing WSUS v3 on SBS2003.
> http://www.microsoft.com/downloads/d...displaylang=en
>
>
> The second is a paper I authored for the WSUS team discussing the same
> scenarios.
> http://download.microsoft.com/downlo...3_networks.doc
>
>
>
> Along with that -- I would encourage you to first install WSUS v3 (and
> preferably the SP2 release) on a standard edition Windows 2003 server,
> so that you can see and learn how WSUS works in a simple environment, on
> the platform it was designed for deployment on.
>
> From there, you can then incorporate the various *variables* that are
> present on an SBS2003 server, such as:
> 1. WSUS will always deploy to the alternate "WSUS Administration"
> website (because WSS is on the Default Web Site).

I was reading something about if there was already 2 websites on the server.

> 2. SSL is enabled on the Default Web Site (to support Outlook Web Access).
If I did not set WSUS to use SSL could that be the problem?

> 3. Of particular note, the R2 Technologies installs WSUS v2 SP1, which
> means you don't have a clean install of WSUS v3 on the SBS2003 R2 box --
> you have a convoluted upgrade of a heavily customized version of WSUS.
> *** Unless you have some particular reason for installing the SBS R2
> Technologies content, my recommendation is to not install it at all.
> *** At a minimum you should manually uninstall WSUS2SP1 from the
> SBS2003R2 system, and confirm it has been completely removed from the
> platform (including the custom MMC snap-in contained in the SBS Server
> Management tool).
> *** As of April, 2009, Windows Server 2003 =SP1= is no longer a
> supported platform for any edition of Windows Server 2003, so you *must*
> install Windows Server 2003 Service Pack 2 if you wish to obtain any
> updates for the platform. (Updates released since April, 2009, will not
> detect as needed on a Win2003SP1/SBS2003SP1/SBS2003R2
> platform.)

Hmm. I took a shortcut here (only on the test box)
I did not install the above s-packs for this testing.
My first install of R2 I went to Windows Update (on line) and let it
install the updates.
Was not a pretty picture.
When it was all installed I had SQL errors and WSUS service had to be
started manually on each re-boot.
Could not find much on the error code and just re-installed R2 again.
(it has been re-installed a few times over the last few months)


>
> In addition, since you're attempting to use the WSUS Server as the test
> client, if you've created your own WSUS v3 GPO, you need to link it to
> the "Domain Controllers" OU, which is where the SBS2003 server is located.
I found a doc on line for how to configure the link.
I think I got it right as the server does not have access to Windows
Update any more. I think the policies are being pushed to the server.
I has the update server as http://sbs2003r2 at first, then added the
..testbox.local to the policy. Re-booting the server and it shows up in
the log I provided.
I should add the :8530 to that?


>
> If you're attempting to use the R2 WSUS policies, you need to be aware
> that those policy objects are heirarchical and incomplete, and the
> entire R2/WSUS2 environment is based on a fair amount of "custom
> functionality" built into the SBS Update Services custom service --
> which includes overriding some settings in those provided policy
> objects. Upgrading to WSUSv3 on SBS2003R2 undoes (disables) that SBS
> Update Services custom service, and makes those legacy R2 GPOs
> essentially dysfunctional.
>
> The 0x80244019 error is an HTTP 404 error and it means the resource is
> not available at the specified URL. On SBS2003 systems this most likely
> is caused because the policy configured URL does not properly contain
> the port suffix which is required on SBS2003 systems because WSUS is
> always installed to the alternate v-root "WSUS Administration". The
> correct URL for a WSUS-on-SBS environment is http://sbs_server_name:8530
>
> So.. looking at this log. . .
>
>> 2009-09-13 18:15:02:812 1384 288 Service *********
>> 2009-09-13 18:15:14:359 1384 288 Agent * WU client version 7.2.6001.788
>
> So we see from this that you've connected this test SBS server to
> Microsoft Update at some point, as that's the only way to get the v7.2
> client (unless you manually deployed the WindowsUpdateAgent30-x86.exe
> package).
>
>
>> 2009-09-13 18:16:04:303 1384 288 Agent * WSUS server:
>> http://sbs03r2.testbox.local
>> 2009-09-13 18:16:04:303 1384 288 Agent * WSUS status server:
>> http://sbs03r2.testbox.local
>
> And here we see the URL is missing the port 8530 suffix.
> The correct URL should be http://sbs03r2.testbox.local:8530

I tried http://sbs03r2:8530 in a browser and get a no permission message.
A few of the links I found in Google indicated checking something in IIS
to allow anonymous access to the WSUS web site.
I will have to re-check this. I'm not that familiar with IIS


>
>
>> 2009-09-13 18:16:04:912 1384 288 Report * OS Version =
>> 5.2.3790.1.0.131377
>
> Confirmation that SP2 is not installed on this machine: v5.2.3790.1 is a
> Windows Server 2003 SP1 build number.

Can I just install Server 2003 SP1 and SBS 2003 SP2 or should I do the
Exchange SP as well? (if needed)

>
>
>> 2009-09-13 18:16:50:912 1384 d74 PT WARNING: GetConfig failure, error
>> = 0x80244019, soap client error = 10, soap error code = 0, HTTP status
>> code = 404
>
> And this is an HTTP 404 error because the /ClientWebService cannot be
> accessed in the Default Web Site of the SBS/WSUS server (due to the
> missing port suffix on the configured URL).
>

Thanks again
Rich W.

"Rich Wonneberger" <> wrote in message
news:...
> Lawrence,
>
> Thank you for the 2 links, I will print them out tomorrow at work.
>
> The reason I installed SBS 2003 R3 is I can not find SBS 2003 files from
> Technet d-load. I thought it might be better to use SBS 2003 as that is
> what the client is running.
> I can install Server 2003 if you think it will get me on the right track.

I would recommend installing on a freshly installed Win Server 2003 Std
Edition SP2 as your first exercise. A Virtual Machine is a great way to do
this. In this way you can see what the product does in an uncomplicated
environment.

>> 1. WSUS will always deploy to the alternate "WSUS Administration" website
>> (because WSS is on the Default Web Site).
>
> I was reading something about if there was already 2 websites on the
> server.

Yeah... that's a confusing (and somewhat useless note)... what it means is
if there are multiple logical *SITES* running within the same IIS Virtual
Server -- like might be the case if you installed Windows Sharepoint
Services *and* Outlook Web Access in the same IIS virtual server.

>> 2. SSL is enabled on the Default Web Site (to support Outlook Web
>> Access).

> If I did not set WSUS to use SSL could that be the problem?

No. The WSUS installation on the Default Web Site of SBS must not use SSL.
The concern comes in verifying that the Default Web Site v-root properties
and the selfupdate v-dir properties are verified to not require SSL.

> I had the update server as http://sbs2003r2 at first, then added the
> .testbox.local to the policy. Re-booting the server and it shows up in
> the log I provided.
> I should add the :8530 to that?

Yes.

>> And here we see the URL is missing the port 8530 suffix.
>> The correct URL should be http://sbs03r2.testbox.local:8530
>
> I tried http://sbs03r2:8530 in a browser and get a no permission message.

That's *normal*. There is *no* web browsable content in a WSUS installation
(with the exception of the web services message configured for the
SimpleAuth.asmx web service).

> A few of the links I found in Google indicated checking something in IIS
> to allow anonymous access to the WSUS web site.
> I will have to re-check this. I'm not that familiar with IIS

On the "WSUS Administration" v-root this should not be an issue, as WSUS
creates and correctly sets all of these permissions. On SBS, for the Default
Web Site, you'll need to confirm that Anonymous Access for the Default Web
Site has not been disabled, as well as the selfupdate v-dir (which is
probably not an issue since the WSUS installer also creates that).

In short, anything created by the WSUS installer should be good; the concern
is that the WSUS installer does not change/fix anything that might be
incorrect, which is why the config of the Default Web Site v-root is of
concern.

>> Confirmation that SP2 is not installed on this machine: v5.2.3790.1 is a
>> Windows Server 2003 SP1 build number.
>
> Can I just install Server 2003 SP1 and SBS 2003 SP2 or should I do the
> Exchange SP as well? (if needed)

There is no SBS "SP2". After installing SBS2003 (whatever version) simply
apply the "Windows Server 2003 Service Pack 2" update to the SBS server. For
WSUS testing purposes there is no need to apply application updates; but, of
course, for a production server you should install Exchange 2003 Service
Pack 2, Windows Sharepoint Services 2.0 Service Pack 3 or Windows Sharepoint
Services 3.0 Service Pack 2, SQL Server 2000 Service Pack 4 (for the
SBSMonitoring and WSS 2.0 MSDE database), Windows Internal Database Service
Pack 3 (for the WSS 3.0 Windows Internal Database and/or the WSUS 3.0
Windows Internal Database) and SQL Server 2005 Service Pack 3 (for SQL
Server 2005 Workgroup Edition - if installed on a Premium Edition server).


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence,

Making progress.
I added the :8530 to the server name and the server shows up in the WSUS
console.

Now the console shows a message "Computers have requested the following
nonexistent computer groups WSUS"
Do I need the cn=,ou=,ou= for the group pointer?
Is there a link I can read up on doing the GPO link to a OU??
I'm not sure if I have the link correct.

See inline:

Lawrence Garvin [MVP] wrote:
> "Rich Wonneberger" <> wrote in message
> news:...
>> Lawrence,
>>
>> Thank you for the 2 links, I will print them out tomorrow at work.
>>
Printed out & I will go over them before the weekend.

>> I had the update server as http://sbs2003r2 at first, then added the
>> .testbox.local to the policy. Re-booting the server and it shows up
>> in the log I provided.
>> I should add the :8530 to that?
>
> Yes.
Done and seems to be a step forward.

>
> There is no SBS "SP2". After installing SBS2003 (whatever version)
Sorry, got it backwards.

> simply apply the "Windows Server 2003 Service Pack 2" update to the SBS
> server. For WSUS testing purposes there is no need to apply application
> updates; but, of course, for a production server you should install
> Exchange 2003 Service Pack 2, Windows Sharepoint Services 2.0 Service
> Pack 3 or Windows Sharepoint Services 3.0 Service Pack 2, SQL Server
> 2000 Service Pack 4 (for the SBSMonitoring and WSS 2.0 MSDE database),
> Windows Internal Database Service Pack 3 (for the WSS 3.0 Windows
> Internal Database and/or the WSUS 3.0 Windows Internal Database) and SQL
> Server 2005 Service Pack 3 (for SQL Server 2005 Workgroup Edition - if
> installed on a Premium Edition server).
>
Tonight I installed Server 2003 SP2, Sharepoint SP3, and Exchange SP2.
My list indicated XP deploy SP2 (iIrr) next before SBS 2003 SP1.
Any preference to the order for SQL and internal database service packs?
The order you listed them in?

I think I may have to install Server SP2 at the client. The others I
mentioned above are up to date (iIrr)
The SQL and internal database updates have to be done as well.

I think I am close at getting things working now.

Thanks in advance
Rich W.

"Rich Wonneberger" <> wrote in message
news:...
> Lawrence,
>
> Making progress.
> I added the :8530 to the server name and the server shows up in the WSUS
> console.
>
> Now the console shows a message "Computers have requested the following
> nonexistent computer groups WSUS"

Have you created the Groups in the WSUS Admin console?

The message is indicating that the groups configured in policy for the
clients do not exist on the server. The clients cannot auto-create their
groups.


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

On Wed, 16 Sep 2009 08:08:45 -0500, "Lawrence Garvin [MVP]"
<> wrote:

>"Rich Wonneberger" <> wrote in message
>news:...
>> Lawrence,
>>
>> Making progress.
>> I added the :8530 to the server name and the server shows up in the WSUS
>> console.
>>
>> Now the console shows a message "Computers have requested the following
>> nonexistent computer groups WSUS"
>
>Have you created the Groups in the WSUS Admin console?
>
>The message is indicating that the groups configured in policy for the
>clients do not exist on the server. The clients cannot auto-create their
>groups.
To add a little. WSUS uses "Groups" and AD uses "Groups", they are not related
in any way. You may use Group Policy to set the "WSUS Group" and you may use "AD
Groups" to filter a GPO but the WSUS and AD "Groups" are different. They may
have the same name but that is just coincidence.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

Lawrence,

I added the port to the GPO and started a test box. (XP w/ sp2)
Before the test box booted I saw the server already was in the WSUS console.
Shortly after I had other PC's show up.

I did approve a bunch of security updates for XP & W2k (only a few W2k
boxes)

Didn't have a lot of time there today but I want things to run a while
before I make any other changes anyway.

Thank You for the help
Rich W.


Lawrence Garvin [MVP] wrote:
> "Rich Wonneberger" <> wrote in message
> news:...
>> Lawrence,
>>
>> Making progress.
>> I added the :8530 to the server name and the server shows up in the
>> WSUS console.
>>