rddvls1999

Hi Aurock, I'm having the exact same issue. Were you ever able to find a solution to this? TIA, Paul

Actually, I was just looking at the AppDiscovery.log, and saw the following: Performing detection of app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18) +++ Application not discovered. [AppDT Id: ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, Revision: 3] AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18) +++ Did not detect app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18) Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633" AND Revision = 3)" AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18) Performing detection of app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18) +++ Application not discovered. [AppDT Id: ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, Revision: 3] AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18) +++ Did not detect app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18) ActionType - Install will use Content Id: Content_3d04b904-5578-4764-88b2-e05c8c5838e2 + Content Version: 1 for AppDT "VLC" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633], Revision - 3 AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18) ActionType - Install will use Content Id: Content_3d04b904-5578-4764-88b2-e05c8c5838e2 + Content Version: 1 for AppDT "VLC" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633], Revision - 3 AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18) Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8" AND Revision = 1)" AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18) Performing detection of app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18) +++ MSI application not discovered [MSI Product Code: {1EF3289E-C805-11E2-8F40-0024E808B313}, MSI Product version: ] AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18) +++ Did not detect app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18) Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8" AND Revision = 1)" AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18) Performing detection of app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18) +++ MSI application not discovered [MSI Product Code: {1EF3289E-C805-11E2-8F40-0024E808B313}, MSI Product version: ] AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18) +++ Did not detect app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18) ActionType - Install will use Content Id: Content_23c52018-ad4a-40de-8b22-e904fcfeb8d7 + Content Version: 1 for AppDT "PaperCut MF Client - Windows Installer (*.msi file)" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8], Revision - 1 AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18) ActionType - Install will use Content Id: Content_23c52018-ad4a-40de-8b22-e904fcfeb8d7 + Content Version: 1 for AppDT "PaperCut MF Client - Windows Installer (*.msi file)" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8], Revision - 1 AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18) You may want to also check your "PaperCut MF Client" package and make sure that the source files are present.

in looking at the logs (ccmexec.log & the smsts.log in the ccm folder), I think that the second app (PaperCut MF Client) is invoking a reboot outside of SCCM's control. Have a look in the NT event logs to see if you see a reboot being called around 10:53am (client time). Perhaps you can place a "restart computer" step in between the application installs until you can figure out which one(s) require a reboot and control it. From SMSTS.log: Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/Application_235b8c8d-16fe-4880-9bca-e6023045199e'='{9B5A9551-DF84-4C4D-A00D-A9C15963E194}' InstallApplication 8/21/2014 10:53:00 AM 2248 (0x08C8) Waiting for installation job to complete.. InstallApplication 8/21/2014 10:53:00 AM 2248 (0x08C8) From CCMEXEC.log: Notifying endpoint 'DCMAgent' of __InstanceCreationEvent settings change on object CCM_ApplicationCIAssignment.AssignmentID="DEP-LCG2004E-ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/Application_235b8c8d-16fe-4880-9bca-e6023045199e" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4) Notifying endpoint 'CIStore' of __InstanceCreationEvent settings change on object CCM_CIVersionInfo.ModelName="ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/Application_235b8c8d-16fe-4880-9bca-e6023045199e",Version="3" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4) Notifying endpoint 'CIStore' of __InstanceCreationEvent settings change on object CCM_CIVersionInfo.ModelName="ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8",Version="1" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4) Notifying endpoint 'CIStore' of __InstanceCreationEvent settings change on object CCM_CIVersionInfo.ModelName="ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/RequiredApplication_235b8c8d-16fe-4880-9bca-e6023045199e",Version="3" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4) Notifying endpoint 'PolicyAgent_PolicyEvaluator' of __AggregateEvent settings change on object for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:59 AM 1032 (0x0408) WM_QUIT received in the main message loop. CcmExec 8/21/2014 10:53:19 AM 1536 (0x0600) Shutting down CCMEXEC... CcmExec 8/21/2014 10:53:19 AM 1536 (0x0600) BEGIN ExecuteSystemTasks('PreShutdown') CcmExec 8/21/2014 10:53:19 AM 1532 (0x05FC) Using system task exclusion list 'SchedulerStartup;SchedulerShutdown;SchedulerLogon;SchedulerLogoff;ClientRegistrationStartup'. CcmExec 8/21/2014 10:53:19 AM 1532 (0x05FC) Invoking system task 'StatusAgentShutdown'. CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70) Invoking system task 'PolicyEvaluator_PreShutdown' via ICcmSystemTask2 interface. CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70) Invoking system task 'MtcShutdown'. CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70) END ExecuteSystemTasks('PreShutdown') CcmExec 8/21/2014 10:53:20 AM 1532 (0x05FC) BEGIN ExecuteSystemTasks('Shutdown') CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70)

Also check the root of the c: drive for a folder called smstslog (I believe). There may be some logs left in that directory that are not being copied to the ccm\logs directory in the event of a failed deployment.

Schikitar, The smsts.log file should be present on a machine, even if it failed the osd. Have you tried enabling f8 support? If you have, you could try launching task manager during the osd to see if you can see any errant processes that may be causing the issue. Please post all the logs from the ccm\logs directory from the next failed deployment. Also, have you looked at the reports from a machine that failed? Does that give any clues as to the cause? Paul

Schikitar, The only time I've seen the OSD hang like that is when the app that's being installed is waiting for a user response. Is it the same app that's hanging the process, or different ones? Have you tried enabling F8 support and viewing the smsts.log file in real time (speaking of that, it's missing in the logs you posted). Another thing to do would be to try installing the app in question as system on a fully functional system to see what the behavior is (does it install successfully or does it hang).

Hi J Mac, I came across a powershell script that does most of what you need. You can probably tweak it to better suit your needs. You can find it at the link below. http://www.powershellpro.com/why-i-no-longer-hate-writing-documentation/614/ Hope this helps! Paul

I have used the following in an SCCM OSD to apply updates that are not present in the updates folder. It worked well for my needs. http://myitforum.com/myitforumwp/2012/01/04/workaround-for-installing-office-updates-during-an-image-build/

have you advertised to the "All Systems" collection, or "Unknown Computers" collection?

The following line from the smspxe.log file indicates that the machine is already known to SCCM, which will prevent it from being imaged again until you delete it from the console (assuming the MAC below is tied to the machine in question): MAC: GUID: Status: 18:A9:05:F9:6E:C5, 816A6538-BB0B-11DF-BBDA-05F96EC518A9: device is in the database.]LOG]!><time="09:28:15.790-120" date="07-03-2014" Try deleting the device from the SCCM console and see if it then allows you to image.

you say you have two primary sites, are they independant, or are you using a CAS? If on a CAS, have you advertised from the CAS? On the site where it's not working, have you reviewed the smspxe.log file to see what it's logging when that mahcine pxe boots?

here's an export of a TS I've used. It checks to see if Java 1.6 is installed, and if it is, removes it and installs 1.6_45. It then installs 1.7_51. Java.xml

What have you tried using so far?

Hi JimmyJ, I was looking for something similar to use during OSD. I found the following link and was able to come up with a solution based on it (also posted what works for my situation): http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/enabledisable-network-interface-via-command-line/17a21634-c5dd-4038-bc0a-d739209f5081?page=2&msgId=a3a0ad24-56d1-4768-9c5d-a4487f36bf37 Hope this helps. Paul

I would check the clientlocation.log file first, see what MP your client is communicating with, then verify that the package is present on the DP.