Unsolved
1 Rookie
•
26 Posts
0
1209
April 19th, 2023 13:00
dcu-cli /configure - error code 2
There is a problem with this product when using a tool like SCCM Application to install the software, and configure it. The installation is fine, however when using dcu-cli /configure ... (doesn't matter what command) the dcu-cli returns error code 2.
This is due to the fact that SCCM runs these installations using the SYSTEM account in non-interactive mode. Apparently you're new version of dcu-cli doesn't like that and returns error code 2.
If it open a command prompt in the SYSTEM context, and run the same command, it's fine. I know I'm not the only one with this problem because many on other sites report the same.
https://www.reddit.com/r/SCCM/comments/xfg8of/comment/iop2kp0/
I highly dislike reddit but this does prove I'm not the only one. Some users are using serviceui.exe to wrap the installation command in it. This, however, would give a pop-up on a user system - even if brief - is unacceptable.
Please look into why the behavior has changed since 4.5 (which works fine).
From memory dcu-cli.exe worked correctly in system context with version DCU 4.2.1, Dell broke it with versions 4.3 and 4.4, then fixed it in version 4.5, and it's been broken again in 4.6, 4.7 and 4.8 versions.
DELL-MARCO G.
1 Rookie
•
8 Posts
0
April 28th, 2023 10:00
Hello! This will be corrected in DCU 4.9 which correctly has a release date of May 9th at the moment.
IanPMurphy
2 Posts
0
August 2nd, 2023 06:00
It seems like every version of DCU-cli comes with its own set of problems. For such a small tool it is just impressive that quality control can be so bad.
Whats wrong now? Well it seems that someone thought it would be a good idea to add a check to see if an older version of dcu-cli was already installed like, say, version 4.8 and simply bomb out if it is.
IanPMurphy
2 Posts
0
August 2nd, 2023 06:00
and before I forget, what gives with the continual swapping back and forth between 64bit and 32bit versions. It seems like every second version installs into \program files (x86), only to be then replaced with a 64 bit version. flip-flop-flip-flop ..... zero QA involvement
tanielsen
1 Rookie
•
26 Posts
0
August 2nd, 2023 07:00
I feel your pain Ian, but I do blieve 4.9 resolved my issues. We stayed on 4.5 and I'm now rolling out 4.9. As for the x86 or x64 folder location, that is funny you mention. I wrote a script to find the program before it attempts to run it! LOL