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…
We have been working on migrating a customer from Windows 7 over to Windows 10. Our goal is to have Windows 8 and 10 clients pull the pictures from Active Directory to the users local profiles.
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.
Security is very important, especially when it comes to IT.
We’ve created a password generating script to assist in making sure we all use high security passwords.
I’ve always liked VB scripting, but I have officially converted to Powershellism (?!).
If you’d like to convert your old VBS scripts to Powershell check this out…
Understanding how the Configuration Manager client works is a crucial part of troubleshooting.
Here you will find information about how to retrieve policies from the SCCM server.
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…
There is not enough temporary space reserved to download the software. You can use the Configuration Manager control panel applet to adjust the available temporary space.
Heres a small VBs script for fast Active Directory group creation.
Paste the following code into a text file and rename it to “CreateADGroups.vbs”.
