— pissing into the wind

Started a new job a few weeks ago and now that the new team is all done with training, we’re going through and trying to fix things we’re coming across.  One of the errors that showed up on every single domain controller is 8194 and has to do with Group Policy Registry happening every 5 minutes .  The fix for this is pretty simple.  Look up the ID of the GPO in the event log.  Navigate to c:\programdata\microsoft\group policy\history.  You may have to show hidden folder or system folders if they are not visible.  If you drill into the problem directory, you should come across a Registry.xml file that is 0Kb.  Rename the ID folder to <original name>_old.  The errors should stop.

It seems that for whatever reason or another, that policy gets corrupted and needs to be recreated.

Read More

I’m starting a new job in a couple weeks.  This is the first time I’ve had to deal with counteroffers and the whole thing has left a bittersweet taste in my mouth.  The big takeaway from the experience for me is this:  unless the SOLE reason for looking elsewhere is financial, once you start down the path and give your resignation, there is no going back.  Even then I’d still be wary of accepting a counteroffer from your current employer.  The second you give a hint that you’d leave, you become a liability and a risk.  You’ve demonstrated you are willing and able to walk away from all the investment the business has put into you as an employee.

My reason for leaving was one of wanting more professional development.  The work I’m doing now isn’t very technical in nature, but technical work is what I want to do.  I’m happiest when I’m deep in command lines.  I walked into my boss’s office and let him know my reasons for wanting to leave.  There wasn’t much financial incentive, just the potential for work in things I’m more interested in.  He said he could pull me from my current project and put me on other things that I should find more interesting.  Sounded great to me, so I went to decline the offer from the potential new employer.  They then threw money at the problem and I had to give a lot more weight to the financial aspect of it. 

The next day I went to work prepared to give my boss the bad news.  However, he called me into his office before I went to see him.  He’d been thinking about our conversation and decided that maybe I should take that offer after all.  He didn’t want to have to worry about me being happy all the time.  From his tone and what he was saying, I thought he was going to let me go right then and there.  I let him know the other company countered and I was going to accept their offer then.  We shook hands and I gave a formal 2-week notice letter a day later.  Ultimately, he did make me feel like a cog in a money-making machine, and no, I’m not naïve and I do understand that that’s what a business is supposed to do.

Imagine if the other company did not counteroffer.  I’d have been pretty screwed at that point.  It worked out in my favor this time, but I certainly was not aware of the stakes at that point and what cards each player was holding at the time.

So now I’m in the space in between again.  I don’t really believe the 2-week notice thing anymore and I hate feeling like a lame duck, but here I am.  For now.

 

On another note, I was looking back at frustrated I was last year just trying to get a job and people are bidding on me now.  It’s funny how things ultimately work out.

Read More

for /L %x in (1,1,255) do @ping -n 1 192.168.0.%x -w 100 | find “Reply”

This works right in CLI

Read More

1) Add machine2 as an administrator to machine1

2) Create a batch file with the following 3 lines:

C:\Windows\System32\netsh.exe -r machine1 nps export filename=”c:\npsexport.xml” exportPSK=”YES”
c:\windows\system32\netsh.exe nps import filename=”c:\npsexport.xml”
del /F /Q c:\npsexport.xml

3) Create a scheduled task

Done.

Read More

Dear Symantec,

Your web training for Altiris sucks. It is incredibly boring and not interactive enough. I’d be better off with a PDF to read, but none is provided and so I have been forced to watch slideshows for 10 hours (yes, 10 hours).

I hate you.

Love,

Donovan

Read More

A few weeks ago, I was banging my head on the table trying to get the management port group working on a nic team/etherchannel for a client.  They use Netgear switches, so I was kinda feeling my way through the GUI to make it work.  Everything looked right, but I still couldn’t get the stupid etherchannel working.  Everytime I plugged both nics in on the 2 nic channel, the link would drop.  It would come right back up when I removed one of the links.  I got fed up and blamed the switches.

Normally when you create an etherchannel you also go into the vswitch properties and enable “Route based IP hash” for the load balancing algorithm.  As it turns out, THE MANAGEMENT NETWORK PORT GROUP DOES NOT INHERIT THIS SETTING IN 4.1.  I followed the instructions tonight and the etherchannel works like a champ now (again?) at the client site.

%#$@%#$!!!

Read More

I recently went through the exercise of upgrading my standalone VMware ESXi 4.1 server.  The process is pretty easy.

Grab the vSphere CLI from:  http://www.vmware.com/support/developer/vcli/

Grab the relevant patches.  Make sure you select the correct version of ESX/ESXi.  I facepalmed when I realized I was trying to update using the ESX (not ESXi) packages and nothing was happening.  http://www.vmware.com/patch/download/

Move the downloaded zip file to C:\Program Files (x86)\VMware\VMware vSphere CLI\bin.  In a command prompt run:  C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>vihostupdate.pl -server <server ip> -i –b <updatefile>.zip

Reboot and that’s it.

Read More

Promiscuous mode needs to be enabled on the vSwitch if you are using bridge mode.  Remember that before you facepalm.

Read More

I went to a contract job yesterday and was working for about 3 hours before I needed a bathroom break.  As I finally got in front of a mirror, I noticed my shirt was inside out!  Hah!  I couldn’t do anything but laugh. 

Note to self:  look over yourself prior to stepping out of the house.

Read More

I’m going to call this a successful migration with a couple issues:

1)  I didn’t/forgot to set the block size of the vmfs when I installed ESXi.  The default is 1MB.  This means my virtual disks are limited to 256GB.  Not a big deal for now.  I plan on putting a set of 2TB disks on the controller as well at a later point in time and I’ll remember to set the block size to 8MB then.  As a workaround in the meantime, I’m just using dynamic disks on Windows when I need more than a 256GB disk.

2)  The Perc 6i card got hot.  It never failed or exploded, but it was hot enough to burn my finger the instant I touched the heatsink.  These things were meant to be in servers with airflow going over them, so that’s understandable.  I installed a 40mm chipset cooler to solve the heat issue.  Here are some pics:

Start
perc6i_01

Heatsink removed
perc6i_02

Chipset sans heatsink
perc6i_03

New heatsink mounted
perc6i_04

Side shot.  Notice that I reused the clips from the original heatsink to attach the upgraded one.
perc6i_05

This does take up the PCI slot immediately next to the controller, so keep that in mind if you decide to go this route.

So now I’m on ESXi 4.1 with 2TB of RAID10 storage.  I‘ve added a couple more servers and increased the memory on a couple others where before I was just completely maxed out in terms of memory capacity and couldn’t do anything more.  Huzzah!

Read More

I made a post over at http://ubuntuforums.org/showthread.php?t=1609521&highlight=ventrilo, but here’s a startup script I put together for Ventrilo 3.0.

#!/bin/sh
#
### BEGIN INIT INFO
# Provides:          ventrilo_srv
# Required-Start:    $network $remote_fs $syslog
# Required-Stop:     $network $remote_fs $syslog
# Should-Start:      $named
# Should-Stop:       $named
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Ventrilo version 3.0
### END INIT INFO

NAME=ventrilo_srv
DESC=”Ventrilo 3.0″
DAEMON=/usr/local/ventrilo/ventrilo_srv
PIDFILE=/usr/local/ventrilo/$NAME.pid
DAEMON_ARGS=”-f/usr/local/ventrilo/ventrilo_srv -d”
VENT_USER=ventrilo

do_start() {

        start-stop-daemon –quiet –start \
                –user $VENT_USER \
                –chuid $VENT_USER \
                –pidfile $PIDFILE \
                –exec $DAEMON — $DAEMON_ARGS < /dev/null
        return $?

}

do_stop() {
        start-stop-daemon –stop –quiet \
                –retry=TERM/30/KILL/5 \
                –pidfile $PIDFILE \
                –name $NAME
        rm -f $PIDFILE
        return “$?”
}

case “$1” in
start)
        do_start
        ;;

stop)
        do_stop
        ;;

restart|reload|force-reload)
        do_stop
        sleep 10
        do_start
        ;;

*)
        echo “Usage: $0 start|stop|restart|reload|force-reload”
        exit 1
        ;;

Read More

The migration of my Hyper-V R2 environment to ESXi 4.1 is at the halfway point right now.  At this point, all the systems have been imported into VMware Workstation 7.1 that I have installed on my desktop.  The process didn’t go as smooth as I had hoped.  For starters, I couldn’t use the built-in importer on Workstation.  It just wouldn’t work, and I didn’t want to troubleshoot all day.  I downloaded the standalone converter, but when I tried to P2V remote systems, it would let me select only VMware infrastructure destinations.  So, I ended up installing the converter on all my Windows systems and, by running it locally, you can send it to a network share.  Also, GPT is NOT supported by converter.  This is in the readme, but of course I didn’t read it until I ran into problems.  Pretty much the only way to get around it is to move the data onto another drive that’s been setup as MBR.

Linux systems didn’t go as smoothly either.  The latest version of the converter does not have a *nix version.  Maybe I’m wrong, but I couldn’t find it.  I ended up using Winimage to convert the vhd file to a vmdk.  Then I created a new virtual machine in Workstation 7.1 using roughly the same specs as the Hyper-V machine and then telling it to use the existing vmdk that was just created.  The machine boots up fine, but there’s no nic.  VMware tools has to be installed, then /etc/udev/rules.d/70-persistent-net.rules has to be editted.  All I did was comment out the first line for the tulip driver and change the line for the e1000 to be eth0 instead of eth1.  Reboot and it should be good to go from there.  See this post for more info.

Perc 6i card is installed, 2TB RAID 10 is building now.  I install ESXi 4.1 after that and hopefully import everything in nice and smooth.

Read More