Your Mom is a Default VLAN...

Something I did recently using a SSG 20 with commercial T1 and Comcast and both default virtual routers. (You don't have to use two virtual routers, but here's why I did this at first). Initially, my client reported that Comcast was assigning DHCP to the firewall's interface. When DHCP is used, the default route created from DHCP cannot be modifed and will show up as a directly connected route, so it will have a higher metric (unless you modify your preference / metric settings, but I have not tried that) So, if Comcast is supposed to be the backup route, placing it in the untrust-vr and controlling traffic in the trust-vr worked great. This works fine with a static IP as well. Here we go: Here are the default zones in the default trust-vr. set zone "Trust" vrouter "trust-vr" set zone "Untrust" vrouter "trust-vr" I created a new custom zone and placed it in the untrust-vr set zone id 101 "Comcast" set zone "Comcast...

So, I have to say what a drag it is to have 20+ .pst files from an Exchange 2000 server and having no way to import said .pst files at the server level into Exchange 2007. Oh yes, I'm well aware of the SP1 option for the <!@%^%$#> Import-Mailbox Powershell command syntax, but, I'm also aware that SP1 is not yet out of beta. And even if it was today, it wouldn't have helped me 10 days ago. Here's the situation. I'm in the middle of trying to migrate a small organization over from Windows 2000 DC's and Exchange 2000 to Windows Server 2003 + Exchange 2007, I run into what I am still dwelling on, no .pst import option. Well, the two biggest problems / pain in the  <!@%^%$#>  on this project was the fact that 1) Active Directory has inconsistencies 2) Exchange 2000 is installed on a Domain Controller. Now, what's the problem with that? I can't ADPREP Active Directory with inconsistencies that are not easily resolved. But, for fun let's ...