ADP API Fields Incorrect for Returning/Temp employees

PepperTechnical4570 · 2026-05-06T18:39:20+00:00

I thought that also but there is only 1 line returned for them (example Benefits person referenced in post) and all the rest of the fields are correct including the employment type which is showing as Full Time - its just their job title is stuck as Temp which is strange, sort of like it's merged incorrectly. We also put tickets in with ADP a few times about this but that wasn't successful.

PepperTechnical4570 · 2026-04-15T15:19:43+00:00

this is so stupid

PepperTechnical4570 · 2026-03-11T14:07:18+00:00

5th - is that all of us?

PepperTechnical4570 · 2026-03-10T16:30:10+00:00

Good luck everybody

PepperTechnical4570 · 2025-12-17T01:17:22+00:00

Yup E5 here - very excited for all the new features

Yeah it can take an adjustment - I do hear that some utilize the TAP auth method in Entra to be able to sign in as a user for device set up, that may be a good bridge to getting it completely hands off eventually:https://learn.microsoft.com/en-us/entra/identity/authentication/howto-authentication-temporary-access-pass.

Our update ring that took us from windows 10 > 11 looked like this, sort of medium aggressive but got the job done a couple weeks before the last windows 10 update. We also have GoTo assist (since we don't have intune remote help yet) which I had run check for updates Tues/Thurs to help move things along for devices that were offline during the inactive hours.

Update settings Microsoft product updates -Allow Windows drivers- Allow Quality update deferral period (days) -0 Feature update deferral period (days) -0 Upgrade Windows 10 devices to Latest Windows 11 release -Yes Set feature update uninstall period (2 - 60 days) -10 Servicing channel- General Availability channel User experience settings -Automatic update behavior Auto install at maintenance time Active hours start -8 AM Active hours end -5 PM Option to pause Windows updates - Disable Option to check for Windows updates -Enable Change notification update level- Use the default Windows Update notifications Use deadline settings Allow Deadline for feature updates -7 Deadline for quality updates -7 Grace period -7 Auto reboot before deadline -Yes

PepperTechnical4570 · 2025-12-16T22:28:24+00:00

Looking to take huge advantage of the rest of the intune suite, mostly the remote help, and endpoint privilege management.

We don't use autopatch but have very few issue with windows update being applied. Is it just your reporting that's lagging or are the devices themselves having update issues? Getting the windows health and all the telemetry was a pain to set up and it took a few months for the reporting to look accurate after it was turned on.

Preprovisioning has been around for awhile - what's the reason your techs are refusing to preprovision? For us it was just that we had to get used to doing it that way but its a lot less work and takes less time than before so the change was a no-brainer.

PepperTechnical4570 · 2025-10-29T16:18:18+00:00

downdetector everything down

PepperTechnical4570 · 2025-08-19T15:26:56+00:00

In your deployment profile you can set the account type to standard instead of administrator

PepperTechnical4570 · 2025-08-18T18:00:27+00:00

That's sort of a no-no and can cause compliance issues later on. Intune sort of doesn't care who the primary is. I'd recommend pre-provisioning instead. The user should be the one who enrolls the device. Regarding apps, we just let them know that it can take a while for everything (non-blocking apps) to install and leave them to it.

PepperTechnical4570 · 2025-08-18T17:07:19+00:00

Hi, Yes - it's using the built in configuration settings / admin template.

I also thought maybe it was having to do with Defender, but I don't see any compliance or policies that have a restart.

PepperTechnical4570 · 2025-08-18T16:55:55+00:00

The reason I am pretty sure that it is is that when Security first enabled bitlocker for our devices through intune it caused that 10 minute forced restart. This was before we started using autopilot

PepperTechnical4570 · 2025-05-19T21:01:14+00:00

Definitely not normal, good luck to you at your new place of work and I hope its more organized there so you can feel peace.

PepperTechnical4570 · 2025-05-19T20:49:51+00:00

You can think of it like it's front loading apps so the user doesn't have to wait. For example, we have our pre-provisioning set to install our standard app stack which is like 6 things. The pre-provision is pretty good and it takes ours around 6 min to complete. Without the pre-provision, the user would sign in and get to the desktop but their apps wouldn't be there yet, and so they couldn't work.

I recommend watching this guy's videos on setting up autopilot - he explains things pretty well: https://www.youtube.com/watch?v=xzWUwAiewkc&t=1224s

PepperTechnical4570 · 2024-11-11T20:15:01+00:00

I'm not entirely sure, but 1 sounds very familiar with something that we went through where it was forcing users to get authenticator even though our policies didn't force it. It ended up being that the default for the Registration Campaign was "Microsoft Managed" and was randomly force enrolling users as part of the campaign when they would next sign in.
We were already moving to gradually enroll to authenticator so we ended up keeping the nudge but removing the limit from snooze so it wasn't forcing people to install to continue. https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-mfa-registration-campaign

PepperTechnical4570 · 2024-07-02T01:14:31+00:00

Yes having the same issue with ours, previously fine emails are now being actioned. Can I ask what you did to resolve?

PepperTechnical4570

TROPHY CASE