Re: Clients not showijng up in WSUS 3.0 SP1
- From: "Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Thu, 1 May 2008 16:47:49 -0500
It sure eliminates most of the WSUS installation and administration load. Not a whole lot else included, though.
SBS R2 does a sweet job on the GPOs, and while it's largely cookie-cutter WSUS update approval/installation configuration is not 100% efficient - it works great for the 80% of the folks that just want to do their work ...
--
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us
"Mike in Nebraska" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message news:%236$$sJ9qIHA.672@xxxxxxxxxxxxxxxxxxxxxxx
Maybe I should go buy it. Might help with the little things.
"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message news:18EB4AD3-7F5B-4759-97A8-DF72B6B8982E@xxxxxxxxxxxxxxxxTwo letters ... R2 ;-).
Simple WSUS configuration, it works, little maintenance.
--
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us
"Mike in Nebraska" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message news:O5OJls8qIHA.3616@xxxxxxxxxxxxxxxxxxxxxxxFound another are of confusion .... Page 97 (of 151). For Steps 1 and 2, is this from the WSUS server or the client? On Steps 3 and 4, do I wait 6-10 minutes, then another minute to check the registry? And on which machine? And on Step 4, WHERE in the registry will I find these values?
"Liam" <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6E8F03D2-F4F2-41B5-9D15-44FB08ABBEAF@xxxxxxxxxxxxxxxxYup I had bad instructions too.
I reconfigured all previously configured GPO's to "Not configured" and all
the Pc's magically began appearing....all except one...there is always a
trouble maker.
Liam
"Russ (SBITS.Biz)" wrote:
And I don't know what Instructions people are using for this, because I'm
seeing a rash of people with this issue?
In the WSUS 2.0 you had to Create a NEW GP to get WSUS to use WSUS
In 3.0 You don't need to WSUS Creates one...
And I use the WSUS console to find the PC's and it finds them just fine?
What instructions are you using?
Maybe there is an error in it?
Russ
--
SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
World Wide Remote SBS2003 Support - http://www.SBITS.Biz
-
"Mike in Nebraska" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message
news:etOGJkTqIHA.5096@xxxxxxxxxxxxxxxxxxxxxxx
> Running on SBS 2003 Premium SP2.
> ===================
> New install of WSUS 3.0 SP1. Works fine in getting/downloading > updates,
> but clients are not showing up under "Computers"; not even the host
> server.
>
> Read a few things on http://wsuswiki.com and tried the Client > Diagnostic
> Tool on my PC, (download from MS), and got errors on the last > section:
>
> "Checking Connection to WSUS/SUS Server
> AU does not have Policy Set
> AU does not have Policy Set
> UseWuServer is diabled
> .................................................................. > FAIL"
>
> I have set the option to "use Group Policy" to assign computers to > the
> Unassigned Computers group and then I'll move them to either Servers > of
> Workstations groups. I've also tried assigning from just the > console - no
> luck, either.
>
> We use a mix of IE7 and Mozilla Firefox in the office. All set to > Manual
> Proxy Configuration.
>
> What should I do next?
> -- > Mike Webb
> Platte River Whooping Crane Maintenance Trust, Inc.
> a conservation non-profit (501 (c)(3)) organization
> Wood River, NE
>
.
- Prev by Date: Re: SBS Transition Pack Advice
- Next by Date: Can't access Companyweb
- Previous by thread: Alerts not being sent by companyweb
- Next by thread: Re: Clients not showing up in WSUS 3.0 SP1
- Index(es):
Relevant Pages
|
