Windows Enterprise Desktop


May 9, 2017  3:55 PM

What’s your app priority?

Colin Steele Colin Steele Profile: Colin Steele
Enterprise mobility, VDI, Windows 10, Workspace

Applications are the key to end-user computing, but they haven’t always been the industry’s focus. Security fears around BYOD and the consumerization of IT put the spotlight on mobile device management and, later, EMM. And the flood of major software vendors into that market kept our attention there for much of the past decade.

That will change this year.

Application development, deployment and delivery are some of the top end-user computing (EUC) projects taking place in IT departments this year, according to TechTarget’s 2017 IT Priorities Survey. Let’s take a closer look at some of the app-related results.

Deploying an enterprise application is this year’s most popular mobility project. Among organizations implementing mobility, half said they will roll out at least one app this year. Collaboration apps will be a popular choice, with nearly 40% of respondents planning to deploy those.

Organizations will explore different approaches to get these apps into users’ hands. Some will build them themselves, as more than 35% plan to adopt a mobile application development platform. And 29% will use desktop or application virtualization to deliver apps to mobile devices.

Speaking of virtualization, it’s one of the most common data center projects planned for 2017. Of organizations with IT infrastructure projects in the works, 28% will implement VDI. That beats out much-hyped technologies such as converged and hyper-converged infrastructure, private cloud computing and containers. Clearly, it’s a priority to bring enterprise applications to users wherever they are, on whatever devices they have.

On the desktop side, more than 46% of organizations that have projects planned this year will deploy or migrate to Windows 10. Applications dominate the rest of the list, however, with software as a service, app and desktop virtualization, and cloud apps all garnering at least 25%. IT departments seem content to stick to these more traditional technologies; only 7% of respondents plan to deploy workspace suites, a new approach to delivering and managing all of a user’s applications and data across all of his devices.

Management and security are still important and always will be. Almost 40% of organizations with a mobility project will deploy enterprise mobility management (EMM) this year. But it’s applications that will drive end-user computing growth.

This post originally appeared in the May 2017 issue of Access Magazine.

May 8, 2017  12:25 PM

Insider Win10 UWP File Explorer

Ed Tittel Ed Tittel Profile: Ed Tittel
UWP, Windows 10

Here’s an odd and interesting bit of Windows trivia for you. Windows 10 Insider Builds since 15063 (arrived 3/20/2017) include a UWP version of File Explorer. It’s not immediately usable without creating a special shortcut, though. If you’re willing to cut’n’paste a specific and cryptic string to define one, the Insider Win10 UWP File Explorer is yours to play with. That string is:

explorer shell:AppsFolder\c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App

Be careful if the string spans more than one line. If so, paste the string into a text editor and remove any spurious linefeeds (there shouldn’t be any). YMMV, depending on which browser you use. I pasted it as a continuous string from my source, so you should be able to grab and use it that way, too. My source, BTW, is a tip that appeared at onMSFT.com  on 5/6/17.

What Does Insider Win10 UWP File Explorer  Look Like?

If all goes well with your shortcut creation, you’ll see something like this on your Windows 10 Insider desktop:

Insider Win10 UWP File Explorer

The UI is greatly stripped down and simplified in UWP File Explorer. I’m curious, but by no means ready to switch over from the old version.

Playing around with this version of File Explorer, I make numerous immediate observations:
1. It’s greatly stripped down from the explorer.exe version. There are only minimal display controls (icons at lower right include only list and icon view, a simplified checkbox selection capability, and limited “other” options under the ellipsis at furthest bottom right).
2. I really miss the ability to display file details, such as size, creation/modification dates, and so forth.
3. I likewise miss the ribbon with its extensive, context-sensitive controls.
4. The search function is slow and seems a bit cumbersome (I use VoidTools Everything anyway, so I’m spoiled).

Overall, this earliest version seems more like a throwaway experiment or a toy implementation, rather than a serious contender to replace the current heavyweight  version of File Explorer. But with Windows S looming and UWP the main UI for touch and limited-capability versions of Windows I don’t expect things to stay that way for long. It’s interesting though, and worth checking out, for those who have an interest in such things.

Build the Shortcut for Insider Win10 UWP File Explorer

The quickest way to build the shortcut for this version of Explorer is as follows:

1. Right-click the desktop background on Windows 10 Insider
2. Select “New” –> Shortcut from the resulting pop-up menus
3. Paste the string into the location box in the Create Shortcut window, then click next.

That’s it. The shortcut will appear on your desktop. Double-click same to launch the Insider Win10 UWP File Explorer. Enjoy!


May 5, 2017  11:27 AM

Fix CCleaner Install Hang

Ed Tittel Ed Tittel Profile: Ed Tittel

In rebuilding my Windows 10 Insider test desktop, I’ve been re-installing my usual toolbox of Windows apps and applications. Chief among the latter is Piriform’s CCleaner, a long-time go-to for cleaning up file clutter on Windows PCs. This time around while installing CCleaner, I ran into something I’ve never encountered before. As I fired off the installer, it got to about 10% complete and then hung. I let it sit for 10 minutes and when the progress bar hadn’t moved I realized something was wrong. I searched Google for “CCleaner install hangs Windows 10” and found lots of helpful information online. For me, the best way to fix CCleaner Install hang appeared in a Piriform Forums post entitled “[Solution] When CCleaner won’t install or download (Windows).”

How Best to Fix CCleaner Install Hang

The forum post explains a great many techniques for resolving download or install problems. For me, the tip that did the trick read “Make sure CCleaner isn’t already running. To find out if it is, open Task Manager to see if it’s in the list of running processes.” I checked, and sure enough, I saw not one, but two instances of CCleaner.exe on the alphabetical list (by process name) on the Details pane therein.

Fix CCleaner Install Hang

Normally, one sees only a single CCleaner.exe or CCleaner64.exe running in Task Manager. On my test machine, I saw 2!

I right-clicked each of those two items, and selected “End Task” from the resulting pop-up menu. Then, when I relaunched the installer, it immediately completed the job. The whole thing was done in under 30 seconds as has been typical on that and other machines for years. I can only speculate I double-double-clicked when launching the installer, and thus and had two instances of the installer running at the same time. The program wisely chose to forgo honoring my erroneous request for two installs, but I didn’t understand that’s what I was seeing until I looked into Task Manager to see what was going on.

Overall, the afore-linked Forum article is a good one. Might be a good idea to bookmark it in case you, too, ever fall prey to some CCleaner install or download difficulties. It worked nicely for me, so it could also do likewise for you.


May 3, 2017  12:30 PM

Troubleshooting Windows Recovery Environment (WinRE)

Ed Tittel Ed Tittel Profile: Ed Tittel
system recovery, Windows 10

In resuscitating my Insider Preview desktop, I’ve been fixing dual boot and Windows Recovery (WinRE). (Links to previous posts: Balky Mobo, Clean Install.) Apparently, something about dual boot interferes with WinRE’s normal operation. It usually lurks in the background, ready to take over if Windows boot or startup issues appear. Dual booting, however, appears not just to disable WinRE. Alas, it also breaks its normal re-enablement process. In researching this, I’ve discovered a couple of peachy resources, and found a nice fix. The resources help with troubleshooting Windows Recovery Environment issues, so I share them here.

Here’s what you see on a typical Windows 10 PC, after you set up dual boot then run the REAgentC command. For those unfamiliar with that command, it’s used to configure a WinRE image and “push-button reset recovery.” Happily, that quote comes from one of my two nonpareil resources on WinRE.

Troubleshooting Windows Recovery Environment

After setting up dual-boot on Win10 on my PC, both installations show status as “Disabled.” Time for some troubleshooting!

Tools for Troubleshooting Windows Recovery Environment

First comes the “official resource” — the MSDN Hardware Dev Center’s 5/4/2016 documentation. It’s a multi-part opus. Thus, I provide links to each part, along with a brief explanation. Helpfully, the first item defines what WinRE is and does:

Windows Recovery Environment (WinRE) is a recovery environment that can repair common causes of unbootable operating systems. WinRE is based on Windows Preinstallation Environment (Windows PE), and can be customized with additional drivers, languages, Windows PE Optional Components, and other troubleshooting and diagnostic tools. By default, WinRE is preloaded into the Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) and Windows Server 2016 installations.

WinRE produces a familiar “alternate boot” screen during Windows boot-up. It can come when called, or when the primary active install of  Windows 10 can’t or won’t boot:

Troubleshooting Windows Recovery Environment

When WinRE kicks in, this is what you see on your PC’s display.

Tool 1: MSDN/Hardware Dev Center WinRE Reference

Here are WinRE items from Microsoft. Key sections are flagged with an asterisk (*):

Windows Recovery Environment (Windows RE)*: general WinRE overview.
Customize Windows RE: manipulate a WinRE image (using DISM). Include languages, packages, drivers, and custom  diagnostic or troubleshooting tools.
Add custom tool to the Windows RE boot options menu: mount and configure a WinRE image.
Add hardware recovery button to start Windows RE: simplified process introduced with Windows 10.
Deploy Windows RE: deploy WinRE to a new computer including BIOS and UEFI options.
Push-button reset: for OEMs wanting push-button reset features for computer systems.
REAgentC command-line options*: command-line tool for WinRE setup and management.
ResetConfig XML reference: XML elements in the ResetConfig.xml file for push-button reset.
Windows RE troubleshooting features: Recovering from startup failures and WinRE troubleshooting utilities. Automatic Repair, System image recovery, Command Prompt, and more.

In working with reagentc.exe, I found the overview and the command line options elements useful and germane. Those who wish to customize WinRE will find the other sections helpful, too.

Tool 2: TeraByte KB Article 587

This gem is entitled “Repairing the Windows Recovery Environment (WinRE).” It’s both long and incredibly detailed. Believe me, that’s what you want when exploring various ways to get WinRE working on a Windows PC.

For me, the fix that worked appears in a section entitled “Reset the ReAgent.xml File.” It shows how to edit that configuration file. ReAgent.xml drives a running Windows image’s set-up for and understanding of WinRE. By changing XML elements as this section recommends, I was able to run reagentc /enable successfully. This meant that the tool rebuilt my Windows Recovery environment and made changes needed to get it working again.

But the article covers a range of ways to repair WinRE. First, it explains various ways that WinRE might fail. These include:

  • WinRE disabled
  • BCD file not correctly configured to boot WinRE
  • missing or misplaced WinRE.wim file
  • wonky WinRE configuration file (ReAgent.xml)

Repairs discussed include

  • disabling and re-enabling WinRE
  • correcting invalid BCD file references to WinRE
  • moving WinRE to the right path/location
  • resetting the ReAgent.xml file
  • finding and restoring the Winre.wim file

Each repair provides sufficient detail to work your way through it. Even better, each section is illustrated with examples. Bottom line: I was able to diagnose and fix my issues using this Guide. ‘Nuff said!


May 1, 2017  3:51 PM

Insider Preview Clean Install Confers Insights

Ed Tittel Ed Tittel Profile: Ed Tittel
Clean install, Windows 10

As I explained in a recent blog post, I’m busy rebuilding my Win10 desktop test PC. (Details: “Balky Mobo Caused Insider Boot Woes,” 4/28/17.) For the past few hours, I’ve been clean installing the Insider Preview version of Windows 10 Enterprise. Working through that process, I observe that the Insider Preview clean install confers insights worth sharing. I’d been updating the previous installation for over two years, so that’s saying a lot.

What impelled the clean install? I had to switch motherboards because the previous occupant of the test system went south. That is, after power on, I could only get it to give me an error code for “SATA problem” (A2) or “USB problem” (99). It’s hard to use a system when you can’t even get into the BIOS/UEFI! Thus, I had to rip out a failing MSI z87-G45 motherboard.

After shopping around, I replaced the old unit with an Asrock z97 Fatal1ty Killer. That meant I had to switch from a Samsung 840 EVO mSATA SSD, to a Samsung 951 m.2 NVMe SSD in the new board. Alas, the Insider Preview OS on that dual boot machine was affected. So that’s why I performed a clean install this time around. A “back to bare metal” situation argues pretty convincingly for such a move anyway.

Insider Preview Clean Install Confers Insights

This are the drivers the Windows installer found on its own in setting up the test system.
[Click image to see full-size view]

If Insider Preview Clean Install Confers Insights, What Are They?

I got my good friend and occasional collaborator, Kari the Finn, to build me an ISO for the latest Insider Preview build (16184).  (Kari’s the author of the recent “Windows 10 Custom ISO” 6-part-series of blog posts here, and a true master of the Windows image arts. Here are links to Parts 1234 56.) This morning, I used the latest version of Rufus (2.14) to build a bootable USB flash drive from that ISO, being careful to select the UEFI only option that perforce uses FAT32 formatting for the install media.

Overall, the install process proceeded without a single hitch. I did notice some changes in its overall speed. In fact, the first phase is much, much faster. The last time I clean-installed Windows 10 on that machine back in late 2014, it took 20-25 minutes to work through that process. This time, I was done in less than 15 minutes. The Enterprise installer is much more aware of its capabilities now, too. When asking for a Microsoft account for account set-up, it wouldn’t let me use my Yahoo! email address, and it was smart enough to know that neither edtittel.com nor spamarrest.com would permit me to draw on a domain server or DNS connection. In fact, I had to set up a local account to get through initial install (my preference anyway). After the initial install was done, I linked to my primary MS account through the Accounts page in Settings without difficulty.

How Clean Install Has Changed Since Then…

This time around, Windows 10 did a bang-up job with device drivers, too. Earlier, the Windows Installer couldn’t recognize the Killer 2200 Ethernet adapter on the MSI motherboard (also present on the Asrock, BTW). I needed a USB GbE dongle (a $21 Startech model still available from Newegg) to bring my network connection back to life. In fact, all of the drivers I needed showed up after the latest clean install on that machine. I only had to update these exceptions:

  1. Logitech SetPoint for my m325 mouse.
  2. Dell E228WFP monitor (almost time to replace this guy, too)
  3. Intel devices 0C01 (PCI express controller), 0C00 (DRAM controller), and 8CA2 (SMB host controller)
  4. Intel Management Engine Interface (MEI)
  5. Nvidia display driver

None of this stuff was terribly hard to run down, and I’ve seldom seen any install get the Intel stuff completely right anyway. A quick check into Reliability Monitor shows me the system tried to grab current drivers for all system items (shown in the preceding screen grab). For some items my tool of choice (Windows Update MiniTool, or WUMT) was better informed or up-to-date than MS. But everything was working, with no unknown devices in Device Manager.

And then, there’s the usual tweaking and clean-up that follows any clean install. I had to change the network status from Public to Private, and join a Homegroup, before Remote Access worked. Usual tweaks in File Explorer options must come via the Microsoft account, because they were already set. Ninite helps with the tedium of adding back in most of my common apps, but not with more specialized tools. I still have a few hours left to go before things will be just the way I like them, and my toolbox fully restocked. Wish me luck!


April 28, 2017  11:53 AM

Balky Mobo Caused Insider Boot Woes

Ed Tittel Ed Tittel Profile: Ed Tittel

I just got finished rebuilding my test desktop Windows Insider PC. This system was set up for dual boot, actually. It could boot either Current Branch (1703/Build 15063) or Insider Preview (Enterprise Build 16179). I’d been having terrible boot issues lately trying to manage both boots. That’s because the Windows Installer happily trashes dual-boot setups when it performs a feature upgrade. That makes rebuilding the boot files and boot configuration data a necessary follow-up. Given the frequency of feature upgrades in the Insider Program, that drove me bonkers. When I replaced some hardware, I determined that my (former) balky mobo caused Insider boot woes galore. A motherboard swap set things right. Let  me explain…

How Do I Know a Balky Mobo Caused Insider Boot Woes?

I’d been having problems getting the system to boot into the BIOS for some time. Even the maker’s “Boot to UEFI” function was hit or miss. I ran that MSI Z87-G45 board for just over three years, but recently it started getting wonky. Eventually, I found myself in a situation where if I tried to boot with any SATA drives attached, the board would hang with a SATA device error code (A2). But with no SATA devices attached, it would hang with a USB error code instead (99). Ouch!

Alas, you can’t boot a system that can’t get past the error codes. That’s when I decided to purchase a new motherboard, so I could reclaim most of the components at a modest cost. Because I chose an Asrock Fatal1ty Z97 Killer, I also decided to spring for an M.2 NVMe SSD (a Samsung 951) to replace the mSATA Samsung 840 EVO I’d been using in the previous build. I confirmed my initial diagnosis when the new build fired right up, upon inserting the CPU, RAM, and the 1703 boot drive into the new motherboard. I didn’t even have to reinstall Windows 10, though I did have to go through some contortions to get the new install activated. For the first time, the activation troubleshooter didn’t automatically activate my install when I clicked the “hardware changes” button. I’m guessing it was because I was using an MSDN key that had been auto-upgraded from Windows 8. But I still have MSDN keys for Windows 10 Pro available, so burned another one of those…

Balky Mobo Caused Insider Boot Woes

With a combination of nice features and a good price ($140), I pick the Asrock Z97 Fatal1ty Killer.

Not Quite Home Just Yet, Though

I switched from an mSATA to an NVMe SSD for the other part of the dual boot: Windows 10 Enterprise Insider Preview. That meant I wanted to perform a clean install to a brand-new drive. Wouldn’t you know it? Microsoft has turned off Insider Preview ISO downloads at the moment, and I can’t find them anywhere for that reason. Even the usually infallible HeiDoc.Net Windows and Office ISO Downloader comes up blank for Insider Preview items right now. No sooner than is one problem solved, than another jumps up to take its place. To be continued…


April 27, 2017  9:01 AM

Citrix CEO talks H-1B visas, other Trump proposals

Alyssa Provazza Alyssa Provazza Profile: Alyssa Provazza
Citrix, H-1B visas, Microsoft

As President Donald Trump’s administration considers changes to tax, healthcare and immigration laws, large technology companies are primed to feel some of the biggest effects.

The CEO of one such organization, Citrix, discussed the potential fallout in an interview with SearchEnterpriseDesktop.

“There’s a lot of anticipation,” Kirill Tatarinov said.

That’s especially true regarding the rules around H-1B visas, which allow U.S. companies to temporarily employ foreign workers in specialty careers such as technology. These visas are distributed to candidates based on a random computer-generated lottery system. Last month, the U.S. Citizenship and Immigration Services suspended the fast-tracking process for H-1B approval, which lets applicants pay a fee to get a faster response to their applications.

“Expectations are very high for — I would characterize it as ‘modernization’ of — H-1B visas,” Tatarinov said. “We employ highly educated, highly paid workers that were brought up in countries other than the United States. Citrix, just like frankly most other native high-tech U.S.-based companies, would benefit from something other than a lottery.”

In terms of healthcare, Citrix employs about 4,000 people in the U.S. who would feel the waves of any changes there.

“It’s not insignificant,” Tatarinov said. “Expectations are still high, despite what transpired, in healthcare reform that impacts everybody.”

Republicans in March shelved a first attempt at a new healthcare bill that would repeal and replace the Affordable Care Act, but the White House said just last week that it would continue those efforts.

Tatarinov also discussed Citrix’s turnaround over the past year and its partnership with Microsoft. Check out more of the interview on SearchVirtualDesktop.


April 26, 2017  10:25 AM

Build 15063 DISM Fix Available

Ed Tittel Ed Tittel Profile: Ed Tittel
DISM, Windows 10, Workarounds

If you’re running the Current Branch release for Windows 10 — namely, Build 15063 — you may have a DISM problem. Some tangible percentage of such installs will puke if you run DISM /checkhealth on the runtime image. But with a Build 15063 DISM fix available, you can repair this anomaly yourself. Here’s what the symptoms look like:

Build 15063 DISM Fix Available

SFC finds nothing amiss, but DISM erroneously thinks something’s off in the Component Store.</>

The key elements for these peculiar circumstances are:

  • SFC /scannow completes without a hitch
  • DISM /online /cleanup-image /checkhealth reports repairable component store issues
  • DISM … /restorehealth cannot fix those issues, no matter what /source you use (I’ve tried them all)
  • The DISM log file reports a variety of (mostly driver-related) files MIA as the cause of the errors

With a Build 15063 DISM Fix Available, What’s the Deal?

Warning! Some registry editing will be required, so prudence dictates you back up your registry before proceeding. But that editing simply involves deleting these two specific keys. First, reset permissions on each key to give Administrators full access before entering the delete command, or that command will fail.:


Key 1:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]


Key 2:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

With those edits performed, the DISM problem will vanish. And while cleaning this up might seem like a bit of over-the-top OCD because it restores DISM to proper operation, it actually has real value. That’s because should the running Windows image actually need some kind of real repair, DISM will then be able to perform such tasks.

[Note: I’d like to give a shout-out to the relentless expert Win10 tweakers at TenForums.com, particularly user gommace from posts #39 and 40 in this thread: Creators update component store shows corruption but unable to repair. Be sure to read the whole thread to get a sense of potential gotchas that applying this fix could invite. Most of the more senior members of the forum are electing to wait for MS to fix this issue, as I am myself (except for the test system where I tried out this fix).]


April 24, 2017  10:38 AM

Monitor Upgrade Saves on Money and Energy

Ed Tittel Ed Tittel Profile: Ed Tittel
Dual monitors, Hardware Upgrade, Windows 10

Just recently, I decided it was time to upgrade my dual desktop monitors. I’ve been running a pair of Dell 27″ monitors for over 8 years now. They’re identical 2707 WFP UltraSharp monitors, and turn ten years old this year. When I purchased the first member of that pair in 2007/2008, I paid over $700 to put it on my desk. When I purchased the second member of that pair, it set me back just almost $570 including shipping. In switching over to a pair of Dell Ultrasharp 2717 monitors this weekend, I paid just under $960 for both of them (less than $480 apiece) all told. My monitor upgrade saves on money and energy, and buys a lot more for less money. Let me explain…

Monitor Upgrade Saves on Money and EnergyMonitor Upgrade Saves on Money and Energy

2707 left, 2717 right

Why My Monitor Upgrade Saves on Money and Energy

It just goes to show that the relentless forward march of technology keeps delivering more bang for our bucks. The original monitors measured 25″ x 16.5″ with a nearly 1″ bezel all the way around. The new ones measure 23.75″ x under 14″ with a 5/8″ bezel. I see the same amount of screen real estate while gaining back some space on my desk. Even better, energy consumption is waaaay down. The 2707s consumed 125W at peak graphics load, while the 2717s only suck up 28W likewise. That’s a 77.6% reduction! Over time, that will make a huge difference. That’s because I routinely run my monitors 14 or more hours a day during the week, and at least 10 hours a day on weekends.

According to RapidTables Energy Consumption Calculator, the old monitors consumed around 60 kWh per month. But the new ones will come in under 14 kWh. At 10.2 cents per kWh from my provider, monthly cost drops from $6.12 to $1.37, for a savings of $4.75. Let’s assume I keep these monitors for 10 years like I did their predecessors. If so, I’ll have recovered over half their purchase price ($570) by the time the next generation takes over. Not enough to justify the outlay by itself, but not a bad dividend for an overdue upgrade.

But Wait … There’s More

The old monitors offered up 1980×1200 resolution, while the new ones deliver 2560×1440. The new monitors also offer a 5 ms response time, while the old ones clocked in at just slightly less (6 ms). The old ones included a built-in USB 2.0 hub and an SD card reader. The new ones drop the card reader, but offer 4 ports of USB 3.0 access instead. I also like the switch from VGA/DVI-D video ports to a single HDMI port, one mini-DisplayPort (DP), and three full-sized DP ports (2 in, 1 out, for daisy-chaining).

Hooking up the new monitors was also considerably easier, though Windows didn’t recognize the screens until I reinstalled the latest Nvidia driver (version 381.65). But that’s because I also installed an MSI Armor GeForce GTX 1070 to drive them. And although I already had 381.65 installed on that machine to drive the GTX 750 Ti already in place, Windows wasn’t happy until it was uninstalled and reinstalled on my production PC. Only then did it recognize the second monitor, and allow me to extend my desktop to encompass both together.

All in all, my monitor upgrade saves on money and energy, but also delivers higher resolution plus more and better connectivity options. A good deal, all the way around.


April 21, 2017  3:41 PM

A smorgasbord of apps

Colin Steele Colin Steele Profile: Colin Steele
Apple iOS, Application delivery, google android, Windows 10, Windows desktop

I love ice cream.

There’s a small stand down the street from my house that I frequent during the summer. I spend my time in line staring at the dozens of flavors, pondering my options. Mint chocolate chip? Ooh, that sounds good. I could go for cookie dough, too. Or maybe coffee …

But when the time comes to order, I always get the same thing: chocolate peanut butter. It just works for me.

IT administrators do not have the same luxury when it comes to delivering applications to end users. Their options are nearly as plentiful as the flavors at an ice cream stand, but in this era of the mobile, distributed workforce, there’s no single choice that’s right for every situation.

Windows desktops and applications are still the foundation of how workers do their jobs. And with Windows 10, which runs on tablets as well as desktops, Microsoft made significant progress toward bringing the native Windows experience to mobile users. But what about all those workers using their Apple iOS and Google Android devices for work?

Even though most major enterprise vendors make mobile or web versions of their software available, custom legacy applications are often stuck on Windows. Small and medium-sized businesses typically don’t have the resources to build their own mobile apps. And the use of desktop and application virtualization to deliver Windows apps to smartphones, with their small and touch-enabled screens, can create a frustrating user experience. Application refactoring is an option for making virtualized Windows apps touchscreen-friendly, but it’s a niche technology in an unproven market.

Add in desktops and applications as a service, cloud apps and file-sharing platforms, and there’s quite the menu of application delivery flavors to choose from. Picking a favorite and ordering it every time won’t work these days. IT must mix and match to meet the needs of both the business and its users.

This post originally appeared in the April 2017 issue of Access Magazine.


Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: