![]() ![]() ![]() A variable set by the CustomSettings.ini file, can be read and modified by the Wizard, the Task Sequence Engine, the MDT VBScripts, and PowerShell scripts. MDT (And SCCM OSD) all use the *same* namespace for variables. Variables are typically created in the CustomSettings.ini or BootStrap.ini file, or the Litetouch Wizard, and then variables are consumed by the Stand Alone task Sequencer, and other Litetouch scripts. But are there any other ways to provide UI input options? MDT VariablesĪ quick reminder about variables in MDT. MDT provides a way to add pages to the LiteTouch deployment wizard, Michael Niehaus even has a tool on his Blog site where you can edit these pages, and create new ones. For example, an LOB App that needs to know which local database to connect to run: San Francisco, New York, London, or Beijing? Now optimally, I would recommend a script to try to determine which local server to connect to, perhaps a table of Local Gateways and their associated Database servers. Say you have an application that requires some additional information from the user during installation. View the last picture of this post to get an idea of what this hack is about. ![]() It’s not really a feature of MDT, more like a hack for the scenario(s) listed here. I developed this solution back in 2009, but I never got around to documenting how it would work in practice. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |