Help - Search - Members - Calendar
Full Version: WUS Beta
Neowin Forums > Windows Support > Windows NT4/2000/2003/2008 Server
IPv6
I was just wondering if anyone is beta testing Windows Update Service (WUS) from Microsoft?

I finally got some time to test it out, it has such a nice interface and it has mature well beyond what SUS is. So I am reading this 86 pages deployment guide for WUS and created some groups.

The problem is that I am using server-side targeting rather then forcing clients to use this WUS server via GPO as I still have SUS 1.0 w/ sp1 running on the production server. My all computer group has 0 computers and my new IT group has 0 computers. This documentation said on page 31 step 3:

QUOTE
use WUS to load computers into groups or use whatever means you are using for pointing clients to WUS to automatic this task.


Well that isn't quite clear to me ... and I definitely do NOT want to use any type of GPO at the moment since it is only beta. Any one know how to add computers into WUS and its groups?

Thanks.
beacon
Hey IPv6

From what i understand you still need to use GPO to point the client to the WUS server and all the other options as per SUS. Once you do that your ALL Computers group will become filled with computers you can create groups for in WUS.
From what i can see these groups are purely for viewing and reporting type stuff.

cheers
b smile.gif
JJ6829
You will need to use the GPO, or local machine policy to point the clients to use ur WUS server still. The first time they successfully authenticate with the WUS server, they will be added.

If all the web services werent installed on port 80, in the GPO where you specify intranet and statitistics server, make sure you append the port to the end.

IPv6
yeah, I end up creating a test OU and moving my workstation and the WUS server into that OU, then creating a GPO for WUS.

QUOTE
From what i can see these groups are purely for viewing and reporting type stuff


The groups or target groups are used for more then just viewing and generating reports, in the whitepaper and my own WUS research write up:

QUOTE(my research article)
The benefit of having target groups is to test updates.  You can have an accounting and human resources groups.  From these two groups, 1 workstation from each group can be put into a pilot group.  The pilot group will get the updates first and if all works well, the updates can be push to everyone else.  Unlike SUS, everyone gets the update.


So far WUS seems extremely cool, I like the new interface and they way they changed things for the better. However, it seems that they have dropped support for Office 2000 in the BETA version of WUS. There are still about 20 people in our corp. office that uses Office 2000 (including myself), which is sad but I think they should reconsider supporting that product.

Another thing I like to see is having the breakdown which product I want to download. For example, they have the 'Windows 2003 family' product, which include small business. Personally, I don't want to download small business stuff, I just want windows 2003 standard and all patch related to it.
garethevans1986
Did anybody have any problems with remote desktopping into the server after applying the .NET framework and BITS patches?

ChocIST
IPv6
QUOTE(ChocIST @ Jan 7 2005, 15:46)
Did anybody have any problems with remote desktopping into the server after applying the .NET framework and BITS patches?

ChocIST
[right][snapback]585249600[/snapback][/right]



Nope, I am able to RDC into the console of the server (0) and into console 1 and 2 without any problem.
garethevans1986
I had to uninstall the BITS patch and reboot for RDC to come back. But its now working fine.

ChocIST
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.