Sravan,
I gave up trying to use the AMDX, there is something that conflicts with the ADMX and the Office 2016 customization tool when I installed office...
- When I installed office in my golden image, i ran it local, did a full install but used a customization
Here's what I did -
Setup a 2016 custom install, that creates no outlook profile, and set a ADMX/gpo to auto create the mail profile based on the users domain.
My simple script -
net use B: \\horizonvdi.domain.local\horizonost /Persistent:Yes
mkdir B:\%username%.%userdomain%\ITPool\2016\Ost
mklink /D "c:\users\%username%\AppData\Local\Microsoft\Outlook" "B:\%username%.%userdomain%\ITPool\2016\Ost"
This will -
1. map a "B" drive to a remote file share on a 2012 clustered file server just for VDI (Nimble All Flash array)
2. Makes a directory - this is important as the symbolic link can not be created until the directory exists, and will NOT create it for you
3. Creates a symbolic link for the users local OST location to this remote location.
I have this working with no issues for 85 users and will scale it much higher soon.
I use UEM between both physical and VDI, so in physical, the OST stays local script doesnt need to re point the local OST)
UEm will import the "mail profile" and point to the "local" (Symbolic linked) OST location
I tried to use the writable volume JUST for the OST, but VMware could not provide me an a working solution on how to JUST redirect a OST.
The article referenced is not a working solution for what you or I wanted to do, and it adds time to logon to mount the appvolume.
I kinda gave up on appvolumes as they just dont provide the user a good clean environment, and are a nightmare to undo down the road.
I still have issues in tests activating office 2016, IF i stack on an additional app (like add visio in an appvol, when office is in the golden image)
I do love UEM though!
