Deploying MSI using GPO

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I've been beating my head against a wall for a little while here, so I'm hoping someone can move the wall.
I'm trying to deploy IDFinder 5 via GPO.  I have an MSI that installs fine locally, and installs fine with the /qn switch using msiexec.  It even installs fine via GPO when the installer is specified to be local (i.e. c:\installme.msi).  As soon as I put that same installme.msi file on a network share, it doesn't install, and I get errors on the client that I'm trying to install it on.  The errors I'm getting are 1612, which means it can't get to the installer.  I'm installing it via a Computer policy, so I've made sure Authenticated users has read permission to the share the installme.msi is in, and heck, for testing I even created a new share, gave everyone full access and I got the same error.  In searching, I keep coming across a possible problem in the MSI (http://social.technet.microsoft.com/Forums/ar/winserverGP/thread/ed65b306-7f31-4530-bd17-3a7ef9dd8ee7) and it talks about using the SOURCELIST property.  I am not an MSI novice even, never mind expert, and that's what attracted us to IDFinder.  Now, the strange part is that I got this to work with a 4.7.0.3 installer, and that was distributed OK, but a couple months ago, that one stopped working too, with the same error.  Now, it took me a little while to notice because it's a very limited deployment, so in looking back at my change logs across these servers, all I can really see as a change was the retirement of all our Windows 2003 R2 domain controllers so when it was working, our whole domain has 2003 R2 DC's, and now it has all 2008 R2 DC's.  That could just be a coincidence, but that's the only thing I can think changed.

Has anyone else got a custom MSI with their license and registry entries to work and deploy from a network share using GPO and IDFinder 5?  Are there new MSI tools for IDFinder 5?  I didn't see any, so I'm still using the ones that have documentation for 4.

Thanks for the help.

 - Joe

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
jkalinowski Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Aug 2011 Location: Worcester, MA Status: Offline Points: 2	Post Options Post Reply Quote jkalinowski Report Post Thanks(0) Quote Reply Topic: Deploying MSI using GPO Posted: 10 Oct 2011 at 3:59pm
	I've been beating my head against a wall for a little while here, so I'm hoping someone can move the wall. I'm trying to deploy IDFinder 5 via GPO. I have an MSI that installs fine locally, and installs fine with the /qn switch using msiexec. It even installs fine via GPO when the installer is specified to be local (i.e. c:\installme.msi). As soon as I put that same installme.msi file on a network share, it doesn't install, and I get errors on the client that I'm trying to install it on. The errors I'm getting are 1612, which means it can't get to the installer. I'm installing it via a Computer policy, so I've made sure Authenticated users has read permission to the share the installme.msi is in, and heck, for testing I even created a new share, gave everyone full access and I got the same error. In searching, I keep coming across a possible problem in the MSI (http://social.technet.microsoft.com/Forums/ar/winserverGP/thread/ed65b306-7f31-4530-bd17-3a7ef9dd8ee7) and it talks about using the SOURCELIST property. I am not an MSI novice even, never mind expert, and that's what attracted us to IDFinder. Now, the strange part is that I got this to work with a 4.7.0.3 installer, and that was distributed OK, but a couple months ago, that one stopped working too, with the same error. Now, it took me a little while to notice because it's a very limited deployment, so in looking back at my change logs across these servers, all I can really see as a change was the retirement of all our Windows 2003 R2 domain controllers so when it was working, our whole domain has 2003 R2 DC's, and now it has all 2008 R2 DC's. That could just be a coincidence, but that's the only thing I can think changed. Has anyone else got a custom MSI with their license and registry entries to work and deploy from a network share using GPO and IDFinder 5? Are there new MSI tools for IDFinder 5? I didn't see any, so I'm still using the ones that have documentation for 4. Thanks for the help. - Joe

jkalinowski Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Aug 2011 Location: Worcester, MA Status: Offline Points: 2	Post Options Post Reply Quote jkalinowski Report Post Thanks(0) Quote Reply Posted: 11 Oct 2011 at 11:06am
	The wall has been moved. The path I was using, which worked OK in Windows 2003, was a couple directories deep. Authenticated Users had privs to the folder and the MSI, but it didn't have privs to one of the directories higher up in the structure. Now that we're running 2008R2 DC's, that seems to matter. I moved the MSI to an install directory where Authenticated Users could browse the entire directory structure between the host and the directory the MSI was in, and it worked OK.