bytesizedalex / get-supportinfo Goto Github PK

Add check for version of Windows - function is only supported on Windows 10.

A test should be run to determine the version of Windows and either throw a terminating error or at the least a warning indicating the function may not run as expected/at all.

Create extended help documentation/wiki detailing purpose of each command and generated output.

Create a WPF graphical application which makes the necessary calls to run the PowerShell function.

This executable can be run by end users, negating the need to run commands in a PowerShell prompt which can be challenging for users.

The Get-SupportInfo function should exist on the endpoint so that the WPF application simple has to invoke it. This method of invocation has been requested by colleagues at my current employer and I do see the value in this request.

Feedback and suggestions are welcomed.

Add a check for available disk space to ensure function run will not consume remaining disk space.

It is highly unlikely the function would result in a drive being filled due to the very small data capture. That being said, it may be beneficial to add a check so that future code changes which may increase required space do not cause problems.

It can be beneficial to know if a full memory dump (%systemroot%\memory.dmp) and minidump files (%systemroot%\minidump) exist on an endpoint. These can indicate crashes which may relate to an issue under investigation or related faults.

Due to the potential size of a memory.dmp file it is probably not wise to add it to the support archive. Flagging it's existence via a console output or creation of a proxy file in the archive may be appropriate.

Minidump files are typically small in size and could be considered for inclusion though it may be better to add a proxy file to the archive indicating the number of minidump files and their creation time.

Update function to include Write-Progress functionality.

Add -IncludeInvocationHeader to PowerShell Transcription Logging

Add dxdiag.exe output - choice of XML/TXT or both depending on requirements for later ingest

Add code to PowerShell gallery for easier distribution

Is your feature request related to a problem? Please describe.
Add netstat or equivalent output to assist network troubleshooting and security. Such output will provide details on open TCP/UDP ports and current connections.

Describe the solution you'd like
Output TCP/UDP sockets to CSV as part of current capture process.

Native PowerShell cmdlets can be used -

Get-NetTCPConnection
Get-NetUDPEndpoint

Describe alternatives you've considered
While netstat would work the preference is to use native PowerShell cmdlets where possible.

Additional context
n/a

Sysmon (https://docs.microsoft.com/en-us/sysinternals/downloads/sysmon) is commonly used by many enterprise environments.

Test for the existence of a Sysmon event log and export if found.