Home » Posts tagged '10'
Tag Archives: 10
To ensure that the same background is applied to all users when they log in, you can add two Task Sequence steps that will automatically set their background to whatever you specificy it to be..
CMD /C REG ADD HKU\DU\Control Panel\Desktop /v "Wallpaper" /t REG_SZ /d "<PATH>\background.jpg" /f
Then we can set the style, or how it will apply…
There are 6 possible values:
|Wallpaper Style||Value Data|
CMD /C REG ADD HKU\DU\Control Panel\Desktop /v "WallpaperStyle" /t REG_SZ /d "4" /f
Rermember to replace <PATH>\background.jpg with the actual path of your file (No quote marks or the image wont be applied!)
Here is how to remove the Edge Icon from the desktop on Windows 1803:
Create a new “Run Command Line” step with the following command:
cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ /v "DisableEdgeDesktopShortcutCreation" /t REG_DWORD /d "1" /f
And voila – the Icon is gone!
(Credit for Reg Hack goes to NathanielArnoldR2 on Reddit)
For a while, like most of you I guess, I have maintained at least one Task Sequence for not only each type of OS (Server, Windows 7, Windows 10, etc) but also for each edition of an OS (Pro, Enterprise, Standard, Data Center, etc).
Whilst this is great, it does mean that it requires a lot of effort to keep these up-to-date when you have new Applications, or Updates ,or drivers.
Each individual TS needs to be updated to reflect those changes.
So, I decided to try and reduce that to one “Super” task sequence that has everything in on place and installs the required OS, Setttings and Apps all from a single variable that you specify at the start of the Deployment.
Create the Collection Variable
This is essential – without this the whole thing wont work. Simply create a new Collection Variable (see here for how) and call it something suitable – I used “OSSelection”.
Create the Task Sequence
You can either create a new TS from scratch, or as I did, create a blank TS and copy/paste your existing information in and edit it there.
For ease I am only doing 2 OS types – Server 2016 and Windows 10
Once you have done that you can start to organise it depending on your requirements.
First up was to select which Operating System to apply.
So I created a group called “OS Selection and moved the existing Apply Operating System Image step into here and copied it, renamed them to my respecting OS and changing the settings accordingly. The example below shows my settings for Server 2016:
Once done, we now need to tell the TS when to apply these settings by clicking on the Options tab and settings the conditions as shown:
.This means that this step will only apply if you enter “2016” into the prompt during deployment – more on that later
For Windows 10, I decided to use the release number (1703, 1709, 1803, etc)
It is then just a case of repeating the process for all the settings where you only want them to apply to specific OS types or versions
The following condition can be used to apply to all non Windows Server OSs (10,7, etc) and, as its applied to a group, will affect all steps within that group:
And this is the end product. The expanded sections (except the top branch) are where I have applied my conditions:
That’s it – just deploy it to the desired collection (In this case – All Unknown Computers). Oh and remember to add a boot image as well!
I also created Collection Variables with preset values so that if a machine needs to be re-imaged, the correct OS Variable is re-applied. (You don’t want your Web Server to become Windows 10!)
Deploying your Task Sequence
Once you have deployed your TS you can now use it:
Select the Task Sequence:
Now Fill in your variables – As this is a new computer, I also need to fill in its intended name.
By entering “2016” I am saying I want to install Server 2016…
And we’re off..