Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Joe.McCall last won the day on November 5 2020

Joe.McCall had the most liked content!

Community Reputation

21 Excellent

My Information

  • Location
    Tri Cities, WA USA
  • Agent Count
    1000 - 1500 Agents

Recent Profile Visitors

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

  1. You can run these via Execute Script or parse them for your own usage. Add ! to your Execute Script parameters to disable the timeout. Silent install, downloads all setup files via CDN, and includes some predefined custom settings that are delineated in the attached word doc. In this form, it supports Office 365 c2r, Project, and Visio, but could pretty easily be modified to add Office 2019. Recently updated this with the new update channels and the latest ODT, which changed filenames. PS1: Create your config file function New-ClickToRunConfig() { Param( [Parameter(Position =
  2. THE PROBLEM: Windows Update stops reporting the monthly security Cumulative Update and instead only reports the Feature Update to the latest OS release. Automate relies on Windows Update to report that there are available security updates, so it treats it as "Everything is great, no missing updates!" when in fact the system is missing potentially critical Cumulative Updates. I used PSWindowsUpdate to test and confirm the behavior on a number of computers. As of yet, I have not found a way to get around this wonderful "feature" (presumably it works differently if you are using Enterprise o
  3. This function script should work regardless of whether you are on-prem or cloud. It uses the LT Server Execute function to run any powershell code you pass to it as a parameter. Run-PowershellOnLTServer.xml
  4. USMT is Microsoft's utility for profile migration (can be used in tandem with WDS for re-imaging, OS upgrades, etc); Windows Easy Transfer back in Windows 7 was basically a fancy GUI running USMT. It's part of the Windows 10 ADK (https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install); there's command line syntax for the adksetup.exe to only install USMT. CL docs here: https://docs.microsoft.com/en-us/windows/deployment/usmt/usmt-command-line-syntax ScanState.exe to analyze and capture, LoadState.exe to restore. I scripted some basic validation to estimate the capt
  5. USMT works wonderfully and can be fully done via command line. I built a script that uses the XML files from EhlerTech: https://ehlertech.com/customxmls/
  6. Exchange CU's since Exchange 2013 are not typical updates, so they don't show up in Automate.
  7. We approve Security, Office (since Office security updates are not classified as Security) and Definition updates in the default policy. We have a ticket template to review the rest the last week of the month; if nothing legitimate comes up from a Google or Reddit search for issues with that KB, it typically gets approved.
  8. If you are using Execute Script in Automate, all error handling and validation needs to be done in the script. Don't write unnecessary output if you plan to do variable validation in the Automate script. Is this path valid? No, write-output "FAILED: Path is invalid", exit. Did my files download? No, write-output "FAILED: File xyz not found", exit. Wrap your new-item, download, and shortcut commands in try{} catch{} so you can capture any errors if those are failing. If it passes each validation and you get to the end and you test-path on your new shortcut and it exists, write-output "Success".
  9. There are out-of-box scripts that handle this. Look at _System Automation\Functions\Ticket Comment* and Ticket Finish* ; I recommend creating a scriptlet for calling the Ticket Comment function that includes the variables it uses so you can just drop the scriptlet in and set the subject and comment values.
  10. If your script is literally just those two lines with no validation of the result afterwards, the script will always returns as successful unless it is unable to run the Shell command. You can run a shell command with invalid parameters and have it "succeed", because the Shell command executed with the parameters provided, regardless of your intended result. There should always be validating of the command; Shell returns %shellresult% with any output from the executed program. For most software installers, you're likely to receive "OK", so you should be calling a Resend Software command after
  11. You can convert to an Automate script (Shell Execute for the taskkill and wmic commands, Folder Delete command for deleting the folders, just create entries that are filtered by 32-bit and 64-bit), but the simpler method is to just use the Execute Script function and set it to BAT file, paste that in, and you're done.
  12. We're an HP shop, so the majority of our managed agents are HP pro/elite models. Softpaq Download Manager can do BIOS updates (there's a thread on the forums with the scripts I use). I run a script that pulls a reportinto an EDF. Internal monitors run off the EDF contents. Drivers are auto-installed. BIOS updates generate a ticket so we can coordinate with end users to make sure they don't interrupt. We inherited a handful of Dell systems, so we have dabbled a little bit with the Dell Command Update tool, which I believe also can do BIOS updates, but I have not automated anything for them yet.
  13. In the database, it's in the computers table. PowerProfiles lists all available on the agent (format: "GUID, Name|GUID, Name"), CurrentPwrProfile shows the active profile GUID. You can search for it, via the Legacy search (Prower Profile GUID).
  14. @mikey090tx I ported the whole set of scripts over to the Image Assistant last year, but I was having a lot of mixed results, downloads/installs failing, etc. I suspect it's improved since then, but I have not had time to revisit and see if the updates have resolved the issues I was seeing.
  15. You can (could? I assume this still works) pass the server information to the MSI /quiet /norestart SERVERADDRESS=https://yourserver.com SERVERPASS={yourpass} LOCATION={id} Found that those were needed when I was deploying via Intune the first time; didn't matter if it was a custom client specific MSI, if I didn't pass the extra params it just installed with no server information.
  • Create New...