Re: WSUS Install on second (child) Server

"Banktech" <> wrote in message
news:dc23f2eb-cc0d-4c66-afff-...
> Hey there first time poster here, I am installing a WSUS 3.0 SP1
> server and trying to select the option of "use an existing database
> server on a remote computer" Where you enter the server name\instance
> name. From what I read the instance name if you chose the simple mssql
> is MICROSOFT##SSEE. I enter (servername\MICROSOFT##SSEE) and it says
> it can't connect because it doesn't exist or no access.
>
> Any suggestions please would greatly be appreciated.

You've either misread, or misunderstood.

1. A remote database server cannot be an instance of Windows Internal
Database the string "MICROSOFT##SSEE" specifically refers to an installed
instance of the Windows Internal Database, so that string is only valid on
the *local* machine.

2. A remote database server must use SQL Server 2005 SP1
(Workgroup/Standard/Enterprise), so the "use an existing database server on
a remote computer" would either be just the MACHINENAME (if the database
service is installed on the default instance), or MACHINENAME\INSTANCENAME
where INSTANCENAME is the named instance of an installation of SQL Server
2005 SP1 (Workgroup/Standard/Enterprise).

[Suggestion] If you're attempting to install WSUS with a remote database
server, do the following:

1. Read the entire WSUS Deployment Guide (and other preliminary
documentation such as Overview, Release Notes, and Getting Started Guide).

2. Perform a TEST installation using a LOCAL instance of the Windows
Internal Database, so that you can TEST all other aspects of the
implementation -- synchronization, configuration, and most notably,
successful client connectivity to your test server.

3. After successfully testing WSUS in a single-server installation, and thus
being familiar with what to expect, then install WSUS using a remote
database server -- which will introduce a whole new set of connectivity
issues to validate (and possibly troubleshoot).


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Banktech" <> wrote in message
news:f5792ee9-4396-46b5-9540-...

> I am installing a WSUS server at a remote location to be able
> to send updates to it's local PC's to help not bog down the network.
> I will be doing this for various sites.

> But I was going to have them point to the main one here
> for it's database info AND updates.

With all due respect.. this is what happens when you don't read the product
documentation before acting. :-)

> Is that possible in an MS SQL Express or Windows Internal Database?

It's not possible in *any* scenario involving WSUS. Each and every WSUS
Server must have it's own dedicated database, and this requirement is
plainly and clearly documented in the product documentation.

It's also not possible to share the update content store either. Each
downstream server will need it's own local volume for storing content files,
and the space allocated for that store should be equal to or greater than
the maximum known consumption of the primary server's current store. I'd
suggest adding 50% to the consumption of the current upstream server's store
to allow for growth.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Banktech" <> wrote in message
news:8701beea-1e64-4986-b847-...

WHo said I didn't read it, and besides that during the install there
are options for such things.

The fact that you're even asking these questions, or that you're
misinterpreting the fields in the installer pretty much says it all. Not
understanding the options can only be a result of *assuming* you think what
they mean, instead of having actually verified their purpose in the
installation guides.

> And when I said I wanted them to
> go to the main server for its updates
> as well I meant to download them
> with its own local storage obviously.

My misunderstanding. I apologize. Your statement was not well written, and
easily misinterpreted, and when combined with the idea of sharing the same
database in the same sentence would naturally be interpreted that you were
trying to share the database AND the files.

> Get off your high horse and don't be suck a dick.

That kind of language and attitude is absolutely unnecessary in this forum.

> I hate people like you in IT I really do.

O.K., but hating the people you need to get help from isn't a very
constructive attitude, though, is it?

So, if you'd like *HELP*, then here are my suggestions:

1. Go back and *READ* the documentation, cover to cover, every section every
page:
-- the Overview
-- the Getting Started Guide
-- the Deployment Guide

2. After you've *READ* the documentation, I'll be happy to answer any
questions you might have -- provided you can lose the nasty attitude.

Otherwise, your options will be limited to:
1. Figuring it out for yourself.
2. Writing a check to Microsoft Product Support Services (who also won't put
up with such attitudes).





--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin