Error: Idm client exception: Error trying to join AD, error code [40024], user [administrator], domain [home.lab], orgUnit []

Couldn’t find anything on google, so connected to the VCSA via SSH, tried a simple ping test to see if DNS was the issue.. no dice. Then tried adding the VCSA to AD manually.
Heavy Palmface
Looks like the administrator password is expired.

So.. I logged into the DC, and as we expected,

So, as it turns out, if AD is healthy, this isn’t an issue. Who would have known…

The post VCSA 6.7: Error trying to join AD, error code [40024] appeared first on VirtJunkie.

To duplicate this on your system, you’ll need a copy of the script from my github. Once you have it, open Settings, Devices, and then select Keyboard:

Scroll all the way down to the bottom of the keyboard shortcuts, and select  the “+” to create a new shortcut.

As you can see, I’ve already got a couple of custom keyboard shortcuts there. I’ll show you how to create one to mute your line in input using the keyboard. Once you click the “+”, the screen below will appear. You’ll want to select your own keyboard shortcut, and ensure you’re using the correct path to the script.

Below is a copy of the script:

#!/bin/bash
#http://www.virtjunkie.com/ubuntu---mute-line-in-using-keyboard/
#https://github.com/jonhowe/Virtjunkie.com/blob/master/toggleLineIn.sh

OUT=$(amixer sset Line toggle)
RESULT=$(echo $OUT | grep "Left:" | cut -d'[' -f4 | cut -d ']' -f 1)
#notify-send pulls icons from /usr/share/icons/gnome/32x32
notify-send "Toggling Line In" "Line in is now: $RESULT" -i audio-volume-low

Note 1:

In order for this to work, you may need to ensure that Loopback is enabled. The easiest way to do this is to install the alsa-utils package, and run Alsamixer to enable it.

The post Ubuntu – Add Keyboard Shortcut for line in appeared first on VirtJunkie.

Some assumptions and prerequisites:

1. You have horizon workspace 1.5.1 (at least) downloaded, deployed to your infrastructure successfully, and you’re ready to go through the web configuration.
2. You have VMware vFabric Postgres downloaded and deployed to your infrastructure successfully, with no configuration added.

1. Proceed through the web configuration until you get to step 2a, and select External Database. Stop here…
2. Prepare your new external database
   1. SSH to the postgres server (I’ll assume the server is named hzn-db.test.in)
   2. Make changes to the postgres config: /var/vmware/vpostgres/9.2/pgdata/postgresql.conf.auto
      1. Max_connections = 300 (default is 100)
      2. Search_path = ‘saas’ (no value by default)
   3. You’ll have to prepare the postgre sql schema. Run these commands to configure it. VMware graciously has not provided the default password for the postgres user in any of their documentation, even after I opened a SR requesting the password. For your reference, it is “H0rizon!”. “myPassword” below should be replaced with the password you want to use for your horizon workspace postgres user.
      1. /opt/vmware/vpostgres/current/bin/psql -U postgres -W
      2. DROP SCHEMA IF EXISTS saas CASCADE;
      3. CREATE SCHEMA saas;
      4. CREATE USER horizon WITH PASSWORD ‘myPassword‘;
      5. ALTER ROLE horizon SET search_path TO saas;
      6. CREATE EXTENSION citext WITH SCHEMA saas;
      7. CTRL+D
   4. SSH to your service-va, and run the following command
      1. /usr/local/horizon/bin/setupExternalDb.sh
      2. The wizard will ask you for a postgres admin user (postgres), and the horizon user (horizon). The password for the postgres user, unless you change it is “H0rizon!”, and the password for the horizon user is set in step 3.

This should work – if you run into any issues, please comment!

The post VMware Horizon Workspace – Part 3 – Configure VMware vPostgres External Database appeared first on VirtJunkie.

The first section of the script contains variables that need to be set.

#region ========================================================================
# Created on:	9/3/2013 8:01 PM
# Created by:	Jon Howe
# URL: http://45.63.13.214/?p=539
# Filename:		Set-MailboxMoveActive-v2.ps1
#endregion ========================================================================

#region Set Variables
#Amount of mailboxes to migrate at a time
$BatchSize = 5
#Mailbox DB to pull mailboxes from
$sourceMailboxDatabase = "Mailbox Database 3"
#Default amount of time to sleep when we hit a roadblock
$sleepMinutes = 20
#Time to start migrating mailboxes
$startTime = Get-Date -Hour 23 -Minute 00 -Second 00
#Time to stop migrating mailboxes
$stopTime = Get-Date -Hour 05 -Minute 00 -Second 00
#Array containing all of your DAG servers (used to check disk space)
$DAG_Servers = @("EXCH-DAG-A","EXCH-DAG-B")
#OS label for the DAG DAGA/Log drives on your DAG servers.
$OS_Label_Prefix = "DAGDB*"
#Threshold for stopping the migration (in bytes)
$MinOSDriveFreeBytes = 16106127360 #32212254720 is 30GB, 16106127360 is 15GB
#endregion Set Variables

$PS_Is_Awesome = $TRUE #!!!
While ($PS_IS_Awesome) #region Main Loop
{
#region Check for Business Hours
if ( (Get-Date) -gt $stopTime -and (Get-Date) -lt $startTime ) #region In Business Hours
{
	Write-Host "We're in business hours. Sleeping..." -ForegroundColor 'DarkCyan'
	Start-Sleep -Seconds ($sleepMinutes * 60)
} #endregion In Business Hours
else #region Out of Business Hours
{
	#region Check to make sure drive space isn't too low
	foreach($mbx in $DAG_Servers)
	{
		$space = `
		get-WmiObject win32_volume -ComputerName $mbx |
		select driveletter,label,freespace,capacity |
		where {$_.label -like $OS_Label_Prefix}

		foreach($drive in $space)
		{
			$human_freespace = [math]::Round($drive.freespace / (1024*1024*1024),1)

			if ($drive.freespace -lt $MinOSDriveFreeBytes)
			{
				Write-Host "Drive" $drive.driveletter "on server $mbx with label" $drive.label "is under 30 GB. It's currently at" $human_freespace "GB..."
				write-host "Sleeping for $sleepMinutes minutes." -ForegroundColor 'DarkCyan'
				for ($i = 1; $i -le ($sleepMinutes * 60); $i++)
				{
					Write-Progress -Activity 'Drive Space is too low. Waiting until it frees up.' -Status "We've waited $i Seconds" -SecondsRemaining (($sleepMinutes * 60)-$i)
					sleep -Seconds 1
				}
			}
		}
	}
	#endregion Check to make sure drive space isn't too low

	#region Check to see if a move-request is currently occurring
	if (Get-MoveRequest | Where-Object { $_.Status -eq "Queued" -or $_.Status -eq "InProgress" -or $_.Status -eq "CompletionInProgress"})
	{
		Write-Host "There are move requests currently processing.  Sleeping for $sleepMinutes minutes" -ForegroundColor 'DarkCyan'

		for ($i = 1; $i -le ($sleepMinutes * 60); $i++)
		{
			Write-Progress -Activity "Can't begin if move requests are already running. Waiting for them to complete" -Status "We've waited $i Seconds" -SecondsRemaining (($sleepMinutes * 60)-$i)
			sleep -Seconds 1
		}
		continue
	}
	#endregion Check to see if a move-request is currently occurring

	#region General information display and information gathering.
	Write-Host "We're out of business hours, drive space looks good, and there are no batches running" -ForegroundColor 'Yellow'
	write-host "Let's submit one!" -ForegroundColor 'Yellow'

	# Get Mailbox Sizes
	Write-Host "Getting Mailbox Sizes" -ForegroundColor 'Blue'
	$allmbx = Get-Mailbox -database $sourceMailboxDatabase |
   		Get-MailboxStatistics |
   		Sort-Object TotalItemSize |
   		Select-Object DisplayName,TotalItemSize

	#endregion General information display and information gathering.

	# Submit move requests to best datatabase
	Write-Host "Submitting move requests now" -ForegroundColor 'Blue'

	$batch = 1
	for ($i=1;$i -le 5;$i++) #region For Loop
	{
		#region Determine the best database to send mailboxes to
		if ($i % $BatchSize -eq 0)
    	{
			# Find best Database
			$result = Get-MailboxDatabase -identity "DAG*" -Status |
 				Select-Object name,DatabaseSize,AvailableNewMailboxSpace |
        		Sort-Object -Property DatabaseSize

			$bestDatabase = $result[0].name

			$batch++
		}
		#endregion Determine the best database to send mailboxes to

	#Submit the mailbox move requests
	Write-Host "New Move -" $allmbx[$i].DisplayName "to DB" $bestDatabase  -ForegroundColor 'DarkGreen'
	New-MoveRequest -TargetDatabase $bestDatabase -Identity $allmbx[$i].DisplayName | out-null

	} #endregion For Loop

	Write-Host "Batches submitted. Sleeping for $sleepMinutes minutes" -ForegroundColor 'DarkCyan'
	for ($i = 1; $i -le ($sleepMinutes * 60); $i++)
	{
		Write-Progress -Activity 'Waiting while move requests complete' -Status "We've waited $i Seconds" -SecondsRemaining (($sleepMinutes * 60)-$i)
		sleep -Seconds 1
	}

} #endregion Out of Business Hours
#endregion Check for Business Hours
} #endregion Main Loop

The post Update: Exchange 2010 – Bulk Mailbox Migration In Batches (The Right Way) appeared first on VirtJunkie.

Fortunately, powershell gives us the ability to do this very easily.

Here’s how:

The command below is the building block for everything else you want to do with a service. Since vendors don’t provide a standard prefix with their service names (ahem, vmware – or in this case, HP), you need to use the -DisplayName parameter of this commandlet. You can use the asterisk as a wildcard.

Get-Service -DisplayName "HP*

Once you have a set of services, you can pipe them to another commandlet, and take action, such as stopping the service, or disabling automatic startup.

Run this command to stop the services.

Get-Service -DisplayName "HP* | Stop-Service

Run the command below in order to disable these services from starting automatically

Get-Service -DisplayName "HP* | Set-Service -StartupType "Disabled"

The post Disable Multiple Services using Powershell appeared first on VirtJunkie.