Hi all, does this issue affect Windows 10 upgrading process?
A customer is upgrading version 1703 to 1709, but keeps failing (have tried on 2 different machines, both failing), the client version is 9.5.6 .
Does it mean the customer has to upgrade client to 9.5.7.94 before they can upgrade Windows 10 to version 1709 from 1703?
Exactly. You have to upgrade the client version prior to the Windows 10 1709 upgrade.
Is this true? That 1703 needs to be updated with BES Agent 9.5.7.94 to succesfully upgrade to 1709? I’ve been having a non-sensible nightmare with those upgrades as defined in my posts.
Yes. I’ve created my own Windows 10 1709 deploy task with a local repository and in the relevance it checks if the agent version is 9.5.7.94 and everything works fine.
I hope to test this today. I’m doing the same as you and I hope it works. That will be a big time sync off my hands (and I’ll owe you a Coke!). 
Plus you may take a look at your antiviurs version.
In my case I had problems in both attemps, using BigFix and using the Windows Update to upgrade to Fall Creators. After upgrading OfficeScan from version 11 to version 12, prior to the Fall Creators deploy, everything worked fine.
I thought that would be too easy. It didn’t work with having 9.5.7.94 installed prior to upgrading from 1703 to 1709. Recall that I’ve mentioned that running it manually using the same command line as used in the fixlet, works every time.
Try to test in a computer without any antivirus installed if you haven’t yet.
Has your fixlet been generated using software distribution or have you customized the BigFix fixlet 1100992?
What I did was to create a customized copy of the fixlet ID 1100992 with my own relevances and replace the prefetch block to fit the correct Windows version for us (Win10_1709_BrazilianPortuguese_x64.iso).
This has been working since then in local computers and domain computers.
My whole process is explained here.
But to answer your question, I used SWD. I did not try without AV installed because that is not realistic and won’t do my any good (I can’t very well uninstall/reinstall AV on 100’s of endpoints). Plus this works manually. Plus this worked with 1703. So something is going on. I’ll try more testing with the 9.5.7.94 agent (I only tried one).
The AV question is just because it was the main villain here in the update process. I manage 5000 endpoints and there’s really no point in uninstall AV, upgrade and reinstall AV. However, trying in just 2 endpoints with same specs and softwares but no AV everything went fine. Then I looked for information and saw that I would need to update my AV (in my case Trend OfficeScan) from version 11 to 12. I didn’t change anything in my fixlet, just updated the AV version and things ran smoothly regardless user preset I select.
That’s good information just the same and I understand the logic. Do you recall if you tried manual installs with AV 11 and what those results were? If it was AV, I would suspect it would fail even when doing it manually. If however, they were successful, as mine have been, then certainly AV is worth a closer look.
Manual seemed to work fine in the beginning, but shortly after the 1709 version installed it started to give blue screen after a few restarts.
I’ve posted here what is been working for me so far if you wanna take a look.
So I think it is safe to say that it isn’t AV in my case. And these facts are pretty substantial I think:
- Manually always works
- BigFix fails on 3rd reboot at 85%
What I have experienced so far from BigFix+Win10 is that, for some reason, BigFix isn’t able to implement a command in Windows 10 as you would do locally. I had exactly the same problem when tried to install some browsers certificates via BigFix in Windows 10. The same command line worked as a charm in Win7 computers but not in the Win10 ones. However, performing the exactly same command line locally it worked perfectly in both OS.
The 9.5.7.94 client creates an IBM BigFix Support Center icon on the the start menu which, if deleted, gets recreated when the BigFix client service is restarted. How can this be permanently deleted ?
Can any one suggest for Win10 fall creator update for 1709 build from BigFix console.
Is it from OSD in system lifecycle. ( in-place upgrade).
Thanks in Advance
@SysAdmin3,
I didn’t understand your request but if that’s what you’re asking I’m using the Windows 10 Multi-edition VL Version 1709 - Windows 10 (x64) (Portuguese Brazil) available fixlet, just replacing the prefetch block code area with the informations of the ISO that I uploaded to the BigFix server, as in a software distribution.
No, FCU means win10 fall creator update.
suppose we have win 10 1703 and want to upgrade to win10 1709 … that is Fall creator update.
That’s not happening. Need help. Many blogs says it’s getting fail and still solution did not come around.
If you have an existing system to upgrade, you can do that via fixlet from the “Patches for Windows” site.
Yes, results are mixed. Many people have had problems, but so far these seem to be Microsoft issues and not BigFix content issues (that I’ve been able to identify, anyway). Some of us, myself included, seem to have better results if we run tge upgrade only when there are no users logged on and reboot immediately after running the upgrade fixlet.
I haven’t checked into the methods on the OSD site, but if there are methods in OSD they would involve an OS Migration, where the machine is reimaged using a previously-captured, sysprepped image uploaded into the OSD Image Library. I upgraded from Win7 to Win10 using that method, but haven’t tried it for upgrading one build of Win10 to another.