dpalazeke's Posts

Hello Enthusiast, I have not had this issue, but have a worry I will run into something like this.  Right now we just have instant clone pool with fslogix profile containers.  We've had issues with printers mapping correctly through group policy, so we were considering DEM.  Out of curiosity, which group policy method did you use and how did you bypass the printnightmare bug?  Our current production environment is Windows 7 and we put in the point and print registry settings and that seemed to work for that OS, but not for Windows 10.  Did you have to pre-load the parent image wth all of the print drivers first? Thank you, dromios

Thank you for the quick response.  VMware actually got back to me in a timely manner and reinforced your input: "You are correct in that vCenter & Composer supported environments are required to have 1 to 1 relationship, the same is not a requirements for instant clones as per KB 80673 below. While multiple vCenters are supported with a single Hz deployment the reverse as you mention, Sharing of a single vCenter Server across multiple Horizon Pods is not supported with Composer. How to share a Single vCenter Server Across Multiple Horizon Pods : https://kb.vmware.com/s/article/80673 As there will be only 1 instance of Composer, while a cut over is being implemented with adequate resources available this should not pose too much of an issue in itself." I'm a bit confused on the term Pod, I was just going to create a separate instance.  I'm not sure if the term is being used colloquially in this case, or if you have to actually create different pods.  Do you have any input there?  There is only one datacenter.