MDM in SCCM 2012 R2 - Extend Windows Intune trial

Back to ConfigMgr main menu
   
Back to MDM Menu

You can create a Windows Intune trial subscription for 30 days here
 
Previously, if you wanted to extend this trial you had to enlist the help of your Microsoft account manager and this was a bit of a process. Customers can now do this on their own. You can extend your trial by a further 60 days by calling customer support  (you have to extend 30 and a further 30 - not 60 together). You must have global administrator access to your portal to verify your identity.
 

Edit 24th November 2014

Find your local number for Intune support here

http://technet.microsoft.com/en-US/jj839713.aspx


(((((Find your local CSS telephone number here

http://support.microsoft.com/gp/customer-service-phone-numbers/en-ie )))))

Under special circumstances you may be able to extend past the 90 days but this will not be the norm.

MDM in SCCM 2012 R2 - Windows 8.1 Phone

Back to ConfigMgr main menu
 
Back to MDM Menu

The procedure is exactly the same as for Windows 8 Phone until you are actually enrolling the phone. Instead of  Settings > Company Apps you need Settings > Workplace

Windows 8.1 Phone

Navigate to Settings

Open Workplace

Click to Add and account.

Enter your email address as before (or more correctly - your AD account UPN).

Enter the Microsoft server name if required.

Windows 8.1 is connecting to Intune.

The device is enrolled. Install the Company App.

 

Double-click on the account to see synchronization. Policy is being downloaded.

Synchronization is complete. Compliance policies will soon be applied to the device.

MDM in SCCM 2012 R2 - Device Collection Queries

Back to ConfigMgr main menu
 
Back to MDM Menu


Collection of Windows Phone 8 devices

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_DEVICE_OSINFORMATION on SMS_G_System_DEVICE_OSINFORMATION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_DEVICE_OSINFORMATION.Platform like "Windows Phone" and SMS_G_System_DEVICE_OSINFORMATION.Version like "8.0%"


Collection of Windows Phone 8.1 devices

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_DEVICE_OSINFORMATION on SMS_G_System_DEVICE_OSINFORMATION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_DEVICE_OSINFORMATION.Platform like "Windows Phone" and SMS_G_System_DEVICE_OSINFORMATION.Version like "8.1%"


Collection of Windows RT devices

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Model like "Surface%"


Collection of iPhones 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,
SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_DEVICE_COMPUTERSYSTEM on SMS_G_System_DEVICE_COMPUTERSYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_DEVICE_COMPUTERSYSTEM.DeviceModel like "%iphone%"


Collection of iPads

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,
SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_DEVICE_COMPUTERSYSTEM on SMS_G_System_DEVICE_COMPUTERSYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_DEVICE_COMPUTERSYSTEM.DeviceModel like "%ipad%"


Collection of Android devices

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_DEVICE_OSINFORMATION on SMS_G_System_DEVICE_OSINFORMATION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_DEVICE_OSINFORMATION.Platform like "Android%"

ConfigMgr 2012 - additional Distribution Points

Back to ConfigMgr 2012 menu 

Additional Distribution Points can be deployed on remote sites. They can provide content locally to clients and reduce the need for excessive traffic to be transferred over the WAN links.

A good "rule of thumb" is to install a DP in locations of 20 users or more.

Supported Operating Systems

The matrix of supported operating systems can be found on the TechNet Library here 
You can use a client (Windows Vista & later) or a server (Windows 2003 SP2 or later) OS - however the client OS will not support PXE or mulitcast.
There are also some other caveats that you should be aware of.

Pre-requisites 

Add Primary Site Server computer account to be local administrator on the remote server.

Disable the Windows Firewall on the remote server (or configure the firewall - see here for ConfigMgr and firewall ports reference).

Add NO_SMS_ON_DRIVE.SMS file to all drives that you do not want ConfigMgr to use as a DP.

Add the required Windows Features - specifically IIS and Remote Differential Compression. Note that BITS is not required on the DP (BITS is installed on the ConfigMgr clients).

Add the DP

Navigate to Administration > Site Configuration.

Right click "Servers and Site System Roles" and choose "Create Site System Server"

Verify the server name and select the site code. Click Next.

No proxy required in my case.

Select "Distribution Point".

We have already installed IIS on the remote server - however it doesn't hurt to select the IIS box. We want HTTP.

Accept the defaults. Remember we have already configured NO_SMS_ON_DIVE.SMS

This will not be a Pull DP.

You can enable PXE now or later (this will install Windows Deployment Services). I like to do this later so that I can see WDS installing and I'm able to control the reboot).

Multicast not required.

Boundary Groups can be added now or later.

Click Next to deploy the DP.

Click Close to finish.

Monitor progress using the distmgr.log file.

See DP Content Library created.

DP successfully added

 

Empower People Centric IT Roadshow

I had the pleasure of presenting a session at the "Empower People Centric IT Roadshow" in Reading this week.

Here I am presenting the Unified Device Management session on behalf of the Windows Management User Group. 

MVP Empower People Centric IT Roadshow

·    June 17, 2014, 09:00 AM to 05:00 PM

·    Microsoft Campus, Thames Valley Park, Reading, Berkshire RG6 1WG

WMUG Hosts : MVP Empower People Centric IT Roadshow

Join speakers from WMUG and the outstanding MVP community in the UK and Ireland for this FREE event and find out more about:  

·    How IT can provide a consistent and personalised experience for users across a wide range of devices.

·    How IT can keep corporate information protected

And how the above can be achieved without adding unrealistic cost and complexity to the business?

Throughout June 2014, MVPs will be delivering sessions in Edinburgh, Sunderland, Birmingham, Bristol and Reading.

On Tuesday 17th June WMUG will be hosting the Reading session of this roadshow to be held at the Microsoft UK headquarters. 

The agenda is as follows:

Time	Topic
9.30am	What is People Centric IT?
10.00am	Why Windows 8.1 and the devices it brings to life
11.00am	Windows XP End of Support
11.15am	Tea and Coffee
11.30am	Operating System Deployment in SCCM
12.15pm	Desktop and App Delivery with Virtual desktop Infrastructure
1.00pm	Lunch
2.00pm	Unified Device Management with SCCM + Windows Intune
2.45pm	Exploring bring your own device vs. choose your own device
3.30pm	Tea and Coffee
3.45pm	Access to corporate apps and date with work folders/dynamic access control/RMS/Direct Access/VPN
4.15pm	Identity Management with Windows Server 2012 R2/AD/ADFS
5.00pm	Close