In V3, Dell Removed CLI support. No Importing Policy or Triggering DCU from command line. However, as you have found, you can create the settings on a test machine, export the associated registry key, then use that as your make-shift policy. For Enterprise use, until they add CLI support to 3.X, I see no point in moving past 2.4.
You can export/import settings over the registry but you can't trigger to do the updates over the command line (usefull by deployment tools like sccm). That the reason why enterprises are still using 2.4.
Customers are waiting about 6 Months for this feature "(will be restored in future release)". It will be nice when Dell can here make a comitment about when we can have this feature back.
MikeyMcG
9 Posts
1
November 1st, 2018 11:00
I think I found an alternate way to set this in the registry.
HKLM\SOFTWARE\DELL\UpdateService\Clients\CommandUpdate\Preferences\Settings\Schedule
ScheduleMode = ManualUpdates
gwblok
3 Posts
0
January 31st, 2019 20:00
In V3, Dell Removed CLI support. No Importing Policy or Triggering DCU from command line. However, as you have found, you can create the settings on a test machine, export the associated registry key, then use that as your make-shift policy. For Enterprise use, until they add CLI support to 3.X, I see no point in moving past 2.4.
Christian_IT
1 Message
0
February 1st, 2019 07:00
You can export/import settings over the registry but you can't trigger to do the updates over the command line (usefull by deployment tools like sccm). That the reason why enterprises are still using 2.4.
Customers are waiting about 6 Months for this feature "(will be restored in future release)". It will be nice when Dell can here make a comitment about when we can have this feature back.
FlowLive
1 Message
2
May 16th, 2019 11:00
You used "Dell" and "commitment" in the same phrase?
How could you?