Windows Enterprise Desktop

July 2, 2018  9:29 PM

Strange Display Behavior Gets Workarounds

Ed Tittel Ed Tittel Profile: Ed Tittel
Display resolution, Troubleshooting, Windows 10

Every now and then, Windows 10 gets a little wonky. Ever since the 6/12 Cumulative Update (KB4284835) I’ve been dealing with a strange display behavior. It only happens on my right-hand display. I’ve not been able to figure what’s causing it. For a while, a fix eluded my grasp. Along the way, though, this strange display behavior gets workarounds that have kept me going. Let me explain…

Strange Display Behavior Gets Workarounds.settings

Reset the resolution, then keep those changes, maintaining the original aspect ratio. Repeat, but revert the resolution back to its original values.
[Click image for full-sized view.]

How Exactly Strange Display Behavior Gets Workarounds

If I maximize a window on my right-hand display (I have a pair of Dell 2717D 2560×1440 monitors), the top portion of the window is not rendered. Because that’s where the window controls reside that means I can’t grapple with them directly. If I click in the region where they’re supposed to be, the cursor behaves just as it would if no window was present in that space. Thus, not only can I not see the controls, the screen mapping doesn’t detect them either. Initially this led to my first workaround. Because I couldn’t access the window directly, I right-clicked on the corresponding icon in the Taskbar. This let me choose “Close window” from among the various options presented. Crude, but effective in dispelling the window.

A little research showed me that by clicking the Alt+Space keys, I could use the Restore option to switch back from full-screen mode to the original size of the window before it had been maximized. Because this has the useful property of restoring the window controls, with URL box, menus, and so forth for my web browsers (my most frequently-used applications by far) or the Ribbon (for MS Office components), this pretty much puts me entirely back to rights. And thus, this quickly became my workaround of choice.

Display Property Ju-Jitsu: Fix or Just Another Workaround?

I was chatting with Kari the Finn today (he’s my partner in Win10.Guru, and a general sounding board for all things Windows) and he came up with another solution. I can’t tell yet if it’s just another workaround or a real fix. That’s because I can no longer get my apps to misbehave by dropping the top portion of a maximized window. The simple version of his fix is best understood in recipe form:

1. Right-click on the desktop background
2. Select Display Settings from the resulting pop-up menu
3. Pick another resolution for the wonky display
4. Click keep changes
5. Repeat steps 2-4, returning the display to its original resolution

The real “trick” however, is to pick an alternate resolution that maintains the same aspect ratio as the original resolution. Mine was 2560×1440 (aspect ratio of 1.78, or 16:9), so I chose 1920×1080 (same aspect ratio 16:9). A quick save, then a quick restore, with “Keep changes” at each step removed all symptoms of this problem.

If it comes back again (hasn’t so far) it’s just another workaround. So far, though, it works and acts like a fix. Very interesting!

June 27, 2018  12:12 PM

WUMT Resolves Update Woes Yet Again

Ed Tittel Ed Tittel Profile: Ed Tittel
Troubleshooting, Windows 10, Windows Update, Windows Update Management

Yesterday, Microsoft released Cumulative Update KB4284848. As usual, I updated all eligible machines once I noticed the update was available (this morning). On all six PCs, the update was attempted. For five of them, it succeeded without difficulty. On the sixth, however, things quickly became interesting. First, WU had difficulty scanning for this update. But even after I downloaded the .MSU from the Microsoft Update Catalog, it stalled out at “Checking for updates.” And alas, it never got around to installing anything. Thus, I turned to the Windows Update MiniTool, aka WUMT, to see if it might help before attempting more serious WU repairs. Happily, WUMT resolves update woes yet again. It managed to download and install KB4284848 without difficulty.

WUMT Resolves Update Woes Yet Again.screencap

WUMT Update History shows all applied updates since the last Feature Upgrade.
[Click image for full-sized view.]

How WUMT Resolves Update Woes Yet Again

Obviously, something odd was up with Windows Update on this PC. Specifically, the update check function seemed stymied somehow. This is the first time I’ve seen a manual catalog-based update fail because its own built-in update checks couldn’t (or wouldn’t) complete. WUMT uses a different method to interrogate the WU servers. And apparently, WUMT succeeded even when the built-in update functions weren’t working properly.

Even so, WUMT didn’t report on the download of KB4284848, either. It simply showed progress bars for Updates 1 and 2, but didn’t report on download progress in the status bar as it is normal behavior. There’s no doubt that something odd and interesting was up on the T520.

FWIW, I’m glad to see that WUMT was able to grab and install the update even when Windows Update itself got stuck. It’s still taking minutes for an update check to complete on that machine now, but it is working. But, as is also usual, WUMT completes faster. If you don’t already have a copy of the free WUMT program in your toolbox, grab a copy right now. It’s completely portable and does not require installation. [Note: download link is to MajorGeeks, a reliable and virus-free purveyor of all kinds of great Windows downloads. For more information on WUMT, see my mini-review of this tool at Win10.Guru. Great stuff!]

June 25, 2018  9:37 AM

MS Answers Offers 1803 Networking Resolution

Ed Tittel Ed Tittel Profile: Ed Tittel
Network administration, Networking, Windows 10

The latest version of Windows 10, 1803, made its public debut on April 30. By May 9, I’d already published a blog post here entitled “Bring Back Basic Win10 1803 Networking.” It recited some relatively sure-fire methods for restoring LAN nodes to visibility in File Explorer. But the complaints about simple networking have continued unabated online at TenForums, SuperUser, social.MS and answers.MS. As of late last week, Microsoft Agent Justin Emb of MS Answers offers 1803 networking resolution. Here’s a snapshot of his June 21 response:

MS Answers Offers 1803 Networking Resolution.response

Resetting startup type for a plethora of networking related services in 1803 offers some hope of relief, according to MS Answers.

Exactly How MS Answers Offers 1803 Networking Resolution

While the MS Answers response labels this as a “home networking” issue, it actually applies to all Win10 networks where a formal network infrastrucutre is absent. By that I mean no local or cloud-based domain controllers, no local DNS, no Windows Server based file and print services. That describes a lot of small business networks as well as home networks, so it’s a bigger population than one might think.

Personally, I didn’t have any trouble connecting over the LAN from one node to another after upgrading the 1803. My issue was node visibility.  That means seeing all “live” Win10 nodes on the network at any given moment. For me, the only service changes necessary were those for the Function Discovery items in the MS Answers Q&A item.

Those who do experience network issues with 1803 might want to try resetting startup type for both Function Discovery items. If that doesn’t fix things, make sure the local network is set to “Private” status. Ditto for network discovery and file and printer sharing in the Network and Sharing Center. Some users also report that turning on Public folder sharing under All Networks makes networks visible. If all else fails, try the whole gamut listed above.

One more thing: I was able to confirm by experiment that a restart is necessary for machines whose settings are changed make them visible to the network. If you make some or all of the aforementioned changes but nodes still remain invisible on the LAN in File Explorer, try a restart. That may do the trick!

June 22, 2018  5:34 PM

Win10 Hyper-V VMs Benefit from More VRAM

Ed Tittel Ed Tittel Profile: Ed Tittel
Hyper-V, VM Performance, Windows 10

I saw a fascinating article from long-time Windows maven Ed Bott this morning at ZDNet. It exhorts users to “Fine-tune memory usage” for best results when working with Hyper-V VMs. In that story, he vindicates a long-held belief of mine, based on repeated observation. That belief is that indeed, Win10 Hyper-V VMs benefit from more VRAM (virtual RAM) in their configurations. By default the Hyper-V Quick Create utility creates VMs with memory allocations of 2 GB. Bott suggests, and I concur, that this might be too little memory for at least some (if not most) VMs.

How Do Win10 Hyper-V VMs Benefit from More VRAM?

Mostly, they benefit with improved performance. Bott observes that the default allocation of 2GB “is not enough for acceptable performance.” My observations confirm this assertion when a VM is going to run demanding applications or heavy workloads. If the sole purpose of a VM is to familiarize yourself with and explore a new or preview Windows release, 2 GB is actually OK. Bott recommends that VMs be allocated about half of the physical RAM on their host PCs. Thus, he says a PC with 8 GB of physical RAM should have a minimum of 4GB VRAM for VMs, one with 16 GB gets 8 GB minimums, 32 GB gets 16 GB minimums, and so on. I think this may be overkill, but it will depend on what you’re going to do with those VMs. Certainly, it’s not incorrect to throw a bigger RAM allocation at a VM that’s lagging or dragging noticeably.

Memory allocation in Hyper-V is a min-max assignment: you set both values. On Hyper-V you use dynamic memory by default. This starts the VM at the minimum allocation, but adjusts upward as it needs it, until it hits the maximum. If dynamic memory isn’t enabled, Hyper-V allocates the amount shown in the RAM box at the top of the Memory setting pane and that’s that (no change in allocation occurs at runtime).

Win10 Hyper-V VMs Benefit from More VRAM.RAMsettings

Dynamic Memory is enabled (checked) by default, though you can alter the min/max values as you see fit.
[Click image for full-sized view.]

More About Hyper-V Quick Create

I learned the hard way that it’s probably best to work from a local OS ISO image. In other words, build your VM from an image obtained using the Media Creation Tool, MSDN, or some other source. The Developer image that the tool makes available by default is 12.73 GB in size. This is much bigger than bare-bones OS images, because it includes Visual Studio and debugging tools galore. It takes some time to download, longer to verify the image, and still longer to extract the virtual hard disk. I spent several hours waiting for this process to complete to see what was involved. Suffice it to say that exercizing this capability makes an excellent CPU and I/O stress test for most PCs. Ouch!

All this said, Quick Create is a great tool and makes it simple, fast and easy to create new VMs. If you use your own ISOs or other local sources to build those VMs you won’t be subject to the delays that come along with using the Microsoft-supplied default.

[Note Added 6/23/2018: More Good Provisioning Info]

In response to this blog post and its impetus (Ed Bott’s ZDnet article), my good friend and business partner Kari Finn wrote a more nuanced post describing the ins and outs of provisioning Windows 10 VMs. He argues against leaving dynamic memory enabled and urges users to provide enough RAM in the static allocation to cover added needs for things like upgrading Windows itself and apps that need to run within the VM itself. He also digs into virtual CPU provisioning, a VM resource on par with memory for ensuring best performance. Check it out at: Hyper-V, Virtual RAM and Virtual CPUs over at Win10.Guru. Good stuff!

June 20, 2018  1:24 PM

UWP Win10 Sticky Notes Backup

Ed Tittel Ed Tittel Profile: Ed Tittel
Sticky notes, Windows 10

Slowly but surely, I’m learning to like the new Universal Windows Platform (aka Microsoft Store) version of Sticky Notes in Windows 10. I’ve learned to right click on its entry in the Taskbar to make it disappear from the desktop when I’m not using it. But otherwise, it’s a pretty handy (and attractive) little tool. I entrust it with enough information that I want to make sure it remains available to me, no matter what. That’s why I was tickled to see Sergey Tkachenko’s WinAero story on the tool this morning. Entitled “Backup and Restore Sticky Notes in Windows 10,” it zeroes in on some simple essentials. That’s why I can present UWP Win10 Sticky Notes backup in a single statement: copy the file named plum.sqlite to a safe place! It’s just that easy.

UWP Win10 Sticky Notes Backup.everything

Getting to the file is most of the work. But if you make a copy and keep it on another drive (or UFD), you can restore it by copying it into its home directory.
[Click image for full-sized view.]

Making a UWP Win10 Sticky Notes Backup

The trickiest part to making the backup is navigating to the file. It resides deep in the AppData file hierarchy at:

Because the filename is unique, you can use either File Explorer or another search tool to look for it on your Windows drive. I use Voidtools Everything for my searching. It found the file as soon as I’d finished typing most of its name. File Explorer, OTOH, took almost a minute to run it down (on a Skylake i7 PC with 32 GB RAM). Need I say more?

A quick right-click to copy the file to another drive and my backup was complete. Interestingly, when I opened the file in NotePad++, I also observed that you can see multiple versions back inside the plum.sqlite file as well. This could be useful if you ever wanted to go back in time on the contents of the file (the plain text portion shows up as plain text, so you can cut’n’paste it into another file in NotePad++, if you like). Good stuff.

June 18, 2018  4:20 PM

Grab New DriverStore Explorer from GitHub

Ed Tittel Ed Tittel Profile: Ed Tittel
Device drivers, Hardware Drivers, Windows 10

Over the years I’ve written repeatedly about a terrrific tool from ace developers Kannan Ramanathan and Teddy Zhang. It’s called DriverStore Explorer, also known by its executable name: RAPR.exe. A few years back this open source project moved from Microsoft’s CodePlex to GitHub. This great little tool looks up and organizes all of the device drivers in the Windows OS DriverStore. This resides in %windir%\System32\DriverStore\FileRepository, and is far too often home to obsolete and duplicated device drivers. Simply put, DriverStore Explorer remains the best tool for identifying unneeded drivers, and getting rid of those you don’t want. But because there are multiple versions floating around the web, be sure to grab new DriverStore Explorer from GitHub using its Latest Version link. As I write this blog post, that version is number 0.9.10, as shown in the About information on this screenshot:

Grab DriverStore Explorer from GitHub.about

These days, you need only click the “Select Old Drivers” button in RAPR.EXE and it does the rest. You can see it has ID’d older Nvidia display drivers — a common source of DriverStore congestion — for removal.
[Click image to see full-sized view]

Why Not Grab DriverStore Explorer from GitHub?

I started using RAPR.exe back in 2011 (here’s a link to my original blog post about it, based on version 0.5). In the meantime, I’ve mentioned the program no less than 15 times here at Windows Enterprise Desktop, other TechTarget online properties, and in writings for outlets that include ComputerWorld,, Win10.Guru, and Simply put, it’s a great program. I just used it to remove the 3 extraneous copies of Nvidia’s GeForce drivers for my GTX 1070 card in prepping this story and reclaimed over 1 GB of disk space as a consequence. On less freqently tweaked systems, I’ve seen this tool recover 5-15 GB of disk space instead. Great stuff.

Even if you’ve got an older version of the program, it’s a good idea to download and start using the latest version instead. It’s portable and does not require installation, either. Highly recommended!

June 15, 2018  11:06 AM

AI Drives Win10 Update Access

Ed Tittel Ed Tittel Profile: Ed Tittel
Windows 10, Windows Update, Windows Update Management

The title grabbed my attention right way: “AI powers Windows 10 April 2018 Update rollout.” This fascinating post appeared on MS’s Win10 blog yesterday. It’s from John Cable, Director of Program Management, Windows Servicing and Delivery. Basically, it explains how MS uses device telemetry to decide which machines get offered updates or upgrades. Cable said: “Our AI approach intelligently selects devices that our feedback data indicate would have a great update experience and offers the April 2018 to those devices first.” He continues: “Our overall rollout objective is for a safe and relaible update, which means we only go as fast as is safe.” And that is how AI drives Win10 update access for the latest Win10 versions.

When AI Drives Win10 Update Access, What Happens?

Microsoft has been slowly but surely taking advantage of machine learning. It’s using AI in analyzing which machines can handle updates, and which ones have problems. According to Cable, this started in earnest with a pilot during the Fall Creators Update last year (version 1709). The company identified device characteristics likely to lead to a positive update experience with Insider Previews and “trained our model to spot and target those devices” when the update went into more general release. He goes on to say of this pilot that “… we consistently saw a higher rate of positive update experiences identified using the AI model.” That experience included “… fewer rollbacks, uninstalls, reliability issues, and negative user feedback.” That’s just what MS wants, so it’s no surprise that the 1803 rollout leans heavily on this methodology.

The Results Are Encouraging

Cable claims that this approach is working. He reports that over 250 million devices are running 1803. He also seeing “higher satisfaction numbers, fewer known issues, and lower support call volumes compared to previous Windows 10 releases.” Interestingly, press and forum coverage indicates that many users are having problems with 1803. But apparently overall satisfaction is up and trouble reports down from the MS perspective.

IMO, the uptake numbers speak for themselves. Given that 1803 appeared on April 30, for 250 million devices to have upgraded in 1.5 months is noteworthy. And, FWIW, these “official” MS numbers more or less prove my June 1 assertion  about AdDuplex numbers. I said that the 50% uptake figures extrapolated from AdDuplex numbers were flat wrong. MS currently puts those numbers at 35% of the Win10 user base, which more or less proves my point. ‘Nuff said!

June 13, 2018  11:00 AM

Sysprep Audit Mode Alternate Key Sequence

Ed Tittel Ed Tittel Profile: Ed Tittel
Keyboard Shortcuts, MS Sysprep, Sysprep, Windows 10

When it comes to building custom Windows images, few tools are as helpful as Microsoft’s venerable System Preparation Tool. Usually known as “Sysprep,” this tool works with a variety of other elements from the Microsoft Assessment and Deployment Kit (ADK). Savvy admins use Sysprep in Audit Mode to make and capture alterations to running Windows images. The Microsoft docs tell us that once you get to the final dialog after the last boot during the Windows install process, one can enter Audit mode using Ctrl+Shift+F3 keys. Why, then, is a Sysprep audit mode alternate key sequence necessary? [Note: this is the dialog where the system asks you to choose “Customize” or “Use express settings.” See Kari’s great TenForums tutorial Customize Windows !0 Image in Audit Mode with Sysprep… for fully illustrated step-by-step instructions.]

Sysprep Audit Mode Alternate Key Sequence.screencap

When you enter Audit Mode, the System Preparation Tool pops up. For those who wish to customize a Windows install, the next thing to do is to press the Cancel button to close this window.

It seems that on some keyboards — especially those found on laptops — system builders monkey with the handling of function keys. Often, that’s because keyboards are smaller and include fewer options. On my Lenovo laptops, for example, there’s a blue function (Fn) key that must be pressed for those keys to perform alternate functions. These include lock/unlock, sleep, display redirection, snapshots from the built-in camera, brightness controls, and so forth. On my Dell Venue Pro, the function keys work only if the blue Fn button is depressed. Otherwise, system control functions apply. Still other laptop makers use different conventions, key assignments, and so forth. You get the idea, I hope.

Sysprep Audit Mode Alternate Key Sequence Revealed

Ok, then. Let’s assume you try the default key sequence of Ctrl+Shift+F3 and nothing happens. What then? My preceding discussion foreshadowed the fourth key you’ll add to this mix. Try Ctrl+Fn+Shift+F3. That’s because you’re trying to use the Function key as a veritable function key and pressing Fn on some keyboards will make that happen. If neither sequence works, you’ll have to visit your laptop (or keyboard) maker’s website to get the right sequence from them. Since their deployment techs invariably use some sequence to get Sysprep into Audit Mode, somebody there will undoubtedly know the answer. All you have to do then, is to find your way to that somebody or some other source for that information. My best guess is that if the site has a user forum, you’ll be able to find the info there in short order by searching on “Sysprep” or “Audit Mode.” Good luck!

For the record, on my Lenovo systems Ctrl+Fn+Shift+F3 works like a champ to get into Audit Mode. If the default sequence doesn’t work for you try the alternate sequence next.


June 11, 2018  12:35 PM

Fixing Win10 Restart PC to Finish Installing Drivers Issue

Ed Tittel Ed Tittel Profile: Ed Tittel
Device drivers, Troubleshooting, Windows 10

I’ve chased down a strange sequence of clues over the past few days to finally resolve an odd device driver issue. The reason I say the device driver issue is odd stems from its origin. It followed in the wake of a recent Security Update for the Adobe Flash Player. “I don’t see that a device was involved,” was my reaction to unwinding the clues that led me to this discovery. I’m sure other readers may react likewise. But the clues that led me to this understanding are convincing. Thus, let me present the evidence for fixing Win10 restart PC to finish installing drivers issue.

Evidence for Fixing Win10 Restart PC to Finish Installing Drivers Issue

On June 8, I got a notification from Windows 10 that I needed to finish installing a device driver. With no new device drivers added to my machine that day, I was a little puzzled. First off, I turned to Reliability Monitor, which showed me only two information items, neither of which specifically mentioned a device driver:

Fixing Win10 Restart PC to Finish Installing Drivers Issue.relimon

Only two info items for that day, neither of which is labeled explicitly as a device driver. Curious, eh?
[Click image for full-sized view].

Quite naturally, this led me to the Windows log file, where Windows 10 logs all device driver additions and changes. For the record, this file resides in %windir%\INF, and can be an occasional and valuable source for driver insight. This time, it showed me an entry at the same time the Adobe Flash Player update was installed. Thus, the evidence is unshakeable that part of the security update includes a device driver of some sort or another. Here’s that log entry:

1  [Boot Session: 2018/06/08 10:41:05.428]>>>  [Finish Install Action – USB\VID_046D&PID_C52B&MI_02\6&44B3556&0&0002]
2  >>>  Section start 2018/06/10 08:42:21.371
3  dvi: {Build Driver List} 08:42:21.375
4  dvi:      Searching for hardware ID(s):
5  dvi:           usb\vid_046d&pid_c52b&rev_2406&mi_02
6  dvi:           usb\vid_046d&pid_c52b&mi_02
7  dvi:      Searching for compatible ID(s):
8  dvi:           usb\class_03&subclass_00&prot_00
9  dvi:           usb\class_03&subclass_00
10 dvi:           usb\class_03
11 dvi: {Build Driver List – exit(0x00000000)} 08:42:21.385
12 dvi: Class GUID of device changed to: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
13 dvi: {DIF_FINISHINSTALL_ACTION} 08:42:21.385
14 dvi:      Using exported function ‘CoDeviceInstall’ in module ‘C:\WINDOWS\system32\LkmdfCoInst.dll’.
15 dvi:      CoInstaller 1 == LkmdfCoInst.dll,CoDeviceInstall
16 dvi:      CoInstaller 1: Enter 08:42:21.392
17 dvi:      CoInstaller 1: Exit
18 dvi:      Default installer: Enter 08:42:21.393
19 dvi:      Default installer: Exit
20 dvi: {DIF_FINISHINSTALL_ACTION – exit(0xe000020e)} 08:42:21.393
21 <<<  Section end 2018/06/10 08:42:21.394
22 <<<  [Exit status: SUCCESS]

Digging Into Details

A search on the device ID involved, however — namely usb\vid_046d&pid_c52b&rev_2406&mi_02 (line 5) — tells me it’s actually a Logitec device driver. Most likely, it’s for the Universal USB Receiver that connects to my RF-based M325 mouse. So actually, Flash Player isn’t responsible. It’s something that came along for the ride with the Flash player. In fact, the issue is that even after restarting the machine in the wake of the update, the install status of the driver fails to clear. The “Configure a device” troubleshooter keeps displaying the same status, no matter how many times I restart my PC. Here’s what that looks like:

Fixing Win10 Restart PC to Finish Installing Drivers Issue.troubleshooter

The desired transformation failed to occur, despite numerous restarts. Sigh.
[Click image for full-sized view.]

Some quick research on Bing led me to some possible fixes. The first one I tried indicated that an anti-malware package could interfere with the proper status reset during the restart process. So I disabled Norton on my PC for 15 minutes, restarted the machine, and presto! Problem solved. It just goes to show that you can indeed figure out how to fix many Windows gotchas, if you carefully collect the evidence available and let it lead you to a solution online. Case closed, thank goodness!

June 8, 2018  2:20 PM

VDI vendors must change tack as on-premises market slows

Alyssa Provazza Alyssa Provazza Profile: Alyssa Provazza
cloud, DaaS, Desktop virtualization, Desktop Virtualization Implementation, End user security, survey, VDI

Several factors have slowed new on-premises VDI adoption, and VDI vendors are forced to shift their strategies as a result.

VDI projects in the design, pilot and rollout stages make up a tiny portion of VDI environments, and they have decreased over the past year, according to the State of the EUC 2018 report released in May. Just 1.18% of respondents said their on-premises VDI is in the newly designed or proof-of-concept phase, down from 3.07% in 2017, according to the survey by research initiative VDI Like a Pro. Meanwhile, 41.3% said their VDI has been in production for two to four years, with 33.92% in production for five years or longer.

That’s because most IT departments interested in deploying VDI likely have already done so. Major challenges that cropped up around the technology — storage capacity, GPU power, cost — have since been considerably eased.

Very large organizations or even higher-end mid-market companies with 3,000 to 5,000 users are still good candidates for VDI, but they’re hesitant to move because of the time commitment, said Dane Young, strategic business advisor at Entisys360, an IT consultancy based in Concord, Calif.

“Now we’re dealing with the harder long pole in the tent — the slower adopters,” Young said. “They recognize that they need to, but also that it’s a three- to five-year plan. It takes a lot of time to move a couple thousands users into that environment.”

VDI vendors can gain new ground by focusing their attention on these companies — and pushing the security benefits.

“The number one trend that we’re seeing drives these types of VDI or app delivery initiatives has been security,” Young said. “IT leaders need to… involve their security [team] early and often.”

Desktop and application as a service has also shifted IT’s interest away from on-premises VDI. This trend presents new opportunities for vendors that provide VDI management and monitoring because IT needs tools aimed at handling these cloud workloads.

Another way for VDI vendors to find new customers may simply be a renewed emphasis on winning business from competitors, said Ruben Spruijt, CTO of cloud workspace provider Frame and an author of the report, along with Mark Plettenberg, senior product manager at Login VSI.

“The vendors will look at customers who are replacing their hardware or are not totally satisfied with the vendor that they have,” Spruijt said. “As the market matures, the way that VDI vendors engage with the customer has to change.”

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: