wsus 3.0
in [Windows Update]
|
Prev: Vista Windows Update Error 80070664
Next: Wsus 3.0 Install Error: Request for principal permission failed
From: orhan baytok orhan on 19 Jun 2007 08:27 client computer names do not appear in wsus console. And htpp://<server>:8530/selfupdate gives authrization problems.
From: MowGreen [MVP] on 19 Jun 2007 15:05 Try here, Orhan : Discussions in Windows Server Update Services http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.update_services MowGreen [MVP 2003-2007] =============== *-343-* FDNY Never Forgotten =============== orhan baytok wrote: > client computer names do not appear in wsus console. And > htpp://<server>:8530/selfupdate gives authrization problems. >
From: uwcableguy on 25 Jun 2007 18:55 i too am having the same issue with the error message MMC could not create the snap-in on win 2k3 sp2 server. i have .net 2.0 and all updates, i have mmc 3.0, i have report viewer 2005 w sp1. tried uninstall/reinstall of all 3 plus wsus 3.0. tired caps lock. tried renaming mmc.exe. tried renaming wsus.msc. this is driving me crazy! i also added admin acct to wsus admins and wsus reports groups. i performed reg hack per ms kb918041 to fix the damn iis worker process errors/w3wp.exe crashes. i am about to call ms business critical... could this be a sp2 issue? not sure what else it is... argh! On Jun 5, 5:54 pm, DaveMills <DaveMi...(a)newsgroup.nospam> wrote: > On Tue, 5 Jun 2007 08:09:04 -0500, "Lawrence Garvin \(MVP\)" > > <onsit...(a)community.nospam> wrote: > >> "Adde" <A...(a)discussions.microsoft.com> wrote in message > >>news:096F1B6A-BAA0-4F4C-AC94-5204D765BCFF(a)microsoft.com... > >> |I have setupWSUS3.0 The group policys are fine and running gpresult on > >> | clients show that grouppolicy is loaded. But only 1 out of 30 clients > >> are > >> | showing up inWSUSconsole. Had same problem with prior versions of > >>WSUS... > >> | > >> | I was hoping3.0would resolve the problem, but there my luck ran out... > >> Any > >> | ideas? > > Are the clients "cloned" PCs. If so you may see a PC inWSUSonly to find it > replaced by another PC a bit later. Is that what is happening? > > > > >This is a classic case of throwing an orange against a wall, hoping to turn > >it green, because the grapes didn't do the job. > > >The fundamental flaw here is that the *clients* cannot communicate with the > >WSUSserver, and it probably doesn't matter what version theWSUSserver > >actually is. > > >Download the Client Diagnostic Tool, run it on one of these clients *and* on > >theWSUSserver, and post the results from both systems. > > >http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-... > > -- > Dave Mills > There are 10 type of people, those that understand binary and those that don't.
From: Lawrence Garvin (MVP) on 25 Jun 2007 22:52
<uwcableguy(a)gmail.com> wrote in message news:1182812115.796955.236140(a)q69g2000hsb.googlegroups.com... >i too am having the same issue with the error message MMC could not > create the snap-in on win 2k3 sp2 server. i have .net 2.0 and all > updates, i have mmc 3.0, i have report viewer 2005 w sp1. tried > uninstall/reinstall of all 3 plus wsus 3.0. tired caps lock. tried > renaming mmc.exe. tried renaming wsus.msc. this is driving me crazy! > > i also added admin acct to wsus admins and wsus reports groups. i > performed reg hack per ms kb918041 to fix the damn iis worker process > errors/w3wp.exe crashes. > > i am about to call ms business critical... > > could this be a sp2 issue? Yes.. it could. Given that: [a] WSUS 2 demonstrated some issues being installed on SQL Server 2000 SP4, for which the common wisdom is "Install to SQL Server 2000 SP3 and then apply SP4 after installation" [b] WSUS 3 demonstrated some issues being installed to SQL Server 2005 SP2, for which the common wisdom is "Install to SQL Server 2005 SP1 and then apply SP2 after installation" and given that Windows Server 2003 Service Pack 2 was released *after* WSUS v3, and the documented (supported) platform for WSUS 3 is "Windows Server 2003 Service Pack 1" or "Windows Server Longhorn" (which, of course, is still pre-release, so technically it's not yet supported at all), I find it entirely possible that WSUS 3 will demonstrate some issues being installed on Windows Server 2003 SP2 systems, for which the common wisdom will likely become: "Install to Windows Server 2003 SP1 and then apply SP2 after installation". -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com ..... |