Jump to content

tonkabay

Members
  • Content Count

    5
  • Joined

  • Last visited

  • Days Won

    1

tonkabay last won the day on June 28 2018

tonkabay had the most liked content!

Community Reputation

2 Neutral

My Information

  • Agent Count
    1500+

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. tonkabay

    Automating Domain Join

    @DarrenWhite99 I'm getting this error when I try to open many of the imported scripts, eg "AUTOMATIC - Perform Domain Join". Any idea how to resolve that? Could this have anything to do with the fact that I've previously imported (and renamed) many of your other scripts (eg, GetFile and Email results to technician)?
  2. tonkabay

    Repository of scripts to remove programs

    My advice: Take a look at this for an example of how you can build a master PowerShell script that acts as "repository" of sorts for removing bloatware: https://github.com/arcadesdude/BRU/blob/master/Bloatware-Removal-Utility.ps1 I'm sure you can adapt it to your purposes and deploy via an Automate script (suggest using the Execute Script: Powershell Bypass function or similar technique to bypass execution policy). Since bloatware often evolves over time, this framework can easily be adapted. This approach of course requires some PowerShell savvy. You can also accomplish these uninstalls via a series of smaller LabTech scripts that are called by a master de-bloat script (this is my approach, to allow for EDF-controlled granularity in extent of each client's "debloating"). Consider selling different hardware next time, if possible. The way I see it, Microsoft ships Win10 with enough bloatware (which, BTW, can also be removed with LT/PoSh scripts). Find an OEM (or perhaps their "business" product line) that doesn't bundle as much bloatware of their own. We sell exclusively Dell for workstations (Business lines only, eg, no Vostro or Inspiron), and they are very light on the bloatware (some of it is actually super useful, eg, Dell Command Update).
  3. Thanks for the tip @DarrenWhite99. I've edited my post to include a ZIP of the update script, which should bundle the other dependencies as you said. Once this script is more mature, I'll probably start a new topic for it.
  4. @mr.wallstrom Attached are two scripts — one installs (or upgrades) Dell Command Update, and the other utilizes dcu-cli.exe to install all available updates and reboot. I have yet to implement logging of dcu-cli output or error/return code handling, so at the moment, the script is unaware of the what was installed, which updates were successful, or whether a reboot is required (the script simply assumes one is required and does so, unless param AutoReboot is set "false"). If any of you want to help out with adding that, I'd certainly appreciate it! These scripts rely heavily on @DarrenWhite99's fantastic GetFile and "Email Script Results to Technician" scripts. I don't think these XML exports will import GetFile or "Email Script Results to Technician" for you, so you'll probably need to get those separately and ensure they are linked properly wherever you see that they are called within the "Run Script" functions in these 2 scripts. More info is contained within the notes for each script. Note that these scripts are only tested on DCU-compatible Dell models running Win10 v1607 or later. Also note that you must place the DCU installers in the appropriate directory on your LTShare (as written, Software\Dell Command Update\Dell-Command-Update_@TargetVersion@.exe, where TargetVersion = 2.4.0), available here (you want 2.4.0, NOT 3.0!). Be sure to look over the scripts and the variables, globals, and parameters before deploying this script en masse. Hope this helps out, and sorry if my script isn't as well commented/portable as others on this site... this is my first script contribution to LTG LTG_DCU_InstallUpdatesandReboot.zip
  5. @mr.wallstrom, I've been working on it. Right now I have a working auto-install DCU script (w/optional auto-reboot/recall), but it doesn't have any (working) logging or error handling functions. All I have right now is an email of the DCU XML report to the person that ran the script — haven't finished the log/report parsing and error handling yet. I should have something working to share by the end of this week... I have a lot of new Dells to build that could use this.
×