Loading

Posts by MB

Microsoft 365 Apps (Office 365) hantering i MECM (SCCM)

Kör även denna bloggning på svenska (English by Google).

I min tidigare bloggpost, Office 365 ProPlus (Microsoft 365 Apps) hantering i SCCM (MECM) skrev jag om mitt sätt att säkerställa att samtliga Applikationspaket för Office 365 ProPlus, Visio Pro for Office 365, och Project Online Desktop Client alltid är av senast verifierad (godkänd för installation) version.

I denna bloggning så tar jag steget lite längre. Här ser jag även till att Office Deployment Tool (ODT) är i senaste version för att stödja installationen av den nya versionen av Office.
Jag har modifierat ett Powershell-script som Marco Hofmann & Trond Eric Haavarstein har skapat, så att det passar min idé.
Original scriptet: https://www.meinekleinefarm.net/download-and-install-latest-office-365-deployment-tool-odt

Det min version av scriptet gör:

  • Laddar ner senaste versionen av Office 365 Deployment Tool (ODT)
  • Kontrollerar om det är en nyare version av Office 365 Deployment Tool (ODT), och om det är en nyare version så Installeras den till en undermapp med versionsnummer som mappnamn. Är det inte en nyare version så hoppas steget över
  • Kopierar sedan den nya setup.exe till både mappen för källfilerna samt applikationspaketet i CM
  • Och till sist körs setup.exe /download download.xml för att ladda ner alla källfilerna

För att automatiserat detta kan man lägga in det i en schemalagd aktivitet.

<#
.SYNOPSIS
    Download and install latest Office 365 Deployment Tool (ODT)
.DESCRIPTION
    Download and install latest Office 365 Deployment Tool (ODT)
.EXAMPLE
    PS:> \\DFSSHARE.ORGANISATION.ORG\...\download.ps1
    Downloads latest officedeploymenttool.exe
    Creates a sub-directory for each new version
    Copies the setup.exe from the sub-directory to source-directory and cmsetup-directory
.NOTES
    Author: Magnus Bäcke
    URL: https://backes.nu
    Original Author: Marco Hofmann &amp; Trond Eric Haavarstein
    Original Author URL: https://www.meinekleinefarm.net &amp; https://xenappblog.com/
.LINK # This is the original script
    
Download and install latest Office 365 via Office Deployment Tool (ODT)
.LINK https://www.microsoft.com/en-us/download/details.aspx?id=49117 .LINK https://www.microsoft.com/en-us/download/confirmation.aspx?id=49117 #> $StartDTM = (Get-Date) $ODTDownload = "\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\ODTDownload\" $Vendor = "Microsoft" $Product = "Office 365 x64" $PackageName = "setup" $InstallerType = "exe" $LogPS = "\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\Logs\$StartDTM $Product $Version ODTDownload.log" $SourcePath = "\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\" $SetupPath = "\\DFSSHARE.ORGANISATION.ORG\CMSourceFiles$\Applikations\Microsoft Office 365\Files\" $Downloadxml = 'download.xml' $URL = $(Get-ODTUri) $ProgressPreference = 'SilentlyContinue' Set-Location $ODTDownload function Get-ODTUri { <# .SYNOPSIS Get Download URL of latest Office 365 Deployment Tool (ODT). .NOTES Author: Bronson Magnan Twitter: @cit_bronson Modified by: Marco Hofmann Twitter: @xenadmin .LINK https://www.meinekleinefarm.net/ #> [CmdletBinding()] [OutputType([string])] param () $url = "https://www.microsoft.com/en-us/download/confirmation.aspx?id=49117" try { $response = Invoke-WebRequest -UseBasicParsing -Uri $url -ErrorAction SilentlyContinue } catch { Throw "Failed to connect to ODT: $url with error $_." Break } finally { $ODTUri = $response.links | Where-Object {$_.outerHTML -like "*click here to download manually*"} Write-Output $ODTUri.href } } Write-Verbose "Setting Arguments" -Verbose Start-Transcript $LogPS Write-Verbose "Download latest version of Office 365 Deployment Tool (ODT)." -Verbose Invoke-WebRequest -UseBasicParsing -Uri $url -OutFile .\officedeploymenttool.exe Write-Verbose "Read version number from downloaded file" -Verbose $Version = (Get-Command .\officedeploymenttool.exe).FileVersionInfo.FileVersion Write-Verbose "If downloaded ODT file is newer, create new sub-directory." -Verbose if( -Not (Test-Path -Path $Version ) ) { New-Item -ItemType directory -Path $Version Write-Verbose "Extract setup.exe from ODT" -Verbose .\officedeploymenttool.exe /quiet /extract:.\$Version start-sleep -s 5 Write-Verbose "New folder created $Version" -Verbose Set-Location $Version Copy-item ".\setup.exe" -Destination $SourcePath -Force Write-Verbose "setup-exe copied from $Version to $SourcePath " -Verbose Copy-item ".\setup.exe" -Destination $SetupPath -Force Write-Verbose "setup-exe copied from $Version to $SetupPath (CM O365 setup Source files)" -Verbose } else { Write-Verbose "Version identical. Skipping folder creation." -Verbose } Set-Location $SourcePath Write-Verbose "Downloading Office setup-files according to the XML-file." -Verbose Start-Process ".\setup.exe" -ArgumentList "/download $Downloadxml" -Wait -PassThru start-sleep -s 15 Set-Location $ODTDownload Write-Verbose "Stop logging" -Verbose $EndDTM = (Get-Date) Write-Verbose "Elapsed Time: $(($EndDTM-$StartDTM).TotalSeconds) Seconds" -Verbose Write-Verbose "Elapsed Time: $(($EndDTM-$StartDTM).TotalMinutes) Minutes" -Verbose Stop-Transcript

 

Office 365 ProPlus (Microsoft 365 Apps) hantering i SCCM (MECM)

Ledsen, men denna bloggning blir på svenska (in English, by Google).

Jag har upplevt att en del företag har svårt att få till en bra hantering av Office 365 ProPlus, Visio och Project när det gäller installation och uppdateringar via SCCM/MECM (System Center Configuration Manager, eller som det numera heter Microsoft Endpoint Configuration Manager).
För att säkerställa att samtliga Applikationspaket för Office 365 ProPlus, Visio Pro for Office 365, och Project Online Desktop Client alltid är av senast verifierad (godkänd för installation) version är detta lösning som jag förespråkar.

Bakgrund
I SCCM/MECM skapas det statiska installationspaket (Application packages) för så väl Office 365 ProPlus som Visio och Project. Där Office 365 ProPlus oftast installeras under OS-installationen (via Task Sequence). När Office 365 ProPlus är installerat på klienterna blir de uppdaterade (patchade) via sedvanlig uppdaterings-rutin till nyare ”build” och ibland till ny version.
De statiska installationspaketen (Application packages) ligger fortfarande kvar på samma version och build som när de skapades.

Problemet
Användare A har sin dator installerad med Office 365 ProPlus sedan en tid, och fått både säkerhetsuppdateringar och ny version av Office 365 ProPlus. Nu behöver användare A även ha Visio installerat. Men eftersom den packade Visio-versionen i SCCM/MECM är äldre än den Office 365 ProPlus som användare A har installerat så kommer installationen att misslyckas.

Lösningen
På ett DFS-share som är åtkomligt från alla nät där klienter sitter (inkl. stagning-nät & VPN) skapar man en mapp för Office 365 filer (tex. Office365SetupFiles så att sökvägen ser ut ungefär så här: \dfs-share.organisationen.net\Office365SetupFiles$), i den skapar man två mappar, x86 och x64.
I mappen Office365SetupFiles lägger man sedan Office Deployment Tool (setup.exe) tillsammans med två XML-filer som man får skapa (en för x86 och en för x64) och som talar om vad som skall laddas ner (för exempel på XML-filer se längre ner i dokumentet).
I XML-filerna för nedladdning anger man alla produkter, språk och rättstavningsverktyg som kan tänkas behövas inom organisationen.
När mapparna och XML-filerna är skapade och på plats tillsammans med setup.exe (från Office Deployment Tool) kör man kommandot: setup.exe /download download_x86.xml för att ladda ner alla filerna för 32-bitars version, och sedan setup.exe /download download_x64.xml för 64-bitars version.

I rutinen för uppdateringar varje månad kör man setup.exe /download download_x32.xml (och setup.exe /download download_x64.xml) för att få de uppdaterade installationsfilerna (man tar sedan bort föregående version från nedladdningen). På detta sätt är alltid installationsfilerna uppdaterade, och givetvis kan man automatisera detta.
För installation skapar man sina statiska installationspaket (Application packages), enbart med filen setup.exe (från Office Deployment Tool) och den konfigurations-fil (XML-fil) som talar om vad som skall installeras. I XML-filen hänvisar man till DSF-sharet där nedladdningen finns, och installeras därifrån (exempel på XML-filer se längre ner i inlägget). Jag rekommenderar att använda PSADT (PowerShell App Deployment Toolkit) för att paketera installationen.

Sammanfattning
Nu i denna lösning när användare A med sin dator installerad med Office 365 ProPlus sedan en tid, med både ny version och säkerhetsuppdateringar nu behöver Visio så kommer installationen fungera, då installationsfilerna är i samma version som användare A redan har sitt Office 365 ProPlus på.

Office Deployment Tool (setup.exe) behöver uppdateras när man går upp i version för att stödja nya funktioner, på samma sätt som man kan behöva se över XML-filerna för att de nya funktionerna/produkter ska komma med, eller förhindras (använd Office Office Customization Tool).
Office Deployment Tool, https://go.microsoft.com/fwlink/p/?LinkID=626065
Office Customization Tool, https://config.office.com/deploymentsettings (skapa/importera/exportera konfigurationsfiler)

Exempel på konfigurationsfiler
Exempel på download_x64.xml

<Configuration ID="11666593-c103-4fad-bc07-0951fdee1223">
  <Add OfficeClientEdition="64" Channel="Broad" SourcePath="\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\x64">
    <Product ID="O365ProPlusRetail">
      <Language ID="sv-se" />
      <Language ID="da-dk" />
      <Language ID="nl-nl" />
      <Language ID="en-us" />
      <Language ID="fi-fi" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
      <Language ID="nn-no" />
    </Product>
    <Product ID="VisioProRetail">
      <Language ID="sv-se" />
      <Language ID="da-dk" />
      <Language ID="nl-nl" />
      <Language ID="en-us" />
      <Language ID="fi-fi" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
      <Language ID="nn-no" />
    </Product>
    <Product ID="ProjectProRetail">
      <Language ID="sv-se" />
      <Language ID="da-dk" />
      <Language ID="nl-nl" />
      <Language ID="en-us" />
      <Language ID="fi-fi" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
      <Language ID="nn-no" />
    </Product>
    <Product ID="LanguagePack">
      <Language ID="sv-se" />
      <Language ID="da-dk" />
      <Language ID="nl-nl" />
      <Language ID="en-us" />
      <Language ID="fi-fi" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
      <Language ID="nn-no" />
    </Product>
    <Product ID="ProofingTools">
      <Language ID="da-dk" />
      <Language ID="nl-nl" />
      <Language ID="en-us" />
      <Language ID="fi-fi" />
      <Language ID="fr-fr" />
      <Language ID="de-de" />
      <Language ID="nn-no" />
      <Language ID="sv-se" />
    </Product>
  </Add>
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Exempel på configuration_x64.xml för Office 365 ProPlus

<Configuration ID="5140f541-3226-4067-84d0-c3e53ac6d29f">
  <Add OfficeClientEdition="64" Channel="Broad" SourcePath="\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\x64" OfficeMgmtCOM="TRUE" AllowCdnFallback="FALSE">
    <Product ID="O365ProPlusRetail">
      <Language ID=" en-us " />
      <ExcludeApp ID="Bing" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="OneNote" />
    </Product>
    <Product ID="LanguagePack">
      <Language ID="sv-se" />
      <ExcludeApp ID="Bing" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="OneNote" />
   </Product>
    <Product ID="ProofingTools">
      <Language ID="fr-fr" />
      <Language ID="de-de" />
     </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="FALSE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Updates Enabled="TRUE" />
  <AppSettings>
    <User Key="software\microsoft\office\16.0\excel\options" Name="defaultformat" Value="51" Type="REG_DWORD" App="excel16" Id="L_SaveExcelfilesas" />
    <User Key="software\microsoft\office\16.0\powerpoint\options" Name="defaultformat" Value="27" Type="REG_DWORD" App="ppt16" Id="L_SavePowerPointfilesas" />
    <User Key="software\microsoft\office\16.0\word\options" Name="defaultformat" Value="" Type="REG_SZ" App="word16" Id="L_SaveWordfilesas" />
  </AppSettings>
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%windir%\Logs\Software\" />
</Configuration>

Exempel på configuration_x64.xml för Visio Pro for Office 365

<Configuration ID="986241dd-06ab-49ed-a5e0-5fb25297a666">
  <Add OfficeClientEdition="64" Channel="Broad" SourcePath="\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\x64" OfficeMgmtCOM="TRUE" AllowCdnFallback="FALSE">
    <Product ID="VisioProRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Bing" />
      <ExcludeApp ID="Groove" />
    </Product>
    <Product ID="LanguagePack">
      <Language ID="sv-se" />
      <ExcludeApp ID="Bing" />
      <ExcludeApp ID="Groove" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="TRUE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Display Level="Full" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%windir%\Logs\Software\" />
</Configuration>

Exempel på configuration_x64.xml för Project Online Desktop Client

<Configuration ID="2755de1d-24bf-4299-b3a0-70ce31c8941b">
  <Add OfficeClientEdition="64" Channel="Broad" SourcePath="\\DFSSHARE.ORGANISATION.ORG\Office365SetupFiles$\x64" OfficeMgmtCOM="TRUE" AllowCdnFallback="FALSE">
    <Product ID="ProjectProRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Bing" />
      <ExcludeApp ID="Groove" />
	</Product>
    <Product ID="LanguagePack">
      <Language ID="sv-se" />
      <ExcludeApp ID="Bing" />
      <ExcludeApp ID="Groove" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="TRUE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%windir%\Logs\Software\" />
</Configuration>

Summer is here

The summer heat is here, and I’m completely out of office. Looking forward to an exciting autumn.
Have terminated me from my current job and see the light in the tunnel of the future. It will be an exciting autumn.

Have a greate summer!

A Safer Message App

Thought to get my friends on a little more secure thoughts.
If you agree to this, it will cost you about US $ 3.57 if you use Android, or US $ 2.99 if you use iPhone to be safer.

At first, I just thought of mentioning something that I experienced as scary.
Me and Terese sat and talked as we sometimes do. After a while, Terese picks up her mobile and goes into the Facebook App, and hux flux then it shows up advertising about something we had recently talked about. None of us have used any device (neither mobile, computer or anything else) to search or anything else to check on / up what we had talked about.

The only conceivable thing is that the Facebook App listens (it has rights to record sound via the microphone) on us and uses what we are talking about in order to target advertising (and build on our shadow profiles).

And even WhatsApp Messenger is good at leaking, so it will soon appear advertisements in different flows about what we have written to each other in messages. 
I totally understand why Jan Koum and Brian Acton (both co-founders of WhatsApp) chose to jump off from WhatsApp / Facebook 
https://en.wikipedia.org/wiki/Jan_Koum | https://en.wikipedia.org/wiki/Brian_Acton

I can buy this with cookies that stalk us online when we browsing the Internet (there are other tools that can protect us there). But having Apps that actually listen / spy on us when we don’t even use them is not really what I “signed” up on.

Sure, we need Facebook to follow friends and what’s going on in the world nowadays. I mostly use Facebook to follow my interests (in the same way I use Twitter, LinkedIn, WeMe, Google+, etc.). 
But I do NOT use the Facebook App, nor the Facebook Messenger App. 
I run with the browser version of both, and chose not to install their apps and give Facebook rights that I do not think they should have.

I still have WhatsApp installed and use the App since most people I communicate with using WhatsApp. But I’d rather stop using that App as well.

So a while ago I made the choice to go over to Threema. 
Threema is a secure communication app, where all communication (message / conversation) is encrypted, and not even the company behind Threema (Threema GmbH) can intercept or spy on their users . As cream on the cake, Threema GmbH in Switzerland currently has the best data protection laws (delivering better privacy than GDPR, and is not under the EU or US laws). 
https://threema.ch/en | https://en.wikipedia.org/wiki/Threema

However, there are 2 “disadvantages” with Threema.

  1. Not many users use it, certainly because of point 2.
  2. The app / service costs about US $ 3.57 / $ 2.99, and WhatsApp costs you no money (but WhatsApp will cost you, and your friends souls).

But you do not need a mobile subscription to use Threema. No mobile number is needed to register or use Threema.

And you, your mobile / internet provider cannot sniff your communication when you pass it over Threema. Your mobile / internet provider can use your information in SMS and mobile calls to build a profile about you (thanks to GDPR you can say no thanks to it, if you live in Europe). 
And don’t make me start to waffle about the vulnerabilities in SS7 (which allows anybody to listen to conversations, read text messages and track a mobile as easily as possible). 
https://sv.wikipedia.org/wiki/Signalsystem_number_7 | https://www.theguardian.com/technology/2016/apr/19/ss7-hack-explained-mobile-phone-vulnerability-snooping-texts-calls

The final sprint:

  1. Stop using Apps where there are web versions
  2. Switch to a Safer Message App (Threema ?)
  3. Start and think about what you are worth, and protect your value and privacy.

Threema for Android 
https://play.google.com/store/apps/details?id=ch.threema.app

Threema for iOS 
https://itunes.apple.com/us/app/threema/id578665578

Threema in the browser 
https://web.threema.ch/

A comparison between Facebook Messenger, Threema and WhatsApp 
https://versus.com/us/facebook-messenger-vs-threema-vs-whatsapp

Diskpart to the rescue

In my work, I recently heard that more often new devices (desktop’s/laptop’s) fails in the beginning of the OSD (OS deploy) because of something is wrong with the partitions on the hard drive. The Boot-image can’t download policys or files to the disk, so it fails. Often the IT-person needs to boot the device and re-partition the disk, and after that start the OSD again, and it will work. I have not done some examination on why it fails. The OEM’s OS works on the device/disk. But I have a workaround, or it’s not mine workaround. I did find it on the Internet for a few years ago, so I don’t remember whos to credit (I’m sorry).

But this is the workaround I have.

Begin by creating a txt-file with the content of commands for diskpart we will be using later (this is for UEFI-disks).
sel disk 0 clean convert gpt cre par efi size=200 assign letter=s format quick fs=FAT32 cre par msr size=128 cre par pri assign letter=c format quick fs=NTFS exit
Save the file (I have named my file uefi_disk.txt ), and put it on your SCCM Package-share. Then you will need to create a Package in your SCCM-console, where you will point out the source files (where you saved your new .txt-file). You don’t need to create a program, just select “Do not create a program” and click next, and just go on and finish the wizard. Here is two ways to use this. The first one, if you boot your PC’s from a boot-media (CD/USB), you can create a new boot-media and put in a prestart command to run diskpart. So go one and create a new Task Sequence Media if you choose this way. Mark Boot media, and Next Continue the wizard, entering your “SCCM-info” till you come to Customize the task sequence media. Here you will need to tick the Enable prestart command checkbox, and also enter Command line: cmd.exe /c diskpart /s uefi_disk.txt <– or the name you gave your .txt-file You must also select the Diskpart package you created earlier, and point out your Distribution point. After that, finish the wizard, and you are now ready to boot using your new boot-media.
The other one is to put this in your boot-image (if you PXE-boot your devices, choose this). Using this way the prestart command will always run (when using TS using this boot-image), and you don’t need to create a new boot-image with this prestart command. Go to your Boot-image in the SCCM-console, and right-click it and choose Properties. Go to the Customization tab, and tick the Enable prestart command checkbox, and also enter Command line: cmd.exe /c diskpart /s uefi_disk.txt <– or the name you gave your .txt-file Klick Ok, to save and re-distribute your boot-image, and after that your done.
When you are here, click Next And diskpart will run After diskpart is finished, you can choose your TS, and continue your installation

What a wonderful beginning of the year?

Meltdown/Specter, 2 serious vulnerabilities.
Meltdown vulnerability is “only” on Intel’s CPUs, while Spectre is found in addition to Intel’s CPUs also with AMD and ARM CPUs.
Info: A Simple Explanation of the Differences Between Meltdown and Spectre

Many operating system manufacturers are in the process of developing software updates to protect against the Meltdown vulnerability. But due to the fact that information about these vulnerabilities leaked to the media prematurely, more or less many manufacturers were forced to release their updates prematurely, which in turn could have caused problems for many users.
There have been reported problems for Microsoft Azure customers after Microsoft updated their system.
Other users who installed updates have been affected by BSOD (Windows crashes, displays “blue screen”), this in relation to the fact that some AntiVirus products make unsupported calls to Windows kernel memory. Here, one must ensure that the AntiVirus is supported/updated, and also ensure that the following registry key is in the registry before installing the update:

RegKey="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name ="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD"
Data="0x00000000"

More information in the following links:

Important information regarding the Windows security updates released on January 3, 2018 and anti-virus software.

List of AntiVirus products and how they “support” the Windows update.

Windows Server guidance to protect against speculative execution side-channel vulnerabilities.

However, as this is hardware vulnerabilities, it may not be enough to update the operating system only, but you must also update the firmware for the hardware.
US-CERT has put together a list of manufacturers who have information/recommendation about their hardware:
https://www.us-cert.gov/ncas/alerts/TA18-004A

Infomaniak offering students free Web and Mail hosting

Swiss web host Infomaniak is offering students a chance to receive free professional Web and Mail hosting during their higher education. This full offer, which is unique in Europe, has a dual goal of promoting both the acquisition of digital skills and the creation of digital-related projects.

Read more about this great opportunity, and how to grab it: https://news.infomaniak.com/en/free-hosting-for-students/

Clear Clipboard when locking Windows

First, let me just say that I’m no security expert, but safety is something that I find interesting.

Today I saw the posts by Hasain Alshakarti on Facebook, Hasain had posted a link to Accessing the clipboard from the lockscreen into Windows 10 # 2.
Interestingly, Microsoft should have already blocked that security risk.

But you can prevent this yourself, so that Clipboard  is emptied when you lock Windows. No thirdparty software is needed.

Start Task Scheduler
Click on Create Task... under Actions, Task Scheduler Library in the right task pane (or right-click on Task Scheduler Library folder)
On General tab ->
Name: Clear Clipboard 
On Triggers tab ->
Click on New.. button
Under Beging the task, choose: On workstation lock, and click Ok button
Under Actions tab ->
Click on New.. button
Under Program/script, write: cmd.exe
Under Add arguments (optional): write: /c "echo off | clip" and click Ok butoon
Click on Ok button again, and you are done.

Cant turn on RSAT (0x80073701) in Windows 10

rsat-2For about 10 days ago, I tryed to install RSAT (Remote Server Administration Tools) on my work computer.
I downloaded the latest version, WindowsTH-RSAT_WS2016-x64.msu and run the installation. But when I went to turn RSAT on, I got the error message:

The referenced assembly Could not be found.
Error code 0x80073701
Tell me how to solve this problem

Unfortunately, Microsoft’s solution was not the right one for me.

But today (10 days later, and a variety of attempts to activate the RSAT) so I got to it.

I took the downloaded file, WindowsTH-RSAT_WS2016-x64.msu and packed it up (using 7-zip) to C:\RSAT
I started PowerShell as Administrator and went to the path: C:\RSAT and wrote:
DISM /Online /Add-Package /PackagePath:C:\rsat\WindowsTH-KB2693643-x64.cab

After DISM (Deployment Image Servicing and Management tool) run through, I also execute .\ Rsatcustominstaller.exe in the PowerShell window.

A restart later, and RSAT is in action.

 

YouTube to Sonos?

sonoscastFirst day of the holiday and I nailed it. At last we can look at music videos on YouTube, and play the sound in our Sonos speakers. The only thing I had to do was to complete our Sonos system with a Google Chromecast Audio.
But yes. It’s not just YouTube we can cast to Sonos, we can of course also cast sound from Netflix, HBO and everything else possible sound from our computers and mobile devices. And tomorrow I will to cast the sound of British GP (Formula 1), I can’t wait. 🙂