Systems Management

I just came across this same issue... my boss asked me to incorporate the Office 2007 Help Tab into our 2007 deployment via SCCM. (See, you're not the only one. [;)]) Even though the default ALLUSERS setting is 1 (=per machine installation), it only shows up for the profile that ran the install. When installed via SCCM, that would be SYSTEM, so you'll never see it. However, the one-and-only DLL is registered under LOCAL MACHINE, so there's no roadblock there.

So, I installed it manually, found and exported the only registry keys that are user-specific, imported as a new user, and voilà, the Help Tab shows up. I pasted the exact keys below, so you'll need to import them for each user that needs to use the Help Tab; I plan to deploy via login script.

I too tried the Search Commands add-in a while back, with the same results you had. I might go back and try this method for that as well. If I do, I'll post my results here. I've got higher hopes for this li'l add-in, though.

Enough gabbing, here's what you need:
[HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\AddIns\MicrosoftOfficeHelpTab.Connect]
"FriendlyName"="Microsoft Office 2007 Help Tab"
"Description"="Adds a Help tab to Microsoft Office"
"LoadBehavior"=dword:00000003

[HKEY_CURRENT_USER\Software\Microsoft\Office\PowerPoint\Addins\MicrosoftOfficeHelpTab.Connect]
"FriendlyName"="Microsoft Office 2007 Help Tab"
"LoadBehavior"=dword:00000003
"Description"="Adds a Help tab to Microsoft Office"

[HKEY_CURRENT_USER\Software\Microsoft\Office\Word\Addins\MicrosoftOfficeHelpTab.Connect]
"FriendlyName"="Microsoft Office 2007 Help Tab"
"LoadBehavior"=dword:00000003
"Description"="Adds a Help tab to Microsoft Office"

I had the same issue with deploying Office 2007 and the help tab add-in by SCCM.
Each of them was added as program separately and they are in the same package.

I just changed the environment option of the help tab add-in to "run with user's rights" and it started functional.

matsui,
That's all fine... as long as your users are local admins. Ours are not, and you couldn't pay me to change that. Well... ok, you could, but it would be a lot, and I wouldn't like it.

Seriously, all of our installs are "run as admin", so finding little tweaks like this are important. I did try installing this under a limited user on the off chance that it might work, but no dice.

HI folks,

I have a requirement of customising microsoft outlook 2010 with pinned icon of outlook 2010 in win7.I tried doing it through msp by additing one more shortcut of outlook 2010 and giving the target location as [APPDATAFolder]\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar.after running the msp the shortcut din't appear in the taskbar,but wa present in the task bar folder and the status was pinned.I tried another method of exporting the[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Taskband] registry key.but after running the exported key from the the shortcut again din't appear on the taskbar.but again when i right clicked the outlook shortcut i could found the unpinning option.
Kinldy tell us if we can customise the pinned outlook 2010 using oct or some other method

Hi
Same problem here.
Has anyone found the reghack to get "Office Labs Search Command" tab to work on ALL Users?
Thanks

Kory

Ok
Looking at the MSI itself, a reghack itself probably wont fix it.
The MSI probably needs to be rearranged, as it seems to be copying bunch of files to the users profile.
Anyway, i might have to stick with the Active Installation method.
Kory

Hi,

I am new to the SCCM packaging and have the same task to deploy Microsoft Office 2007 Help Tab as a add on, but facing difficulties in setting up the command line in the program...

I know it soild look like "msiexec.exe /q ALLUSERS=2/m....... but stuck at finding the MIF file nam for the package....

Can some one help me in finding the MIF file name please....

Thanks in Advance....

- MSIEXEC is used to execute MSIs not MIFs.
- The '/m' argument is unknown to me
- With no qualifier, the '/q' argument runs the install with a full UI which is not what you want for an SCCM push.
- I'd go with ALLUSERS=1 for an SCCM push
MSIEXEC /I [path_to_and_name_of_MSI] /QN ALLUSERS=1 /L*V %TEMP%\[name_of_log_file]