Dirk DBremen

Export chrome bookmarks

This is a script to export bookmarks from the web browser Google Chrome to a users home drive in a Windows environment with clients and domain controllers. Most of the script comes from this article

Instruction

Double-click on the bat-file.
Go the home drive on the users new computer.
Double-click on openChromeFolder.bat which will take you to the chrome directory on that machiene.
Copy the file Bookmarks to the newly opened window.

PowerShell execute command with arguments safely

In my opinion this is the best way for executing external commands from PowerShell with arguments in a safe manner - via the use of an array to hold the arguments.

Consider this one a PowerShell gem to keep in the toolbox.

Note

The example below makes use of EchoArgs.exe - a small utility that simply echoes back arguments passed to it. Utility is part of the PowerShell Community Extensions, or the exe alone can be downloaded at https://ss64.com/ps/EchoArgs.exe.

Example

It "types" the contents of the clipboard.

Why can't you just paste the contents you ask? Sometimes pasting just doesn't work.

One example is in system password fields on OSX.
Sometimes you're working in a VM and the clipboard isn't shared.
Other times you're working via Remote Desktop and again, the clipboard doesn't work in password boxes such as the system login prompts.
Connected via RDP and clipboard sharing is disabled and so is mounting of local drives. If the system doesn't have internet access there's no easy way to get things like payloads or Powershell scripts onto it... until now.

Windows

The Windows version is written in AutoHotKey and easily compiles to an executable. It's a single line script that maps Ctrl-Shift-V to type the clipboard.

	# Example of how to use Invoke-RestMethod with headers and cookies

	$Credential = Get-Credential # Your credential goes here

	[System.Uri]$Uri = "http://server01.example.com/api/pizza/1" # Add the Uri
	$ContentType = "application/json" # Add the content type
	$Method = 'PUT' # Add the method type
	$Body = '{ "id" = 1, "Name" = "Peperoni" }' # Add the body for the request

	$Cookie = New-Object System.Net.Cookie

	Function New-PSWebServer {

	<#
	.Synopsis
	Creates a web server that will invoke PowerShell code based on routes being asked for by the client.

	.Description
	New-PSWebServer creates a web server. The web server is composed of a schema that defines the client's requests to routes where PowerShell code is executed.

	Under the covers, New-PSWebServer uses the HTTPListener .NET class to execute powershell code as requested, retrieves the results and sends data back through the httplistener web server framework.

	function new-PowershellWebGUI ($HTMLRaw,$Title,$Runspace) {

	[xml]$xaml = @"
	<Window
	xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
	Title="$Title" Height="500" Width="700">
	<Grid>
	<DockPanel>
	<WebBrowser Name="WebBrowser" DockPanel.Dock="Top" Margin="30">
	</WebBrowser>

	function Show-HTML ([string]$HTML)
	{

	[void][System.Reflection.Assembly]::LoadWithPartialName('presentationframework')
	[xml]$XAML = @'
	<Window
	xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
	xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
	Title="PowerShell HTML GUI" WindowStartupLocation="CenterScreen">
	<WebBrowser Name="WebBrowser"></WebBrowser>

	Function Show-Diff {

	param([String[]]$OldString,[String[]]$NewString)

	$WebPage = @"
	<!DOCTYPE HTML>
	<html>
	<head>
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<meta http-equiv="X-UA-Compatible" content="IE=edge" />

	# It might work in 4, but I'm not testing there. Lower you'll have to tweak code
	#requires -Version 5.0
	param(
	# Your Live ID for MSDN login
	[Parameter(Mandatory)]
	[PSCredential]
	[System.Management.Automation.CredentialAttribute()]
	$Credential,

	# Pick a browser to use. Defaults to Firefox (which doesn't seem to require an external Driver file)

	<Configuration>
	<ViewDefinitions>
	<View>
	<Name>MatchInfo</Name>
	<ViewSelectedBy>
	<TypeName>Microsoft.PowerShell.Commands.MatchInfo</TypeName>
	</ViewSelectedBy>
	<CustomControl>
	<CustomEntries>
	<CustomEntry>