Windows 10 Works with Existing Infrastructure

Deploying and managing Windows 10 in your business does not mean upgrading your client management infrastructure.  Use your existing SCCM and Windows Server investments to deploy and manage the new Windows 10, which has now been officially released.  See the matrix below for compatibility information.  Also note, a new version of System Center Configuration Manager is in the works which will offer new capabilities related to Windows 10 features but is not needed to get Windows 10 out to your users today!

2015-07-29_16-13-21

Twitter: @jparekh_tech

Enroll Windows 10 Enterprise Preview to Hybrid ConfigMgr + Microsoft Intune

The following are quick steps to enroll the Microsoft Windows 10 Insiders Preview (as of build 10130) to Microsoft Intune in a hybrid environment with Microsoft System Center 2012 R2 SP1 Configuration Manager (SCCM).

This assume you have already configured Microsoft Intune into your SCCM environment.

  1. In the SCCM console, navigate to Administration -> Overview -> Cloud Services -> Microsoft Intune Subscriptions.
  2. On the top ribbon bar, click the Configure Platforms button. Click Windows in the drop down

  3. From the Microsoft Intune Subscription Properties, click the Enable Windows enrollment.

  1. Log onto your Windows 10 desktop, go to Settings and choose Network and Internet

  2. Click on Accounts and then Work access. On the Connect to work or school section, click the + Connect

  3. Enter your work email address that are Intune enabled (an account that has synchronization between your on-premise Active Directory and Windows Azure Active Directory). After you click continue, you will be sent to the Microsoft site to authenticate.

  4. Once done, you see the connected account on the main section.

  5. In the SCCM console, you will now be able to see your newly enrolled device as a Mobile device. You will be able to deploy applicable compliance policies just like any other mobile devices in your organization.

-Jay

Hybrid – Intune Mobile Application Management and Conditional Access for Outlook blog NOTE

As most have seen the blog announcing the Intune Mobile Application Management and Conditional Access for Outlook.  At the very bottom, there is a Note about the hybrid customers (SCCM) availability that seems to be missed by few folks when they update to SP1.

Note: These features are currently available in Intune standalone (cloud only) and will be made available to hybrid customers by July 2 as part of an upcoming Intune service update.

Configuration Manager Collection Query for Android Devices

Quick query to dynamically identify Android devices in Configuration Manager 2012 R2

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%”

Microsoft Intune – March Update

Microsoft will be making the next update for Microsoft Intune between March 4, 2015 and March 7, 2015. New Intune standalone (cloud only) features that will be released as part of this service update include:

  • Ability to streamline the enrollment of iOS devices purchased directly from Apple or an authorized reseller with the Device Enrollment Program (DEP)
  • Ability to restrict access to SharePoint Online and OneDrive for Business based upon device enrollment and compliance policies
  • Management of OneDrive apps for iOS and Android devices
  • Ability to deploy .appx files to Windows Phone 8.1 devices
  • Ability to restrict the number of devices a user can enroll in Intune

It’s important to note that the updates are for the stand alone Cloud only and not the integrated with SCCM. Updated to the integrated extensions are usually 3-6 months after the standalone is available.

Jay

Installing Secondary Sites and other Roles on Windows 2012 with Riverbed in the mix

During a new Configuration Manager 2012 implementation project, we tried to push a secondary site at another location (Datacenter B) from our primary site (in Datacenter A). We saw failures in the logs specifically it can’t connect to the secondary server’s c$ and failed other queries. Both Primary and the secondary servers are Windows Server 2012. Some testing showed we are not able to connect to c$ manually from the primary server from Datacenter A to the secondary server in Datacenter B. But we can connect from a Windows 7 desktop from Datacenter A to the server (2012) in Datacenter B.

After much research, we found this is was because the sites are optimized by Riverbed and the current firmware of the appliances do not support SMB3.

Riverbed just announced SMB3 support late July 2013 with the release of RiOS 8.5 for Q3 2013.

In RiOS 8.5, Riverbed is introducing new optimizations for business-critical Microsoft applications and environments including SharePoint® 2013, Exchange 2013, Office365® and file sharing applications that utilize the server message block 3 (SMB3) protocol in Windows® 8 and Server 2012 environments. As a result, mutual customers of Microsoft and Riverbed can increase productivity and efficiency, while enhancing business resilience.

Their blog (from August 5, 2013) also stated the same.

Work around is to disable Secure Negotiate.

To change this setting, set the following LanmanWorkstation parameter using PowerShell cmdlet:

Set-SmbClientConfiguration – RequireSecureNegotiate <0|1|2>

0 – Disabled

1 – Required

2 – Enabled if needed 

You can also edit the DWORD value through the registry editor.

HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\RequireSecureNegotiate.

To change the default behavior, you need to define the registry key. If not present, its default value is “Required” in Windows 8 clients.

The registry key can be populated via GPP in the computer configuration.

More information on SMB on 2012 and previous version:

http://blogs.technet.com/b/josebda/archive/2012/06/06/windows-server-2012-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-or-smb-3-0-you-are-using-on-your-file-server.aspx

Client / Server OS Windows 8
Windows Server 2012
Windows 7
Windows Server 2008 R2
Windows Vista
Windows Server 2008
Previous versions
of Windows
Windows 8
Windows Server 2012
SMB 3.0 SMB 2.1 SMB 2.0 SMB 1.0
Windows 7
Windows Server 2008 R2
SMB 2.1 SMB 2.1 SMB 2.0 SMB 1.0
Windows Vista
Windows Server 2008
SMB 2.0 SMB 2.0 SMB 2.0 SMB 1.0
Previous versions
of Windows
SMB 1.0 SMB 1.0 SMB 1.0 SMB 1.0

ThinkPad Driver Packs for ConfigMgr available

Some of us have been waiting a long time for these.

ThinkPad Driver Packs for ConfigMgr are self-extracting executables with drivers in the folder structure and format so they can imported into ConfigMgr 2007 or 2012 and used in an Operating System Deployment task sequences for deployments.

http://forums.lenovo.com/t5/Enterprise-Management-IT/Introducing-ThinkPad-Driver-Packs-for-ConfigMgr/m-p/800691

If the links above don’t work, driver packs are a bit harder to locate than they are for Dell and HP. You have to hit the Drivers & Software page on the Lenovo site, then walk through their wizard to identify the model of PC for which you want drivers. Once you do that, you can jump to the Enterprise Management spot and grab the ConfigMgr Packs for the various processor types.

Technical Documentation Download for System Center 2012 Configuration Manager

The downloadable files listed on this page contain the product documentation for System Center 2012 Configuration Manager. The available file types include:

  • CHM (as part of the Help Update Wizard msi) – last updated May 23, 2012
  • DOCX – last updated May 23, 2012
  • PDF – last updated May 23, 2012

 

http://www.microsoft.com/en-us/download/details.aspx?id=29901