locked
Updating a WIndows 10 Enterprise PC that is not joined to a domain RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've installed Windows 10 Enterprise build 10240 onto a small number of PCs at my place of work, none of these PCs have been joined to a domain.  I've changed no settings that could delay an update, and despite small updates occurring, the major update to 10586 isn't happening.  I'm aware of the various pre-conditions that exist to prevent the update occurring, but none of these apply to the PCs (all built from a clean installation).

    How do Windows 10 Enterprise PCs get major updates if they're never going to be joined to a domain?

    Thursday, December 10, 2015 5:12 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    It appears that standalone enterprise builds can pick up the 1511 update after all.  Provided your PC was activated with a MAK code, and you haven't joined the PC to a domain AND added it to an OU that applies policies that would use WSUS.  All you need to do was wait one calendar month from the original update release date.  In other words, the update became available on December 15.

    I don't know if that's how it will always work for major update releases, in the sense that Microsoft makes enterprise builds defer by one month, or whether there was a change of heart at Microsoft.  The next major update (whenever that may be) will reveal all.

    Wednesday, January 6, 2016 7:55 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Can I ask are you using the Long Term Service Branch release of Windows 10? No November update for that afaik.
    Thursday, December 10, 2015 7:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Are you servicing these machine via windowsupdate.com, or via WSUS ?

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, December 10, 2015 8:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    If you don't have a WSUS server, you can upgrade directly with the updated ISO file. Because you have an enterprise edition I believe you have an access to MSDN/VLSC. As of today Windows 10 Enterprise 1511 is not available in Windows Update because corporates don't use Windows Update but rather WSUS or tools like SCCM/MDT to update PC.

    regards,

    signatureforums

    • Proposed as answer by Deason Wu Wednesday, January 6, 2016 1:24 AM
    Thursday, December 10, 2015 9:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    These machines should only get their updates from WIndows Update, they'll never have access to WSUS.

    The 1511 ISO file is available, but it appears to be the USA release (I'm in the UK).  I tried updating via the new ISO, but it insists that that the OS is different (which it is as far as country locale is  concerned) so their is no way to update and keep all installed apps.  You might as well just start all over again from scratch.

    I can't seem to find a way around this, unless I can get hold of the UK ISO for 1511, it's not available as yet.  Frustrating!

    Friday, December 11, 2015 7:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    when I check my VLSC, I can't see a UK ISO either, but I do see [32bit English 2725MB] and [32bit English International 2740MB].

    Can't help wonder what these are (e.g. if MSFT have changed the labels to some new cryptic title?)

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, December 11, 2015 8:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It appears that standalone enterprise builds can pick up the 1511 update after all.  Provided your PC was activated with a MAK code, and you haven't joined the PC to a domain AND added it to an OU that applies policies that would use WSUS.  All you need to do was wait one calendar month from the original update release date.  In other words, the update became available on December 15.

    I don't know if that's how it will always work for major update releases, in the sense that Microsoft makes enterprise builds defer by one month, or whether there was a change of heart at Microsoft.  The next major update (whenever that may be) will reveal all.

    Wednesday, January 6, 2016 7:55 AM