I'm coming to this massive comment party late, but I wanted to drop my thoughts about this and explain why I'm personally very excited by OneGet.
I'm a very experienced Windows Server Admin (15 years). I'm also a fairly experienced Linux Server Admin (7 years, on and off).
I'm currently an SCCM guru for a ~4000 user organisation.
I'm sure that if OneGet is supported by MS to the level which the developer explained in the reddit thread it'll be a boon to power users managing their own systems and to desktop support people.
But I can imagine that it'll be the SCCM teams who can leverage the most out of it.
The thought of being able to deploy and manage software across desktops and servers in a similar way to apt or yum makes me feel something close to utter joy.
I've had to build some very complex task sequences to install software on corporate machines. The worst example I can give is MS's own Dynamics CRM application. I was seriously proud of the batch files, registry inserts, dll hell avoidance, dependency solving, mother of all automated install processes to get Dynamics installed and hooked into Outlook in a magical way that the end user had no clue the complexity of.
It was only after slugging through developing all of the above that I found the incredible PowerShell App Deployment Toolkit [1], which people smarter than me had developed to basically handle everything I'd just slogged through.
From what I see OneGet has the potential of allowing us to easily push installs and updates via SCCM with out having to rely on 3rd party tools, batch files, msi rebuilding and general hackery.
Even if it doesn't gain wide support from software vendors, just enabling me to rip everything out of an msi and repackage it into a private OneGet repo sounds superior to having to rely on complex SCCM task sequences.
I'm a very experienced Windows Server Admin (15 years). I'm also a fairly experienced Linux Server Admin (7 years, on and off).
I'm currently an SCCM guru for a ~4000 user organisation.
I'm sure that if OneGet is supported by MS to the level which the developer explained in the reddit thread it'll be a boon to power users managing their own systems and to desktop support people.
But I can imagine that it'll be the SCCM teams who can leverage the most out of it.
The thought of being able to deploy and manage software across desktops and servers in a similar way to apt or yum makes me feel something close to utter joy.
I've had to build some very complex task sequences to install software on corporate machines. The worst example I can give is MS's own Dynamics CRM application. I was seriously proud of the batch files, registry inserts, dll hell avoidance, dependency solving, mother of all automated install processes to get Dynamics installed and hooked into Outlook in a magical way that the end user had no clue the complexity of.
It was only after slugging through developing all of the above that I found the incredible PowerShell App Deployment Toolkit [1], which people smarter than me had developed to basically handle everything I'd just slogged through.
From what I see OneGet has the potential of allowing us to easily push installs and updates via SCCM with out having to rely on 3rd party tools, batch files, msi rebuilding and general hackery.
Even if it doesn't gain wide support from software vendors, just enabling me to rip everything out of an msi and repackage it into a private OneGet repo sounds superior to having to rely on complex SCCM task sequences.
I'll be watching this closely.
[1] https://psappdeploytoolkit.codeplex.com/