ConfigMgr for (More) Evil! Devious systems management… Evil Guy: Ryan Ephgrave Concurrency, Inc. Good Guy: Nash Pherson Now Micro, Inc.

Evil is coming... Feel free to entertain yourselves on twitter. Tweet @EphingPosh and/or @KidMystic and see your tweets on the screen! Don't be the guy who makes us turn it off...

WARNING! The things you hear may help you keep you job, or help you lose your job...

Ryan Ephgrave Nash Pherson @EphingPosh @KidMystic Prominent Community Leader Microsoft MVP - ConfigMgr ConfigMgr and PowerShell Expert ConfigMgr and Org. Development Diet Coke, pretty please! Coffee… right now… please…

WARNING! The things you hear may help you keep you job, or help you lose your job...

ConfigMgr for More Evil! What’s the point? ConfigMgr is Powerful... Does what you tell it to do What’s the catch? What’s the next? Ideas on next year – keep them coming...

Control Access to your Distribution Points Don't enable "Anonymous Access" to get around authentication issues... Fix your auth issues Specify a Network Access Acount

Service Accounts should be for one thing Use separate service accounts for separate things! If the computer uses it, the computer knows the password

Be careful what you put on your DPs Content on your DP's can be viewed by the local Users group, which by default contains Domain Users You can get stuff out of the content library and package share... so don't put sensitive text (or even 'encoded' sensitive text) on your DP's Local Admin Password script? Use LAPS instead

Be Thoughtful with Role Based Administration If you get permissions to EDIT stuff that is already deployed, you can do a lot of damage unknowingly... Ok, you can do all the damage

Lose CM, Lose AD, Lose it all Let's have some fun with it! (REMEMBER TO REMIND US TO GIVE AWAY THE COFFEE CARD HERE) What should we do with the Domain Controller? What should we do with the ConfigMgr Environment?

Key to the Kingdom gives you more Keys Since we own DC... Let's dump the password hashes!

Security guys are a pain in the butt, so... Let's wake up the Security Team!

Find those folks who annoy you, and annoy them! Nothing like a little BLUE... BLUE SCREEN... BLUE SCREEN OF DEATH!

Summary What did we learn? What should we do next year?

And Then …

Section Header This is the next section

Title Line1 Line2 Line3 Line4 Line5 Line6 Bullet Level 1

Title Code

Text Only with Border Level 1 Level 2 Level 3

Text Only without Border Level 1 Level 2 Level 3

Title Text 1 Level 1 Level 2 Level 3 Text 2 Level 1 Level 2 Level 3

Title Text Text Section 1 Section 2 Level 1 Level 1 Level 2 Level 2

Demo Title