Jump to content


Search the Community

Showing results for tags '1702 update'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

Website URL

Location

Interests

Found 1 result

  1. Admiral Awesome
    Hi, I had to update my SCCM environment to 1702 due to the Office 365 update bug. The upgrade went okay until the install procedure copied the new x86 and x64 boot images. Now the installation seems to be stuck for around an hour (nothing happens in cmupdate.log) These are the last messages my SCCM delivered: INFO: Default SMS_BootPackageImage instance for x64 already exists. Updating the instance now. CONFIGURATION_MANAGER_UPDATE 28.04.2017 14:45:55 11116 (0x2B6C) INFO: The source path for the old boot image package is \\blanked out\SMS_PS1\osd\boot\x64\boot.PS100005.wim CONFIGURATION_MANAGER_UPDATE 28.04.2017 14:45:55 11116 (0x2B6C) INFO: Successfully copied the new source WIM file from \blanked out\SMS_PS1\osd\boot\x64\boot.wim to \\blanked out\SMS_PS1\osd\boot\x64\boot.PS100005.wim CONFIGURATION_MANAGER_UPDATE 28.04.2017 14:45:56 11116 (0x2B6C) Should I just roll back to my previously made snapshot or wait further until something happens? There are no errors in the log that I could think of being the reason of this?
×
×
  • 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.