greetings
Recently implemented a SCCM 2012 infrastructure and so far so good, however we are currently having issues deploying App-V 5.0 packages via SCCM to VDI Clients in a timely fashion.
I have seen other posts with other users saying that this has been done successfully, however we are finding the following :-
- VDI clients show up in SCCM 2012 as being physical devices despite being built under hyper-V and never seeing a physical device
- Once the VDI session loads, I need to run a manual Machine Policy Refresh Eval cycle in order to get the apps down to the client, otherwise it can take at least 30 minutes for the apps to appear.
so my questions are
- Is there anything I need to do with the SCCM client agent on the template build
- Is there anything I can do to automate the Machine Policy and User Policy refresh commands?
- Or is it better to drop SCCM 2012 for this and revert back to a native App-V 5.0 infrastructure for VDI?
Any help or advice would be appreciated