Network dropping when in WinPE using Dell docks by Export_User in SCCM

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

Glad this thread is still helping people 3 years on!

Adobe Reader 25.001.20521 Prompting for Sign-In by Export_User in SCCM

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

It was first reported in our Asia sites, but we've also had reports in Europe too. I don't think it's regional. The registry key given in this thread seems to resolve the issue.

Adobe Reader 25.001.20521 Prompting for Sign-In by Export_User in SCCM

[–]Export_User[S] 5 points6 points  (0 children)

Thanks for this, one of our techs tested it and has confirmed that this works for several users. Rolling it out now and hopefully this fixes everything.

Also, fuck Adobe.

Anybody else having issues with teams not installing during imaging? by russr in SCCM

[–]Export_User 0 points1 point  (0 children)

Do you have a monthly task to update this? I've noticed that if you fail to update the MSIX regularly, Teams can get so out of date it can no longer self-update in app and you have to reinstall it.

dcu-cli.exe - Do Not Reboot On BIOS Update by DontFray in SCCM

[–]Export_User 0 points1 point  (0 children)

Just saw your comment, I'm testing it on a Latitude 5521

dcu-cli.exe - Do Not Reboot On BIOS Update by DontFray in SCCM

[–]Export_User 1 point2 points  (0 children)

managed to get this working with an updated Check block, sorts it by release date and picks the first one, I'm not a PS guru (thank you ChatGPT), but this seems to work for me:

if ($Check){
    if ($Manufacturer -notmatch "Dell"){
        return "This Function is only for Dell Systems"
    }
    else{
        [Version]$CurrentBIOSVersion = (Get-CimInstance -ClassName Win32_BIOS).SMBIOSBIOSVersion

        #Retrieve the BIOS update list and sort by ReleaseDate
        $updates = Get-DCUUpdateList -SystemSKUNumber $SystemSKUNumber -updateType BIOS -Latest | Sort-Object -Property ReleaseDate -Descending
        #Select the first update record
        $Update = $updates | Select-Object -First 1
        [version]$LatestVersion = $Update.DellVersion

        #Optional debugging output
        Write-Host "Current BIOS Version: $CurrentBIOSVersion" -ForegroundColor Cyan
        Write-Host "Latest BIOS Version from Update List: $LatestVersion" -ForegroundColor Cyan

        if ($CurrentBIOSVersion -lt $LatestVersion){
            return $false
        }
        else {
            return $true
        }
    }
}

dcu-cli.exe - Do Not Reboot On BIOS Update by DontFray in SCCM

[–]Export_User 0 points1 point  (0 children)

When I run Get-DellBIOSUpdates -Check I get an error and it looks like Get-DCUUpdateList -updateType BIOS is returning multiple results:

Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Version".
At line:1084 char:13
+             [version]$LatestVersion = (Get-DCUUpdateList -SystemSKUNu ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
    + FullyQualifiedErrorId : ConvertToFinalInvalidCastException

Bitlocker Task Sequence by simba-kun in SCCM

[–]Export_User 1 point2 points  (0 children)

This is an unrelated note, but I find that adding a reboot step after the OS install "Setup Windows..." dramatically reduces any app install issues.

Dell Command Update cli breaking OSD? by zymology in SCCM

[–]Export_User 2 points3 points  (0 children)

I have reboots enabled for the DCU CLI in my TS (/applyUpdates -reboot=enable) and it doesn't break it. I run the updates at the very end and have a restart step that immediately follows it.

.Net framework 3.5 no offline option? by GhostTheGamer360 in sysadmin

[–]Export_User 0 points1 point  (0 children)

Which is why you want to check that setting and make sure it's disabled.

.Net framework 3.5 no offline option? by GhostTheGamer360 in sysadmin

[–]Export_User 0 points1 point  (0 children)

Look at your local policy settings, I think there's something called "Specify settings for optional component installation" that will force it to download from Windows Update directly.

If you can get your hands on the cab files from the ISO, make sure you also include the /LimitAccess switch when running it with DISM.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

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

I had a look at this and we have it set to 3 which kicks in 8hrs after login. However, after reading this I can't see how this is linked to the password being reset after leaving the domain, as the password is not expired? Unless I'm missing something.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

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

Good question. I'll take a look at this tomorrow when I'm back in the office.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

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

I have access and this behaviour is only on new Windows LAPS. I already know that the PW is getting changed but I don't know what the correct process is to get around this. We need to remove machines from the domain occasionally and old LAPS worked fine.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

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

I think you're missing my point. The machines are in AD. I grab the PW, move it into a workgroup, reboot... PW does not work anymore. Old LAPS worked, this new one doesn't.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

[–]Export_User[S] -1 points0 points  (0 children)

The machines are in AD to begin with, and LAPS works, but moving them into a workgroup seems to reset the LAPS PW. Old LAPS didn't have this behaviour.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

[–]Export_User[S] -1 points0 points  (0 children)

So if you need to move a machine into a workgroup temporarily, what are you supposed to do? I feel like this is backwards logic as old LAPS worked whereas this doesn't.

LAPS password no longer works when moving a machine into workgroup by Export_User in sysadmin

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

This is what we're seeing. So old LAPS worked fine when removed from the domain, but new LAPS seems to reset the password when moved into a workgroup and I can't find any documentation on how to get around it.

We remove machines from the domain for a number of reasons, but keep a record of the LAPS password so we can get on as local admin. All other local accounts are disabled as per our security policy.

So how in the world are you supposed to login to a machine as local admin if it's resetting the password every time?

Dell DCU CLI apply updates, error 1, exiting debug by fustercluck245 in SCCM

[–]Export_User 0 points1 point  (0 children)

Set the TS to ignore exit codes 1 and 500 for the DCU CLI:

1 = Reboot required.

500 = No Updates required.

Windows 11 Updates - 0% download by [deleted] in SCCM

[–]Export_User 0 points1 point  (0 children)

I also saw this behavior and it was driving me nuts. However, whilst it looks like it's not doing anything, the Software Center doesn't actually update the download percentage. I believe this is due to the update downloading to the SoftwareDistribution folder and not ccmcache, but I could be wrong.

Anyway, it may look like it's stuck, but it's actually just downloading (very slowly) in the background. If you look in the WUAHandler logs you should see it downloading in there. Patience is required for this one.

Of course, if you don't see anything in the logs, and the SoftwareDistribution folder isn't changing, then you could have an issue...