Create a file with a space at the end:
echo Foo > "\\?\c:\rcs\boo.txt "
List files on system in a batch file with modified date and bare listing:
for /f "tokens=*" %%A in ('dir /s/b %target%') do @echo %%~tA,"%%~A"
For example, a directory with three files including "boo.txt " looks like:
, "C:\rcs\boo.txt "
02/03/2011 17:48, "C:\rcs\foo1.txt"
02/03/2011 17:47, "C:\rcs\foo2.txt"
Note how the file date is missing. This could be your clue that the file name is illegal.
Take a look at filelist.exe from [http://www.jam-software.com/freeware/].
This program creates an expanded listing (many more data points) but doesnt balk at attributes like date.
Deleting is easy, renaming is harder.
The following tool renamed "boo.txt " to boo.txt
http://wren.adoxa.cjb.net
wren.exe boo~1.txt boo.txt
took care of the filename.
Note: Wren appears to have a 16 and 32 bit versions - I used the 16 bit one to perform the rename, and was constrained to renaming it to a 8.3 filename. You should be able to work around this.
In my opionion 32 - 40 billable hours to perform the testing necessary for a domain rename in such a small infrastructure is insanely high.
The configuration you describe could be tested in an afternoon with a couple of physical "scratch" client computers, a virtual domain controller, and a virtual member server on an isolated LAN.
I'd start by obtaining a test domain controller by installing a VM connected to the LAN, joining it to the domain, and promoting it to a domain controller. I'd install a DNS server, mark it as a Global Catalog server, and set it to refer to itself for DNS. Once all AD replication completed I'd take a snapshot of the VM, and then demote it back to being a member server before removing it from the domain. This leaves the production AD domain in a state consistent with how it started.
I'd detach the VM host from the LAN (or otherwise isolate it), reboot the domain controller VM from the snapshot taken when it was still a DC and seize the FSMO roles to it. This gives you a DC "under glass" to work from. I'd join a couple of "scratch" client computers to the domain hosted by the DC in the isolated network, and bring up a test file server VM as a member server. Once I verified that the "domain under glass" functioned properly I'd proceed with taking snapshots (to give me a fall-back position to re-start testing) and start the domain rename resting.
Domain rename without an Exchange 2003 infrastructure to worry about isn't something you should be too scared of. It's reasonably well documented (others provide links in their answers that are reasonable) and is "supported" by Microsoft. As you've already noted, doing it before you deploy Exchange is important because this is your last chance to rename the domain.
Best Answer
Open a command prompt in the directory your .pst files are located in, and place the following file in that directory (save it as
renamepst.cmd
)This batch file has an
echo
command in place so that it doesn't actually perform any actions. If you are happy with the output after runningrenamepst.cmd
in your command prompt window, then remove theecho
from the last line, leavingrename %file% %file:~0,2%%file:~3,999%
in place.Please test before using this though!