Archive for March, 2018

Here are two articles to explain the usage of USAGE LOCATION field, required when assigning an Office 365 license:

Assigning an Office 365 license:

Usage Location and the Limits depending of the countries:


How to install the Exchange management tools and PowerShell cmdlets:

For Exchange 2016:

in short: Setup.exe /Role:ManagementTools /IAcceptExchangeServerLicenseTerms

Best practices:

Connecting to Exchange on-premises using PowerShell remoting is a simple task, and means that you do not need to go the trouble of installing the Exchange management tools on your computer just to perform day to day administrative tasks.

There are three steps to establishing a remote PowerShell session to your Exchange server:

  • Capture admin credentials
  • Create a new PSSession
  • Import the PSSession

Usage: Connect-Exchange -URL exchange2.mydomain.local


Scripts repository for Exchange:




Web resources:


New Microsoft French Datacenters:

  • 3 new datacenters in Paris working synchronously + 1 datacenter in Marseille working asynchronously with Paris.

Interesting in the context of GDPR rules and sovereign data. But also important will be the Multi-Geos offer coming to provide worldwide presence:

Control where each user’s data is stored

  • Meet your data residency needs in the cloud by storing your Office 365 data at-rest, on a per-user basis, in chosen Office 365 datacenter geographies

Empower global collaboration

  • Migrate from on-premises to a single Office 365 tenant and enable a unified communication & collaboration experience across your company

Supported DATA: Exchange, Sharepoint, Onedrive

Some links:

Microsoft Trust Center

Data Resiliency in Microsoft Office 365

Cloud for Good

LinkedIn: Yes, you can put your toxic data in Office 365

By default Microsoft does not provide tools to migrate OneDrive data; Sharepoint data; exchange mailboxes data from a O365 tenant to another O365 tenant, in a context of company acquisition or devestiture:

Here is the List of software vendors for Azure/Office 365 tenant data migrations:


Quest => pros: for exchange online migrations

Avepoint => pros: for sharepoint online migrations

Sharegate => pros: for sharepoint online migrations

Cloud fastpath by tervela => pros: for data migrations

code2 => pros: Exchange online migrations




Cloud migrator 365

bitTitan => pros: for exchange online migrations





Deciding which protocol to use for which service

The key distinguishing factor for our service will be found in the URL of the resource… If our URL looks like X, then it is a Y service, and you use Z tool to get to it

URL Service Type Cmdlet
Ends in .asmx or ?WSDL SOAP New-WebServiceProxy
Contains API, especially api/v2 REST Invoke-RESTMethod
Ends in .php PHP/Form Invoke-WebRequest

REST v. Soap, whats the difference?

Both REST and SOAP are simply methods of accessing information presented via web services. It will suffice to say that REST is now in vogue, and is generally believed to be easier to use and manage than SOAP, which tends to be a bit heavier on XML.

“A nice analogy for REST vs. SOAP is mailing a letter: with SOAP, you’re using an envelope; with REST, it’s a postcard. ”


Working with Web Services, SOAP, PHP and all the REST with PowerShell

PowerShell Core 6.0 is a new edition of PowerShell that is cross-platform (Windows, macOS, and Linux), open-source, and built for heterogeneous environments and the hybrid cloud.

The goal of PowerShell Core is to remain as compatible as possible with Windows PowerShell. PowerShell Core uses .NET Standard 2.0 to provide binary compatibility with existing .NET assemblies

Microsoft will not replace the standard PowerShell by PowerShell Core. Both will coexist side by side until further notice.




This was one of the main blockers of Firefox adoption in the enterprise :


PowerShell remoting with SSH:


How to use SFTP (and SSH) with Powershell?

or Using WinSCP:

Else other:

SFTP powershell snap-in:

and paying software:


example of code using POSH SSH to use SFTP for secure file transfer (certified working! ;)))

$sftpUser = “myaccount”
$sftpServer = “103.x.y.z”
$LocalFile = “d:\data\filetoupload.txt”
$sftpPass = ConvertTo-SecureString -String “ttIJP0YPuPS6” -AsPlainText -Force
$sftpCred = new-object -typename System.Management.Automation.PSCredential -argumentlist $sftpUser, $sftpPass
$sftpSession = New-SFTPSession -ComputerName $sftpServer -Credential $sftpCred

Set-SFTPFile -SFTPSession $sftpSession -LocalFile $Localfile -RemotePath “/tmp/mydirectory/” -Overwrite




Now you can download and install Kali Linux directly from the Microsoft App Store on Windows 10 just like any other application:

First install the Linux subsystem and restart:

You can even do the same by opening PowerShell as Administrator and running the following command and restart your computer.

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux