Skip to main content

2012 r2 series: productive users and protected information

this morning’s read: part 2 of 9, titled making device users productive and protecting corporate information. here’s my summary of another incredibly long and detailed post. don’t forget to go back and get the full read. away we go.

  • people-centric IT (pcit). addresses four key areas.
    • users. expect to have access to all of their corporate resources from anywhere.
    • devices. diversity is not just about controlling which models of a particular brand to use. diversity of device type continues to grow as well. diversity = complexity.
    • apps. complexity in cross-platform management and deployment of apps.
    • data. provide data access without while staying compliant and secure.
  • bring your own device (byod). byod is not a trend so much as a turning point. there’s no going back. diversity of devices will continue to climb which positions companies to have to fight the trend or embrace the trend. that’s what pcit is about.
  • user productivity. embracing byod effectively means having a healthy balance of access to corporate resources coupled with the right amount of security. with pcit, access policies can be enabled against the following criteria:
    • user’s identity
    • user’s device
    • user’s current network
  • common engineering criteria. engineers with server, configmgr, and intune shared common engineering milestones. focused on three key areas:
    • empowering users. users can have access to a variety of apps and data across a spectrum of devices – desktops, laptops, phones, tablets. windows, ios, and android are all supported (though it sounds like android might not get all the features initially.)
      • simple registration and enrollment.
        • workplace join. offers users a simple way to opt-in to IT services. creates user@device record in AD. governs access to resources and enables sso only. does not allow any IT control.
        • intune. users can enroll for management. wifi/vpn profiles, settings, side loading, etc.
      • consistent access to company resources. users can access apps, manage their own device, and access data via work folders.
      • automatically connect to internal resources. only works with enroll for management. vpn profiles launch on demand.
      • access resources from anywhere. data will be accessible via work folders and web application proxy.
    • unifying environment. single pane of glass management for apps and devices across scenarios from on-premise to cloud-based, including malware protection.
      • single console. the configmgr console is the basis of all management. cloud based management added through an intune connector.
      • user-centric app management. uses the user-centric model in configmgr to determine which app to deploy based on device and capability.
      • multiple delivery mechanisms. includes msi, app-v, remote apps, web links, windows store, app store, and google play.
      • cross-platform settings management. manage certifies, vpn, and wireless network profiles, apply compliance policies (to the extent of the platform, of course), receive inventory data, push installs, remote wipe and unregistration.
      • single identity. common identity from on-premise to cloud-based. ad fs tightly integrated to web application proxy is a key component.
    • protecting data. information access controlled by user, device, and location. shutdown access from devices no longer used.
      • control data. ability to selectively wipe data while leaving personal data intact. (see the original post for a table detailing device to capability.)
      • policy-based access control. made possible by ad fs, dynamic access control, web application proxy and work folders. obviously the implementation will be very complex.
        • web application proxy. provides ability to publish access to internal resources with optional multi-factor authentication.
        • work folders. file sync that allows syncing from corporate file server to user device over https. data is stored encrypted, locally on the device. files can be removed when device is un-enrolled from management.

Comments

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …