In the Deployment Type, on the User Experience tab (I think) there is an option to deploy for system or deploy for user – same thing – to deploy as admin, deploy to the system.
J From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Tuesday, July 9, 2013 10:04 PM To: '[email protected]' Subject: RE: [mssms] RE: Question/Help about uninstall app in CM12 You can only make this decision if I deploy this as an Program not as an Application. Because I am using the .msi of Lync 2013 I assumed it would be better to make it an Application and not a program. Unless I am missing a serious option, I am not sure how to set it to run as Admin when creating it as an Application. I will try and deploy this as a Program and see if I get better results. Thanks, From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, July 09, 2013 2:14 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Question/Help about uninstall app in CM12 Make sure you have the program set to run with Admin privileges and not with the current user’s privileges. The System account does not “bypass” UAC, it is simply not subject to UAC. It’s a subtle difference, but an important distinction to make. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Tuesday, July 9, 2013 12:17 PM To: '[email protected]' Subject: RE: [mssms] RE: Question/Help about uninstall app in CM12 Thanks all for your help. I did in fact use the method below, but it still fails. Then I noticed what I believe is my headache when I ran the same script manually. I got the MS bootstrapper UAC prompt box that was asking for a yes or No response. I believe this is the cause of my issue, but I am not sure why the application is not uninstall as SYSTEM, which I understand would bypass the UAC prompt. Even though my config file has all the things for a silent uninstall, that all happens only after I click Yes. Not sure if there is something I can add so it bypasses the prompt. Kevin From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tuomo Leppänen Sent: Thursday, July 04, 2013 11:00 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Question/Help about uninstall app in CM12 I would do exactly the same, the command should then be something like this: Setup.exe /uninstall LyncEntry /config lyncentry.ww\config.xml In my opinion, much better way to handle configurations... On 5.7.2013 3:12, CESAR.ABREG0 wrote: I would include the XML file with your source files within the same app and will be found on the cached app at runtime. Cesar A. Meaning is NOT in words, but inside people! Dr. Myles Munroe My iPad takes half the blame for misspells. On Jul 4, 2013, at 4:54 PM, "Johns, Damon (DoJ)" <[email protected]<mailto:[email protected]>> wrote: Thinking about this a little more, you could also modify the path to your xml file removing the spaces. It may also be worth setting up an actual share with appropriate access so you’re not trying to reference an xml file sitting on a hidden file share. (d$) So Setup.exe /uninstall LyncEntry /config \\servername\mysharedlyncsourcefolder\config.xml<file:///\\%5C%5Cservername%5Cmysharedlyncsourcefolder%5Cconfig.xml> I’m assuming the setup.exe requires an explicit path to the config.xml file otherwise you could just include it in an application with all of the source files and call it? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Friday, 5 July 2013 9:33 AM To: '[email protected]<mailto:[email protected]>' Subject: [mssms] Question/Help about uninstall app in CM12 I have been working on creating an uninstall application package to remove Lync 2013 Basic from machines. I have made the uninstall as follows: setup.exe /uninstall LyncEntry /config \\servername\d$\Source\Software\Lync 2013\BasicX86\lyncentry.ww\config.xml<file:///\\%5C%5Cservername%5Cd$%5CSource%5CSoftware%5CLync%202013%5CBasicX86%5Clyncentry.ww%5Cconfig.xml> The config file contains the “silent” stuff, as stated on the MS site. When I run the uninstaller in my AppEnforce log file I have the following: ++++++ App enforcement completed (3 seconds) for App DT "Microsoft LyncEntry 2013 - Windows Installer (*.msi file)" [ScopeId_FCBF917E-15D8-4B74-99F7-2478A740373B/DeploymentType_84152d30-f0d6-42a3-a1a6-f5a845395d3f], Revision: 10, User SID: ] ++++++ AppEnforce 7/4/2013 4:02:36 PM 2776 (0x0AD8) +++ Starting Uninstall enforcement for App DT "Microsoft LyncEntry 2013 - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_FCBF917E-15D8-4B74-99F7-2478A740373B/DeploymentType_84152d30-f0d6-42a3-a1a6-f5a845395d3f, Revision - 12, ContentPath - C:\Windows\ccmcache\v, Execution Context - System AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) A user is logged on to the system. AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Performing detection of app deployment type Microsoft LyncEntry 2013 - Windows Installer (*.msi file)(ScopeId_FCBF917E-15D8-4B74-99F7-2478A740373B/DeploymentType_84152d30-f0d6-42a3-a1a6-f5a845395d3f, revision 12) for system. AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) +++ Discovered application [AppDT Id: ScopeId_FCBF917E-15D8-4B74-99F7-2478A740373B/DeploymentType_84152d30-f0d6-42a3-a1a6-f5a845395d3f, Revision: 12] AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) App enforcement environment: Context: Machine Command line: setup.exe /uninstall LyncEntry /config \\servername\d$\Source\Software\Lync<file:///\\%5C%5Cservername%5Cd$%5CSource%5CSoftware%5CLync> 2013\BasicX86\lyncentry.ww\config.xml Allow user interaction: No UI mode: 0 User token: null Session Id: 4294967295 Content path: C:\Windows\ccmcache\v Working directory: AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Prepared working directory: C:\Windows\ccmcache\v AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Prepared command line: "C:\Windows\ccmcache\v\setup.exe" /uninstall LyncEntry /config \\ servername \d$\Source\Software\Lync 2013\BasicX86\lyncentry.ww\config.xml AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Executing Command line: "C:\Windows\ccmcache\v\setup.exe" /uninstall LyncEntry /config \\ servername \d$\Source\Software\Lync 2013\BasicX86\lyncentry.ww\config.xml with system context AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Working directory C:\Windows\ccmcache\v AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Post install behavior is BasedOnExitCode AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Waiting for process 1340 to finish. Timeout = 120 minutes. AppEnforce 7/4/2013 4:30:00 PM 4700 (0x125C) Process 1340 terminated with exitcode: 30045 AppEnforce 7/4/2013 4:30:04 PM 4700 (0x125C) Looking for exit code 30045 in exit codes table... AppEnforce 7/4/2013 4:30:04 PM 4700 (0x125C) Unmatched exit code (30045) is considered an execution failure. AppEnforce 7/4/2013 4:30:04 PM 4700 (0x125C) When I look up the error code 30045 I get: InvalidMetadataFile Maybe I am missing something, and I have spent a few days on this doing it multiple ways. If I only user setup.exe /uninstall LyncEntry then I get the pop up windows, so I need it to be silent, so it said I needed to use the /config option. I am going to start from scratch with a new install just in case, but maybe someone has had good things with Lync 2013 and CM12… cause I have not. After this I need to then create an install package, so that should be no fun. Thanks, Kevin Johnston ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
