SCCM 2012 Retired Application log info

I want to know if there is any log file or any entry in any log  file created if we retire an application. I'd also like to know the log file information when we Reinstate the application.
Krishna Santosh Maadasu Please remember to click “Mark as Answer” on the post that helps you, and click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I'm willing to know retired application information through a Log. Based on what you have told I assume we don't have this data logged in logs...
Krishna Santosh Maadasu Please remember to click “Mark as Answer” on the post that helps you, and click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • SCCM 2012 R2 - Application Deployment - on startup

    Hi, I would like to deploy Office 2010 Pro Plus and Lync 2013. Both packages have already been created and tested. I would like to set the install to occur on machine startup. Right now, if i add the machine to the AD Group set for the Lync and Office installs,
    it installs randomly during the day on a test machine.
    As I am new to SCCM, how can i set the install to occur on machine startup. It doesnt make sense to install Office during the day while a person is using it! I will be able to pinpoint which machines require Office 2010 installed before I install Lync 2013.
    If you need anymore info from me, as the above may not be clear, please let me know
    Thanks
    SCCM 2012 R2/Windows 7 Enterprise/Office 2010 Pro Plus/Lync 2013

    Hi,
    If you create the Office package as a package/program then you can set it to run on Computer startup, applications cannot be deployed that way.
    However, using at computer startup often gives very low number on actual installs becuase if the user logs in directly when the computer startup the installation will not run.
    I normally use PSAppdeploymen toolkit and prompt the user to close running office applications prior to the upgrade, then the user can postpone the installation as well and much much more.
    https://psappdeploytoolkit.codeplex.com/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM 2012 R2 - WindowsUpdate.log showing error 0x80240037

    Hi,
    Setup details:
    1) OS: Windows 2012 R2
    2) SCCM version: SCCM 2012 R2 with SUP role (WSUS v6.3.9600.16384)
    3) SQL: SQL 2012
    All the above resides on a single machine.
    Error description:
    Windows 2012 R2 Server clients are not reporting back to the server. "Required" column is showing "0" for all security updates. Investigation in the WindowsUpdate.log shows "WARNING: Failed to get WU Exemption info from NLM,
    assuming not exempt error = 0x80240037".
    Latest updates are downloaded, synchronized and deployed via SUP but the clients are not receiving the updates. Please advise. Thanks.
    Regards,
    KL

    Hi,
    You may check the following blog.
    http://blogs.technet.com/b/sus/archive/2012/09/05/additional-note-on-kb-2734608-regarding-wsu-windows-8-and-windows-server-2012.aspx
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 SP1 Application catalog website

    Architecture:
    SCCM 2012 SP1 installed on Windows 2012
    Application catalog website issue----->
    In SMSAWEBSVCSetup.log we found "IIS component ASP net not installed please install it.
    Installlation failed Error Code:125"
    whereas we have installed ASP.net already (registering ASp. net not supported please review the MS article: "http://support.microsoft.com/kb/2736284 "
    Let know me know what could be the cause.

    All depending on how/what order you install the IIS components sometimes it's just to reinstall IIS. To me it sounds like the .Net Framework http-activation and non-activation features are missing.
    Kent Agerlund | My blogs: blog.coretech.dk/kea and
    SCUG.dk/ | Twitter:
    @Agerlund | Linkedin: Kent Agerlund |
    Mastering ConfigMgr 2012 The Fundamentals

  • SCCM 2012 deployed application outside of Maint Window and before Deployment time

    I have an application that I set for deployment time of 7pm today. The collection that I deployed it to had a maint window start time of 7pm - stop time of 6am.
    Its 3:12 (MST) and 4:12 in my regional office, however they have all got the software installed.
    Am I overlooking something, what did I do wrong? Is there a setting somewhere that I need to check?

    I have time based on: UTC should I change that to Client Local Time? I thought UTC meant that for example if I have deployment set at 7pm and My sccm server is in a different time zone that when the respective time zone reached 7pm that it would start the
    deployment.
    I clicked on the maint Tab on the collection that I deployed it to and there is only 1 maint window for that collection.
    I went to a client that it installed on and viewed the execmgr.log. The lasttime it was populated was today at 6am. I then tried another client and same thing last entry was from 6am.

  • SCCM 2012 OSD: central logging, smsts.log

    Hi,
    Is there a way to follow an SCCM MDT integrated task sequence in real time?
    We configured central logging and this is working fine, though it is only BDD.log that is copied. When task sequence fails or is succesfull the other files are copied too.
    We want to have the possibilty to monitor in real time, without needing to go on the machine itself and open smsts.log.
    Please advise.
    J.
    Jan Hoedt

    I first created threads about configuring central logging in SCCM, numerous indeed.
    That worked fine but then we decided to go to MDT logging, again some threads.
    No logging is satisfactory to us, neither is the status message. I don't get the concept of the satus message, why is it there whereas smsts.log is containing all logdata.
    We deploy a lot of machines to debug. These are on the central logging share. Loggings like smsts.log also can easily be sent for comment when issues. To be able to debug correctly, we need the smsts.log, it's a struggle each time to go on the machine and
    get the smsts.log (when machine is in winpe-phase or has network issues. I don't understand why a simple concept = central logging of smsts.log (not the status messages) is that hard to configure/would not exist at all.
    Jan Hoedt

  • SCCM 2012: install applications to terminal server (2012)?

    Hi,
    I'm trying to deploy a hotfix for App-v to a terminal server (Windows 2012). The install of the App-v 5.0 SP2 client worked fine but the install of the hotfix doesn't install silently to RDS-servers (the same install parameter works on a Windows 7 client
    = setup.exe /accepteula /qn).
    Problem: installation starts but then the installation screen pops up.
    Probably related to RDS (I should give some extra installation parameters? But why the App-v 5.0 SP2 client then installated without any issues)?
    Pls advise.
    J.
    Jan Hoedt

    How many servers? In cases like this it can be quicker to install it manually. After all, this is a one-time scenario.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • How can you expire deployments in bulk in SCCM 2012 SP1?

    As April 8th approaches and we've all but purged XP from our environment, I want to expire all of our deployments for XP packages, however; going through 350+ deployments by hand seems rather ludicrous. PowerShell for CM doesn't seem to be very developed
    or suited for this (though I admit I'm much more well versed in AD cmdlets) and while I could do this by directly running a SQL statement against the database, my understanding is that this is not supported and generally frowned upon.
    Does anyone have any ideas of a good way of doing this? Eventually it would apply to purging all XP related data (deployments, packages, collections) from our SCCM environment. We're running 2012 SP1.
    Thanks in advance!
    WB

    Hi,
    Here is a right click menu method for your reference.
    SCCM 2012 – Retire Application
    http://thedesktopteam.com/blog/raphael/sccm-2012-retire-application/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • How do Virtual Applications get published in SCCM 2012

    SCCM 2012 Virtrual applications are deployed, icons appear on desktop and appear to be installed according to the Application Management Client console.  However the SCCM2012 AppDiscovery.log states "Required component is not published".  
    We are running MS Application Virtualization Desktop Client is V4.6.3.25171.  Where can I find the publishing errors?

    Only find Dll, exe files and some XML files there. 
    I do see in the CCM\log\AppDiscovery.log the following:
    <![LOG[    Performing detection of app deployment type PRU-VAPP_U_ATTRouteIt131-A - Microsoft Application Virtualization 4(ScopeId_756A69C5-BB0D-442E-BC79-54E767A8B034/DeploymentType_1acd73db-4883-43c9-90b2-ac044ed12dd8, revision 3) for
    user.]LOG]!><time="13:38:29.891+300" date="12-04-2014" component="AppDiscovery" context="" type="1" thread="936" file="appprovider.cpp:2148">
    <![LOG[Required component [Route It! 1.0.0.1] is not published for S-1-5-21-31572-1897081133-3783826585-2300]LOG]!><time="13:38:32.730+300" date="12-04-2014" component="AppVHandler" context="" type="1"
    thread="936" file="appvhandler.cpp:584">
    <![LOG[+++ AppV application not discovered for S-1-5-21-31572-1897081133-3783826585-2300 [AppDT Id: ScopeId_756A69C5-BB0D-442E-BC79-54E767A8B034/DeploymentType_1acd73db-4883-43c9-90b2-ac044ed12dd8, Revision: 3, AppV Pkg GUID: {D699AA09-CA0E-4774-A5D6-BBD97496FA69},
    AppV Version GUID: {AC834D03-3524-43A3-B5FC-8ED6FE3079E1}]. Some required components are not published.]LOG]!><time="13:38:32.730+300" date="12-04-2014" component="AppVHandler" context="" type="1"
    thread="936" file="appvhandler.cpp:224">
    <![LOG[+++ Did not detect app deployment type PRU-VAPP_U_ATTRouteIt131-A - Microsoft Application Virtualization 4(ScopeId_756A69C5-BB0D-442E-BC79-54E767A8B034/DeploymentType_1acd73db-4883-43c9-90b2-ac044ed12dd8, revision 3) for S-1-5-21-31572-1897081133-3783826585-2300.]LOG]!><time="13:38:32.730+300"
    date="12-04-2014" component="AppDiscovery" context="" type="1" thread="936" file="appprovider.cpp:540">
    But I don't know why all the components are not getting published.
    I have the icons for this app on the desktop and my ID is in the uninstall collection. The uninstall collection says:
    SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueUserName,SMS_R_USER.WindowsNTDomain from SMS_R_User inner join SMS_G_System_AppClientState  on SMS_R_USER.UniqueUserName = SMS_G_System_AppClientState.UserName where SMS_G_System_AppClientState.AppName='AppV
    - ATTRouteIt131-A' and SMS_G_System_AppClientState.ComplianceState = 1
    But it seems like the AppDiscovery.log does not think the app is installed.  Everytime I run the Application Deployment Evaluation Cycle on the client the AppDiscovery.log shows it trying to install. And since it does not think the app is
    installed, the uninstall does not seem to run.  I know I am missing something as I have many apps that act this way. 
    Hope you can help!

  • Collection in SCCM 2012 of SCCM 2007 clients?

    Hi,
    I'd need to make a collection of SCCM 2007 clients in SCCM 2012. This way I know which clients need to be updated.
    Can that be done?
    I guess queries can only be run on what sccm 2012 client return on info (I tried a simple query: configuraiton manager client state - version but it only return versions 5.x).
    Pls advise.
    J
    Jan Hoedt

    I'd need to make a collection of SCCM 2007 clients in SCCM 2012. This way I know which clients need to be updated.
    Can that be done?
    Can't you just add the column '(client) version' in the console? Are they displayed then? (Also keep in mind that it's theoretically not possible that CM07 clients can be assigned to a CM12 site)
    Torsten Meringer | http://www.mssccmfaq.de

  • Retired applications are not deleted after 60 days

    We have several applications that are retired, all deployments are removed. According to SCCM documentation retired applications should get deleted after 60 days automaticly. It has been about 1 year since that the application is retired, but it does not
    get deleted.
    Any idea's?
    Steven Mudde

    Application is retired, deployments removed, no references. Manual deletion of the applications is not the problem, this works as it should.
    However SCCM documentation says "If an application that has no deployments is retired, it will be deleted from the Configuration Manager console after 60 days."
    http://technet.microsoft.com/en-us/library/gg682031.aspx
    This does not work
    Steven Mudde

  • SCCM 2012 R2 C2 OSD deployments no logs when Applications fail

    Hello,
    Have Task Sequences with the Install Application step {as well as other steps for packages, etc.} that installs Applications when one of the Applications fail I usually see exactly what Application fails through the Console Status Message Query "All
    Status Messages for a Specific Package at a Specific Site".
    Troubleshooting: When I look in C:\Windows\CCM\logs. I see none of the logs: AppDiscovery.log(s), AppEnforce.log(s), AppIntentEval.log (s)?
    Note: This only happens if there is an error in the Install Application step...normally the logs are there. Any ideas on how to fix this?
    Thanks!

    Here is a snippet of smsts.log There are 2 Install Applications steps the first one has 9 applications the 2nd has 1 application.
    <![LOG[
    Parsing step node: CCL Shipboard Applications]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
    <![LOG[Description: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
    <![LOG[ContinueOnError: true]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
    <![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
    <![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
    <![LOG[Disable: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
    <![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
    <![LOG[Timeout: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
    <![LOG[DefaultVarlist found]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
    <![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp1Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp1Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp2Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp2Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp3Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp3Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp4Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp4Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp5Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp5Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp6Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp6Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp7Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp7Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp8Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp8DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp8Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_75fb5490-a490-4e64-9545-fcd0429bc135,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_848807ff-6527-4984-b789-315489b5d8fb,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_275df3b1-48df-49dd-8f4d-e739352e9da5,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_a5e881ca-e355-4119-ae4c-ecb0b809da1d,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b4ade0f0-0801-4772-a1b1-2f07b9e774d9,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_c57aedb5-5a8a-49a7-98ed-89b48fe78d12,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_01266b3d-f6cb-4dc4-b255-36c3244b998f,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b5d3c8f3-cb78-4e1a-8796-f8285128e315,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_83d05a3c-a613-40d7-88da-ceb0a07ef60e
    /basevar: /continueOnError:True]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
    <![LOG[Adding instruction at 56]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">
    <![LOG[
    Parsing step node: CCL Shipboard Application Part 2]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
    <![LOG[Description: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
    <![LOG[ContinueOnError: true]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
    <![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
    <![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
    <![LOG[Disable: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
    <![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
    <![LOG[Timeout: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
    <![LOG[DefaultVarlist found]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
    <![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
    <![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_cdad2a4f-c0cc-4fd5-9833-0b273c8dca01 /basevar: /continueOnError:False]LOG]!><time="09:30:41.517+240" date="04-10-2015"
    component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
    <![LOG[Adding instruction at 57]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">

  • Deploying Applications with SCCM 2012 R2 to Server 2008 R2 RDS servers

    I'm having some trouble finding some concrete information from Microsoft regarding the deployment of applications to RDS servers using SCCM 2012 R2. There seems to be a lot of conjecture, old information and old wives tales floating around and I was hoping
    I could get some information confirmed!
    1. MSI installs automatically switch to install mode on RDS servers? 
    I've seen this mentioned a few times. I've also seen it mentioned that it is only true when running the MSI from the console session manually (i.e clicking the MSI file) not running as SYSTEM as SCCM would usually do. Can someone confirm if they do this
    themselves or not?
    2. Users still logged in when deploying applications? 
    Is it possible to deploy an application while users are still logged in? Is this only related to going into 'install' mode and taking the chance that a user will do something that will cause issues? Or is it known to cause issues?
    I guess those are the main ones, I'm experienced in SCCM but not with deploying to RDS servers, I cant seem to find any straight answers!
    Anyway, thanks in advance!

    I've never had large enough RDS environment to use SCCM for app push, but from my experience in managing 2012/R2 RDS and local installs, I never bother with switching to install mode anymore and it works fine.  Now if you're skeptical, you can
    easily build this into a script that runs as a pre-req to your .MSI as part of the software package in SCCM so it's not a big deal.
    As for installing apps while users are logged in, shouldn't be a problem if you're installing a new app., if however you're updating an existing application or uninstalling it, then it may be best to drain that RDS host first of all user sessions then do
    the work just to be safe.  this also helps avoid reboots.

  • Deploying CC Enterprise Applications With SCCM 2012

    Hi all,
    We are using CC Packager to package up individual applications (Photoshop, InDesign etc) and are having trouble deploying the applications once packaged. To deploy, we are using SCCM 2012 and are deploying to Windows 7 x64 clients. It appears that the install begins on the client, then hangs, never to finish.
    We are running the MSI with the REBOOT=ReallySuppress and MSIRESTARTMANAGERCONTROL=Disable commands, but with no luck.
    This has us really stumped. The applications seem to package fine, yet just won't install. If we manually run the installer, we can see it begin installing, then the progress bar goes backwards and the installation ends without displaying any sort of message.
    Also, as an FYI, we have followed this guide closely in our attempts: http://helpx.adobe.com/creative-cloud/packager/deploying-packages-sccm.html
    Has anyone experienced a similar problem? Any ideas?
    Thank you in advance.
    Ryan

    Windows 7 x64 Clients
    Deploying with SCCM 2012
    I have called Adobe before and was told that the application package needs to be on a local drive on the computer. The package cannot be installed if the package is sitting on the network. My installation for a adobe creative cloud  package fails to install when I try to install the application from the software center. At some moment the installation searches to ensure it is on a local disk. Not sure how this happends. If you place the installation package on a drive on your computer the package will install, although it will take time depending on how many applications you have packaged.
    Another problem that you might have is having users log out of the applications without admin previlages.
    I have yet to find a solution for these two problems, I could really use some help from someone who has sucessfully deployed a creative cloud package to a user.
    Thank you

  • SCCM 2012 Application Catalog Website Point role Status is critical

    Hi team,
     In a client's SCCM 2012 R2 environment there is a Critical Icon and Status against one of two Application Catalog Website point roles. Looking at the Component status, there are no errors and all the components show as green.
     Trying to find any warnings or errors in the messages for the Site System role doesnt show any errors, and I tried to reset counts but this has not changed the status.
     I am not sure where to go from here. The application catalog itself works and is up. All the services are running. I am unsure as to where this error status comes from or what it pertains to.
     Any advice would be appreciated.

    Hi,
    Please check portlctl.log and awebsctl.log to see if there is any error.
    You could also check the thread below.
    Symptom: Reporting Services Point Status (under Monitoring - System Status - Site Status) appears as Critical, No error messages in logs or status messages
    Cause: 'Status' can be set to "2" for 'SMS SRS Reporting Point' in dbo.summarizer_sitesystem table in sql
    Resolution: > Run below query:
    update dbo.summarizer_sitesystem set status = '0' where SiteSystem = '["Display=\\abc.local\"]MSWNET:["SMS_SITE=ABC"]\\abc.local\' and role = 'SMS SRS Reporting Point'
    > It should set the status back to 0.
    > Check in console and errors should go away.
    > In case if value reverts back then check below namespace in wmi of site server:
    root\sms\site_pri\sms_sitesystemsummarizer
    > check the value for reporting services point, ideally it should be 0, let's say it's set to 2 there as well then remove role of reporting services point.
    > if entry for reporting services point goes away from both the places then it's good, you can re-install the reporting services point and it should work fine.
    > Let's say if value/values doesn't get removed from sql/wmi , remove them manually via queries and then go with uninstall and re-install.
    > then it should work and errors in console and common.log should go away.
    https://social.technet.microsoft.com/Forums/en-US/5e0b7af6-f00c-4610-a709-f3e0e26505be/sccm-2012-monitoring-site-status-reporting-services-point-status-critical?forum=configmanagergeneral
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Maybe you are looking for