Users

All Posts (7)

avatar

OldLost

RDM CMDlets under 64 bit

avatar
avatar
avatar
avatar

You can run 32 bit RDM Cmdlets from 64bit Powershell. Here's how. Do all the following on the machine that has RDM installed, of course.

1. Enable PSRemoting. This only needs done once, not every time you want to use RDM Cmdlets. If you've already enabled it, skip this step.

Enable-PSRemoting -Force

2. Start a 32bit "remote" (it's actually local) session.

$Session32 = New-PSSession -ConfigurationName microsoft.powershell32

3. Load the RDM Snapin in the session. This assumes the RDM PS dll has already been registered.

Invoke-Command -Session $Session32 -ScriptBlock {Get-PSSnapin -Name *Remote.Desktop* -Registered | % { Write-Host "$_..." -NoNewline; if ( (Get-PSSnapin -Name $_ -ErrorAction SilentlyContinue) -eq $null ) { Write-Host "installing" -ForegroundColor Yellow; Add-PsSnapin $_ } else { Write-Host "already installed" -ForegroundColor Green; } }}

4. Import the RDM Cmdlets into your current (64bit) session.

$RDMModule = Import-PSSession $Session32 -CommandName *-RDM*

You can now use 32bit RDM Cmdlets in your 64bit PowerShell!

Get-RDMCurrentDataSource

Etc.

If and when you're done using RDM Cmdlets, do this:

Remove-Module $RDMModule.Name

Remove-PSSession $Session32

Click sends window behind RDM window to front

avatar
avatar
avatar
avatar
avatar

Nope. Macro/Script List is totally empty.

Click sends window behind RDM window to front

avatar
avatar
avatar
avatar
avatar

It's not always OneNote. It could be any program, as long as it's window is behind RDM's window, and directly below where the mouse is clicked.

Click sends window behind RDM window to front

avatar
avatar
avatar
avatar
avatar

I managed to capture a video of this happening. The video's about 30 seconds long. At the 21 second mark I click on the start button of the remote desktop, at which point the OneNote program I have running behind the RDM window suddenly pops to the front of the screen. I've attached the video (AVI) file as a zip file to save space.

Click sends window behind RDM window to front

avatar
avatar
avatar
avatar
avatar

Not sure that I can, it happens maybe once an hour or two. I've not been able to predict when it may happen; it seems pretty random but does happen often enough where it's very annoying when it does, so kind of hard to catch, but I'll see what I can do.

I have a two monitor setup so I'm trying to see if running RDM on its own screen with no other windows behind or in front of it cause it not to occur, as it does seem to be it's always a window underneath the mouse cursor (but behind the RDM window) when the click occurs.

If no one else is experiencing it, though, it's probably something specific with my workstation, such as another program that's running at the same time, like a mouse utility or something.

FYI, I'm running the Enterprise version, in case that makes any difference...

Click sends window behind RDM window to front

avatar
avatar
avatar
avatar
avatar

RDM v9.2.6.0 (but this has happened with all recent versions)

Every now and again, but several times a day at least, when I click on an item in an RDP window within RDM, another window (on my computer) somewhere behind where I click on the screen will suddenly pop to the front. Or it could be the RDM window is being pushed back, I really can't tell which it is.

Does anyone else experience this?

Powershell -norefresh

avatar
avatar
avatar
avatar
avatar

Powershell has a way to do this built-in. Add a line similar to the following to your profile file, or add it to the top of your script:

$PSDefaultParameterValues['Set-RDM-Username:NoRefresh'] = $true

This tells powershell that for the Set-RDM-Username command, the default for the NoRefresh parameter is $true. So it's the equivalent of having -NoRefresh on by default each time you call that Cmdlet. After this, if you did want it to refresh on a particular call, you'd need to add "-NoRefresh:$false" to the command line for that call.

Not sure what version of Powershell would be required for this; it may be a v3 feature and may not work in v2 (I don't know off hand, as I never use anything less than v3 myself).

HTH

edited by OldLost on 5/20/2014

edited by OldLost on 5/20/2014

1 - 7 of 7 items