skissinger
Posts: 1992
Score: 129 Joined: 9/13/2001 From: Sherry Kissinger Status: offline
|
We deploy .MSI's all the time w/ConfigMgr, and Add/Remove Programs is populated with an entry. Based on your command line, you are dropping a log file in %temp%, if you look inside that log file, it should tell you what's really going on. ConfigMgr is just the delivery van... it's nothing more or less magical than any other SW Distribution tool. Another trick to kind of see what ConfigMgr would do, is to run the install using SYSTEM context, just like ConfigMgr would. A way to get to System context is to on an xp workstation cmd prompt, type in AT <1minute in the future> /interactive cmd.exe like... at 15:31 /interactive cmd.exe At 3:31pm, a cmd window would open that is running under system context. If you run your installation from within that cmd window, you are emulating how ConfigMgr installs using System context. Perhaps that will help you find what the issue may be.
_____________________________
mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com Microsoft MVP - ConfigMgr
|