What’s new with your favorite virtualization companies and executives.


Check out what’s happening in your area, from webinars to lunch and learns.


Get the scoop on the latest technology news from industry experts.

How To’s

Step by step instructions on a variety of need to know virtualization topics.


Take a look at the industries most recent company and product annoucements.

Home » Blogs

Using the custom VDI stack with Windows 10

Submitted by on January 9, 2018 – 8:34 pmNo Comment

Within the Windows 10 image we would have the relevant agents installed (FSLogix, Cloudhouse, Uniprint, DataNow and our monitoring daemon) and we would also need to extend at least one of these (the monitoring one) to the existing estate so we can start scanning for non-standard data areas. So the “pilot” phase would involve application testing on the new Windows 10 platform and data gathering on the old estate. Once this phase is finished, we will then have the information on data, profiles, and printing which we can then build up into Group Policy Objects that can enable the migration to the live environment.

Then we can begin the actual migration. We would extend the DataNow client onto the existing estate at this point and start to synchronize user data in the background. Once this is finished, the user will be marked ready for migration and we can add them to a group that triggers the process (of course, the “classroom” areas can be done on a phased basis, as there will be no user data to be managed). At this point, they will have their machines replaced or repurposed and at next logon they will fire up a virtual Windows 10 desktop. When they log in, their applications will be virtualized onto the endpoint, their profile will be mounted on a VHD across the network, their data will be represented by overlays which will sync down either on-demand or in the background, and their printer(s) should be mapped as expected.

To read the entire article, please click on this