SCCM 2011 기술 미리보기

SCCM 2011 기술 미리보기.

Categorize Community hub content

Community hub content is grouped into a Microsoft, curated, or unreviewed category to allow admins to choose the types of content their environment displays. Admins can choose from the different categories of content that are provided in the Community hub to match their risk profile and their willingness to share and use content from those outside Microsoft and outside their own company.

Community hub content has three categories for content sources:

• Microsoft curated: Content provided by Microsoft
• Community curated: Content provided by the community that gets reviewed by Microsoft
• Community unreviewed: General content from the community that doesn’t get reviewed by Microsoft

Admins can choose the types of content their environment displays from the following options:

• Display Microsoft content: Selecting this option means that only content created by Microsoft will be shown in the Community hub. This content has had some basic testing and scanning validation to confirm no malware and inappropriate text.
• Display Microsoft and curated community content: Show curated content from both Microsoft and community partners with basic level of review. Selecting this option means that only content that has been curated will be shown. The curation process includes basic review to confirm that the content doesn’t have malware and inappropriate text, but hasn’t necessarily been tested. It will include content from the community, not just from Microsoft.
• Display all content including unreviewed content: Selecting this option means that all content is shown. This option includes unreviewed open-source type samples from the community, meaning that the content hasn’t necessarily been reviewed at all. It’s provided as-is as open-source type sample content. Doing your own inspection and testing before using is highly encouraged, which is good practice on any content, but especially this class of content.

Since the content is open-source style content, admins should always review what is provided before consuming it. The new curation process is intended to vet the material to make sure there aren’t obvious quality or compliance issues, but it will be somewhat of a cursory review. All content stored within GitHub and accessed from the Community hub isn’t supported by Microsoft. Microsoft doesn’t validate content collected from or shared by the general community. For more information, see GitHub Terms of Service and GitHub Privacy Statement.

권한

Full Administrators can opt in the hierarchy for unreviewed content via hierarchy settings. Lower hierarchy administrators can’t opt in the hierarchy for unreviewed hub items.

Most built-in security roles will have access to Community hub:

Role name	View the hub	Contribute hub content	Download hub content
Remote Tools Operator	아니요	N/A	N/A
Read Only Analyst	예	아니요	아니요
All other roles	예	예	예

Improvements to the product lifecycle dashboard

This release includes improvements to the product lifecycle dashboard to make it more actionable for you.

• Customize the timeframe on the charts for your preference.
• 찾다, sort, and filter the data.
• View a list of devices with products that are near or at end of support, and you need to update.

The dashboard also has a new subnode, All Product Lifecycle Data. You can sort and filter the product lifecycle information, which gives you multiple ways to view it. When you select a product, 당신은 할 수 View devices for that product. From the list of devices, you can currently create a direct membership collection. Use this action to deploy the latest software versions to these collections so that the devices are kept current.

The dashboard has a new time slider. Use it to control the timeframe for the 맨 위 5 products nearing end-of-support tile. 기본값은입니다 18 months, but you can adjust it from 1 에게 36 months.

Software Center notifications display with logo

If you enable Software Center customizations, then notifications on Windows 10 devices display the logo that you configure in client settings. This change helps users to trust these notifications.

When you deploy software to a client, the user sees notifications with your logo. The following example uses a star logo:

Approved scripts for Orchestration Groups

You can now select from scripts that have already been approved when configuring pre and post-scripts for an orchestration group. When in the Create Orchestration Group Wizard, you’ll see a new page called Script Picker. Select your pre and post scripts from your list of scripts that are already approved. You can still add scripts manually on the pre and post-script pages. Additionally, you can also edit scripts that you pre-populated from the Script Picker.

Community hub on Windows Server operating systems

You can now display the Community hub on Windows Server operating systems. Follow the instructions below to enable Windows Server 2012 and later to load the Community hub:

1. In the upper-right corner of the console, select the bell icon to display Configuration Manager console notifications.
2. The notification will say New custom console extensions are available.
3. Select the link Install custom console extensions to launch the install.
4. When the install completes, 선택하다 닫다 to restart the console.
5. Confirm that you can view the Community hub node from the machine running the Windows Server operating system.
   • You may also notice that a new folder AdminConsole\bin\Microsoft.WebView2.FixedVersionRuntime.<version>.x86 was created.
   • The files are automatically downloaded from https://developer.microsoft.com/en-us/microsoft-edge/webview2/#download-section with the other redistributable files.

Improvements to Support Center

When you troubleshoot software update deployments, you might ask the following questions:

• Are any updates missing or failing?
• Are specific updates deployed to a device?
• What are the error codes for a deployment?
• Why didn’t the device reboot during a maintenance window?
• What’s the current state of an update?

Support Center already shows updates that are targeted to the device but not yet installed. Now in this release, 선택하다 All Updates on the Content tab of Support Center to show all updates targeted to the device. To help you troubleshoot, this list includes information about whether the update is installed or missing.

Also on the Content tab, 선택하다 Maintenance Windows to show the available maintenance windows for the device.

For more information on the additional features of Support Center that you can use to help troubleshoot a device, see Support Center overview.

Improvements to OS deployment

This release includes the following improvements to OS deployment:

• Based on your UserVoice feedback, task sequence conditions now include a not like operator. This operator applies to task sequence variable conditions. It’s also used in the Set Dynamic Variable task sequence step.
• Based on your UserVoice feedback, this release fixes issues with the SMSTSDisableStatusRetry task sequence variable.
• Based on your UserVoice feedback, the Check Readiness task sequence step now also checks free space on disks without partitions.
• Based on your UserVoice feedback, the following PowerShell cmdlets now have an Index parameter:
  • New-CMOperatingSystemImage: When you run this cmdlet with the new Index parameter, it creates a new single-index image file in the same source folder.
  • New-CMOperatingSystemInstaller (alias New-CMOperatingSystemUpgradePackage): When you run this cmdlet with the new Index parameter, it replaces the original image file in the source folder with a single-index image file.
• Based on your UserVoice feedback, the following new cmdlets are available to get the list of existing hardware IDs in the site database:
  • Get-CMDuplicateHardwareId
  
  
  • GuidGet-CMDuplicateHardwareIdMacAddress
  These new cmdlets supplement the existing cmdlets to add and remove duplicate IDs. For more information, see Version 1910 PowerShell release notes.

Update PowerShell help

You can now use the Update-Help cmdlet to get the latest information for the Configuration Manager PowerShell module. This content is the same as what’s published on docs.microsoft.com for the ConfigurationManager module.