![]() The table does not have CostInitialize defined at all and therefore the setup stops with Error 2732, Directory Management not initialized. The developers seems to have missed that ResolveSource CustomAction need to run after CostInitialize CustomAction, see ResolveSource Action documentation. I've reviewed the broken MSI and debugged the bug down to the InstallUISequence table. After some investigation it looks like very many others reported this bug in the VMware Community Forums, but nobody came up with a solution. At very first it's not possible to install at all. If you try to deploy VMware Player 4.0.0-471780 or 4.0.1-528992 to your Desktops via Active Directory you will expierence some major difficulties. Now you have the required MSI file vmware player.msi in the copied folder. Make a copy of this folder to your distribution share. While the setup is launched setup creates a folder in C:\Users\%username%\AppData\Local\Temp\vmware_. exe, wait until the setup shows the "Welcome to the installation wizard for VMware Player", but don't install the Player. You need to download the normal VMware-player-4.0.1-528992.exe file from VMware site. If you'd like to deploy VMware Player in your Enterprise you need to extract the MSI setup from the standard setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |