Remington 742 Woodsmaster - repairing broken toe

Ok so recently I bought a new hunting rifle, a Remington 742 Woodsmaster.  I know what you might say or think but I had a budget of only 300 smackers and this was the best thing I found.

Now you can see by the pictures the tip of the toe was broken off, which is the reason I got it for less than $400 or $450.

Now being that I have a few wood working skills, but I am not expert by any means I figured.. yes I can fix this.  The following are progressive shots of the work I've done thus far.

Note that I assumed the stock was walnut.. I was wrong and now I'm leaning more towards maple.  However I did source walnut and used it in the repair.

I was able to source the replacement butt plate from https://www.gunpartscorp.com/ and being a cheap skate I did not want to pay $8 for the white plastic trim piece.  So I fashioned one out of white plastic gutter down spout.

And here's the finale pics.. I wound up putting 4 coats of Minwax Antique Oil Finish, which is a 50/50 mix of boiled linseed and varnish (basically)  Oh yeah and I let each coat dry for about 5 minutes then buffed out with a clean rag and allowed to sit for about 24 hours.

*Thinking about putting on a couple more coats once it warms up outside.

And finally the before and after overall:

Windows 7 - Cannot connect to windows event notification service

Ran into this little gem of an error today on a freshly installed (via ISO) Windows 7 64 Enterprise.

I first tried installing some AV becasue I had found that someone resolved their issue by removing and reinstalling Microsoft Endpoint Protection.. did not help.

Next I found this guy: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_7/Q_28408338.html

So I tried installing the Hotfix http://support.microsoft.com/kb/2590550/en-us?fr=1

And it worked.. the hotfix description did not really give me a feeling that it'd solve this issue but it actually did.  Cheers.

Powershell script to create a new domain user object

Ok so since we've migrated from on premise Exchange 2010 to Office365 our old way of creating new users had to be re-worked.  Now we're forced to manually input the values for proxyaddresses or else they are unable to have a mailbox license assigned to them.

So I just completed a nice script that among other things, does exactly that.  It's been sanitized but here's it is in all it's glory.

#Create-NewADUserO365.ps1
#3/3/15 Benjamin Hart, Unified Brands, Inc
#Created with Powershell ISE
#This powershell script will create a domain user object using a format of lastname, firstname, a SAM of first initial + last name
#It will also populate displayname, a default password, office and both proxyaddresses, the primary as used in your org and the 
#Dover required O365 one.  It will also verify the primary proxy address is not already used.
#With set-aduser you can alter almost any attribute of the user.

$theOU = read-host "Enter the OU name"
$Surname = read-Host "Enter the surname"
$GivenName = read-host "Enter first name"
$DisplayName = "$Surname, $GivenName"
$Password = "December1"
$name = $GivenName.substring(0,1)+$Surname
$proxyaddress = read-host "Enter the email address in full"


Import-Module activedirectory
import-module servermanager



#Edit the SearchBase to match your organization
$myOU = Get-AdOrganizationalUnit -Filter "Name -eq '$theOU'" -Searchbase 'OU=People,DC=domain,DC=org'


while (Get-ADuser  -filter * -Properties ProxyAddresses|?{$_.proxyaddresses -contains $proxyaddress})
{
  $proxyaddress = read-host "$proxyaddress is already in use, please try another one"
}
Write-Host "$proxyaddress is not used yet."


#Edit the below to match your domain(s)
$DomainProxyAddress = "$("smtp:")$($givenname.substring(0,1))$surname-$("domain")-$("net")@domain.mail.onmicrosoft.com"
$Description = read-host "Enter persons description"
$jobtitle = read-host "Enter the Job Title"

#Edit the below to match your locations
$office = read-host "Enter the user's location, Michigan, Mississippi, Georgia, Oklahoma or Remote"

#Edit your locations if you choose to use this part
Switch ($Office)  {
    "Michigan" {
        $Street = "001 Any Street."
        $City = "Weidman"
        $State = "Michigan"
        $Zip = "48898"
        $scriptpath = "\\domain\netlogon\milogin1.bat"
}
    "Mississippi"  {
        $Street = "789 Any Street."
        $City = "Jackson"
        $State = "Mississippi"
        $Zip = "39272"
        $scriptpath = "\\domain\netlogon\adlogin.bat"
        }
    "Oklahoma"  {
        $Street = "456 Any Street"
        $City = "Pryor"
        $State = "Oklahoma"
        $Zip = "74361"
        $scriptpath = "\\domain\netlogon\oklogin.bat"
        }
    "Georgia"  {
        $Street = "123 Any Street"
        $City = "Conyers"
        $State = "Georgia"
        $Zip = "30013"
}
}

$department = read-host "Enter the users Department"

New-ADUser -path $myOU -samaccountname $name -name $displayname -DisplayName $DisplayName -Surname $Surname -givenname $givenname -AccountPassword (ConvertTo-SecureString $Password -AsPlainText -force) -enabled:$false
set-aduser $name -emailaddress $proxyaddress -Description $Description -Title $jobtitle -Office $office -StreetAddress $Street -city $city -state $state -PostalCode $zip -UserPrincipalName $proxyaddress -ScriptPath $scriptpath -Department $department -Company "My Companyc" -Country "US"

set-aduser $name -add @{proxyaddresses = "$("SMTP:")$proxyaddress"}
set-aduser $name -add @{ProxyAddresses = "$doverproxyaddress"}

 
get-aduser $name