chris adams

Hey ~

I have to plead ignorance and say that I don't typically remove either the
lockdown or urlscan once I have applied it...

With that said, I preface this - the metaback was designed for this type of
role;
a). Install lockdown to ****nal config
1a). Backup original in case of disaster
2a). Lock down according to selections (template, etc.)
b). Uninstall Lockdown
1b). Verify that good backup of original exists in metaback
2b). Uninstall lockdown
3b). Restore "original metabase"

Hence, it wasn't designed to serve as a backup of every action. I can't say
that I am 100 percent confident in this answer, but in short, I think you
may be looking @ needing to restore your metabase from a backup to close
that gap of changes that occurred in that year or so...

NOTE: I BOLD THIS FOR THOSE WHO DO NOT KNOW, URLSCAN IS DIVORCED FROM THE
LOCKDOWN TOOL. THEY ARE STILL RECOMMENDED ON ALL IIS SERVERS PRIOR TO IIS
6.0. HOWEVER, THEY ARE SEPARATE DOWNLOADS.

URLScan only:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/tools/tools/urlscan.asp

LockDown Tool:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/tools/tools/locktool.asp

Thanks,

--

~Chris (MSFT)
IIS Supportability Lead

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

bj freeman

I am not clear if the metabase that has the Nov2002 and June 2003 was
backed up.
assuming it was.
in the Inetsrv/adminsamples is a bunch of VB scripts that access the
metabase.
you can use these to built a script to extract data from one database and
put it in the other.
Warning: There are a lot of gotchas, so back up, by copying, all the
metabases and back meteabases.
Also your Web sever will have to be offline while this process is done.