Trying to push out the newest DCU with an xml file for the settings that I want to use. I’ve looked on YouTube, Dell and here for answers but still cannot seem to find anything that works. I’m looking for the simplest solution. I don’t write scripts and am just a desktop support technician so this is new for me.
Right now I’m using the MSI and have tried bundling into intunewinapp as well as LOB but cannot seem to get it to pick up the XML file. Any help would be greatly appreciated.
Videos
Hi guys,
So am trying to deploy this tool by using this video:
https://www.youtube.com/watch?v=yoIN6DXYWRA&feature=youtu.be
Everything works fine except for the fact that on the device the app has default values only, not the ones I have changed prior to exporting the .xml
Did any of you work with this tool and can assist? Thanks.
EDIT:
Managed to fix the issue by running a PS script as a custom detection script with the following arguments:
New-ItemProperty -Path Registry::"HKLM\SOFTWARE\Dell\UpdateService\Clients\CommandUpdate\Preferences\CFG" -Name "ShowSetupPopup" -PropertyType "DWORD" -Value "0" -Force
Start-Process "C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" -ArgumentList "/configure -lockSettings=enable" -NoNewWindow -Wait
Start-Process "C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" -ArgumentList "/configure -scheduleAuto" -NoNewWindow -Wait
Start-Process "C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" -ArgumentList "/configure -userConsent=disable" -NoNewWindow -Wait
Start-Process "C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" -ArgumentList "/configure -scheduleAction=DownloadInstallAndNotify" -NoNewWindow -Wait
Edit 2:
Having an issue with 3 devices that offer exit code 1602, but the users didn't cancel the instalation.
Edit 3:
Found out the reason. It was because either Dell Support Assist or Dell Updater was installed on the target machine. So if you are trying this, make sure to uninstal first.
Is anyone managing Dell Command | Update for Azure AD Joined devices (cloud only)? My understanding is that you can use the Dell Cloud Repository Manager to specify what drivers/BIOS updates you want and it spits out an XML. This XML would then need to be delivered to the device via Intune and consumed by Dell Command. You would need to update this XML and repeat the process every month or every quarter whenever you pick new drivers or BIOS. Unless, however you just said install ALL drivers and BIOS then it might be a set it and forget it operation. Thoughts on this process?
Hi, I recently deployed Dell Command Update 5.7.0 to my test endpoint (Dell Latitude 5410) I imported the ADMX config files and have deployed them too, all other updates have shown up and been installed successfully (wifi drivers, intel graphic drivers ,etc) all except BIOS which I double checked and its 2023 version, although looking at dells website theres a much later version of the bios, its also plugged into the power plug and at 100% (tried reinstalling windows and redoing enrollment etc)
I have uploaded images of the ADMX configurations, machine is running Windows 11 Business
https://ibb.co/hFLrQPvX
https://ibb.co/Pv2BFP74
https://ibb.co/qShPPjY
I am trying to push out both dell command update and a config for my machines.
I am able to push out cell command with no issues. My issue is the config.
All videos and write ups tell me to use an XML but I've been having issues. I see others as well but everyone just replies saying to use dcu-cli.
I am struggling really hard to understand and deploy a config with dcu-cli.
From my understanding it's just running to dcu-cli.exe and using config commands. It just Does not work at all!!
Can someone who pushes out a config vid dcu-cli please post how they do it. I'm going insane
I do it through dcu-cli. Dell's documentation on the CLI is good but what they don't tell you is that in 4.6 setting the restart option and automatic updates are cannot be done in one go. You have to call it twice because it tries to set the child attributes before the parent attributes.
I deploy as a Win32 app and key off the registry values for each setting to determine whether or not it's been configured.
I got this working with 4.6.0. I will try to remember to post it when I'm in the office tomorrow