Taget files newer than source files on upgrade

[MattJpopo]

I am working in a test environment preparing for an upgrade from Exchange 5.5 to Exchange 2000. During my test run upgrade I got seven message popups stating:

"The existing target file is newer than the source. Do you want to overwrite?" The seven files that I was prompted about were edbbcli.dll, emsui32.dll, msfs32.dll, amlusa.dll, fradm32.dll, admin.exe, kmsadmin.dll. I'm trying to determin why I was prompted about these files and if either overwritting them or not could pose a problem in my live network.

My test lab is very basic and limited and is not an exact replica of my true network environment, but it's the best I have. This is my test lab set up.

1 Server w/Exchange - Windows 2000 server, sp4.
1 Client - Windows 2000 pro, sp4.

The lab is running Active Directory. In the live network I will be upgrading in place from Exchange 5.5 sp 4 to Exchange 2000. I'm doing an in place upgrade as downtime is not an issue and I do not have a new server to migrate the messages to.

I installed the AD connector and then ran the forestprep and then the domainprep. All of which worked fine and I verified as working/successful. During the upgrade process is when my seven prompts occured. Of which all seven I answered yes, overwrite. Why would Exchange 5.5 sp 4 files be newer than Excahnge 2000s? Could overwritting these files cuase problems in my live network? Has anyone had this happen during an upgrade?

My live network environment is as follows

4 Domain Controllers - Windows 2000 sp4
1 BDC - Windows NT 4 sp 4a
90 Clients - Windows NT/2000/XP
Exchange 5.5 sp 4 installed on a member server
Active Directory is running in mixed mode and working fine

Any advice, input or suggestions would be appreciated.
Thanks,
Matt

 

[Davetoo]

FWIW, I just upgraded from Exchange 2000 SP1 to Enterprise and ran into a similar issue. I got on the MS group and they advised that I keep the newer files.

I setup a test environment and tried it both ways, upgrade/reapply SP1 saying not to overwrite, then upgrade/reapply SP1 but overwriting, and in both cases I found no issues. When I did it to the production servers, I kept the newer files, then reapplied SP1 and it's been running just fine for the past week (knock on wood).

It is strange that an Exchange 5.5 file is newer, but maybe it's an OS file and not related to the Exchange? Do you hav Veritas on the system? A quick google search for the first dll you listed discussed issues related to Veritas.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[MattJpopo]

Thanks for the quick reply. I've not ran into problems in my test lab yet and will be trying the install again next week with keeping the newer files. I don't have Veritas running in my test lab. The files were locted in the system root though. I too thought it was strange I got that message coming from 5.5 to 2000. My guess was that it might had something to do with Exchange sp 4 and Windows sp 4? But really I have no clue and only a guess.

Thanks again, knowing something similar has happened to others and all is working for them makes me feel a bit better.