locked
Installed programs are missing after PC crash RRS feed

  • Question

  • Just if someone can give me an explanation. We are deploying OSD and task sequence to install products like MS Office, Anti-Virus... But at times with some computers everything seems to install without problems. The user starts using the compture with all the software that is installed. But after sometime (it can be 2-3 months) the PC goes to "system restore", drops out of the Domain. When investigating we see that some software is missing on the computer, looking at the installed programs in control panel, we can actually see that this program are missing. When we look at the SMSTS log, we can actually see that the installation did not finish only the programs that were seen in the SMSTS log as installed are the only ones that are seen in the computer but the rest are missing. I can also see that C:\_SMSTasksequence folder exists with some subfolders, I think meaning that the installation was not complete
    So my question is that, how has this user been using this programs for over 2 months until the computer crashed. Was the user using this in cache mode or something like that? SCCM 2012 R2 CU1

    An example of the last part of the smsts log is like this:

    Setting TSEnv variable 'SMSTSInstallSoftwareJobID_KUL0001C_KUL20105_Microsoft .Net 4.0 Installation'='{02D2FBAF-5B2D-4E5C-9EB1-8F429986A9E3}' InstallSoftware 18.02.2014 16:52:18 3768 (0x0EB8)
    Waiting for installation job to complete.. InstallSoftware 18.02.2014 16:52:18 3768 (0x0EB8)
    Waiting for job status notification... InstallSoftware 18.02.2014 16:52:48 3768 (0x0EB8)

    Friday, May 16, 2014 7:46 AM

Answers

  • It almost sounds like there is a new OSD sequence being deployed to the machines, reformatting the drive, and having an issue before deployment completes. It is far more likely something has reimaged the machine and just not reinstalling everything than it is that a task sequence is removing all these specific apps and disjoining the domain?

    Daniel Ratliff | http://www.PotentEngineer.com

    • Marked as answer by Juke Chou Sunday, June 8, 2014 11:12 AM
    Monday, May 19, 2014 3:07 PM

All replies

  • An example of the last part of the smsts log is like this:

    Setting TSEnv variable 'SMSTSInstallSoftwareJobID_KUL0001C_KUL20105_Microsoft .Net 4.0 Installation'='{02D2FBAF-5B2D-4E5C-9EB1-8F429986A9E3}' InstallSoftware 18.02.2014 16:52:18 3768 (0x0EB8)
    Waiting for installation job to complete.. InstallSoftware 18.02.2014 16:52:18 3768 (0x0EB8)
    Waiting for job status notification... InstallSoftware 18.02.2014 16:52:48 3768 (0x0EB8)


    That logfile is 3 months old. Does it really end at that point?
    I don't think that those events are related though.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 16, 2014 8:07 AM
  • That was the date the OSD was deployed and the log file ends here. And the user has been using the computer until it crashed. So looking at the smsts log, this what we saw.
    Friday, May 16, 2014 10:50 AM
  • Can you post the related execmgr.log? It may give more detail into the execution of your install. Do you have an install log from .NET as well?

    Daniel Ratliff | http://www.PotentEngineer.com

    Friday, May 16, 2014 2:02 PM
  • Where do I get the .NET log file ? Here is the execmgr.log

    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 18.02.2014 15:56:14 3948 (0x0F6C)
    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 18.02.2014 15:56:15 3728 (0x0E90)
    Service startup. execmgr 18.02.2014 15:56:21 3192 (0x0C78)
    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 18.02.2014 15:56:22 3192 (0x0C78)
    Software distribution agent was enabled execmgr 18.02.2014 16:01:21 3312 (0x0CF0)
    ExecMgr::GetTaskState - GetTaskState Failed with error code 0x87d00317 execmgr 18.02.2014 16:01:28 2144 (0x0860)
    Creating mandatory request for advert KUL20105, program Office 2010 Pro+ Proofing Tools Installation, package KUL0001B execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Policy arrived for child program Office 2010 Pro+ Proofing Tools Installation execmgr 18.02.2014 16:29:06 4028 (0x0FBC)
    An existing MTC token was supplied, this execution request is not owner of MTC object. execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Request a MTC task for execution request of package KUL0001B, program Office 2010 Pro+ Proofing Tools Installation with request id: {10B304B9-4A5E-42FD-98DB-A63F025722CE} execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Executing program 32bit\setup.exe /config "\\sccm\Packages\Office 2010 Pro+ with SP1 & Proofing Tools\32bit\ProofKit.WW\config.xml" in Admin context execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Execution Request for advert KUL20105 package KUL0001B program Office 2010 Pro+ Proofing Tools Installation state change from NotExist to NotifyExecution execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Checking content location C:\_SMSTaskSequence\Packages\KUL0001B for use execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Successfully selected content location C:\_SMSTaskSequence\Packages\KUL0001B execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Executing program as a script execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Successfully prepared command line "C:\_SMSTaskSequence\Packages\KUL0001B\32bit\setup.exe" /config "\\sccm\Packages\Office 2010 Pro+ with SP1 & Proofing Tools\32bit\ProofKit.WW\config.xml" execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Command line = "C:\_SMSTaskSequence\Packages\KUL0001B\32bit\setup.exe" /config "\\sccm\Packages\Office 2010 Pro+ with SP1 & Proofing Tools\32bit\ProofKit.WW\config.xml", Working Directory = C:\_SMSTaskSequence\Packages\KUL0001B\ execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Created Process for the passed command line execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     CommandLine = "\"C:\\_SMSTaskSequence\\Packages\\KUL0001B\\32bit\\setup.exe\" /config \"\\\\sccm\\Packages\\Office 2010 Pro+ with SP1 & Proofing Tools\\32bit\\ProofKit.WW\\config.xml\"";
     DateTime = "20140218142906.632000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL0001B";
     ProcessID = 2752;
     ProgramName = "Office 2010 Pro+ Proofing Tools Installation";
     SiteCode = "KUL";
     ThreadID = 3800;
     UserContext = "NT AUTHORITY\\SYSTEM";
     WorkingDirectory = "C:\\_SMSTaskSequence\\Packages\\KUL0001B\\";
    };
     execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Raised Program Started Event for Ad:KUL20105, Package:KUL0001B, Program: Office 2010 Pro+ Proofing Tools Installation execmgr 18.02.2014 16:29:06 3800 (0x0ED8)
    Program exit code 0 execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Looking for MIF file to get program status execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Script for  Package:KUL0001B, Program: Office 2010 Pro+ Proofing Tools Installation succeeded with exit code 0 execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramCompletedSuccessfullyEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     DateTime = "20140218143227.603000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL0001B";
     ProcessID = 2752;
     ProgramName = "Office 2010 Pro+ Proofing Tools Installation";
     SiteCode = "KUL";
     ThreadID = 3184;
     UserContext = "NT AUTHORITY\\SYSTEM";
    };
     execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Raised Program Success Event for Ad:KUL20105, Package:KUL0001B, Program: Office 2010 Pro+ Proofing Tools Installation execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Execution is complete for program Office 2010 Pro+ Proofing Tools Installation. The exit code is 0, the execution status is Success execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Execution Request for advert KUL20105 package KUL0001B program Office 2010 Pro+ Proofing Tools Installation state change from Running to Completed execmgr 18.02.2014 16:32:27 3184 (0x0C70)
    Requesting MTC to delete task with id: {5BE6AADA-CEAC-46F5-87B3-9655B1DF8181} execmgr 18.02.2014 16:32:27 3128 (0x0C38)
    This execution request does not own the corresponding task in MTC, returning without deleting it from MTC. execmgr 18.02.2014 16:32:27 3128 (0x0C38)
    Policy arrived for child program SAP GUI 7.10 INSTALLATION execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Creating mandatory request for advert KUL20105, program SAP GUI 7.10 INSTALLATION, package KUL00014 execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    An existing MTC token was supplied, this execution request is not owner of MTC object. execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Request a MTC task for execution request of package KUL00014, program SAP GUI 7.10 INSTALLATION with request id: {14E2A224-0D5C-4A4A-BF9F-4C67A4196AB6} execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Executing program PRES1\GUI\WINDOWS\WIN32\Setup\NwSapSetup.exe /Silent /Product="SAPGUI710" in Admin context execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Execution Request for advert KUL20105 package KUL00014 program SAP GUI 7.10 INSTALLATION state change from NotExist to NotifyExecution execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Checking content location C:\_SMSTaskSequence\Packages\KUL00014 for use execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Successfully selected content location C:\_SMSTaskSequence\Packages\KUL00014 execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Executing program as a script execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Successfully prepared command line "C:\_SMSTaskSequence\Packages\KUL00014\PRES1\GUI\WINDOWS\WIN32\Setup\NwSapSetup.exe" /Silent /Product="SAPGUI710" execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Command line = "C:\_SMSTaskSequence\Packages\KUL00014\PRES1\GUI\WINDOWS\WIN32\Setup\NwSapSetup.exe" /Silent /Product="SAPGUI710", Working Directory = C:\_SMSTaskSequence\Packages\KUL00014\ execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Created Process for the passed command line execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     CommandLine = "\"C:\\_SMSTaskSequence\\Packages\\KUL00014\\PRES1\\GUI\\WINDOWS\\WIN32\\Setup\\NwSapSetup.exe\" /Silent /Product=\"SAPGUI710\"";
     DateTime = "20140218145034.654000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL00014";
     ProcessID = 2752;
     ProgramName = "SAP GUI 7.10 INSTALLATION";
     SiteCode = "KUL";
     ThreadID = 3904;
     UserContext = "NT AUTHORITY\\SYSTEM";
     WorkingDirectory = "C:\\_SMSTaskSequence\\Packages\\KUL00014\\";
    };
     execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Raised Program Started Event for Ad:KUL20105, Package:KUL00014, Program: SAP GUI 7.10 INSTALLATION execmgr 18.02.2014 16:50:34 3904 (0x0F40)
    Program exit code 0 execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Looking for MIF file to get program status execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Script for  Package:KUL00014, Program: SAP GUI 7.10 INSTALLATION succeeded with exit code 0 execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramCompletedSuccessfullyEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     DateTime = "20140218145130.662000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL00014";
     ProcessID = 2752;
     ProgramName = "SAP GUI 7.10 INSTALLATION";
     SiteCode = "KUL";
     ThreadID = 3076;
     UserContext = "NT AUTHORITY\\SYSTEM";
    };
     execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Raised Program Success Event for Ad:KUL20105, Package:KUL00014, Program: SAP GUI 7.10 INSTALLATION execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Execution is complete for program SAP GUI 7.10 INSTALLATION. The exit code is 0, the execution status is Success execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Execution Request for advert KUL20105 package KUL00014 program SAP GUI 7.10 INSTALLATION state change from Running to Completed execmgr 18.02.2014 16:51:30 3076 (0x0C04)
    Requesting MTC to delete task with id: {5BE6AADA-CEAC-46F5-87B3-9655B1DF8181} execmgr 18.02.2014 16:51:30 3904 (0x0F40)
    This execution request does not own the corresponding task in MTC, returning without deleting it from MTC. execmgr 18.02.2014 16:51:30 3904 (0x0F40)
    Policy arrived for child program SAPREG execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Creating mandatory request for advert KUL20105, program SAPREG, package KUL0001E execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    An existing MTC token was supplied, this execution request is not owner of MTC object. execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Request a MTC task for execution request of package KUL0001E, program SAPREG with request id: {12A58D36-079A-4F43-92AC-68340983C7F5} execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Executing program sapreg.bat in Admin context execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Execution Request for advert KUL20105 package KUL0001E program SAPREG state change from NotExist to NotifyExecution execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Checking content location C:\_SMSTaskSequence\Packages\KUL0001E for use execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Successfully selected content location C:\_SMSTaskSequence\Packages\KUL0001E execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Executing program as a script execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Successfully prepared command line "C:\_SMSTaskSequence\Packages\KUL0001E\sapreg.bat" execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Command line = "C:\_SMSTaskSequence\Packages\KUL0001E\sapreg.bat", Working Directory = C:\_SMSTaskSequence\Packages\KUL0001E\ execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Created Process for the passed command line execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     CommandLine = "\"C:\\_SMSTaskSequence\\Packages\\KUL0001E\\sapreg.bat\"";
     DateTime = "20140218145134.515000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL0001E";
     ProcessID = 2752;
     ProgramName = "SAPREG";
     SiteCode = "KUL";
     ThreadID = 3904;
     UserContext = "NT AUTHORITY\\SYSTEM";
     WorkingDirectory = "C:\\_SMSTaskSequence\\Packages\\KUL0001E\\";
    };
     execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Raised Program Started Event for Ad:KUL20105, Package:KUL0001E, Program: SAPREG execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Program exit code 0 execmgr 18.02.2014 16:51:34 3076 (0x0C04)
    Looking for MIF file to get program status execmgr 18.02.2014 16:51:34 3076 (0x0C04)
    Script for  Package:KUL0001E, Program: SAPREG succeeded with exit code 0 execmgr 18.02.2014 16:51:34 3076 (0x0C04)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramCompletedSuccessfullyEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     DateTime = "20140218145134.952000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL0001E";
     ProcessID = 2752;
     ProgramName = "SAPREG";
     SiteCode = "KUL";
     ThreadID = 3076;
     UserContext = "NT AUTHORITY\\SYSTEM";
    };
     execmgr 18.02.2014 16:51:34 3076 (0x0C04)
    Raised Program Success Event for Ad:KUL20105, Package:KUL0001E, Program: SAPREG execmgr 18.02.2014 16:51:34 3076 (0x0C04)
    Execution is complete for program SAPREG. The exit code is 0, the execution status is Success execmgr 18.02.2014 16:51:34 3008 (0x0BC0)
    Execution Request for advert KUL20105 package KUL0001E program SAPREG state change from Running to Completed execmgr 18.02.2014 16:51:34 3008 (0x0BC0)
    Requesting MTC to delete task with id: {5BE6AADA-CEAC-46F5-87B3-9655B1DF8181} execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    This execution request does not own the corresponding task in MTC, returning without deleting it from MTC. execmgr 18.02.2014 16:51:34 3904 (0x0F40)
    Policy arrived for child program VLC Media Player 2.0.7 Installation execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Creating mandatory request for advert KUL20105, program VLC Media Player 2.0.7 Installation, package KUL00006 execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    An existing MTC token was supplied, this execution request is not owner of MTC object. execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Request a MTC task for execution request of package KUL00006, program VLC Media Player 2.0.7 Installation with request id: {773205CC-0D0B-4447-B733-B65D5651B07C} execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Executing program vlc-2.0.7-win32.exe /L=1033 = EN-us /S in Admin context execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Execution Request for advert KUL20105 package KUL00006 program VLC Media Player 2.0.7 Installation state change from NotExist to NotifyExecution execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Checking content location C:\_SMSTaskSequence\Packages\KUL00006 for use execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Successfully selected content location C:\_SMSTaskSequence\Packages\KUL00006 execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Executing program as a script execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Successfully prepared command line "C:\_SMSTaskSequence\Packages\KUL00006\vlc-2.0.7-win32.exe" /L=1033 = EN-us /S execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Command line = "C:\_SMSTaskSequence\Packages\KUL00006\vlc-2.0.7-win32.exe" /L=1033 = EN-us /S, Working Directory = C:\_SMSTaskSequence\Packages\KUL00006\ execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Created Process for the passed command line execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     CommandLine = "\"C:\\_SMSTaskSequence\\Packages\\KUL00006\\vlc-2.0.7-win32.exe\" /L=1033 = EN-us /S";
     DateTime = "20140218145144.827000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL00006";
     ProcessID = 2752;
     ProgramName = "VLC Media Player 2.0.7 Installation";
     SiteCode = "KUL";
     ThreadID = 3340;
     UserContext = "NT AUTHORITY\\SYSTEM";
     WorkingDirectory = "C:\\_SMSTaskSequence\\Packages\\KUL00006\\";
    };
     execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Raised Program Started Event for Ad:KUL20105, Package:KUL00006, Program: VLC Media Player 2.0.7 Installation execmgr 18.02.2014 16:51:44 3340 (0x0D0C)
    Program exit code 0 execmgr 18.02.2014 16:51:55 3008 (0x0BC0)
    Looking for MIF file to get program status execmgr 18.02.2014 16:51:55 3008 (0x0BC0)
    Script for  Package:KUL00006, Program: VLC Media Player 2.0.7 Installation succeeded with exit code 0 execmgr 18.02.2014 16:51:55 3008 (0x0BC0)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramCompletedSuccessfullyEvent
    {
     AdvertisementId = "KUL20105";
     ClientID = "GUID:b46aaa3e-fc95-4e41-aba0-78ee02447038";
     DateTime = "20140218145155.560000+000";
     MachineName = "BLC_MD_LAB";
     PackageName = "KUL00006";
     ProcessID = 2752;
     ProgramName = "VLC Media Player 2.0.7 Installation";
     SiteCode = "KUL";
     ThreadID = 3008;
     UserContext = "NT AUTHORITY\\SYSTEM";
    };
     execmgr 18.02.2014 16:51:55 3008 (0x0BC0)
    Raised Program Success Event for

    Friday, May 16, 2014 2:13 PM
  • Executing program 32bit\setup.exe /config "\\sccm\Packages\Office 2010 Pro+ with SP1 & Proofing Tools\32bit\ProofKit.WW\config.xml" in Admin context execmgr 18.02.2014 

    You cannot call network locations \\sccm\packages by default, because ConfigMgr installs as LOCAL SYSTEM. It will not have access to a network share. You need to change that reference to something local within your content like below.

    32bit\setup.exe /config "32bit\ProofKit.WW\config.xml"

    For the setup log you need to add the switch to the .NET install to output to a log.

    http://blogs.msdn.com/b/astebner/archive/2012/01/15/10256984.aspx


    Daniel Ratliff | http://www.PotentEngineer.com

    Friday, May 16, 2014 2:50 PM
  • Thanks for that information, my question still remains as to why all the programs were working even Msoffice and MS Proofing tools on the users computer for over 2 months until the computer crashed to "system restore", then when looking at logs we can see that the installation had failed but during the installation there was not error at all that installation had failed. Only the programs in the task sequence before MS Proofing tools could been seen as installed in control panel.
    Saturday, May 17, 2014 1:06 PM
  • I think Torsten is right, these events are not related to the original OSD task sequence. If you are analyzing the users machine after the crash and the apps are missing I would check the event logs for MSIinstaller events and possible uninstalls. It doesn't seem like the OSD task sequence is the culprit here. 

    Daniel Ratliff | http://www.PotentEngineer.com

    Sunday, May 18, 2014 7:14 PM
  • I have a bunch of computers with the same symptoms,  they have been running for some time, all the applications were running, but then they crashed. All of them have c:\_SMStasksequence folder with OSD, packages... folders under this folder. and looking at the smsts log file I can see all of them got stuck when installing the applications in the task sequence (Waiting for jog status notifications.....). After the crash, only the applications that were before the last application it was trying to install remain on the computer, but the other applications are removed. The only thing that suprises me is, all that time how were this applications running in the first time. But most of the computers that were installed with the same OSD deployment and task sequence completed successfuly when looking at the smsts log and never crashed, they don't have c:\_smstasksequence folder. An example of the last part of the log smsts log file of successfuly installed computer is below.

    Removing setup hook from registry.    OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)
    Successfully removed C:\Windows\system32\OSDGINA.DLL OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)
    Could not delete the file C:\Windows\system32\OSDSETUPHOOK.EXE. Error code 5           OSDSetupHook            15.04.2014 09:57:38   2440 (0x0988)
    Marking the file C:\Windows\system32\OSDSETUPHOOK.EXE for deletion on Reboot          OSDSetupHook            15.04.2014 09:57:38   2440 (0x0988)
    Successfully removed C:\Windows\system32\OSDSETUPHOOK.EXE            OSDSetupHook           15.04.2014 09:57:38          2440 (0x0988)
    Successfully removed C:\Windows\system32\_SMSOSDSetup           OSDSetupHook           15.04.2014 09:57:38            2440 (0x0988)
    ::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,811)     OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram            OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)
    GetTsRegValue() is unsuccessful. 0x80070002.         OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)
    End program:   OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)
    Finalizing logging from process 2436  OSDSetupHook           15.04.2014 09:57:38   2440 (0x0988)

    Monday, May 19, 2014 8:30 AM
  • After the crash, only the applications that were before the last application it was trying to install remain on the computer, but the other applications are removed.


    Are you really sure that the applications were present on the computers before it crashed? smsts.log indicates that the task sequence did not finish (so my guess is that not all applications were installed at all). It's next to impossible to find the reason here in the forums. You have to investigate what's common between those machines (make/model, location etc) and why the TS failed in first place.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 19, 2014 9:15 AM
  • That is why I am puzzled too. The technicians who install the computers always check if all the programs are installed before handing them to the users. Some can use them for 2 months till it crashes. The other thing is that even the programs they install manually after OSD deployment are removed too and the computer is disjoined from the Domain. I have been invetigating this issue for some weeks now. At first we thought it was "system restore" issue and we try to disable this option using GPO. But after more investigation, with those computers that crashed all had this in common (c:\_smstasksequence and installation seems to have stopped).  Make/Model, location does not matter. We have one Primary and 26 Distribution Points.
    Monday, May 19, 2014 2:55 PM
  • It almost sounds like there is a new OSD sequence being deployed to the machines, reformatting the drive, and having an issue before deployment completes. It is far more likely something has reimaged the machine and just not reinstalling everything than it is that a task sequence is removing all these specific apps and disjoining the domain?

    Daniel Ratliff | http://www.PotentEngineer.com

    • Marked as answer by Juke Chou Sunday, June 8, 2014 11:12 AM
    Monday, May 19, 2014 3:07 PM