Skip to main content

Creating an Error Log: Verifying the Log Exists

By
This is day 2 of how to create an error log.

For those of you who have taken one of my PowerShell classes over the years, you know that I like to address all of the issues of a problem.  Our first issue is “does the error log exists?”  If we are going to append to if, we need to make sure that it is already present.  The function below can be added to your code to verify that the log exists.  If not, then it will create the log.  One thing to take note of, this code does note address error logs stored on a remote system.  This is only tested for error logs stored on the local system.

Function Test-ErrorLog
{
[CmdletBinding()]
Param (
    [parameter(Mandatory=$true)]
    [String]
    $Path,

    [parameter(Mandatory=$true)]
    [String]
    $Name
    )

    # Test the path.
    If (!(Test-Path -Path $Path))
    {
        Write-Verbose "Creating the directory $Path"
        New-Item -Path $Path -ItemType Directory
    }

    # Test the file
    If (!(Test-Path -Path "$Path\$Name"))
    {
        Write-Verbose "Creating the file $Name"
        New-Item -Path "$Path\$Name" -ItemType File
    }

<#
.SYNOPSIS
Verifies the existence of an your error log.

.DESCRIPTION
Verifies the existence of an your error log. If no error log is present,
then the file is created.

.PARAMETER Path
The directory location of the error log.

.PARAMETER Name
The name of the error log.

.EXAMPLE
Test-ErrorLog -Path c:\ps\error -Name Error.csv

.NOTES
===============================================================================
== Function: Test-ErrorLog                                                   ==
== Author: Jason A. Yoder                                                    ==
== Company: MCTExpert of Arizona                                             ==
== Date: October 2, 2016                                                     ==
== Copyright: All rights reserved.                                           ==
== Version: 1.0.0.0                                                          ==
== Legal: The user assumes all responsibility and liability for the usage of ==
== this PowerShell code.  MCTExpert of Arizona, Its officers, shareholders,  ==
== owners, and their relatives are not liable for any damages.  As with all  ==
== code, review it and understand it prior to usage.  It is recommended that ==
== this code be fully tested and validated in a test environment prior to    ==
== usage in a production environment.                                        ==
==                                                                           ==
== Does this code make changes: NO                                           ==
===============================================================================
#>

} # END: Function Test-ErrorLog



Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Error icon when creating a GPO Preference drive map

By
You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...
1 comment
Read more