Dell Command Update Registry Settings

[Rashawn Devegowda]

Sorryfor my post it was late and I was tired. Let me attempt to clear this up a bit. The Get -ItemProperty locates the Registry keys based on it finding the DisplayName being = Dell Command Update. Which I defined in the beginning statement. The uninstall string is defined in the registry keys as MsiExec.exe /X4CD85DD3-A024-4409-A0F2-F70DE1E4A935 the number between the brackets changes based on the version. So after the ($DellCommandUpdate) and before the start of the subcommand I need to pull that registry key out, strip out the brackets, so it can be shoved in the variable $Uninstall which I had defined.

Maybe the better question is the Regkey is found above so I need to define that Regkey minus the brackets as the $Uninstall variable. I hope that makes sense. I only listed what the found variable was for this as a reference to what was found. Sorry about that.

dcu-cli.exe /Configure -scheduleAuto

However, if you bring up the GUI it still asks for the recommended auto update.

Is there a registry entry that shows this set?

Any help is appreciated.

Thanks

EDIT: It may be a file within your profile as well but it may not be human readable(like a dat file). I guess the export/import might be the best option but again, just trying to see if any files are modified when you run your command may tell you whether the settings are being applied. Perhaps even try to change another setting just to see if it works.

I am trying to add registry keys to Windows 10 using a PowerShell script. The key in the registry must have double quotes included in the data field so I understand I must escape the double quote with a backslash.

[Tested] For anyone that still wants to use reg add in powershell, just add ` after the backslash. The reg commands requires \" when you need to add double quotes in the value of an entry and powershell escapes double quotes by using `

This is possibly a two part worklet, depending on the version of Dell Command installed. If you have the normal executable application version you can run the Run Update script below. However if running the UWP version for Win10, you need to uninstall that and install the non UWP version using the uninstall/reinstall script below (Make sure to include all needed files like the DCU executable, MUP and Package files. Those are currently available at: -us/sln311129/dell-command-update?lang=en

Remediation:

Grab the Dell command update .msi and attach to a worklet. You can make two separate worklets with installation + scanning / patching. Since automox will clean up our msi at the end and its a relatively small file, I just run it as a combo install + scan/patch.

I ran Dell update again. It reports my system up-to-date. Windows update show version available is 0.1.10.0. Device Manager reports version 1.8.0 installed. How do I kill Windows attempt to install apparently incorrect firmware?

Some folks are leery of going into the registry to do things and much prefer making changes via the GUI. It is those folks that I had in mind when I posed the above question intended to be for Alex, since I quoted Alex.

Device Installation settings is under Settings\System. But it includes all things from other Mfg, such as icons that depict your h/w like printers, and apps from other mfg including drivers. Best to use GP or regedit specific for drivers in WU.

Im trying to run a script to disable bitlocker for one restart and then run dell updates so when bios is done we dont wind up with dozens of users stuck on a "enter your bitlocker key" screen. However, when I try to create a task chain I can add my suspend bitlocker script, but dell updates are seemingly not allowed in task chain?

If Dell updates are not included as an option within a task chain that will be because Quest thought it was a bad idea to put them in. There will be no workaround, the only advice I can offer is to raise it as an idea in uservoice.

Looks like I can't reply to that comment chain anymore, but no, we have not gotten bitten by BIOS updates triggering Bitlocker when done via KACE. We are using the default settings for Bitlocker with PCRs 0, 2, 4, and 11 for UEFI. Been couple of years now. I had just assumed something automatic was suspending Bitlocker for me, since our testing (and now lots of field use) has not given us issues.

Yes, it is for the initial install where openmanage is needed, and thus needs to be pushed twice since the only thing to show on first detect is openmanage and the rest don't populate until that is installed.

So with this tool installed you can retrieve the warranty information about your Dell systems using SCCM. This tool scans your SCCM SQL database for Dell machines and their asset tags. Furthermore the information is checked against its own warranty database for the warranty information. It then inserts all the warranty information into a new table in your SCCM SQL database. You will find the table is created with name DellWarrantyInformation. Finally this information stored in the table can be seen using reports.

In addition, enter the SCCM database server FQDN or IP address. In the next step enter SCCM database name. For use integrated security type YES and press enter. So the configuration settings are now stored in the system registry.

Most noteworthy, the warranty information is first retrieved. The information is then saved as an XML file in the %ProgramData%\Dell\CommandIntegrationSuite folder. In addition you will find the file saved as WarrantyInformation_MM_DD.xml.

Dell Command Update 3.0 is shipping with the Dell FIDA (Factory Installed Dell Application) Image. Some of you already have hundreds of devices on your shelves, or end users that have Dell Command Update 3.0 installed on them. But Workspace ONE UEM only supports Dell Command Update 2.x because of the lack of the command line (CLI) support in the latest version.

We needed a workaround. We wanted to use Workspace ONE UEM to remove Dell Command Update 3.0, verify that it is removed, then install Dell Command Update 2.4, and verify its success. We worked with one particular company that has almost 9500 SCCM-managed Dell Windows 10 devices and is working toward Workspace ONE management on all devices, with a co-management goal of only 2-3 months per device. We needed a way to roll back Dell Command Update 3.0 and install 2.4 when a device becomes enrolled.

We wrote a PowerShell script that detects whether or not Dell Command Update 3.0 is installed, and if so, it runs an uninstall command against the MSI for Dell Command Update 3.0. We zipped these up and created a Dependency App in Workspace ONE UEM.

On the Deployment Options tab, configure the Install Command to run the PowerShell script. The script checks the registry to determine if the application is installed. If it is installed, it runs an msiexec uninstall command. If it is not installed, it exits with code 0.

Configure Deployment Options as below. We considered adding a data contingency to this, but the way the data contingency works was not conducive to the company in question, who has thousands of devices in the field, sometimes with only 3G connectivity. Please take note of the exit codes here; they are essential for this to work.

Senior Customer Success Engineer, Omnissa.Jason has been a part of VMware, then Broadcom, and now Omnissa for almost 15 years. He has worked as a Technical Account Manager, Professional Services Consultant, and now, a Customer Success Engineer.

Dear Forum Users & Mr Adobe...

Looking at the Forum, a number of people are encountering the same issue as me...

I have had problems opening PDF files progressively over time (past 6 months) and I reached a point where none of the files I had previously opened/edited would open by double clicking the file, or right clicking the file and selecting . I could open via the back door, viz. Open Acrobat then open the file, however the files would eventually lock up & crash...

I recently upgraded Acrobat to 64 bit which made the problem worse, such that I couldn't open any PDF files at all.

By running the Windows Task Manager I found that Acrobat was running as a background process, force stopping it and restarting did not fix the issue...

Protected Mode is a security feature introduced in Reader 10.0 that protects users from viruses and attacks. This is a good thing for your security, but it sometimes misinterprets files as malicious and doesn't open them correctly. (Sometimes?!)

Run the PDF file again with Protected Mode off. Keep Protected Mode off if everything works well this time instead of having to turn it on/off many times throughout the day. Of course, this will compromise your security, so it's up to you to decide if it's worth keeping off!

______________________________

Thankyou Adobe for running protected mode in the background and not telling your customers.

And I would like to undertand Mr Adobe, what is the purpose of this "Protected Mode", and who exactly is it you are protecting, your cloud?? I run both Virus & Malware Protection on all my machines. So what is the purpose of you locking my PC down?

You are in breach of my Privacy!!

Please also note Mr Adobe you have wasted 5 days of my time this month while I have dealt with your under performing "Product". And I now must set up all my settings (again). Are you going to compensate me for this time??

And Mr Adobe, don't you dare modify the registry on my PC and blow my registry settings away the next time you deliver me and "upgrade"...

Can I come along and adjust the registry in your machines? I seriously doubt it...

Thankyou for your rubbish response. The link provides no solution to the problem, other than have a guess because Adobe recons it's the User's virus protection software.

Nothing to do with my antivirus software.

This problem has been occuring on 3 different PCs each running different virus protection software and different version of Windows 10.

The solution to the problem is provided in my content above, by turning off protected mode in the O/S registry...

None of the questions I raised above have been answered...

3a8082e126