Had another issue at work where I had to merge two DHCP scopes that divided a single segment between the scopes. Each scope controlled a range of IP addresses (Scope #1, .1 - .127, Scope #2, .128 - 254).

Both of the scopes had custom scope attributes defined.

One of the scopes had reservations defined.

To make matters more interesting, the subnet mask had to be changed from /25 (255.255.255.128) to /24 (255.255.255.0) - DHCP scope allows you to edit the defined range but the subnet mask is greyed out.

Lastly, a new scope had to be created under a new segment based on one of the old scopes above.

How to merge scopes without losing custom settings and re-doing reservations:

A variation of the commands at the start of this post will get you a text dump.(Note there are two kinds of export data; binary and text and they are not interchangable)

If you need to quickly modify a scope on DHCP, eg, delete a scope and recreate all the reservations in a new scope, the above technique with the following steps will make it easier.

I bet some of you guys have had these "power users" that absolutely screw up their own workstations so much so that you as an administrator can't control the file system nor control the machine remotely.

Well...

To restore Windows 2000/XP’s default system security you can execute following command:

Friday, March 23, 2012

I was asked this question by my colleagues and after answering it with the official VMware explanation, they still didn't quite get it. (Yeah, actually if I look at it without the necessary background info, I'd probably not get it either...)

The following visualization helped put it simply:

CPU USAGE and CPU READY - What is it?

CPU Ready = % of time there is work to be
done for VMs, but no physical CPU available to do it on (all host CPUs are busy
serving other VMs). One rule of thumb that I heard is that below 5% Ready is
normal; anything between 5% and 10%, best keep an eye on the VM and the host.
Over 10% (for extended periods) you should be planning on taking some action.

-

-CPU Usage = raw, absolute amount of CPU
used by corresponding VM at the given moment.

The amount of time a
virtual machine waits in the queue in a ready-to-run state before it can be
scheduled on a CPUis known asready time.

The higher the ready time is, the slower the virtual machine is
performing. The ready time should preferably be as low as possible. Virtual
machines that are allocated multiple cpus or havehigh
timer interruptsare more
frequently seen with high ready time values.

Tuesday, March 20, 2012

Reposting here for my own reference.
Original thread can be found here

Here is a VBScript program Richard Mueller wrote a few years ago to disable computer accounts from a text file. The file name and path are hard coded in the program, so the file can be anywhere. The file must be a list of computer names (NetBIOS names), one name per line: