Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

1,615 profile views

jvmorrell's Achievements


Newbie (1/14)



  1. Hi I'm trying to upgrade some surfaces pro 4 to 1803 using an OSD Inplace. (this works on other machines BTW) I seen two devices with exactly the same HARDBLOCK in the logs. OEM01.inf and OEM02.inf I cannot find what these devices are anyone got any ideas where I can find out the information, I've scanned through the full scan and searched for a Hardblock without any results. Thanks for any assistance in advanced. Cheers CompatData_2018_08_21_11_51_26_3_006f0018.xml
  2. Hi I was looking at doing an upgrade this week, have these problems now been ironed out by Microsoft? I have 1710 installed ATM so i'm abit wary to continue with the upgrade until 100% confident. The release date on the 1802 is 04/04/2018 Thanks John
  3. Hi So I've updated the ADK on my SCCM server following this guide. "anotherSCCLWebsite"/how-to-update-windows-adk-on-a-sccm-server/ It now updated to 15063 I then fixed the Secure boot Bug as below https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/ then replicated the changes using the following powershell script. https://gallery.technet.microsoft.com/RegenerateBootImageWinPE10-f508f1e4/view/Discussions#content Our SCCM version is 1702 Everything went to plan but when I boot from the PE it gets just before the log on and crashes out and reboots. I've hit f8 and brought up the command prompt to check that the device is getting a ip which it is. How do I go about debugging this issue? I was thinking about removing some of the drivers but since running all the above I seem to be missing the tabs on the SCCM console for the boot image in question. Another idea which I was thinking was install adk 1607 instead of 1703. Thanks John
  4. Hi Has anyone seen the situation where you deploy the Feature update to 1703 to a machine using windows 10 servicing, this then updates correctly but after the upgrade the update is still available in the update and has failed. But the operating system is now 1703 and the upgrade worked correctly. Thanks John
  5. Had this exact issue thanks for pointing in the right direction
  6. hi so I've upgrade to 1702 though after this clients cannot communicate back to the primary server. I'm seeing the following issues on the primary server in system logs The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {1A9FFCE9-10C1-40BC-9815-B20C1DC2D156} and APPID {AD65A69D-3831-40D7-9629-9B0B50A93843} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. management point is at critical and is flagging up a load for different errors. sMS_Providers Site Component Manager failed to reinstall this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager SMS_Providers Site Component Manager could not stop the winmgmt service on site system "\site name Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. Any one seen this, every other upgrade has gone smooth before, I have a site snapshot from VMware before update from the start of the day so I could roll back if needs be thanks for any assitance
  7. Absolutely top work, I foresee problems to forcing users to upgrade and this deferring upgrades to suit the user is something that SCCM should have built in. I migrated from Zenworks to SCCM and for all its problems there's a few bits of functionality that I miss. This is definitely one. Thanks again.
  • Create New...