It's a long story as to why we are looking for this functionality but can the error be suppressed from the user when deploying via Active Directory?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Ok, I'll add a bit more info as to why we are looking at doing it. There is a SAP patch that needs to go out via AD but reinstalling the product is considered too much impact. There is a MSI with the patch made but it has to be pushed via AD. The problem is that everyone that has SAP assigned does not necessarily have it installed. So they want to have a launch condition on the MSI to check for the presence of SAP. Things get complicated when they don't want the user to see the launch condition error.

I know this solution is not textbook at all but any help would be welcome.
Answered 11/23/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Can't you just run it with no interface? Or am I missing something?
Answered 11/23/2004 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
Unfortunately as far as I know in Active Directory you cannot set the user interface level except down to basic. I still have yet to hear back if the LIMITUI property fixed it but I'm pretty sure errors still show up in basic mode. If I could do everything from a command line there would be no issue with the user interface.
Answered 11/23/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity