Alas…Microsoft is playing catch up yet again.
This time the industry buzz is about exiting CEO Steve Ballmer’s keynote comments at this week’s Gartner Symposium/ITxpo in which he finally acknowledged Microsoft would be coming out with an Office for iPad version.
But the company already has lost substantial revenue since the iPad came out three years ago by not having an Office for iPad app, and it doesn’t sound like the suite is coming out any time soon.
Microsoft says its wants to make sure an Office version is truly touch-enabled whether it’s for the iPad or even Windows 8. A Windows 8 touch version of Office is slated for 2014 but in the meantime, frustrated users seek Office alternatives.
Some theorize that Windows 8 could have even had a better response from day one.
The problem is Office, says Robert Enderle, principal analyst of the Enderle Group, a long-time consultant in the IT industry. Office hasn’t even been converted to the Windows 8 interface, he said.
So the constant waiting drives software entrants to fill the holes created by Microsoft’s lack of a true touch-enabled Office suite. Indeed, the recent spate of office collaboration tools like those from CloudOn and others fill a gap for office productivity tools running on mobile devices that support the Office document formats.
But even as Ballmer finally states Microsoft’s intent to deliver Office for iPad, end users may not be interested in paying for what could potentially turn out to be a pricey package.
Now, Microsoft is waving its hands to gain attention. In fact, a few days after rival Apple said it would give away iWorks for free on its new iOS devices and Google said it would offer QuickOffice for no charge, Microsoft blogged that its Office for Web apps was also free.
Unfortunately for Microsoft, end users may have lost interest already, even if Ballmer’s booming voice finally tells them what they want to hear; Office for the iPad is in progress – but it may be too little, too late.
When I read Larry Seltzer’s Zero Day blog post yesterday — which appeared on a Patch Tuesday morning, by no coincidence whatsoever I’m sure — I was both amazed and amused to realize that it has indeed been a decade since Microsoft changed from its prior practice of pushing patches primarily as circumstances and availability dictated to its current practice of batching them up and pushing them out at a regular and predictable interval. This change occurred primarily in response to qvetching from IT departments everywhere that pushing patches out the door randomly didn’t really fit the working methods and models of modern IT organizations. Even then, standard best practices were already in commonplace use that employed formal change controls within the context of scheduled update activities to rationalize patching and update processes, and better fit them into the overall IT workflow.
A regular, predictable update schedule is what IT organizations wanted, and what Microsoft gave them with Patch Tuesday. Seltzer’s comment about all of this is right on the money “…the predictability of the update schedule and the improved information that comes with security bulletins these days, as well as improvements in patch management systems, were also a big part in making IT life more normal.”
Just last week, I was explaining to my nine-year-old son — who is the proud owner of “his” first PC (a Dell XPS 2710 Haswell model) — that he needed to get ready for Patch Tuesday. “What’s that?” he asked. I explained: “Round about the second Tuesday of every month, Microsoft releases most of its security updates and patches for the month. It’s part of the regular routine of keeping Windows systems up to date.” “Oh,” he said, “what do I have to do?” “I’ll show you,” I said, and yesterday we worked through his first-ever Patch Tuesday, as I showed him how to download and install the important patches, and evaluate and select the optional items he might or might not want.
I’m bemused to find myself passing the torch for Windows upkeep and maintenance to another generation, but that’s what started happening around our house late yesterday afternoon. And so the world keeps turning…
The first thing one should always ask when reviewing any kind of poll result is “Who’s in the survey population?” I was forcibly — and humorously — reminded of this essential basis for analysis upon taking a poll in an article about the impending release of Windows 8.1 (it’s due out about 10 days from today) entitled “11 days until Windows 8.1 rolls out for Windows 8 users, are you ready for it?” (from the Website, WinBeta.org). If you stop for just one second to consider that anybody who actually reads an article like this has to have some kind of interest, not just in Windows 8.1, but in its approaching release date, the following poll results make perfect sense:
Does this poll remotely approximate a cross-section of the general public (or even the whole population of IT professionals)? No freakin’ way, my readers, no freakin’ way! The population is what statisticians call “self-selecting” in that an indication of strong interest — namely, clicking a link to get to an article about the upcoming release of Windows 8.1, and then making it all the way to the end of the article before the poll even shows itself — is required to enter the population of survey respondents in the first place. Nevertheless, I find it very interesting that the vast majority of those respondents are apparently panting with lust to install the release as soon as it becomes available. That makes me wonder why they haven’t installed the RTM version already, itself widely available through MSDN and TechNet downloads for nearly one month now.
All of this goes to show that not all surveys are the same, nor do all convey genuinely meaningful information, either. If you see anybody quoting survey results, especially for surveys like this one, please take the time to find out where those results originate, and you may also be able to conclude that while these results may be interesting or amusing, that they also are not terribly informative about the attitudes or mindsets of the general population. If anything, these results are a perfect inverse of the general population, where I would be highly surprised if even 10 percent of Windows users plan to install 8.1 soon after the October 17/18 impending general availability (GA) date.
Almost forever, I’ve been a big proponent of the “clean install school” of Windows upgrade methodology. That is to say, rather than upgrading my systems from an older Windows version to a new one, I’ve been mostly inclined to blow away the older install in favor of a new one, followed by the added effort of reinstalling all my applications, restoring settings manually, and so forth and so on. What’s guided my activities has been the belief that this results in a leaner, more stable system, and reduced time to complete the overall installation process. And FWIW, many Windows experts — including the likes of Ed Bott, Paul Thurrott, and Woody Leonhard — have all voiced opinions or advice more or less in keeping with this approach.
But with the impending release of Windows 8.1 as a free upgrade for PCs already running Windows 8 on October 17/18, I’m prepping my PCs currently running Windows 7 — for which I purchased the $40 Windows 8 upgrades last year, when MS ran what still looks to be a “once in a lifetime” dirt cheap promotion to get people to move up from 7 to 8 — by upgrading them to Windows 8 in advance of the upcoming GA date. As an experiment, I’d planned to perform an in-place upgrade of my Windows 7 production desktop this weekend, with all of its 237 applications (as reported in Secunia PSI for that system) coming along for the ride.
Finding myself with some unexpected idle time yesterday afternoon, I decided to run the upgrade a bit sooner than planned. This blog post recounts my observations and experiences along the way to the successful and surprisingly smooth conclusion to that process (I’m writing this blog right now on the upgraded PC, which has shown no signs of outright weirdness or flakiness since the upgrade completed at around 5:15 PM yesterday afternoon, following about two hours of upgrade activity). I began the process by capturing two image backups of the original Windows 7 system: one using the built-in image backup captured in the Control Panel Backup and Restore utility, the other using Acronis True Image Home 2013 with the added precaution of creating a bootable UFD with the ability to restore that image to its original drive. I’d already replaced CPUID HWMonitor 1.18 with the Pro version, and uninstalled DualBootPro, Nvidia GeForce Experience, and VirtualCloneDrive to take cognizance of the pre-install warnings courtesy of the Windows 8 Upgrade Assistant beforehand.
The Upgrade tool downloaded the Windows 8 ISO from the Internet to start off the process, an activity that consumed about 24 minutes overall (I didn’t know how to point it at the local ISO copy I already had on one of my 2 TB conventional HDs, and didn’t bother to research those details, though I do see a very good discussion of this process on Windows EightForums). This approach did have one benefit that saved me from myself, however: using the MS-provided installer I obtained when I paid for the $40 license last year apparently had the product key baked into the installer, so my oversight in neglecting to store that key on another system (it currently resides in my Outlook PST file on that very PC) didn’t impede the installation process in any way, shape, or form, to my great relief and delight. Here’s how the rest of the timeline for the overall install process shook out (all times are approximate, based on my glancing over to my laptop where I relied on its system clock for rough-n-ready timing info, rounded to the nearest minute):
00:00 – 00:24 Download Windows 8 install files from Microsoft (perhaps Akamai; source wasn’t visible)
00:24 – 00:40 Copy files and perform in-place upgrade file copy, initial installation, and configuration
00:40 – 00:44 Getting devices ready (installing device drivers is handled during this phase)
00:44 – 00:54 Getting ready (system set-up and configuration)
00:54 – 00:56 Moving your settings (importing settings and preferences from the previous Windows 7 install)
00:56 – 00:57 Finalizing your settings (adapting/customizing settings for the Windows 8 runtime environment)
00:57 – 00:59 Getting your PC ready
00:59 – 01:03 Installing apps (this means Windows 8 Store/Modern UI/Metro apps, I imagine)
01:03 – 01:05 Establishing initial log-in, switching to Windows Live account, first complete Windows 8 log-in
01:05 – 02:00 Download and install 62 updates from Windows Update to catch system up to current patch/update levels
There were six (!) reboots during this process, one during the second step above, and between each of the next three steps, with the fifth one following installing apps, and the final one after the massive update installation that concluded the overall actual upgrade process. I didn’t hit any snags along the way, nor any serious hiccups or delays. Once this process was complete, I fired up DriverAgent to observe that it now reported 5 out-of-date drivers — an interesting improvement following the upgrade, because it had reported six out-of-date drivers (all either bogus or insoluble) for the previous Windows 7 installation resident on that machine. After about one hour of downloading files and fiddling about with them, I got the number of out-of-date drivers down to one, a considerable improvement over my “healthy status” on the prior Windows installation. It is for a “motherboard resources” item in the “Disconnected Devices” section for which DriverAgent supposes that a 2010 vintage version of the Intel Extreme Tuning Utility will address the issue. However, I’ve got the latest (2013) version of that utility already installed on this PC, and because it addressed all other items related to the Intel Thermal Monitoring devices to which the out-of-date finding attaches, I’m of the opinion that this is a false negative (“bad driver”) report from DriverAgent, rather than a genuine and fixable “bad driver” report from the utility. Case closed!
Summary, Observations, and Conclusions
Now that the process is over and done with, I understand that the process of recognizing, handling, and accommodating applications adds considerably to the Windows 8 install process, and the time required to complete it. The usual 15-18 minutes for a clean install zoomed to 65 minutes or thereabouts once my sizable collection of 200-plus applications entered the picture. Soluto reports that my boot time went up from 0:55 to 1:55 following the upgrade (something that I plan to investigate and whittle away at, if I can). But otherwise, the system is running well, my applications are working (at least, all of those I’ve checked so far), and if anything, seems more stable and responsive than it did when running Windows 7. I’ve installed Start8 to help me work on the desktop more effectively (that’s where I spend 90-plus percent of my time on the system anyway), and RecImg Manager to capture Windows 8 snapshots as backups for use in the Windows 8 “Refresh your PC” facility. Since I’ll be using this system every day henceforth, count on me to report further if and when any glitches or gotchas should make themselves known to me. But “so far, so good” is how I’d sum up my experiences so far, much to my surprise.
I’m facing an interesting issue that I’m sure is at least somewhere on the minds of fellow Windows-focused IT professionals — namely, how well an upgrade might work from Windows 7 or Vista to Windows 8 in anticipation of the upcoming GA release of Windows 8.1 (a free upgrade to those with Windows 8 already installed on their PCs). To that end, I’m planning to bite the bullet this weekend, and try the upgrade from Windows 7 to Windows 8 on my production PC. To that end, I just re-ran the Windows 8 Upgrade Advisor to see what it could tell me about the upgrade-readiness and -worthiness of that machine. Here’s what I see after running the program, which took about one minute to run to completion on my Bloomfield vintage i7 930 based PC, with its ASUS P6X58D-E motherboard and other accoutrement.
A click on the “See compatibility details” element reveals the following items, none of which looks distressing or even terribly serious:
I must say, I’m more encouraged by this result than I had initially expected to be. But in preparation for the upgrade this weekend, I’ll be making an image backup of the system as it currently stands, and also, turning it into a VM so I can keep running the same environment inside Hyper-V after the upgrade is complete, just in case — as I suspect might be more likely than this list of potential issues indicates — that some issues with the 290-odd applications I have installed on this machine might manifest after the move to Windows 8 is complete. Stay tuned: I’ll report on the results of this “big move” next Monday, October 7.
I’ve got a total of 5 out of 8 PCs in my house running Windows 8 now, and every now and then I encounter some new form of wacky Windows behavior that requires certain shenanigans to fix. I stumbled upon another interesting case in point yesterday, when I tried to establish a Remote Desktop Connection link to our Dell XPS12. When I got this machine from Dell it came with Windows 8 installed, which I proceeded to upgrade to Windows 8 Pro so that, among other things, I could use RDP to log into that machine remotely and manage updates and such from the production Windows 7 desktop I work at customarily in my home office.
Even though my XPS12 was properly configured for remote access, my connection wouldn’t stay up long enough to get through the hand-off process.
Without giving the matter too much thought, I checked the machine yesterday to make sure that Remote Access settings were properly configured. As shown in the preceding screencap, they were just what I thought they should have been, with remote connections turned on and RD-NLA turned off. However, when I tried to establish an RDP connection to that machine, I would start to go through the process of establishing a remote connection, only to have it fail before the entire process of opening the remote window and obtaining a working view of its desktop could complete. Non-plussed, I tried to establish a connection going the other way — that is, from the desktop of the XPS 12 to my production desktop — only to have it fail and hang in the same way. Bizarre!
By searching on “Windows 8 RDP fails during login” and “Windows 8 RDP fails immediately,” I learned two very interesting things I didn’t already know. First, I had to purge some outdated printer connections in the Devices and Printers entry in Control Panel, apparently because print queue and device driver connections were interfering with network access for RDP. And second, I had to make a registry hack to turn off the version of UDP that RDP uses in the Windows 8 environment as follows:
In the key at HKLM\SOFTWARE\Policies\Microsoft\WindowsNT\Terminal Services\Client\, create a DWORD named tofClientDisableUDP and assign the value “1″ (either Hex or Decimal, I used Hex) to it.
I had to remove the printer references and then restart the machine immediately after that to get them to “stay gone,” because if I didn’t restart, they would magically re-appear within 30-60 seconds of their removal. This took some careful observation and fiddling about to achieve. I found the registry hack documented on Microsoft’s social.technet pages in a thread entitled “Remote Desktop client on Windows 8 drop connection.”
To me, it all goes to show the sometimes forensic characteristics of Window troubleshooting. I’ve learned to try to characterize the symptoms as tersely as possible, and then to put Google to work to help me find information or discussions around those topics. If I keep at it long enough, as I did yesterday afternoon, I will almost always stumble my way into a workable solution. But why, oh why, I must plaintively ask, does it have to be this way? Sigh.
As of the end of August, a new version of the Windows Assessment and Deployment Kit (aka the Windows ADK) is now available for Windows 8.1 (RTM version, which presumably means it will also work with the General Availability, or GA, version scheduled for release on October 16). The download page at the MS Download Center provides a link to grab the full kit for experimentation and/or production use.
The latest ADK is ready to work with the most recent RTM release of Windows 8.1 (and presumably with the GA release, too).
Here’s a list of some of the tools available in the Windows ADK (see the ADK download page for a complete list):
1. Application Compatibility Toolkit (ACT) helps IT professionals prioritize, test, and detect compatibility issues with applications, and to find and share risk assessments with other ACT users. Visit the ACT page for more information on this tool.
2. Deployment tools: a whole raft of items to help IT professionals in customizing, managing, and deploying Windows images, such as the Deployment Imaging Servicing and Management (DISM) command line utility along with numerous DISM PowerShell cmdlets and its API, the Windows System Image Manager (Windows SIM), and OSCDIMG, a command-line tool for creating an image (.iso) file of a customized 32-bit or 64-bit version of the Windows Preinstallation Environment (PE) 3.0. See the Deployment tools page for more info.
3. User State Migration Tool (USMT): a scriptable command line tool designed for migrating user data from an older Windows installation to a newer one. The USMT home page offers more information and documentation.
4. Windows Assessment Toolkit, used to run system assessments on a single computer based on tasks that simulate user activity and examine computer state to produce metrics for various aspects of the system, and make recommendations for improvement. See the Windows Assessment Toolkit home page.
5. Windows Preinstallation Environment (Windows PE) is a minimal OS created to provide a runtime environment for preparing a computer for installation and servicing of Windows OSes. The Windows PE Technical Reference is the go-to for this outstanding and valuable Windows resource.
For those who work with Windows OSes, and plan to work with or deploy Windows 8.1, the ADK is an invaluable toolset. It’s definitely well worth the time and effort needed to inspect, learn about, and master the various components it contains. At a minimum, these items provide a baseline against which other commercial toolsets must be measured, if only because MS gives them away for free.
Earlier this afternoon, I finished a story for SearchWindowsVirtualization.com that’s currently entitled “Automation Technology in VDI Environments.” Given that it usually takes a week or two before my submissions show up online I’ll provide a link to the final version right here when it goes live (and change the title if those with editorial authority decide that something a bit different or jazzier is needed to attract reader interest). What blew me away about researching this story is the hundreds of ready-to-run scripts one can find easily online, to help automate every aspect of virtual desktop infrastructure, from initial set-up and image construction, to VM deployment, applying patches and updates, and monitoring and managing fully operational VDIs.
All you have to do to get a sense of the massive resources available for your use are to check out these mostly Hyper-V related resources online (no surprise, really, because the vast majority of these links come from Microsoft itself, in one guise or another):
- Hyper-V Scripts: A social.technet.Microsoft wiki for free PowerShell Scripts for Hyper-V; contains about 100 links to ready-to-use scripts for Hyper-V.
- Hyper-V Portal: From the same wiki, a set of resources for working with Hyper-V that includes free books, tutorials, technical info, and a whole lot more.
- Hyper-V Cmdlets in Windows PowerShell: 172 ready-to-run PowerShell scripts for most aspects of Hyper-V and VM definition, upkeep, and management.
- Script Center Gallery: Microsoft’s centralized script resources for IT professionals thousands of scripts include many relevant to Hyper-V and VDI.
- Virtualization automation with Hyper-V: Windows PowerShell Scripting (TechTarget article)
- Search on Hyper-V Scripts for more stuff than you can imagine! (Skip page 1 to get past the preceding items quickly.)
There’s lots of really great stuff here that admins are hopefully already using. If that doesn’t include you, be sure to check one or more of these items out immediately. That means today!
Microsoft is holding an invitation only press event next Monday, September 23, to announce its new generation of Surface tablets, currently known as Surface 2. Both the RT model (to which rumors currently ascribe the label “Surface 2″) and the full-blown Windows model (to which the name “Surface Pro 2″ currently sticks likewise by rumor) are supposed to get some serious upgrades. By combining interesting rumor coverage from The Verge, ZDnet, and Design&Trend, here’s what I’ve been able to piece together about the next-gen version of these devices, which appear to get about half-way to meeting the wish list I put together for the Pro model in November 2012. I’ll list what I’ve been able to learn about for each model separately, in bulleted list form (both are expected to acquire a two-step kickstand, which permits the extension to lock into two different positions rather than the current single position):
Surface 2 (Windows 8.1 RT model)
- Slated to include a faster Tegra 4 CPU
- RAM capacity will double, from 2 GB to 4 GB
- Screen resolution will increase to 1080p
- New RT OS is reportedly based on Windows 8.1, and designed to boot up, run, and shut down more quickly
Surface Pro 2 (Windows 8.1 full OS model):
- Haswell i5 CPU, with some i7 ULV models also possible.
- 8 GB RAM (now that one SO-DIMM accommodates 8 GB easily, this is a no-brainer).
- 256 and 512 GB SSD configurations should be available (don’t forget: you can talk to the Microsoft Store about special-ordering higher-end models).
- Paul Thurrott reports that battery life shold go up from 4-5 hours to as high as 7 hours (from MJF at ZDnet in her Surface Pro 2 leaks story). A new Power Cover will include a built-in, rechargeable battery pack, along with a Type Cover style keyboard, and will extend the unit’s battery life still further (by how much, however, isn’t yet known).
- A dock for the unit is widely expected to be made available, and is said to support external monitor connections, gigabit Ethernet, plus one USB 3.0 port and three USB 2.0 ports. Sources say the dock will work with both first and second generation Surface Pro models. The dock will also charge up any attached Surface Pro tablet. No pricing information is available, though.
If the Power Cover brings the Surface Pro 2 up to 8 hours of battery life or longer, I may just find myself in the market for one. I’ll be looking forward to more detailed coverage after next week’s event concludes. Stay tuned for more info.
[Notes added 9/23/2013, based on reporting from the MS announcement:
Surface 2 (Arm version, formerly Surface RT): Tegra 4 confirmed, 4 GB RAM confirmed, higher 1080p resolution confirmed, 25% better battery life, 1xUSB3.0 port. Price starts at $499.
Surface Pro 2 (x86 version, replaces Surface Pro): MS claims 75% better battery life! 4GB RAM goes with 64 or 128 GB SSDs, 8GB with 256 or 512 GB SSDs; Power Cover said to increase total battery life to ~10 hours; Docking station supports total resolution for all screens up to 3840x2160 (equal to 2x1080p in both dimensions), adds 1xUSB3.0, 3xUSB2.0, an additional mini-DisplayPort, and GbE. Price starts at $899, but no pricing for accessories disclosed yet.
There's even a Surface Music Kit -- namely a touch cover for mixing sound instead of typing text. See the Ars Technica coverage for more details.]
[More Notes from 9/25/2013, based on Paul Thurrott's excellent "Need to Know: Surface 2 and Surface Pro 2" article for WindowsITPro.
More complete pricing information available, especially for peripherals like the new Type Cover offerings, Power Cover, and dock, as well as for more advanced Surface Pro 2 models ($1,299 for 256 GB SSD/8 GB RAM, $1,799 for 512 GB SSD/8 GB RAM). Worth a read-through!]
Microsoft’s monthly Patch Tuesday updates have started to resemble motor vehicle recalls as the company once again encounters problems after releasing a public patch update.
In the September Patch Tuesday cycle, Microsoft recalled a non-security update dubbed KB2817630, which affected Microsoft Office 2013 and Office 2013 Pro. The update caused the Outlook 2013 folder pane to disappear.
The issue was caused by incompatibility between the outlook.exe and mso.dll files. The minimize button in the navigation pane will render very large and become invisible to the end user, thus causing it to disappear. Microsoft confirmed the issue in a blog post, where the company expressed “regret” for any inconvenience caused by this update, and explained how to address the problem.
For Microsoft and its pursuit of a rapid release cadence for updating software, the latest mishap with the Patch Tuesday updates might be cause for concern.
The company recently pulled several patches off its sites and offered band aid fixes. In August, Microsoft pulled the MS13-061 Exchange security update and reissued an update later in the month. In April, the company recalled security update MS13-036, which affected Windows 7 and Windows Server 2008 R2 end users, and re-released it later in the month.
The recent string of patch issues serve as a reminder to IT pros to implement them with care.
“The rule has always been to test out patches before deploying widely, and it appears that administrators have been letting that best practice lapse,” said Eric Beehler, an IT professional who offers consulting and training services with Consortio Services LLC, of Colorado Springs, Colo. “Admins just need to reset their best practices and always have their rollback plans ready, just in case.”