none
Message ID 10027 - Client version 5.00.8913.1012 RRS feed

  • Question

  • Does anyone know why message ID 10027 does not appear in the all status messages with the new client version of 5.00.8913.1012 ?    Was this by design?

    Thanks in advanced.

    Wednesday, January 22, 2020 12:52 PM

All replies

  • Sorry, but I think you'll need to be far more specific with your question and your expectations for anyone to even begin to help here.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, January 22, 2020 1:09 PM
  • Every time a machine can online or when it was rebooted it would would show a message ID of 10027 in the all status messages - description would be "the cache size has been modified ... to ...."

    It seems now when the SCCM client is 5.00.8913.1012, the client must no longer send this type of message to the SCCM server.

    I hope this is enough details or specifics for you.   I really didn't know how to full explain this.   There is nothing in the release notes about any of this.

    Thanks for helping me out on this matter.

    Wednesday, January 22, 2020 1:31 PM
  • > It seems now when the SCCM client is 5.00.8913.1012, the client must no longer send this type of message to the SCCM server.

    Possibly. I doubt anyone has every truly cared about this message. It may be a functionality change in the product (as it really doesn't make sense for the client to reconfigure it's cache every time it starts if the cache size hasn't changed) or the result of some other change. Also, keep in mind that there are far, far too many changes with each release to be listed in the release notes so while the release notes are great, they aren't comprehensive. 

    If you need to know about this, then you'll probably have to open a support case with Microsoft.

    What exactly were you using this message for?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, January 22, 2020 1:41 PM
  • Since your a MVP do you get any more information about the new version that the average public gets.   

    I guess in our environment, we did use this message ID to tell if the SCCM service restarted or if the machine was actually rebooted.    As from time to time, SCCM clients for some reason or another get stuck.   I will open a call with Microsoft 

    Wednesday, January 22, 2020 1:49 PM
  • Yes to your first question but that's also a loaded question as many of things we are privy to are subject to our individual NDAs. Also, the breadth and depth of possible info is staggering -- for reference, each ConfigMgr build contains on average 3,000 updates. Also, ConfigMgr 2007 has about 12 million lines of code (that was written 15 years ago so I wouldn't be surprised if there's at least 20 million lines currently).


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, January 22, 2020 3:09 PM