The Office 365 container configuration admx miss the entry for changing the name of the VHD. Registry entry exist. Can you complete the admx3 votes
Currently, when you specify CCDLocations, the first one is used for all non-cached reads. This is an issue when there are multiple hot-hot sites in place, as we then need two different configurations targeting the sites with a different order to the CCDLocations in order to force the VDI in that site to read from the CCDLocation located locally at that site. We are currently solving this with two Group Policy registry preferences, each using item-level targeting to apply to a specific site, but a native mechanism to auto-detect the closest CCDLocation to use for reads would be preferred.1 vote
In silent mode the CRT installers are executed all the time. There is check if the included CRT is needed or not. But even if a newer version is installed the older CRT installers are executed and fail.1 vote
- Don't see your idea?