wgv-zbonham

$context = New-AzureStorageContext -storageaccountname "elsadevusaia001" -storageaccountkey "{hidden}" -Endpoint "core.usgovcloudapi.net"

wgv-zbonham

using System;
using System.Diagnostics;
using System.Text;

namespace TickTickBoom
{
    
    public class AzureStorageTraceListener : TraceListener
    {
        public AzureStorageTraceListener()

wgv-zbonham

<#
    We only get Azure commercial and Azure China by default but this seems to work for Azure Gov by specifying the -Endpoint parameter

#>
$storageKey = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("My really long key that came from somewhere else and why isn't there a get-base64string cmdlet already??"))
$context = New-AzureStorageContext -StorageAccountName "Testing" -StorageAccountKey $storageKey -Endpoint "core.usgovcloudapp.net"

$context

wgv-zbonham

using System;
using System.Web.Http;

namespace WgvPlayback.Controllers
{
    [RoutePrefix("/api/sharelinks")]
    public class ShareLinksController : ApiController
    {
        public IHttpActionResult Get(Guid id)
        {

wgv-zbonham

This configuration file does not ship with the version of openssl I pulled for some reason. Found a default openssl.cnf

1. generate an RSA private key

• openssl genrsa -des3 -passout pass:x -out server.pass.key 2048

2. write out the RSA private key

• openssl rsa -passin pass:x -in server.pass.key -out server.key

3. create the certificate signing request (CSR) for the server or common name;

• openssl req -new -key server.key -out server.csr -config openssl.cnf -subj "/C=US/ST=TX/L=Allen/O=WatchGuard Video/CN=localhost"

4. generate the x509 certificate from the request (this certificate will work in Root, but not WebHosting because no private key yet); this is normally handled by certificate CA

• openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

wgv-zbonham

public class Trash : IDisposable 
{
	public void Dispose() 
	{
		Console.WriteLine ("Goodbye, cruel world.");
	}
		
}
	

wgv-zbonham

# running from same working directory as WatchGuard assemblies
#

$assembly = (Get-Item WatchGuard.Services.Contracts.dll).FullName
[system.reflection.assembly]::LoadFrom($assembly)

[Enum]::GetValues([WatchGuard.Services.AvduState]) | %{ Write-Host ( [int]$_):$_ }

# produces
# 0 :Unknown

wgv-zbonham

param([int]$databaseVersion)

<#
	.SYNOPSIS
		Converts Database Version [int] to human readable string.
		
	.DESCRIPTION
		Converts Database Version [int] to human readable string.
		
		build = value & 0x0fff

wgv-zbonham

The attached counter set is just the ‘System Performance’ template with ‘Logical Disk’ counters added. The sample interval has been changed to 15 seconds. The counters are collected at c:\perflogs\admin\EL4. You need to be running under an account that is in the Administrator role for servers we are publishing counter sets to.

The perfmon template, el4perf.xml, is assumed to be in the current working directory.

From an administrator PowerShell command prompt:

To publish this counter set to a server:

logman import –n EL4 –xml .\el4perf.xml –s SERVERNAME

wgv-zbonham

use WGEvidenceLibrary
go

/*** ACTIONS BEING PERFORMED IN ORDER
	1.  REBUILD INDEXES
	2.  TRUNCATED LOG FILE
	3.  SHRINK DATABASE
	4.  UPDATE STATISTICS
	5.  UPDATE AUTOGROWTH SETTINGS