• 2,000 pages a month
• Agree to a three year term (after that you keep it or you can return it at any time during your three years)
• Purchase your supplies from Xerox

Xerox will provide free shipping and free service and support for you during the three years.

Microsoft has recently updated (as of Jan 26th, 2007) this introduction to IPv6.

Yes, it really will be implemented in our lifetime. It is worth a couple of minutes (or hours) to get started thinking about IPv6.

Download the guide at Microsoft's download site at: http://www.microsoft.com/downloads/details.aspx?familyid=cbc0b8a3-b6a4-4952-bbe6-d976624c257c&displaylang=en&tm

Since the issue keeps coming up, I have decided to add it to my blog.

Many people like to create a basic VPC or VS image and then copy the vhd and vmc files and rename them to build a new virtual machine. Sysprep is often used so the copied image isn't exactly like the original. It sure works nice, except, the ethernet address is not changed by sysprep and TCP/IP has lots of problems when there are multiple systems with the exact same MAC.

Paul Adare has discussed this about 8 bazillion times (he is getting tired of it, too). The answer is to go into the vmc file (make sure the virtual image is not in use) and remove the hex code from the xml tags. Search for ethernet_card_address and then remove the information between the opening and closing tag.

When you restart the virtual machine, it will automatically generate a new random address so there will be no conflicts.

Pearon/Vue is a testing center company. One of the things I like about them is that they have finally figured out how to promote themselves by using the Microsoft Certified Trainers in the field. As an MCT, I meet a pretty large number of IT pros that work on Microsoft platforms. I help them learn about the products and how they are integrated. In many cases, I also provide in class consulting for them by helping explain and fix problems they are having in their companies. In some cases, they come to me to help them fix problems.

Anyways, I received a package from Vue/Pearson this weekend. The package basically says, "Thanks for supporting us in the past and here is some motivation for helping us in the future..."  Yes, that is very much a paraphrase.

So, here is the concept - they gave me a gob (actually 3/4 of a gob) of book marks to give to students. On the book marks is their phone number, 800-837-8734, so you can book exams. Also on the book mark is a 20% discount code that you can use as much as you want, MSUU6C3E011F. The "0" might be an "O" but I can't tell for sure.

It is nice to see that some companies out there understand that MCTs can be a great resource to them.

Yesterday, I ran across a great article on how to use the Windows Debugger for analysis dump files. I haven't seen such a great article in a long time and highly recommend that everyone give it a read.

http://www.nwfusion.com/news/2005/041105-windows-crash.html?fsrc=rss-windows

I am having a cow right now. OK, maybe not a cow, but definitely a calf or something smaller.

I was just reviewing http://support.microsoft.com/default.aspx/kb/896367 which lists applications that have passed Windows Server 2003 SP1 testing. I loved the section afterwards that listed many applications with known issues. I was very impressed to see the list so clearly made available.

I was not pleased to see so many known issues. I am now going to have to postpone some of my scheduled upgrades to SP1 until I verify some agent versions (i.e. CIM and Dell OpenManage) and get some patch upgrades for other applications.

I guess I should be happy, though, because I read it before I started my upgrades.

I have heard lots of people talking in the hallways about many subjects before, but I had to laugh today.

I was just about to go around the corner and I overheard one of my coworkers talking to my boss about me. He said, "Yeah, I was talking to Russ and asked him to explain TCP/IP subnetting to me. I think he would still be explaining it if he hadn't filled up his whiteboard." Of course, once I got around the corner, I said, "Hey, I got another whiteboard from the conference room, we can finish our discussion now." My boss about fell over laughing.

A few minutes later somebody came in and took a picture of my whiteboard.  I am sure the picture will be enlarged and posted someplace in the office in the next few days. Yes, the whiteboard is fully crammed with binary and graphics, and I used five different colors. It really does look like a geek brain blew up all over it.

<Per Sean Tucker: Yes, the evil wheel of IP is one of my methods of teaching subnetting - it leaves your head spinning or makes you hungry>

The second Tuesday of each month is a special hell for many of us in the industry. The second Tuesday is when Microsoft releases its standard scheduled patches. Many of us then scramble around as we evaluate the importance of each patch to each of our clients and their systems. You can hear the screams of pain from some offices that usually go like this, "Holy crap! Do you see how many patches there are? What are these idiots thinking when they wrote this mess of code? Damn it, I need some vacation! I can't take it anymore!"

So, this month, we are being told, there will be no new patches issued. I don't know whether to be relieved or to be scared out of my wits. Right at this point, I am scared.

Does this mean that nothing was found during this last month? Does it mean that problems were found but Microsoft didn't think they were important enough to fix this month? Does it mean that problems were found but Microsoft wasn't able to fix them this month?

Personally, I like the idea of not having to patch all of those systems for a month. It has been a continuous process for many of us in the field. It kind of goes like this:

1. Patches are announced. We take some time to evaluate the vulnerabilities and see if they apply to individual customers and individual servers.
2. Patches are applied to Development systems during one week. Results of patching are closely watched. If anything unusual is found, it is tested and checked multiple times to see if it is predictable or repeatable and whether the problem is related to a single patch out of the list.
3. Patches are applied to the Test systems during the next week. Again, they are tested and watched to make sure they are not having a negative impact.
4. Patches are applied to the Production systems during the next week. Again, they are tested and watched to make sure they are not having a negative impact.
5. New patches announced and around we go again.

Patching continues for ever and ever. The big problem during this cycle is when problems are found that impact 3rd party applications or home grown applications. If there are problems, then somebody has to coordinate communications and break/fix efforts with all of the vendors involved and assist with testing.

I like the idea of a break in this cycle. I am afraid, though, that something really big is being missed or not being fully addressed. I think I will say a prayer for all of us tonight.