Note: New article on Services Optimization for VDI posted that includes the Anniversary (Build 1607) and Creator (Build 1703) updates. This post is only for the original (Build 1511) release.
In the Windows 10 Optimization – Part 1, I mostly focused on those applications which come pre-installed. Removing the apps shouldn’t help us get better server density, unless the users are spending all day watching videos or interacting with Xbox. Mostly, removing unneeded applications will create a cleaner image from which we can build our master image.
In this part, I want to take a closer look at Windows 10 services. Are there any that we can shut down to make the operating system consume less resources? Will it impact the experience? And while we are looking at services, let’s keep in mind our XenApp Best Practice
For the best combination of user experience and resource consumption, optimize appropriately
And maybe we should add “optimize responsibly” when it comes to services. The more you monkey with the services, the more likely you will experience application or user issues.
First, these services are running, by default, and can be stopped and disabled (Caution: Disabling these services can result in applications not working appropriately and will increase troubleshooting time).
Service Name | Default State | Default Status | Notes |
Background Intelligent Transfer Service | Automatic (Delayed Start) | Running | Set default state to “Manual” as 3rd party software might require the service. |
Diagnostic Policy Services | Automatic | Running | |
Diagnostic Service Host | Manual | Running | |
Diagnostic System Host | Manual | Running | |
Diagnostics Tracking Service | Automatic | Running | |
Function Discovery Provider Host | Manual | Running | |
Function Discovery Resource Publication | Manual | Running | |
Home Group Provider | Manual (Trigger Start) | Running | Not used in VDI environment |
Security Center | Automatic (Delayed Start) | Running | |
Shell Hardware Detection Service | Automatic | Running | Supports AutoPlay, which is not typically used in VDI. |
SSDP Discovery | Manual | Running | Not typically used in corporate environments. |
SuperFetch | Automatic | Running | Can enable for dedicated desktops |
Themes | Automatic | Running | This will impact the user experience |
Windows Connect Now – Config Registrar Service | Manual | Running | Not required in VDI |
Windows Search | Automatic (Delayed Start) | Running | Consider disabling. Will have a high impact on server density. |
Second, these services are not running, but they are set to Manual or Manual (Trigger Start). Although they are not running, disabling them will prevent their accidental execution in a VDI environment. (Caution: Disabling these services can result in applications not working appropriately and will increase troubleshooting time).
Service Name | Default State | Default Status | Notes |
AllJoyn Router | Manual (Trigger Start) | Stopped | |
Application Layer Gateway Service | Manual | Stopped | Not needed for VDI environments. |
BitLocker Drive Encryption Service | Manual (Trigger Start) | Stopped | Drive encryption not typically used in VDI environments. |
Block Level Backup Engine Service | Manual | Stopped | Windows backup not typically used in VDI. |
Bluetooth Hands free Service | Manual (Trigger Start) | Stopped | Not typically used in VDI. |
Bluetooth Support Service | Manual (Trigger Start) | Stopped | |
BranchCache Service | Manual | Stopped | Used for network savings to a WAN and not typically needed in VDI |
Computer Browser Service | Manual (Trigger Start) | Stopped | |
Encrypting File System Service | Manual (Trigger Start) | Stopped | |
Fax Service | Manual | Stopped | |
Home Group Listener | Manual | Stopped | Not used within corporate environments. |
Internet Connection Sharing (ICS) | Manual | Stopped | Not used within VDI environments. |
Offline Files | Manual (Trigger Start) | Stopped | |
Optimize Drives | Manual | Stopped | Should only optimize in the master image |
Retail Demo | Manual | Stopped | |
Sensor Monitoring Service | Manual (Trigger Start) | Stopped | |
UPnP Device Host Service | Manual | Stopped | |
Windows Error Reporting Service | Manual (Trigger Start) | Stopped | Disable if logs are not being gathered and analyzed |
Windows Media Player Network Sharing | Manual | Stopped | Not typically used in VDI environments. |
Windows Update | Manual (Trigger Start) | Stopped | Only update the master image. |
WLAN AutoConfig | Manual | Stopped | Not typically used in VDI environments. |
WWAN AutoConfig | Manual | Stopped | Not typically used in VDI environments. |
Xbox Live Auth Manager | Manual | Stopped | Not typically used in VDI environments. |
Xbox Live Game Save | Manual | Stopped | Not typically used in VDI environments. |
Xbox Live Networking Service | Manual | Stopped | Not typically used in VDI environments. |
IMPORTANT
If these services are disabled in the master image, it will be more difficult to effectively manage the master image. For example, if Windows Update is disabled in the master image, an administrator will be required to re-enable the Windows Update Service BEFORE trying to run Windows Update. The administrator will then have to remember to disable Windows Update when the update process is complete.
It is advisable to use a Group Policy to disable the services and apply the policy onto to the VDI-based desktop objects.
And remember our XenApp Best Practice:
For the best combination of user experience and resource consumption, optimize appropriately
If you are unsure about a service, LEAVE IT ALONE!
Note: The complete Windows 10 optimization blog series
Daniel (Follow @djfeller)
XenApp Best Practices
XenApp Videos
Should “Function Discovery Resource Host” be “Function Discovery Provider Host”?
LikeLike
Good catch.
LikeLike
It would appear that “Device Association Service” causes an Login/Locked issue if disabled it. Not apparent straight away but i found if there is any alteration to the local users on the PC it causes the issue.
LikeLike