Windows 8 Enterprise activation problem

Microsoft released the final version of Windows 8 to developers through MSDN and or Technet subscriptions last week.  So I quickly logged into Technet and downloaded Windows 8 Enterprise.
I’ve been using the Consumer Preview version since they released it and was anxious for the final version.  Everything installed as expected and was working great.

Until I went to activate Windows that is.  It wouldn’t activate and kept giving me an error “The filename, directory name or volume label syntax is incorrect. (ox8007007B).”

I figured at first it was the firewall at my work, then I figured it must be because they were just a lot of people activating Windows.  But the problem continued.
I did some searching and found the following command which fixed the issue:

slmgr.vbs -ipk “Your product key here”

After putting in my product key using this, the activation went through no problem.
Unfortunately I can’t find the site where I found this command to give credit.

Certificate errors in Internet Explorer and Google Chrome

This was a weird one.  I’m surfing the web this evening and web pages are acting funny and I start getting certificate errors on a few websites.  Ok, this can happen from time to time when a website fails to renew their certificate and such.  But  And several other huge sites?  I’ve been using Google Chrome so I figure it’s just acting up.  I clear my history and open and close it…still getting errors.  I open Internet Explorer, same thing certificate errors on most all websites.  I clear it’s history and reset it back to defaults.  After a few Google searches someone in a forum mentions the date and time on your computer might be off.  Sure enough.  My date was set back 2 months.  Set the correctly and voila.  No more certificate errors.  Weird.  My Dell XPS 15Z laptop started having a line of dead pixels on the screen.  Dell promptly sent a replacement screen and a technician out the next day onsite to fix it.  They put in the wrong display and left something rattling around inside.  The very next day they had another technician replace the screen and fix the rattling which turned out to be the CMOS battery.  I guess they unplugged it during the repair and it changed the date on my laptop which caused the certificate errors.

Wallpaper – Worry Why Should I Care?


Alive in the age of worry
Smile in the age of worry
Go wild in the age of worry
And sing Worry, why should I care?

– John Mayer

  • Camera: NIKON D7000
  • Taken: 21 June, 2011
  • Aperture: ƒ/5.3
  • Focal length: 75mm
  • ISO: 250
  • Shutter speed: 1/1000s

Setting up VNCServer on Linux CentOS 6.2

CentOS does have a built in VNC server I found called Remote Desktop (not to be confused with Windows Remote Desktop).  I managed to get that turned on and working but the performance of it seemed slow.
I then tried RealVNC but had troubles getting it started at boot.   I found these instructions  and used them to form my set of instructions.

These instructions will help you install VNCServer (TigerVNC), open ports on the firewall and start VNCServer at boot.
A few things about VNCServer on Linux.  It doesn’t work quite the same as on Windows.  You get connected to a new instance of X Windows for each user.
If you log off the user it tends to kill the session and it won’t work again unless vncserver is restarted or you reboot.
This doesn’t connect you to the “console” session, the session that’s present at the keyboard and monitor.
I didn’t take time to figure out the best way to do that.

These instructions assume you know how to edit text files using vi.
If no here is a good cheat sheet:

Install VNCServer as root: yum install vnc-server

Login and create vnc password: vncpasswd (logged in as vnc user not root)

Edit vnc server configuration: vi /etc/sysconfig/vncservers

Remove the # sign from the VNCSERVERS AND VNCSERVERARGS
Add a port for each user you need (2:username means port 2)
Remove -localhost or you won’t be able to connect to the server.
That is for encrypted connections through ssh.
So mine looks like:
VNCSERVERARGS[2]=”-geometry 1280×768″

Start VNC Server manually /sbin/service vncserver start

Add VNC ports to firewall (iptables)

vi /etc/sysconfig/iptables
Add these under the :OUTPUT ACCEPT [0:0]
-A INPUT -m tcp -p tcp –dport 5900 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 5800 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 6000 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 5901 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 5801 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 6001 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 5902 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 5802 -j ACCEPT
-A INPUT -m tcp -p tcp –dport 6002 -j ACCEPT
(Note: you don’t have to put in all of these sets if you only are connecting one user.)
(Also if you only want to allow the connections from one interface and not all you can add  -i eth0 after the second tcp.
This would allow connections to only interface eth0)

Restart iptables: service iptables restart

Test connecting from another VNC client with

Set VNCServer to start at boot: /sbin/chkconfig vncserver on

To see if the vncserver is running: netstat -tulpan | grep vnc