Tuesday, February 21, 2012

How to Uninstall Any Anti-Virus!

Embarrassingly enough this one comes from Microsoft itself, however it is amazingly useful:

Site for quickly gathering some technical statistics from users


It’ll automatically tell you your OS, browser, IP, Flash version, etc. Might prove useful in some circumstances where gathering this data over the phone is unwieldy otherwise.

Credit to my co-worker Sean for showing me this

Windows 7 "Run as" + "Run as domain user from non-domain machine"!

I know that we all miss the Windows XP right click > run as trick...

Well to get that option in Windows 7, you simply have to Shift + Right Click and select “Run as different user”! (News to me, maybe some people already knew).

In addition if you have a need to run a program as a domain user from a non-domain computer, you can use the “runas” PowerShell command with the /netonly flag.

E.g. runas /netonly /user:domain\username


Windows DHCP running out of IPs and can't change scope?

Took a call tonight from a client regarding them being unable to get DHCP IP address throughout the day and learned something incredible about Windows DHCP in the process that was I didn’t learn when studying for the 640 exam.

Obviously increasing the DHCP scope would resolve this problem, but I didn’t have a good way of telling why their scope was set the way it was and what was using the excluded IPs nor did I want to add another subnet because I didn’t know what implications it would have.
My “Story”/Resolution notes:

Looked into the DHCP issue they were seeing. DHCP server was reporting only ~50 leases active. Checked the DHCP lease period and it was set to 6 hours, which seemed accurate as they would expire overnight and then free them up right? But they were still running out of IPs for some reason... I checked DHCP statistics and the DHCP scope was reporting only 14 leases open for leasing!?

Researched why this was occurring and found 2 registry values that explained it.

The DHCP Cleanup Interval (how often the DHCP server cleans up stale leases):

The DHCP Grace period (how long after a lease expires that it is reserved to be renewed before being subject to DHCP cleanup):
HKLM\System\CurrentControlSet\Services\DHCPServer\ Parameters\LeaseExtension

The DatabaseCleanupInterval was/is set to 60 minutes by default will renew during that period if they are active on the network. (They become active within 60 minutes of inactivity, they can still renew their lease)

However, the LeaseExtension registry key was not present and I finally found out the default is 4 hours! This means that a client would get a lease that is good for 6 hours and if they don't renew it during that time they would get an additional 4 hours "grace" period before it would be deleted during clean up. Since clean up only occurs once an hour, if the client got the lease 1 minutes before that mark, it would actually give it another 59 minutes before it was cleaned up (essentially 5 hour grace period and 11 hours to renew their lease!).

After figuring this out I decreased the lease period to an 1 hour 30 minutes and set the grace period to 60 minutes. After restarting the DHCP service I instantly saw the DHCP scope go from 92% full to 35% full!

This does increase DHCP traffic on the network, however its resolves the issue of running out of IPs if you can’t increase DHCP scope.

DHCP lease = amount before the lease on your IP expires.
DHCP Clean up = interval at which DHCP removes stale leases.
Can be changed with HKLM\System\CurrentControlSet\Services\DHCPServer\Parameters\DatabaseCleanupInterval reg key (in minutes)

DHCP Grace Period = Amount of time AFTER DHCP lease expires before it is subject to DHCP clean up (default = 4 hours!)
Can be set by adding HKLM\System\CurrentControlSet\Services\DHCPServer\ Parameters\LeaseExtension DWORD reg key (in minutes)

Not sure if this was common knowledge or not, but thought it might be able to save at least one of us from going through the trouble I did tonight!