Jump to content


jvmorrell

Established Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by jvmorrell

  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

    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

     

     

     

     

     

  3. 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

  4. 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.

     

     

     

    • Like 1
  5. Hi

     

    So I've had a site recovery and am seeing the exact error in this Microsoft software support

    https://support.microsoft.com/en-us/help/2890472/sql-exception-on-a-system-center-2012-configuration-manager-sp1-site-server-after-recovery

     

    How do I go about reforcing the update on to the SCCM servers? that require it.

     

    cheers in advance

  6. HI

     

    I've updated to with all the latest patches in 1610 now I'm getting the following. in the Primary site log.

     

     

    Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = DCC00003).
    Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point.
    Solution: Verify that distribution manager can access the package source directory/distribution point.
    Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
    Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
    Possible cause: There is not enough disk space available on the site server computer or the distribution point.
    Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
    Possible cause: The package source directory contains files that might be in use by an active process.
    Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.

     

     

    I've checked over access and Disk size everything is fine, All the access looks good as well. The problem is that this is not the only application/package that I'm having problems with replicating to other DP.

     

     

    Distribution Manager failed to process package "Adobe Acrobat DC (Pro)" (package ID = DCC003BC).
    Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point.
    Solution: Verify that distribution manager can access the package source directory/distribution point.
    Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
    Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
    Possible cause: There is not enough disk space available on the site server computer or the distribution point.
    Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
    Possible cause: The package source directory contains files that might be in use by an active process.
    Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.

     

     

    Anyone got any idea where to start with this problem?

     

    Thanks

     

    John

     

     

  7. Hi

     

    If I connect to our corporate VPN (CAG) Edge is not able to browse internal and external sites though IE 11 or Chrome works perfectly.

    Disconnect from the VPN and all is back working again?

     

    Seems very odd that Edge which microsoft is pushing is limited in this way?

     

    How is everyone else getting on in your enviroments?

     

    Cheers

     

    John

     

     

  8. Hi

     

    thanks for the advice, problem is that I know all of the above is fine. I can offline service a previous windows 8.1 wim. But with a newly created windows 8.1 exactly the same manor it fails every time and only gives me the options to update one windows update which is. Security update - KB3042058, If I apply this it promptly fails to apply.

     

    Anyone else seen anything like this?

  9. Hi

     

    I'm trying to offline service a Windows 8.1 image which I've built.

    I've built the wim from the Latest Windows 8.1 ISO from Ms VLS.

     

    All I've done to it is enabled .net 3.5 and built the Reference Image through SCCM

     

    when I've come to offline service it there are no patches enabled for me to do this. As shown below.

     

    this is not something I've seen before, My previous reference image worked fine, Also when I run an OSD using this WIM the updates all download as normal through the build.

     

    Anyone got any ideas whats going wrong?

     

    Also I'm on 1602

     

    Thanks

     

    john

     

     

    sccmoffline.png

     

     

×
×
  • Create New...