![]() So there are a few options available to you. As mentioned previously, because content is not stored on your Apple TV, this is not as big of a deal as. As such you Apple TV will return to factory settings once the Jailbreaking process finishes. I posted on another forum and another user also said that they resolved the issue by remoting onto devices and performing a 'reset this pc' from the device directly also worked. SeasonPass is a Jailbreaking tool that forces your Apple TV to be restored to a pre-Jailbroken IPSW that it creates. If we had access to more brand new devices, we could have worked out exactly which method appears to have solved the issue. run reagentc /enable (found an article that recommended doing it twice) So we turned that off.Ģ) We stopped using Wipe and only use Fresh Start now.ģ) We have a task sequence that applies to newly built devices that runs the following steps Ĥ. The problem is that we implemented a few changes at the same time.ġ) So firstly, MS advised us that if we are not using Secure Core Devices (which we aren't) then to disable Virtualisation Based Security (which we had on because we were using the Intune Baseline). All i know is that previously we had the issue on every new device and now we haven't had it on 5 devices. We only had 5 new laptops available to us, so I can 't tell you a) if the issue is entirely fixed or b) which method fixed it. I don't think this is an 'autopilot' issue per se, i believe that the issue would also occur if we attempted to do a systemreset on the device itself. We are running low on new devices and wanted to reach out and see if anyone else has come across and solved this issue as it really is a show stopper for us using AutoPilot. To recreate the recovery information and then the device reset successfully, but we can't be sure that it was the above that fixed it. We did have a single device that repeated the issue on reset. We are unable to reproduce the problem which is proving frustrating, it only occurs on brand new devices. There was mention in the above thread about disabling secureboot appeared to resolve the issue, but given there is no command-line / automated way to disable secureboot, we wouldn't want users messing about in the BIOS. We also found that the February 2020 Cumulative Update appeared to contain a fix which directly related to PBR (push button reset) and autopilot, but that patch was pulled and I can't find any subsequent patch that references it Security update for Windows 10, version 1607, 1703, 1709, 1803, 1809, 1903, 1909, Windows Server 2016, Windows Server 2019: Febru() ![]() I've seen a similar thread here on reddit, but no definitive solution Autopilot Reset and Secure Boot : Intune () The devices themselves are either 1909 or 2004. The only way to recover these devices is to use a Win10 USB to rebuild them (which obviously isn't suitable in a live environment). Ordinarily the wipe goes well, but we've noticed that on brand new devices, the first reset after a build results in a failed recovery screen (Blue screen - Your PC/Device needs to be repaired - Error Code 0xc000000f) and will not recover. When returning devices to OOBE, we use Intune Wipe as the other options (AutoPilot Reset / Fresh Start) aren't supported on Hybrid devices. We have a hybrid AutoPilot build which uses secureboot and bitlocker with pre-boot authentication. We are having an issue with our AutoPilot builds.
0 Comments
Leave a Reply. |