I virtualized my domain controllers and ran across this error:

The File Replication Service has detected that the replica root path has changed from “c:\windows\sysvol\domain” to “c:\windows\sysvol\domain”. If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
“DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”

A pretty random error and really not very informitive. What it is telling you is that the s/n of the drive has changed as far as the OS is concerned and NTFRS is not happy with it. Here is what I did to resolve the problem based on what I found on the Microsoft site:

1. Create a blank file named NTFRS_CMD_FILE_MOVE_ROOT
2. open a dos prompt and run “net stop NTFRS”
3. once complete run “net start NTFRS”
4. Wait 15 minutes and the problem resolves itself

Tried to install new 5908 controllers in the i this weekend. Didn’t quite go so well turns out you need v5r4m5 of the lic to make it work. Would have been nice had the configurator not let us do it at 5.4. Oh well something learned for the next upgrade.

This is cobbled together from a couple of different places. I used my Ubuntu install to do this as I didn’t want to use Windows and I am not allowed to use my Mac at my work.

install net-snmp on Ubuntu with “sudo apt-get install net-snmp”
Once that is installed using this site to find the relevant snmp OID’s was pretty easy:
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&substep=2&translate=Translate&tree=NO

Here are the two for S/N and Model#:

mib-2.47.1.1.1.1.11.1 – Cisco Serial #
mib-2.47.1.1.1.1.13.1 – Cisco Model#

Put into a command:

snmpget -v1 -c (community string) (ip address) (OID)

Then I just output this into a file and had everything from my network.

In the process of trying to institute a 200MB email quota for all of my users. We will have to see how well this is going to go over, I have a feeling having done this in the past that it may be as painful as I remember. Then again to go along with it I am also going to stop backing up the email for longer than 2 weeks. This should help in the event that email needs to be recoverable vs. it being discoverable. I always hate leaving email lying around because some auditor is always going to want to pull up email for several months ago. The easier I can make the life the better, especially when it comes to email restores.

Connecting to the darn netshares. This person seems to have found an answer to the problem:

http://www.shield.on.ca/Blog/?p=728

Hope this helps someone out there.

So there is a new installer for Wireshark for Mac OS X: http://www.wireshark.org/download.html

This install actually installs the application without using macports or anything like that. However you need to follow the directions that are in the readme:

Quick Setup

1. Drag the Wireshark icon onto to the Applications alias.
2. Open the Utilities folder from the Wireshark.dmg
3. Drag the contents of the Command Line folder to $HOME/bin, /usr/local/bin, /opt/wireshark/bin or any other location that makes sense (preferably one that’s in your PATH). Easiest way I found to do this was to use the terminal and do a cp to a directory in your path.
4. You will probably need to adjust the permissions of /dev/bpf* in order to capture. You can do this by hand or by dragging the ChmodBPF folder onto the StartupItems alias. Read the readme in the ChmodBPF directory especially if you are using Snow Leopard.
5. Reboot

Now you should be able to use Wireshark on your machine correctly.

So I finally got notified of passing my CISSP, it only took about 3 weeks to get the notification. Now I just have to get myself endorsed and I will be awarded the certification. Then of course comes the fun part of maintaining my cert by getting the continuing education credits.

Working on building my virtual lab machine at home to work on my routing stuff. Since I got esxi up and running I have built an XP machine with minimal services and then running GNS3. Currently I have 5 routers and 2 firewalls running and those I am using just to brush up on my skills. So far I have used the following to build the system:

http://www.gns3.net/

Then I used this to limit the amount of processor that the PEMU process takes. If you don’t do this then the PEMU Process will take up all of your CPU.

http://mion.faireal.net/BES/

Overall I am pretty happy with the solution, especially since I can use RDP to access the host machine and reboot any of the routers when needed.

So I just added the SATA Lefthands to my config and got to remove the Failover Manager from the config. I decided to just turn it off for now, but leave the vm on the farm in case I needed it. However it is nice to have 4 units going, it is also nice to now have some tiered storage so that things that just need storage are not chewing up the good SAS disk. So now I have almost 5TBs of usable storage associated to my VM farm.

So I finally got my virtual routing up and rinning within my esxi environment. I did have some problem with a corrupt 7200 image and needed to download a new copy. It is nice that I can increase the size of the ram and make the machine run more virtual routers for larger environments. I am going to try and work on my ccnp and see where o get with that.