blue_calx's Posts

Why join the gold image to the domain? I thought it was best practice not to
If that is all you use app volumes for then you should ditch it and look into fslogix containers.
Hello, I have some questions about this. How do you exactly view what is on a writable volume (UIA only). If I view it via C:\snapvolumestemp it looks like the whole file system is on the user writa... See more...
Hello, I have some questions about this. How do you exactly view what is on a writable volume (UIA only). If I view it via C:\snapvolumestemp it looks like the whole file system is on the user writable volume. Also with this config, won't excluding program files not capture applications that users installed themselves?
I am having the same problem with Creative Cloud. App Volumes 2.18 or 4.01...same results...If I install it on a persistent VM it work's fine but not with instant clones. This is even with using ... See more...
I am having the same problem with Creative Cloud. App Volumes 2.18 or 4.01...same results...If I install it on a persistent VM it work's fine but not with instant clones. This is even with using FSlogix containers for full windows profiles.
No it was not attached to anything. I can't even attach the app template vmdk. This is app volumes 2.18
I need to update the snapvol.cfg for some appstacks because we plan on rolling out FSLogix soon. When I try to attach any appstack VMDK to a non-app volumes VM, it won't let me and fails with a r... See more...
I need to update the snapvol.cfg for some appstacks because we plan on rolling out FSLogix soon. When I try to attach any appstack VMDK to a non-app volumes VM, it won't let me and fails with a read-only error. Any thoughts?
Windows Server 2016
Hello, I upgraded to UEM 9.5 and can't utilize the new download  template feature. When I attempt to sign in with myvmware account I get: Anyone else get this and know of a fix? Thank... See more...
Hello, I upgraded to UEM 9.5 and can't utilize the new download  template feature. When I attempt to sign in with myvmware account I get: Anyone else get this and know of a fix? Thanks!
We are not using ADFS so that is why that path needs to be captured by UEM.
Yes I have followed that guide. Are you using Azure SSO or just password syncing?
Thank you for the suggestions! I am testing this with a O365 account that is cloud only. I do not have ADFS SSO setup. The tenant was setup this year so I am sure modern authenication is enabled.... See more...
Thank you for the suggestions! I am testing this with a O365 account that is cloud only. I do not have ADFS SSO setup. The tenant was setup this year so I am sure modern authenication is enabled. I will try that disabling that GPO setting. Maybe O365 is excepting federation account but it's not setup. Thanks!
Hello, I am in the process of setting up a new VDI environment and having a very hard time with Office 365 account persistence. I am running an instant clone non-persistence desktop pool with ... See more...
Hello, I am in the process of setting up a new VDI environment and having a very hard time with Office 365 account persistence. I am running an instant clone non-persistence desktop pool with Windows 10 Enteprise Build 1709. I have tried Office 365 builds 1708 and 1803. I have authentication token roaming setup to the UEMProfile network share via GPO and capturing <LocalAppData>\Microsoft\Credentials via UEM (in the Office 2016 Shared Settings template). Office 365 account persistence works for a bit but then after a while, this happens: I have tried having these Office 365 builds via App Volume or baked into the master image. Still the same results. I am pulling my hair out on this one. If I click "Fix Me" I have to sign back into Office 365 or sometimes just reactivate. Shared Computer activation is definitely enabled. Has anyone ran into this problem? If you don't have this problem and have a similar setup as mine, what Office 365 build are you using? You can find a build history here: Update history for Office 365 ProPlus (listed by date) | Microsoft Docs I would appreciate any help on this. My next step is to open a case with VMware if I can't get it resolved. Thank you!!
Hello, I am in the process of setting up a new VDI environment and having a very hard time with Office 365 account persistence. I am running an instant clone non-persistence desktop pool with ... See more...
Hello, I am in the process of setting up a new VDI environment and having a very hard time with Office 365 account persistence. I am running an instant clone non-persistence desktop pool with Windows 10 Enteprise Build 1709. I have tried Office 365 builds 1708 and 1803. I have authentication token roaming setup to the UEMProfile network share via GPO and capturing <LocalAppData>\Microsoft\Credentials via UEM (in the Office 2016 Shared Settings template). Office 365 account persistence works for a bit but then after a while, this happens: I have tried having these Office 365 builds via App Volume or baked into the master image. Still the same results. I am pulling my hair out on this one. If I click "Fix Me" I have to sign back into Office 365 or sometimes just reactivate. Shared Computer activation is definitely enabled. Has anyone ran into this problem? If you don't have this problem and have a similar setup as mine, what Office 365 build are you using? You can find a build history here: Update history for Office 365 ProPlus (listed by date) | Microsoft Docs I would appreciate any help on this. My next step is to open a case with VMware if I can't get it resolved. Thank you!!