Re: WSUS port issue
- From: "kj" <kj@xxxxxxxxxxx>
- Date: Thu, 10 Aug 2006 09:54:48 -0700
There's really only one way to add WSUS to SBS2003 and not break anything.
It's well documented and it works very well.
http://www.microsoft.com/downloads/details.aspx?FamilyID=28c43d57-2e15-47b2-9a6f-1514aa3ed05f&displaylang=en
If the clients aren't getting updated with the correct group policy
settings, then that should be resolved and not "worked around".
--
/kj
"Greg O" <gregorme@xxxxxxxxx> wrote in message
news:1155221443.962286.187350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
You could move sharepoint to another port perhaps. Not an ideal
solution but perhaps a workaround.
kj wrote:
WSUS on port 80 on SBS isn't a good thing. Sharepoint site and all, ya
know.
(Works fine on regular IIS servers without Sharepoint.)
--
/kj
"Greg O" <gregorme@xxxxxxxxx> wrote in message
news:1155089419.368497.190120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Couldn't he change the port back to port 80 instead of 8530? If he did
then nothing would be needed to be changed in group policy.
kj wrote:
Mark,
Is this just one workstation or all workstations?
Do any workstations show up in the WSUSAdmin console?
There are a couple of other possibilities (at least) besides a
superseding
GPO.
One; the GPO isn't applying. Change or delete the registry setting and
see
if returns. If it does, then *something* is setting it. Check the
event
log
and verify group policy is being applied successfully.
Two; something is coming along after the GPO applies and setting this
back.
I took over a site where the admin had deployed a login script with
.reg
files apparently because he couldn't fix the problem with group
policies.
When we upgraded them from SUS to WSUS and modified the GPO's the
clients
wouldn't stay associated with the WSUS server. That one was really
weird
to
track down.
--
/kj
"Mark" <info-nospam@xxxxxxxxxxxx> wrote in message
news:%237W$pwpuGHA.5084@xxxxxxxxxxxxxxxxxxxxxxx
KJ is correct, the GPO shows :8530 but the reg key doesn't and all
are
XP
SP2, quite odd!
"kj" <kj@xxxxxxxxxxx> wrote in message
news:eXU0jrnuGHA.4292@xxxxxxxxxxxxxxxxxxxxxxx
As I recall the really old windows update clients didn't handle the
non
80 port numbers. Is this an RTM XP client or pre SP4 Win 2K
machine?
I'd
still be surprised if the registry wasn't correct with the
presiding
policy setting.
No running the clientdiag would just confirm the settings but
perhaps
provide something missed or overlooked.
--
/kj
"Mark" <info-nospam@xxxxxxxxxxxx> wrote in message
news:e6Zd%23hnuGHA.1852@xxxxxxxxxxxxxxxxxxxxxxx
negatory, triple checked the GPO. will run the diag but if the
location isn't correct, that won't help.
"kj" <kj@xxxxxxxxxxx> wrote in message
news:OukaXYnuGHA.4544@xxxxxxxxxxxxxxxxxxxxxxx
No, WUServer and WUStatusServer should look like
http://server:8530
Fat finger on the colon in the GPO and perhaps a semicolon got
inserted
instead?
Run the (wsus) clientdiag.exe and check the results.
--
/kj
"Mark" <info-nospam@xxxxxxxxxxxx> wrote in message
news:enHHHQnuGHA.4544@xxxxxxxxxxxxxxxxxxxxxxx
Installed WSUS on SBS2003, no problem except in GPO I specified
http://server:8530 for the location yet in the registry it just
puts
http://server but is that normal???
.
- References:
- WSUS port issue
- From: Mark
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Mark
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Mark
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Greg O
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Greg O
- WSUS port issue
- Prev by Date: Re: how to safely remove exchange from sbs 2003
- Next by Date: Event ID 529 on cleint workstation
- Previous by thread: Re: WSUS port issue
- Next by thread: Re: WSUS port issue
- Index(es):
Relevant Pages
|