Get-SCJob / Get-Job alias conflicts

Unfortunately, the Get-SCJob SCVMM command was aliased to Get-Job , which is a command that comes with Windows / Powershell natively..

In order to get around this awesome (sarcasm) problem, if you are trying to get to the Windows jobs, you have to reference the fully qualified command, which is:

Microsoft.PowerShell.Core\Get-Job

Otherwise, you'll always get the results from Get-SCJob whether you intended to or not.

Have an open case on this, no hotfix / fix date supplie

September 2nd, 2014 10:44pm

Thank you, I run into that problem. 

Thanks, 

Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2015 5:37pm

To give the full history - SCVMM actually had Get-Job back in 2008, prior to it making sense as a native cmdlet.

So, beginning with SCVMM 2008 R2 and continuing with SCVMM 2012 all of the SCVMM cmdlets began to be aliased with the 'SC' to designate to define SCVMM cmdlets from system cmdlets.  To prepare for the system cmdlets that they knew were going to conflict.

And, if you are using SCVMM 2012 R2 I thought the aliasing was gone. (I could be wrong on that)

BTW - you would only have this issue where you have the SCVMM Management Console installed.

February 3rd, 2015 6:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics