Hello,

we have to redistribute SQL Server 2005.
Is there a problem, to change the productcode of the msi-files with
tools like orca?
Or is this not supported by microsoft?

Changing the productcode may affect the ability of Windows to apply security
updates to the SQL 2005 Express package.

"WebMan" wrote:

> Hello,
>
> we have to redistribute SQL Server 2005.
> Is there a problem, to change the productcode of the msi-files with
> tools like orca?
> Or is this not supported by microsoft?
>
>

DLee65 schrieb:

> Changing the productcode may affect the ability of Windows to apply security
> updates to the SQL 2005 Express package.
>

But Updates can be applied with the upgradecode of the msi-file.
The Problem is. We install the SQL Server 2005 with an own
setup-programm.
We do some things before, call the msiexec like:

msiexec.exe /i SqlRun_SQL.msi /qb /l*v
"%temp%\sql2005log\SqlRun_SQL.log" INSTANCENAME=DATEV_SV_SE01_05
ADDLOCAL=SQL_Engine

Wen we deinstall, we want to manage this with the following command:

MsiExec.exe /X {F88C8A8D-6D35-4580-9EB7-315D563E10AF} /qb

We don't want to uninstall other foreign instances from other software
vendors.

For this we must determine some productcodes, we can use for
installation and deinstallation.

Are there any known problems with this method?