Comments on: OpsMgr Command Shell Performance

By: Cory Delamarter

Cory Delamarter — Wed, 27 Jan 2010 08:42:07 +0000

Just to close the loop on this Lincoln found a great way to work around this if you are using PowerShell v2 to run the command shell in. He posted those details to http://blogs.technet.com/momteam/archive/2009/12/09/slow-tab-expansion-in-ops-mgr-powershell-v2-console.aspx.

In the next release we’re looking at doing away with the provider altogether so this problem should go away moving forward.

Thanks again for bringing this to our attention!

By: jpavleck

jpavleck — Mon, 01 Jun 2009 05:09:06 +0000

Yup, I was doing it that way, typing Get- and that was taking forever and a day to complete. Seems like it’s pretty dependent on the size of the network. I’d been talking to people about it for awhile to make sure it wasn’t just me before I bugged it.

By: Daniele Muscetta

Daniele Muscetta — Thu, 28 May 2009 12:41:07 +0000

your comment form is stripping out brachets, I should have imagined it…
what I really wrote was something like: if you type GET and hit TAB immediately, it takes ages….
if you type GET- and then hit TAB…
hope this makes it clearer

By: Daniele Muscetta

Daniele Muscetta — Thu, 28 May 2009 12:38:41 +0000

if what you are trying to auto-complete a cmdlet name, you need to reach the “-” dash sign.

So if you type GET -THIS will take ages, because yes, it is searching for a file on the current drive FIRST – which in ops mgr is an object, since the drive is a provider… and it is a SQL query at the end of the chain.

But if you type Get- <<– see? you actually include the “-” that separates VERB from NOUN in a cmdlet, THEN it is fast, as it will search in cmdlets FIRST.

Try it out.