Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to remotely install a 32 -bit MSI and a 64-bit MSI, using Group Policies in Windows Server 2003 (32 bit).

I've created a distribution point and a Group Policy Object. When I try to "Assign a Package" and pick the 32-bit MSI, everything works fine. However, when I try to assign a 64-bit MSI, I get this error:

"Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct"

Any idea what might be going on here? Is it even possible to remotely install 64-bit MSI via group policies using Windows Server 2003 (32 Bit)?

share|improve this question
As far as I know it is possible but I've now easy way to verify. Are either of the MSI's installed on the computer you are creating the GPO on? That used to cause problems/may still cause problems. – chunkyb2002 Oct 1 '10 at 23:05
Nope. MSIs are not installed on the Windows Server 2003 machine – Think Floyd Oct 1 '10 at 23:53
Have you tried the failing package on another server or a different 64bit MSI on this server? I don't have experience doing this on 2003, but have not had issues doing it on 2008 32bit. – edusysadmin Oct 3 '10 at 3:15
I have just tried the failing package on Windows Server 2008 (32 bit). I still see the same error. The MSI as such, works well if I install it manually on a 64 bit machine. – Think Floyd Oct 4 '10 at 6:05

(old question I know, but maybe a useful answer to someone)

You can't use a Group Policy Editor on a 32bit machine to assign a 64bit application. You need to run Group Policy Editor on a 64bit machine to make the assignment. (even if it is just a client machine accessing the same 32 bit server)

share|improve this answer

From memory, I had this problem a while back and it was caused by the file path being too long. What happens if you shorten the UNC path to the MSI and try again? If it is still too long, you could also create the admin install point using the SHORTFILENAMES=TRUE switch?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.