View Connection Server 4.5 on Server 2008 R2 Std - Won't Install

[six4rm]

Hi,

I've just built a new VM of Server 2008 R2 Std and am trying to install View 4.5 Connection Server. I'm not trying anything special with the install, it's a next, next, next install of Connection Server. I'm getting the following error...

"Error 1720. A script required for this install to complete could not be run. Custom action VM_AdamLoadVdiSchemaPreReqs script error -2147024894 , : Line 16, Column 1,"

Any ideas?

[eeg3]

Are you running the installer as Administrator?

____________

blog.eeg3.net | Useful VMware-related Links

If you found this or any other post helpful, please consider the use of the Helpful/Correct buttons to award points.

[six4rm]

I am logged on as a Domain Admin, but also right-clicking and running as Administrator.

I'm using VMware-viewconnectionserver-x86_64-4.5.0-293049.exe, it being a 64-bit server and all.

If you look at the attached screenshot you can see the point that it is failing.

[six4rm]

I've managed to get it installed. It was actually an issue with Windows rather than VMware. When looking at Server Manager within Windows both the Roles and Features sections were erroring. On checking Event Viewer there were loads of errors showing...

Faulting application name: TrustedInstaller.exe

Installing the below update resolved the issue within Server Manager and I have now been able to install Connection Server.

http://support.microsoft.com/kb/947821

[fejf]

Just FYI:

I ran into the same problem with View-5.0.1. The root cause was the following:

1. Log in as User_A

2. Add/Remove roles/features + Reboot

Now if you don't log in as the same User_A the installation of the servermanager can't finish. So if you now log in as User_B and try to install View you get the above mentioned error because the view installer trys to install AD LDS. And while trying the server manager says that there's still another installation active.

=> Resolution for me: I had to log in as User_A again and then everything worked fine after the server manager had finished installing the group policy management feature...