|
|
where can they be downloaded from please?
I've poked all around MS and the wiki. Simply can't see a link.
|
|
On Sat, 26 May 2007 07:55:20 +1000, "SuperGumby [SBS MVP]" <not[ at ]your.nellie> wrote:
[Quoted Text] >where can they be downloaded from please? > >I've poked all around MS and the wiki. Simply can't see a link. >
I used to be able to find them quite easily but they seem to have been removed. -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
|
|
Here's the 'old' download page you are looking for.
http://www.microsoft.com/technet/windowsserver/wsus/20/downloads/tools/default.mspx
Cheers,
Jeff Centimano MVP - Windows Server http://windowsconnected.com/blogs/jeff
"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message news:9iff53d95sl70sfnc3m8cklkbmae1t3ec9[ at ]4ax.com...
[Quoted Text] > On Sat, 26 May 2007 07:55:20 +1000, "SuperGumby [SBS MVP]" > <not[ at ]your.nellie> > wrote: > >>where can they be downloaded from please? >> >>I've poked all around MS and the wiki. Simply can't see a link. >> > > I used to be able to find them quite easily but they seem to have been > removed. > -- > Dave Mills > There are 10 type of people, those that understand binary and those that > don't.
|
|
tks Jeff.
The server tool seems to have successfully pulled the logs out of WSUS 3, do you know the status of compatability to WSUS 3? I'm trying to shoot a problem where the server was upgraded WSUS2-3 and the client PC's are now showing as 'not yet reported'.
The client logs show 'cookie expired or new PID' but I've tried most normal reset stuff (stop AU service, deleting WSUS reg entries, deleting files/folders, restart PC) and they simply refuse to report. The server is reporting to itself OK so I don't _think_ it's really the server.
"Jeff Centimano [MVP]" <my_last_name[ at ]msn.com> wrote in message news:6220D824-BA72-4C49-835B-C012AA7FD193[ at ]microsoft.com...
[Quoted Text] > Here's the 'old' download page you are looking for. > > http://www.microsoft.com/technet/windowsserver/wsus/20/downloads/tools/default.mspx> > Cheers, > > Jeff Centimano > MVP - Windows Server > http://windowsconnected.com/blogs/jeff> > "DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message > news:9iff53d95sl70sfnc3m8cklkbmae1t3ec9[ at ]4ax.com... >> On Sat, 26 May 2007 07:55:20 +1000, "SuperGumby [SBS MVP]" >> <not[ at ]your.nellie> >> wrote: >> >>>where can they be downloaded from please? >>> >>>I've poked all around MS and the wiki. Simply can't see a link. >>> >> >> I used to be able to find them quite easily but they seem to have been >> removed. >> -- >> Dave Mills >> There are 10 type of people, those that understand binary and those that >> don't. >
|
|
On May 26, 3:49 pm, "SuperGumby [SBS MVP]" <n...[ at ]your.nellie> wrote:
[Quoted Text] > tks Jeff. > > The server tool seems to have successfully pulled the logs out of WSUS 3, do > you know the status of compatability to WSUS 3? I'm trying to shoot a > problem where the server was upgraded WSUS2-3 and the client PC's are now > showing as 'not yet reported'. > > The client logs show 'cookie expired or new PID' but I've tried most normal > reset stuff (stop AU service, deleting WSUS reg entries, deleting > files/folders, restart PC) and they simply refuse to report. The server is > reporting to itself OK so I don't _think_ it's really the server. > > "Jeff Centimano [MVP]" <my_last_n...[ at ]msn.com> wrote in messagenews:6220D824-BA72-4C49-835B-C012AA7FD193[ at ]microsoft.com... > > > > > Here's the 'old' download page you are looking for. > > > http://www.microsoft.com/technet/windowsserver/wsus/20/downloads/tool...> > > Cheers, > > > Jeff Centimano > > MVP - Windows Server > > http://windowsconnected.com/blogs/jeff> > > "DaveMills" <DaveMi...[ at ]newsgroup.nospam> wrote in message > >news:9iff53d95sl70sfnc3m8cklkbmae1t3ec9[ at ]4ax.com... > >> On Sat, 26 May 2007 07:55:20 +1000, "SuperGumby [SBS MVP]" > >> <n...[ at ]your.nellie> > >> wrote: > > >>>where can they be downloaded from please? > > >>>I've poked all around MS and the wiki. Simply can't see a link. > > >> I used to be able to find them quite easily but they seem to have been > >> removed. > >> -- > >> Dave Mills > >> There are 10 type of people, those that understand binary and those that > >> don't.- Hide quoted text - > > - Show quoted text - I have had that issue on a few client computers. Just visit the Windows Update which will do the client side update and then they will start reporting.
|
|
I've taken a couple to WU then MU without effect.
"Gus" <vines77[ at ]gmail.com> wrote in message news:1180287114.249700.100070[ at ]m36g2000hse.googlegroups.com...
[Quoted Text] > On May 26, 3:49 pm, "SuperGumby [SBS MVP]" <n...[ at ]your.nellie> wrote: >> tks Jeff. >> >> The server tool seems to have successfully pulled the logs out of WSUS 3, >> do >> you know the status of compatability to WSUS 3? I'm trying to shoot a >> problem where the server was upgraded WSUS2-3 and the client PC's are now >> showing as 'not yet reported'. >> >> The client logs show 'cookie expired or new PID' but I've tried most >> normal >> reset stuff (stop AU service, deleting WSUS reg entries, deleting >> files/folders, restart PC) and they simply refuse to report. The server >> is >> reporting to itself OK so I don't _think_ it's really the server. >> >> "Jeff Centimano [MVP]" <my_last_n...[ at ]msn.com> wrote in >> messagenews:6220D824-BA72-4C49-835B-C012AA7FD193[ at ]microsoft.com... >> >> >> >> > Here's the 'old' download page you are looking for. >> >> > http://www.microsoft.com/technet/windowsserver/wsus/20/downloads/tool...>> >> > Cheers, >> >> > Jeff Centimano >> > MVP - Windows Server >> > http://windowsconnected.com/blogs/jeff>> >> > "DaveMills" <DaveMi...[ at ]newsgroup.nospam> wrote in message >> >news:9iff53d95sl70sfnc3m8cklkbmae1t3ec9[ at ]4ax.com... >> >> On Sat, 26 May 2007 07:55:20 +1000, "SuperGumby [SBS MVP]" >> >> <n...[ at ]your.nellie> >> >> wrote: >> >> >>>where can they be downloaded from please? >> >> >>>I've poked all around MS and the wiki. Simply can't see a link. >> >> >> I used to be able to find them quite easily but they seem to have been >> >> removed. >> >> -- >> >> Dave Mills >> >> There are 10 type of people, those that understand binary and those >> >> that >> >> don't.- Hide quoted text - >> >> - Show quoted text - > > I have had that issue on a few client computers. Just visit the > Windows Update which will do the client side update and then they will > start reporting. >
|
|
On Sat, 26 May 2007 11:54:29 -0500, "Jeff Centimano [MVP]" <my_last_name[ at ]msn.com> wrote:
[Quoted Text] Thanks Jeff, I have bookmarked the page but have to wonder why the tools are no longer available for WSUS 3. It seems odd that MS have an updated product but do not consider the tools useful enough to have a link on the WSUS 3 pages. Or is it just that all the WSUS 2 stuff is being removed and nobody has made a WSUS 3 tools page. -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
|
|
|
|
On Wed, 30 May 2007 16:20:01 -0500, "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> wrote:
[Quoted Text] >"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message >news:qipr53tjfgut5ju4ng7jv0see1137kphnn[ at ]4ax.com... > >>>Here's the 'old' download page you are looking for. >>> >>> http://www.microsoft.com/technet/windowsserver/wsus/20/downloads/tools/default.mspx> >> Thanks Jeff, I have bookmarked the page but have to wonder why the tools >> are no >> longer available for WSUS 3. > >The tools have not yet been /rewritten/ for WSUS 3, and many of those tools >are now incorporated into the WSUS 3 product. Which is why a WSUS 3 tools page would be useful. Even if the only tool was the Client Diag tool as it is such an important tool for trouble shooting the WSUS system. > >Remember, this was an unsupported toolset to begin with. -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
|
|
"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message news:erls53lvedcijl5k63ti4qvvp28ivbg011[ at ]4ax.com...
[Quoted Text] >>> Thanks Jeff, I have bookmarked the page but have to wonder why the tools >>> are no longer available for WSUS 3.
>>The tools have not yet been /rewritten/ for WSUS 3, and many of those >>tools >>are now incorporated into the WSUS 3 product.
> Which is why a WSUS 3 tools page would be useful.
Dave.... there are *no* tools to put on a such a page. I'm sure that when there are such tools available, that's exactly what will be done.
> Even if the only tool was the > Client Diag tool as it is such an important tool for troubleshooting the > WSUS > system.
A whole page for one tool?
The Client Diagnostic Tool continues to be available from it's permanent location in the Download Center.
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
The CDT is not WSUS version specific. It emulates the behavior of the WUA to determine if the client is configured and behaving correctly in any WSUS environment. To my knowledge there is no difference in behavior, within the scope of the WUA, between v5.8 and v7.0 of the WUA -- except that the CDT doesn't properly identify the v7.x WUA as a WSUS 3.0 client.
But then, again, the CDT was never part of unsupported API Samples and Tools kit. It's actually a supported utility.
-- 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 .....
|
|
|
[Quoted Text] >> Even if the only tool was the >> Client Diag tool as it is such an important tool for troubleshooting the >> WSUS >> system. > >A whole page for one tool?
A whole page for the "first" tool with others to follow.
I do not understand why you do not think it worthwhile to provide a download link on the WSUS 3 page to a tool that you tell people to download on a daily basis and which is quite difficult to find unless you have a book marked link already. The client diagnostic tool may have been first written for WSUS 2 but is not revision specific of itself.
> >The Client Diagnostic Tool continues to be available from it's permanent >location in the Download Center. > >http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE >
>The CDT is not WSUS version specific. It emulates the behavior of the WUA to >determine if the client is configured and behaving correctly in any WSUS >environment. To my knowledge there is no difference in behavior, within the >scope of the WUA, between v5.8 and v7.0 of the WUA -- except that the CDT >doesn't properly identify the v7.x WUA as a WSUS 3.0 client. > >But then, again, the CDT was never part of unsupported API Samples and Tools >kit. It's actually a supported utility. -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
|
|
"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message news:dra2639mup22d5dr49nehk3me91g0vhgtt[ at ]4ax.com...
[Quoted Text] >>> Even if the only tool was the >>> Client Diag tool as it is such an important tool for troubleshooting the >>> WSUS >>> system.
>>A whole page for one tool?
> A whole page for the "first" tool with others to follow.
You assume there are "others to follow"?
> I do not understand why you do not think it worthwhile to provide a > download > link on the WSUS 3 page to a tool that you tell people to download on a > daily > basis
I never said it wouldn't be worthwhile to put a *link* on the WSUS 3 page to download the CDT. You asked about an entire downloads page for WSUS 3. I said it was pointless to create a whole *page* for one link.
Furthermore, if you look at the downloads page for WSUS 3, you'll find that the *only* actual direct link on that page is for the WSUS3 installer package itself. *Nothing* is linked from that page, anyway!
Otherwise, everything else is available from the download center.
> and which is quite difficult to find unless you have a bookmarked link > already.
Given that I've "..[told] people to download on a daily basis" this tool, and I've rarely posted the actual link myself, it would seem that a large number of people have successfully found the tool.
What's unfortunate, as I've just found out, is that apparently the Technet people have redirected the link in my sig back to the WSUS3 home page.
> The client diagnostic tool may have been first written for WSUS 2 but > is not revision specific of itself.
It's not 100% compliant with WSUS3/WUA v7.0 either == have you noticed that it reports the v7 WUA as a WSUS 2.0 client???
I'm sure that if/when the tool is updated to recognize the v7 WUA as a WSUS 3.0 client (and any other anomalies I've not noticed), that it will then be published as a WSUS3 tool. But right now, it's not a WSUS3 tool == but it *works* for the purposes intended.
Furthermore, 95% of the issues the CDT was designed to detect, or has detected, have now either been eliminated by the use of the configuration wizard, or by the addition of health monitoring in the product itself.
-- 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 .....
> >> >>The Client Diagnostic Tool continues to be available from it's permanent >>location in the Download Center. >> >>http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE >> > > >>The CDT is not WSUS version specific. It emulates the behavior of the WUA >>to >>determine if the client is configured and behaving correctly in any WSUS >>environment. To my knowledge there is no difference in behavior, within >>the >>scope of the WUA, between v5.8 and v7.0 of the WUA -- except that the CDT >>doesn't properly identify the v7.x WUA as a WSUS 3.0 client. >> >>But then, again, the CDT was never part of unsupported API Samples and >>Tools >>kit. It's actually a supported utility. > -- > Dave Mills > There are 10 type of people, those that understand binary and those that > don't.
|
|
Lawrence Garvin (MVP) wrote:
[Quoted Text] There does seem to be something peculiar going on here, though. Searching the download center for "WSUS" does not return this link.
Harry.
|
|
|
|
|