When I use SCCM to build a VHD, does it generalize the VHD for use as a master VM automatically or is it making an image that is suitable for only a single VM?
When I pass the VHD that SCCM creates to the Virtualization team, is that VM going to be generalized, or does VMM take care of generalizing the VHD, or if we want to end up with 40 personal/persistent VMs, do I need to create 40 VHDs and hand them all off to the Virtualization team. Similarly, is it possible to use SCCM 2012 R2 to create a VHD that is suitable for pooled use? Does my task sequence have to take care of the generalization? I guess what I don't know is, it feels like I should be using a TS that is similar to Build and Capture to build these VHDs so that they can be used as templates for new machines in VMM rather than a standard deployment TS where there is a one-to-one VHD to VM relationship. There are 1000 blogs out there with screenshots of how to create the VHD in SCCM 2012r2, but they are all very light on discussion or guidance. Create the VHD and hand it off/upload it to VMM.... And then what? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
