Back in 2012 I wrote an article about dynamically setting a computer name during a Task Sequence. Here is my updated and improved script. I’m currently setting up a deployment solution running SCCM with MDT 2013…
I set up a small script which adds the username supplied during OSD to the local administrative group instead, which you could run from a TS.
This way only the Primary User gets elevated privileges over their own PC.
Here is the back end script that does all of the work. I’ve made some comments on the script in efforts to keep this post less wordy and more scripty.
Again if you have any specific questions please let me know.
Deployment solution based on SCCM 2012 intregrated with MDT 2012. The idea was to set up a User Driven Installation (UDI) so the IT department would have to do as little as possible during the installation process.
Part of this solution was to manage the clients names, we decided to use the serial number as an identifier…
As part of MDT 2012 UDI there is a new wizard page for setting User Device Affinity as part of the task sequence as well as a designer page for configuring the UDA page. The User Device Affinity wizard page is…
After editing the UDIWizard_Config.xml file and updating my Distribution points the UDI wizard would no longer let me through.
I edited the welcome text to something a bit more personal than the standard version, however there seems to be a limitation in UDI…
A customer requested a Lite touch installations process with the ability to change the computers name, OU’s and application setup. Here’s a quick guide how to get the applications to work.
