Office Communicator Woes With Vista February CTP

Published Tuesday, March 07, 2006 4:32 PM

I’d like to think I can solve any problem. However, getting Office Communicator to install on the February CTP of Vista has got me quite perplexed! It will get all the way to the end of the install, then say it encountered an “error” and roll back. You know, that installation progress bar in reverse we all hate to see? I even tried to run the .msi in verbose logging mode, but the User-Mode protection in Vista wont let me create the log file. A plain ‘ol text file! Come on! Application compatibility mode and “run as administrator” were no help either. Has anyone else run in to this or has anyone got this to install successfully? We are running the web-based Communicator at my company but it just isn't the same!

Share this post:                                       
by Chris Haaker

Comments

# Scott said on Wednesday, March 15, 2006 9:13 AM

I don't have a solution, but I do have the same problem...

I have been stuck using the web version of LCS for the past week.

# Scott said on Friday, March 17, 2006 5:05 PM

Found the fix... perform the steps below, reboot, and then the install will work...

Disable User Account Protection (UAP)

Once you have installed the February CTP and set up an every day user account, one of the first things you will notice is that you have almost no rights to do anything administrator related on your system. Disabling this is purely up to you but if you find UAP is getting in your way, or some applications refuse to run because of it, you may want to take a look at this. Here are the instructions:
NOTE: You should be logged in as Administrator to do this, or you could run the Microsoft Management Console (MMC) elevated.

Press WinKey (the flag key on your keyboard) + R and type “secpol.msc”. (Without the quotes). If asked to permit Microsoft Management Console to run, allow it.
In the Local Security Settings window, in the left hand pane, navigate to “Security Settings, Local Policies, Security Options”.
In the pane to the right, scroll all the way to the bottom.
Set the first two User Account Protection items to “No Prompt”, and “Disabled” on the remaining three items.
Close the Microsoft Management Console (MMC), and if you are asked to save the settings for “Console1”, press “No”.
Reboot or log off and log back in to enforce the new settings; or alternatively open an elevated Command Prompt and type “gpupdate /force” (without the quotes), and then press Enter.
Alternatively, you can also do this to disable UAP:

Press WinKey+R on your keyboard.
Paste the following into the Run box, including the quotation marks: “C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f”
Press Enter. If asked for permission to perform this action, click “Allow”.
Reboot the system.
To renable UAP after applying this method:

Press WinKey+R on your keyboard.
Paste the following into the Run box, including the quotation marks: “C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f”
Press Enter.
Reboot the system.

Found info on http://digitalfive.org