Edit: Interesting HTML tags on it, and it seems I need my own server to set up pictures. Well, good thing we have a static IP! Just need to get the DNS records moved...
This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved. Additional Information: Folder: F:\Users$\user.name\Desktop\Random Folder Name\ Replicated Folder Root: F:\Users$ File ID: {00000000-0000-0000-0000-000000000000}-v0 Replicated Folder Name: Users Replicated Folder ID: 33F0449D...
For this quarter's health checks I wanted to get some actual data out of the process and act on the 'continuous improvement' stuff we all talk about but don't always do. I asked myself some questions... What do people actually think about the process? What would they change? Is this really worth continuing? ( and more to the point, what am I doing about improving this process? ) How would people react to the idea of 'advance voting', where you essentially had the option to do 'Planning Poker' for your votes - would stir some controversy, if nothing else, give people opportunity to think in advance ( idea c/o Steve Rogalsky ) Instead of bumping through the pre-during-post process of this, maybe I could write it out this time?...a health check playbook? ( there are a surprising amount of moving parts ) What do people actually think about the process? I used a basic NPS survey formula through Google Forms and managed to get just over half t...
tl;dr: the onset of rapid prototyping dev crews will increase both the speed and size of the organizational foot-gun. ("Survival is not mandatory." - Deming) Platform eng folk should consider time-to-onboard-a-service as an inbound KPI. All software engineering should rejoice that competent orgs will, c/o rapid prototyping, provide a somewhat more regular flow of meaningful work.
Comments
Post a Comment