wpeditor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/briangon/public_html/wp-includes/functions.php on line 6114
Since there is no MDT built-in variable assigned with just the wim name, i had to create a seperate step to create the variable “OSDImageName”, which i then used in my standard image apply step.
Here is what the Task Sequence looks like:
Step Name Text:
Expanding %OSDImageName% (%ImageSize%) to %OSDisk%\…
And here is how I create the OSDImageName variable.
cmd /c echo Set objShell=WScript.CreateObject("Wscript.Shell"):objShell.run "cscript.exe //nologo ""%SCRIPTROOT%\ZTISetVariable.wsf"" /VariableName:OSDImageName /VariableValue:"""^&Split(Mid("%InstallFromPath%",Len("%SourcePath%")),"\")(1)^&"""" > %temp%\test.vbs,1,True && wscript //nologo %temp%\test.vbs
/BG
https://chocolatey.org/packages/BatteryBar
Chocolately is like apt-get, but for Windows. My favorite thing about chocately is having the ability to reach out and update all of my packages with one command line “choco upgrade all”! Making the package took a bit of trial and error, but it was easy enough. It uses Powershell at it’s base and has an excellent package library and community. I only wish I found it earlier in my IT career!
I eventually will figure out a way to use these packages to my advantage within the MDT/SCCM world. That or learn PowerShell DSC (Desired State Configuration) already.
-BG
MDT Task Sequence’s Inject driver steps do not support specifying folders, so Selection Profiles are the defacto method for bridging this gap. Here is a script I created to ease the process of creating/importing multiple system drivers into MDT at once. If ran more than once, it will not create duplicate selection profile entries.
/BG
