/build/static/layout/Breadcrumb_cap_w.png

Office COmmunicator

Hi All

Trying to deploy Office Communicator 2007 and also drop in the reg key to stop the first run tour from playing. I was working through a Transform using Wises and it kept throwing a wobbly saying it was not licensed and had to be uninstalled and reinstalled. finally I remembered it was a MS thing and needs to be tweaked using there "Office Customization Tool" I have already done that for a trial push of Outlook 2k7 and it produces a really bloated Transform (a patch they call it).

I just want to deploy it via SMS and drop in the reg key nothing else too fancy, mainly because of time constraints I don't want to mess around with the OCT

Help please

0 Comments   [ + ] Show comments

Answers (8)

Posted by: turbokitty 15 years ago
6th Degree Black Belt
1
I wish I could remember more about that one.. it was quite awhile ago (and 4 clients ago). I only remember that MSI being a massive PIA and that I was working with Microsoft's Communicator team to figure it out. The conclusion we came to was that they screwed up that MSI pretty badly.
Posted by: turbokitty 15 years ago
6th Degree Black Belt
0
Did you check the packaging KB?

Also know that a lot of Communicator settings are controlled through GPO.
Posted by: blade2 15 years ago
Blue Belt
0
Yes Thanks TK I saw your notes and the additional one that mentions the reg key which is how I found out about the key needed; if I try and tweak it at all with a transform it errors out. Further reading says it is part of office 2k7 suite therefore any tweaks needs to be done via the OCT.

Edit: I guess will do any of the other stuff through GPO.

Thanks for your help TK
Posted by: blade2 15 years ago
Blue Belt
0
ORIGINAL: turbokitty

... I only remember that MSI being a massive PIA ...



Really! Do tell. I hope it was an older version and they have fixed it by now. It is something my company plans deploy carte blanch, it would be funny if that turned out to be a disaster...
Posted by: anonymous_9363 15 years ago
Red Belt
0
I hope it was an older version and they have fixed it by now. [Everly Brothers sing...]"Dree-ee-ee-ee-eam, dream, dream, dream, dree-ee-ee-eam..."
Posted by: dinozilla 15 years ago
Orange Senior Belt
0
ORIGINAL: blade2

Hi All

Trying to deploy Office Communicator 2007 and also drop in the reg key to stop the first run tour from playing. I was working through a Transform using Wises and it kept throwing a wobbly saying it was not licensed and had to be uninstalled and reinstalled. finally I remembered it was a MS thing and needs to be tweaked using there "Office Customization Tool" I have already done that for a trial push of Outlook 2k7 and it produces a really bloated Transform (a patch they call it).

I just want to deploy it via SMS and drop in the reg key nothing else too fancy, mainly because of time constraints I don't want to mess around with the OCT

Help please



the registration details is actually recorded somewhere in the registry, under Microsoft\Communicator (can't remember HKCU/HKLM). if you check, before applying transform, that value for the registration(some PID thingy) is referred to a property defined in MSI, once you applied transform, the value goes null/none. My way of solving this is to apply the PID directly to the registry table.
Posted by: blade2 15 years ago
Blue Belt
0
oops, a momentary lapse of reason...
Posted by: Killragtshirts 14 years ago
Orange Belt
0
Just been dealing with too today...O2K07 Communicator R2

Under HKLM\SOFTWARE\Microsoft\Communicator\3.5\Registration

ProductID looks to a Value [PID] and In the property table ProductID = NONE.

It gets mentioned a fair bit on the net. Including here: http://ocs2008.blogspot.com/
Personally the fixes mentioned didnt really suit my situation so...

(1) I installed the msi without a transform and grabbed the Product ID
(2) Created a transform
(3) In the Proerty Table I added in the Product ID I grabbed in step 1
(4) Under the above reg entry I changed the [PID] Value to [ProductID]

Sorted....
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ