So this is applicable to BMC Client Management 12.0 151124p (Windows 10 Support) and up, correct?
Yes. This impacts all versions of BCM.
Serena Lambiase ha scritto:
3. Move the update.bin file from data\Vision64database\pmupdates\current to data\Vision64database\pmupdates\pending
Hi Serena, move the update.bin file...where? Or can we simply delete it?
This will force the master to reprocess the patch KB.
Just to make this clear: Oracle is not impacted as it manages ints in a different way.
I should buy a new pair of glasses...
Hi Serena Lambiase,
Could it be that after applying this workaround the build upgrade of windows 10 (1607 or 1703) will not be shown as missing service pack and by this the patch deployment won't be able to deploy it?
Installed Service Packs:
Missing Service Packs:
Patch history before the workaround was in place - so service pack 1703 was identified as missing:
I am not sure if this is affected by the workaround or by the latest shavlik kb.
It looks like that as soon as an Windows 10 Enterprise device get's the latest KB and update it's patch inventory of the "missing service packs" will not contain the build upgrade as missing.
Screenshot of missing service packs from a device which has an "out of date" patch kb:
Windows 10 Enterprise 1511 x64 with up-to-date patch inventory:
For Windows 10 Professional it looks like it should be:
patch inventory before applying the workaround:
Have you tried downloading this SP 1703 yet? With this fix and latest KB applied I show the need to install SP 1703 but unable to download SP. Here is the log from the Master:
2017/04/18 08:23:32 PatchManagementPremium I  Request for downloading ToBeAsked patch: 1703 for product: Windows 10 Pro (x64) with language: 0409
2017/04/18 08:23:55 PatchManagementPremium I  Patch information is missing, checking knowledge base
2017/04/18 08:30:48 PatchManagementPremium I  Patch download will start (https://www.microsoft.com/)
2017/04/18 08:30:48 PatchManagementPremium W  Patch download did fail, bad URL (https://www.microsoft.com/)
Notice the KB has this pointing to a bad URL. I was wondering if GERMAN language works?
I guess you need to take the same steps as for 1607. So downloading the ISO file with the Windows media creation tool, rename it and put it into your configured local patch source on the patch manager.
When it's about Enterprise (or volume licensing) you need to manually download the latest ISO from the volume licensing portal instead of using the creation tool.
I'll give it a try with the windows 10 pro 1703 upgrade and let you know. Should need around 15-30 minutes.
2 of 2 people found this helpful
So the implementation of 1703 works the same as the last time. The patch KB only contains microsoft.com as URL and you'll have to use the local repository. I did not try the deployment cause the only test devices I've available have Windows 10 Enterprise...
At your patch manager add "Path for Local Patch Repository", download the ISO file manually (windows creation tool kit). Rename the ISO file to the correct name. I guess you are using US - English so the correct name should be: Windows10x64Professional1703.iso and place the ISO file in the "Local Patch Repository folder". After this is done just let BCM re-download the 1703 service pack.
Hope this helps.
EDIT: If you're not sure about the file name which the iso file needs to have you could open the SQL management studio and run the following query:
SELECT PatchName, ProductName, PatchKey
where ProductName like '%windows 10 P%'
order by PatchName
The line will be created in the DB after you're first failed download. The "PatchKey" is the name which is ISO file should have. Be aware that you also have to adjust the query above to you database name (e.g. [bcmdb].[bcmdbuser].[PatchLanguages])
Thanks kind sir... I totally spaced out about the manual process required for the Win 10 SP upgrades. As always much appreciated!