I’ll bring some things up that are new in 1803, that I think it will be useful in daily work

Diagnostics & Feedback

In Europe its a lot of talk about GDPR and security about the personal information. So when they are focusing on this part, I think many companies are very happy about this feature.
In Settings\Privacy\Diagnostics & Feedback you can see that they added Basic

It means that they dont send anything about your personal information and so on.

They even added an app “Diagnostic data viewer” that you can see what information sends to microsoft and the information that stays on the machine. So now they trying to be as transparancy as posible.
You can find the app just “Settings\Privacy\Diagnostics & Feedback aswell”, just scroll down.

Fun fact with this is that they are live data for example go and google something and go back here and you see what’s happening on the machine.

https://docs.microsoft.com/en-us/windows/configuration/configure-windows-diagnostic-data-in-your-organization

Focus Assist

If you are working very deep with something, like writing a blog post or just want not to get interrupted by colleagues.
You can set automatic rules, let say every morning from 08.00 – 09.00 I don’t want to get notifications and so on.
If you duplicating your display, let say you have an important presentation that you don’t wanna get spammed by colleagues, also possible to make a rule like this.

If you go to the Priority list, you can specify people that you wanna let through even you are on “focus assist mode”

Task View

They have rebuild this button totally, you can find this in the left corner of your screen

The new one is working like this: It remembers what windows you have opened for as long as one month, so if you accidentally closed something you can go back here, and quickly find it.
On the right side you see a Timeline, so you can easily scroll down to a specific date.

That was all, for now, then its a bunch of other features but I think these three sticks out from the rest

Thank you for reading

/Pontus

Hey there!

If you working with Client Management, you probably have some test-pc´s on your machine, Hyper-V machines maybe?

So Ive made a script that creates Hyper-V machines pretty sweet actually.

Let me go through the script here.

1. First, you need to modify the script, Go to the #Modify part of the script, change it so it fits your computer.

2 If you dont know what NetworkSwitch that you uses, you can find it Here
(In my case im using “Bridge”

2. Then save it and run the script.

Param(
[Parameter(mandatory=$True,HelpMessage="Whats the name of the VM?")]
[ValidateNotNullOrEmpty()]
$VM_Name,

[parameter(mandatory=$True,HelpMessage="How much memory do you want in GB?(Example 4)")]
[ValidateNotNullOrEmpty()]
$VMMemoryinGB,

[parameter(mandatory=$True,HelpMessage="How large HD in GB (Example 80)")]
[ValidateNotNullOrEmpty()]
$HDsizeinGB
)

Function Select-FolderDialog
{
    param([string]$Description="Select a Folder that you wanna save your vhdx files",[string]$RootFolder="Desktop")

 [System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms") |
     Out-Null     

   $objForm = New-Object System.Windows.Forms.FolderBrowserDialog
        $objForm.Rootfolder = $RootFolder
        $objForm.Description = $Description
        $Show = $objForm.ShowDialog()
        If ($Show -eq "OK")
        {
            Return $objForm.SelectedPath
        }
        Else
        {
            Write-Error "Operation cancelled by user."
        }
    }

# You can modify here if you always want to save your machines to a specific folder.
$Folderpath = Select-FolderDialog
$Path = "$Folderpath\$VM_name.vhdx"

#Modify
#Change $NetworkSwitch to your standard switch in hyper-v, mine is Bridge
$NetworkSwitch = "Bridge"

#Creating Virtual machine
New-VM -Name "$VM_Name" –MemoryStartupBytes ([int64]$VMMemoryinGB*1024*1024*1024) -NewVHDPath $Path -NewVHDSizeBytes ([int64]$HDsizeinGB*1024*1024*1024) -Generation 2 -SwitchName $NetworkSwitch

#Change boot Order 'Network THEN Hardrive'
$vmNetworkAdapter = get-VMNetworkAdapter -Name "Network Adapter" -VMName "$VM_Name"
$vmHardDiskDrive = get-VMHardDiskDrive -VMName "$VM_Name"
Set-VMFirmware "$VM_Name" -BootOrder $vmNetworkAdapter, $vmHardDiskDrive

Start-vm $VM_name

& vmconnect.exe localhost $VM_name

Write-host "Succefully Created VM, Starting.."  -ForegroundColor Green

( You can also download the script here New-VM )

3. When you running the script, you gotta answer some questions. (Type !? for help)

4 (Optional) If you want you could just run the script with some parameters like this or you could run the script in the console

5. Answer all of them like this.

6. Then the Machine will start, and you are good to go.

7. Done

Good luck

/Pontus

Add a language pack these days can be done in different ways, I recommend do it by DISM. Here´s a guide how you can do it

What you need
* Powershell 3.0 or later.
* ADK
* Windows 10 Pro 1703 or later

Ok, Now we need to put some files on the right place to begin, Start to create a folder structure like this.

1. Start with ISO folder.
1.1 Download the ISO from Voluming Licensing Service Center or a Windows 10 EVAL ( https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise)
1.2 Just right click on the ISO and Mount
1.3 Copy all the files from the Mounted ISO to your ISO folder.
1.4 Now it gonna look like this.

2. Language_files
2.1 Download the CAB file here: https://www.itechtics.com/windows-10-version-1709-language-packs-direct-download-links/#Swedish
2.2 Copy the CAB file the the “Language_files” folder.
2.3 Now its gonna look like this.

3. Scratch its just a empty folder.

4. temp_ISO also is a emtpy folder

5. Lets start the scripting. Open up the Powershell script.
You can find it Here:Add-Language-pack

6. Open up the script and we need to do some Editing.

7. Edit the variables so it fits your environment.

8. Run your variables

9. Now in Windows 10 1709 its same ISO for PRO, PRO N, Enterprise, Enterprise N etc. So we need to figure out what Index we want to modify

10. In my case, I want to modify Windows 10 Enterprise N, Run the variable

11. Now its time for some Action, Run the next line, to “#Mount your ISO with that specific index and put it in a temporary folder.”

11. Then run the next one, #Time to Add the language pack

12. Time to run the next one. “#Do changes in the mounted Image”

13. Ok, Now the last command, #Unmounting the ISO file and saving it..

14. The language pack is now into the .ISO file, and you have succeeded to do your mission.

BUT

15. We need to modify the answer file, if you want to deploy this with MDT/SCCM, otherwise, it will choose EN because its “standard” on the ISO file

16. Open Windows System Image Editor on your machine ( you need ADK to have this program installed)

17. Right click on Select a Windows image or catalog files – Select Windows Image..

18. Choose the .ISO file that you just modified.
“C:\temp\Add-Language-pack\ISO\sources\install.wim”

19. Choose the Index that you wanna modify, In My case Windows 10 Enterprise N

20. Rightclick “Create or open an answer file” then New Answer file.

21. Click on Components then “amd64_Windows-International-Core_10.0.16299.15_neutral then Add Settings to Pass 4 specialize

21. Change Settings like below
InputLocale sv-SE
Systemlocale sv-SE
UILanguage sv-SE
UILanguageFallback en-US
UserLocale sv-SE

22. Click on Components then “amd64_Windows-International-Core_10.0.16299.15_neutral then Add Settings to Pass 7 OOBesystem

22. Change Settings like below
InputLocale sv-SE
Systemlocale sv-SE
UILanguage sv-SE
UILanguageFallback en-US
UserLocale sv-SE

23. Save the file and name it like answer.xml or something like that.

24. Now we are done, You have a proper ISO to work with, and a answer file that will change the language while deploying your machines.

/Pontus