The chaps at WMUG have come up with a fantastic community event ‘Enterprise Client Management for the Modern World’ to be hosted at Microsoft’s offices in Victoria on 24th August 2015.
As community contributor to WMUG, I’m happy to announce that I am involved in two presentations that day.
I’ll be running an Introduction to App-V integration in ConfigMgr 2012 R2.
This talk will focus on the creation, deployment, updating and death of an App-V package using ConfigMgr 2012 as the deployment tool.
Later in the day I will be teaming up with fellow WMUG friend Peter Egerton to run a more practical presentation on Windows 10 IoT on Raspberry Pi 2 and an Introduction to Blinky.
In this talk we will be installing the Windows 10 IoT Core release on a Raspberry Pi and then using a program called Blinky to control a LED light.
All the details, along with registration link, are here.
Here’s the agenda.
| Time | Subject | Speaker |
| 08:30 | Registration & Coffee | |
| 09:00 | Welcome from WMUG | |
| 09:15 | System Center with Secunia | Paul Hossack |
| 10:00 | Introduction to App-V integration in ConfigMgr 2012 R2 | Paul Winstanley |
| 10:45 | BREAK | |
| 11:00 | Getting Started with Enterprise Mobility Suite | Gerry Hampson MVP |
| 11:45 | SDK and Development with ConfigMgr 2012 | Robert Marshall MVP |
| 12:30 | LUNCH | |
| 13:30 | Windows 10 for the Enterprise | Peter Egerton |
| 14:15 | Mobile Device Management with Microsoft Intune | Gerry Hampson MVP & Robert Marshall MVP |
| 15:00 | BREAK | |
| 15:15 | Windows 10 IoT and Raspberry Pi2 with an introduction to Blinky | Peter Egerton & Paul Winstanley |
| 16:00 | Questions for speakers & open discussion | All |
| 16:45 | Thanks and giveaways | |
| 17:00 | Close |
SCCMentor - Paul Winstanley 
Excellent – however there is one small problem. Since I don’t see this addressed anywhere else, the issue is downloading SP1 and attempting to run the SP1 gets an error message saying the SCCM 2012 is not running – which is correct, it is SCCM 2012 R2 – what gives? Action Pack or Tech Eval produces same results.
Do you have the ConfigMgrSetup.log from the root of the C: drive? What does this report?