How to quickly and easily test your ConfigMgr packages

re: How to quickly and easily test your ConfigMgr packages

joejoeinc. — Tue, 01 Nov 2011 00:06:14 GMT

I concur with PackagerGuy, I have also seen packages fail once in SCCM because of some small subtle difference in the way that SCCM installs software verse PSexec. I agree this method may be handy to quickly test something but it is not a true reflection of testing SCCM deployed software.

re: How to quickly and easily test your ConfigMgr packages

JohanW — Thu, 20 Oct 2011 10:36:00 GMT

Another thing to add to the text. When starting a command prompt as System. Make sure to use the 32bit cmd.exe inside C:\Windows\SysWOW64\ if you're running on x64, since the SCCM client is 32bit. That way registry and folder redirect will apply correctly.

re: How to quickly and easily test your ConfigMgr packages

PackagerGuy — Fri, 14 Oct 2011 20:54:41 GMT

I am the guy who has "repackaged" a lot of applications. One of my regular tasks is to test my repackaged apps in sccm environment. I had an idea to shorten testing time by using psexec..., but i must warn you, even though it seems to be the same testing scenario, ITS NOT, some rare applications still act the different way if you run them from psexec or sccm sw distribution or TS. This test is not 100%. Its close, I would say its around 98%, but still you have risk that app will not work in TS or SW distribution if you just rely on psexec test.