We use it with SCCM 2012 R2 OSD ZTI scenarios now and it works great. In fact I was using PSADT before we implemented ZTI OSD and didn't have to change the majority of my packages. They just worked.
You just need to be aware of packages that require user environment customizations/settings in OSD scenarios though.
You have to do other things to supplement apps that require these. There has been new work in PSADT with Active Setup and ways to modify the default user. But I don't like modifying the default profile and have not invested the time to try the new Active Setup functions (yet). But I already have apply once Group Polices Preferences configured to customize our core apps. Eventually, I would like to utilize powershell DSC to replace most of our GPPs in the future.
With SCCM 2012 R2 we have less core apps now and with most of the non-core apps user customizations do not require any special mojo because we are using user based collections and user based installations. It is pretty amazing how quickly user based apps come down in our ZTI OSD scenarios.
You just need to be aware of packages that require user environment customizations/settings in OSD scenarios though.
You have to do other things to supplement apps that require these. There has been new work in PSADT with Active Setup and ways to modify the default user. But I don't like modifying the default profile and have not invested the time to try the new Active Setup functions (yet). But I already have apply once Group Polices Preferences configured to customize our core apps. Eventually, I would like to utilize powershell DSC to replace most of our GPPs in the future.
With SCCM 2012 R2 we have less core apps now and with most of the non-core apps user customizations do not require any special mojo because we are using user based collections and user based installations. It is pretty amazing how quickly user based apps come down in our ZTI OSD scenarios.