Notes - future replication entries - time waster!

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

one of my most common probs of late is where customers are changing their computer system date in windows, then replicating lotus notes...

then complaining because no one is receiving their updates when they next replicate...(If notes has replicated when the system date was set in the future, it gets confused, registers the replication entry, and thinks it's that date - so refuses to accept/ send any updates users have made to a database until Windows reaches the date, or us mugs have to go in and sort Notes out - usually the latter)

I find this such a time waster to fix (dial in, go into each future replication entry and remove it, then exit and run Ncompact, and sometimes a Nfixup)

We can't disable these particular customers Windows access to time/ date settings, as we are only contracted to deal with the Notes side of things...

Does anyone know a way I can stop this from happening short of driving over to each individual unit (there are hundreds) and yelling at them to leave the system dates alone?......or does anyone know a quicker way of cleaning up the mess it makes when Notes has replicated into the future?

Cheers,

L

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

if you unable to stop them changing the dates and that is the cause of the replication fault, then the answer may be no...

 

Get the customers IT people to use Group Policy to lock down the time and date settings? - Tell them it will save money on supports charges. Solves problem, but may land you in hot water!

 

Leehaa,

The professional thing to do is for you to notify your supervisor/boss about this issue. If possible, try to document some sort of "before" and "after" perspective of the issue with like maybe obtaining screen shots. Then using the help desk software, open a trouble ticket for yourself with the start date/time when you start to: 1) dial in 2) go into each future replication entry and remove it 3) exit 4) run Ncompact 5) Nfixup. Then close the trouble ticket. Tell your supervisor/boss that you're done with fixing the problem. The reason why this is important to document is so somewhere the beancounters will find out about the "inefficiencies" or "increased costs" for your company due to the customers' "screw up." Then maybe the sales person who sold the service package might have to contact the client to basically demand that they stop messing with the date/time settings. Remember, you're supposed to be the friendly, helpful, and nice "face"/voice that the customers deal with. Let someone else do the "bad cop" routine for you.

I hope this helps.

 

Hiya Sparky!

Just noticed this post...

It is on a Windows domain, but unfortunately it's not that straight cut - we are totally different companies - the other company look after the windows side of things, and we are supposed to support Notes only....having said that, you may be onto something - I'm gonna email one of their support team to see if anything can be done about it as it's in their best interest - it will mean that it'll reduce the amount of support calls that they fire our way!