• Browse Blogs
  • My Blog
  • My Updates

+Tags Get help with tags?

  • View as cloud  | list

+ Similar Entries

photo

Annoying Domino URL ...

Blog:  Pascal David
Pascal David
Updated 
No RatingsRatings 0     CommentsComments 2
photo

Sametime Entry 8.5 C...

Blog:  AnythingAroun...
Maurice Teeuwe
Updated 
No RatingsRatings 0     No CommentsComments 0
photo

8.5.1 UNFAIL - Part ...

Blog:  Erik Brooks
Erik Brooks
Updated 
RatingsRatings 2     No CommentsComments 0
photo

8.5.1 UN-FAIL! The F...

Blog:  Erik Brooks
Erik Brooks
Updated 
No RatingsRatings 0     CommentsComments 6
photo

maintain your consol...

Blog:  AnythingAroun...
Maurice Teeuwe
Updated 
No RatingsRatings 0     No CommentsComments 0

+ Bookmarks

+ Blog Authors  

Never change the system clock!

Chad Scott |   | Tags:  administration domino | Comments (1)  |  Visits (685)
Changing the system clock is one of the most damaging things you can do in a Notes/Domino environment. In particular, setting the clock forward in time and then back to the current time is a scenario that seems to play out much more than it should. Doing this on a Notes or Domino machine can have many serious ramifications that can have lengthy clean-up procedures.

I understand there may be times where you want to test the correct function of some task or agent at some point in the future, perhaps as part of planning for a specific project or business cycle. If this type of testing must be done, make sure it's in a completely disposable environment. I don't even recommend your normal test environment unless you plan on rebuilding it afterward. This is a perfect scenario for a client/server running in a virtual machine. Make a snapshot, do your testing, and then delete it.
No RatingsRatings 0

Comments (1)

photo
1 walter scanlan commented   Permalink No RatingsRatings 0

The BIG problem with moving time forward THEN BACK, is the time stamps on documents created while the time was pushed forward are in the future, This can cause BIG problems with some things, Example. A view update is triggered by the time stamp of a document relative to the server time, If a document has a create time in the future. EVERY access to the view will trigger an update.
This is the most common problem, but not the only one.

recovery isn't fun, but I did Technote the process http://www.ibm.com/support/docview.wss?rs=899&uid=swg21252915

Add a Comment Add a Comment

Previous |  Main  | Next
Skip to main content link. Accesskey S
IBM Lotus Connections Help Tools About