Jump to content


dozi

Established Members
  • Posts

    16
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Germany

dozi's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thank you so much, that worked like a charm! Greetings, D.Ziegler
  2. Does anybody know this message and how to turn it off? It appears after a while in my new Windows 10 2016 LTSB image when its deployed on a new machine. Greetings, D.Ziegler
  3. Use this solution with vendor classes in dhcp: http://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/ Regards, D.Ziegler
  4. Hello folks, have you seen this behaivor? Seems like the titles of the updates are corrupted in a awkward way. Can i delete those updates manually? Regards, dozi
  5. Adding a restart after client install did the trick. So the thread can be closed . Regards, dozi
  6. Dear Folks, i got a problem with the Application Installation step within an task sequence. The problem only occurs on an Dell Venue 11 Pro 7140 device with Windows 8.1. The App is Adobe Acrobat Pro XI with all the patches packed in setup.ini. This works on every other device with W7 and W8.1. I have set up the installation of UEFI due to this error. But this does not work aswell. The task sequence does simply not continue after the installation of Adobe Acrobat. It stays there forever. I have a screenshot attached. In the AppEnforce.log, the installation shows exit code "0" and the detection of the software was successfull. After canceling the ts i can start Adobe Acrobat without problems. I have really no idea of whats going on here. Regards, dozi logs.zip
  7. Hello, in ran into an strange behavior with updating Adobe Acrobat Pro/Reader to version 11.0.09. The detection method is set to MSI with version equal to "11.0.09". The version installed on the targeted client is "11.0.08". The application logs tell me, that the patch is already installed and skips the installation of the patch. Registry and WMI show version "11.0.08" instead. I have no idea whats going wrong here. Attached you will find some screenshots of the problem. Kindly regards, dozi
  8. May you have just to readd the applications to your UDI-wizard via the designer?
  9. Absolutely no problems after the TS finishes. Just wanted to no if theres a problem with our OSD. Its simply annoying that we cant use the monitoring feature like its meant ...
  10. Hi, we got a collection for each version of Adobe Reader XI, because the updates are not incremental, except some major releases, as far as i know. The clients will automatically move to the next collection and so on. You can see it on the attached image.
  11. Ok, after some researching and stuff, theres an error on the end of the TS: End program: cmd /c shutdown /r /t 0 /f TSManager 05.08.2014 14:42:31 1564 (0x061C) Finalize logging request ignored from process 1528 TSManager 05.08.2014 14:42:31 1564 (0x061C) Waiting for CcmExec service to be fully operational TSManager 05.08.2014 14:42:31 1564 (0x061C) CcmExec service is up and fully operational TSManager 05.08.2014 14:42:31 1564 (0x061C) Access handle will be read from _SMSTSActiveRequestHandle TSManager 05.08.2014 14:42:31 1564 (0x061C) Access handle: {2B55AA51-7853-439B-8F7E-7C5D801C1416} TSManager 05.08.2014 14:42:31 1564 (0x061C) Attempting to release request using {2B55AA51-7853-439B-8F7E-7C5D801C1416} TSManager 05.08.2014 14:42:31 1564 (0x061C) CoCreateInstance succeeded TSManager 05.08.2014 14:42:31 1564 (0x061C) pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 05.08.2014 14:42:31 1564 (0x061C) ReleaseRequest failed with error code 0x80004005 TSManager 05.08.2014 14:42:31 1564 (0x061C) Task Sequence Manager could not release active TS request. code 80004005 TSManager 05.08.2014 14:42:31 1564 (0x061C) Process completed with exit code 0 TSMBootstrap 05.08.2014 14:42:31 1924 (0x0784) Exiting with return code 0x00000000 TSMBootstrap 05.08.2014 14:42:31 1924 (0x0784) Process completed with exit code 0 OSDSetupHook 05.08.2014 14:42:31 1016 (0x03F8) Task sequence completed 0x00000000 OSDSetupHook 05.08.2014 14:42:31 1016 (0x03F8) Waiting for command shell to complete. OSDSetupHook 05.08.2014 14:42:31 1800 (0x0708) Resume SCCM Client. OSDSetupHook 05.08.2014 14:42:31 1016 (0x03F8) Uninstalling Setup Hook OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Removing setup hook from registry. OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully removed C:\WINDOWS\system32\OSDGINA.DLL OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully removed C:\WINDOWS\system32\_SMSOSDSetup OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) End program: cmd /c shutdown /r /t 0 /f OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) But it says "Task Sequence Completed" with "0". So i don't get it ... Attached you will find the log-files from that deployment. smsts.log smsts-20140805-144202.log smsts-20140805-234018.log
  12. Yep, the last step (SMSTSPostAction) is executed. I have manually confirmed it trough the logs aswell. All is fine here. Any ideas?
  13. Hello, i have configured the monitoring from the MDT-Workbench and it works like a charm. I can see the SCCM-Task-Sequences running and reporting every time the MDT-Gather step runs. My only problem is now, that i would not show, when the TS is finished. It hangs on "Running" forever and change to "not responding" after some time. Do i need some "finishing" step at the end of the UDI-Tasksequence to inform the Monitoring-Web-Service that the TS is finished? I have tryed to put a "Gather"-Step at the end, but its not working. Additionally i have added a FinishAction= and SkipFinalSummary= Step to the CustomSettings.ini in the settings-files. Haven't tested that yet, because of running installations of other users. Is that maybe the right step? Thanks for helping. Dominik
  14. Hello everyone, solved. I installed the new .NET Package 4.5.2 on the master image. Now it works without any problems again. Regards, D.Ziegler
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.