[Brendan42]

Just noticed this timestamp in BAS for a user I resent service books and IT policy to:

Last contact date 1/1/70 12:00:00 AM

Should I be concerned?

This user was migrated from 4.1.5 using the BET and somehow remained on both servers. Hence I kept getting the following error:

User appears to be running on a BES administered with separate database. Other database's stamp = Fri Dec 18 14:07:11 2009 ours = Thu Jul 10 17:30:34 2008

Once again, strange timestamps. Should I be concerned?

[Brendan42]

BES 5.0.1, Exchange 2003, The eventlog entry was from today.

[cyclmpc]

I've migrated 800 users from 4.x to 5.0 and didn't see any issues when a user appeared on both BES. I know that really doesn't answer your question on if you should be concerend, but I assume that you are migrating to retire the 4.x server and obviously should be addressed.

I'd be curious to see what pops up if you use the transporter once more on the user in the preview.

The next step wouod be to remove the user from the 4.x DB and see if the BB still reponds. If not, then an activation should set things correct on the correct BES.