gsadmin/Set-OSDInformation
1
0
Fork 0
mirror of https://github.com/freedbygrace/Set-OSDInformation.git synced 2026-07-26 11:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
freedbygrace
2020-05-31 22:41:26 -04:00
committed by GitHub
parent a9ffef2ec5
commit 380b7a53c4
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -2
View File
@@ -1,7 +1,9 @@
# Set-OSDInformation
Works independently or along with the Set-OSDTime script to retrieve built-in and custom task sequence variables marked with a prefix. The values from those variables can then be optionally recorded to the registry, and additional WMI. The WMI class properties will be tied to the registry values. This is the same functionality seen from the ZTITatoo script from MDT, but more flexible and complete. The WMI class will also be set with auto recovery using MofComp in the event of WMI repository rebuilds.
Works independently or along with the Set-OSDTime script to retrieve built-in and custom task sequence variables marked with a prefix. The values from those variables can then be optionally recorded to the registry, and additionally WMI. This is some of the same functionality seen from the ZTITatoo.wsf script from MDT, but more flexible and complete. The newly WMI class will also be set with auto recovery using MofComp in the event of WMI repository rebuilds. This script will also make a best attempt at determing the data types based on variable names and value type combinations so that when the data gets recorded into WMI, you retain the ability to sort the data based on date, true/false, numerical values, etc. If all the data went in as strings, dates for example would only be cosmetic, so you could not sort oldest to newest.
Some default task sequence variables will always get recorded, but anything that you prefix with the configurable "OSDVariablePrefix" parameter, allows you to create custom task sequence variables and this script will detect those variables and add them to the registry or WMI. See the script notes at the top of the script for more information. This script will also make a best attempt at determing the data types based on variable names and value type combinations so that when the data gets recorded into WMI, you retain the ability to sort the data based on date, true/false, numerical values, etc. If all the data went in as strings, dates for example would only be cosmetic, so you could not sort oldest to newest.
Note: The MOF file for the WMI class will be created on the fly and imported using MOFComp.exe
Note: Alot of attention was put into the logging. Please check it for errors and more detailed information when testing in your respective environments!
Have Fun!