Video Screencast Help


Created: 05 Mar 2013 • Updated: 03 Apr 2013 | 1 comment
This issue has been solved. See solution.

OS : Windows Serve 2008 R2 64 bit

NB Version :

Actually we have master servers running on the above specifications and 4 to 5 members are looking after the backup and taking the console.

How would the change got replicated in NB console level if any one changes without closing it. Is there any cmd that can be scheduled at certain intervals please help

Comments 1 CommentJump to latest comment

Mark_Solutions's picture

I dont believe there is a way to force a refresh in the way you are looking for.

It has always been a case of "whoever selects OK last wins"

You do find that recent versions, especially with policies etc. do warn a user that other changes have already been made and that their changes are not valid so that the user has to reload and make the changes again.

However, the only real way to keep this under control is for any changes you need to make to go through change control (even if a very simple change control where changes are registered first and the person allocated to do that change allocated - a simple spreadsheet would be fine)

Hope this helps - "too many cooks" and all that!

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.