Hi folks, as promised i present the next part of my MDX posts. This time i will elaborate on the technical part of MDX as well as give you, the reader, a view of how OS deployments are done; the MDX way.
MDX design; technical facts
MDX is build in PowerShell, the GUI is designed in SAPIEN’s Primal Forms Community Edition and the application is programmed in Microsoft’s own PowerShell ISA. the script counts around 3000 lines of code of which roughly 2000 lines are accounted for by the GUI. the script is divided in 15 Functions and 6 sections.
The general idea of the applications is: unification and simplification of MDT and accompanying tools to an end-to-end deployment solution.
Architecture
MDX is designed around the functionality of a few components:
- Microsoft’s MDT
- MDTdb.psm1 PowerShell module by Michael Hiehaus
- Mark Russinovich’s PsExec.exe
- Microsoft’s WDSUtil.exe
Here is the graphical representation of the design
MDX has a few sections that do the work. each section does a part of the total solution; for example there is a section in MDX that accepts input from the GUI checks its validity and, if verified, adds or modifies a corresponding computer item in MDT- in its database. another section does communicate with PzExec.exe and adds the needed variables to the tools to get a deployment started.
How does MDT accomplish end-to-end automated deployment?
The ‘secret’ of MDX is the way all under laying components are ‘orchestrated’ to make a ‘deployment symphony’ …. the way MDX does this is as follows:
- MDX controls the MDT database (which is crucial for end-to-end automated deployments) via PowerShell
- MDX takes variables from the UI and combines it with preconfigured components in MDT and other used tools
- MDX manipulates a computer object from the MDT database in such a way that it is deployment ready
- MDX adds ‘non standard’ items or features to the preconfigured building blocks like: for example: add a few applications to the deployment of a certain computer and adds a user account as local administrator to the same deployment as well
- MDX controls the WDS PXE server and thus controls who may- and may not boot to PXE and do a deployment via the network
- MDX can directly fire a preconfigured computer to do a deployment.
What is to be expected from doing deployments with MDX
Apart from the fact that MDX takes away the direct interaction with MDT, MDX will give the User direct control over all building blocks of the deployment chain from a single GUI. the user can start off with a computer name, check the settings and modify them and fire of the deployment to the machine.
One important thing to realize is: MDX will help the user to select ALL settings and set them without the possibility of human error (like typing). MDX eases these tasks by presenting a simple but effective UI that will help de user select those things needed MUCH faster AND easier than when he- or she would do manually in MDT itself. as a bonus it eases the management of tools like WDS or the start of MDT deployment in the traditional way.
The next post will present a real world example of deployment with MDX. till next time.
