ProductID in MS Office Communicator 2005
Gents,
Need help here.
I build a transform on the communicator.msi
after months just right before rollout,
the application fails to launch because of expired license, later was found that the entry of registration in registry is missing (but it is there if you install using its own msi)
The transform does not much, therefore I am confuse now how to work around.
After test, there is 2 key name: ProductID and DigitalProductID
while the DPID are the same for all from the same msi, PID is different, but as said, it is not generated properly if using transform.
Please help.
Need help here.
I build a transform on the communicator.msi
after months just right before rollout,
the application fails to launch because of expired license, later was found that the entry of registration in registry is missing (but it is there if you install using its own msi)
The transform does not much, therefore I am confuse now how to work around.
After test, there is 2 key name: ProductID and DigitalProductID
while the DPID are the same for all from the same msi, PID is different, but as said, it is not generated properly if using transform.
Please help.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
AB
17 years ago
Creating a Transform for this MSI using Wise writes the Property "ProductID"="None" in to the installation.
Delete this property - save your MST - and the Property is written back again...
I used an evaluation copy of Camwood's AppEditor to remove this Property from the MST permanently.
Then your deployment will write the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\1.0\Registration]
"ProductID"="76775-270-*******-*****"
... rather than "ProductID"="None"
To fix those deployments that now show the licence expiration error just add the key above - you only need the following digits "76775-270" or replace the *'s with zero's - it might be worth doing a test install of the MSI only to check the ProductID is correct...
The key "DigitalProductID" is also written to the above location - installing the SP1 Patch deletes the value of this key but this doesn't seem to have any detrimental effect.
Set the system clock to "the future" and check the 120 day trial period error doesn't appear.
Regards,
Al
Delete this property - save your MST - and the Property is written back again...
I used an evaluation copy of Camwood's AppEditor to remove this Property from the MST permanently.
Then your deployment will write the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\1.0\Registration]
"ProductID"="76775-270-*******-*****"
... rather than "ProductID"="None"
To fix those deployments that now show the licence expiration error just add the key above - you only need the following digits "76775-270" or replace the *'s with zero's - it might be worth doing a test install of the MSI only to check the ProductID is correct...
The key "DigitalProductID" is also written to the above location - installing the SP1 Patch deletes the value of this key but this doesn't seem to have any detrimental effect.
Set the system clock to "the future" and check the 120 day trial period error doesn't appear.
Regards,
Al
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
