Office Communicator wont set the license key when applyinf transfo

Discussion:

(too old to reply)

Johan L

2008-02-05 16:45:01 UTC

Hi!

We're trying to customize the communicator.msi ( 2007 ) for deployment in
our company. The only thing we want to change is the icon placement.

When we create an MST ( in wise package studio ) with this change the
communicator wont start. "The product license may be expired.... Please run
setup again") When we use the original msi we dont get this error.

When we check the register on the machine that wont start the communicator
it reads ;

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\2.0\Registration]
"ProductID"= <blank>
"DigitalProductID"= <blank>

If we export this key from a machine that have installed without the MST and
import on a machine with the error the communicator will start just fine.

The ProductID is unique for each machine installing the communicator.
Appearently theres some custom action in the communicator.msi that wont work
when building an MST file.

Is there any workaround? Can we apply the same ProductID for every machine?

Regards. Johan
Sweden

--
// Johan

Linköping / Sweden

Siegel, Maik

2008-02-05 21:54:22 UTC

Permalink

Hi !

Which Icon Placement do you like to to change ?
Maybe there is another way to change this - Without the need to
customize the Installer Package.

Greets, Maik

Post by Johan L
Hi!
We're trying to customize the communicator.msi ( 2007 ) for deployment in
our company. The only thing we want to change is the icon placement.
When we create an MST ( in wise package studio ) with this change the
communicator wont start. "The product license may be expired.... Please run
setup again") When we use the original msi we dont get this error.
When we check the register on the machine that wont start the communicator
it reads ;
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\2.0\Registration]
"ProductID"= <blank>
"DigitalProductID"= <blank>
If we export this key from a machine that have installed without the MST and
import on a machine with the error the communicator will start just fine.
The ProductID is unique for each machine installing the communicator.
Appearently theres some custom action in the communicator.msi that wont work
when building an MST file.
Is there any workaround? Can we apply the same ProductID for every machine?
Regards. Johan
Sweden
--
// Johan
Linköping / Sweden

Johan L

2008-02-06 07:36:00 UTC

Permalink

Hi!

We just want to move the Microsoft "Office Communicator 2007" icon to the
same place where we put all other managed application icons in our company.
Where our users are used to find there applications.

The only thing I've changed in the MST is this.
--
// Johan

Linköping / Sweden

Post by Siegel, Maik
Hi !
Which Icon Placement do you like to to change ?
Maybe there is another way to change this - Without the need to
customize the Installer Package.
Greets, Maik

Siegel, Maik

2008-02-07 21:43:48 UTC

Permalink

Maybe you could expand the msi-File and just pack it again - without any
changes.
Let´s see if it´s working then ...

Greets, Maik

Post by Johan L
Hi!
We just want to move the Microsoft "Office Communicator 2007" icon to the
same place where we put all other managed application icons in our company.
Where our users are used to find there applications.
The only thing I've changed in the MST is this.
--
// Johan
Linköping / Sweden

Post by Siegel, Maik
Hi !
Which Icon Placement do you like to to change ?
Maybe there is another way to change this - Without the need to
customize the Installer Package.
Greets, Maik

Johan L

2008-02-08 07:28:00 UTC

Permalink

We made a script that copies the icon to our companys standardized location
instead. Safer not to touch the original MSI. Microsoft seems to be "picky"
about this for this application. :-)

Thank you for your time!
--
// Regards Johan

Linköping / Sweden

Post by Siegel, Maik
Maybe you could expand the msi-File and just pack it again - without any
changes.
Let´s see if it´s working then ...
Greets, Maik

Post by Siegel, Maik
Hi !
Which Icon Placement do you like to to change ?
Maybe there is another way to change this - Without the need to
customize the Installer Package.
Greets, Maik

unknown

2010-04-07 15:51:27 UTC

Permalink

When we create an MST ( in wise package studio ) with this change the
communicator wont start. "The product license may be expired.... Please run
setup again") When we use the original msi we dont get this error.

While Creating the Transform Just delete the property
ProductID=none.
It will take from the original MSI and MST changes for this will not be overwritten.

Please check it and confirm if this solution works.

johan_relaco wrote:

Office Communicator wont set the license key when applyinf transfo
05-Feb-08

Hi

We're trying to customize the communicator.msi ( 2007 ) for deployment in
our company. The only thing we want to change is the icon placement.

When we create an MST ( in wise package studio ) with this change the
communicator wont start. "The product license may be expired.... Please run
setup again") When we use the original msi we dont get this error.

When we check the register on the machine that wont start the communicator
it reads ;

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\2.0\Registration
"ProductID"= <blank
"DigitalProductID"= <blank

If we export this key from a machine that have installed without the MST and
import on a machine with the error the communicator will start just fine.

The ProductID is unique for each machine installing the communicator.
Appearently theres some custom action in the communicator.msi that wont work
when building an MST file.

Is there any workaround? Can we apply the same ProductID for every machine?

Regards. Joha
Sweden

--
// Johan

Link??ping / Sweden

Previous Posts In This Thread:

On Tuesday, February 05, 2008 11:45 AM
johan_relaco wrote:

Office Communicator wont set the license key when applyinf transfo
Hi

We're trying to customize the communicator.msi ( 2007 ) for deployment in
our company. The only thing we want to change is the icon placement.

When we create an MST ( in wise package studio ) with this change the
communicator wont start. "The product license may be expired.... Please run
setup again") When we use the original msi we dont get this error.

When we check the register on the machine that wont start the communicator
it reads ;

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\2.0\Registration
"ProductID"= <blank
"DigitalProductID"= <blank

If we export this key from a machine that have installed without the MST and
import on a machine with the error the communicator will start just fine.

The ProductID is unique for each machine installing the communicator.
Appearently theres some custom action in the communicator.msi that wont work
when building an MST file.

Is there any workaround? Can we apply the same ProductID for every machine?

Regards. Joha
Sweden

--
// Johan

Link??ping / Sweden

On Tuesday, February 05, 2008 4:54 PM
Siegel, Maik wrote:

Hi !Which Icon Placement do you like to to change ?
Hi

Which Icon Placement do you like to to change
Maybe there is another way to change this - Without the need t
customize the Installer Package

Greets, Maik

On Wednesday, February 06, 2008 2:36 AM
johan_relaco wrote:

Hi!
Hi

We just want to move the Microsoft "Office Communicator 2007" icon to the
same place where we put all other managed application icons in our company.
Where our users are used to find there applications.

The only thing I've changed in the MST is this.

--
// Johan

Link??ping / Swede

"Siegel, Maik" wrote:

On Friday, February 08, 2008 2:28 AM
johan_relaco wrote:

We made a script that copies the icon to our companys standardized location
We made a script that copies the icon to our companys standardized location
instead. Safer not to touch the original MSI. Microsoft seems to be "picky"
about this for this application. :-)

Thank you for your time

--
// Regards Johan

Link??ping / Swede

"Siegel, Maik" wrote:

Submitted via EggHeadCafe - Software Developer Portal of Choice
BizTalk: Writing and using a custom referenced functoid.
http://www.eggheadcafe.com/tutorials/aspnet/f843db77-a775-415e-bd08-71c2b1127e40/biztalk-writing-and-usin.aspx