« Posts under Uncategorized

Enable Microsoft Update

Once annoyance I have always had with Windows is that once I run Office (or something else) and I say “NO!” to enabling updates for it, there’s never seemed to be a simple way of getting back to enable those updates.  You Google around for it and find a lot of posts saying “goto http://update.microsoft.com/microsoftupdate and follow the directions” but it never works for me.

I found this today, used it on two servers to enable updates for Report Viewer, SQL Server, Microsoft Access Database something or other horse shit, and some other Microsoft stuff.

Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
ServiceManager.ClientApplicationID = "My App"

‘add the Microsoft Update Service, GUID
Set NewUpdateService = ServiceManager.AddService2(“7971f918-a847-4430-9279-4a52d1efe18d”,7,””)

It’s vbscript (obviously) and I found it here: http://msdn.microsoft.com/en-us/library/windows/desktop/aa826676%28v=vs.85%29.aspx


FOG: Overview

I love FOG.  My current employer is the third company that I’ve implemented it for.  FOG is an open source computer cloning and application / printer management solution.  FOG literally stands for Free OpenSource Ghost.  I never ever post about anything, so I think I’ll do some posts about FOG.

FOG is available at http://fogproject.org/.

FOG forums are available at http://fogproject.org/forum/.

Current version is 0.32, but 0.33 is available as a release candidate.

Didn’t think this one through…

If you’re running a Windows based DHCP server, make sure you add an exclusion in your AV software for c:\windows\system32\dhcp, otherwise you’re going to have a bad time. Potentially anyways.

Old school trick to reset admin password (copy/paste from reddit)

You just need a Win7 disc:

  • Boot to Win7 disc.
  • Choose “Repair your computer”
  • Open DOS
  • Navigate to C: (or wherever Windows is installed)
  • Type: copy c:\windows\system32\sethc.exe c:
  • Then type: copy /y c:\windows\system32\cmd.exe c:\windows\system32\sethc.exe

Then reboot the machine. When the login screen pops up, hit SHIFT 5 times and you’ll get a command prompt. Then type:

  • net user administrator (password)

Obviously, without the parenthesis. Then you can close the DOS prompt and login with the password you just set. If the local admin account is disabled, type:

  • net user administrator /active:yes

This is a really old trick, but is really useful if you’re in a pinch. Where I work, it’s necessary to replace the sticky keys feature, so that’s why you copied it to the C: drive in the first step. You can follow the other steps and just replace it when you’re done.

Delay on boot, dmesg shows i915 driver attached, reenabling gpu turbo

Google shows a plethora of causes and solutions for this (https://www.google.com/search?q=i915+driver+attached%2C+reenabling+gpu+turbo+boot+delay)

For me, I just needed to do a BIOS update.

Disable DHCP for wired connection on boot

I have a Dell Latitude E5410 that I use exclusively from the couch, only on wireless.  Therefore, waiting ten seconds for it to decide that it couldn’t get a DHCP lease for the wired connection on boot was a silly waste of time.

It’s easily solved:

sudo chmod -x /etc/rc.d/rc.inet1

Yeah.  Easy, right?

I’m on Slackware, so I suppose YMMV.

Cannot use CBT: Soap fault. Error caused by file [path/to/file]

I’ve found that sometimes a VM crashing, storage being powered down before VMs are, or an ESX host issue can cause Change Block Tracking to stop working properly.  According to Veeam KB article 1113, the solution to this is to reset CBT by:

  1. Powering down the VM in question
  2. Head into the settings for the VM, click the Options tab, head down to General (under Advanced) and select the Configuration Parameters button.
  3. Set ctkEnabled to false
  4. Set scsi0:x:ctkEnabled to false for each disk for the VM
  5. Remove any files ending in -CTK.VMDK in the source folder, either via SSH (or emergency mode or whatever they call it) or through the datastore browser
  6. Power on the VM
  7. Power the VM off (updates the CTK table)
  8. Power the VM back on.
  9. Rerun your Veeam backup to renable CBT


However, this is a production server that has thousands of active connections at any time, so this kind of sucks.

Fatal error during installation. (Error installing driver “klim”. It is recommended to restart your computer.)

Rolled out Kaspersky to several hundred workstations over the past few weeks, and was getting the error “Fatal error during installation. (Error installing driver “klim”. It is recommended to restart your computer.)” on several administrative machines.  After the third or fourth one, I noticed that they were users that had things like Cisco VPN Client and remembered that Windows 7 only allows for so many network filters.  A quick google search for the proper registry key and I was back in business.


The key you want is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters and the max value for that is 14 (default was 8 if I recall).