N
Nick van Ogtrop-de Ruiter
Guest
I have a client who, for reasons of testing, does not want to tamper with
their existing WSUS v2 environment. They are wanting to install the WSUS v3
application on a test server, but want to host the database on their current
SQL production server (SQL Server 2005).
The installation in this manner fails, and I have the feeling that it has to
do with the fact that there already is a database named SUSDB on the SQL
server (serving the current WSUS v2 environment).
I suspect that WSUS v3 also only wants to name its database SUSDB,
regardless of whether or not SQL Server or WID is used, and as a result an
existing database with that name will cause the installation to fail.
Can anyone confirm if this is the case?
their existing WSUS v2 environment. They are wanting to install the WSUS v3
application on a test server, but want to host the database on their current
SQL production server (SQL Server 2005).
The installation in this manner fails, and I have the feeling that it has to
do with the fact that there already is a database named SUSDB on the SQL
server (serving the current WSUS v2 environment).
I suspect that WSUS v3 also only wants to name its database SUSDB,
regardless of whether or not SQL Server or WID is used, and as a result an
existing database with that name will cause the installation to fail.
Can anyone confirm if this is the case?