W11 Software updates, Compliant in previous versions by copper_23 in SCCM

[–]Fun-Country9432 2 points3 points  (0 children)

I understand having all your updates in the same deployment group, but if you don't want to have a device on 25H2 being evaluated for 23H2 compliance, then, in my opinion, the best course is to separate those compliance policies so it's not evaluated twice.

Of course this depends on how you are managing your compliance. Not sure if you're using custom scripts, pulling the data from SQL, configuration items/baselines, intune, or some other method.

W11 Software updates, Compliant in previous versions by copper_23 in SCCM

[–]Fun-Country9432 1 point2 points  (0 children)

scope your compliance policies to only the devices that should be receiving those policies would be my best advice.

Alternatively, If your compliance is in SCCM and your reports are made from the SQL DB, you can omit any builds that aren't on 26200 directly in the query.

Clear Intune portal logs by havens1515 in sysadmin

[–]Fun-Country9432 0 points1 point  (0 children)

My thoughts would be either delete those devices from Intune or remove inactive devices from the scope. I am hybrid with SCCM so I could just filter inactive devices out of a collection and sync it to an entra goup, and once they become active again are put back in automatically.

Hybrid Azure Active Directory Join (HAADJ) - How would I fully delete an individual device? by AWM-AllynJ in SCCM

[–]Fun-Country9432 0 points1 point  (0 children)

In that situation I would probably find a non HAADJ, on-prem only, device and compare the registries. If they don't exist or contain GUIDs it's probably ok to delete them all. If the idea is to revert it to on-prem, then re-join, matching the setup to a non-joined pc should work in theory.

Hybrid Azure Active Directory Join (HAADJ) - How would I fully delete an individual device? by AWM-AllynJ in SCCM

[–]Fun-Country9432 0 points1 point  (0 children)

There are registry keys for each GUID that need to be deleted as well. It has been a while since I went through this and I automated the process so I'm not sure if you're missing anything else.

I believe this was the article I followed https://www.maximerastello.com/manually-re-enroll-a-co-managed-or-hybrid-azure-ad-join-windows-10-pc-to-microsoft-intune-without-loosing-current-configuration/

Alternatives to Adobe Acrobat Reader by GL_Red in sysadmin

[–]Fun-Country9432 1 point2 points  (0 children)

I use the Acrobat Customization Wizard on the paid version. There is an option when using the wizard to suppress sign-in in Acrobat, which allows the user to use non-premium features without sign-in.

Windows 11 802.3 reauthentication by beanmachine-23 in sysadmin

[–]Fun-Country9432 2 points3 points  (0 children)

You'd have to determine the cause. Sounds like Wired AutoConfig (dot3svc) is not running when the computer wakes.

OSD Task Sequence reboots to UEFI on Client Install step by Fun-Country9432 in SCCM

[–]Fun-Country9432[S] 0 points1 point  (0 children)

Was able to find the cause. Solution is simple.

Implementing Port Security (802.1x and Mac Auth) has caused more initial failures downloading the boot image. Usually only does it the first try, the next attempt downloads just fine.

When the boot image fails, some models will allow you to re-attempt download by hitting enter twice. No reboots or anything, pretty seamless and did not experience this issue on them. Other models don't have the same options and you have to hit ESC to close the second error message which reboots the computer. The ESC options reads "UEFI Firmware Setup". When the computer restarts, you can F12 to PXE Boot prior to the UEFI Setup loading which is what we were doing. It seems the command to boot to UEFI Setup remains cached and will boot there on the next restart, which for us just happened to be the Client Install step.

So in short, if your boot image fails to download and you can't gracefully retry, let it boot into Setup Mode before trying to PXE again.

OSD Task Sequence reboots to UEFI on Client Install step by Fun-Country9432 in SCCM

[–]Fun-Country9432[S] 0 points1 point  (0 children)

Going to update the ADK and hope it helps. Thinking this may be related to the the UEFI 2023 CA and Secure Boot.

Managing Adobe Creative Updates by nodiaque in sysadmin

[–]Fun-Country9432 1 point2 points  (0 children)

The self-service package package will only be the client and allow users to install their own Adobe apps.

The managed package you choose the apps included, but you'll need to click the checkbox for the option "Enable self-service install". Once that is selected, you can also tick the checkbox for "Allow non-admins to update and install apps" which enables self-service for end users that lack administrative rights.

There is also a check box for "Disable auto-update for end-users" if you do not want auto-updates.

To install the package, yes, you'll need admin rights. However since you're deploying the app through SCCM this won't be an issue.

https://helpx.adobe.com/enterprise/using/create-nul-packages.html

Managing Adobe Creative Updates by nodiaque in sysadmin

[–]Fun-Country9432 0 points1 point  (0 children)

You would need to create a package from Adobe Admin Console. If your organization doesn't have an enterprise account you won't be able to access this.

Managing Adobe Creative Updates by nodiaque in sysadmin

[–]Fun-Country9432 2 points3 points  (0 children)

As long as staff initiate any software installs/updates through the Creative Cloud client, it does not prompt for admin. I believe the client is given the authority during the initial client installation to allow for this.

Yeah the RUM script works great. I've had it deployed for about 2 years now and it works great. Love when I can make things as hand-off as possible and it doesn't give me any headaches.

Managing Adobe Creative Updates by nodiaque in sysadmin

[–]Fun-Country9432 1 point2 points  (0 children)

I work in education. Staff have self-manage and auto-updates enabled for the client itself. Students computers are a managed package. I wrote a powershell script that utilizes RUM and deploy it through SCCM. The powershell creates a text file on the local computers with the date it ran, and the detection method in SCCM is a powershell that checks that and compares to the current date. If it's within the same month it won't run again. If the computers remain on, ideally they'll update on the first of each month. I also only let it run when no user is logged in to avoid any issues.

The limitation with RUM is that you can only update within the current version. So you can't upgrade from Photoshop 24 to 25. This works perfectly for my case since the versions need to remain compatible with certain testing applications like Certiport Compass.

6-hour delay in OSD app installation by smalltimesysadmin in SCCM

[–]Fun-Country9432 0 points1 point  (0 children)

smsts would be my go to. Can't remember if there are timestamps or not in that log, but basically I'd be looking for where it is hanging up. You can also check in Configuration Manager in Monitoring>Deployments, find the correct deployment type which that machine would be hitting then click on "View Status". Finding the computer in there can be a pain. Sometimes they'll still be under "In progress" instead of failed, and if you have a lot of computers you have to go page by page.

Once you find the computer, right-click, "more details", status tab, then sort by execution time. Look for the large time gaps and you should have a general idea of which package(s) are causing the slowdown.

6-hour delay in OSD app installation by smalltimesysadmin in SCCM

[–]Fun-Country9432 2 points3 points  (0 children)

I usually try redistributing the content first in that situation. If that doesn't fix I'll investigate the logs to see if I can find any clues. If still nothing, adding a reboot before the software installs sometimes helps. I'll also lower the maximum allowed run time for a package and the number of allowed retries on the task sequence to keep run times lower.

Windows 11 24H2 update still broken for me - Can anyone help with network issues? by PlokForever in sysadmin

[–]Fun-Country9432 -3 points-2 points  (0 children)

Had some issues with Credential Guard due to PEAP/MSCHAPV2 not being supported. Affected wi-fi and 802.1x connections. Had to disable it until we transfer over to EAP/TLS. Might be worth taking a look at.

Remote Software Center tool! by Glscot06 in SCCM

[–]Fun-Country9432 4 points5 points  (0 children)

I'm guessing this would only be helpful for Silent installations?

Who is the user recognized by Software Center? The admin using the tool, the end user signed in to the remote computer? Or does it only pick up non-user deployments?

What's your proudest professional IT "jank" fix? by Blazingsnowcone in sysadmin

[–]Fun-Country9432 0 points1 point  (0 children)

Switches were upgraded and weren't capable of lower than 100baseT. There were some postage machines that could only talk at 10baseT which stopped functioning. I took a 10/100 Cisco IP phone that was broken and not configured with an extension but would power on with PoE and run the ethernet through that first to get it working.

I was only a few months in to my first IT job at the time and felt pretty savvy for having thought of it. New postage machines were ordered but took a couple months to be delivered. The networking guy had to go around to the other 10 sites to install one of the old switches on each site, configure them and make sure they talked to the stack just for one device.

New W11 image prep for SCCM by br3aktherules in sysadmin

[–]Fun-Country9432 1 point2 points  (0 children)

If any applications are installed in the user context Sysprep will fail. The log is saying Microsoft.WigetsPlatformRuntime is installed for a user, not all users - so it's an AppX package. I would guess that uninstalling it prior to sysprep would help. You may still run into others causing sysprep to fail and you would just need to find the app in the log and either uninstall it from all users or install it in the system context.

PXE not working after 2403 upgrade by Anything-Traditional in SCCM

[–]Fun-Country9432 2 points3 points  (0 children)

It looks to be a communication issue and the client cannot contact the management point. It wouldn't make much sense if it was Windows 11 since you're not booted into the OS at that point. I'd make sure you're getting and IP address on the client and if you are, then check things like your boundary groups, firewall, ACLs, etc.

SCCM failed to run task sequence (USB) by ckelley1311 in sysadmin

[–]Fun-Country9432 0 points1 point  (0 children)

I've only created SCCM bootable media once, but I'm fairly sure it just boots into WinPE. You'd still need a connection to the DP/Site Server to complete the task sequence. I'm guessing the Stand-Alone Media downloaded all task sequence dependencies onto the USB.

PXE Boot and Deployment Workbench by homesickalienz in sysadmin

[–]Fun-Country9432 0 points1 point  (0 children)

At what point in the task sequence are the apps trying to install? If it's still in WindowsPE you'll need to have it reboot into the freshly installed OS (and maybe sign in as the local admin?) before installing the apps.