with Horizon licenses you are allowed to host all the additional infrastructure needed for VDI, eg. Connection Server, Composer, UAG, vCenter (if it is managing VDI hosts only). Domain controllers may be a thing to argue about I guess (then again, who uses DCs only for VDI users?), but Exchange and file servers should clearly be on the not-allowed list.
Thanks for your fast response. As you said, it "should" be and I would agree with that. We plan to use the DC's only for the VDI environment (completely new infrastructure), if we are saving the user profiles on DFS shares (two file server), then the file server are needed for VDI and should be allowed?
I can only guess based on the information I have, but my advise would be to not mistake the infrastructure that's needed for making the Windows OS usable (DC, profiles, GPOs etc.) with the infrastructure that is really needed for VMware Horizon to work.
I would recommend contacting your VMware team and get something in writing on what's allowed if you must do it this way.
To keep things simple and due to the nature of the workloads we run seperate vCenter for desktops and servers. Even the supporting Horizon infrastructure is run in the server environment.
We're doing the same here. If you have got multiple systems dependent on vCenter (as it is the case with Horizon) you'd be running into complicated update procedures as often the supported vCenter builds may not be the same for these systems.