Search the Community

bit of back story. In our environment we didn't want to go the whole DP route because we already have replicated folders with DFS setup for network software installs. SCCM 2007 this worked great, create the package specify the install strings and starting path and you were away to the races. SCCM 2012 in testing has been more.. finicky. We've been able to deploy to existing computers with Script (native) deployment types however OSD task sequences won't move past checking for dependencies, complaining the application deployment can't be found on the DP. We can work around this once again by using command line steps in our TS but then it seems like we're losing a lot of our existing benefits of creating applications etc. Some great features in 2012 so far but would be nice to support our old workflow . anyone else do this or get it to work?