medwards

"First time poster, long time lurker" This site has been tremendous help over the years, however I'm running into a situation my google-fu and searching skills on this site are not coming up with a real answer for... First off - my SCCM setup is rather simple, just a single server/distribution point. (SCCM 2012 R2 CU3) Recently, something has gone buggy. Any package or application I create stops working after its created and distributed, where it installed fine before the package or application is created What I mean by that is, lets say I have "dummyprog.msi" on \\sccmserver\packages\dummyprog\, I open a command line to the folder, and run msiexec /i dummyprog,msi /qn and dummyprog.msi installs silently, no issues on a test workstation From the same folder I ran the above test install from, I create the package and distribute it as I always have... pretty simple application and use of SCCM. However, recently after the package is created and distributed successfully, the package won't install via SCCM, and if I run the same command line from the same source, I now get "This installation package could not be opened. Verify the package exists and you can access it..." when I run it with out the /qn switch. Any idea what's going on? To my intermediate SCCM skills, it seems when the package is created, it is some how corrupting the files? After the package is created, I can no longer run the command line manually or deploy through SCCM? What's going on? TIA Matt