Harry1980 Posted November 21, 2014 Posted November 21, 2014 Hi All, I have just noticed that my msi deployment via group policy is failing. I am using Server 2012 R2 (newly installed) group policy to deploy policy central, for some reason it shows that it is installing during startup but when I check the laptop it does not show anything installed. I have checked Event Viewer on the laptop and it shows MsiInstaller with Event ID: 1040 and 1042. Message is Beginning a Windows Installer transaction:{2a858ef4-0801-40ca-b045-2dee9874804e}. Client Process Id: 1084. Thanks.
localzuk Posted November 21, 2014 Posted November 21, 2014 In my experience with an MSI "launching" but never finishing, is that it is prompting to do something behind the scenes. Are there compulsory options that aren't being supplied via an MST or the like?
foofighterjim Posted November 21, 2014 Posted November 21, 2014 In my experience with an MSI "launching" but never finishing, is that it is prompting to do something behind the scenes. Are there compulsory options that aren't being supplied via an MST or the like? I'm sure that the standard policy central client install needs to have the address of the server entered. As @localzuk mentions there should be a way to do this either by adding a switch or via MST.
jertsy Posted November 21, 2014 Posted November 21, 2014 (edited) Hi All, I have just noticed that my msi deployment via group policy is failing. I am using Server 2012 R2 (newly installed) group policy to deploy policy central, for some reason it shows that it is installing during startup but when I check the laptop it does not show anything installed. I have checked Event Viewer on the laptop and it shows MsiInstaller with Event ID: 1040 and 1042. Message is Beginning a Windows Installer transaction:{2a858ef4-0801-40ca-b045-2dee9874804e}. Client Process Id: 1084. Thanks. Is it all MSI or just one, if its just one then its likely to be something with that MSI as previously stated. I have 2012 R2 and I deploy software via GPO with no issues, standard stuff really. Just re-read, policy central MSI. I missed that somehow! Edited November 21, 2014 by jertsy
Patrick Posted November 21, 2014 Posted November 21, 2014 check permissions on the MSI share location.
woreilly Posted November 26, 2014 Posted November 26, 2014 is there a previous version that wasn't removed properly?
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 Hi Everyone, It is failing to install all MSI's that I am trying to deploy. I have checked the permissions on the msi folder and it seems fine. The server was installed during the last half term. I am also trying to deploy Microsoft XNA Framework and that is also failing. I have deployed these software in the past on other servers and they worked fine.
cscc Posted December 8, 2014 Posted December 8, 2014 Are you able to manually browse to the UNC path of the MSI share location and run the MSI setup successfully?
snagrat Posted December 8, 2014 Posted December 8, 2014 Do Domain Computers have read access to the share, rather than any user group? All XNA frameworks needs .Net4 I believe so may be failing due to that being missing?
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 Yes. I have just installed policy central and Microsoft XNA framework browsing to the UNC path.
cscc Posted December 8, 2014 Posted December 8, 2014 Sounds like permissions then, what share and security permissions do you have set currently?
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 The folder that contains the msi's, is a hidden share. Would that be the issue?? The permissions on the MSI folder are as follows: System - Full Control Administrator - Full Control Domain Users - Full Control Administrators - Full Control
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 Currently the computers don't have access to the share, only what's stated above.
cscc Posted December 8, 2014 Posted December 8, 2014 Is it an administrative share e.g MSI$ or similar? I would set the share itself to have: Everyone - Full Control Then under security: System - Full Control Administrator - Full Control Authenticated Users - Read and Execute
speckled Posted December 8, 2014 Posted December 8, 2014 I know it sounds stupid but i am going to say it anyway i have seen people do this, you are dragging it from a folder with a path the workstation can access \\server\share\folder and not just open explorer d:\ and dragging it in?
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 CSCC - the msi folder is labelled as MSI$. I will change the settings and see I that makes any changes. Speckled - I'm a bit confused to what you trying to say.... lol
speckled Posted December 8, 2014 Posted December 8, 2014 Ok so when you import your msi, you open the folder containing the msi using the actual path the workstation will look for, then drag it into the GPO to import it, the folder path listed under source then reads the location the workstation looks to (\\server\share\folder) if you just open explorer on the server and browse to the drive and folder the source would be D:\folder\folder. When the workstation then tries to install it it cant find the msi as it doesn't exist at that location.
snagrat Posted December 8, 2014 Posted December 8, 2014 Computers need access to the share as it tries to install as a computer account, not as a user account. Authenticated Users or Domain Computers with read access is required. 1
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 CSCC - The shared folder it called MSI$. I will change the permission and see what happens.
Harry1980 Posted December 8, 2014 Author Posted December 8, 2014 Thanks guys, finally working. It was a permission issue, I added authenticated users and domain computers.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now