Windows 10 Upgrade

[drepouille]

Our ward computer received a couple MLS updates today. Windows 7 also displays a large pop-up window that tell us to keep the computer powered on for the Windows 10 download and upgrade. After church, just as we started to enter the donation batch, Tivoli wanted to reboot the computer. After I had transmitted the batch and backed up MLS, I allowed it to reboot. Still no Windows 10 yet, but I am sure it is coming.

[johnshaw]

Ooh, and you'll never guess what else I heard . . .

The update replaces Windows with a Linux installation, moves custom reports to Leader and Clerk Resources, updates the LDS.org Lesson Schedules tool, and allows members to report their home teaching via LDS Tools?

Not only that but attends the temple for you, actually DOES the Home Teaching, has PPI's with your kids but it still teaches Gospel Doctrine the same old way... Question, Can anyone define Repentance?... Which of Nephi's brothers didn't believe their father Lehi?

[kai4785]

I had a problem with users trying to upgrade to Windows 10 shortly after it was released last year. On one occasion, I simply uninstalled the KB, and set it to hidden. On another occasion, I updated the Registry to "disable" the upgrade. Two weeks ago, I reverted my registry changes, and re-enabled the upgrade software. The best part is that this Sunday, now that the icon is back, another user had whimsically scheduled a manual upgrade to happen later that night (having not received any of the formal church communications about the upgrade.) I cancelled the scheduled upgrade (though I let it complete the download).

So at this point, my computer has been on (with a big sticky note on the screen) waiting for the upgrade to happen for a little over two weeks now. I'm growing concerned that I may have taken some action that interrupted the automated upgrade process.

With some 10 years of IT experience, what I could really use is either:
* some more specific instructions about what the state of the Clerk's computer *should* be in order to "enable" the upgrade.
* some confirmation that 2 weeks isn't long enough to have waited. (I've been asked more than once why I'm not turning off the computer when I'm done.)

[Biggles]

I shouldn't worry. I have two computers in my Stake/Ward building that have been turned on for two weeks. Nothing has happened yet. W10 Upgrade FAQ #4, gives the answer that the rollout is being done in stages. We still have 3 weeks for it to happen.

https://www.lds.org/help/support/win10-upgrade?lang=eng

[sbradshaw]

Most computers nowadays are made to be left on for long periods of time; and when they're asleep, they don't use a lot of power – so leaving them on for a few weeks shouldn't cause any problems.

[drepouille]

My ward's computer had been set to sleep (suspend mode, not hibernate) after a few hours. This caused the DSL modem to disconnect overnight, so we always had to wake it up using a browser before we could Send/Receive with MLS. I changed the power settings to turn off the monitor after an hour, but never allow the computer to sleep. So far, that has kept the DSL modem online. I am hoping my actions will help the Windows 10 download to occur on schedule.
I fear that the other 11 computers in my stake may not download the update, but that is no longer my problem, since I was released from my stake callings last July!

[rick.winterton]

I'm the stake clerk and also the stake technology specialist in my stake. I have 12 unit administrative computers. In the last three days, 11 of them have been upgraded to Windows 10. After the first two days, three units (that did not receive the on-screen notice that Windows would be upgraded) had failed to upgrade. After discussing this with the help desk, I checked the Windows Defender and Windows Firewall services and shut them off. That enabled two of the three to upgrade. One still isn't upgrading, though I tried another suggestion that the help desk gave me (it doesn't seem to work so I'd best not say what it is).

One of the 11 computers that went through the upgrade process failed. It reboots continually every few seconds. I'll reinstall Windows 7 from the Church's image onto that computer next week and see what happens. The computer is still under warranty, so if there's a hardware problem, I'll have to make Dell fix it.

[pete.arnett]

Seven (7) MLS desktops upgraded to Window 10 with no issues
Still have several to go

[drepouille]

My ward's computer has been successfully upgraded to Windows 10 with no problems noted. MLS started fine. The printer drivers still work fine. All the accounts and passwords are unchanged.

[gizmotek]

This note has just been added to W10 Setup & Upgrade notes in the Help Centre.

'Notice: Please DO NOT attempt to manually upgrade your computer to Windows 10. If you do, you will break various applications and security measures currently used on the device. The Church-approved upgrade process will automatically switch your computer to Windows 10 within the next few weeks.'

https://www.lds.org/help/support/win10-upgrade?lang=eng

Ooops, just saw this after posting the above comment. But then again I`m not sure if that is only US based PC`s or is it worldwide?...

anyways, mls is running on all win10 pc's now and one was done back in march odd (becuase the clerk upgraded to win10 and then PF nor GSC had a win7 iso in spanish for us -parent language version- , so I left that spanish language win10 in place after getting mls to work with the restore to factory setting trick!) however I guess sophos isn´t really running at full capacity

Did you find a solution to this? I had a ward take it upon themselves to upgrade manually without waiting, and for the most part everything works except Sophos. I haven't called GSC about it yet, but seeing as the other computers in our stake are transitioning fine on the church update method, I may need to do some resetting on this machine.