VMware

Do you use SCCM in your VDI machines, and or Base image?

Do you use SCCM in your VDI machines, and or Base image? We have non persistent vms and are contemplating using SCCM to do updates to windows and office. Once updated, remove SCCM and clone/deploy to the pool.

Reading into this and wondering if anyone on here has any input as to it being good practice or and horrible stories.



View Reddit by vwdieselloverView Source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

10 Comments

  1. Yes, but only for persistent virtuals.

    Basically if you have dedicated VDI workstations that get treated like physical workstations nothing particularly different needs to be done.

    For non-persistent VDI, we exclude them entirely from discovery in SCCM.

  2. PDQ Deploy is a lot easier to use and less hardware needed. I used to be an SCCM Admin and I prefer using it as oppose to using the 800lb beast.

    In a VMWare envionrment you don’t need image management, you do need app and automation tools and PDQ can handle everything I need to manage deployed persistent VMs.

  3. For persistent clones, we keep an sccm agent on them. For non-persistent/instant clones, we have an agent on the master image machines. Before we update the pool machines, we snap shot the master with the client, remove the agent, snap shot the master again, update the pool, then revert to the snapshot with the sccm client. This way, we keep our instant clones as close to production machines as possible.

  4. in a previoues role our “VDI” was just VMs provisioned in vSphere that were accessed with RDP since it met the needs. VMs were created with a script that took the pertinent details and created object in SCCM adding it to a collection with a required OSD. The VM was then provisioned with our standard TS that was applied to desktops/laptops.

  5. No. I installed a power shell module that I use to install updates instead. My other desktops all use SCCM, but since my desktop pool is not persistent it doesn’t make sense to use SCCM.

  6. For our Persistent desktops, the SCCM client is installed. For our non-Persistent gold image we update using Ivanti (Shavlik), which picks up the updates for most all of our COE applications. It works out well for us most of the time. We’re an airgapped network, so we are at the mercy of the admins that update the Ivanti repository.

  7. Once we Sysprep the Gold Image and rebuild the collection, we boot the gold iamge back up again. Then we have a scheduled task that runs a powershell script that runs windows updates 2 times per day and will reboot and keep installing if needed. (This scheduled task gets disabled before sysprepping and deployment). When it’s time to rebuild the patched collection, we just login to the gold image machine and make sure no other updates are needed. If not, we shut down, do a checkpoint, boot it back up disable the update script scheduled task, and Sysprep. Deploy patched collection.

Leave a Reply