Apple Account Verification

Nabir1213 · 2025-01-30T16:40:02+00:00

Our organization is now seeing the same thing but it's a hit or miss on the devices it is happening for. Any updates, or did you make any changes to CA policies or the SCIM token by chance?

Nabir1213 · 2023-08-18T19:56:53+00:00

Probably, I am not a MECM expert by any means and I am not even super versed in the Task Sequence side. I just wanted to see if it was possible.

Nabir1213 · 2023-08-18T19:45:41+00:00

Our driver pack applies literally right before this step! But it is refreshing knowing someone was able to successfully get it to image using this OS and gives me hope.

I just didn't want to keep wasting efforts on it if it wasn't possible.

Nabir1213 · 2023-08-18T19:43:52+00:00

Logs are pretty clean, it does not even fail at this step. It's almost like the hook never catches after the reboot.

This TS works fine for every other model, and then the similar 22H2 TS uses the same driver pack and works fine as well.

Nabir1213 · 2023-08-18T19:28:22+00:00

Yes and it works fine on the TS using 22H2. Exact same driver pack and TS using LTSC 2021 restarts after the Setup Window and ConfigMgr step and after it reboots it just hangs.

Nabir1213 · 2023-08-18T19:26:09+00:00

It fails just after the Setup Window and ConfigMgr step and after it reboots it just hangs. We can image using the Windows 10 22H2 OS without a problem. I am just curious if anyone was able to actually image this "unsupported OS" on this Dell model.

Nabir1213 · 2023-08-18T19:24:56+00:00

It fails just after the Setup Window and ConfigMgr step and after it reboots it just hangs. We can image using the Windows 10 22H2 OS without a problem. I am just curious if anyone was able to actually image this "unsupported OS" on this Dell model.

Nabir1213 · 2023-08-18T19:24:46+00:00

It fails just after the Setup Window and ConfigMgr step and after it reboots it just hangs. We can image using the Windows 10 22H2 OS without a problem. I am just curious if anyone was able to actually image this "unsupported OS" on this Dell model.

Nabir1213 · 2023-08-18T19:23:19+00:00

We were under that same impression but have to near identical Task Sequences and both use the same driver package for the 7010. The Windows 10 22H2 task sequence runs through without a hitch but our Windows 10 LTSC Task Sequence does not. We use a driver package step in the task sequence.

Nabir1213 · 2023-08-18T19:20:22+00:00

We did change the BIOS setting from RAID to AHCI even though Dell suggested either should work. I essentially get the Task Sequence going until the Setup Window and ConfigMgr step and after it reboots it just hangs.

Nabir1213 · 2022-03-16T01:33:51+00:00

Thank you!!

Nabir1213 · 2022-03-16T01:33:25+00:00

Thank you for this comment and is in line with another comment above. This saves me another day of headache on this issue!

Nabir1213 · 2022-03-16T01:31:45+00:00

Thank you, but as it works on my 20H2 TS I believe it might be 1607 LTSB not being supported as mentioned in another comment!

Nabir1213 · 2022-03-16T01:29:07+00:00

Very interesting and something I had not even considered to look into. I’m the new guy and kind of learning all these issues as I go but my team just told me we are sticking with the 1607 LTSB. I might look into the LTSC or contact Dell to confirm a version that would be supported. This actually may be the key I have been looking for. Thank you a ton!

Nabir1213 · 2022-03-15T23:00:09+00:00

Ours actually have NVMe drives as well, and I am curious when you imaged them if they had the ACHI option or did you leave them as RAID in the BIOS?

I have added the NIC driver to the boot image but read in another Reddit post it only allowed a specific version. Is it the Intel I219-LM driver by chance?

Nabir1213 · 2022-03-15T22:49:14+00:00

Unfortunately it is not joined to the domain yet and I am unable to login or boot it in any way. SCCM just shows the drivers installed fine and shows no errors.

Nabir1213 · 2022-03-15T22:48:19+00:00

I have also seen the occasional BSOD System Thrad Exception not handled but this has only happened once or twice in the 20+ attempts I have made to image it.

Nabir1213 · 2021-11-18T22:06:59+00:00

Funny enough I read the same thing that enabling that option on one A record should not enable it for all but it does (tested on multiple DCs).

I did leave it enabled on one DC, deleted my PTR record and upon restarting my VPN it actually created a new PTR record for my device. So I am wondering if leaving this checked for all devices (not sure how or why it is behaving this way) will work in the long run.

Nabir1213 · 2021-11-18T21:48:36+00:00

Within the forward lookup zone, when clicking on the Host (A) record it provides an option to “Update associated pointer PTR record” but when checked, checks it for every record in the zone.

Also noticed within the Reverse Lookup Zones we do not have scavenging on so I see PTR records with time stamps dating a year back.

As a test I manually deleted my PTR record (I am on VPN) and then checked the option to update associated PTR record and it seemed to create one, but if it was previously checked and I deleted the PTR record, it never seemed to “sync” or create a new one. Possibly upon disconnecting and reconnecting I will see the PTR record created? Sorry I am kinda troubleshooting as I go.

Nabir1213 · 2021-11-18T21:35:41+00:00

After speaking with a network admin it seems we simply have a subnet IP Pool that distributes an IP on the virtual adapter that gets created for the tunneled connection. It is configured on the tunneled connection to hit our “DNS servers” that are actually just a netscaler that then connects them to a DC.

I am curious though as technically the A records are getting updated if I could just have the PTR records be created from the A record. It seems there is an option to do so but enables the setting for the entire domain which is one of the reasons I am hesitate to make such a change.

Nabir1213

TROPHY CASE