Getting error when installing SQL Server 2012 remotely on Windows 2008 R2 SP1 using Powershell V2.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2067922433
  Exit facility code:            1214
  Exit error code:               511
  Exit message:                  The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
  Start time:                    2013-09-19 15:08:00
  End time:                      2013-09-19 15:08:22
  Requested action:              RunRules

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130919_150745\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngineRuleFailureException
    Message: 
        The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
    HResult : 0x84be01ff
        FacilityCode : 1214 (4be)
        ErrorCode : 511 (01ff)
    Data: 
      SQL.Setup.FailureCategory = RuleViolationFailure
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Configuration.RulesEngineExtension.RunRulesAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)

I am using Powershell V2 to attempt to script a simple installation of SQL Server 2012 Management Tools via the command line options as follows:

$ret = Invoke-Command -ComputerName $Computer -ArgumentList $MEDIA,$FEATURES,$ACTION,$OPTIONS,$INSTALLDIR -Credential $cred -Authentication Credssp  -ScriptBlock {
param($MEDIA,$FEATURES,$ACTION,$OPTIONS,$INSTALLDIR)
Import-Module ServerManager
$tran = ""
if (-not [IO.Directory]::Exists($MEDIA)){
$hn = hostname
return 0,"Failed to find SQL Server Installer at $MEDIA on $hn"
}

Try{
& $MEDIA\setup.exe /Q /ACTION=$ACTION /FEATURES=$FEATURES /IAcceptSQLServerLicenseTerms /UpdateEnabled=False /INSTALLSHAREDDIR="$INSTALLDIR\Program Files\Microsoft SQL Server" /INSTALLSHAREDWOWDIR="$INSTALLDIR\Program Files (x86)\Microsoft SQL Server" $OPTIONS | Out-String -OutVariable tran
} Catch [System.Exception] {
return 0,$_.Exception.ToString()
}
return 1,$tran
} 

I am passing credentials as well as authentication level of Credssp. The SQL Media resides on the remote server. I run the script with elevated permissions and yet it still acts like it does not have permissions to the registry. I have checked the remote registry service to be enabled as well. Credssp for the client and server are configured.

This very same process works fine in Windows 2012. but seems to fail in Windows 2008 R2, can anyone give me some possible things to look for?

Also this is an new install, no existing installations of SQL Server, and I am using a user that is a domain user with local Administrator rights on both the local and remote systems.