Start a Conversation

Unsolved

TH

5 Posts

11505

January 29th, 2019 13:00

Command | Update 3.0 Not Working

We recently upgraded Command Update from 2.3.1.46 to 3.0 on all systems (currently Windows 10 1703). After the upgrade I started getting reports from our support techs that Command Update was not working. They reported that when running Command Update 3.0 on a system it only returned "No updates available, This system is up-to-date". When investigating the issue, we could see that Dell's support pages offered updates that should be available via Command Update. Further investigation revealed that if the older version of Command Update is run on the same system where 3.0 did not offer updates, the older version would offer updates.

Research on this issue has not uncovered any known issues.

Is anyone else experiencing this issue?

Does anyone know of any reason that might prevent it from working correctly?

Is there any additional troubleshooting I can perform?

Or is this a bug for which we need to use 2.x as a workaround until the next version is released?

I appreciate the community's help on this issue.

 

Command Update v2.xCommand Update v2.xCommand Update v3.0Command Update v3.0

5 Posts

April 22nd, 2019 07:00

I discovered today that version 3.0.1 was released, however there's no details on this version. I've tested it on some systems, but the problem persists.

https://www.dell.com/support/article/us/en/19/sln311129/dell-command-update?lang=en

8 Wizard

 • 

47K Posts

April 23rd, 2019 04:00

You should be using version 4 and later for 10.  CCTK is now Dell Command. Dell Command and Configure (DCC, Formerly Client Configuration Toolkit CCTK) & Skylake systems

Dell Command | Configure 4.0 later is for platforms supporting WMI-ACPI BIOS (WINDOWS 10 UEFI)

View the complete list of the Newer and the Older Nomenclature Knowledged Base

Version 4.2 is the 2019 version of Dell Command | Configure.

There is support for this but its not free.

https://www.dell.com/learn/us/en/555/services/support-services-prosupport

Dell ProSupport. Proactive automated detection and alerts on critical issues with Dell SupportAssist technology* 24x7 direct access to highly trained engineers. Same or next business day onsite* repair after remote diagnosis.  Incident-based third-party software assistance*

 

Dell Command | Configure Version 4.2 Installation Guide PDF HTML

Dell Command | Configure Version 4.2 Command Line Interface Reference Guide PDF HTML

Dell Command | Configure Version 4.2 Release Notes PDF HTML

 

 

 

 

 

5 Posts

June 19th, 2019 12:00

My post is regarding Command Update, not Command Configure. There hasn't been a new version for a year now.

https://www.dell.com/support/article/us/en/04/sln311129/dell-command-update?lang=en

8 Wizard

 • 

47K Posts

July 12th, 2019 06:00

Dell Command | Update replaces DCSU and is a part of the Dell Client Command Suite

https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=y2kwd

Add awareness of Dell Command | Update 3.0 architecture. Windows 10 64-Bit LTSC 2019 required

UWP version of Dell Command | Update does not include a command line interface (CLI). For CLI functionality and additional scheduling options, please install DCU v2.4

https://downloads.dell.com/FOLDER05312739M/1/Dell-Command-Update_Y2KWD_WIN_3.0.1_A00.EXE

 

 

This UWP package provides the Dell Command | Update Application and is supported on OptiPlex, Venue Pro Tablet, Precision, XPS Notebook and Latitude models that are running the following Windows operating system: Windows 10 Version 1607 (RS1 Build 14393) systems or later.

If your system does not support windows 10 this will not work.

 

 

5 Posts

August 21st, 2019 15:00

As noted in my original post, we are running Windows 10 1703 (now 1809).

We discovered the root cause to this issue and are now using a workaround. For organizations that use a Powershell Execution Policy that requires Powershell scripts to be signed (i.e. "Allsigned") DCU will not work. To workaround the issue we temporarily change the Powershell Execution Policy registry value to "Bypass".

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ExecutionPolicy

We attempted to automate the process using a script to change the registry value and then launch DCU, but were unsuccessful in getting the app to launch. Reference: https://www.mrlacey.com/2017/01/launch-store-installed-app-from-command.html 

Having to change the registry value manually before we use the product is not ideal, but at least it works now.

3 Posts

February 24th, 2020 08:00

This issue seems to have persisted into 3.1 with the CLI feature and it's causing havok in our environment, did you ever discover a workaround that may encompass the CLI method? I've got 3020s on old BIOS versions that SHOULD be on A20 but DCU is reporting there are "No updates Available. Exit Code 500"

8 Wizard

 • 

47K Posts

February 24th, 2020 09:00

2 Posts

August 18th, 2020 17:00

Did anyone ever find a solution for this?  We are using v3.1.3 and it is not finding updates for some of our Optiplex systems.

No Events found!

Top