by lunarg on April 26th 2017, at 16:50

Although Debian 7 "Wheezy" (release info) has been superseded by newer releases, it still benefits from Long Term Support (LTS) until end of May 2018. In case of disaster recovery, it may still be useful to download Debian 7 install images (ISO). They can be found here:

Installing Debian 7.11

by lunarg on April 26th 2017, at 10:35
After updating Rapid Recovery to 6.1, you will notice the reporting Powershell scripts (such as Reports.ps1) no longer work.

When running such a script, the following error is generated:

Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'file:///C:\ProgramFiles\AppRecovery\Core\CoreService\coreadmin\bin\Reporting.Implementation.dll' or one of its dependencies. The systemcannot find the file specified."

This is caused by several auxilliary script files not being updated as part of the general 6.1 release of Rapid Recovery, causing the reporting scripts (such as Reports.ps1) not to work properly.

To resolve, you can either dow  ...
by lunarg on April 14th 2017, at 17:15

By default, when logging in on a HP switch in IRF mode using the web interface, you can only retrieve hardware information of the switch holding the master role. You can retrieve information for the other switches when you log on using Telnet or SSH, then type:

display device manuinfo

This will display hardware information for all chassis and slots.

by lunarg on April 11th 2017, at 15:52
In Veeam, when backing up linux-based VMs with application-aware processing turned on, testing the credentials may fail even though they have been entered correctly.

First, check whether you are really using linux-credentials and not Windows credentials, this can often be overlooked very quickly.

Check whether you see the logon attempt in linux. Depending on the distro, it is logged in a file in /var/log. E.g. for Debian/Ubuntu, it's logged in /var/log/auth.log. Looking at the logging will reveal whether it is a password or SSH key problem, or something else is going on.

Another possibility is that the required cipher is not allowed. Veeam requires the cipher aes128-cbc to be enabled. Alt  ...
by lunarg on April 11th 2017, at 14:03

I wrote a script to list virtual disk information for a specified VM, including VMDK path, SCSI IDs and more. It is loosely based on this script but excludes all WMI info.

Download here.

by lunarg on April 10th 2017, at 11:36

You can manually trigger Azure AD Connect to perform a sync cycle. Open a Powershell on the server running Azure AD Connect, then type:

  • Perform a delta sync:
    Start-ADSyncSyncCycle -PolicyType Delta
  • Perform a full sync:
    Start-ADSyncSyncCycle -PolicyType Initial
by lunarg on April 10th 2017, at 10:41

During the installation of Azure AD Connect, the registration of the Azure AD Connect Health for Sync-agent may fail. When this happens, you can manually register the agent by running this Powershell cmdlet:

Register-AzureADConnectHealthSyncAgent -AttributeFiltering $false -StagingMode $false

You need the credentials of an O365 account with Global Admin rights.

by lunarg on April 6th 2017, at 10:35
Differentiating users that are synchronized from an on-premise AD and users created in Office 365 is easy when logged in through the Office 365 Portal. When using Powershell, it's another matter. While there's a parameter for Get-MsolUser to show only synchronized users, the ability to filter on only cloud users is missing. However, as cloud-only users do not have the ImmutableID set, you can build your own filter.

This one's obvious:

Get-MsolUser -All -Synchronized

You can filter on ImmutableID as it's not set for cloud-only users:

Get-MsolUser -All | ? ImmutableID -eq $null

If you want to filter out external users (i.e. if you shared something in Sharepoint Online with users that aren  ...
« April 2017»
« Most people tend to avoid true conflict. Ironically this breeds more conflict. »