When creating a SQL Server maintenance plan, the owner of the plan is set to the user logged in when the plan is created. If another user makes changes, the owner does not change. Sometimes it may become necessary to change the owner (e.g. if the owner's account is being disabled or removed). You can manually change the owner through the SQL Server Agent's Job Activity Monitor but changing it there is only temporary: changes to a maintenance plan will reset the owner back to the original one. Changing the owner from within the maintenance plan is not possible through the GUI, but there is a way to make the change through T-SQL statements.
The following queries need to be run against the msd ...
A few steps to enable management of your Office 365 subscription using Powershell. One uses Powershell because not all configuration is available through the Office 365 Portal, and it's also useful for automation.
Note that the old method of installing the Azure Active Directory Module is deprecated. The only supported way is to install the cmdlets directly through Powershell, as described below.
UPDATE (2018-07-09): removed all deprecated information.
UPDATE (2016-04-20): updated links and information.
Download and install the Microsoft Online Services Sign-In Assistant.
Download and install Windows Management Framework 5.1.
Open an elevated Powershell, and run the following comma ...
If you are using multi-factor authentication, it is not possible to use the old method of connecting to Exchange Online. You will have to install the Exchange Online Remote PowerShell Module, and use the Connect-EXOPSSession cmdlet to connect.
You can install the PowerShell module by following these instructions:
Log on to Exchange admin center.
In the left menu, click on hybrid.
Click the configure button for the Exchange Online Remote PowerShell Module. This will start the installation.
In the Application Install that appears, click the Install button.
A shortcut will be placed on your desktop which will start PowerShell with the required modules.
You can manage Exchange Online through Powershell in a similar fashion as you would an on-premise Exchange. There are some differences between available cmdlets and what they do between on-premise Exchange and Exchange Online, but the majority are the same.
Using multi-factor authentication
The method mentioned below is deprecated and only works for non-MFA usage. If you are using multi-factor authentication, you will have to use the Exchange Online Remote PowerShell Module to connect to Exchange Online. Instructions can be found in this article.
Using PS remoting, the cmdlets for Exchange Online are imported through the internet, so first, you need to change the Powershell execution polic ...
When using VMware vConverter Standalone 6.1 or newer, performing a P2V may fail very early in the process with the following error:
FAILED: A file I/O error occurred while accessing ''.
You can work around the issue by enabling Use proxy mode on the Destination System page at the conversion wizard. As an alternative workaround, perform the P2V directly to a ESX host.
The reason for the error has to do with the ESX host's certificate not being trusted when performing a P2V to a vCenter.
If the Use proxy mode does not resolve your issue, please check whether the FQDN of the ESX host is resolvable on the machine running vConverter. Even when using strictly IP addresses, the FQDN still ...