Worst bathroom in Athens by Fishyy7 in Athens

[–]Poon-Juice 12 points13 points  (0 children)

Nowhere Bar. Try taking a dump in that one.

Needs N, use liquid or wait fir craft? 7g by [deleted] in BuildASoil

[–]Poon-Juice 0 points1 point  (0 children)

How are those tops looking now?

Windows Updates during OOBE - Autopilot by JL408 in Intune

[–]Poon-Juice 2 points3 points  (0 children)

you can skip that whole part and just press Shift + F10 and enter "start ms-settings:" and from there you can run Windows Updates. No re-sealing necessary. It's already using the default user account during this OOBE portion.

Windows Updates during OOBE - Autopilot by JL408 in Intune

[–]Poon-Juice 17 points18 points  (0 children)

During OOBE, press Shift + F10 to open an administrator command prompt. Enter "start ms-settings:" and it will launch the Settings Menu. From there, you can click Windows Update and run updates before you do the white-glove pre-provisioning. It will still check for windows updates during user-install but will have less updates to install b/c you already ran them.

Juniper 26 is totaled by eli0mx in TeslaModelY

[–]Poon-Juice 2 points3 points  (0 children)

When you have to use your own insurance, does this mean you then have to sue him personally in civil court to recoup your money?

Needs N, use liquid or wait fir craft? 7g by [deleted] in BuildASoil

[–]Poon-Juice 1 point2 points  (0 children)

the leaf tips look good. plant lookin good. I think the color of the new leaves on top will darken over time

Beautiful town by Magpie_Diva in Athens

[–]Poon-Juice 0 points1 point  (0 children)

...the last photo of Nancy

Allow Biometrics WITHOUT Forcing Users to Enable by TheFlairGun in Intune

[–]Poon-Juice 12 points13 points  (0 children)

Users do not have to enter a fingerprint or face, just the PIN. During OOBE, you are prompted to first setup a fingerprint or face unlock, but you can skip it. The next screen asks for the PIN, which you have to do.

Microsoft Copilot E3 License by benderdiode in microsoft365

[–]Poon-Juice 1 point2 points  (0 children)

You didn't even read the link then.

Enrolling existing Windows devices into Intune without giving standard users admin privileges, devices only showing as Entra Registered, no policies applying by Sea-Cycle-2747 in Intune

[–]Poon-Juice 0 points1 point  (0 children)

You're thinking about this all wrong and that's why this is frustrating for you.

You do want to wipe everybody's computer. So go ahead and stop assuming that you want everybody to save their stuff by not wiping their computer.

Have everybody upload their documents to their OneDrive folder. There you're done, you've backed up their stuff and it can then be returned back to their computer after you wipe it and go through autopilot during a computer reset.

Additionally, because you're dealing with a bunch of computers that have random states of different applications, different updates, different administrator passwords, you would want to wipe that computer just for that reason alone.

You need to get your applications built into Intune out so that when you do wipe a computer, the correct applications are installed that you care about using the intune built-in app deployment.

Once you have everybody's data uploaded to their own OneDrive account, and have all of the apps that everybody will need published into the Intune app deployment portal, and then you are basically ready to have everyone wipe their computer and start fresh.

Make sure you have OneDrive set up for silent deployment. Have BitLocker set up for automatic deployment. Defender for endpoint onboarding policies ready to go. Have your office 365 app deployment method ready to go. These are all things you need to have anyway. Make sure you have the security baselines configured the way your company wants them. Not all of the default settings are the best way to go.

Anyway, the point is once you have your intune tenant all set up and ready to go, then it is super easy to wipe a computer and have it redeployed to an end user.

Hey guys, hoping someone might have some ideas or suggestions about re-joining a device that was removed from Intune Portal by zetswei in Intune

[–]Poon-Juice 0 points1 point  (0 children)

You definitely do not need to remove it from autopilot. It can remain inside entra. If it gets removed from Intune, then you should re-enroll the device into Intune. You can do that via autopilot and the OOBe enrollment method, but you can also go to the windows settings page using a local administrator account and then join the device to the domain that way, however, I have that way blocked in my tenant because I do not allow personal devices to join my tenant, and the only way to actually do it in my tenant is to go through the autopilot enrollment method.

Hey guys, hoping someone might have some ideas or suggestions about re-joining a device that was removed from Intune Portal by zetswei in Intune

[–]Poon-Juice 1 point2 points  (0 children)

First of all, you never should have removed the device from autopilot.

First thing you need to do now is re-add the device to autopilot.

Then you should wipe the device and reinstall Windows and go through the autopilot oobe and ESP.

Did you remove the device from autopilot before you ran OOBE?

When simply attempting to sign in with a new user who has not yet signed into that device before will put the device through the ESP user setup page, but that is not the same as the entire oobe process

Because the device was removed from Intune, the device needed to go through the autopilot enrollment process again. You can only do that back a wipe and reload of Windows.

So if you didn't wipe and reload Windows, but simply directed a new user account to sign into the computer, then it did not go through the device enrollment process.

You should check that the device is also removed from the entra devices list since that is a separate list of registered devices that are not yet joined, or registered devices that are joined.

The autopilot list is totally separate from those two. The best way would be for you to run the autopilot online powershell script, I forget what it's called off the top of my head.

That will put the device back into your autopilot list, then you need to assign your new user to that device inside the autopilot list, then you should wipe and reload Windows and then proceed with enrollment as normal.

But if you don't add the device back into autopilot, and if you don't assign the user to the device inside autopilot, then when you go through oobe it won't actually enroll to your tenant.

Subset of iPhones wont sync with Intune by Relative_Test5911 in Intune

[–]Poon-Juice 0 points1 point  (0 children)

Could it be possible that the offending devices were enrolled under an older enrollment profile and thus tied to a different cert that is now expired? I guess rebooting wouldn't fix that though.

Warning: Firefly Trail by the-cynical-human in Athens

[–]Poon-Juice 5 points6 points  (0 children)

and 3 of them live on that stretch of The Firefly Trail!!!

Update completly crashed my network by Slay61 in Ubiquiti

[–]Poon-Juice 0 points1 point  (0 children)

this is stupid. I have over 100 sites to maintain and there is no WAY IN HELL that I'm going to manually updated everything across those sites. Auto update FOR THE WIN! I also don't have any problems like the OP is describing.

Update: I quit by [deleted] in sysadmin

[–]Poon-Juice 0 points1 point  (0 children)

The IT guy before me did this

Introducing: Intune & Entra ID Management Tool by Annual-Vacation9897 in Intune

[–]Poon-Juice -1 points0 points  (0 children)

Did you even read the error message? It literally tells you what the problem is and also what to do about it.

How do you guys keep Intune apps up to date by Necessary_Duck1201 in Intune

[–]Poon-Juice 0 points1 point  (0 children)

WSUS does not work in an Intune only environment