Shawn Melton

@potatoqualitee @andreasjordan I can confirm this issue still exists even in the new code changes coming in 2.0 release. The issue that is happening is once a credential is provided...

All user scope won't fix this because I'm using the module from a saved path (c:\git\dbatools\dbatools.psd1). Recall I'm using the development branch of GitHub (local development) so the module exist...

It is only the core library module that has to be installed in all user scope, follow now. That is a pretty big breaking change for those users that don't...

Not sure remoting plays into here because there is no session created. I'm local on my machine doing this and the impersonation is a thread within pwsh running under that...

We may need to separate this to another issue because there is a difference between PS Remoting and the issue with credential from our Connect function. User awareness is responsible...

If a user wants to run the module in Windows PowerShell from PS 7 on their local machine they can `Import-Module ... -UseWindowsPowerShell`. That will create a runspace in PS7...

I'm using 7.3.1 and whether I'm passing in a credential or creating a connection with credential I don't see the issue occurring with PS Remoting. A credential being passed to...

You are either getting the one you want or all of them with Get verb. Find is where we allow wildcard filters.

I would be fine with a `Find` command. The other difference between Find and Get is object size returned. Find is generally a partial object with smaller list of properties...

Adjust the code to dynamically generate the `PSCustomObject` instead of hard coding all the properties returned by the query object.