Hi All, The switch was implemented by a consultant we are using. I’m not entirely sure of his reasons but I will give that a go.
Thanks Mike [cid:imageeea051.JPG@ebbe5eac.4b84f563] Michael Adamson IT Infrastructure Manager A: 741 Nudgee Road Northgate QLD 4013 T: +61 7 3117 3300 F: +61 7 3117 3381 E: madam...@healthworld.com.au W: www.healthworld.com.au From: Andreas Hammarskjöld [mailto:jun...@2pintsoftware.com] Sent: Tuesday, 27 September 2016 3:44 AM To: mssms@lists.myitforum.com; Michael Adamson <madam...@healthworld.com.au> Subject: RE: [mssms] SCCM OSD failures Yeah, think the AD polices also comes down if you kill that key. Typically what you can run into is that all sorts of things happens on the machine when you just wants to install some software. 2 MSI’s cant run at the same time etc. //A From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: den 26 september 2016 08:06 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>; Michael Adamson <madam...@healthworld.com.au<mailto:madam...@healthworld.com.au>> Subject: RE: [mssms] SCCM OSD failures FYI, can confirm. Provisioning Mode is required while the machine is running the Task Sequence. SCCM will remove the client from Provisioning Mode once the TS completes successfully, unless you have an unexpected reboot or something else that takes control away from SCCM during the build. Don’t ever just turn off Provisioning Mode, find the root cause in your TS and fix that! Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeff Poling Sent: Sunday, September 25, 2016 10:17 PM To: Michael Adamson <madam...@healthworld.com.au<mailto:madam...@healthworld.com.au>>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM OSD failures Just a quick look at the logs. . .here is the error: [cid:image002.jpg@01D218C0.1EF38930] I noticed that there are several post-client installation steps that are part of the task sequence, one of which is a step that does this: ProgramName = 'REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f' Why are you removing the client from provisioning mode during the task sequence? There should be no need for that and that may actually be causing the problem. Can you try disabling those steps used to configure the client and see if you get better results? Jeff ________________________________ From: madam...@healthworld.com.au<mailto:madam...@healthworld.com.au> To: jeffrey.d.pol...@outlook.com<mailto:jeffrey.d.pol...@outlook.com> Subject: RE: [mssms] SCCM OSD failures Date: Mon, 26 Sep 2016 00:48:20 +0000 Hi John Please find the attached logs. Thanks Mike [cid:image004.jpg@01D218C0.1EF38930] Michael Adamson IT Infrastructure Manager A: 741 Nudgee Road Northgate QLD 4013 T: +61 7 3117 3300 F: +61 7 3117 3381 E: madam...@healthworld.com.au<https://madam...@healthworld.com.au> W: www.healthworld.com.au<https://www.healthworld.com.au> From: Jeff Poling [mailto:jeffrey.d.pol...@outlook.com] Sent: Wednesday, 21 September 2016 10:08 AM To: Michael Adamson <madam...@healthworld.com.au<mailto:madam...@healthworld.com.au>>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM OSD failures Can you provide an smsts.log for review? Having the full context of the error helps in diagnosing it. Jeff Sent from my Windows 10 phone From: Michael Adamson<mailto:madam...@healthworld.com.au> Sent: Tuesday, September 20, 2016 6:06 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] SCCM OSD failures Hi, I have rather weird OSD issues we have been battling for a long while and I’m hoping the list can help me out. Our environment is pretty simple, a single SCCM 2012 R2 SP1 /w CU3 (Site Version 5.00.8239.1000) server doing everything running on Server 2012. The symptoms presented appear to contradict each other below and have been ongoing for around 6 months. We have now upgraded to CU3 with no difference. Symptoms • OSD error code “download failed error 87d00267” or “access denied” when client tries to download the packages • OSD will fail on either Windows 7 x64 and Windows 8.1 x64 • Sometimes it will fail on Java or Silverlight or Adobe Reader or other applications. Re-running an OSD will usually fail at a different application. Disabling a package means that it fails on the next application. • Running two machines at the same time, with the same TS can have different results. i.e one will work and one will fail • Always fails during an application install, i.e after WIM is applied, drivers applied and SCCM agent is installed • I have tried it on hardware (Lenovo P500 – Xeon with SSD and Lenovo T460s with SSD) and VMs (Hyper-V) • Re-Running the OSD usually has a different package that fails or it might succeed Changes to SCCM • I have added some new driver packs-testing confirms drivers are working as expected. Appling or not Appling as expected. • Changed back the TFTP setting to 4096 – only slowed PXE booting down • Rebooted SCCM server multiple times • Doubled CPU to 4 cores on server • Increased RAM to 24GB – it is only using ~8GB • Confirmed free space • Tried a delay in the Win81 TS - https://social.technet.microsoft.com/Forums/en-US/c0e01eed-7beb-4e18-bc09-bb153c7082ad/osd-failing-on-random-application-installations?forum=configmanagerapps • Applied CU3 Observations • Server is not wanting for grunt and can be monitored using 500-600mbs network throughput to the client during WIM/driver pack download. Thanks Mike [cid:image004.jpg@01D218C0.1EF38930] Michael Adamson IT Infrastructure Manager A: 741 Nudgee Road Northgate QLD 4013 T: +61 7 3117 3300 F: +61 7 3117 3381 E: madam...@healthworld.com.au<https://madam...@healthworld.com.au> W: www.healthworld.com.au<https://www.healthworld.com.au> ________________________________ This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks with regards to this message or any attachments. We cannot accept liability for any loss or damage caused by software viruses. ________________________________ This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks with regards to this message or any attachments. We cannot accept liability for any loss or damage caused by software viruses. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks with regards to this message or any attachments. We cannot accept liability for any loss or damage caused by software viruses.