If you haven't already, I strongly suggest you read my previous blog entries on this subject. This avoids me having to re-hash what I've already said! They are:
http://www.edugeek.net/blogs/norphy/1982-adventures-macland-my-experiences-configmgr-2012-macs-part-1.html
http://www.edugeek.net/blogs/norphy/1984-adventures-macland-my-experiences-configmgr-2012-macs-part-2.html
http://www.edugeek.net/blogs/norphy/2010-adventures-macland-my-experiences-configmgr-2012-macs-conclusion.html
http://w
Introduction
Assuming that you're interested in this, I would suggest that you read my previous three blog posts first. This will put this new post into some context and it saves me having to write it all again! Links to the previous posts:
http://www.edugeek.net/blogs/norphy/1982-adventures-macland-my-experiences-configmgr-2012-macs-part-1.html
http://www.edugeek.net/blogs/norphy/1984-adventures-macland-my-experiences-configmgr-2012-macs-part-2.html
http://www.edugeek.net/blogs/norphy/2
So, At the end of my last blog entry I asked which agent is better: The Microsoft or the Parallels one? This isn't really very clear cut but lets try to answer the question.
So in the blue corner, we have the Microsoft native client. Its advantages are:
Native Solution
On the whole, easier to create and add applications to the ConfigMgr console
A Client side GUI
Disadvantages are:
Treats the Macs as mobile clients so therefore requires the use of HTTPS secured MPs and DPs
No
I actually started writing this just after I finished my last blog entry. However, a nasty bout of the flu and other things have got in my way since then and I just hadn't gotten around to finishing this post. Well, no more!
Introduction
In Part One of this blog, I talked about the new Mac client for Microsoft System Center 2012 Configuration Manager SP1 (God, that's a mouthful!). I talked about my impressions of it and how well it's been working so far. I also mentioned that Parallels have
