> On Jun 16, 11:09 am, "Lawrence Garvin \(MVP\)"
> <onsit...[ at ]community.nospam> wrote:
> > "Jake" <J...[ at ]discussions.microsoft.com> wrote in message
> >
> > news:93EF2A9E-B93E-4D5D-B243-153D598C3827[ at ]microsoft.com...
> >
> > > I don't have a dedicated server, but what is the best place to install
> > > this
> > > on?
> >
> > On any machine that can reliably and securely run IIS and a database server,
> > and meets the documented hardware requirements for your expected client
> > load.
> >
> > > I have read yes/no on doing it on DC's,
> >
> > The issue of Domain Controllers is primarly beget by those who are DC
> > purists. The purity of a DC is really only critical in large organizations
> > where the DC is working around the clock, non-stop, doing Domain Controller
> > things. In a small/medium organization, the typical DC sits idle about 90%
> > of the time.
> >
> > There are no issues at all installing WSUS on a Domain Controller in a
> > small/medium size organization (Medium = <= 500 clients)
> >
> > If your only Win2003SP1 system is a DC, that's where you should put WSUS,
> > unless you can arrange to get another machine installed, or you have more
> > than 500 clients in your network. (And, if you have more than 500 clients in
> > your network and you only have one Win2003 machine and it's a DC, then
> > you've got bigger fish to fry than worrying about installingWSUS 2 or WSUS
> > 3!)
> >
> > > and I also want to make sure I can upgrade to version 3 when it is ready.
> >
> > Then you have two requirements:
> > [1] Don't install WSUS 2. Install WSUS 3 *now*. There's absolutely no
> > point in installing a downlevel version of a free product when the newer
> > version is available and still free.
> > [2] If you insist on installing WSUS 2, install it on a Windows Server
> > 2003 SP1 system to ensure the easiest upgrade path to WSUS 3.
> >
> > If you don't have a Windows Server 2003 SP1 system deployed, you cannot
> > upgrade to WSUS 3. (See parenthetical notes above and below.)
> >
> > I would *not* recommend investing the time and effort in installing WSUS 2.0
> > SP1 on a Windows 2000 Server system at this time. You'd serve your
> > organization much better by focusing on upgrading the server operating
> > systems, rather than deploying a new application on an old operating system,
> > which will do nothing except complicate the day when you finally do upgrade
> > the operating system.
> >
> > > Also, one person I ran into had a script that did something on client
> > > startup to clear out the windows update stuff on the client because they
> > > were
> > > not registering on the client.
> >
> > See my previous message for the answer to this question.
> >
> > --
> > Lawrence Garvin, M.S., MCTS, MCP
> > Independent WSUS Evangelist
> > MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...> >
> > Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/...> >
> > And, almost everything else is at
http://wsusinfo.onsitechsolutions.com> > ....
>
> Hi,
> What is the post about the script issue and clients not registering?
>
>