SUSReports, SUS and WUS RC

Anyone know if SUSReports works with WUS RC?

I have SUS installed on a machine quite happily running on port 80,
along with a few other sub-webs on the same port.

Reading the WUS RC Deployment guide, I see I can install WUS on a second
port 8530, but will this interfere with the existing SUS local database?
And when it comes time to shutdown SUS and move WUS to port 80 (if I
actually have to?), will my other sites have to be affected?

On install, does WUS setup IIS with the secondry port (as required in my
case), or is that a pre-requisite ?

Cheers,

Adrian

Comments inline to your post...

"Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
news:...
> Anyone know if SUSReports works with WUS RC?

Don't know.

> I have SUS installed on a machine quite happily running on port 80, along
> with a few other sub-webs on the same port.
>
> Reading the WUS RC Deployment guide, I see I can install WUS on a second
> port 8530, but will this interfere with the existing SUS local database?
> And when it comes time to shutdown SUS and move WUS to port 80 (if I
> actually have to?), will my other sites have to be affected?

SUS and WSUS can coexist on the same box. However the only thing that you
have to keep in mind is that the "SelfUpdate" virtual web folder is going to
get replaced by the WSUS components. Has to be done since legacy AU clients
only know how to upgrade the AU client bits from port 80.

> On install, does WUS setup IIS with the secondry port (as required in my
> case), or is that a pre-requisite ?

The WSUS install will detect that SUS is installed and default to port 8530.
If SUS is not on the box, it will default to port 80. This is done to help
with migration strategies from SUS to WSUS. (e.g. you can import your
approvals from SUS to WSUS as WSUS cannot synchronize content against a SUS
server.)

Hi Adrian,
For more information on WSUS RC, check out http://www.wsuswiki.com

Good day,
Mohammed Athif Khaleel
MVP - SUS / WSUS
Windows Server Update Services Wiki
http://www.wsuswiki.com/Athifs
Tutorial: Patch Management with Microsoft Software Update Services
(SUS) - Part 1
http://www.2000trainers.com/article....eID=336&page=1

what happens to the other sub-webs that share port 80 though? would they
get affected?


neo [mvp outlook] wrote:
> Comments inline to your post...
>
> "Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
> news:...
>
>>Anyone know if SUSReports works with WUS RC?
>
>
> Don't know.
>
>
>>I have SUS installed on a machine quite happily running on port 80, along
>>with a few other sub-webs on the same port.
>>
>>Reading the WUS RC Deployment guide, I see I can install WUS on a second
>>port 8530, but will this interfere with the existing SUS local database?
>>And when it comes time to shutdown SUS and move WUS to port 80 (if I
>>actually have to?), will my other sites have to be affected?
>
>
> SUS and WSUS can coexist on the same box. However the only thing that you
> have to keep in mind is that the "SelfUpdate" virtual web folder is going to
> get replaced by the WSUS components. Has to be done since legacy AU clients
> only know how to upgrade the AU client bits from port 80.
>
>
>>On install, does WUS setup IIS with the secondry port (as required in my
>>case), or is that a pre-requisite ?
>
>
> The WSUS install will detect that SUS is installed and default to port 8530.
> If SUS is not on the box, it will default to port 80. This is done to help
> with migration strategies from SUS to WSUS. (e.g. you can import your
> approvals from SUS to WSUS as WSUS cannot synchronize content against a SUS
> server.)
>
>

I also assume that if WUS replaces the Selfupdate VW, then effectively
the SUS update would stop (until I had WUS working 100%) ?

Adrian Marsh (NNTP) wrote:
> what happens to the other sub-webs that share port 80 though? would they
> get affected?
>
>
> neo [mvp outlook] wrote:
>
>> Comments inline to your post...
>>
>> "Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
>> news:...
>>
>>> Anyone know if SUSReports works with WUS RC?
>>
>>
>>
>> Don't know.
>>
>>
>>> I have SUS installed on a machine quite happily running on port 80,
>>> along with a few other sub-webs on the same port.
>>>
>>> Reading the WUS RC Deployment guide, I see I can install WUS on a
>>> second port 8530, but will this interfere with the existing SUS local
>>> database? And when it comes time to shutdown SUS and move WUS to port
>>> 80 (if I actually have to?), will my other sites have to be affected?
>>
>>
>>
>> SUS and WSUS can coexist on the same box. However the only thing that
>> you have to keep in mind is that the "SelfUpdate" virtual web folder
>> is going to get replaced by the WSUS components. Has to be done since
>> legacy AU clients only know how to upgrade the AU client bits from
>> port 80.
>>
>>
>>> On install, does WUS setup IIS with the secondry port (as required in
>>> my case), or is that a pre-requisite ?
>>
>>
>>
>> The WSUS install will detect that SUS is installed and default to port
>> 8530. If SUS is not on the box, it will default to port 80. This is
>> done to help with migration strategies from SUS to WSUS. (e.g. you can
>> import your approvals from SUS to WSUS as WSUS cannot synchronize
>> content against a SUS server.)
>>
>>

Nothing should happen to any other virtual webs you have running on port 80
either by assigned IP or host header. The installer is real basic where
WSUS is going to install into the default web site or create a new virtual
web site on port 8530. The only thing the installer will do is install a
"SelfUpdate" virtual folder into the default web site. This cannot be
changed as it is hard coded into the installer at this time*.

With the above said about the "SelfUpdate" virtual folder being placed into
the default web site, if SUS is on the box and SUS is running out of the
default web site, then SUS's "SelfUpdate" folder will be removed and
replaced with WSUS's "SelfUpdate" folder. The "SelfUpdate" web folder is
where the automatic updates client updates itself. Do not confuse the
"SelfUpdate" folder with the IIS folder that supplies the catalog and/or
patches.

SUS and WSUS can be ran off the same server. If the site desires, it can
have some clients go to SUS and some go to WSUS. I just wanted to give you
a heads up that client workstations *will* receive an updated automatic
updates client if running SUS and WSUS off the same box.

"Adrian Marsh (NNTP)" <> wrote in message
news:egG8S%...
>I also assume that if WUS replaces the Selfupdate VW, then effectively the
>SUS update would stop (until I had WUS working 100%) ?
>
> Adrian Marsh (NNTP) wrote:
>> what happens to the other sub-webs that share port 80 though? would they
>> get affected?
>>
>>
>> neo [mvp outlook] wrote:
>>
>>> Comments inline to your post...
>>>
>>> "Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
>>> news:...
>>>
>>>> Anyone know if SUSReports works with WUS RC?
>>>
>>>
>>>
>>> Don't know.
>>>
>>>
>>>> I have SUS installed on a machine quite happily running on port 80,
>>>> along with a few other sub-webs on the same port.
>>>>
>>>> Reading the WUS RC Deployment guide, I see I can install WUS on a
>>>> second port 8530, but will this interfere with the existing SUS local
>>>> database? And when it comes time to shutdown SUS and move WUS to port
>>>> 80 (if I actually have to?), will my other sites have to be affected?
>>>
>>>
>>>
>>> SUS and WSUS can coexist on the same box. However the only thing that
>>> you have to keep in mind is that the "SelfUpdate" virtual web folder is
>>> going to get replaced by the WSUS components. Has to be done since
>>> legacy AU clients only know how to upgrade the AU client bits from port
>>> 80.
>>>
>>>
>>>> On install, does WUS setup IIS with the secondry port (as required in
>>>> my case), or is that a pre-requisite ?
>>>
>>>
>>>
>>> The WSUS install will detect that SUS is installed and default to port
>>> 8530. If SUS is not on the box, it will default to port 80. This is
>>> done to help with migration strategies from SUS to WSUS. (e.g. you can
>>> import your approvals from SUS to WSUS as WSUS cannot synchronize
>>> content against a SUS server.)
>>>
>>>

Ah, ok, I understand

I take it theres no problem allowing the clients to upgrade to the new
client. Is there a way of telling which version a client has got? I've
a mixture of 2000 SP4 and XP SP2 clients, so they should've upgraded to
the SP2 client already. Is that the latest - or does the WUS client
superceed the XP SP2 one?

My concern about the existing virtual sites was twofold: 1) What would
happen at WUS install, and 2) The docs say once you're happy with WUS,
that you should move the WUS folders back onto port 80.

I guess that the steps in 2) are optional and I could leave WUS on 8530
(but then the WUS version might hit problems possibly...). Should I move
the folders over then I wondered about the impact onto the existing
Virtual folders at that point. I guess theres only one way to find out
though..

Cheers for the help.

Adrian

neo [mvp outlook] wrote:
> Nothing should happen to any other virtual webs you have running on port 80
> either by assigned IP or host header. The installer is real basic where
> WSUS is going to install into the default web site or create a new virtual
> web site on port 8530. The only thing the installer will do is install a
> "SelfUpdate" virtual folder into the default web site. This cannot be
> changed as it is hard coded into the installer at this time*.
>
> With the above said about the "SelfUpdate" virtual folder being placed into
> the default web site, if SUS is on the box and SUS is running out of the
> default web site, then SUS's "SelfUpdate" folder will be removed and
> replaced with WSUS's "SelfUpdate" folder. The "SelfUpdate" web folder is
> where the automatic updates client updates itself. Do not confuse the
> "SelfUpdate" folder with the IIS folder that supplies the catalog and/or
> patches.
>
> SUS and WSUS can be ran off the same server. If the site desires, it can
> have some clients go to SUS and some go to WSUS. I just wanted to give you
> a heads up that client workstations *will* receive an updated automatic
> updates client if running SUS and WSUS off the same box.
>
> "Adrian Marsh (NNTP)" <> wrote in message
> news:egG8S%...
>
>>I also assume that if WUS replaces the Selfupdate VW, then effectively the
>>SUS update would stop (until I had WUS working 100%) ?
>>
>>Adrian Marsh (NNTP) wrote:
>>
>>>what happens to the other sub-webs that share port 80 though? would they
>>>get affected?
>>>
>>>
>>>neo [mvp outlook] wrote:
>>>
>>>
>>>>Comments inline to your post...
>>>>
>>>>"Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
>>>>news:.. .
>>>>
>>>>
>>>>>Anyone know if SUSReports works with WUS RC?
>>>>
>>>>
>>>>
>>>>Don't know.
>>>>
>>>>
>>>>
>>>>>I have SUS installed on a machine quite happily running on port 80,
>>>>>along with a few other sub-webs on the same port.
>>>>>
>>>>>Reading the WUS RC Deployment guide, I see I can install WUS on a
>>>>>second port 8530, but will this interfere with the existing SUS local
>>>>>database? And when it comes time to shutdown SUS and move WUS to port
>>>>>80 (if I actually have to?), will my other sites have to be affected?
>>>>
>>>>
>>>>
>>>>SUS and WSUS can coexist on the same box. However the only thing that
>>>>you have to keep in mind is that the "SelfUpdate" virtual web folder is
>>>>going to get replaced by the WSUS components. Has to be done since
>>>>legacy AU clients only know how to upgrade the AU client bits from port
>>>>80.
>>>>
>>>>
>>>>
>>>>>On install, does WUS setup IIS with the secondry port (as required in
>>>>>my case), or is that a pre-requisite ?
>>>>
>>>>
>>>>
>>>>The WSUS install will detect that SUS is installed and default to port
>>>>8530. If SUS is not on the box, it will default to port 80. This is
>>>>done to help with migration strategies from SUS to WSUS. (e.g. you can
>>>>import your approvals from SUS to WSUS as WSUS cannot synchronize
>>>>content against a SUS server.)
>>>>
>>>>
>
>
>

I see no problems if working with the release candidate of WSUS as Microsoft
generally supports a migration/upgrade of RC binaries to RTM. The AU client
that comes in WSUS is a bit newer than what is packaged with service pack 2
for Windows XP and Windows 2003 Service Pack 1. The binaries appear to work
flawlessly against SUS, WSUS, and Microsoft's Windows Update. About all I
can say is that the major/minor version numbers of the new AU client are
higher than what is found on Windows 2003 Service Pack 1. Since WSUS isn't
final at this stage, its just best to leave it at that since these numbers
can change between now and the final release of WSUS.

This is only a guess, but my take is that Microsoft has made an assumption
that many will have hardware dedicated to supporting WSUS rather than a site
running multiple virtual webs off a single server. Part of this assumption
on my part is that the backend of WSUS is going to run off SQL, which may
raise the bar in some sites that aren't used to SQL and that a site would
upgrade SUS to WSUS. Considering most install SUS into the default web
site, it seems natural for the recommendation to move 8530 back to 80 once
SUS is retired*.

Outside of that, I've just started testing the use of host headers and
assigned ips to virtual webs. Too early for me to say if a site will be
able to maximize its return on IIS application server(s) since I haven't
completed my testing. Best advice is to follow the beta newsgroups for WSUS
since Microsoft has tried there dandiest to provide the beta bits for an
open evaluation in test environments. See
http://www.microsoft.com/windowsserv...newsgroup.mspx
if you wish to access the newsgroups for WSUS.

/neo

* Other aspect to take into account is network configuration. For example,
firewall and proxy server support. Much easier to work from port 80 than
say 8530.

"Adrian Marsh (NNTP)" <> wrote in message
news:...
> Ah, ok, I understand
>
> I take it theres no problem allowing the clients to upgrade to the new
> client. Is there a way of telling which version a client has got? I've a
> mixture of 2000 SP4 and XP SP2 clients, so they should've upgraded to the
> SP2 client already. Is that the latest - or does the WUS client superceed
> the XP SP2 one?
>
> My concern about the existing virtual sites was twofold: 1) What would
> happen at WUS install, and 2) The docs say once you're happy with WUS,
> that you should move the WUS folders back onto port 80.
>
> I guess that the steps in 2) are optional and I could leave WUS on 8530
> (but then the WUS version might hit problems possibly...). Should I move
> the folders over then I wondered about the impact onto the existing
> Virtual folders at that point. I guess theres only one way to find out
> though..
>
> Cheers for the help.
>
> Adrian
>
> neo [mvp outlook] wrote:
>> Nothing should happen to any other virtual webs you have running on port
>> 80 either by assigned IP or host header. The installer is real basic
>> where WSUS is going to install into the default web site or create a new
>> virtual web site on port 8530. The only thing the installer will do is
>> install a "SelfUpdate" virtual folder into the default web site. This
>> cannot be changed as it is hard coded into the installer at this time*.
>>
>> With the above said about the "SelfUpdate" virtual folder being placed
>> into the default web site, if SUS is on the box and SUS is running out of
>> the default web site, then SUS's "SelfUpdate" folder will be removed and
>> replaced with WSUS's "SelfUpdate" folder. The "SelfUpdate" web folder is
>> where the automatic updates client updates itself. Do not confuse the
>> "SelfUpdate" folder with the IIS folder that supplies the catalog and/or
>> patches.
>>
>> SUS and WSUS can be ran off the same server. If the site desires, it can
>> have some clients go to SUS and some go to WSUS. I just wanted to give
>> you a heads up that client workstations *will* receive an updated
>> automatic updates client if running SUS and WSUS off the same box.
>>
>> "Adrian Marsh (NNTP)" <> wrote in message
>> news:egG8S%...
>>
>>>I also assume that if WUS replaces the Selfupdate VW, then effectively
>>>the SUS update would stop (until I had WUS working 100%) ?
>>>
>>>Adrian Marsh (NNTP) wrote:
>>>
>>>>what happens to the other sub-webs that share port 80 though? would they
>>>>get affected?
>>>>
>>>>
>>>>neo [mvp outlook] wrote:
>>>>
>>>>
>>>>>Comments inline to your post...
>>>>>
>>>>>"Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
>>>>>news:. ..
>>>>>
>>>>>
>>>>>>Anyone know if SUSReports works with WUS RC?
>>>>>
>>>>>
>>>>>
>>>>>Don't know.
>>>>>
>>>>>
>>>>>
>>>>>>I have SUS installed on a machine quite happily running on port 80,
>>>>>>along with a few other sub-webs on the same port.
>>>>>>
>>>>>>Reading the WUS RC Deployment guide, I see I can install WUS on a
>>>>>>second port 8530, but will this interfere with the existing SUS local
>>>>>>database? And when it comes time to shutdown SUS and move WUS to port
>>>>>>80 (if I actually have to?), will my other sites have to be affected?
>>>>>
>>>>>
>>>>>
>>>>>SUS and WSUS can coexist on the same box. However the only thing that
>>>>>you have to keep in mind is that the "SelfUpdate" virtual web folder is
>>>>>going to get replaced by the WSUS components. Has to be done since
>>>>>legacy AU clients only know how to upgrade the AU client bits from port
>>>>>80.
>>>>>
>>>>>
>>>>>
>>>>>>On install, does WUS setup IIS with the secondry port (as required in
>>>>>>my case), or is that a pre-requisite ?
>>>>>
>>>>>
>>>>>
>>>>>The WSUS install will detect that SUS is installed and default to port
>>>>>8530. If SUS is not on the box, it will default to port 80. This is
>>>>>done to help with migration strategies from SUS to WSUS. (e.g. you can
>>>>>import your approvals from SUS to WSUS as WSUS cannot synchronize
>>>>>content against a SUS server.)
>>>>>
>>>>>
>>
>>

Thanks for the detail Neo,

And sorry to go on about this- I use AD GPO to dictate the URL, so this
will change to https://sus.uk-lab.lucent.com:8530 during testing right?
Will the computers in that GPO be able to pickup the autoupdate client
from the Selfupdate folder hanging off port 80? (I assume that if the
directory is hard-coded then so is the port?) I added "https" as I think
WUS is SSL based.

I understand your comments. Mine is only a small lab thought <100
active clients at a time, and the updates are still considered "low
priority", so I only get one machine to play with....

Thanks for the link, useful info.

Adrian

neo [mvp outlook] wrote:
> I see no problems if working with the release candidate of WSUS as Microsoft
> generally supports a migration/upgrade of RC binaries to RTM. The AU client
> that comes in WSUS is a bit newer than what is packaged with service pack 2
> for Windows XP and Windows 2003 Service Pack 1. The binaries appear to work
> flawlessly against SUS, WSUS, and Microsoft's Windows Update. About all I
> can say is that the major/minor version numbers of the new AU client are
> higher than what is found on Windows 2003 Service Pack 1. Since WSUS isn't
> final at this stage, its just best to leave it at that since these numbers
> can change between now and the final release of WSUS.
>
> This is only a guess, but my take is that Microsoft has made an assumption
> that many will have hardware dedicated to supporting WSUS rather than a site
> running multiple virtual webs off a single server. Part of this assumption
> on my part is that the backend of WSUS is going to run off SQL, which may
> raise the bar in some sites that aren't used to SQL and that a site would
> upgrade SUS to WSUS. Considering most install SUS into the default web
> site, it seems natural for the recommendation to move 8530 back to 80 once
> SUS is retired*.
>
> Outside of that, I've just started testing the use of host headers and
> assigned ips to virtual webs. Too early for me to say if a site will be
> able to maximize its return on IIS application server(s) since I haven't
> completed my testing. Best advice is to follow the beta newsgroups for WSUS
> since Microsoft has tried there dandiest to provide the beta bits for an
> open evaluation in test environments. See
> http://www.microsoft.com/windowsserv...newsgroup.mspx
> if you wish to access the newsgroups for WSUS.
>
> /neo
>
> * Other aspect to take into account is network configuration. For example,
> firewall and proxy server support. Much easier to work from port 80 than
> say 8530.
>
> "Adrian Marsh (NNTP)" <> wrote in message
> news:...
>
>>Ah, ok, I understand
>>
>>I take it theres no problem allowing the clients to upgrade to the new
>>client. Is there a way of telling which version a client has got? I've a
>>mixture of 2000 SP4 and XP SP2 clients, so they should've upgraded to the
>>SP2 client already. Is that the latest - or does the WUS client superceed
>>the XP SP2 one?
>>
>>My concern about the existing virtual sites was twofold: 1) What would
>>happen at WUS install, and 2) The docs say once you're happy with WUS,
>>that you should move the WUS folders back onto port 80.
>>
>>I guess that the steps in 2) are optional and I could leave WUS on 8530
>>(but then the WUS version might hit problems possibly...). Should I move
>>the folders over then I wondered about the impact onto the existing
>>Virtual folders at that point. I guess theres only one way to find out
>>though..
>>
>>Cheers for the help.
>>
>>Adrian
>>
>>neo [mvp outlook] wrote:
>>
>>>Nothing should happen to any other virtual webs you have running on port
>>>80 either by assigned IP or host header. The installer is real basic
>>>where WSUS is going to install into the default web site or create a new
>>>virtual web site on port 8530. The only thing the installer will do is
>>>install a "SelfUpdate" virtual folder into the default web site. This
>>>cannot be changed as it is hard coded into the installer at this time*.
>>>
>>>With the above said about the "SelfUpdate" virtual folder being placed
>>>into the default web site, if SUS is on the box and SUS is running out of
>>>the default web site, then SUS's "SelfUpdate" folder will be removed and
>>>replaced with WSUS's "SelfUpdate" folder. The "SelfUpdate" web folder is
>>>where the automatic updates client updates itself. Do not confuse the
>>>"SelfUpdate" folder with the IIS folder that supplies the catalog and/or
>>>patches.
>>>
>>>SUS and WSUS can be ran off the same server. If the site desires, it can
>>>have some clients go to SUS and some go to WSUS. I just wanted to give
>>>you a heads up that client workstations *will* receive an updated
>>>automatic updates client if running SUS and WSUS off the same box.
>>>
>>>"Adrian Marsh (NNTP)" <> wrote in message
>>>news:egG8S%. ..
>>>
>>>
>>>>I also assume that if WUS replaces the Selfupdate VW, then effectively
>>>>the SUS update would stop (until I had WUS working 100%) ?
>>>>
>>>>Adrian Marsh (NNTP) wrote:
>>>>
>>>>
>>>>>what happens to the other sub-webs that share port 80 though? would they
>>>>>get affected?
>>>>>
>>>>>
>>>>>neo [mvp outlook] wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Comments inline to your post...
>>>>>>
>>>>>>"Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
>>>>>>news:.. .
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Anyone know if SUSReports works with WUS RC?
>>>>>>
>>>>>>
>>>>>>
>>>>>>Don't know.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>I have SUS installed on a machine quite happily running on port 80,
>>>>>>>along with a few other sub-webs on the same port.
>>>>>>>
>>>>>>>Reading the WUS RC Deployment guide, I see I can install WUS on a
>>>>>>>second port 8530, but will this interfere with the existing SUS local
>>>>>>>database? And when it comes time to shutdown SUS and move WUS to port
>>>>>>>80 (if I actually have to?), will my other sites have to be affected?
>>>>>>
>>>>>>
>>>>>>
>>>>>>SUS and WSUS can coexist on the same box. However the only thing that
>>>>>>you have to keep in mind is that the "SelfUpdate" virtual web folder is
>>>>>>going to get replaced by the WSUS components. Has to be done since
>>>>>>legacy AU clients only know how to upgrade the AU client bits from port
>>>>>>80.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>On install, does WUS setup IIS with the secondry port (as required in
>>>>>>>my case), or is that a pre-requisite ?
>>>>>>
>>>>>>
>>>>>>
>>>>>>The WSUS install will detect that SUS is installed and default to port
>>>>>>8530. If SUS is not on the box, it will default to port 80. This is
>>>>>>done to help with migration strategies from SUS to WSUS. (e.g. you can
>>>>>>import your approvals from SUS to WSUS as WSUS cannot synchronize
>>>>>>content against a SUS server.)
>>>>>>
>>>>>>
>>>
>>>
>

Concept is on target, but the SSL port would be 8531. See
http://www.microsoft.com/windowsserv...eployment.mspx
for additional details about deploying WSUS. (There is a section on SSL.)

"Adrian Marsh (NNTP)" <> wrote in message
news:...
> Thanks for the detail Neo,
>
> And sorry to go on about this- I use AD GPO to dictate the URL, so this
> will change to https://sus.uk-lab.lucent.com:8530 during testing right?
> Will the computers in that GPO be able to pickup the autoupdate client
> from the Selfupdate folder hanging off port 80? (I assume that if the
> directory is hard-coded then so is the port?) I added "https" as I think
> WUS is SSL based.
>
> I understand your comments. Mine is only a small lab thought <100 active
> clients at a time, and the updates are still considered "low priority", so
> I only get one machine to play with....
>
> Thanks for the link, useful info.
>
> Adrian
>
> neo [mvp outlook] wrote:
>> I see no problems if working with the release candidate of WSUS as
>> Microsoft generally supports a migration/upgrade of RC binaries to RTM.
>> The AU client that comes in WSUS is a bit newer than what is packaged
>> with service pack 2 for Windows XP and Windows 2003 Service Pack 1. The
>> binaries appear to work flawlessly against SUS, WSUS, and Microsoft's
>> Windows Update. About all I can say is that the major/minor version
>> numbers of the new AU client are higher than what is found on Windows
>> 2003 Service Pack 1. Since WSUS isn't final at this stage, its just best
>> to leave it at that since these numbers can change between now and the
>> final release of WSUS.
>>
>> This is only a guess, but my take is that Microsoft has made an
>> assumption that many will have hardware dedicated to supporting WSUS
>> rather than a site running multiple virtual webs off a single server.
>> Part of this assumption on my part is that the backend of WSUS is going
>> to run off SQL, which may raise the bar in some sites that aren't used to
>> SQL and that a site would upgrade SUS to WSUS. Considering most install
>> SUS into the default web site, it seems natural for the recommendation to
>> move 8530 back to 80 once SUS is retired*.
>>
>> Outside of that, I've just started testing the use of host headers and
>> assigned ips to virtual webs. Too early for me to say if a site will be
>> able to maximize its return on IIS application server(s) since I haven't
>> completed my testing. Best advice is to follow the beta newsgroups for
>> WSUS since Microsoft has tried there dandiest to provide the beta bits
>> for an open evaluation in test environments. See
>> http://www.microsoft.com/windowsserv...newsgroup.mspx
>> if you wish to access the newsgroups for WSUS.
>>
>> /neo
>>
>> * Other aspect to take into account is network configuration. For
>> example, firewall and proxy server support. Much easier to work from
>> port 80 than say 8530.
>>
>> "Adrian Marsh (NNTP)" <> wrote in message
>> news:...
>>
>>>Ah, ok, I understand
>>>
>>>I take it theres no problem allowing the clients to upgrade to the new
>>>client. Is there a way of telling which version a client has got? I've a
>>>mixture of 2000 SP4 and XP SP2 clients, so they should've upgraded to the
>>>SP2 client already. Is that the latest - or does the WUS client superceed
>>>the XP SP2 one?
>>>
>>>My concern about the existing virtual sites was twofold: 1) What would
>>>happen at WUS install, and 2) The docs say once you're happy with WUS,
>>>that you should move the WUS folders back onto port 80.
>>>
>>>I guess that the steps in 2) are optional and I could leave WUS on 8530
>>>(but then the WUS version might hit problems possibly...). Should I move
>>>the folders over then I wondered about the impact onto the existing
>>>Virtual folders at that point. I guess theres only one way to find out
>>>though..
>>>
>>>Cheers for the help.
>>>
>>>Adrian
>>>
>>>neo [mvp outlook] wrote:
>>>
>>>>Nothing should happen to any other virtual webs you have running on
>>>>port 80 either by assigned IP or host header. The installer is real
>>>>basic where WSUS is going to install into the default web site or create
>>>>a new virtual web site on port 8530. The only thing the installer will
>>>>do is install a "SelfUpdate" virtual folder into the default web site.
>>>>This cannot be changed as it is hard coded into the installer at this
>>>>time*.
>>>>
>>>>With the above said about the "SelfUpdate" virtual folder being placed
>>>>into the default web site, if SUS is on the box and SUS is running out
>>>>of the default web site, then SUS's "SelfUpdate" folder will be removed
>>>>and replaced with WSUS's "SelfUpdate" folder. The "SelfUpdate" web
>>>>folder is where the automatic updates client updates itself. Do not
>>>>confuse the "SelfUpdate" folder with the IIS folder that supplies the
>>>>catalog and/or patches.
>>>>
>>>>SUS and WSUS can be ran off the same server. If the site desires, it
>>>>can have some clients go to SUS and some go to WSUS. I just wanted to
>>>>give you a heads up that client workstations *will* receive an updated
>>>>automatic updates client if running SUS and WSUS off the same box.
>>>>
>>>>"Adrian Marsh (NNTP)" <> wrote in message
>>>>news:egG8S%.. .
>>>>
>>>>
>>>>>I also assume that if WUS replaces the Selfupdate VW, then effectively
>>>>>the SUS update would stop (until I had WUS working 100%) ?
>>>>>
>>>>>Adrian Marsh (NNTP) wrote:
>>>>>
>>>>>
>>>>>>what happens to the other sub-webs that share port 80 though? would
>>>>>>they get affected?
>>>>>>
>>>>>>
>>>>>>neo [mvp outlook] wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Comments inline to your post...
>>>>>>>
>>>>>>>"Adrian Marsh (NNTP)" <marsh_removeme_@lucent.com> wrote in message
>>>>>>>news:. ..
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Anyone know if SUSReports works with WUS RC?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>Don't know.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>I have SUS installed on a machine quite happily running on port 80,
>>>>>>>>along with a few other sub-webs on the same port.
>>>>>>>>
>>>>>>>>Reading the WUS RC Deployment guide, I see I can install WUS on a
>>>>>>>>second port 8530, but will this interfere with the existing SUS
>>>>>>>>local database? And when it comes time to shutdown SUS and move WUS
>>>>>>>>to port 80 (if I actually have to?), will my other sites have to be
>>>>>>>>affected?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>SUS and WSUS can coexist on the same box. However the only thing
>>>>>>>that you have to keep in mind is that the "SelfUpdate" virtual web
>>>>>>>folder is going to get replaced by the WSUS components. Has to be
>>>>>>>done since legacy AU clients only know how to upgrade the AU client
>>>>>>>bits from port 80.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>On install, does WUS setup IIS with the secondry port (as required
>>>>>>>>in my case), or is that a pre-requisite ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>The WSUS install will detect that SUS is installed and default to
>>>>>>>port 8530. If SUS is not on the box, it will default to port 80.
>>>>>>>This is done to help with migration strategies from SUS to WSUS.
>>>>>>>(e.g. you can import your approvals from SUS to WSUS as WSUS cannot
>>>>>>>synchronize content against a SUS server.)
>>>>>>>
>>>>>>>
>>>>
>>>>
>>