Writing ... or Just Practicing?

Random Disconnected Diatribes of a p&p Documentation Engineer

  • Writing ... or Just Practicing?

    Hotel Cablefornia


    So there's another New Year on the horizon and it's time to make some resolutions that will hopefully last for at least a few weeks into January. But at the moment I can think only one: find a new Internet provider.

    As previously documented in these pages, I really do try hard to deal with my business cable broadband provider. But they seem to try even harder to make it difficult. I guess the only saving grace is that, on average so far, I've only had to actually contact them once every four years.

    The trials and tribulations of it taking four months to get my account set up initially are long forgotten (except as an anecdote for long winter evening when geeks gather around a hot router discussing technology). And even the seven weeks waiting for an upgrade that simply involved changing the modem to a different model (where I did most of the configuration myself) are gradually fading into distant memory.

    Of course, I joked at the time that it would probably take another four months to get the invoicing right, though after intervention from the local office manager it seemed for a while that I was being unduly pessimistic. After only a month, I had a correct invoice for the upgraded package. Amazing.

    What I didn't realize was that I was still being billed for the old package as well. It was only when I checked the welter of paperwork dropping through the letterbox in more detail that I discovered two invoices with the same number. That's when I found that an "upgrade" is really a "brand new customer".

    Yep, despite the difficulties in actually getting a line installed at all, or a modem replaced, I am now the proud owner of two different accounts - and I get the privilege of paying for both. I'm confidently expecting to be told there is a charge to have the old account closed, and a waiting list of five weeks to do so. Perhaps they'll send an engineer round again to check if I have two cables coming into the house.

    It makes me laugh when I hear people say they will never deal with our ex-monopoly British Telecom ISP because they are "a pain in the neck" and "useless". BT are my secondary supplier and I cannot fault their service, be it technical or paperwork-related. The only problem is that their promised roll-out of high-speed fibre seems to have stalled before it got as far as me. I'd switch over to them tomorrow if I could get more than 1.5 Mbs.

    Though, based on experience, I'll probably have half a dozen Virgin Cable connections by the time BT find a bit of fibre long enough to reach the cabinet on our street. It seems it's rather like Hotel California. You can cancel, but you can never leave…

    UPDATE: According to the BT website today, the availability of its "Infinity" high speed upgrade that was due last September, morphed into October, drifted quietly into November, and was finally promised to be definitely here in December, is now advertised as "between January and March". Yet they still keep phoning me to ask why I haven't yet signed up for their broadband TV package.    


  • Writing ... or Just Practicing?

    All I Want For Christmas...


    So I continue to battle with Windows 8.1 and Outlook 2103 on my nice big Dell workstation. Our IT support department have given up on me, saying it's obviously a problem with my own network configuration. And it looks like they are correct. It's just a shame they can't tell me what the problem is.

    For a long while Outlook has been doing strange things. It had a few days of keeping count of how many messages I sent during the day (see Downwardly Upgraded) but that problem seems to have gone away again. It also regularly loses its connection to the mail server and then restores it - sometimes immediately but at other times it takes several minutes. And, best of all, it waits about ten minutes before displaying the Windows 8 desktop notification of new emails. Usually I've read and deleted them by the time it pops up.

    The same issues occur on other computers as well, both Windows 8 and Windows 7, but only when connected to my internal domain and going out through my ISA proxy server and load-balancing router to one of my ISPs. Bypassing all this, and plugging directly into the back of the ADSL modem, seems to solve the problem. So it's increasingly looking like an internal network issue.

    I've checked all the DNS servers I use as Forwarders and they resolve fine. There are no event log warnings in any of the servers. The ISA proxy server log reveals no denied requests to my email host, and only one or two to anywhere else - certainly not enough dropped packets to justify the problems with Outlook. I turned on logging in Outlook and used the new Microsoft Message Analyser to read them, but I can't make any sense of the contents. I tried network packet sniffing, but that revealed nothing useful from the few bits I could decipher.

    And then there's browser. Occasionally it has a spell of not being able to find sites. Today it couldn't find Bing for about five minutes yet other sites worked fine. Then it couldn't find the MSDB Blogs site. Other days it can't find anything for several minutes, then it all starts working again. Yet everything else seems to work just fine. My internet radio plays radio, Lync links, Team Foundation Server serves, and News has the up to date news.

    I've tried disconnecting the modem for the cable ISP connection and just using ADSL to a different ISP, and vice versa. I've run network diagnostics and DNS validation checks. I've monitored the performance of the ISA 2006 server, and double-checked all the rules. I've played with the routing tables in the separate hardware load balancer. I tried specifying the proxy server settings manually in the browser. All to no avail.

    Maybe my network is just too complicated. It's left over from the days when I was an IT consultant (well, jumped-up writer and occasional conference speaker actually) when I needed lots of infrastructure for developing and testing the few applications I built for customers. And, I guess, because I enjoyed playing with hardware. Perhaps it's time to review that decision. Do I actually need:

    • A file server
    • A Hyper-V host
    • A cold-swap backup Hyper-V host
    • An ISA server
    • A web server
    • A SQL Server
    • A domain with three domain controllers
    • A 24-port switch, three 4 port switches, and 300 yards of Cat-5
    • A wireless access point
    • Load-balanced routing to two ISPs
    • A NAS, a backup NAS, and two more for archiving

    ...just to use Word, Visio, and Visual Studio? Probably not. And all of a sudden I can see why my electricity bill is so high.

    Perhaps my Christmas present to myself will be a nice hardware firewall that I can just plug everything else into and forget about it...

  • Writing ... or Just Practicing?

    Downwardly Upgraded


    So it looks like my upgrade from Windows 7 to Windows 8.1 actually downgraded me to Windows 6.3. I know I don't keep up with all the latest whizz-bang O/S releases, but I can't say I've ever heard anyone eulogising Windows 6.3 as the ideal choice for today's modern computing environment.

    My regular reader will know that I'm generally averse to changing anything that's not completely broken, and I was quite happy with my old big-iron Dell Precision 7500. It's got bags of disk space, lots of CPUs, two big screens, and is easy to use. But, as usual, I got overtaken by technology.

    The problem in this case was Visual Studio. I was still on 2010 but the latest Windows Azure stuff needs at least 2012 to work. So if I have to upgrade on a box that's been gradually filling up with the usual effluent from years of operation and upgrades, why not go the whole hog and upgrade everything? Windows 8.1, Visual Studio 2013, and Office 2013. Who says I'm afraid to take risks?

    I even ran the upgrade checker to make sure the box was capable of handling all this exciting new software, and it generally looked optimistic. So I hop over to our software distribution site and grab Windows 8.1 Enterprise, thinking I might as well have all the available goodies. Except that, after an hour or so, I discover that you can't install Media Center on this. Well you can, if you read some blog posts on nefarious sites, but it seems to involve lots of hacks that I probably want to avoid.

    So do I accept that I have to give up watching the golf or snooker on TV in a window on the second screen while I work, and no longer enjoy some old Kate Bush videos to smooth the path through my daily Windows Azure documentation woes? No chance. Just grab Windows 8.1 Pro from our software site and install that over the top. Amazingly, it worked, and I quite happily paid my £6.99 to buy the Media Center add-on.

    And so, onwards I go installing the rest of my daily working environment requirements. It all seems to just work, and even Corel Photo and a couple of other apps that are supposed to have issues with Windows 8.1 installed and ran. But here's the intriguing thing. When I send emails through Outlook 2013 on this box it seems to have gained a new memory feature. The send/receive bar starts off OK with "Sending message 1 of 1". But when I send another message, even long after the first has gone and the Outbox is empty, it says "Sending message 2 of 2". Then "Sending message 3 of 3", and so on.

    I guess it's neat because I can tell how many emails I sent since the last time I opened Outlook. Though, according to our IT help desk, this isn't supposed to happen. Or Outlook getting fed up every now and then and locking up with the message "Send/Receive" in the status bar and nothing coming in or out. The technical term for this is, I'm reliably informed, "broken".

    And the fun doesn't end there. According to the computer list in my Windows Software Update Service, I'm now running Windows 6.3. Have I actually downgraded from Windows 7? Though WSUS does seem to deliver the Windows 8.1 patches and updates to the computer without complaining. And at least, when I look at the System Info page, it's comforting to see that Windows 8.1 thinks it is 8.1.

    And it's also kind of nice to reminisce about the last time we had a "point" upgrade in Windows. Though I doubt many people will remember Windows 3.1 now. It's interesting that, in those days, the biggest problems you had were trying to get devices such as printers, disks, and network cards to work at all. Usually it involved fighting with lots of different drivers, cables, connectors, and configuration files.

    Now everything hardware-wise just works, and the biggest problem is figuring out how to make the increasingly complicated software do what you want. Or even be able to tell what it is doing. My corporate laptop insisted I upgrade from Windows 8 to Window 8.1 this week (I'm not even the boss in my own office, never mind in my own house). It sat there with just a green box in one corner of the screen for a whole day with no sniff of a status bar or any indication it was actually doing anything. I had to go down to the garage and look at the lights on the router to see if there was any sign of life. Please can I have my animated network icon back in Windows 8.2?

    Though I'm still a little nervous that, when I upgrade next time, it will just take me back to Windows 7 again. Or maybe I have to work my way through 6.4, 6.5, 6.6, etc. first...?

  • Writing ... or Just Practicing?

    Agile Documentation - Tested to Destruction


    Agile development is an important technique here at p&p; and throughout much of Microsoft. However, I'm yet to be convinced that it's a good way of creating user guidance and documentation. It seems to me that the process often gets in the way more than it helps to produce a great final product.

    I've rambled on many times in the past about agile documentation. Most specifically in Can Writers Dance The Agile? and other posts here. Yet I keep thinking it needs deeper investigation - especially as the group I'm officially assigned to, CSI, insists we keep prodding it to see if it works.

    Note: Here at Microsoft, CSI is "Content Services & International". It's probably a bit less exciting than doing clever stuff with fingerprints and DNA, but we do have fancy computers that nearly come close to those you see in the TV versions of CSI. Maybe we should call ourselves "CSI Microsoft," wear white coats, and walk around with a flashlight held over our head.

    Anyway, coming back to the point, we've had another go at agile docs recently. Instead of a solid and agreed structure plan and detailed implementation notes of what we wanted to achieve, we started off with a "vision" (but see this post from a couple of weeks ago) and "brainstorming" to get a list of topics. Then we "asked the audience" with developer and advisory board surveys to see which of the topics they liked most. Next, we threw together some rough notes about each topic and then produced a first draft of each topic document.

    The next stage was multiple reviews. After each review we restructured the content, and often the whole document, to get it closer to the ideal. But, because it's agile, we often changed our mind about what the doc was trying to achieve (remember, there's no detailed implementation notes to guide us here) and completely rewrote it. And then did this again after the next review pointed out the holes left by (or introduced by) the previous reworking. Some documents went through four or more complete restructurings, and several were rewritten twice.

    The agile process also resulted in some of the "envisioned" topics being abandoned, often after they'd been rewritten several times, because - after investigation - they were too hard to define accurately. Or because they turned out to be not really relevant or practical. And as there is no overall structure plan, it was hard to see which topic should contain what section of the content, and how it related to other sections. It also meant that the focus could only ever be at the individual document level rather than the entire guide level, because that isn't defined yet.

    But what we could be sure of was that each individual topic was precise, accurate to the nth degree, and compact with no irrelevant content. This is, of course, extremely important; especially if the content will be used as reference information. But is it still "guidance?" I guess that's the core of the problem. What exactly should "guidance" look like?

    Typical equivalents of the word "guidance" include the obvious ones such as "help" and "advice." However, there are broadly two categories of meaning: "leadership" and "assistance." These almost seem like opposites - one leading from the front and the other pushing from the back. Yet the sub-meanings according to my thesaurus include "direction", "support", "management", and "control." Some of these seem more like they are related to aiding through understanding, whereas others are more related to despotic regulation. I'm going to take a guess that we're aiming for the first of these.

    So did we end up with what we wanted, and does it aid through understanding? It's not completely finished yet and it will be a while before we see any user feedback. And there's no doubt that the content will be extremely useful for the specific users and use cases it addresses. But it still seems like we missed opportunities. The agile process narrowed the focus and transformed the content based on individual reviews of segments, and forced additional depth of detail. It also removed a lot of the general "understanding" content because it already was familiar to the experienced reviewers. Most of all, it resulted in huge amounts of extra work writing and repeatedly updating (and then sometimes discarding) the content.

    Without a predefined (if flexible) structure and an overall feel for how it will all fit together and appear to the readers, there is nothing to prevent this wandering. As a writer, I'm lost if I can't see the finished thing in the back of my mind. It's like driving through a city in your car while blindfolded, and navigating by reversing and choosing a new direction at random every time you hit something.

    Maybe agile is good thing that can help to focus guidance more accurately. Or maybe it just allows the guidance to wander away from the original vision and risk irrelevance. If the original plan was to provide guidance around X and you end up with fabulous documentation of Y instead, did you do a good job?

  • Writing ... or Just Practicing?

    The Network Ate My Shortcuts!


    It's a bit scary when you turn on your computer and it's different from when you left it the day before. I don't mean it's a different computer (though sometimes that would be nice), but that something changed while you were in the land of nod.

    This happened to me last week. As I sat yawning and stretching in front of the screen waiting for some sign that the technology was also waking up from sleep, I noticed that several of the shortcuts to network resources that used to be on my Windows 7 desktop had disappeared. The first immediate panic reaction is "do I have a virus?" But a scan with a virus checker, and exploring the event logs, found nothing untoward.

    Next, try refreshing the desktop. No change. Then the trick of turning off display of icons (right-click the desktop, select View, and untick Show desktop icons) and then back on again. No luck. Next, look in the C:\Users\[user]\Desktop folder to see if the shortcuts are on the disk but not shown. Nope, not there either. Very odd...

    Maybe it's something to do with File and Print Sharing, or some domain-related issue. So I wander down to the server cabinet and start poking the domain controller. Strange - at 5:00 AM precisely that morning it had started reporting errors that there was a fault in the Active Directory. It happened immediately an automated backup started. And now the network icon in the taskbar was reporting that it was connected to an "unidentified network" rather than its own domain network.

    So I do the usual fix for that problem, disable and re-enable the network connection. Immediately it comes back with the correct network name. Except that I now have to reconnect to all the Hyper-V instances it hosts because they lost their connection when I disabled the network. And then, every six minutes, an error in the event log that Group Policy could not be processed because it can't find a domain controller. Even though it is one. The detail of the error is simply "Directory Error." Not exactly helpful.

    For a minute or so I ponder a full reboot, but that means stopping all the Hyper-V VMs. One is the proxy server, and my wife is currently in the middle of her morning Facebooking session so that's not a relationship-friendly option. The next best guess is to restart Active Directory Domain Services, which automatically stops and restarts several other important sounding services. There's heart-in-the-mouth moment when the DNS Service takes almost a minute to start up, but thankfully it all comes back with no errors in the event logs. And, magically, several hours later no more Group Policy errors either. Amazingly, I seemed to have fixed it.

    After that rather exciting start to the day, I do the research bit and discover that the shortcut issue is not my fault. According to KB 978980 on MSDN, being greedy and getting kicked for it is by design:

    "The System Maintenance troubleshooter performs a weekly maintenance of the operating system [and] either fixes problems automatically or reports problems through Action Center. When there are more than four broken shortcuts on the desktop, the System Maintenance troubleshooter automatically removes all broken shortcuts from the desktop."

    Furthermore, it says, "a broken shortcut is a shortcut to a file, folder or drive that may not always be available, for example, [...] a network folder that is currently not available due to the network not being available". I'll take a guess that being on a different network from the one the shortcut points to qualifies as "not always available." The workaround suggestion in the article is "keep the number of broken shortcuts on your desktop to four or less [or] create a folder on your desktop and move the shortcuts to that folder [which] will not be removed since they don't sit directly on the desktop."

    Or you can just disable the System Maintenance utility in Control Panel | Troubleshooting | Change settings.

    I can't help wondering how the meeting went where the Windows 7 developer team decided to include this feature:

        "Have you seen Joe's desktop recently, it's covered in shortcut icons. I'm
        sure he has no idea what they're all for!"

        "Yep, soaking up valuable resources and hiding that lovely picture of
        Niagara Falls that we went to so much trouble to include in our themes!"

        "It shouldn't be allowed. There should be someone who checks user's
        computers regularly to make sure they aren't being untidy after
        we went to all that effort to make the background pretty!"

        "Yes, but they might want to have a few shortcuts there for their favorite
        programs and regularly used files..."

        "I suppose so. How many do you reckon we should allow? Twenty? Ten?"

        "Why mess about. Let's just include a secret process that detects when
        a user is getting a bit slovenly and tidy up automatically. They'll never notice..."

    Except that, as the KB article reveals, sometimes we do...

Page 1 of 1 (5 items)