cnl83
asked on
Error trying to deploy Logmein via GPO
Trying to deploy Logmein via GPO and im getting Event ID 102. The install of application Logmein from policy Logmein failed. The error was %%1603.
I checked and the security of the MSI file is set to Everyone with full permissions. It even added the computer to the logmein control panel but there are no system files in the Logmein program folder.
I checked and the security of the MSI file is set to Everyone with full permissions. It even added the computer to the logmein control panel but there are no system files in the Logmein program folder.
Hi, I haven't used LogMeIn for years so to provide a quick solution for you.
Install to host first.
Then use the client versions to GPO
Please refer to
LogMeIn host software for Windows
System Requirements – Client Device
How to Deploy LogMeIn Host Software
Best Wishes
Install to host first.
Then use the client versions to GPO
Please refer to
LogMeIn host software for Windows
System Requirements – Client Device
How to Deploy LogMeIn Host Software
Best Wishes
So LogMeIn is an MSI package and they (LogMeIn Corp.) say it should work that way?
Did you try it on a clean machine?
Please note that the path as set in the GPO must not be a network drive letter but has to be a UNC path (\\someserver\someshare\yo ur.msi).
PLEASE NOTE: You must NOT give full access to setup files. Big mistake. Just use read access, else, your domain is about to be compromised in seconds.
Did you try it on a clean machine?
Please note that the path as set in the GPO must not be a network drive letter but has to be a UNC path (\\someserver\someshare\yo
PLEASE NOTE: You must NOT give full access to setup files. Big mistake. Just use read access, else, your domain is about to be compromised in seconds.
ASKER
Turns out it was just that one particular server that would not take the install. It works fine on all others.
Ok, if you are satisfied with that, please close the question by selecting your own comment as solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please check that the share in which you are hosting this msi has the following share and NTFS security permissions: Group "Domain Computers" has read rights.
Permissions Entry Window
Double check is that the path to the MSI file in the script uses a UNC path. E.G. \\dataserver1\msis\msi_ins
Check that the package is compatible with installing via GPO. In order for it to be compatible it needs to be able to install with no user interaction, to test this log on to a computer where it is not installed, copy the msi file to somewhere local such as the root of the C:\ drive and type "msiexec /i C:\path_to_msi.msi /quiet". If it installs correctly it is compatible, if not it will need to be repackaged