dnscmd - records from command line

DNSCMD dns1.my.internal.domain /RecordAdd my.internal.domain newhost CNAME orighost.my.internal.domain.

DNSCMD dns1.my.internal.domain /RecordAdd my.internal.domain newhost.my.internal.domain. CNAME orighost.my.internal.domain.

DNSCMD dns1.my.internal.domain /RecordAdd my.internal.domain A 10.1.1.17

Of course small/capital letters are not important - only for better understanding. Why to use DNSCMD still? Because not everywhere I can use PowerShell to register record and in this way it is much simpler than using GUI console of course.

powershell upgrade - windows 2008r2

Install WMF 5.1 - before installation upgrade .Net Framework to 4.5.2 and check $PSVersionTable. After WMF installation there will be additional restart.

Windows 10 telemetry & Windows Server - what to disable

Windows 10 and Windows Server 2016

Services to disable:

- diagtrack - stop and disable (it can be enabled by updates)

hosts file

::1 vortex-win.data.microsoft.com
::1 settings-win.data.microsoft.com
::1 vortex.data.microsoft.com
::1 vortex-win.data.microsoft.com
127.0.0.1 telecommand.telemetry.microsoft.com telecommand.telemetry.microsoft.com.nsatc.net
127.0.0.1 oca.telemetry.microsoft.com
127.0.0.1 oca.telemetry.microsoft.com.nsatc.net
127.0.0.1 sqm.telemetry.microsoft.com sqm.telemetry.microsoft.com.nsatc.net
127.0.0.1 watson.telemetry.microsoft.com watson.telemetry.microsoft.com.nsatc.net
127.0.0.1 redir.metaservices.microsoft.com
127.0.0.1 choice.microsoft.com choice.microsoft.com.nsatc.net
127.0.0.1 df.telemetry.microsoft.com
127.0.0.1 reports.wes.df.telemetry.microsoft.com
127.0.0.1 services.wes.df.telemetry.microsoft.com
127.0.0.1 sqm.df.telemetry.microsoft.com
127.0.0.1 telemetry.microsoft.com
127.0.0.1 watson.ppe.telemetry.microsoft.com
127.0.0.1 telemetry.appex.bing.net
127.0.0.1 telemetry.urs.microsoft.com
127.0.0.1 settings-sandbox.data.microsoft.com vortex-sandbox.data.microsoft.com