• VMware Fusion 4 – Did they move vmrun?

    Did they move vmrun in VMware Fusion 4?

    In version 4, I find it here: “/Applications/VMware Fusion.app/Contents/Library/”

    But this documentation says that the command should be in “/Library/Application Support/VMware Fusion”, but I found it here”/Applications/VMware\ Fusion.app/Contents/Library/vmrun”

    I don’t see anything in the release notes.

    Anyone?

     


  • PowerShell wrapper for creating a new distribution group

    Unknown to me, in Exchange 2010 when you create a new distribution group in EMC, by default, the group will not receive email from external recipients – the setting “Require that senders are authenticated” is checked. We use distribution groups to communicate with clients, so unauthenticated senders need to email these groups.  This setting is on the Mail Flow Setting – Message Delivery restrictions page.  I wrote a simple wrapper script to create a new distribution group and turn off the “Require that senders are authenticated” setting:

    function JBMURPHY-EXCHANGE-NewDistributionGroup {
    Param([parameter(Mandatory = $true)]$GroupName)
    Write-host "Creating group named $GroupName"
    new-DistributionGroup -Name $GroupName -OrganizationalUnit 'site.name/OUName' -SamAccountName $GroupName -Alias $GroupName
    Set-DistributionGroup $GroupName -RequireSenderAuthenticationEnabled $false
    write-host "The $GroupName distribution group has been created."
    }
    

    Simple one. I know.


  • PowerShell wrapper scripts for Exchange 2010 – first step: make a connection

    As I talked about in this previous post, I like to write wrapper scripts that collect input and pass it along to the actual provided functions. I call these wrapper scripts because they are not really doing anything ground breaking, they are just a series of conditionals and commands that I put together, with a common naming convention. Then, all we have to do is tab completion through the scripts that I have written.

    I wanted to do the same for creating new distribution groups in Exchange 2010, but first ,I needed to make  the Exchange 2010 PowerShell functions available on our local machines. I wrote the following function that starts a PSSession on the exchange server. This function will be called at the beginning of every Exchange wrapper script, guaranteeing that we have a connection to the Exchange PowerShell functions.

    Here is that function:

    Function JBMURPHY-EXCHANGE-StartPSSESSION {
    if(! (Get-PSSession | Where-Object { $_.ComputerName -like "servername.company.com" })){
    Write-Host "Createing PSSession to SVNYEXCH01.SARDVERB.LOCAL" -ForegroundColor Green
    Import-PSSession (New-PSSession -Configurationname Microsoft.Exchange –ConnectionUri http://servername.company.com/powershell) | out-null
    }
    }
    

  • PowerShell script to email users if password expires soon, and send a summary to IT

    I wanted to expand on my previous script: powershell-to-list-all-users-and-when-their-password-expires, so that it would send the user an email if their password was going to expire soon. Additionally I wanted to send a summary to our IT staff of accounts that were going to expire soon.

    Here is that script:

    $maxdays=(Get-ADDefaultDomainPasswordPolicy).MaxPasswordAge.TotalDays
    $summarybody="Name `t ExpireDate `t DaysToExpire `n"
    
    (Get-ADUser -filter {(Description -notlike "IfYouWantToExclude*") -and (Enabled -eq "True") -and (PasswordNeverExpires -eq "False")} -properties *) | Sort-Object pwdLastSet |
    foreach-object {
    
    $lastset=Get-Date([System.DateTime]::FromFileTimeUtc($_.pwdLastSet))
    $expires=$lastset.AddDays($maxdays).ToShortDateString()
    $daystoexpire=[math]::round((New-TimeSpan -Start $(Get-Date) -End $expires).TotalDays)
    $samname=$_.samaccountname
    $firstname=$_.GivenName
    if ($daystoexpire -le 3){
    	$ThereAreExpiring=$true
    
    	$emailFrom = "[email protected]"
    	$emailTo = "[email protected]"
    	$subject = "$firstname, your password expires in $daystoexpire day(s)"
    	$body = "$firstname,
    	Your password expires in $daystoexpire day(s).
    
    	Please press Ctrl + Alt + Del -> Change password"
    
    	$smtpServer = "smtp.yourdomain.com"
    	$smtp = new-object Net.Mail.SmtpClient($smtpServer)
    	$smtp.Send($emailFrom, $emailTo, $subject, $body)
    
    	$summarybody += "$samname `t $expires `t $daystoexpire `n"
    }
    }
    if ($ThereAreExpiring) {
    $emailFrom = "[email protected]"
    $emailTo = "[email protected]"
    $subject = "Expiring passwords"
    $body = $summarybody
    $smtpServer = "smtp.yourdomain.com"
    $smtp = new-object Net.Mail.SmtpClient($smtpServer)
    $smtp.Send($emailFrom, $emailTo, $subject, $body)
    }
    

  • Quick bash script to change .htpasswd passwords across a server

    I wanted to change passwords for a users that is in all of our htpasswds. Here is a quick bash find script to do that:

    for PATH in $(find / -name .htpasswd); do htpasswd -b $PATH username NewPassword; done


  • Cisco ASA hacking – Getting started

    My wife (Team Murphy’s CFO) allowed me to purchase a Cisco ASA 5505 for home. We use ASAs at work, and I am interested in how we can leverage these devices to their fullest. I am new to Cisco and to their IOS (the original IOS). I was impressed, the 5505 was easy to setup, I just swapped out my existing DDWRT and it worked out of the box. The 5505 had DHCP running on the internal interface, and NAT configured correctly.

    Next I wanted to change the default network to use a different range. That proved more difficult when trying to do it over a network connection. I know I should be using the serial connection, but I did not want to sit in my coat closet to make the change. I also knew I would be hacking my config, and I wanted a scenario where I could early reset to the defaults. Every time I tried to reset to the defaults, the interface would hang because i was trying to do it over the network (as expected).

    I found this link in the ASA documentation that described the default config for an ASA. I also found the environmental variable CONFIG_FILE. My thinking was, I could use the default config listed in the ASA documentation and save it to a file on the flash. If I wanted to return to the defaults, I could just change the  CONFIG_FILE environmental to point to that default config file on disk0:, and I would be back up and running in “factory defaults”.

    I took it a step further and I added the following to my “jbmurphy_factory_defaults”:

    ssh 192.168.XX.0 255.255.255.0 inside
    ssh timeout 5
    aaa authentication ssh console LOCAL
    ssh scopy enable
    

    These 4 lines enable ssh access to the ASA and allow me to scp my config file to disk0. Now, when I am working on a new config, I can scp it from my filesystem to the onboard storage, and issue a reboot.

    That is my workflow so far. Thoughts?


  • VMware ESX suspended machine won’t resume because of missing hardware

    We recently had some downtime to physically move a rack for our server room expansion. One of the servers we were shutting down was a VMware ESX host. When I tried to resume the machine, I received an error saying “Module DevicePowerOn power on failed. Unable to open the SCSI device . . .”

    We had removed a daisy chained tape device, and I forgot! I wanted to remove it from the hardware profile, but I couldn’t because the machine was suspended.

    So  . . . , I can’t power on, I can’t power down, and I can’t edit the hardware profile because the machine is suspended. Crap.

    I sshed into the ESX box and tried: vmware-cmd stop hard. I received the error : “The attempted operation cannot be performed in the current state . . .”.

    Crap.

    The only way I could get the machine powered on, was to comment out the missing scsi device in the VM’s vmx file. After that, I could power on the machine no problem. Hope that may help someone!


  • PowerShell Active Directory wrapper scripts.

    In my PowerShell profile I have a routine the sources all the *.ps1 files in a folder. One of these .ps1 files contains Active Directory “wrapper” functions. I call them “wrapper” functions because they simplify the parameters needed to return data in a format we want. The idea is that I can write a series of “wrapper” scripts, alias them, and then everyone on our team can use the same script. All a user has to do is type “jbmurphy” (if that is the script starts with) and hit TAB  and the command completion will cycle through all the wrapper scripts. Some of the scripts are not much different than the actual “wrapped” script, but there usually is simplified formatting to just dump the needed info. Here are two wrapper scripts to interact with ActiveDirectory (AD).

    First one finds users in a group:

    function jbmurphy-GetGroupMembers {
        Param($GroupName)
        return Get-ADGroupMember $GroupName | ft -hidetableheaders name
    }
    

    Second one finds the groups a users is a member of:

    function jbmurphy-AD-GetGroupMembership {
    Param($UserName)
       $user=Get-ADUser -properties memberof $UserName
       return $user.MemberOf -replace '^cn=([^,]+).+$','$1'
    }