How do you deploy/uninstall a program with SCCM if user interaction is required?
Dear all,
Case: I have a couple of machines with Adobe Acrobat XI installed. I would like to remove this via SCCM 2012 application deployment. Usually, this can be done unattended with msiexec /x /q.
Problem: This only works, if Acrobat is not running, else msiexec will terminate with error 1602. This could be solved by running msiexec non-unattended (in this case the user would be asked to close Acrobat) or by a batch that checks for the process and then asks the user to close it. However, execution of the uninstall-command via SCCM usually happens in the context of SYSTEM, in the background. The user (non-admin, of course) will not see it and have no way to interact.
Question: How do you deploy a package or application with SCCM and at the same time have the process displayed for the logged on user?
Surely I am not the only on facing this problem with SCCM. How do you solve this?
Thanks and regards
Lars
Case: I have a couple of machines with Adobe Acrobat XI installed. I would like to remove this via SCCM 2012 application deployment. Usually, this can be done unattended with msiexec /x /q.
Problem: This only works, if Acrobat is not running, else msiexec will terminate with error 1602. This could be solved by running msiexec non-unattended (in this case the user would be asked to close Acrobat) or by a batch that checks for the process and then asks the user to close it. However, execution of the uninstall-command via SCCM usually happens in the context of SYSTEM, in the background. The user (non-admin, of course) will not see it and have no way to interact.
Question: How do you deploy a package or application with SCCM and at the same time have the process displayed for the logged on user?
Surely I am not the only on facing this problem with SCCM. How do you solve this?
Thanks and regards
Lars
3 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
triadenfisch
9 years ago
Solution: as proposed by rad33k above, this can be done via the Deployment Type's User Experience tab. Set Logon requirement to "Only when a user is logged on" and check "Allow users to view and interact with the program installation".
Thanks, rad33k, unfortunately I do not know how to mark your comment as the correct answer.
Thanks, rad33k, unfortunately I do not know how to mark your comment as the correct answer.
Comments:
-
You are welcome - I'm glad that I could help.
I think that you can add a summary of the question (at the bottom of your main post you should see: "Click here to enter a summary of the best answer(s) for this question (optional)" - rad33k 9 years ago
Posted by:
CraftyByte
9 years ago
It is not a complete answer to your question, but why not kill the process before uninstalling? You could wrap the uninstall in a batch file or a vbscript file and kill the process before running the uninstall command...
Comments:
-
Not what I want; I want to give users the change to save their work. - triadenfisch 9 years ago
Posted by:
anonymous_9363
9 years ago
One of the advantages of using AD groups to populate SCCM collections is that the group can be used for other, related purposes.
To wit, at clients I have worked with, the group's members would receive a message, via a generic HTA to which parameters are passed (group name, message text and so on), that the application would be updated on day 'x' at time 'y' and that they will need to not have it running at that time. They may receive a follow-up message on the day with 'z' hours warning. The message text would make it clear that the application would be terminated if it was running and that the loss of any unsaved work would be the responsibility of the user.
To wit, at clients I have worked with, the group's members would receive a message, via a generic HTA to which parameters are passed (group name, message text and so on), that the application would be updated on day 'x' at time 'y' and that they will need to not have it running at that time. They may receive a follow-up message on the day with 'z' hours warning. The message text would make it clear that the application would be terminated if it was running and that the loss of any unsaved work would be the responsibility of the user.
Comments:
-
Sure, could do it like this. But I know my users, and many of them tend to ignore information like this or forget about it. Yes, that is not really my fault; but I like to give them the best service possible, so I want to take a safer approach, one they cannot ignore. - triadenfisch 9 years ago
http://technet.microsoft.com/en-us/library/bb680462.aspx - rad33k 9 years ago