-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Software
- Commercial PC Software
- SSM Deployment Architecture

Create an account on the HP Community to personalize your profile and ask a question
10-21-2018 12:21 PM
System Software Manager(SSM) deployment strategy.
I have used SSM successfully in a Win7Sp1 environment for a number of years with little to no problems. However, now our organization (like many) is struggling to keep up with the multitude of Win10 versions being produced. We current have builds 1703, 1709, 1803 and soon 1809 in the environment.
I have had a couple of SP's not install on the 1703 build stating "(The system doesn't meet the minimum requirement of this driver. (Return code=0x643)" and had to roll back to the previous update. I understand MS's solution to the issue is just flip the switch and roll up to the next build, ASAP. But that is just not a "real world" solution, at least not "my world", since I will be forced to support these builds until they are simply no longer supported.
My question to HP is this:
Is it necessary, recommended or "a best practice" to maintain a separate SSM share for each of these build versions and using SDM select build specific drivers for each of the shares?
Any insight would be appreciated. Many Thanks!