Skip to main content

2012 r2 series: three scenarios of pcit

 

pcit. there’s that term again. it doesn’t mean personal computer though. it actually means people-centric IT. as more and more devices are born to consume cloud-based services, it makes sense for management of such devices to be cloud-based as well. part 3 – people-centric IT in action – end-to-end scenarios across products – (coincidentally) looks at three scenarios of pcit.

 

scenario 1: company access, personal device.

company access already exists today through technology such as vpn. this is really more about giving users the ability to get to their work files on a personal device. it address some of the risks around compliance by utilizing authentication (ad fs) and encryption (work folders).1 of course, remote wipe is a part of the scenario.

the core component to scenario 1 is work folders. think of work folders as a skydrive pro for file servers. (skydrive pro is for sharepoint, in case you were curious.) work folders requires both a server2 and a client. windows 8.1 will be the first to get it with windows 7 and ios following shortly thereafter. work folders runs over https so if you are so inclined, you can publish it via the web application proxy – which integrates with ad fs.

for those IT admins that yearn for more control in their life, configmgr + intune delivers the ability to provision devices with work folders settings. group policies can be used for those pesky domain-joined machines. configmgr r2 has work folders support so you can use all of the familiar targeting capability to deliver policies.

1 optionally, use dynamic access control (dac) and rights management services (rms) can provide additional security/control. complexity is already super high, though.

2 basically, it’s a file server role in windows 2012 r2.

this statement will have you locked away in a cave by your executives for months:

Back to Hypothetical Joe: Suppose Joe buys a new Surface RT and wants to access files from work. He simply has to Workplace Join his device and enroll for management. As part of enrollment, his Work Folder configuration will be automatically provisioned and his files will start to sync to an encrypted folder. Joe now has all his work files available to him. As he makes changes to these files on his Surface RT, the changes synchronize to his desktop at work and vice-versa. As he creates sensitive documents, they are automatically classified and RMS protected.

Later, when Joe leaves the company, the IT team removes his devices from management and Joe’s Surface RT automatically wipes (rendered inaccessible) his Work Folders data while leaving all his personal data intact.

 

scenario 2: register to win!

unified device management (udm) requires azure AD, configmgr, and intune. once your environment is set up, the user will have to go to their respective “store” and download the company portal app. the cool thing is the device will show up in configmgr associated with the user.

granting access to company resources requires web application proxy and ad fs. unregistered devices will be denied access but will be provided links on how to get registered (to win!).

 

scenario 3: managing vpn

windows 8.1 has ms and third party vpn support built in, including new capabilities for profile management and on-demand vpn. let’s start with profile management:

  • configmgr + intune = provision vpn profiles and certs (intune for devices)
  • provision vpn profiles via powershell

automatic vpn (what i refer to as on-demand vpn) is managed by rules that are delivered to the device. when a user tries to connect to a company resource, vpn fires up. if any additional information is required, the user is prompted.

here’s a list of the powershell cmdlets from my 8.1 preview tablet:

Add-VpnConnection
Add-VpnConnectionRoute
Add-VpnConnectionTriggerApplication
Add-VpnConnectionTriggerDnsConfiguration
Add-VpnConnectionTriggerTrustedNetwork
Get-VpnConnection
Get-VpnConnectionTrigger
New-VpnServerAddress
Remove-VpnConnection
Remove-VpnConnectionRoute
Remove-VpnConnectionTriggerApplication
Remove-VpnConnectionTriggerDnsConfiguration
Remove-VpnConnectionTriggerTrustedNetwork
Set-VpnConnection
Set-VpnConnectionIPsecConfiguration
Set-VpnConnectionProxy
Set-VpnConnectionTriggerDnsConfiguration
Set-VpnConnectionTriggerTrustedNetwork

 

technologies involved with pcit architecture:

Labels:

Comments

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

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.   DETECTION status messages take 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 m
3 comments
more »