New WSUS3 install on W2k3 Domain Controller

I'm using a W2k3 server for the WSUS SQL database and was told to install
WSUS with admin console on a W2k3 domain controller. Is this possible? I'm
receiveing access denied error during setup when trying to connect to
database.
No version of WSUS has been used in the domain yet. I read this:

Remote SQL scenario limitations
• You cannot use a server configured as a domain controller for either the
front end (FE) or the back end (BE) of the remote SQL pair.

• You cannot use a server running as a Terminal Services server for the
front end of the remote SQL pair.

• You cannot use Windows Internal Database for database software on the
back-end server.

• Both the front-end and the back-end servers must be joined to an Active
Directory domain.

From this site:
http://technet2.microsoft.com/window....mspx?mfr=true

Does this apply to a new install?

Forwarded to WSUS newsgroup via crosspost.
--
~PA Bear

Bob wrote:
> I'm using a W2k3 server for the WSUS SQL database and was told to install
> WSUS with admin console on a W2k3 domain controller. Is this possible? I'm
> receiveing access denied error during setup when trying to connect to
> database.
> No version of WSUS has been used in the domain yet. I read this:
>
> Remote SQL scenario limitations
> • You cannot use a server configured as a domain controller for either
> the
> front end (FE) or the back end (BE) of the remote SQL pair.
>
> • You cannot use a server running as a Terminal Services server for the
> front end of the remote SQL pair.
>
> • You cannot use Windows Internal Database for database software on the
> back-end server.
>
> • Both the front-end and the back-end servers must be joined to an
> Active
> Directory domain.
>
> From this site:
> http://technet2.microsoft.com/window....mspx?mfr=true
>
> Does this apply to a new install?

Bob wrote:

> I'm using a W2k3 server for the WSUS SQL database and was told to install
> WSUS with admin console on a W2k3 domain controller. Is this possible? I'm
> receiveing access denied error during setup when trying to connect to
> database.

According to this:

<http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?mfr=true>

you can't put the back end on a domain controller but it doesn't say anything
about the front end, so I would presume that is supported. Someone else may be
able to give you a more definite answer.

What SQL server software are you using on the back end? Have you configured it
to allow remote connections? Is the account you're using to install WSUS an
administrator on the back end server, i.e., a domain admin?

Harry.

> Bob wrote:

>> I'm using a W2k3 server for the WSUS SQL database and was told to install
>> WSUS with admin console on a W2k3 domain controller. Is this possible?

No.

>> I'm
>> receiveing access denied error during setup when trying to connect to
>> database.
>> No version of WSUS has been used in the domain yet.

If you're trying to install the front-end of WSUS on a domain controller,
that's the reason why.

>> Remote SQL scenario limitations
>> • You cannot use a server configured as a domain controller for either
>> the
>> front end (FE) or the back end (BE) of the remote SQL pair.

Well.. there ya have it... but ya posted anyway, and tried it anyway. What..
you don't trust the documentation? :-)

>> From this site:
>> http://technet2.microsoft.com/window....mspx?mfr=true
>>
>> Does this apply to a new install?

It applies to *ANY* install. You cannot do it. Period.


--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/pr...2-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Never sure until I double check, twice, and try to do it three times just
in case. I have since tried to install on a different domain member server,
(not DC), but am still getting the same error,
(DBNETLIB)(ConnectionOpen (Connect()).)SQL Server does not exist or access
denied.

THe SQL admin is going to double check the permissions later this morning...

Any ideas on wher to start? Thanks for the help!



"Lawrence Garvin (MVP)" wrote:

> > Bob wrote:
>
> >> I'm using a W2k3 server for the WSUS SQL database and was told to install
> >> WSUS with admin console on a W2k3 domain controller. Is this possible?
>
> No.
>
> >> I'm
> >> receiveing access denied error during setup when trying to connect to
> >> database.
> >> No version of WSUS has been used in the domain yet.
>
> If you're trying to install the front-end of WSUS on a domain controller,
> that's the reason why.
>
> >> Remote SQL scenario limitations
> >> • You cannot use a server configured as a domain controller for either
> >> the
> >> front end (FE) or the back end (BE) of the remote SQL pair.
>
> Well.. there ya have it... but ya posted anyway, and tried it anyway. What..
> you don't trust the documentation? :-)
>
> >> From this site:
> >> http://technet2.microsoft.com/window....mspx?mfr=true
> >>
> >> Does this apply to a new install?
>
> It applies to *ANY* install. You cannot do it. Period.
>
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)
> https://mvp.support.microsoft.com/pr...2-D095EB07B36E
>
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
>
> And, almost everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>

STRANGE. When I put in the servername without the instance name, it connected
and began the installation... although in the window it indicates
"ServerName/Instancename"... And now automagically, there is a "SUSDB"
database on the SQL server... Guess you can't create your own database and
point WSUS to it, eh?

"Bob" wrote:

> I'm using a W2k3 server for the WSUS SQL database and was told to install
> WSUS with admin console on a W2k3 domain controller. Is this possible? I'm
> receiveing access denied error during setup when trying to connect to
> database.
> No version of WSUS has been used in the domain yet. I read this:
>
> Remote SQL scenario limitations
> • You cannot use a server configured as a domain controller for either the
> front end (FE) or the back end (BE) of the remote SQL pair.
>
> • You cannot use a server running as a Terminal Services server for the
> front end of the remote SQL pair.
>
> • You cannot use Windows Internal Database for database software on the
> back-end server.
>
> • Both the front-end and the back-end servers must be joined to an Active
> Directory domain.
>
> From this site:
> http://technet2.microsoft.com/window....mspx?mfr=true
>
> Does this apply to a new install?

"Bob" <> wrote in message
news:3995828C-03D3-4C5F-BA16-...
> Never sure until I double check, twice, and try to do it three times
> just
> in case.

Gotcha! ;-)

> I have since tried to install on a different domain member server,
> (not DC), but am still getting the same error,
> (DBNETLIB)(ConnectionOpen (Connect()).)SQL Server does not exist or access
> denied.

The most useful thing I can do at this point is direct you to Appendix B of
the WSUS Deployment Guide, to make sure you're compliant with every one of
the prerequisites necessary to install WSUS3 with a back-end database
server.

> THe SQL admin is going to double check the permissions later this
> morning...

That would be the next place to start, after Appendix B. Most likely cause
is that the logged on (installation) account on the front-end server doesn't
have permissions to the database server. Two things need to be provided:
[a] The account needs to have access to the database server.
[b] The account needs to have the default database set to 'master'.
[c] The account needs to have permissions to CREATE a database.

While the explicit permissions required are not identified in Appendix B, I
can tell you that those are the basic perms required for the front-end
install account to be able to create the back-end WSUS database.


--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/pr...2-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Now VERY strange... I installed a downlevel WSUS server on a DC. I was
mistaking the "Instancename" as the actual name of the database, which I was
trying to create on my own, not realizing that WSUS must name the database
itself.

"Bob" wrote:

> STRANGE. When I put in the servername without the instance name, it connected
> and began the installation... although in the window it indicates
> "ServerName/Instancename"... And now automagically, there is a "SUSDB"
> database on the SQL server... Guess you can't create your own database and
> point WSUS to it, eh?
>
> "Bob" wrote:
>
> > I'm using a W2k3 server for the WSUS SQL database and was told to install
> > WSUS with admin console on a W2k3 domain controller. Is this possible? I'm
> > receiveing access denied error during setup when trying to connect to
> > database.
> > No version of WSUS has been used in the domain yet. I read this:
> >
> > Remote SQL scenario limitations
> > • You cannot use a server configured as a domain controller for either the
> > front end (FE) or the back end (BE) of the remote SQL pair.
> >
> > • You cannot use a server running as a Terminal Services server for the
> > front end of the remote SQL pair.
> >
> > • You cannot use Windows Internal Database for database software on the
> > back-end server.
> >
> > • Both the front-end and the back-end servers must be joined to an Active
> > Directory domain.
> >
> > From this site:
> > http://technet2.microsoft.com/window....mspx?mfr=true
> >
> > Does this apply to a new install?

Forwarded to WSUS newsgroup again. [@Bob => Please post all further replies
to microsoft.public.windows.server.update_services.]
--
~PA Bear

Bob wrote:
> Now VERY strange... I installed a downlevel WSUS server on a DC. I was
> mistaking the "Instancename" as the actual name of the database, which I
> was
> trying to create on my own, not realizing that WSUS must name the database
> itself.
>
> "Bob" wrote:
>
>> STRANGE. When I put in the servername without the instance name, it
>> connected and began the installation... although in the window it
>> indicates
>> "ServerName/Instancename"... And now automagically, there is a "SUSDB"
>> database on the SQL server... Guess you can't create your own database
>> and
>> point WSUS to it, eh?
>>
>> "Bob" wrote:
>>
>>> I'm using a W2k3 server for the WSUS SQL database and was told to
>>> install
>>> WSUS with admin console on a W2k3 domain controller. Is this possible?
>>> I'm
>>> receiveing access denied error during setup when trying to connect to
>>> database.
>>> No version of WSUS has been used in the domain yet. I read this:
>>>
>>> Remote SQL scenario limitations
>>> • You cannot use a server configured as a domain controller for either
>>> the front end (FE) or the back end (BE) of the remote SQL pair.
>>>
>>> • You cannot use a server running as a Terminal Services server for
>>> the
>>> front end of the remote SQL pair.
>>>
>>> • You cannot use Windows Internal Database for database software on
>>> the
>>> back-end server.
>>>
>>> • Both the front-end and the back-end servers must be joined to an
>>> Active Directory domain.
>>>
>>> From this site:
>>> http://technet2.microsoft.com/window....mspx?mfr=true
>>>
>>> Does this apply to a new install?

The fact that you put machine name without instance name there and setup
worked is because the setup is using your default instance on that machine
for setup.

--
Fei Cao
Microsoft, WSUS

This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"PA Bear" <> wrote in message
news:...
> Forwarded to WSUS newsgroup again. [@Bob => Please post all further
> replies to microsoft.public.windows.server.update_services.]
> --
> ~PA Bear
>
> Bob wrote:
>> Now VERY strange... I installed a downlevel WSUS server on a DC. I was
>> mistaking the "Instancename" as the actual name of the database, which I
>> was
>> trying to create on my own, not realizing that WSUS must name the
>> database
>> itself.
>>
>> "Bob" wrote:
>>
>>> STRANGE. When I put in the servername without the instance name, it
>>> connected and began the installation... although in the window it
>>> indicates
>>> "ServerName/Instancename"... And now automagically, there is a "SUSDB"
>>> database on the SQL server... Guess you can't create your own database
>>> and
>>> point WSUS to it, eh?
>>>
>>> "Bob" wrote:
>>>
>>>> I'm using a W2k3 server for the WSUS SQL database and was told to
>>>> install
>>>> WSUS with admin console on a W2k3 domain controller. Is this possible?
>>>> I'm
>>>> receiveing access denied error during setup when trying to connect to
>>>> database.
>>>> No version of WSUS has been used in the domain yet. I read this:
>>>>
>>>> Remote SQL scenario limitations
>>>> • You cannot use a server configured as a domain controller for
>>>> either
>>>> the front end (FE) or the back end (BE) of the remote SQL pair.
>>>>
>>>> • You cannot use a server running as a Terminal Services server for
>>>> the
>>>> front end of the remote SQL pair.
>>>>
>>>> • You cannot use Windows Internal Database for database software on
>>>> the
>>>> back-end server.
>>>>
>>>> • Both the front-end and the back-end servers must be joined to an
>>>> Active Directory domain.
>>>>
>>>> From this site:
>>>> http://technet2.microsoft.com/window....mspx?mfr=true
>>>>
>>>> Does this apply to a new install?
>