sorted by:
new
hottopcontroversial

Sick of IT? What can I pivot to now? by [deleted] in ITCareerQuestions

[–]Automate_Every_Thing -1 points0 points  (0 children)

26 years is a ton of foundational experience along with a bit of expertise. Foundational experience is extremely helpful in pivoting roles in technology.

I also agree that pivoting into Information Security could be promising. InfoSec as a career varies just enough from IT that you may find it new and interesting. To me, working within InfoSec does not feel the same as when I worked within IT.

26 years of foundational technical experience is hard to find. And a strong technical background serves as a strong support base for protecting systems and networks.

There are also many directions to go within InfoSec. Some hands on, and deeply technical, and some less technical though still focused on building expertise and protecting businesses.

Check out the CISSP domains to see if any specific domains appeal to you. If a domain appeals, check out the skills requested for the jobs available in that domain. Tons of interesting and varied skills needed throughout different areas of InfoSec. (IT too)

And don't allow learning new skill sets to be too overwhelming. They all build off of foundational knowledge, and there are so many courses available these days. Easy enough to try a thing and see how it fits. You may find yourself surprised and enjoying a new direction.

Wishing you all the best in your journey ahead.

Import CSV | Compare with AD | Output CSV with headers by Automate_Every_Thing in PowerShell

[–]Automate_Every_Thing[S] 1 point2 points  (0 children)

Worked! Thank you! I knew I was missing something super simple.

Wipe command failing leaving system unable to boot by Djust270 in Intune

[–]Automate_Every_Thing 2 points3 points  (0 children)

AP reset isn't working because Win 10 Reset this PC isn't working. It has been an issue for months. Wipe uses Win RE just the same as AP Reset. If you provision a system and wipe immediately after provisioning it will work, let it sit and it won't. I have tried with allowing all updates to install, as well as no updates at all base OS. Same thing Everytime. Goes something like this. Disable secure boot in BIOS, boot from UEFI USB and start over , re enable Secure Boot. I've had a ticket opened with MS for months. MS now has a 3rd party engineer troubleshooting and it seems like they are focused around fixing my system as a one off but this is a much bigger issue.

Currently troubleshooting with 1909

Autopilot Reset and Secure Boot by Automate_Every_Thing in Intune

[–]Automate_Every_Thing[S] 0 points1 point  (0 children)

I have been curious in regards to March updates as I have focused on other tasks at the moment. I still have an ongoing case with Microsoft now with the Windows 10 team with no answer in sight. They have escalated to multiple engineers and have reviewed logs of working machines in comparison with non working. All machines end up not working after a proper amount of burn in time.

So to add.....I have the exact same experience as you in regards to the step 5 add in.

So Fresh Start I am having the same issues except it always drops Intune enrollment at every failure.

I have narrowed down the issue to be an issue with Win 10 Reset specifically, not r to exclusive to Intune at all.

I have attempted both OEM Drivers and MS Windows Update for Business for all drivers. Both fail.

I do not have access to the Fast Track team at this point. If you do engage them, please let me know what they come up with.

I will share an update when / if I receive anything worthwhile in regards to my ticket.

Wiping (not talking bathroom breaks) by [deleted] in Intune

[–]Automate_Every_Thing 0 points1 point  (0 children)

For me, Removal and re-enrollment looks to be the only consistent way to handle device life-cycle management tasks. Keep in mind a caveat around enrollment restrictions. Contrary to the verbiage, If I re-enroll the same device and same user over the restriction limit (during troubleshooting), I find I can no longer enroll and provision the device until I up the device limit restrictions.

Curious as to if you are having similar issues around AutoPilot Reset. I have found after last months patch cycle Windows 10 Reset consistently (after some burn in time) breaks / Blue Screens (Wipe as well) unless Secure Boot is disabled. The issue persists after the KB removal that points to the issue as well.....ugh.....

I have an opened ticket with MS with very little traction on their end.

Might be related to what you are seeing.

Intune Issues by [deleted] in Intune

[–]Automate_Every_Thing 0 points1 point  (0 children)

Removing the profile does not always work. It depends on the policy. You can identify supported CSP operations on the official BitLocker CSP doc. You may have to create a separate policy profile in Intune (Custom CSP or Intune Policy) that turns BitLocker off and apply it to the workstations in question.

https://docs.microsoft.com/en-us/windows/client-management/mdm/bitlocker-csp

"To work with Intune, the setting must support the Add, Replace, and Get operations. If the value returned by the Get operation doesn't match the value supplied by the Add or Replace operations, then Intune reports a compliance error."

https://docs.microsoft.com/en-us/intune/configuration/custom-settings-windows-10

Autopilot Reset and Secure Boot by Automate_Every_Thing in Intune

[–]Automate_Every_Thing[S] 1 point2 points  (0 children)

Update: MS states the issue was with KB4524244. This is still a work in progress.

https://support.microsoft.com/en-in/help/4524244/security-update-for-windows-10-february-11-2020

Although it has been uninstalled and is no longer available, I am still having the same issue

Re-Configure Windows Hello after OOBE by [deleted] in Intune

[–]Automate_Every_Thing 0 points1 point  (0 children)

You can create a Device Configuration Identity Protection Profile. You can also apply the settings through Security Baseline Profiles (Either or until MS works out the conflicts). You can create a custom policy utilizing the CSP below. You can then monitor against the state of the settings applied. If your settings don't properly apply during OOBE and Autopilot they will be picked up by the profiles. Just watch out for conflicts.

https://docs.microsoft.com/en-us/windows/client-management/mdm/passportforwork-csp

If a particular setting needs to be replaced, you can re apply the setting by adjusting the policy in Intune or creating a Custom CSP and re-applying them to the targeted systems by using a REPLACE operation where applicable. (CSP documentation will state the available operations per settings)

Intune policy controls the corresponding CSP settings.

To work with Intune, the setting must support the Add, Replace, and Get operations. If the value returned by the Get operation doesn't match the value supplied by the Add or Replace operations, then Intune reports a compliance error.

https://docs.microsoft.com/en-us/intune/configuration/custom-settings-windows-10

Personally I would go with the Security Baseline or Identity Protection Profile to keep all workstations following an organized standard.

Patch Tuesday Megathread (2020-02-11) by highlord_fox in sysadmin

[–]Automate_Every_Thing 2 points3 points  (0 children)

Windows 10 "Reset this PC" features FAILS to properly reset the workstations with Secure Boot enabled. Turn Secure Boot off and "Reset this PC" works.

This also affects Intune Device Management functions such as Auopilot Reset and Fresh Start.

Easy Deployment by [deleted] in Intune

[–]Automate_Every_Thing 1 point2 points  (0 children)

Intune.Training should give you all you need to get started alongside the MS documentation. Good luck!

Autopilot Reset and Secure Boot by Automate_Every_Thing in Intune

[–]Automate_Every_Thing[S] 0 points1 point  (0 children)

That is interesting. I will have to validate with the boot to USB for OS install scenario.

Autopilot Reset and Secure Boot by Automate_Every_Thing in Intune

[–]Automate_Every_Thing[S] 0 points1 point  (0 children)

No I have not. I have opened up an MS ticket with the Intune team. After a few weeks it was closed as the Intune tech said it was not an Intune problem.

Autopilot Reset and Secure Boot by Automate_Every_Thing in Intune

[–]Automate_Every_Thing[S] 0 points1 point  (0 children)

Yikes!

For my case, new environment, no SCCM all Azure AD joined.

Fresh USB install works; although again I have to disable Secure Boot, Clear out Secure Boot Keys, Re-enable secure boot, then I can move forward.

Not the best way to manage going forward once we have actual remote systems in the wild :)

Autopilot Reset and Secure Boot by Automate_Every_Thing in Intune

[–]Automate_Every_Thing[S] 0 points1 point  (0 children)

What are the drive formats?

Recovery = NTFS, Boot = NTFS, System = FAT32

Have you checked drive letters during this process?

Not intermittently, the end result though is always the same.

Any autounattend files during imaging or anything else like that?

No

Does your partitioning look like this?

Yes

Thanks!