-
-
Notifications
You must be signed in to change notification settings - Fork 809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PS Core adjustments related to Test-Connection #4870
Conversation
Phew! We're finally in the green. Please review at your leisure 😅 |
thanks much, Kirill! @niphlod you around to test with your specific network? |
Woops. Never tested it with websites, gonna look into it. |
i was trying to "impersonate" niph's dual dns environment and couldn't think of anything else 😅 |
also, merry christmas, my friend 🤗🎄 |
I've updated some parts of the code to better build the output object. The difference in ComputerName however is (I think) is a flow in current code logic, since it gets that name right now from the input string unchanged due to being unable to connect via PS remoting. The turbo mode returns proper Computer name from DNS resolution. |
And Merry Christmas! |
thank you both 🙇 |
Let's see how many commands will blow after this one
Type of Change
Purpose
Resolving issues in the commands relying on Test-Connection function in PS6 and a few other issues I discovered while testing them on PS Core
Approach
Resolve-DbaNetworkName was rewritten, reducing the number of calls to DNS.
Test-Connection was replaced by
Commands to test
Resolve-DbaNetworkName
Screenshots
Learning
Test-Connection is a different beast in PS6.0 and has different set of properties
$PSVersionTable.CLRVersion is null in Core.