Search results for '(app:forums OR groupid:24)' matching tag 'Test-Connection'

Bug? with Get-ChildItem, Test-Connection, and Junction Points

rpscripter — Thu, 05 Jul 2012 05:00:00 GMT

SYNOPSIS
When I run "gci $somePath -rec -for ", where the path contains junction points, and then "test-connection $someComputer", and finally the first command again, I get different results.

DESCRIPTION
I was trying to measure the total folder sizes of user profile folders on remote machines, when I realized that I was getting different numbers. Before test-connection, the gci command yields errors when trying to access the junction points - those shortcuts introduced in Vista to provide backward-compatibility to "Documents and Settings", "All Users", "My Documents\My Pictures", etc.

However, after I run any test-connection command, and then run the same gci command, the cmdlet is somehow able to "resolve" those junction points and return the items beyond them. And so the second gci command returns more items (via measure-object) but doesn't give errors. Worse, when the gci command is run on an "Application Data" junction point, it loops so that I get nine or ten duplicates.

For example, before test-connection, get-childitem doesn't return "c:\users\public\documents\My Pictures" but gives an error and does return "c:\users\public\pictures". After test-connection, it does return the contents of "c:\users\public\documents\My Pictures" as well as "c:\users\public\pictures", and whatever is in Pictures is returned twice and thus double-counted by Measure-Object.

PARAMETERS
This bug occurs in the ISE; it does not occur in the console unless run with -STA.
This bug only occurs when ISE (or powershell -STA) is run As Administrator.
This bug occurs in both V2 and V3.
Neither the parameters nor the results of Test-Connection seem to make a difference, as long as it can run once.
It doesn't matter whether the gci path is a local or remote path.
It doesn't matter whether the commands are run from a script or one-by-one.
I've tested Windows 7, 2008 R2, and 2012 and gotten this bug.

EXAMPLE

Open PS ISE As Administrator.
Run "Get-ChildItem C:\users\public -recurse -force | measure-object length -sum"
You should get three errors about some paths being access denied.
Run Test-Connection with any parameters.
Run the same gci / measure command again.
Compare the results of gci before and after Test-connection. In my cases, the count and sum increased, and the errors did not occur.

NOTES
I just wanted to see if anyone else can get this bug. If enough people find it, then I will contact Microsoft Connect.

Question: replace Ping with Test-Connection

rpscripter — Tue, 12 Jun 2012 05:00:00 GMT

I see that Test-Connection is superior in almost every way to Ping, and yet there is one useful thing that I cannot do yet:

When I ping a name, I see the fully-qualified name listed, but when I ping an name that is resolved by WINS instead of DNS, I see just the name, lacking the domain suffix, and I instantly know that it is missing a DNS entry. However, I can find no distinction with test-connection between these two cases.

I am trying to find all cases of a name being resolved not by DNS but by WINS so that they may be corrected. I think this is beyond test-connection, but is there something in .NET to help?

Monitor & Log Mapped drive/Network shares

justaguy — Wed, 06 Jun 2012 05:00:00 GMT

We’ve been asked to monitor if a network/mapped drive is available. I did find I can see drive data using the gwmi & filter for the “DriveType”

Gwmi Win32_LogicalDisk -filter "DriveType = 4"

The output is:

DeviceID : T:

DriveType : 4

ProviderName : \\%host%\%sharename%

FreeSpace : 64022515712

Size : 116502863872

VolumeName : Enterprise

That’s great, but integrating it with either of our monitoring tools is another challenge. So I thought if I could get the output to write to an application/event log I could use the log to capture the output, and schedule the script to run say every 5 minutes. I have this:

$NetDisk = Gwmi Win32_LogicalDisk -filter "DriveType = 4"

Write-Eventlog -computername LocalHost -logname 'Windows PowerShell' `

-Category 3 -source PowerShell -eventID 600 -EntryType Information `

-message "$NetDisk is ONLINE."

If it's disconnected it should be an error. The output is readable but I’d like to make it more readable.

Event Type: Information

Event Source: PowerShell

Event Category: Engine Health

Event ID: 600

Date: 6/5/2012

Time: 11:17:57 AM

User: N/A

Computer: %HOST%

Description:

Provider "\\%host%\root\cimv2:Win32_LogicalDisk.DeviceID="T:" is ONLINE." is %2.

(from the event viewer on the %host%

Provider "\\%HOST%\root\cimv2:Win32_LogicalDisk.DeviceID="T:" is ONLINE." is %2.

Details:

What I would really like is to be able to filter before I write the log entry based on DeviceID & /or ProviderName (without the roo\cimv2\etc), for example:

Provider "\\%HOST%.DeviceID="T:" is ONLINE." is %2.

Details:

Not sure that is even possible. Any ideas are appreciated.

Re: test-connection

Chris Kirk — Wed, 08 Feb 2012 06:00:00 GMT

Hi Don,

I tried your solution and recevied one error. I assume it is last pass with no computer name:

Get-Content names.txt | Foreach {if(-not(Test-Connection -ComputerName $_ -Quiet)){Write-Host " $_ is down" -ForegroundColor RED}}

cwdp-nine is down

Test-Connection : Cannot validate argument on parameter 'ComputerName'. The argument is null or empty. Supply an argument that is not null or empty and then try the command again.
At line:1 char:71
+ Get-Content names.txt | Foreach {if(-not(Test-Connection -ComputerName <<<< $_ -Quiet)){Write-Host " $_ is down" -ForegroundColor RED}}
+ CategoryInfo : InvalidData: (:) [Test-Connection], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.TestConnectionCommand

Any suggestions?

Chris Kirk

how to establish and enter an implicit remote session using runspace in powershell

manishjha — Wed, 18 Jan 2012 06:00:00 GMT

Hi,

I am trying to establish an implicit session with a remote host from my machine from a C# code. I am using runspace API for that. the code snippet is provided below

Runspace runspace = RunspaceFactory.CreateRunspace();
                runspace.Open();

                //constructing the vmname parameter here
                vmname = useralias + DateTime.Now.ToString();

                Pipeline pipeline = runspace.CreatePipeline();
                string scripttext = "$secpasswd = ConvertTo-SecureString '222_bbbb' -AsPlainText –Force";
                string scripttext1 = "$mycreds = New-object -typename System.Management.Automation.PSCredential('TS-TEST-09\\Administrator',$secpasswd)";
                string scripttext2 = "$s = New-PSSession -ComputerName TS-TEST-09 -Credential $mycreds";
                //not accepting session string here, only computername acceptable
                string scripttext3 = "Enter-PSSession -Session $s";

                //put invoke command here instead of directly calling out the file execution
                //Command cmd = new Command(@"C:\mypath\helper.ps1", true);
                //cmd.Parameters.Add("local_useralias", useralias);
                //cmd.Parameters.Add("local_vmname", vmname);
                //cmd.Parameters.Add("local_datastore", datastoredropdown.Text.ToString());
                //cmd.Parameters.Add("local_architecture", architecturedropdown.Text.ToString());

                pipeline.Commands.AddScript(scripttext);
                pipeline.Commands.AddScript(scripttext1);
                pipeline.Commands.AddScript(scripttext2);
                pipeline.Commands.AddScript(scripttext3);
                //pipeline.Commands.Add(cmd);

                Collection<PSObject> results = pipeline.Invoke();


                runspace.Close();

this code is expected to enter into an implicit session with machine TS-TEST-09 and invoke the script helper.ps1 existing on that machine(that part is commented out in the code currently).

now the problem is that i can't enter into the session $s using -Session parameter(highlighted) however i can enter into it using -Computername parameter.

In later case, however, the code tries to access helper.ps1 from the local host and not on the remote server.

Is there a method to accomplish this task?

any help will be much appreciated.

Thanks,

Manish

test-connection

patg — Tue, 10 Jan 2012 06:00:00 GMT

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

don - in your Month of Lunches book chapter 9.8 you have ideas for on your own and ask:

Or use Test-Connection to ping several

computers, and only show the results from computers that did not respond

I tried several things then did what I do best and stole a cmd and came up with this (I am sure you know where I stole it from…J)

get-content c:\hold\machines.txt | foreach { if (test-connection $_ -quiet) { $null } else {write-host "$_ is down" -foregroundcolor RED}}

Now I get the desired results but my question is : how does it know if it’s up or down? All I did was run a test-connection and then a write-host. I didn’t call for anything like statuscode or timeout and say if statuscode is X then …….

Also if I ping a computer (who is in dns but not up) I get request timed out…..but test-connection gives me:

Test-Connection : Testing connection to computer 'XXXX' failed: The requested name is valid, but no data of the requested type was found At line:1 char:16 + test-connection <<<< XXXX + CategoryInfo : ResourceUnavailable: (XXXX:String) [Test-Connection], PingException + FullyQualifiedErrorId : TestConnectionException,Microsoft.PowerShell.Commands.TestConnectionCommand

Test-Connection timestamp

Itchy — Thu, 10 Nov 2011 06:00:00 GMT

I pieced together this powershell command:

test-connection dwdmadwsa137 -count 2 -delay 60 | select __SERVER, Address, ProtocolAddress, ResponseTime | out-file c:\temp\test-connection.txt -append

It produces this outpout:

__SERVER          Address       ProtocolAddress            ResponseTime
--------           -------         ---------------                  ------------
ITCHY-P1          wsa137        111.111.111.148                       1
ITCHY-P1          wsa137        111.111.111.148                       1

What I need to do is add a time stamp.

TimeStamp                    __SERVER   Address    ProtocolAddress    ResponseTime
--------                          -------        --------    ------------
11/10/2011 3:22:27 PM   ITCHY-P1     wsa137    111.111.111.148           1
11/10/2011 3:22:27 PM   ITCHY-P1     wsa137    111.111.111.148           1

How can I do this in the powershell pipeline?

Thanks,
Itchy

Re: Test-Connection with Specified timeout

PepeManolo — Thu, 25 Aug 2011 05:00:00 GMT

Mr. RSiddaway,

Would you know if the SourceRoute property in the Win32_PingStatus class would do the trick for specifying which NIC I want to utilize to send the Ping packet?

As I mentioned before, the idea is to send a ping (with short timeout) by one NIC and then send another by the other NIC. This works with Test-Connection cmdlet, but the timeout is too long (+/- 45 seconds).

Thanks in advance

Test-Connection with Specified timeout

PepeManolo — Mon, 22 Aug 2011 05:00:00 GMT

I am writing a short script which pings a list of external servers using two NICs on different Networks. The idea is to verify both networks reach the internet.

The commandlet Test-Connection "$IP" -Source "$NIC" works correctly for the desired NIC. However, the default timeout takes too long when the destination is unreachable.

The documentation indicates -TimeToLive <timeout> as the argument to use but to no avail.

My understanding is that Test-Connection is a wraper for Win32_PingStatus, where TTL has the purpose we have know all this time as the max hops to jump.

Is there an undocumented argument for Test-Connection which would allow me to specify the max timeout to wait for a reply?

Thanks in advance

Re: how to check active server in the custom OU using powershell ?

Aleksandar — Tue, 28 Sep 2010 05:00:00 GMT

As Richard said, you just need to add:

$OnlineServers = @()

before the line:

Get-QADComputer -SearchRoot 'domain.com/Active Servers' -OSName "Windows*Server*" | %{

If you use PowerShell V2 which has a nice little cmdlet Test-Connection, you can see the real power of PowerShell pipeline and run a following one-liner:

Get-QADComputer -SearchRoot 'domain.com/Active Servers' -OSName "Windows*Server*" | ? {Test-Connection $_ -quiet} | % {$_.name + " is online"}