Skip to main content


Showing posts from December, 2015

Starting to diagnose DFS issues

One of my client's server pairs seems to be intermittent in its syncronisation of data. Here are a few commands to test the sync.  Using an elevated command prompt ( right click, run as Administrator ) execute the following: C:\Users\ryv> dfsrdiag.exe backlog /SendingMember:ServerX /ReceivingMember:ServerZ /RGName:RepGroup /RFName:"Data" So what does this do? The initial part of the command is dfsrdiag.exe - the program to run the diagnosis. The switches are as follows: /SendingMember:ServerX - this is the server pushing data to the replication partner /ReceivingMember:ServerZ - and this is the server receiving the data /RGName:RepGroup - DFS Management has servers in groups so it will want the group name /RFName:"Data" - DFS is capable of managing different folder groups with different sync settings so you have to specify the folder.  If all is going well the result from this command should come back with something like:  No backlog - member <ServerZ>

Ubiquity UAP-Outdoor+ Review

Recently for a motel client I rolled out 12 of these little babies. The UAP-Outdoor+ is a compact, apparently weather resistant access point. The website details are here: I chose these for a number of factors: they are designed for the outdoors 183M range (apparently) 300Mbps speeds 802.11b/g/n with plenty of bandwidth and a wide frequency band price point was pretty good (compared to other products) While not strictly producing a meshed network, the UAP-Outdoor+'s have a zero config handoff, so end users won't know as they move around through network range.  Configuration of the access points was really quite easy - Ubiquity has a great bit of software called UniFi v4.7.6 Controller for Windows. Installing this on my laptop, and connecting it to the same network as the first access point got things up and running really fast. UniFi Controller allows you to configure SSID's, guest network information and everythi

OTRS 5 Review and Thoughts

Recently I upgraded our several years old OTRS install to version 5. The upgrade procedure is exactly like all the others have been. It was straightforward and I actually found that the documentation was better this time around than it has been in the past. After backing up, upgrading and testing, I like, mostly, what I see. There are a couple of things that are a bit annoying though. When closing a ticket, the previous version would automatically put in subject in the closure note. Likewise, in the Owner Update note it doesn't do it either. So each time, I have to update it. Not a problem if you're only getting a few notes every now and then, but we are changing and closing tickets in some large numbers at times. Also, I have about 50 statistics generated monthly via a script I run. The syntax for doing this. From: /opt/otrs/bin/ -n number  -blah blah etc To: /opt/otrs/bin/ Maint::Stats::Generate --number number  etc (from:  https: