From 8788b259ea4714069b47918aa2415b9f236c1afb Mon Sep 17 00:00:00 2001 From: mestew Date: Wed, 4 Sep 2019 11:25:12 -0700 Subject: [PATCH] Https checking P0 items from CATS report: https://contentqacats.azurewebsites.net/CheckResults/2019090300007/Report/ --- ThirdPartyNotices | 2 +- sccm/apps/deploy-use/learn-script-security.md | 2 +- .../management-tasks-applications.md | 2 +- .../deploying-app-v-virtual-applications.md | 2 +- .../deploy-use/import-configuration-data.md | 2 +- .../compliance/plan-design/scap/about-scap.md | 4 +-- .../scap/install-configure-scap.md | 4 +-- ...eploy-clients-to-unix-and-linux-servers.md | 2 +- ...-deployment-to-windows-embedded-devices.md | 6 ++-- .../deploy/prepare-to-deploy-mac-clients.md | 2 +- .../configuring-asset-intelligence.md | 2 +- .../prerequisites-for-asset-intelligence.md | 2 +- .../hardware-inventory-for-linux-and-unix.md | 2 +- .../plan-internet-based-client-management.md | 2 +- .../upgrade-clients-on-mac-computers.md | 2 +- .../2019/includes/1902-2/3735402.md | 2 +- .../get-started/2019/includes/1904/2839943.md | 2 +- .../capabilities-in-technical-preview-1511.md | 2 +- .../capabilities-in-technical-preview-1604.md | 2 +- .../capabilities-in-technical-preview-1703.md | 2 +- .../capabilities-in-technical-preview-1712.md | 2 +- sccm/core/get-started/set-up-your-lab.md | 4 +-- .../planning-for-the-migration-of-objects.md | 4 +-- .../security-and-privacy-for-migration.md | 2 +- ...microsoft-sql-server-2012-native-client.md | 2 +- .../eula/microsoft-sql-server-2014-express.md | 4 +-- ...l-server-2014-shared-management-objects.md | 2 +- ...l-server-compact-4.0-service-pack-1-sp1.md | 2 +- ...center-configuration-manager-evaluation.md | 12 ++++---- ...configuration-manager-technical-preview.md | 8 +++--- ...oft-system-center-configuration-manager.md | 2 +- ...m-center-endpoint-protection-evaluation.md | 8 +++--- ...clr-types-for-microsoft-sql-server-2014.md | 2 +- sccm/core/misc/eula/third-party-notices.md | 26 ++++++++--------- sccm/core/misc/online-documentation.md | 10 +++---- .../removed-and-deprecated-cmfeatures.md | 2 +- ...changed-from-configuration-manager-2012.md | 2 +- .../configs/supported-configurations.md | 4 +-- ...erating-systems-for-clients-and-devices.md | 2 +- ...lients-find-site-resources-and-services.md | 2 +- .../plan-design/network/internet-endpoints.md | 2 +- .../network/pki-certificate-requirements.md | 6 ++-- .../websites-for-site-system-servers.md | 2 +- ...database-replicas-for-management-points.md | 6 ++-- .../configure/install-site-system-roles.md | 4 +-- .../deploy/install/get-install-media.md | 2 +- .../servers/deploy/install/setup-reference.md | 4 +-- .../use-the-setup-wizard-to-install-sites.md | 2 +- .../checklist-for-installing-update-1610.md | 2 +- .../checklist-for-installing-update-1702.md | 2 +- .../checklist-for-installing-update-1706.md | 2 +- .../checklist-for-installing-update-1710.md | 2 +- .../checklist-for-installing-update-1802.md | 2 +- .../checklist-for-installing-update-1806.md | 2 +- .../checklist-for-installing-update-1810.md | 2 +- .../checklist-for-installing-update-1902.md | 2 +- sccm/core/servers/manage/cmpivot.md | 2 +- sccm/core/servers/manage/create-queries.md | 6 ++-- .../manage/introduction-to-reporting.md | 2 +- .../manage/modify-your-infrastructure.md | 4 +-- ...perations-and-maintenance-for-reporting.md | 4 +-- .../manage/prerequisites-for-reporting.md | 2 +- .../upgrade-on-premises-infrastructure.md | 2 +- ...the-hotfix-installer-to-install-updates.md | 2 +- .../manage/use-the-service-connection-tool.md | 2 +- sccm/core/support/tools.md | 2 +- .../understand/product-and-licensing-faq.md | 8 +++--- .../supported-configurations-for-ltsb.md | 6 ++-- sccm/core/understand/use-cloud-services.md | 10 +++---- sccm/desktop-analytics/enroll-devices.md | 4 +-- sccm/desktop-analytics/privacy.md | 2 +- ...ication-with-the-script-deployment-type.md | 4 +-- ...ng-the-application-management-extension.md | 6 ++-- ...-settings--dcm--setup-and-configuration.md | 2 +- .../about-configuration-manager-inventory.md | 2 +- ...t-configuration-manager-wmi-programming.md | 2 +- .../programming/client-resource-conditions.md | 6 ++-- ...-configuration-manager-sdk-requirements.md | 4 +-- .../reqs/client-development-requirements.md | 8 +++--- .../core/reqs/client-runtime-requirements.md | 2 +- ...-manager-sdk-libraries-and-header-files.md | 2 +- .../reqs/server-development-requirements.md | 8 +++--- .../configure/how-to-create-a-package.md | 2 +- ...configuration-manager-console-extension.md | 2 +- .../core/servers/console/executable-action.md | 2 +- .../core/servers/console/group-action.md | 2 +- .../about-configuration-manager-queries.md | 2 +- .../configuration-manager-sdk-samples.md | 6 ++-- ...uration-manager-with-windows-powershell.md | 2 +- ...guration-manager-and-windows-powershell.md | 12 ++++---- ...-with-configuration-manager-programming.md | 18 ++++++------ .../understand/introduction-to-wbemtest.md | 10 +++---- .../understand/sms-provider-fundamentals.md | 2 +- .../understand/windows-powershell-basics.md | 2 +- ...iguration-manager-provider-fundamentals.md | 10 +++---- ...ure-mobile-device-client-agent-settings.md | 2 +- ...istribution-packages-for-mobile-devices.md | 2 +- ...nager-custom-action-client-applications.md | 8 +++--- ...ing-system-deployment-driver-management.md | 2 +- .../asset-intelligence-client-wmi-classes.md | 4 +-- .../configure/sms_package-server-wmi-class.md | 2 +- .../sms_packagebaseclass-server-wmi-class.md | 2 +- .../sms_bootimagepackage-server-wmi-class.md | 2 +- .../osd/sms_driver-server-wmi-class.md | 2 +- ...e_applydataimageaction-server-wmi-class.md | 4 +-- ...plydriverpackageaction-server-wmi-class.md | 2 +- ...ynetworksettingsaction-server-wmi-class.md | 8 +++--- ...yoperatingsystemaction-server-wmi-class.md | 4 +-- ...ywindowssettingsaction-server-wmi-class.md | 2 +- ...quence_autoapplyaction-server-wmi-class.md | 2 +- ...enetworksettingsaction-server-wmi-class.md | 4 +-- ...pturesystemimageaction-server-wmi-class.md | 4 +-- ...captureuserstateaction-server-wmi-class.md | 6 ++-- ...ewindowssettingsaction-server-wmi-class.md | 6 ++-- ...ectnetworkfolderaction-server-wmi-class.md | 4 +-- ...ence_convertdiskaction-server-wmi-class.md | 2 +- ..._installsoftwareaction-server-wmi-class.md | 2 +- ...ce_installupdateaction-server-wmi-class.md | 2 +- ...ndomainworkgroupaction-server-wmi-class.md | 6 ++-- ...quence_prepareosaction-server-wmi-class.md | 4 +-- ...ksequence_rebootaction-server-wmi-class.md | 2 +- ...restoreuserstateaction-server-wmi-class.md | 8 +++--- ...e_runcommandlineaction-server-wmi-class.md | 2 +- ...bleconditionexpression-server-wmi-class.md | 2 +- .../sum/how-to-configure-the-wsus-settings.md | 2 +- .../configure-intune-subscription.md | 2 +- sccm/mdm/deploy-use/confirm-dns.md | 6 ++-- ...s-10-devices-managed-without-the-client.md | 2 +- ...hone-devices-managed-without-the-client.md | 2 +- sccm/mdm/deploy-use/enroll-hybrid-windows.md | 2 +- .../import-pfx-certificate-profiles.md | 4 +-- ...rid-enrollment-using-apple-configurator.md | 2 +- ...mobile-devices-with-exchange-activesync.md | 2 +- .../protect-apps-using-mam-policies.md | 2 +- .../set-up-your-subscription-with-lookout.md | 2 +- .../troubleshoot-lookout-integration.md | 2 +- .../mdm/deploy-use/wipe-lock-reset-devices.md | 2 +- .../set-up-certificates-on-premises-mdm.md | 2 +- .../understand/whats-new-hybrid-archive.md | 10 +++---- sccm/mdt/samples-guide.md | 2 +- sccm/mdt/sccm-guide.md | 4 +-- sccm/mdt/toolkit-reference.md | 12 ++++---- sccm/mdt/troubleshooting-reference.md | 28 +++++++++---------- ...er-driven-installation-developers-guide.md | 2 +- sccm/mdt/user-driven-installation-guide.md | 4 +-- sccm/osd/deploy-use/deploy-windows-to-go.md | 2 +- .../upgrade-windows-to-the-latest-version.md | 2 +- sccm/osd/get-started/customize-boot-images.md | 8 +++--- .../customize-operating-system-images.md | 2 +- .../deploy-use/certificate-infrastructure.md | 10 +++---- .../create-windows-firewall-policies.md | 2 +- .../deploy-use/endpoint-definitions-wsus.md | 2 +- .../endpoint-protection-client-faq.md | 2 +- .../deploy-use/find-a-pfn-for-per-app-vpn.md | 6 ++-- .../introduction-to-certificate-profiles.md | 2 +- .../troubleshoot-endpoint-client.md | 2 +- ...ows-defender-advanced-threat-protection.md | 2 +- .../prerequisites-for-certificate-profiles.md | 6 ++-- ...ty-and-privacy-for-certificate-profiles.md | 2 +- ...stallation-files-for-windows-10-updates.md | 2 +- .../manage-office-365-proplus-updates.md | 6 ++-- sccm/sum/deploy-use/office-365-dashboard.md | 2 +- .../manage-settings-for-software-updates.md | 2 +- sccm/sum/tools/updates-publisher.md | 2 +- .../software-updates-introduction.md | 2 +- template.md | 2 +- 166 files changed, 318 insertions(+), 318 deletions(-) diff --git a/ThirdPartyNotices b/ThirdPartyNotices index a0bd09d68f8..faceb5a528e 100644 --- a/ThirdPartyNotices +++ b/ThirdPartyNotices @@ -7,7 +7,7 @@ see the [LICENSE](LICENSE) file, and grant you a license to any code in the repo Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. -Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653. +Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653. Privacy information can be found at https://privacy.microsoft.com/en-us/ diff --git a/sccm/apps/deploy-use/learn-script-security.md b/sccm/apps/deploy-use/learn-script-security.md index 38cea1aee3f..8e75efcebad 100644 --- a/sccm/apps/deploy-use/learn-script-security.md +++ b/sccm/apps/deploy-use/learn-script-security.md @@ -64,7 +64,7 @@ Best practices for preventing malicious parameters or script injection are: ## Environment Recommendations General recommendations for PowerShell administrators. -1. Deploy latest version of PowerShell, such as version 5 or greater, built into Windows 10. Alternatively, you can deploy the [Windows Management Framework](https://www.microsoft.com/en-us/download/details.aspx?id=54616), available down to, and including Windows 7 and Windows Server 2008 R2. +1. Deploy latest version of PowerShell, such as version 5 or greater, built into Windows 10. Alternatively, you can deploy the [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=54616), available down to, and including Windows 7 and Windows Server 2008 R2. 2. Enable, and collect PowerShell logs, optionally including Protected Event Logging. Incorporate these logs into your signatures, hunting, and incident response workflows. 3. Implement Just Enough Administration on high-value systems to eliminate or reduce unconstrained administrative access to those systems. 4. Deploy Device Guard/Application Control policies to allow pre-approved administrative tasks to use the full capability of the PowerShell language, while limiting interactive and unapproved use to a limited subset of the PowerShell language. diff --git a/sccm/apps/deploy-use/management-tasks-applications.md b/sccm/apps/deploy-use/management-tasks-applications.md index b3106395bbc..925ce1c22a9 100644 --- a/sccm/apps/deploy-use/management-tasks-applications.md +++ b/sccm/apps/deploy-use/management-tasks-applications.md @@ -35,7 +35,7 @@ For help creating applications and deployment types, see [Create applications](. |**Update Statistics**|Updates the information that is displayed in the **Deployments** node of the **Monitoring** workspace about the deployments of this application.

See [Monitor applications from the System Center Configuration Manager console](../../apps/deploy-use/monitor-applications-from-the-console.md).| |**Reinstate**|Reinstates an application that was retired by using the **Retire** management task.| |**Retire**|When you retire an application, it is no longer available for deployment, but the application and deployments of the application are not deleted. Existing copies of this application that were installed on client computers will not be removed. Any revisions to the application will be deleted from Configuration Manager after 60 days. But, installed copies of the application are not removed.

To delete an application, you must first retire the application, delete all deployments, remove references to the application by other deployments, and then delete all of the application's revisions.

See [Revise and supersede applications](../../apps/deploy-use/revise-and-supersede-applications.md).| -|**Export**|Opens the **Export Application Wizard** that lets you export the selected applications to a .zip file that you can then archive or install on another site. If you choose to export application content, a folder that has the content will be created.

You can also export application dependencies, supersedence relationships and conditions, and content for the application and its dependencies.

The Windows PowerShell cmdlet, **Export-CMApplication**, does the same function. For more information, see [Export-CMApplication](http://go.microsoft.com/fwlink/p/?LinkID=258880) in the Microsoft System Center 2012 Configuration Manager SP1 cmdlet reference documentation.| +|**Export**|Opens the **Export Application Wizard** that lets you export the selected applications to a .zip file that you can then archive or install on another site. If you choose to export application content, a folder that has the content will be created.

You can also export application dependencies, supersedence relationships and conditions, and content for the application and its dependencies.

The Windows PowerShell cmdlet, **Export-CMApplication**, does the same function. For more information, see [Export-CMApplication](https://go.microsoft.com/fwlink/p/?LinkID=258880) in the Microsoft System Center 2012 Configuration Manager SP1 cmdlet reference documentation.| |**Delete**|Deletes the currently selected application.

You cannot delete an application if other applications are dependent on it, if it has an active deployment, or if it has dependent task sequences.| |**Simulate Deployment**|Opens the **Simulate Application Deployment Wizard** where you can test the results of an application deployment to computers without installing or uninstalling the application.

See [Simulate application deployments](../../apps/deploy-use/simulate-application-deployments.md).| |**Deploy**|Opens the **Deploy Software Wizard** where you can deploy the selected application to collections of computers in your hierarchy.

See [Deploy applications](../../apps/deploy-use/deploy-applications.md).| diff --git a/sccm/apps/get-started/deploying-app-v-virtual-applications.md b/sccm/apps/get-started/deploying-app-v-virtual-applications.md index c3e61c853eb..f0b8cad4e31 100644 --- a/sccm/apps/get-started/deploying-app-v-virtual-applications.md +++ b/sccm/apps/get-started/deploying-app-v-virtual-applications.md @@ -53,7 +53,7 @@ In addition to the other System Center Configuration Manager requirements and pr - **App-V 4.6**: To use virtual applications in Configuration Manager, client computers must have the App-V 4.6 SP1, App-V 4.6 SP2, or App-V 4.6 SP3 client installed. - Before you can successfully deploy virtual applications, you must also update the App-V 4.6 SP1 client with the hotfix that is described in the Knowledge Base article [2645225](http://go.microsoft.com/fwlink/p/?LinkId=237322). + Before you can successfully deploy virtual applications, you must also update the App-V 4.6 SP1 client with the hotfix that is described in the Knowledge Base article [2645225](https://go.microsoft.com/fwlink/p/?LinkId=237322). - **App-V 5, App-V 5.0 SP1, App-V 5.0 SP2, App-V 5.0 SP3, and App-V 5.1**: For App-V 5.0 SP2, you must install [Hotfix Package 5](https://support.microsoft.com/en-us/kb/2963211) or use App-V 5.0 SP3. - **App-V 5.2**: This is built into Windows 10 Education (1607 and later), Windows 10 Enterprise (1607 and later), and Windows Server 2016. diff --git a/sccm/compliance/deploy-use/import-configuration-data.md b/sccm/compliance/deploy-use/import-configuration-data.md index e83da5f6661..de5e38e415f 100644 --- a/sccm/compliance/deploy-use/import-configuration-data.md +++ b/sccm/compliance/deploy-use/import-configuration-data.md @@ -24,7 +24,7 @@ In addition to creating configuration baselines and configuration items in the S - Configuration data that was externally authored and that conforms to the SML schema. - For an example Configuration Pack that helps you manage compliance for System Center 2012 Configuration Manager site server roles, see [System Center 2012 Configuration Manager Configuration Pack](http://www.microsoft.com/en-us/download/details.aspx?id=30710&WT.mc_id=rss_alldownloads_all). + For an example Configuration Pack that helps you manage compliance for System Center 2012 Configuration Manager site server roles, see [System Center 2012 Configuration Manager Configuration Pack](https://www.microsoft.com/download/details.aspx?id=30710&WT.mc_id=rss_alldownloads_all). When you import a configuration baseline, some or all of the configuration items that are referenced in the configuration baseline might also be included in the cabinet file. During the import process, Configuration Manager verifies that all of the configuration items that are referenced in the configuration baseline are either also included in the cabinet file or already exist in the Configuration Manager site. The import process fails if you attempt to import a configuration baseline that references configuration data that Configuration Manager cannot locate. diff --git a/sccm/compliance/plan-design/scap/about-scap.md b/sccm/compliance/plan-design/scap/about-scap.md index effaf9e1ec6..5b3dc9a3234 100644 --- a/sccm/compliance/plan-design/scap/about-scap.md +++ b/sccm/compliance/plan-design/scap/about-scap.md @@ -148,11 +148,11 @@ The SCAP extensions for Configuration Manager include Windows command-line tools - The command-line parameters `-help` and `-?` for each tool print the usage to the screen. These usage details are then available to screen readers and other assistive technology. -- For more information, see [Windows Accessibility](http://windows.microsoft.com/windows/help/accessibility). +- For more information, see [Windows Accessibility](https://windows.microsoft.com/windows/help/accessibility). The SCAP extensions also make use of accessibility features in Configuration Manager. For more information, see [Accessibility features in Configuration Manager](/sccm/core/understand/accessibility-features). -For more information about Microsoft accessibility products and services, see the [Microsoft Accessibility website](http://go.microsoft.com/fwlink/p/?LinkId=9212). +For more information about Microsoft accessibility products and services, see the [Microsoft Accessibility website](https://go.microsoft.com/fwlink/p/?LinkId=9212). diff --git a/sccm/compliance/plan-design/scap/install-configure-scap.md b/sccm/compliance/plan-design/scap/install-configure-scap.md index a4c8b406385..f65039c6a03 100644 --- a/sccm/compliance/plan-design/scap/install-configure-scap.md +++ b/sccm/compliance/plan-design/scap/install-configure-scap.md @@ -46,10 +46,10 @@ Depending on your environment, you may not need all the SCAP data stream files l ### Install the SCAP data streams -1. Visit the [NVD Web site](http://nvd.nist.gov/) to identify the SCAP data streams that are required by your organization. +1. Visit the [NVD Web site](https://nvd.nist.gov/) to identify the SCAP data streams that are required by your organization. The SCAP data streams published by NIST are organized into multiple bundles, which are also called _checklists_. -2. Download the SCAP data streams from the [NVD Web site](http://nvd.nist.gov/home.cfm), which are stored in compressed files with a .zip file name extension or marked as DataStream XML file. +2. Download the SCAP data streams from the [NVD Web site](https://nvd.nist.gov/home.cfm), which are stored in compressed files with a .zip file name extension or marked as DataStream XML file. > [!IMPORTANT] > There are many SCAP data stream files with the .xml extension that you can download from the NVD. However, only .xml files that include XCCDF (SCAP1.0 and 1.1)/DataStream (SCAP1.2) content are appropriate for use with the SCAP extensions. diff --git a/sccm/core/clients/deploy/deploy-clients-to-unix-and-linux-servers.md b/sccm/core/clients/deploy/deploy-clients-to-unix-and-linux-servers.md index 72d73e1476e..3b2b41b0f6a 100644 --- a/sccm/core/clients/deploy/deploy-clients-to-unix-and-linux-servers.md +++ b/sccm/core/clients/deploy/deploy-clients-to-unix-and-linux-servers.md @@ -32,7 +32,7 @@ Before you can manage a Linux or UNIX server with Configuration Manager, you mus After you install the client, you specify Client Settings in the Configuration Manager console to configure the client agent in the same way you would Windows-based clients. For more information, see [Client settings for Linux and UNIX servers](../../../core/clients/manage/manage-clients-for-linux-and-unix-servers.md#BKMK_ClientSettingsforLnU). ## About client installation packages and the universal agent - To install the client for Linux and UNIX on a specific platform, you must use the applicable client installation package for the computer where you install the client. Applicable client installation packages are included as part of each client download from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the **install** script that manages the installation of the client on each computer. + To install the client for Linux and UNIX on a specific platform, you must use the applicable client installation package for the computer where you install the client. Applicable client installation packages are included as part of each client download from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the **install** script that manages the installation of the client on each computer. When you install a client, you can use the same process and command-line properties regardless of the client installation package you use. diff --git a/sccm/core/clients/deploy/plan/planning-for-client-deployment-to-windows-embedded-devices.md b/sccm/core/clients/deploy/plan/planning-for-client-deployment-to-windows-embedded-devices.md index 1e28289f786..979a509efd9 100644 --- a/sccm/core/clients/deploy/plan/planning-for-client-deployment-to-windows-embedded-devices.md +++ b/sccm/core/clients/deploy/plan/planning-for-client-deployment-to-windows-embedded-devices.md @@ -41,11 +41,11 @@ ms.collection: M365-identity-device-management Configuration Manager supports managing the following types of write filters: -- File-Based Write Filter (FBWF) - For more information, see [File-Based Write Filter](http://go.microsoft.com/fwlink/?LinkID=204717). +- File-Based Write Filter (FBWF) - For more information, see [File-Based Write Filter](https://go.microsoft.com/fwlink/?LinkID=204717). -- Enhanced Write Filter (EWF) RAM - For more information, see [Enhanced Write Filter](http://go.microsoft.com/fwlink/?LinkId=204718). +- Enhanced Write Filter (EWF) RAM - For more information, see [Enhanced Write Filter](https://go.microsoft.com/fwlink/?LinkId=204718). -- Unified Write Filter (UWF) - For more information, see [Unified Write Filter](http://go.microsoft.com/fwlink/?LinkId=309236). +- Unified Write Filter (UWF) - For more information, see [Unified Write Filter](https://go.microsoft.com/fwlink/?LinkId=309236). Configuration Manager does not support write filter operations when the Windows Embedded device is in EWF RAM Reg mode. diff --git a/sccm/core/clients/deploy/prepare-to-deploy-mac-clients.md b/sccm/core/clients/deploy/prepare-to-deploy-mac-clients.md index 79e02c9a601..62591e48ef9 100644 --- a/sccm/core/clients/deploy/prepare-to-deploy-mac-clients.md +++ b/sccm/core/clients/deploy/prepare-to-deploy-mac-clients.md @@ -23,7 +23,7 @@ Follow these steps to make sure that you're ready to [deploy the Configuration M ## Mac prerequisites -The Mac client installation package isn't supplied with the Configuration Manager media. Download the **Clients for additional operating systems** from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184). +The Mac client installation package isn't supplied with the Configuration Manager media. Download the **Clients for additional operating systems** from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184). For the list of supported versions, see [Supported operating systems for clients and devices](/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices#mac-computers). diff --git a/sccm/core/clients/manage/asset-intelligence/configuring-asset-intelligence.md b/sccm/core/clients/manage/asset-intelligence/configuring-asset-intelligence.md index 018f5b7ff55..64d599be416 100644 --- a/sccm/core/clients/manage/asset-intelligence/configuring-asset-intelligence.md +++ b/sccm/core/clients/manage/asset-intelligence/configuring-asset-intelligence.md @@ -134,7 +134,7 @@ In addition to downloading new Asset Intelligence catalog information, the Asset 4. On the **Import** page, specify whether you are importing a Microsoft Volume Licensing (MVLS) file (.xml or .csv) or a General License Statement file (.csv). For more information about creating a General License Statement file, see [Create a general license statement information file for import](#BKMK_CreateGeneralLicenseStatement) later in this topic. > [!WARNING] - > To download an MVLS file in .csv format that you can import to the Asset Intelligence catalog, see [Microsoft Volume Licensing Service Center](http://go.microsoft.com/fwlink/p/?LinkId=226547). To access this information, you must have a registered account on the website. You must contact your Microsoft account representative for information about how to get your MVLS file in .xml format. + > To download an MVLS file in .csv format that you can import to the Asset Intelligence catalog, see [Microsoft Volume Licensing Service Center](https://go.microsoft.com/fwlink/p/?LinkId=226547). To access this information, you must have a registered account on the website. You must contact your Microsoft account representative for information about how to get your MVLS file in .xml format. 5. Enter the UNC path to the license statement file or choose **Browse** to select a network shared folder and file. diff --git a/sccm/core/clients/manage/asset-intelligence/prerequisites-for-asset-intelligence.md b/sccm/core/clients/manage/asset-intelligence/prerequisites-for-asset-intelligence.md index 30e754bc48e..6212599dd6b 100644 --- a/sccm/core/clients/manage/asset-intelligence/prerequisites-for-asset-intelligence.md +++ b/sccm/core/clients/manage/asset-intelligence/prerequisites-for-asset-intelligence.md @@ -37,4 +37,4 @@ Asset Intelligence in System Center Configuration Manager has external dependenc |Hardware Inventory Client Agent Dependencies|To collect inventory data required for some Asset Intelligence reports, the Hardware Inventory Client Agent must be enabled. In addition, some hardware inventory reporting classes that Asset Intelligence reports depend on must be enabled on primary site server computers.

For information about enabling the Hardware Inventory Client Agent, see [How to extend hardware inventory in System Center Configuration Manager](../../../../core/clients/manage/inventory/extend-hardware-inventory.md).| |Software Metering Client Agent Dependencies|A number of Asset Intelligence software reports depend on the Software Metering Client Agent for data. For information about enabling the Software Metering Client Agent, see [Monitor app usage with software metering in System Center Configuration Manager](../../../../apps/deploy-use/monitor-app-usage-with-software-metering.md).

The following Asset Intelligence reports depend on the Software Metering Client Agent to provide data:

- Software 07A - Recently Used Executables by Number of Computers
- Software 07B - Computers that Recently Used a Specified Executable
- Software 07C - Recently Used Executables on a Specific Computer
- Software 08A - Recently Used Executables by Number of Users
- Software 08B - Users that Recently Used a Specified Executable
- Software 08C - Recently Used Executables by a Specified User| |Asset Intelligence Hardware Inventory Reporting Class Prerequisites|Asset Intelligence reports in Configuration Manager depend on specific hardware inventory reporting classes. Until the hardware inventory reporting classes are enabled and clients have reported hardware inventory based on these classes, the associated Asset Intelligence reports do not contain any data. You can enable the following hardware inventory reporting classes to support Asset Intelligence reporting requirements:

- SMS_SystemConsoleUsage1
- SMS_SystemConsoleUser1
- SMS_InstalledSoftware
- SMS_AutoStartSoftware
- SMS_BrowserHelperObject
- Win32_USBDevice
- SMS_InstalledExecutable
- SMS_SoftwareShortcut
- SoftwareLicensingService
- SoftwareLicensingProduct
- SMS_SoftwareTag

1 By default, the **SMS_SystemConsoleUsage** and **SMS_SystemConsoleUser** Asset Intelligence hardware inventory reporting classes are enabled.

You can edit the Asset Intelligence hardware inventory reporting classes in the Configuration Manager console, in the **Assets and Compliance** workspace, when you click the **Asset Intelligence** node. For more information, see the [Enable Asset Intelligence hardware inventory reporting classes](../../../../core/clients/manage/asset-intelligence/configuring-asset-intelligence.md#BKMK_EnableAssetIntelligence) section in the [Configuring Asset Intelligence in System Center Configuration Manager](../../../../core/clients/manage/asset-intelligence/configuring-asset-intelligence.md) topic.| -|Reporting services point|The reporting services point site system role must be installed before software updates reports can be displayed. For more information about creating a reporting services point, see [Configuring Reporting in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=232661).| +|Reporting services point|The reporting services point site system role must be installed before software updates reports can be displayed. For more information about creating a reporting services point, see [Configuring Reporting in Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=232661).| diff --git a/sccm/core/clients/manage/inventory/hardware-inventory-for-linux-and-unix.md b/sccm/core/clients/manage/inventory/hardware-inventory-for-linux-and-unix.md index 1dab1c7734b..684371b6d1f 100644 --- a/sccm/core/clients/manage/inventory/hardware-inventory-for-linux-and-unix.md +++ b/sccm/core/clients/manage/inventory/hardware-inventory-for-linux-and-unix.md @@ -101,7 +101,7 @@ Actions for hardware inventory are entered into the client log file, **scxcm.log ### Create a custom hardware inventory provider for Linux and UNIX computers: To create a custom hardware inventory provider for the Configuration Manager client for Linux and UNIX, use **OMI Source - v.1.0.6** and follow the instructions from the OMI Getting Started Guide. This process includes creating a Managed Object Format (MOF) file that defines the schema of the new provider. Later, you import the MOF file to Configuration Manager to enable support of the new custom inventory class. - Both the OMI Source - v.1.0.6, and the OMI Getting Started Guide are available for download from [The Open Group](https://github.com/microsoft/omi/blob/master/README.md) website. You can locate these downloads on the **Documents** tab at the following web page on the OpenGroup.org website: [Open Management Infrastructure (OMI)](http://go.microsoft.com/fwlink/p/?LinkId=286805). + Both the OMI Source - v.1.0.6, and the OMI Getting Started Guide are available for download from [The Open Group](https://github.com/microsoft/omi/blob/master/README.md) website. You can locate these downloads on the **Documents** tab at the following web page on the OpenGroup.org website: [Open Management Infrastructure (OMI)](https://go.microsoft.com/fwlink/p/?LinkId=286805). ### Configure each computer that runs Linux or UNIX with the custom hardware inventory provider: After you create a custom inventory provider, you must copy and then register the provider library file on each computer that has inventory you want to collect. diff --git a/sccm/core/clients/manage/plan-internet-based-client-management.md b/sccm/core/clients/manage/plan-internet-based-client-management.md index 1c31fcdf0a6..e133b982ca2 100644 --- a/sccm/core/clients/manage/plan-internet-based-client-management.md +++ b/sccm/core/clients/manage/plan-internet-based-client-management.md @@ -194,4 +194,4 @@ Internet-based client management (sometimes referred to as IBCM) lets you manage For configuration information to support these requirements, refer to your firewall or proxy server documentation. - For similar communication requirements when you use the software update point for client connections from the internet, see the documentation for Windows Server Update Services (WSUS). For example, for WSUS on Windows Server 2003, see [Appendix D: Security Settings](http://go.microsoft.com/fwlink/p/?LinkId=143368), the deployment appendix for security settings. + For similar communication requirements when you use the software update point for client connections from the internet, see the documentation for Windows Server Update Services (WSUS). For example, for WSUS on Windows Server 2003, see [Appendix D: Security Settings](https://go.microsoft.com/fwlink/p/?LinkId=143368), the deployment appendix for security settings. diff --git a/sccm/core/clients/manage/upgrade/upgrade-clients-on-mac-computers.md b/sccm/core/clients/manage/upgrade/upgrade-clients-on-mac-computers.md index be55c65f6e1..a1762b34d3a 100644 --- a/sccm/core/clients/manage/upgrade/upgrade-clients-on-mac-computers.md +++ b/sccm/core/clients/manage/upgrade/upgrade-clients-on-mac-computers.md @@ -24,7 +24,7 @@ Follow the high-level steps described below to upgrade the client for Mac compu ## Step 1: Download the latest Mac client installation file from the Microsoft Download Center The Mac client for Configuration Manager is not supplied on the Configuration Manager installation media and must be downloaded from the Microsoft Download Center. The Mac client installation files are contained in a Windows Installer file named ConfigmgrMacClient.msi. - You can download this file from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=525184). + You can download this file from the [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=525184). ## Step 2: Run the downloaded installation file to create the Mac client installation file On a computer that runs Windows, run the **ConfigmgrMacClient.msi** that you downloaded to unpack the Mac client installation file, named **Macclient.dmg**. This file can be found, by default, in the **C:\Program Files (x86)\Microsoft\System Center 2012 Configuration Manager Mac Client** folder on the Windows computer after you have unpacked the files. diff --git a/sccm/core/get-started/2019/includes/1902-2/3735402.md b/sccm/core/get-started/2019/includes/1902-2/3735402.md index 6af1c7a3f2f..451b6a38a95 100644 --- a/sccm/core/get-started/2019/includes/1902-2/3735402.md +++ b/sccm/core/get-started/2019/includes/1902-2/3735402.md @@ -37,5 +37,5 @@ By default, the scanning agent looks at the most recently used (MRU) files list If you need a more detailed evaluation, deploy the **Office Readiness Toolkit**. This tool analyzes the code within a macro file. It checks if there are any potential compatibility concerns. For example, the file uses a function that changed in a more recent version of Office. After you run the Office Readiness Toolkit, Configuration Manager can use its results. This additional data enhances the device readiness calculation. -For more information, see [Use the Readiness Toolkit to assess application compatibility for Office 365 ProPlus](http://aka.ms/readinesstoolkit). +For more information, see [Use the Readiness Toolkit to assess application compatibility for Office 365 ProPlus](https://aka.ms/readinesstoolkit). diff --git a/sccm/core/get-started/2019/includes/1904/2839943.md b/sccm/core/get-started/2019/includes/1904/2839943.md index 6413e33c69a..6d1de745e7b 100644 --- a/sccm/core/get-started/2019/includes/1904/2839943.md +++ b/sccm/core/get-started/2019/includes/1904/2839943.md @@ -12,7 +12,7 @@ ms.collection: M365-identity-device-management This release includes the following improvements to OS deployment: -- Based on your [UserVoice feedback](http://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/36448339-powershell-cmdlet-for-modifying-nested-task-sequen), the following two PowerShell cmdlets to create and edit the [Run Task Sequence](/sccm/osd/understand/task-sequence-steps#child-task-sequence) step: +- Based on your [UserVoice feedback](https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/36448339-powershell-cmdlet-for-modifying-nested-task-sequen), the following two PowerShell cmdlets to create and edit the [Run Task Sequence](/sccm/osd/understand/task-sequence-steps#child-task-sequence) step: - **New-CMTSStepRunTaskSequence** diff --git a/sccm/core/get-started/capabilities-in-technical-preview-1511.md b/sccm/core/get-started/capabilities-in-technical-preview-1511.md index ab74aeb8e23..e0a2fb5adf9 100644 --- a/sccm/core/get-started/capabilities-in-technical-preview-1511.md +++ b/sccm/core/get-started/capabilities-in-technical-preview-1511.md @@ -92,7 +92,7 @@ The high level process to configure and use availability groups includes: - You cannot successfully add a new replica member to an Availability Group that is already in use as a site database. Instead, you must reinstall the site after the new replica member is added. -- For this scenario you might need to install the **SQL Server 2012 native client** ([from the SQL Server 2012 Feature Pack](http://www.microsoft.com/download/details.aspx?id=29065)) on the management point server. This prevents SQL connection errors (which are logged in the **mp_getauth.log** on the management point server). +- For this scenario you might need to install the **SQL Server 2012 native client** ([from the SQL Server 2012 Feature Pack](https://www.microsoft.com/download/details.aspx?id=29065)) on the management point server. This prevents SQL connection errors (which are logged in the **mp_getauth.log** on the management point server). ### Try it out! Try to complete the following tasks and then use the feedback information near the top of this topic to let us know how they worked: diff --git a/sccm/core/get-started/capabilities-in-technical-preview-1604.md b/sccm/core/get-started/capabilities-in-technical-preview-1604.md index ef1a6ea6420..0c09c3986e5 100644 --- a/sccm/core/get-started/capabilities-in-technical-preview-1604.md +++ b/sccm/core/get-started/capabilities-in-technical-preview-1604.md @@ -22,7 +22,7 @@ This article introduces the features that are available in the Technical Preview The following are new features you can try out with this version. ## Manage volume-purchased apps from the Windows Store for Business - The [Windows Store for Business](https://www.microsoft.com/en-us/business-store) is where you can find and purchase apps for your organization, individually or in volume. By connecting the store to Configuration Manager, you can manage volume-purchased apps from the Configuration Manager console, for example: + The [Windows Store for Business](https://www.microsoft.com/business-store) is where you can find and purchase apps for your organization, individually or in volume. By connecting the store to Configuration Manager, you can manage volume-purchased apps from the Configuration Manager console, for example: - You can synchronize the list of purchased apps with Configuration Manager diff --git a/sccm/core/get-started/capabilities-in-technical-preview-1703.md b/sccm/core/get-started/capabilities-in-technical-preview-1703.md index f302d0e9155..9b7f80d409b 100644 --- a/sccm/core/get-started/capabilities-in-technical-preview-1703.md +++ b/sccm/core/get-started/capabilities-in-technical-preview-1703.md @@ -136,7 +136,7 @@ This version introduces the ability to expand and collapse task sequence groups. ## Client settings to configure Windows Analytics for Upgrade Readiness -Beginning with this version, you can use device client settings to simplify the configuration of the Windows telemetry necessary to use [Windows Analytics](https://www.microsoft.com/en-us/WindowsForBusiness/windows-analytics) solutions like [Upgrade Readiness](/sccm/core/clients/manage/upgrade/upgrade-analytics) with Configuration Manager. Configuration Manager can retrieve data from Windows Analytics that can provide valuable insights into the current state of your environment based on the Windows telemetry data reported by your client computers. Windows telemetry data is reported by client computers to the Windows telemetry service, and then relevant data is subsequently transferred to Windows Analytics solutions that are hosted in one of your organization's OMS workspaces. Upgrade Readiness is a Windows Analytics solution that can help you prioritize decisions about Windows upgrades for your managed devices. +Beginning with this version, you can use device client settings to simplify the configuration of the Windows telemetry necessary to use [Windows Analytics](https://www.microsoft.com/WindowsForBusiness/windows-analytics) solutions like [Upgrade Readiness](/sccm/core/clients/manage/upgrade/upgrade-analytics) with Configuration Manager. Configuration Manager can retrieve data from Windows Analytics that can provide valuable insights into the current state of your environment based on the Windows telemetry data reported by your client computers. Windows telemetry data is reported by client computers to the Windows telemetry service, and then relevant data is subsequently transferred to Windows Analytics solutions that are hosted in one of your organization's OMS workspaces. Upgrade Readiness is a Windows Analytics solution that can help you prioritize decisions about Windows upgrades for your managed devices. For information about Windows telemetry settings, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization). diff --git a/sccm/core/get-started/capabilities-in-technical-preview-1712.md b/sccm/core/get-started/capabilities-in-technical-preview-1712.md index 2e332cd9bcd..1060e4fd195 100644 --- a/sccm/core/get-started/capabilities-in-technical-preview-1712.md +++ b/sccm/core/get-started/capabilities-in-technical-preview-1712.md @@ -145,7 +145,7 @@ We love feedback so much that we're now enabling feedback through the [Feedback - Configuration Manager OS Deployment - Configuration Manager Server -Continue to use our [user voice page](http://configurationmanager.uservoice.com/) to vote on new feature ideas in Configuration Manager. +Continue to use our [user voice page](https://configurationmanager.uservoice.com/) to vote on new feature ideas in Configuration Manager. diff --git a/sccm/core/get-started/set-up-your-lab.md b/sccm/core/get-started/set-up-your-lab.md index 0e24463e73c..e3234a089b6 100644 --- a/sccm/core/get-started/set-up-your-lab.md +++ b/sccm/core/get-started/set-up-your-lab.md @@ -29,7 +29,7 @@ Following the guidance in this topic will enable you to set up a lab for evaluat - **The lab environment uses SQL Server 2012 SP2** for the site database. - You can download an evaluation version of SQL Server 2012 from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=29066). + You can download an evaluation version of SQL Server 2012 from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=29066). SQL Server has [Supported versions of SQL Server](../../core/plan-design/configs/support-for-sql-server-versions.md#bkmk_SQLVersions) that must be met for use with System Center Configuration Manager. @@ -188,7 +188,7 @@ The next steps required to enable Configuration Manager clients to query Active 9. Click **Install** and verify that the installation completed properly in the **Notifications** pane of **Server Manager**. -10. After the base installation of .NET completes, navigate to the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=42643) to obtain the web installer for the .NET Framework 4.5.2. Click the **Download** button, then **Run** the installer. It will automatically detect and install the required components in your selected language. +10. After the base installation of .NET completes, navigate to the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=42643) to obtain the web installer for the .NET Framework 4.5.2. Click the **Download** button, then **Run** the installer. It will automatically detect and install the required components in your selected language. For additional information, please review the following articles for why these .NET Frameworks are required: diff --git a/sccm/core/migration/planning-for-the-migration-of-objects.md b/sccm/core/migration/planning-for-the-migration-of-objects.md index 545acb0e40d..24132cc8a34 100644 --- a/sccm/core/migration/planning-for-the-migration-of-objects.md +++ b/sccm/core/migration/planning-for-the-migration-of-objects.md @@ -83,7 +83,7 @@ When you migrate objects from a System Center 2012 Configuration Manager or Syst > For each package that you migrate, update the package in the destination hierarchy. This action can prevent issues with deploying the package to distribution points in the destination hierarchy. However, when you update a package on the distribution point in the destination hierarchy, clients in that hierarchy will no longer be able to get that package from a shared distribution point. To update a package in the destination hierarchy, in the Configuration Manager console, go to the Software Library, right-click on the package, and then select **Update Distribution Points**. Do this action for each package that you migrate. > [!TIP] -> You can use Microsoft System Center Configuration Manager Package Conversion Manager to convert packages and programs into System Center Configuration Manager applications. Download Package Conversion Manager from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=212950) site. For more information, see [Configuration Manager Package Conversion Manager](http://go.microsoft.com/fwlink/p/?LinkId=247245). +> You can use Microsoft System Center Configuration Manager Package Conversion Manager to convert packages and programs into System Center Configuration Manager applications. Download Package Conversion Manager from the [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=212950) site. For more information, see [Configuration Manager Package Conversion Manager](https://go.microsoft.com/fwlink/p/?LinkId=247245). ### Virtual applications When you migrate App-V packages from a supported Configuration Manager 2007 site, the migration process converts them to applications in the destination hierarchy. Additionally, based on existing advertisements for the App-V package, the following deployment types are created in the destination hierarchy: @@ -138,7 +138,7 @@ You can migrate the following operating system deployment objects from a support You can migrate configuration items and configuration baselines. > [!NOTE] -> Uninterpreted configuration items from Configuration Manager 2007 source hierarchies are not supported for migration. You cannot migrate or import these configuration items to the destination hierarchy. For more about uninterpreted configuration items, see Uninterpreted configuration items in the [About Configuration Items in Desired Configuration Management](http://go.microsoft.com/fwlink/?LinkId=103846) topic in the Configuration Manager 2007 documentation library. +> Uninterpreted configuration items from Configuration Manager 2007 source hierarchies are not supported for migration. You cannot migrate or import these configuration items to the destination hierarchy. For more about uninterpreted configuration items, see Uninterpreted configuration items in the [About Configuration Items in Desired Configuration Management](https://go.microsoft.com/fwlink/?LinkId=103846) topic in the Configuration Manager 2007 documentation library. You can import Configuration Manager 2007 Configuration Packs. The import process automatically converts the configuration packs to be compatible with System Center Configuration Manager. diff --git a/sccm/core/migration/security-and-privacy-for-migration.md b/sccm/core/migration/security-and-privacy-for-migration.md index 7c31aece404..8f6e7dc1bba 100644 --- a/sccm/core/migration/security-and-privacy-for-migration.md +++ b/sccm/core/migration/security-and-privacy-for-migration.md @@ -43,7 +43,7 @@ When you migrate data from a source site to a destination site, you lose any aud For more information about security and privacy information, see one of the following topics: -- For more information about the privacy information for Configuration Manager 2007, see [Security and Privacy for Configuration Manager 2007](http://go.microsoft.com/fwlink/p/?LinkId=216450) in the Configuration Manager 2007 documentation library. +- For more information about the privacy information for Configuration Manager 2007, see [Security and Privacy for Configuration Manager 2007](https://go.microsoft.com/fwlink/p/?LinkId=216450) in the Configuration Manager 2007 documentation library. - For more information about the privacy information for System Center 2012 Configuration Manager, see [Security and Privacy for System Center 2012 Configuration Manager](https://technet.microsoft.com/library/gg682033.aspx) in the System Center 2012 Configuration Manager documentation library. diff --git a/sccm/core/misc/eula/microsoft-sql-server-2012-native-client.md b/sccm/core/misc/eula/microsoft-sql-server-2012-native-client.md index 4380afed103..3c708663315 100644 --- a/sccm/core/misc/eula/microsoft-sql-server-2012-native-client.md +++ b/sccm/core/misc/eula/microsoft-sql-server-2012-native-client.md @@ -100,7 +100,7 @@ for this software, unless other terms accompany those items. If so, those terms 6. **DOCUMENTATION.** Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes. -7. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](http://www.microsoft.com/exporting). +7. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](https://www.microsoft.com/exporting). 8. **SUPPORT SERVICES.** Because this software is "as is," we may not provide support services for it. diff --git a/sccm/core/misc/eula/microsoft-sql-server-2014-express.md b/sccm/core/misc/eula/microsoft-sql-server-2014-express.md index e8853ba2aef..876ea589ca5 100644 --- a/sccm/core/misc/eula/microsoft-sql-server-2014-express.md +++ b/sccm/core/misc/eula/microsoft-sql-server-2014-express.md @@ -94,7 +94,7 @@ ms.collection: M365-identity-device-management - use the software for commercial software hosting services. -4. **THIRD PARTY NOTICES.** The software may include third party code, that Microsoft, not the third party, licenses to you under the terms set forth in this agreement. Notices, if any, for any third party code are included for your information only. Additionally, any third party scripts, linked to, called or referenced from this software, are licensed to you by the third parties that own such code, not by Microsoft, see ASP.NET Ajax CDN Terms of Use: [http://www.asp.net/ajaxlibrary/CDN.ashx](http://www.asp.net/ajaxlibrary/CDN.ashx). +4. **THIRD PARTY NOTICES.** The software may include third party code, that Microsoft, not the third party, licenses to you under the terms set forth in this agreement. Notices, if any, for any third party code are included for your information only. Additionally, any third party scripts, linked to, called or referenced from this software, are licensed to you by the third parties that own such code, not by Microsoft, see ASP.NET Ajax CDN Terms of Use: [https://www.asp.net/ajaxlibrary/CDN.ashx](https://www.asp.net/ajaxlibrary/CDN.ashx). 5. **BACKUP COPY.** You may make one backup copy of the software. You may use it only to reinstall the software. @@ -102,7 +102,7 @@ ms.collection: M365-identity-device-management 7. **TRANSFER TO A THIRD PARTY.** The first user of the software may transfer it and this agreement directly to a third party. Before the transfer, that party must agree that this agreement applies to the transfer and use of the software. The first user must uninstall the software before transferring it separately from the device. The first user may not retain any copies. -8. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](http://www.microsoft.com/exporting). +8. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](https://www.microsoft.com/exporting). 9. **SUPPORT SERVICES.** Because this software is "as is," we may not provide support services for it. diff --git a/sccm/core/misc/eula/microsoft-sql-server-2014-shared-management-objects.md b/sccm/core/misc/eula/microsoft-sql-server-2014-shared-management-objects.md index 7f067f09f3b..94bf7d677b8 100644 --- a/sccm/core/misc/eula/microsoft-sql-server-2014-shared-management-objects.md +++ b/sccm/core/misc/eula/microsoft-sql-server-2014-shared-management-objects.md @@ -98,7 +98,7 @@ These license terms are an agreement between Microsoft Corporation (or based on 6. **DOCUMENTATION.** Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes. -7. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](http://www.microsoft.com/exporting). +7. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](https://www.microsoft.com/exporting). 8. **SUPPORT SERVICES.** Because this software is "as is," we may not provide support services for it. diff --git a/sccm/core/misc/eula/microsoft-sql-server-compact-4.0-service-pack-1-sp1.md b/sccm/core/misc/eula/microsoft-sql-server-compact-4.0-service-pack-1-sp1.md index 85582f8d1ec..10fb3d2486a 100644 --- a/sccm/core/misc/eula/microsoft-sql-server-compact-4.0-service-pack-1-sp1.md +++ b/sccm/core/misc/eula/microsoft-sql-server-compact-4.0-service-pack-1-sp1.md @@ -114,7 +114,7 @@ ms.collection: M365-identity-device-management 5. **DOCUMENTATION.** Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes. -6. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](http://www.microsoft.com/exporting). +6. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](https://www.microsoft.com/exporting). 7. **SUPPORT SERVICES.** Because this software is "as is," we may not provide support services for it. diff --git a/sccm/core/misc/eula/microsoft-system-center-configuration-manager-evaluation.md b/sccm/core/misc/eula/microsoft-system-center-configuration-manager-evaluation.md index 9ca91e19e0b..14dd5eae7cd 100644 --- a/sccm/core/misc/eula/microsoft-system-center-configuration-manager-evaluation.md +++ b/sccm/core/misc/eula/microsoft-system-center-configuration-manager-evaluation.md @@ -55,11 +55,11 @@ ms.collection: M365-identity-device-management 3. **Included Microsoft Programs.** The software contains other Microsoft programs. These license terms identify them, and indicate if other license terms apply to your use of those programs, or if these license terms apply to your use of them. For the program included but not identified, the license terms with those programs apply to your use. - 4. **Third Party Programs.** The software may include third party programs that Microsoft, not the third party, licenses to you under this agreement. Notices, if any, for the third party programs are included for your information only at http://go.microsoft.com/fwlink/?LinkID=789409. + 4. **Third Party Programs.** The software may include third party programs that Microsoft, not the third party, licenses to you under this agreement. Notices, if any, for the third party programs are included for your information only at https://go.microsoft.com/fwlink/?LinkID=789409. 2. **ADDITIONAL LICENSING REQUIREMENT AND/OR USE RIGHTS.** - 1. **SQL Server Branded Components.** The software contains Microsoft SQL Server branded components and the license terms that would apply to your use of these programs are at http://go.microsoft.com/fwlink/?LinkID=787077. If you do not agree to their license terms, you may not use these programs. + 1. **SQL Server Branded Components.** The software contains Microsoft SQL Server branded components and the license terms that would apply to your use of these programs are at https://go.microsoft.com/fwlink/?LinkID=787077. If you do not agree to their license terms, you may not use these programs. 2. **Site Hierarchy - Geographical View.** The Server Software may include a feature that retrieves content such as maps, images and other data through the Bing Maps (or successor branded) application programming interface (the "Bing Maps API"). The purpose of this feature is to display site data on top of maps, aerial and hybrid imagery. You may use the feature to display the site data on your screen or print a written report including that display. This may be done only in conjunction with and through methods and means of access integrated in the software. You may not otherwise copy, store, archive, or create a database of the content available through the Bing Maps API. You may not use the following for any purpose even if they are available through the Bing Maps API: @@ -67,13 +67,13 @@ ms.collection: M365-identity-device-management - any Road Traffic Data or Bird's Eye Imagery (or associated metadata). - Your use of the Bing Maps API and associated content is also subject to the additional terms and conditions at http://go.microsoft.com/fwlink/?LinkID=223934. + Your use of the Bing Maps API and associated content is also subject to the additional terms and conditions at https://go.microsoft.com/fwlink/?LinkID=223934. 3. **No Copying or Distributing Data Sets.** You may not copy or distribute any data set (or any portion of a data set) included in the software. 3. **INTERNET-BASED SERVICES.** Microsoft provides Internet-based services with the software. It may change or cancel them at any time. - 1. **Consent for Internet-Based Services.** The software features described below and in the System Center Configuration Manager Privacy Statement connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. In some cases, you may switch off these features or not use them. For more information about these features and how to control settings, see http://go.microsoft.com/fwlink/?LinkID=619434. **By using these features, you consent to the transmission of this information.** Microsoft does not use the information to identify or contact you. + 1. **Consent for Internet-Based Services.** The software features described below and in the System Center Configuration Manager Privacy Statement connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. In some cases, you may switch off these features or not use them. For more information about these features and how to control settings, see https://go.microsoft.com/fwlink/?LinkID=619434. **By using these features, you consent to the transmission of this information.** Microsoft does not use the information to identify or contact you. 1. **Computer Information.** The following features use Internet protocols, which send to the appropriate systems computer information, such as your Internet protocol address, the type of operating system, browser and name and version of the software you are using, and the language code of the device where you installed the software. Microsoft uses this information to make the Internet-based services available to you. @@ -97,7 +97,7 @@ ms.collection: M365-identity-device-management In some cases, you will not receive a separate notice before this feature takes effect. By installing the software, you consent to the transmission of standard computer information and the automatic downloading and installation of Updates. - - **Customer Experience Improvement Program (CEIP).** This software uses CEIP. CEIP automatically sends Microsoft information about your hardware and how you use this software. We do not use this information to identify or contact you. To learn more about CEIP, see http://go.microsoft.com/fwlink/?LinkId=52097. + - **Customer Experience Improvement Program (CEIP).** This software uses CEIP. CEIP automatically sends Microsoft information about your hardware and how you use this software. We do not use this information to identify or contact you. To learn more about CEIP, see https://go.microsoft.com/fwlink/?LinkId=52097. - **Usage Data.** Microsoft automatically collects usage data over the internet. Microsoft uses this data to: a) help improve your installation or upgrade experience, and b) improve the quality and security of Microsoft products and services. There are 3 levels of usage data (Basic, Enhanced and Full). This feature is set on the "Enhanced" level by default. @@ -107,7 +107,7 @@ ms.collection: M365-identity-device-management - **"Full"** includes all data collected in "Basic" and "Enhanced" levels as well as data about endpoint protection (number of devices in different EP states), update compliance percentages, and software updates. This level can also include advanced diagnostic information like system files and memory snapshots which may include personal information that existed in memory or log files at the time of capture. Microsoft will not use this information to identify you, contact you, or for advertising purposes. - Administrators can change the level of data collected in the Usage Data setting of the Configuration Manager console. For more information, see the "Learn More" article about Usage Data Levels and Settings at http://go.microsoft.com/fwlink/?LinkId=624310 and the Privacy Statement for System Center Configuration Manager at http://go.microsoft.com/fwlink/?LinkID=619434. + Administrators can change the level of data collected in the Usage Data setting of the Configuration Manager console. For more information, see the "Learn More" article about Usage Data Levels and Settings at https://go.microsoft.com/fwlink/?LinkId=624310 and the Privacy Statement for System Center Configuration Manager at https://go.microsoft.com/fwlink/?LinkID=619434. - **Microsoft Error Reporting Service.** This feature helps Microsoft and Windows partners diagnose problems in the software and provide solutions. Not all problems will have a solution but when a solution is available, it will be offered as a step to solve a problem you have reported or as an update to install. As part of setup and installation, the Microsoft Error Reporting Service sends to Microsoft information about setup and installation failures in order to attempt to diagnose the problem. To help prevent problems and make the software more reliable, some solutions are also included in service packs and future versions of the software. diff --git a/sccm/core/misc/eula/microsoft-system-center-configuration-manager-technical-preview.md b/sccm/core/misc/eula/microsoft-system-center-configuration-manager-technical-preview.md index 8d708275c7f..7efc12225d9 100644 --- a/sccm/core/misc/eula/microsoft-system-center-configuration-manager-technical-preview.md +++ b/sccm/core/misc/eula/microsoft-system-center-configuration-manager-technical-preview.md @@ -66,13 +66,13 @@ for this software, unless other terms accompany those items. If so, those terms - any Road Traffic Data or Bird’s Eye Imagery (or associated metadata). - Your use of the Bing Maps API and associated content is also subject to the additional terms and conditions at http://go.microsoft.com/fwlink/?LinkID=223934. + Your use of the Bing Maps API and associated content is also subject to the additional terms and conditions at https://go.microsoft.com/fwlink/?LinkID=223934. **f. No Copying or Distributing Data Sets.** You may not copy or distribute any data set (or any portion of a data set) included in the software. 2. **INTERNET-BASED SERVICES.** Microsoft provides Internet-based services with the software. It may change or cancel them at any time. - **a. Consent for Internet-Based Services.** The software features described below and in the System Center Configuration Manager Privacy Statement connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. In some cases, you may switch off these features or not use them. For more information about these features and how to control settings, see http://go.microsoft.com/fwlink/?LinkID=619434. **By using these features, you consent to the transmission of this information.** Microsoft does not use the information to identify or contact you. + **a. Consent for Internet-Based Services.** The software features described below and in the System Center Configuration Manager Privacy Statement connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. In some cases, you may switch off these features or not use them. For more information about these features and how to control settings, see https://go.microsoft.com/fwlink/?LinkID=619434. **By using these features, you consent to the transmission of this information.** Microsoft does not use the information to identify or contact you. - **i. Computer Information.** The following features use Internet protocols, which send to the appropriate systems computer information, such as your Internet protocol address, the type of operating system, browser and name and version of the software you are using, and the language code of the device where you installed the software. Microsoft uses this information to make the Internet-based services available to you. @@ -95,7 +95,7 @@ for this software, unless other terms accompany those items. If so, those terms In some cases, you will not receive a separate notice before this feature takes effect. By installing the software, you consent to the transmission of standard computer information and the automatic downloading and installation of Updates. - - **Customer Experience Improvement Program (CEIP)**. This software uses CEIP. CEIP automatically sends Microsoft information about your hardware and how you use this software. We do not use this information to identify or contact you. To learn more about CEIP, see http://go.microsoft.com/fwlink/?LinkId=52097. + - **Customer Experience Improvement Program (CEIP)**. This software uses CEIP. CEIP automatically sends Microsoft information about your hardware and how you use this software. We do not use this information to identify or contact you. To learn more about CEIP, see https://go.microsoft.com/fwlink/?LinkId=52097. - **Usage Data**. Microsoft automatically collects usage data over the internet. Microsoft uses this data to: a) help improve your installation or upgrade experience, and b) improve the quality and security of Microsoft products and services. There are 3 levels of usage data (Basic, Enhanced and Full). This feature is set on the “Enhanced” level by default. @@ -105,7 +105,7 @@ for this software, unless other terms accompany those items. If so, those terms - **“Full”** includes all data collected in “Basic” and “Enhanced” levels as well as data about endpoint protection (number of devices in different EP states), update compliance percentages, and software updates. This level can also include advanced diagnostic information like system files and memory snapshots which may include personal information that existed in memory or log files at the time of capture. Microsoft will not use this information to identify you, contact you, or for advertising purposes. - For more information, see the “Learn More” article about Usage Data Levels and Settings at http://go.microsoft.com/fwlink/?LinkId=624310 and the Privacy Statement for System Center Configuration Manager at http://go.microsoft.com/fwlink/?LinkID=619434. + For more information, see the “Learn More” article about Usage Data Levels and Settings at https://go.microsoft.com/fwlink/?LinkId=624310 and the Privacy Statement for System Center Configuration Manager at https://go.microsoft.com/fwlink/?LinkID=619434. - **Microsoft Error Reporting Service**. This feature helps Microsoft and Windows partners diagnose problems in the software and provide solutions. Not all problems will have a solution but when a solution is available, it will be offered as a step to solve a problem you have reported or as an update to install. As part of setup and installation, the Microsoft Error Reporting Service sends to Microsoft information about setup and installation failures in order to attempt to diagnose the problem. To help prevent problems and make the software more reliable, some solutions are also included in service packs and future versions of the software. diff --git a/sccm/core/misc/eula/microsoft-system-center-configuration-manager.md b/sccm/core/misc/eula/microsoft-system-center-configuration-manager.md index 0dbcbb0d209..fe7b6417739 100644 --- a/sccm/core/misc/eula/microsoft-system-center-configuration-manager.md +++ b/sccm/core/misc/eula/microsoft-system-center-configuration-manager.md @@ -26,4 +26,4 @@ ms.collection: M365-identity-device-management You may not use this software if you have not validly acquired a license for the software or online service from Microsoft or its licensed distributors. -Third Party Programs. The software may include third party programs that Microsoft, not the third party, licenses to you under this agreement. Notices, if any, for the third party programs are included for your information only at http://go.microsoft.com/fwlink/?LinkID=789409. +Third Party Programs. The software may include third party programs that Microsoft, not the third party, licenses to you under this agreement. Notices, if any, for the third party programs are included for your information only at https://go.microsoft.com/fwlink/?LinkID=789409. diff --git a/sccm/core/misc/eula/microsoft-system-center-endpoint-protection-evaluation.md b/sccm/core/misc/eula/microsoft-system-center-endpoint-protection-evaluation.md index 15b140daf6f..ae656121540 100644 --- a/sccm/core/misc/eula/microsoft-system-center-endpoint-protection-evaluation.md +++ b/sccm/core/misc/eula/microsoft-system-center-endpoint-protection-evaluation.md @@ -46,7 +46,7 @@ for this software, unless other terms accompany those items. If so, those terms 2. **INTERNET-BASED SERVICES.** Microsoft provides Internet-based services with the software. It may change or cancel them at any time. - 1. **Consent for Internet-Based Services.** The software features described below and in the System Center Endpoint Protection Privacy Statement connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. In some cases, you may switch off these features or not use them. For more information about these features and how to control settings, see http://go.microsoft.com/fwlink/?LinkID=619434. **By using these features, you consent to the transmission of this information.** Microsoft does not use the information to identify or contact you. + 1. **Consent for Internet-Based Services.** The software features described below and in the System Center Endpoint Protection Privacy Statement connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. In some cases, you may switch off these features or not use them. For more information about these features and how to control settings, see https://go.microsoft.com/fwlink/?LinkID=619434. **By using these features, you consent to the transmission of this information.** Microsoft does not use the information to identify or contact you. 1. **Computer Information.** The following features use Internet protocols, which send to the appropriate systems computer information, such as your Internet protocol address, the type of operating system, browser and name and version of the software you are using, and the language code of the device where you installed the software. Microsoft uses this information to make the Internet-based services available to you. @@ -62,7 +62,7 @@ for this software, unless other terms accompany those items. If so, those terms - **Potentially Unwanted Software.** The software will search your computer for low to medium severity Malware, including but not limited to, spyware, and other potentially unwanted software ("Potentially Unwanted Software"). The software will only remove or disable low to medium severity Potentially Unwanted Software if you agree. Removing or disabling this Potentially Unwanted Software may cause other software on your computer to stop working, and it may cause you to breach a license to use other software on your computer, if the other software installed this Potentially Unwanted Software on your computer as a condition of your use of the other software. You should read the license agreements for other software before authorizing the removal of this Potentially Unwanted Software. By using this software, it is possible that you or the system will also remove or disable software that is not Potentially Unwanted Software. - - **Customer Experience Improvement Program (CEIP).** This software uses CEIP. CEIP automatically sends Microsoft information about your hardware and how you use this software. We do not use this information to identify or contact you. To learn more about CEIP, see http://go.microsoft.com/fwlink/?LinkId=52097. + - **Customer Experience Improvement Program (CEIP).** This software uses CEIP. CEIP automatically sends Microsoft information about your hardware and how you use this software. We do not use this information to identify or contact you. To learn more about CEIP, see https://go.microsoft.com/fwlink/?LinkId=52097. - **Usage Data.** Microsoft automatically collects usage data over the internet. Microsoft uses this data to: a) help improve your installation or upgrade experience, and b) improve the quality and security of Microsoft products and services. There are 3 levels of usage data (Basic, Enhanced and Full). This feature is set on the "Enhanced" level by default. @@ -72,9 +72,9 @@ for this software, unless other terms accompany those items. If so, those terms - **"Full"** includes all data collected in "Basic" and "Enhanced" levels as well as data about endpoint protection (number of devices in different EP states), update compliance percentages, and software updates. This level can also include advanced diagnostic information like system files and memory snapshots which may include personal information that existed in memory or log files at the time of capture. Microsoft will not use this information to identify you, contact you, or for advertising purposes. - Administrators can change the level of data collected in the "Usage Data" setting of the Configuration Manager console. For more information, see the "Learn More" article about Usage Data Levels and Settings at http://go.microsoft.com/fwlink/?LinkId=624310 and the Privacy Statement for System Center Configuration Manager at http://go.microsoft.com/fwlink/?LinkID=619434. + Administrators can change the level of data collected in the "Usage Data" setting of the Configuration Manager console. For more information, see the "Learn More" article about Usage Data Levels and Settings at https://go.microsoft.com/fwlink/?LinkId=624310 and the Privacy Statement for System Center Configuration Manager at https://go.microsoft.com/fwlink/?LinkID=619434. - - **Microsoft Cloud Protection Service Participation (formerly known as Microsoft Active Protection Service or MAPS).** The Microsoft Cloud Protection Service antimalware community is a worldwide community that includes users of the software. Upon initial installation, users will be subscribed by default to participate in the Microsoft Cloud Protection Service. If a Microsoft Cloud Protection Service report includes details about Malware or Potentially Unwanted Software that the software may be able to remove, the Microsoft Cloud Protection Service will download the latest signature to address it. The Microsoft Cloud Protection Service can also find "false positives" (where something originally identified as Malware turns out not to be) and fix them. In some instances, personal information might unintentionally be sent to Microsoft. However, Microsoft will not use this information to identify you or contact you. To learn more about the Microsoft Cloud Protection Service and the information this feature transmits to Microsoft, see the privacy statement at http://go.microsoft.com/fwlink/?LinkID=525344. + - **Microsoft Cloud Protection Service Participation (formerly known as Microsoft Active Protection Service or MAPS).** The Microsoft Cloud Protection Service antimalware community is a worldwide community that includes users of the software. Upon initial installation, users will be subscribed by default to participate in the Microsoft Cloud Protection Service. If a Microsoft Cloud Protection Service report includes details about Malware or Potentially Unwanted Software that the software may be able to remove, the Microsoft Cloud Protection Service will download the latest signature to address it. The Microsoft Cloud Protection Service can also find "false positives" (where something originally identified as Malware turns out not to be) and fix them. In some instances, personal information might unintentionally be sent to Microsoft. However, Microsoft will not use this information to identify you or contact you. To learn more about the Microsoft Cloud Protection Service and the information this feature transmits to Microsoft, see the privacy statement at https://go.microsoft.com/fwlink/?LinkID=525344. 2. **Use of Information.** We may use the computer information, Microsoft Cloud Protection Service data, error reports, CEIP information, and Malware reports, to improve our software and services. We may also share it with others, such as hardware and software vendors. They may use the information to improve how their products run with Microsoft software. diff --git a/sccm/core/misc/eula/microsoft-system-clr-types-for-microsoft-sql-server-2014.md b/sccm/core/misc/eula/microsoft-system-clr-types-for-microsoft-sql-server-2014.md index 67701eb0dce..ba86bf3b2fd 100644 --- a/sccm/core/misc/eula/microsoft-system-clr-types-for-microsoft-sql-server-2014.md +++ b/sccm/core/misc/eula/microsoft-system-clr-types-for-microsoft-sql-server-2014.md @@ -99,7 +99,7 @@ These license terms are an agreement between Microsoft Corporation (or based on 6. **DOCUMENTATION.** Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes. -7. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](http://www.microsoft.com/exporting). +7. **EXPORT RESTRICTIONS.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see [www.microsoft.com/exporting](https://www.microsoft.com/exporting). 8. **SUPPORT SERVICES.** Because this software is "as is," we may not provide support services for it. diff --git a/sccm/core/misc/eula/third-party-notices.md b/sccm/core/misc/eula/third-party-notices.md index 602905b1fee..cdd87b8fbe6 100644 --- a/sccm/core/misc/eula/third-party-notices.md +++ b/sccm/core/misc/eula/third-party-notices.md @@ -74,7 +74,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI OpenSSL This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. -(http://www.openssl.org/). +(https://www.openssl.org/). OpenSSL License Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved. @@ -86,13 +86,13 @@ This product includes software developed by the OpenSSL Project for use in the O 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: - "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" + "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.openssl.org/)" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. -6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" +6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. @@ -144,7 +144,7 @@ THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRA Camellia assembler implementation This product includes material developed by Andy Polyakov for a Camellia assembler implementation. -(http://www.openssl.org/~appro/camellia/). +(https://www.openssl.org/~appro/camellia/). Copyright (c) 2008 Andy Polyakov (appro@openssl.org) @@ -164,7 +164,7 @@ HIS SOFTWARE IS PROVIDED BY Andy Polyakov "AS IS" AND ANY EXPRESS OR IMPLIED WAR **NOTICES AND INFORMATION BEGIN HERE** FreeBSD's cd.c -This software contains material from FreeBSD's cd.c. (http://www.freebsd.org/). +This software contains material from FreeBSD's cd.c. (https://www.freebsd.org/). Copyright (c) 1994, 1995, 1997 Charles M. Hannum. All rights reserved. @@ -221,7 +221,7 @@ THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED WARRA The MIT License - Copyright (c) 2010-2015 Google, Inc. http://angularjs.org + Copyright (c) 2010-2015 Google, Inc. https://angularjs.org Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: @@ -275,7 +275,7 @@ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND Copyright 2006 The Closure Library Authors. All Rights Reserved. - Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. + Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS-IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. @@ -311,7 +311,7 @@ Provided for Informational Purposes Only Copyright 2015 Microsoft Corporation. All rights reserved. - Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. + Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. @@ -324,7 +324,7 @@ Unless required by applicable law or agreed to in writing, software distributed Copyright 2016 Microsoft. All rights reserved. -Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. +Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS-IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. @@ -338,7 +338,7 @@ Unless required by applicable law or agreed to in writing, software distributed Copyright 2016 Microsoft. All rights reserved. -Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. +Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS-IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. @@ -351,7 +351,7 @@ Unless required by applicable law or agreed to in writing, software distributed Copyright 2016 Microsoft. All rights reserved. -Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. +Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS-IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. @@ -364,7 +364,7 @@ Unless required by applicable law or agreed to in writing, software distributed Copyright 2016 Microsoft. All rights reserved. -Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. +Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS-IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. @@ -396,7 +396,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI Copyright (c) 2018 Microsoft Corporation -Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. +Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. diff --git a/sccm/core/misc/online-documentation.md b/sccm/core/misc/online-documentation.md index 43743718179..4590d619127 100644 --- a/sccm/core/misc/online-documentation.md +++ b/sccm/core/misc/online-documentation.md @@ -54,7 +54,7 @@ Find the documentation library for the product version that you use: **Release notes:** Release notes for this technical preview are included with the core documentation for this release, and are presented in-line with the information for each feature. -**Accessibility:** Accessibility information for this technical preview is unchanged from System Center 2012 Configuration Manager. See [Accessibility Features of Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=258586), for information about the features, products, and services that make Configuration Manager more accessible for people with disabilities. +**Accessibility:** Accessibility information for this technical preview is unchanged from System Center 2012 Configuration Manager. See [Accessibility Features of Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=258586), for information about the features, products, and services that make Configuration Manager more accessible for people with disabilities. ## System Center 2012 Configuration Manager **On-line documentation:** for the following: @@ -85,10 +85,10 @@ you can view the on-line documentation in the following guides on TechNet: **Release notes and technical publications:** The release notes and technical publications supplement the Configuration Manager guides. The release notes contain information that is not available in the product documentation and that is required to successfully install Configuration Manager. Technical publications provide additional information that supports Configuration Manager. -- [Release Notes for System Center 2012 Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=529437) +- [Release Notes for System Center 2012 Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=529437) -- [Technical Publications for System Center 2012 Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=261032) +- [Technical Publications for System Center 2012 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=261032) -**Accessibility:** See the online topic, [Accessibility Features of Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=258586), for information about the features, products, and services that make Configuration Manager more accessible for people with disabilities. +**Accessibility:** See the online topic, [Accessibility Features of Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=258586), for information about the features, products, and services that make Configuration Manager more accessible for people with disabilities. -**Downloadable documentation:** You can download a [copy of this technical documentation from the Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=253643). Use the on-line TechNet library for the most up-to-date information. +**Downloadable documentation:** You can download a [copy of this technical documentation from the Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=253643). Use the on-line TechNet library for the most up-to-date information. diff --git a/sccm/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md b/sccm/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md index aa0a14249bc..304c8419658 100644 --- a/sccm/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md +++ b/sccm/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md @@ -56,7 +56,7 @@ The following sections include additional details for features removed with vers With Configuration Manager, native support for AMT-based computers from within the Configuration Manager console has been removed. -- AMT-based computers remain fully managed when you use the [Intel SCS Add-on for Microsoft System Center Configuration Manager](http://www.intel.com/content/www/us/en/software/setup-configuration-software.html). The add-on provides you access to the latest capabilities to manage AMT, while removing limitations introduced until Configuration Manager could incorporate those changes. +- AMT-based computers remain fully managed when you use the [Intel SCS Add-on for Microsoft System Center Configuration Manager](https://www.intel.com/content/www/us/en/software/setup-configuration-software.html). The add-on provides you access to the latest capabilities to manage AMT, while removing limitations introduced until Configuration Manager could incorporate those changes. - Out of Band Management in System Center 2012 Configuration Manager is not affected by this change. diff --git a/sccm/core/plan-design/changes/what-has-changed-from-configuration-manager-2012.md b/sccm/core/plan-design/changes/what-has-changed-from-configuration-manager-2012.md index 0614870e5e5..06e6abb3035 100644 --- a/sccm/core/plan-design/changes/what-has-changed-from-configuration-manager-2012.md +++ b/sccm/core/plan-design/changes/what-has-changed-from-configuration-manager-2012.md @@ -70,7 +70,7 @@ For more information, see [Diagnostics and usage data](/sccm/core/plan-design/di ## Support for Intel Active Management Technology (AMT) -Configuration Manager current branch removes native support for AMT-based computers from within the Configuration Manager console. AMT-based computers remain fully managed when you use the [Intel SCS Add-on for Microsoft System Center Configuration Manager](http://www.intel.com/content/www/us/en/software/setup-configuration-software.html). The add-on provides you access to the latest capabilities to manage AMT, while removing limitations introduced until Configuration Manager could incorporate those changes. +Configuration Manager current branch removes native support for AMT-based computers from within the Configuration Manager console. AMT-based computers remain fully managed when you use the [Intel SCS Add-on for Microsoft System Center Configuration Manager](https://www.intel.com/content/www/us/en/software/setup-configuration-software.html). The add-on provides you access to the latest capabilities to manage AMT, while removing limitations introduced until Configuration Manager could incorporate those changes. The removal of integrated AMT for Configuration Manager includes out-of-band management. The out-of-band management point site system role is no longer available. diff --git a/sccm/core/plan-design/configs/supported-configurations.md b/sccm/core/plan-design/configs/supported-configurations.md index ee7bc779136..0ca9ff732e4 100644 --- a/sccm/core/plan-design/configs/supported-configurations.md +++ b/sccm/core/plan-design/configs/supported-configurations.md @@ -22,10 +22,10 @@ The information in this and the following topics is essential for helping you id When a Configuration Manager feature or capability requires more specific configurations, that information is included with the feature-specific documentation, and is supplemental to the more general configuration details. - The products and technologies that are described in the following topics are supported by Configuration Manager. However, their inclusion in this content does not imply an extension of support for any product beyond that product's individual support lifecycle. Products that are beyond their support lifecycle are not supported for use with Configuration Manager. For more information about Microsoft Support Lifecycles, visit the [Microsoft Support Lifecycle](http://go.microsoft.com/fwlink/p/?LinkId=208270) website. + The products and technologies that are described in the following topics are supported by Configuration Manager. However, their inclusion in this content does not imply an extension of support for any product beyond that product's individual support lifecycle. Products that are beyond their support lifecycle are not supported for use with Configuration Manager. For more information about Microsoft Support Lifecycles, visit the [Microsoft Support Lifecycle](https://go.microsoft.com/fwlink/p/?LinkId=208270) website. > [!NOTE] -> For information about Microsoft support lifecycle policy, go to the Microsoft Support Lifecycle Support Policy FAQ website at [Microsoft Support Lifecycle Policy FAQ](http://go.microsoft.com/fwlink/p/?LinkId=31976). +> For information about Microsoft support lifecycle policy, go to the Microsoft Support Lifecycle Support Policy FAQ website at [Microsoft Support Lifecycle Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976). Additionally, products and product versions that are not listed in the following topics are not supported with System Center Configuration Manager unless they have been announced on the [Enterprise Mobility and Security Blog](https://blogs.technet.microsoft.com/enterprisemobility/). At times, the content on this blog precedes an update to this body of documentation. diff --git a/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices.md b/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices.md index 9a04576acda..142c636beb4 100644 --- a/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices.md +++ b/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices.md @@ -222,7 +222,7 @@ For more information, see [How to deploy clients to Macs](/sccm/core/clients/dep > [!Important] > Configuration Manager version 1902 drops support for Linux and UNIX as a client. Deprecation was announced with [version 1802](/sccm/core/plan-design/changes/whats-new-in-version-1802#deprecation-announcement-for-linux-and-unix-client-support). Consider Microsoft Azure Management for managing Linux servers. Azure solutions have extensive Linux support that in most cases exceed Configuration Manager functionality, including end-to-end patch management for Linux. -The Linux and UNIX client installation packages aren't supplied with the Configuration Manager media. Download the **Clients for Additional Operating Systems** from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the script that manages the installation of the client on each computer. +The Linux and UNIX client installation packages aren't supplied with the Configuration Manager media. Download the **Clients for Additional Operating Systems** from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the script that manages the installation of the client on each computer. ### Requirements and limitations diff --git a/sccm/core/plan-design/hierarchy/understand-how-clients-find-site-resources-and-services.md b/sccm/core/plan-design/hierarchy/understand-how-clients-find-site-resources-and-services.md index c1d11edc0db..b2dc5f38232 100644 --- a/sccm/core/plan-design/hierarchy/understand-how-clients-find-site-resources-and-services.md +++ b/sccm/core/plan-design/hierarchy/understand-how-clients-find-site-resources-and-services.md @@ -57,7 +57,7 @@ A client selects a management point to communicate with based on the client's c You can use preferred management points. Preferred management points are management points from a client's assigned site that are associated with a boundary group that the client is using to find site system servers. A preferred management point's association with a boundary group as a site system server is similar to how distribution points or state migration points are associated with a boundary group. If you enable preferred management points for the hierarchy, when a client uses a management point from its assigned site, it will try to use a preferred management point before using other management points from its assigned site. -You can also use the information in the [management point affinity](http://blogs.technet.com/b/jchalfant/archive/2014/09/22/management-point-affinity-added-in-configmgr-2012-r2-cu3.aspx) blog on TechNet.com to configure management point affinity. Management point affinity overrides the default behavior for assigned management points and lets the client use one or more specific management points. +You can also use the information in the [management point affinity](https://blogs.technet.com/b/jchalfant/archive/2014/09/22/management-point-affinity-added-in-configmgr-2012-r2-cu3.aspx) blog on TechNet.com to configure management point affinity. Management point affinity overrides the default behavior for assigned management points and lets the client use one or more specific management points. Each time a client needs to contact a management point, it checks the MP list, which it stores locally in Windows Management Instrumentation (WMI). The client creates an initial MP list when it's installed. The client then periodically updates the list with details about each management point in the hierarchy. diff --git a/sccm/core/plan-design/network/internet-endpoints.md b/sccm/core/plan-design/network/internet-endpoints.md index 724b6cd14cb..70558df35f3 100644 --- a/sccm/core/plan-design/network/internet-endpoints.md +++ b/sccm/core/plan-design/network/internet-endpoints.md @@ -148,7 +148,7 @@ Allow the active software update point to access the following endpoints so that - `http://download.windowsupdate.com` -- `http://download.microsoft.com` +- `https://download.microsoft.com` - `http://*.download.windowsupdate.com` diff --git a/sccm/core/plan-design/network/pki-certificate-requirements.md b/sccm/core/plan-design/network/pki-certificate-requirements.md index 467cc0f1ba6..8dbd67e06a2 100644 --- a/sccm/core/plan-design/network/pki-certificate-requirements.md +++ b/sccm/core/plan-design/network/pki-certificate-requirements.md @@ -20,9 +20,9 @@ The public key infrastructure (PKI) certificates that you might require for Conf For more about Active Directory Certificate Services, see the following documentation: -- For Windows Server 2012: [Active Directory Certificate Services Overview](http://go.microsoft.com/fwlink/p/?LinkId=286744) +- For Windows Server 2012: [Active Directory Certificate Services Overview](https://go.microsoft.com/fwlink/p/?LinkId=286744) -- For Windows Server 2008: [Active Directory Certificate Services in Windows Server 2008](http://go.microsoft.com/fwlink/p/?LinkId=115018) +- For Windows Server 2008: [Active Directory Certificate Services in Windows Server 2008](https://go.microsoft.com/fwlink/p/?LinkId=115018) For information about using Cryptography API: Next Generation (CNG) certificates with Configuration Manager, see [CNG certificates overview](cng-certificates-overview.md). @@ -34,7 +34,7 @@ For information about using Cryptography API: Next Generation (CNG) certificates > >Effective February 14, 2017, Windows no longer trusts certain certificates signed with SHA-1. In general, we recommend that you issue new server and client authentication certificates signed with SHA-2 (which includes SHA-256 and SHA-512, among others). Additionally, we recommend that any internet-facing services use a SHA-2 certificate. For example, if you purchase a public certificate for use with a cloud management gateway, make sure that you purchase a SHA-2 certificate." > -> In most cases, the change to SHA-2 certificates has no impact on operations. For more information, see [Windows Enforcement of SHA1 certificates](http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-sha1-certificates.aspx). +> In most cases, the change to SHA-2 certificates has no impact on operations. For more information, see [Windows Enforcement of SHA1 certificates](https://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-sha1-certificates.aspx). You can use any PKI to create, deploy, and manage these certificates, with the following exceptions: diff --git a/sccm/core/plan-design/network/websites-for-site-system-servers.md b/sccm/core/plan-design/network/websites-for-site-system-servers.md index 464cf387522..456217b76aa 100644 --- a/sccm/core/plan-design/network/websites-for-site-system-servers.md +++ b/sccm/core/plan-design/network/websites-for-site-system-servers.md @@ -42,7 +42,7 @@ Several Configuration Manager site system roles require the use of Microsoft Int - Set up the custom website to respond to the same port that you set up for Configuration Manager client communication (client request port). -- For each custom or default website that uses a custom folder, place a copy of the default document type that you use in the root folder that hosts the website. For example, on a Windows Server 2008 R2 computer that has default configurations, **iisstart.htm** is one of several default document types that are available. You can find this file in the root of the default website and then place a copy of this file (or a copy of the default document type that you use) in the root folder that hosts the SMSWEB custom website. For more about default document types, see [Default Document <defaultDocument\> for IIS](http://www.iis.net/configreference/system.webserver/defaultdocument). +- For each custom or default website that uses a custom folder, place a copy of the default document type that you use in the root folder that hosts the website. For example, on a Windows Server 2008 R2 computer that has default configurations, **iisstart.htm** is one of several default document types that are available. You can find this file in the root of the default website and then place a copy of this file (or a copy of the default document type that you use) in the root folder that hosts the SMSWEB custom website. For more about default document types, see [Default Document <defaultDocument\> for IIS](https://www.iis.net/configreference/system.webserver/defaultdocument). **About IIS requirements:** **The following site system roles require IIS and a website to host the site system services:** diff --git a/sccm/core/servers/deploy/configure/database-replicas-for-management-points.md b/sccm/core/servers/deploy/configure/database-replicas-for-management-points.md index d3be652081b..b02cb0391da 100644 --- a/sccm/core/servers/deploy/configure/database-replicas-for-management-points.md +++ b/sccm/core/servers/deploy/configure/database-replicas-for-management-points.md @@ -52,7 +52,7 @@ System Center Configuration Manager primary sites can use a database replica to - The site database must **publish** the database replica, and each remote database replica server must **subscribe** to the published data. - - Both the SQL Server that hosts the site database and that hosts a database replica must be configured to support a **Max Text Repl Size** of 2 GB. For an example of how to configure this for SQL Server 2012, see [Configure the max text repl size Server Configuration Option](http://go.microsoft.com/fwlink/p/?LinkId=273960). + - Both the SQL Server that hosts the site database and that hosts a database replica must be configured to support a **Max Text Repl Size** of 2 GB. For an example of how to configure this for SQL Server 2012, see [Configure the max text repl size Server Configuration Option](https://go.microsoft.com/fwlink/p/?LinkId=273960). - **Self-signed certificate:** To configure a database replica, you must create a self-signed certificate on the database replica server and make this certificate available to each management point that will use that database replica server. @@ -167,7 +167,7 @@ Use the following procedure as an example of how to configure a database replica - If the SQL Server Agent runs by using a different account, select **Run under the following Windows account**, and then configure that account. You can specify a Windows account or a SQL Server account. > [!IMPORTANT] - > You must grant the account that runs the Distribution Agent permissions to the publisher as a pull subscription. For information about configuring these permissions, see [Distribution Agent Security](http://go.microsoft.com/fwlink/p/?LinkId=238463) in the SQL Server TechNet Library. + > You must grant the account that runs the Distribution Agent permissions to the publisher as a pull subscription. For information about configuring these permissions, see [Distribution Agent Security](https://go.microsoft.com/fwlink/p/?LinkId=238463) in the SQL Server TechNet Library. - For **Connect to the Distributor**, select **By impersonating the process account**. @@ -452,7 +452,7 @@ To support client notification with a database replica for a management point, y - For each subsequent database replica you use this script to configure, update the Friendly name for the certificate. To do so, edit the line **$enrollment.CertificateFriendlyName = "ConfigMgr SQL Server Identification Certificate"** and replace **ConfigMgr SQL Server Identification Certificate** with a new name, like **ConfigMgr SQL Server Identification Certificate1**. ## Manage database replica configurations - When you use a database replica at a site, use the information in the following sections to supplement the process of uninstalling a database replica, uninstalling a site that uses a database replica, or moving the site database to a new installation of SQL Server. When you use information in the following sections to delete publications, use the guidance for deleting transactional replication for the version of SQL Server that you use for the database replica. For example, if you use SQL Server 2008 R2, see [How to: Delete a Publication (Replication Transact-SQL Programming)](http://go.microsoft.com/fwlink/p/?LinkId=273934). + When you use a database replica at a site, use the information in the following sections to supplement the process of uninstalling a database replica, uninstalling a site that uses a database replica, or moving the site database to a new installation of SQL Server. When you use information in the following sections to delete publications, use the guidance for deleting transactional replication for the version of SQL Server that you use for the database replica. For example, if you use SQL Server 2008 R2, see [How to: Delete a Publication (Replication Transact-SQL Programming)](https://go.microsoft.com/fwlink/p/?LinkId=273934). > [!NOTE] > After you restore a site database that was configured for database replicas, before you can use the database replicas you must reconfigure each database replica, recreating both the publications and subscriptions. diff --git a/sccm/core/servers/deploy/configure/install-site-system-roles.md b/sccm/core/servers/deploy/configure/install-site-system-roles.md index ef7dadeeb3e..6441a5d8504 100644 --- a/sccm/core/servers/deploy/configure/install-site-system-roles.md +++ b/sccm/core/servers/deploy/configure/install-site-system-roles.md @@ -50,7 +50,7 @@ Just prior to installing the site system role, Configuration Manager checks the 7. Complete the wizard. > [!TIP] -> The Windows PowerShell cmdlet, New-CMSiteSystemServer, performs the same function as this procedure. For more information, see [New-CMSiteSystemServer](http://go.microsoft.com/fwlink/p/?LinkID=271414) in the System Center 2012 Configuration Manager SP1 Cmdlet Reference documentation. +> The Windows PowerShell cmdlet, New-CMSiteSystemServer, performs the same function as this procedure. For more information, see [New-CMSiteSystemServer](https://go.microsoft.com/fwlink/p/?LinkID=271414) in the System Center 2012 Configuration Manager SP1 Cmdlet Reference documentation. ## To install site system roles on a new site system server @@ -72,4 +72,4 @@ Just prior to installing the site system role, Configuration Manager checks the 7. Complete the wizard. > [!TIP] -> The Windows PowerShell cmdlet, New-CMSiteSystemServer, performs the same function as this procedure. For more information, see [New-CMSiteSystemServer](http://go.microsoft.com/fwlink/p/?LinkID=271414) in the System Center 2012 Configuration Manager SP1 Cmdlet Reference documentation. +> The Windows PowerShell cmdlet, New-CMSiteSystemServer, performs the same function as this procedure. For more information, see [New-CMSiteSystemServer](https://go.microsoft.com/fwlink/p/?LinkID=271414) in the System Center 2012 Configuration Manager SP1 Cmdlet Reference documentation. diff --git a/sccm/core/servers/deploy/install/get-install-media.md b/sccm/core/servers/deploy/install/get-install-media.md index 984764e81bd..874937578f6 100644 --- a/sccm/core/servers/deploy/install/get-install-media.md +++ b/sccm/core/servers/deploy/install/get-install-media.md @@ -20,6 +20,6 @@ If you have System Center Configuration Manager volume licenses with Software As If you have a System Center Configuration Manager license from EMS, Microsoft 365, or a Cloud Solution Provider (CSP), please see the [Product and Licensing FAQ](/sccm/core/understand/product-and-licensing-faq#bkmk_csp). -If you would like to purchase volume licenses for System Center Configuration Manager, contact your preferred Microsoft Reseller or see [How to purchase through Volume Licensing]( https://www.microsoft.com/Licensing/how-to-buy/how-to-buy.aspx). You can also download media to install an evaluation edition of System Center Configuration Manager from the [TechNet Evaluation Center]( https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection) website. +If you would like to purchase volume licenses for System Center Configuration Manager, contact your preferred Microsoft Reseller or see [How to purchase through Volume Licensing]( https://www.microsoft.com/Licensing/how-to-buy/how-to-buy.aspx). You can also download media to install an evaluation edition of System Center Configuration Manager from the [TechNet Evaluation Center]( https://www.microsoft.com/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection) website. To learn about baseline media for Configuration Manager, see [Baseline and update versions](/sccm/core/servers/manage/updates#bkmk_Baselines). diff --git a/sccm/core/servers/deploy/install/setup-reference.md b/sccm/core/servers/deploy/install/setup-reference.md index 86bdf68d60f..0b4d519b481 100644 --- a/sccm/core/servers/deploy/install/setup-reference.md +++ b/sccm/core/servers/deploy/install/setup-reference.md @@ -41,7 +41,7 @@ You can download client software for Configuration Manager from the Microsoft Do Use the following links to download clients for the version of Configuration Manager you use: -- See [Microsoft System Center Configuration Manager - Clients for Additional Operating Systems](http://www.microsoft.com/download/details.aspx?id=47719) +- See [Microsoft System Center Configuration Manager - Clients for Additional Operating Systems](https://www.microsoft.com/download/details.aspx?id=47719) ## Usage data levels and settings When you install your first System Center Configuration Manager site, Configuration Manager automatically installs and configures a new site system role, the **service connection point**, on the site server. The service connection point has these default settings: @@ -66,4 +66,4 @@ Data collection includes these three levels: For more information, including disclosure of the details collected by each level, see [Diagnostics and usage data for System Center Configuration Manager](../../../../core/plan-design/diagnostics/diagnostics-and-usage-data.md). -To view the System Center Configuration Manager Privacy Statement on-line, go to [http://go.microsoft.com/fwlink/?LinkID=626527](http://go.microsoft.com/fwlink/?LinkID=626527). +To view the System Center Configuration Manager Privacy Statement on-line, go to [https://go.microsoft.com/fwlink/?LinkID=626527](https://go.microsoft.com/fwlink/?LinkID=626527). diff --git a/sccm/core/servers/deploy/install/use-the-setup-wizard-to-install-sites.md b/sccm/core/servers/deploy/install/use-the-setup-wizard-to-install-sites.md index 61461cc655e..86bd152b29e 100644 --- a/sccm/core/servers/deploy/install/use-the-setup-wizard-to-install-sites.md +++ b/sccm/core/servers/deploy/install/use-the-setup-wizard-to-install-sites.md @@ -34,7 +34,7 @@ Install a secondary site from within the Configuration Manager console. Secondar > - [**Read documentation**](https://docs.microsoft.com/sccm) > - **Obtain installation assistance**: [TechNet Forums: Configuration Manager (Current Branch) – Site and Client Deployment](https://social.technet.microsoft.com/Forums/en-us/home?forum=ConfigMgrDeployment) > - **Configuration Manager community**: [System Center Community: How to Participate](https://social.technet.microsoft.com/wiki/contents/articles/11504.system-center-community-how-to-participate.aspx) -> - [**Configuration Manager home**](https://www.microsoft.com/en-us/cloud-platform/system-center-configuration-manager) +> - [**Configuration Manager home**](https://www.microsoft.com/cloud-platform/system-center-configuration-manager) ## Install a central administration or primary site diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1610.md b/sccm/core/servers/manage/checklist-for-installing-update-1610.md index b7fe48de35e..fa7a6bb3cc1 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1610.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1610.md @@ -27,7 +27,7 @@ To get the update for version 1610, you must use a service connection point site - Usually, you can also restart the **SMS_Executive** service on the site server to restart the download of the update's redistribution files. - - Another common download issue occurs when proxy server settings prevent downloads from and . + - Another common download issue occurs when proxy server settings prevent downloads from and . For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1702.md b/sccm/core/servers/manage/checklist-for-installing-update-1702.md index e2fc87e708f..d0d219204da 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1702.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1702.md @@ -30,7 +30,7 @@ To get the update for version 1702, you must use a service connection point site - If the dmpdownloader.log indicates the dmpdownloader process is asleep and waiting for an interval before checking for updates, you can restart the **SMS_Executive** service on the site server to restart the download of the update's redistribution files. - - Another common download issue occurs when proxy server settings prevent downloads from and . + - Another common download issue occurs when proxy server settings prevent downloads from and . For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1706.md b/sccm/core/servers/manage/checklist-for-installing-update-1706.md index 48432a1632c..580eaf69135 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1706.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1706.md @@ -27,7 +27,7 @@ To get the update for version 1706, you must use a service connection point site - If the dmpdownloader.log indicates the dmpdownloader process is asleep and waiting for an interval before checking for updates, you can restart the **SMS_Executive** service on the site server to restart the download of the update's redistribution files. - - Another common download issue occurs when proxy server settings prevent downloads from and . + - Another common download issue occurs when proxy server settings prevent downloads from and . For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1710.md b/sccm/core/servers/manage/checklist-for-installing-update-1710.md index 4b590522471..e00977f6abe 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1710.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1710.md @@ -27,7 +27,7 @@ To get the update for version 1710, you must use a service connection point site - If the dmpdownloader.log indicates the dmpdownloader process is asleep and waiting for an interval before checking for updates, you can restart the **SMS_Executive** service on the site server to restart the download of the update's redistribution files. - - Another common download issue occurs when proxy server settings prevent downloads from and . + - Another common download issue occurs when proxy server settings prevent downloads from and . For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1802.md b/sccm/core/servers/manage/checklist-for-installing-update-1802.md index 0dcc26c111c..90153161d71 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1802.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1802.md @@ -26,7 +26,7 @@ To get the update for version 1802, you must use a service connection point at t - If the dmpdownloader.log indicates the dmpdownloader process is asleep and waiting for an interval before checking for updates, you can restart the **SMS_Executive** service on the site server to restart the download of the update's redistribution files. - - Another common download issue occurs when proxy server settings prevent downloads from and . + - Another common download issue occurs when proxy server settings prevent downloads from and . For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1806.md b/sccm/core/servers/manage/checklist-for-installing-update-1806.md index a2a9842d1f5..8102a919233 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1806.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1806.md @@ -27,7 +27,7 @@ To get the update for version 1806, you must use a service connection point at t - The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update's redistribution files, restart the **SMS_Executive** service on the site server. - - Another common download issue occurs when proxy server settings prevent downloads from http://silverlight.dlservice.microsoft.com and http://download.microsoft.com. + - Another common download issue occurs when proxy server settings prevent downloads from http://silverlight.dlservice.microsoft.com and https://download.microsoft.com/. For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1810.md b/sccm/core/servers/manage/checklist-for-installing-update-1810.md index 6c7af977f93..3082a9c7840 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1810.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1810.md @@ -27,7 +27,7 @@ To get the update for version 1810, you must use a service connection point at t - The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update's redistribution files, restart the **SMS_Executive** service on the site server. - - Another common download issue occurs when proxy server settings prevent downloads from http://silverlight.dlservice.microsoft.com, http://download.microsoft.com, and/or http://go.microsoft.com. + - Another common download issue occurs when proxy server settings prevent downloads from http://silverlight.dlservice.microsoft.com, https://download.microsoft.com/, and/or https://go.microsoft.com. For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/checklist-for-installing-update-1902.md b/sccm/core/servers/manage/checklist-for-installing-update-1902.md index f68f7aa0902..f31b8d8ffd0 100644 --- a/sccm/core/servers/manage/checklist-for-installing-update-1902.md +++ b/sccm/core/servers/manage/checklist-for-installing-update-1902.md @@ -27,7 +27,7 @@ To get the update for version 1902, you must use a service connection point at t - The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update's redistribution files, restart the **SMS_Executive** service on the site server. - - Another common download issue occurs when proxy server settings prevent downloads from http://silverlight.dlservice.microsoft.com, http://download.microsoft.com, and/or http://go.microsoft.com. + - Another common download issue occurs when proxy server settings prevent downloads from http://silverlight.dlservice.microsoft.com, https://download.microsoft.com/, and/or https://go.microsoft.com. For more information about installing updates, see [In-console updates and servicing](/sccm/core/servers/manage/updates#bkmk_inconsole). diff --git a/sccm/core/servers/manage/cmpivot.md b/sccm/core/servers/manage/cmpivot.md index 5b666e0051b..cf348aa7a5b 100644 --- a/sccm/core/servers/manage/cmpivot.md +++ b/sccm/core/servers/manage/cmpivot.md @@ -162,7 +162,7 @@ The CMPivot window contains the following elements: - **Show devices without**: Query for devices without this value for this property. For example, from the results of the `OS` query, select this option on a cell in the Version row: `OS | summarize countif( (Version == '10.0.17134') ) by Device | where (countif_ == 0) | project Device` - - **Bing it**: Launch the default web browser to www.bing.com with this value as the query string. + - **Bing it**: Launch the default web browser to https://www.bing.com with this value as the query string. - Click any hyperlinked text to pivot the view on that specific information. diff --git a/sccm/core/servers/manage/create-queries.md b/sccm/core/servers/manage/create-queries.md index 17c0088bd9f..cf519e1d1c8 100644 --- a/sccm/core/servers/manage/create-queries.md +++ b/sccm/core/servers/manage/create-queries.md @@ -44,9 +44,9 @@ This article describes how to create and import queries in System Center Configu > [!TIP] > You can use the following reference documentation to help you construct your own WQL queries: > - > - [WQL (SQL for WMI)](http://go.microsoft.com/fwlink/p/?LinkId=256653) - > - [WHERE Clause](http://go.microsoft.com/fwlink/p/?LinkId=256654) - > - [WQL Operators](http://go.microsoft.com/fwlink/p/?LinkId=256655) + > - [WQL (SQL for WMI)](https://go.microsoft.com/fwlink/p/?LinkId=256653) + > - [WHERE Clause](https://go.microsoft.com/fwlink/p/?LinkId=256654) + > - [WQL Operators](https://go.microsoft.com/fwlink/p/?LinkId=256655) 8. On the **Criteria** tab of the <Query Name\> **Statement Properties** dialog box, specify criteria that are used to refine the results of the query. For example, you could return only resources that have a site code of **XYZ**. You can configure multiple criteria for a query. diff --git a/sccm/core/servers/manage/introduction-to-reporting.md b/sccm/core/servers/manage/introduction-to-reporting.md index 347b02f3387..62ee4e6c994 100644 --- a/sccm/core/servers/manage/introduction-to-reporting.md +++ b/sccm/core/servers/manage/introduction-to-reporting.md @@ -33,7 +33,7 @@ Reporting in System Center Configuration Manager provides a set of tools and res - Exports reports that users can select in a variety of popular formats. - For more information about Reporting Services, see [SQL Server Reporting Services](http://go.microsoft.com/fwlink/p/?LinkID=212032) in the SQL Server 2008 Books Online. + For more information about Reporting Services, see [SQL Server Reporting Services](https://go.microsoft.com/fwlink/p/?LinkID=212032) in the SQL Server 2008 Books Online. ## Reporting Services Point The reporting services point is a site system role that is installed on a server that is running Microsoft SQL Server Reporting Services. The reporting services point copies the Configuration Manager report definitions to Reporting Services, creates report folders based on report categories, and sets security policy on the report folders and reports based on the role-based permissions for Configuration Manager administrative users. In a 10-minute interval, the reporting services point connects to Reporting Services to reapply the security policy if it has been changed, for example, by using Report Manager. For more information about how to plan for and install a reporting services point, see the following documentation: diff --git a/sccm/core/servers/manage/modify-your-infrastructure.md b/sccm/core/servers/manage/modify-your-infrastructure.md index e5c5cd602a2..040e22f8230 100644 --- a/sccm/core/servers/manage/modify-your-infrastructure.md +++ b/sccm/core/servers/manage/modify-your-infrastructure.md @@ -183,10 +183,10 @@ SQL Server documentation can help you [manually register the SPN](https://techne You can register an SPN for the SQL Server service account of the site database server by using the **Setspn** tool. You must run the Setspn tool on a computer that resides in the domain of SQL Server, and it must use Domain Administrator credentials to run. -Use the following procedures as examples of how to manage the SPN for the SQL Server service account that uses the Setspn tool on Windows Server 2008 R2. For specific guidance about Setspn, see [Setspn Overview](http://go.microsoft.com/fwlink/p/?LinkId=226343), or similar documentation specific to your operating system. +Use the following procedures as examples of how to manage the SPN for the SQL Server service account that uses the Setspn tool on Windows Server 2008 R2. For specific guidance about Setspn, see [Setspn Overview](https://go.microsoft.com/fwlink/p/?LinkId=226343), or similar documentation specific to your operating system. > [!NOTE] -> The following procedures reference the Setspn command-line tool. The Setspn command-line tool is included when you install Windows Server 2003 Support Tools from the product CD or from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=100114). For more information about how to install Windows Support Tools from the product CD, see [Install Windows Support Tools](http://go.microsoft.com/fwlink/p/?LinkId=62270). +> The following procedures reference the Setspn command-line tool. The Setspn command-line tool is included when you install Windows Server 2003 Support Tools from the product CD or from the [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=100114). For more information about how to install Windows Support Tools from the product CD, see [Install Windows Support Tools](https://go.microsoft.com/fwlink/p/?LinkId=62270). #### To manually create a domain user Service Principal Name (SPN) for the SQL Server service account diff --git a/sccm/core/servers/manage/operations-and-maintenance-for-reporting.md b/sccm/core/servers/manage/operations-and-maintenance-for-reporting.md index 6428a2042e2..ed23afbd192 100644 --- a/sccm/core/servers/manage/operations-and-maintenance-for-reporting.md +++ b/sccm/core/servers/manage/operations-and-maintenance-for-reporting.md @@ -34,7 +34,7 @@ After the infrastructure is in place for reporting in System Center Configuratio > There must be a two-way trust established for users from a different domain than that of the Reporting Servicies Point Account to successfully run reports. > [!NOTE] -> Report Manager is a web\-based report access and management tool that you use to administer a single report server instance on a remote location over an HTTP connection. You can use Report Manager for operational tasks, for example, to view reports, modify report properties, and manage associated report subscriptions. This topic provides the steps to view a report and modify report properties in Report Manager, but for more information about the other options that Report Manager provides, see [Report Manager](http://go.microsoft.com/fwlink/p/?LinkId=224916) in SQL Server 2008 Books Online. +> Report Manager is a web\-based report access and management tool that you use to administer a single report server instance on a remote location over an HTTP connection. You can use Report Manager for operational tasks, for example, to view reports, modify report properties, and manage associated report subscriptions. This topic provides the steps to view a report and modify report properties in Report Manager, but for more information about the other options that Report Manager provides, see [Report Manager](https://go.microsoft.com/fwlink/p/?LinkId=224916) in SQL Server 2008 Books Online. Use the following procedures to run a Configuration Manager report. @@ -286,7 +286,7 @@ After the infrastructure is in place for reporting in System Center Configuratio - Send an embedded or attached report. The rendering format and browser determine whether the report is embedded or attached. If your browser supports HTML 4.0 and MHTML, and you select the MHTML \(web archive\) rendering format, the report is embedded as part of the message. All other rendering formats \(CSV, PDF, Word, and so on\) deliver reports as attachments. Reporting Services does not check the size of the attachment or message before sending the report. If the attachment or message exceeds the maximum limit allowed by your mail server, the report is not delivered. > [!IMPORTANT] -> You must configure the email settings in Reporting Services for the **Email** delivery option to be available. For more information about configuring the email settings in Reporting Services, see [Configuring a Report Server for Email Delivery](http://go.microsoft.com/fwlink/p/?LinkId=226668) in the SQL Server Books Online. +> You must configure the email settings in Reporting Services for the **Email** delivery option to be available. For more information about configuring the email settings in Reporting Services, see [Configuring a Report Server for Email Delivery](https://go.microsoft.com/fwlink/p/?LinkId=226668) in the SQL Server Books Online. Use the following procedure to create a report subscription to deliver a report by using email. diff --git a/sccm/core/servers/manage/prerequisites-for-reporting.md b/sccm/core/servers/manage/prerequisites-for-reporting.md index c88e632465f..9371437f7c9 100644 --- a/sccm/core/servers/manage/prerequisites-for-reporting.md +++ b/sccm/core/servers/manage/prerequisites-for-reporting.md @@ -23,7 +23,7 @@ Reporting in System Center Configuration Manager has external dependencies and d |Prerequisite|More information| |------------------|----------------------| -|SQL Server Reporting Services|Before you can use reporting in Configuration Manager, you must install and configure SQL Server Reporting Services.

For information about planning and deploying Reporting Services in your environment, see the [Reporting Services](http://go.microsoft.com/fwlink/p/?LinkId=212032) section in the SQL Server 2008 Books Online.| +|SQL Server Reporting Services|Before you can use reporting in Configuration Manager, you must install and configure SQL Server Reporting Services.

For information about planning and deploying Reporting Services in your environment, see the [Reporting Services](https://go.microsoft.com/fwlink/p/?LinkId=212032) section in the SQL Server 2008 Books Online.| |Site system role dependencies for the computers that run the reporting services point.|[Supported configurations for System Center Configuration Manager](../../../core/plan-design/configs/supported-configurations.md)| ## Dependencies internal to Configuration Manager diff --git a/sccm/core/servers/manage/upgrade-on-premises-infrastructure.md b/sccm/core/servers/manage/upgrade-on-premises-infrastructure.md index 560e8b8b65c..7c2cb21bfc7 100644 --- a/sccm/core/servers/manage/upgrade-on-premises-infrastructure.md +++ b/sccm/core/servers/manage/upgrade-on-premises-infrastructure.md @@ -46,7 +46,7 @@ Configuration Manager supports the in-place upgrade of the server OS that hosts To upgrade a server, use the upgrade procedures provided by the OS you're upgrading to. See the following articles: -- [Windows Server Upgrade Center](http://aka.ms/upgradecenter) +- [Windows Server Upgrade Center](https://aka.ms/upgradecenter) - [Upgrade and conversion options for Windows Server 2016](https://docs.microsoft.com/windows-server/get-started/supported-upgrade-paths) diff --git a/sccm/core/servers/manage/use-the-hotfix-installer-to-install-updates.md b/sccm/core/servers/manage/use-the-hotfix-installer-to-install-updates.md index 1a7d0a8788e..e2a1446c1ec 100644 --- a/sccm/core/servers/manage/use-the-hotfix-installer-to-install-updates.md +++ b/sccm/core/servers/manage/use-the-hotfix-installer-to-install-updates.md @@ -202,7 +202,7 @@ The catalog for Updates Publisher is named **SCUPCatalog.cab** and can be found > [!IMPORTANT] > Because the SCUPCatalog.cab file is created by using paths that are specific to the site server where the update bundle is installed, it cannot be used on other site servers. -After the wizard is finished, you can import the catalog to Updates Publisher, and then use Configuration Manager software updates to deploy the updates. For information about Updates Publisher, see [Updates Publisher 2011](http://go.microsoft.com/fwlink/p/?LinkID=83449) in the TechNet library for System Center 2012. +After the wizard is finished, you can import the catalog to Updates Publisher, and then use Configuration Manager software updates to deploy the updates. For information about Updates Publisher, see [Updates Publisher 2011](https://go.microsoft.com/fwlink/p/?LinkID=83449) in the TechNet library for System Center 2012. Use the following procedure to import the SCUPCatalog.cab file to Updates Publisher and publish the updates. diff --git a/sccm/core/servers/manage/use-the-service-connection-tool.md b/sccm/core/servers/manage/use-the-service-connection-tool.md index 1d523317a48..6c3512f1bbe 100644 --- a/sccm/core/servers/manage/use-the-service-connection-tool.md +++ b/sccm/core/servers/manage/use-the-service-connection-tool.md @@ -33,7 +33,7 @@ The following are prerequisites, and known issues. - Both the **Visual C++ Redistributable** x86 and x64 files. By default, Configuration Manager installs the x64 version on the computer that hosts the service connection point. - To download a copy of the Visual C++ files, visit [Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) at the Microsoft Download Center. + To download a copy of the Visual C++ files, visit [Visual C++ Redistributable Packages for Visual Studio 2013](https://www.microsoft.com/download/details.aspx?id=40784) at the Microsoft Download Center. - .NET Framework 4.5.2 or later. diff --git a/sccm/core/support/tools.md b/sccm/core/support/tools.md index 13c1fa5023d..e0e30aca40b 100644 --- a/sccm/core/support/tools.md +++ b/sccm/core/support/tools.md @@ -24,7 +24,7 @@ Starting in Configuration Manager version 1806, these tools are included in the All Windows operating systems listed as supported clients in [Supported operating systems for clients and devices](https://docs.microsoft.com/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices) are supported for use with these tools. > [!Note] -> The [System Center 2012 R2 Configuration Manager Toolkit](https://www.microsoft.com/en-us/download/details.aspx?id=50012) is still available from the Microsoft Download Center. For Configuration Manager version 1806 and later, use the versions of the tools in the CD.Latest folder on the site server. Some tools were formerly in the toolkit but not included in version 1806. These legacy tools are no longer supported. +> The [System Center 2012 R2 Configuration Manager Toolkit](https://www.microsoft.com/download/details.aspx?id=50012) is still available from the Microsoft Download Center. For Configuration Manager version 1806 and later, use the versions of the tools in the CD.Latest folder on the site server. Some tools were formerly in the toolkit but not included in version 1806. These legacy tools are no longer supported. ## Client tools diff --git a/sccm/core/understand/product-and-licensing-faq.md b/sccm/core/understand/product-and-licensing-faq.md index 44179af940d..5cdcf05eccd 100644 --- a/sccm/core/understand/product-and-licensing-faq.md +++ b/sccm/core/understand/product-and-licensing-faq.md @@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management *Applies to: System Center Configuration Manager (Current Branch), System Center Configuration Manager (Long-Term Servicing Branch)* -This FAQ addresses common licensing questions about Configuration Manager current branch and the long-term servicing branch (LTSB) versions, available through Microsoft Volume Licensing programs. This article is for informational purposes. It doesn't supersede or replace any documentation covering System Center Configuration Manager licensing. For more information, see the product licensing for [System Center 2016](https://www.microsoft.com/en-us/licensing/product-licensing/system-center-2016.aspx) and the [Product Terms](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=53). The Product Terms describe the use terms for all Microsoft products in Volume Licensing. +This FAQ addresses common licensing questions about Configuration Manager current branch and the long-term servicing branch (LTSB) versions, available through Microsoft Volume Licensing programs. This article is for informational purposes. It doesn't supersede or replace any documentation covering System Center Configuration Manager licensing. For more information, see the product licensing for [System Center 2016](https://www.microsoft.com/licensing/product-licensing/system-center-2016.aspx) and the [Product Terms](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=53). The Product Terms describe the use terms for all Microsoft products in Volume Licensing. For more information about Configuration Manager features, see the [product page](https://www.microsoft.com/cloud-platform/system-center-configuration-manager). @@ -39,7 +39,7 @@ Both **Software Assurance** (SA) and **License and Software Assurance** (L&SA) a - **Software Assurance (SA)**: Customers must have active SA on Configuration Manager licenses, or equivalent subscription rights, in order to install and use the current branch option of Configuration Manager. - - While SA is optional for some Microsoft products, the only way to get rights to use Configuration Manager current branch is with SA *or equivalent subscription rights*. For more information, see the [Software Assurance FAQ](https://www.microsoft.com/en-us/licensing/licensing-programs/FAQ-Software-Assurance.aspx). + - While SA is optional for some Microsoft products, the only way to get rights to use Configuration Manager current branch is with SA *or equivalent subscription rights*. For more information, see the [Software Assurance FAQ](https://www.microsoft.com/licensing/licensing-programs/FAQ-Software-Assurance.aspx). - **Microsoft License and Software Assurance (L&SA)**: Customers buying new licenses for Configuration Manager must acquire L&SA (the license and SA coverage). @@ -47,12 +47,12 @@ Both **Software Assurance** (SA) and **License and Software Assurance** (L&SA) a - If your SA expires, and you still have a license for Configuration Manager, you can no longer use the current branch. For more information, see the FAQ [If my SA expires and I had L&SA, what do I get?](#bkmk_sa-expires) -For more information about license offerings, see [Ways to buy](https://www.microsoft.com/Licensing/licensing-programs/licensing-programs) and [Licensing Product Terms](http://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=64). +For more information about license offerings, see [Ways to buy](https://www.microsoft.com/Licensing/licensing-programs/licensing-programs) and [Licensing Product Terms](https://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=64). ### I read the term "equivalent subscription", what programs does that refer to? -Equivalent subscriptions refer to programs like [Enterprise Mobility + Security](http://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=51) (EMS) or [Microsoft 365 Enterprise](https://www.microsoft.com/microsoft-365/enterprise). There can be others, but these programs are the most common. The Microsoft Volume Licensing Product Terms refers to these programs as Management License Equivalent Licenses. +Equivalent subscriptions refer to programs like [Enterprise Mobility + Security](https://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=51) (EMS) or [Microsoft 365 Enterprise](https://www.microsoft.com/microsoft-365/enterprise). There can be others, but these programs are the most common. The Microsoft Volume Licensing Product Terms refers to these programs as Management License Equivalent Licenses. ### I have Enterprise Mobility + Security and it expired, what must I do now? diff --git a/sccm/core/understand/supported-configurations-for-ltsb.md b/sccm/core/understand/supported-configurations-for-ltsb.md index 93ff9896728..53175fd7516 100644 --- a/sccm/core/understand/supported-configurations-for-ltsb.md +++ b/sccm/core/understand/supported-configurations-for-ltsb.md @@ -20,7 +20,7 @@ Use the information in this topic to understand what operating systems and produ If not stated otherwise in this or the LTSB specific topics, the same configurations and limitations that apply to the Current Branch version 1606 apply to the LTSB. When conflicts occur, use the information that applies to the edition you are using. Typically, the LTSB is more limited than the Current Branch. ## General statement of support -The following products and technologies are supported by this branch of Configuration Manager. However, their inclusion in this content does not express an extension of support for any product or version beyond that product's individual support lifecycle. Products that are beyond their support lifecycle are not supported for use with Configuration Manager. For more information, visit the [Microsoft Support Lifecycle](http://go.microsoft.com/fwlink/p/?LinkId=208270) website and read the [Microsoft Support Lifecycle Policy FAQ](http://go.microsoft.com/fwlink/p/?LinkId=31976). +The following products and technologies are supported by this branch of Configuration Manager. However, their inclusion in this content does not express an extension of support for any product or version beyond that product's individual support lifecycle. Products that are beyond their support lifecycle are not supported for use with Configuration Manager. For more information, visit the [Microsoft Support Lifecycle](https://go.microsoft.com/fwlink/p/?LinkId=208270) website and read the [Microsoft Support Lifecycle Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976). Additionally, products and product versions that are not listed in the following topics are not supported unless they have been announced on the [Enterprise Mobility + Security Blog](https://blogs.technet.microsoft.com/enterprisemobility/). @@ -138,7 +138,7 @@ You can use the LTSB to manage the following Windows Embedded devices by install ### Mac computers You can use the LTSB to manage Mac OS X computers with the Configuration Manager client for Mac. -The Mac client installation package is not supplied with the Configuration Manager media. You can download it as part of the "Clients for Additional Operating Systems" download from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184). +The Mac client installation package is not supplied with the Configuration Manager media. You can download it as part of the "Clients for Additional Operating Systems" download from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184). Support for Mac operating systems is limited to those listed in this section. Support does not include additional operating systems that might be supported by a future update to Mac client installation packages for Current Branch. @@ -152,7 +152,7 @@ For more information, see [How to deploy clients to Macs in System Center Config ## Linux and UNIX servers You can use the LTSB to manage Linux and UNIX servers with the Configuration Manager client for Linux and UNIX. -The Linux and UNIX client installation packages are not supplied with the Configuration Manager media. You can download them as part of the "Clients for Additional Operating Systems" download from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the install script that manages the installation of the client on each computer. +The Linux and UNIX client installation packages are not supplied with the Configuration Manager media. You can download them as part of the "Clients for Additional Operating Systems" download from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the install script that manages the installation of the client on each computer. Support for Linux and UNIX operating systems is limited to those listed in this section. Support does not include additional operating systems that might be supported by a future update to Linux and UNIX client packages for Current Branch. diff --git a/sccm/core/understand/use-cloud-services.md b/sccm/core/understand/use-cloud-services.md index 667dfe26cae..ea7161770b4 100644 --- a/sccm/core/understand/use-cloud-services.md +++ b/sccm/core/understand/use-cloud-services.md @@ -31,7 +31,7 @@ Although provisioning cloud resources is not something you must do before you de - For information about cloud-based distribution points, see [Install cloud-based distribution points](/sccm/core/servers/deploy/configure/install-cloud-based-distribution-points-in-microsoft-azure). -- For more information about Azure, see [Azure](http://go.microsoft.com/fwlink/p/?LinkId=262965) in the MSDN Library. +- For more information about Azure, see [Azure](https://go.microsoft.com/fwlink/p/?LinkId=262965) in the MSDN Library. ### Azure virtual machines (for cloud-based infrastructure) Configuration Manager supports using computers that run in virtual machines in Azure, just as it does when run on-premises within your physical corporate network. You can use Azure virtual machines in the following scenarios: @@ -75,10 +75,10 @@ These additional capabilities do not require you to have an Azure subscription. For more information, see the details for the different cloud-based resource scenarios. You can also view the following topics for Azure security: -- [Azure: Understanding Security Account Management in Azure](http://go.microsoft.com/fwlink/p/?LinkId=262968) +- [Azure: Understanding Security Account Management in Azure](https://go.microsoft.com/fwlink/p/?LinkId=262968) -- [Azure Security Overview](http://go.microsoft.com/fwlink/p/?LinkId=262970) +- [Azure Security Overview](https://go.microsoft.com/fwlink/p/?LinkId=262970) -- [Get Past the Security Crossroads in Your Cloud Migration](http://go.microsoft.com/fwlink/p/?LinkId=262971) +- [Get Past the Security Crossroads in Your Cloud Migration](https://go.microsoft.com/fwlink/p/?LinkId=262971) -- [Data Security in Azure Part 1 of 2](http://go.microsoft.com/fwlink/p/?LinkId=262974) +- [Data Security in Azure Part 1 of 2](https://go.microsoft.com/fwlink/p/?LinkId=262974) diff --git a/sccm/desktop-analytics/enroll-devices.md b/sccm/desktop-analytics/enroll-devices.md index 7772c7c783c..c914210ace8 100644 --- a/sccm/desktop-analytics/enroll-devices.md +++ b/sccm/desktop-analytics/enroll-devices.md @@ -50,7 +50,7 @@ Windows 10 includes the compatibility component. To get the latest compatibility #### Windows 8.1 -Download the update: [KB 2976978](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2976978) +Download the update: [KB 2976978](https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2976978) Runs diagnostics on the Windows 8.1 systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether you might have compatibility issues when upgrading to Windows 10. @@ -58,7 +58,7 @@ For more information, see [Compatibility update for keeping Windows up-to-date i #### Windows 7 with Service Pack 1 -Download the update: [KB 2952664](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2952664) +Download the update: [KB 2952664](https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2952664) Runs diagnostics on the Windows 7 with Service Pack 1 (SP1) systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether you might have compatibility issues when upgrading to Windows 10. diff --git a/sccm/desktop-analytics/privacy.md b/sccm/desktop-analytics/privacy.md index 40a9e9726a6..27d96943cec 100644 --- a/sccm/desktop-analytics/privacy.md +++ b/sccm/desktop-analytics/privacy.md @@ -23,7 +23,7 @@ Desktop Analytics is fully committed to customer data privacy, centering on thes - **Security:** Microsoft protects your data with strong security and encryption. -- **Trust:** Desktop Analytics supports the Microsoft [Privacy Statement](https://privacy.microsoft.com/privacystatement) and [Online Service Terms](http://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=46). +- **Trust:** Desktop Analytics supports the Microsoft [Privacy Statement](https://privacy.microsoft.com/privacystatement) and [Online Service Terms](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=46). diff --git a/sccm/develop/apps/how-to-create-an-application-with-the-script-deployment-type.md b/sccm/develop/apps/how-to-create-an-application-with-the-script-deployment-type.md index 4152b481bb6..efdc6c51280 100644 --- a/sccm/develop/apps/how-to-create-an-application-with-the-script-deployment-type.md +++ b/sccm/develop/apps/how-to-create-an-application-with-the-script-deployment-type.md @@ -26,11 +26,11 @@ Applications are new to System Center Configuration Manager. Prior to System Ce - **Saving the World One Line of Code at a Time** - [How to Create a Basic App using the Configuration Manager 2012 Beta 2 SDK](http://blogs.msdn.com/b/one_line_of_code_at_a_time/archive/2011/06/14/how-to-create-a-basic-app-using-the-configuration-manager-2012-beta-2-sdk.aspx) + [How to Create a Basic App using the Configuration Manager 2012 Beta 2 SDK](https://blogs.msdn.com/b/one_line_of_code_at_a_time/archive/2011/06/14/how-to-create-a-basic-app-using-the-configuration-manager-2012-beta-2-sdk.aspx) - **Adam Meltzer's Configuration Manager Blog** - [SDK: How to create a basic application and add a deployment type](http://blogs.msdn.com/b/ameltzer/archive/2012/04/25/sdk-how-to-create-a-basic-application-and-add-a-deployment-type.aspx) + [SDK: How to create a basic application and add a deployment type](https://blogs.msdn.com/b/ameltzer/archive/2012/04/25/sdk-how-to-create-a-basic-application-and-add-a-deployment-type.aspx) - **SDK Sample: AppSupersedence** diff --git a/sccm/develop/apps/verifying-the-application-management-extension.md b/sccm/develop/apps/verifying-the-application-management-extension.md index 33939243fcb..1ced7aa15be 100644 --- a/sccm/develop/apps/verifying-the-application-management-extension.md +++ b/sccm/develop/apps/verifying-the-application-management-extension.md @@ -29,7 +29,7 @@ ms.collection: M365-identity-device-management ![Screenshot showing successful registration](../../develop/apps/media/appmanregistrationscreenshot.gif "AppManRegistrationScreenshot") > [!TIP] -> For additional information on using the Create Application Wizard, see [How to Create Applications in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=215691). +> For additional information on using the Create Application Wizard, see [How to Create Applications in Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=215691). #### Create an application using the Create Application Wizard @@ -44,7 +44,7 @@ ms.collection: M365-identity-device-management 5. Continue through the wizard until successful completion. > [!TIP] -> For additional information on using the Create Application Wizard, see [How to Create Applications in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=215691). +> For additional information on using the Create Application Wizard, see [How to Create Applications in Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=215691). #### Create a deployment type using the Create Deployment Type Wizard @@ -59,7 +59,7 @@ ms.collection: M365-identity-device-management 5. Continue through the wizard until successful completion. > [!TIP] -> For additional information on using the Create Application Wizard, see [How to Create Deployment Types in Configuration Manager](http://go.microsoft.com/fwlink/?LinkID=215692). +> For additional information on using the Create Application Wizard, see [How to Create Deployment Types in Configuration Manager](https://go.microsoft.com/fwlink/?LinkID=215692). #### Check the Deployment Type Properties diff --git a/sccm/develop/compliance/about-compliance-settings--dcm--setup-and-configuration.md b/sccm/develop/compliance/about-compliance-settings--dcm--setup-and-configuration.md index a663614c106..1ca1fd0d5b9 100644 --- a/sccm/develop/compliance/about-compliance-settings--dcm--setup-and-configuration.md +++ b/sccm/develop/compliance/about-compliance-settings--dcm--setup-and-configuration.md @@ -23,7 +23,7 @@ To use desired configuration management on your System Center Configuration Mana - Client computers must have installed the .NET Framework 2.0 or a later version. > [!NOTE] -> The .NET Framework 2.0 is supplied with the latest operating systems, such as Windows Vista, and is also available to download through Windows Update. You can also download it from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=276779) and install it through software distribution or other deployment methods. +> The .NET Framework 2.0 is supplied with the latest operating systems, such as Windows Vista, and is also available to download through Windows Update. You can also download it from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=276779) and install it through software distribution or other deployment methods. Enabling the desired configuration management client agent makes it possible for Configuration Manager clients that are assigned to this site to evaluate compliance with assigned configuration baselines. This client agent is enabled by default, but it will not evaluate its compliance until it downloads one or more configuration baselines and evaluates them at the configured schedule. diff --git a/sccm/develop/core/clients/inventory/about-configuration-manager-inventory.md b/sccm/develop/core/clients/inventory/about-configuration-manager-inventory.md index 0dd1d08c7b8..f248342abb4 100644 --- a/sccm/develop/core/clients/inventory/about-configuration-manager-inventory.md +++ b/sccm/develop/core/clients/inventory/about-configuration-manager-inventory.md @@ -16,7 +16,7 @@ You can use System Center Configuration Manager to collect hardware and software When the hardware inventory client agent is enabled for Configuration Manager sites, hardware inventory data gives you system information (such as available disk space, processor type, and operating system) about each computer. When the software inventory client agent is enabled, you can inventory information, such as the specific file types and versions that are present on client computers. The software inventory client agent can also collect information about files that are inventoried on client systems. Configuration Manager software inventory can also collect files, not just details about the files, from client computers. With file collection, you specify a set of files to be copied from clients to the Configuration Manager site server that the clients are assigned to. > [!NOTE] -> For information about using Inventory in System Center Configuration Manager, see [Inventory in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=275839). +> For information about using Inventory in System Center Configuration Manager, see [Inventory in Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=275839). ## About Collecting Hardware Inventory When it is enabled, the System Center Configuration Manager hardware inventory client agent automatically collects detailed information about the hardware characteristics of clients in a Configuration Manager site. By using this feature, you can collect a wide variety of information about client computers, such as memory, operating system, and peripherals for client computers. diff --git a/sccm/develop/core/clients/programming/about-configuration-manager-wmi-programming.md b/sccm/develop/core/clients/programming/about-configuration-manager-wmi-programming.md index 87fbb43d686..66bd1cb9b1f 100644 --- a/sccm/develop/core/clients/programming/about-configuration-manager-wmi-programming.md +++ b/sccm/develop/core/clients/programming/about-configuration-manager-wmi-programming.md @@ -23,7 +23,7 @@ Programming the System Center Configuration Manager client Windows Management In For more information about using Configuration Manager client WMI namespace objects by using the System.Management namespace, see [How to Read a WMI Object by Using System.Management](../../../../develop/core/clients/programming/how-to-read-a-wmi-object-by-using-system.management.md). - For more information about using the System.Management namespace, see [System.Management Namespace](http://go.microsoft.com/fwlink/?LinkID=84308). + For more information about using the System.Management namespace, see [System.Management Namespace](https://go.microsoft.com/fwlink/?LinkID=84308). ## VBScript If you are using VBScript you access and use Configuration Manager client WMI objects by using the same coding techniques that are used for accessing other WMI objects, including the Configuration Manager WMI objects. For more information, see the [Windows Management Instrumentation](/windows/win32/wmisdk/wmi-start-page). diff --git a/sccm/develop/core/clients/programming/client-resource-conditions.md b/sccm/develop/core/clients/programming/client-resource-conditions.md index 8592c6e80c6..553b8d52921 100644 --- a/sccm/develop/core/clients/programming/client-resource-conditions.md +++ b/sccm/develop/core/clients/programming/client-resource-conditions.md @@ -20,9 +20,9 @@ In System Center Configuration Manager SP1, the Configuration Manager client has |Value|Meaning|Comment| |-----------|-------------|-------------| |0|No resource conditions.|This is the same behavior as versions of Configuration Manager prior to SP1.| -|1|Fire only when the battery is at low or above state.|Definition of critical/low/high battery state is defined in the [Windows SYSTEM_POWER_STATUS structure](http://go.microsoft.com/fwlink/?LinkId=275109).| -|2|Fire only when the battery is at high or changing state.|Definition of critical/low/high battery state is defined in the [Windows SYSTEM_POWER_STATUS structure](http://go.microsoft.com/fwlink/?LinkId=275109).| -|4|Fire only when the computer is charging.|Definition of critical/low/high battery state is defined in the [Windows SYSTEM_POWER_STATUS structure](http://go.microsoft.com/fwlink/?LinkId=275109).| +|1|Fire only when the battery is at low or above state.|Definition of critical/low/high battery state is defined in the [Windows SYSTEM_POWER_STATUS structure](https://go.microsoft.com/fwlink/?LinkId=275109).| +|2|Fire only when the battery is at high or changing state.|Definition of critical/low/high battery state is defined in the [Windows SYSTEM_POWER_STATUS structure](https://go.microsoft.com/fwlink/?LinkId=275109).| +|4|Fire only when the computer is charging.|Definition of critical/low/high battery state is defined in the [Windows SYSTEM_POWER_STATUS structure](https://go.microsoft.com/fwlink/?LinkId=275109).| |8|Fire only when the user is idle.|This check is only performed on desktop systems.| |16|Fire only when the network is connected.|| diff --git a/sccm/develop/core/reqs/about-configuration-manager-sdk-requirements.md b/sccm/develop/core/reqs/about-configuration-manager-sdk-requirements.md index d6026b2dde1..26642eaec0d 100644 --- a/sccm/develop/core/reqs/about-configuration-manager-sdk-requirements.md +++ b/sccm/develop/core/reqs/about-configuration-manager-sdk-requirements.md @@ -19,7 +19,7 @@ Developing applications and scripts for Microsoft System Center Configuration Ma > If you are programming with another .NET Framework language, use the C# examples for reference. ## Development Tools - Visual Studio 2010 provides a suitable environment for developing Configuration Manager applications and scripts. For more information about Visual Studio hardware requirements, see [Visual Studio 2010](http://go.microsoft.com/fwlink/?LinkId=110322). + Visual Studio 2010 provides a suitable environment for developing Configuration Manager applications and scripts. For more information about Visual Studio hardware requirements, see [Visual Studio 2010](https://go.microsoft.com/fwlink/?LinkId=110322). ## Development Requirements For information about development requirements, see [Configuration Manager Client Development Requirements](../../../develop/core/reqs/client-development-requirements.md) and [Configuration Manager Server Development Requirements](../../../develop/core/reqs/server-development-requirements.md). @@ -28,7 +28,7 @@ Developing applications and scripts for Microsoft System Center Configuration Ma For information about runtime requirements, see [Configuration Manager Client Runtime Requirements](../../../develop/core/reqs/client-runtime-requirements.md) and [Configuration Manager Server Runtime Requirements](../../../develop/core/reqs/server-runtime-requirements.md). > [!IMPORTANT] -> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=248211). +> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=248211). ## See Also diff --git a/sccm/develop/core/reqs/client-development-requirements.md b/sccm/develop/core/reqs/client-development-requirements.md index 3c04d9c03a2..e2ead101dd8 100644 --- a/sccm/develop/core/reqs/client-development-requirements.md +++ b/sccm/develop/core/reqs/client-development-requirements.md @@ -18,21 +18,21 @@ The System Center Configuration Manager client can be programmed by using the fo If you are programming the Configuration Manager client by using managed code, you use the System.Management namespace and, where applicable, you use COM Interoperability to access the Configuration Manager automation objects. ### NET Framework - You should have version 4.0 of the Microsoft .NET Framework installed on the development computer and on the computers you want to deploy your .NET Framework application to. The .NET Framework redistributable package is available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=276779). It is also installed as part of Visual Studio 2010. + You should have version 4.0 of the Microsoft .NET Framework installed on the development computer and on the computers you want to deploy your .NET Framework application to. The .NET Framework redistributable package is available from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=276779). It is also installed as part of Visual Studio 2010. ## VBScript You can use VBScript to access the System Center Configuration Manager client WMI namespaces. The client also has a number of COM automation objects that you can use. - For more information about scripting with WMI, see [Windows Management Instrumentation](http://go.microsoft.com/fwlink/?LinkID=276770). + For more information about scripting with WMI, see [Windows Management Instrumentation](https://go.microsoft.com/fwlink/?LinkID=276770). ## C++ - C++ examples are provided for some Configuration Manager technologies where C++ is the most appropriate development language. In most cases, C++ developers should use the VBScript samples as a guide. For more information about using WMI with C++, see [Creating a WMI Application Using C++](http://go.microsoft.com/fwlink/?LinkID=276780). + C++ examples are provided for some Configuration Manager technologies where C++ is the most appropriate development language. In most cases, C++ developers should use the VBScript samples as a guide. For more information about using WMI with C++, see [Creating a WMI Application Using C++](https://go.microsoft.com/fwlink/?LinkID=276780). ## Other Languages For languages that are not based on .NET Framework, use the VBScript samples as a starting point for accessing Configuration Manager through WMI. > [!IMPORTANT] -> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=248211). +> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=248211). ## See Also [Configuration Manager Server Development Requirements](../../../develop/core/reqs/server-development-requirements.md) diff --git a/sccm/develop/core/reqs/client-runtime-requirements.md b/sccm/develop/core/reqs/client-runtime-requirements.md index 769aa68fb92..c2d7458981d 100644 --- a/sccm/develop/core/reqs/client-runtime-requirements.md +++ b/sccm/develop/core/reqs/client-runtime-requirements.md @@ -32,7 +32,7 @@ Applications that run on Microsoft System Center Configuration Manager clients h The Configuration Manager client has a native 64-bit version that is installed automatically on Windows 64-bit operating systems. Applications that relied on the 32-bit interfaces to be present may need to be re-compiled in a native 64-bit environment to interact with the Configuration Manager client APIs. ## General Requirements - For more information about System Center Configuration Manager client requirements, see [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=248211). + For more information about System Center Configuration Manager client requirements, see [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=248211). ## See Also [Configuration Manager Client Development Requirements](../../../develop/core/reqs/client-development-requirements.md) diff --git a/sccm/develop/core/reqs/configuration-manager-sdk-libraries-and-header-files.md b/sccm/develop/core/reqs/configuration-manager-sdk-libraries-and-header-files.md index 0b76f443f87..18f9633170b 100644 --- a/sccm/develop/core/reqs/configuration-manager-sdk-libraries-and-header-files.md +++ b/sccm/develop/core/reqs/configuration-manager-sdk-libraries-and-header-files.md @@ -39,7 +39,7 @@ In System Center Configuration Manager, when you write unmanaged applications, y > The header files can be found in the % Program Files %\Microsoft System Center 2012 Configuration Manager SDK\Samples\Includes folder. > [!IMPORTANT] -> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=248211). +> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=248211). ## See Also [Configuration Manager Server Development Requirements](../../../develop/core/reqs/server-development-requirements.md) diff --git a/sccm/develop/core/reqs/server-development-requirements.md b/sccm/develop/core/reqs/server-development-requirements.md index 2f69087f9aa..94f8aeb3ced 100644 --- a/sccm/develop/core/reqs/server-development-requirements.md +++ b/sccm/develop/core/reqs/server-development-requirements.md @@ -31,7 +31,7 @@ In System Center Configuration Manager, the SMS Provider and associated technolo - Microsoft .NET Framework version 4 ### NET Framework - You should have version 4 of the .NET Framework installed on the development computer and on the computers you want to deploy your .NET Framework application to. The .NET Framework redistributable package is available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=276779). It is also installed as part of Visual Studio 2010. + You should have version 4 of the .NET Framework installed on the development computer and on the computers you want to deploy your .NET Framework application to. The .NET Framework redistributable package is available from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=276779). It is also installed as part of Visual Studio 2010. ## Configuration Manager Console User Interface Extension Programming Configuration Manager console extensions has the following requirements: @@ -61,16 +61,16 @@ In System Center Configuration Manager, the SMS Provider and associated technolo - Windows Script Host - For more information about scripting with WMI, see [Windows Management Instrumentation](http://go.microsoft.com/fwlink/?LinkID=276770). + For more information about scripting with WMI, see [Windows Management Instrumentation](https://go.microsoft.com/fwlink/?LinkID=276770). ## C++ - C++ examples are provided for some Configuration Manager technologies where C++ is the most appropriate development language. In most cases, C++ developers should use the VBScript samples as a guide. For more information about using WMI with C++, see [Creating a WMI Application Using C++](http://go.microsoft.com/fwlink/?LinkId=276780). + C++ examples are provided for some Configuration Manager technologies where C++ is the most appropriate development language. In most cases, C++ developers should use the VBScript samples as a guide. For more information about using WMI with C++, see [Creating a WMI Application Using C++](https://go.microsoft.com/fwlink/?LinkId=276780). ## Other Languages For languages that are not based on the .NET Framework, use the VBScript samples as a starting point for accessing Configuration Manager through WMI. > [!IMPORTANT] -> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=276781). +> For more information about general System Center Configuration Manager requirements, see [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=276781). ## See Also [Configuration Manager Client Development Requirements](../../../develop/core/reqs/client-development-requirements.md) diff --git a/sccm/develop/core/servers/configure/how-to-create-a-package.md b/sccm/develop/core/servers/configure/how-to-create-a-package.md index e2af1cd1806..49942d8d08d 100644 --- a/sccm/develop/core/servers/configure/how-to-create-a-package.md +++ b/sccm/develop/core/servers/configure/how-to-create-a-package.md @@ -125,4 +125,4 @@ public void CreatePackage(WqlConnectionManager connection, string newPackageName ## See Also [Software distribution overview](/sccm/develop/core/servers/configure/software-distribution-overview) [SMS_Package Server WMI Class](../../../../develop/reference/core/servers/configure/sms_package-server-wmi-class.md) - [PowerShell Cmdlet: New-CMPackage](http://go.microsoft.com/fwlink/?LinkId=309284) + [PowerShell Cmdlet: New-CMPackage](https://go.microsoft.com/fwlink/?LinkId=309284) diff --git a/sccm/develop/core/servers/console/about-configuration-manager-console-extension.md b/sccm/develop/core/servers/console/about-configuration-manager-console-extension.md index 269a06de139..0cdc838ae42 100644 --- a/sccm/develop/core/servers/console/about-configuration-manager-console-extension.md +++ b/sccm/develop/core/servers/console/about-configuration-manager-console-extension.md @@ -51,7 +51,7 @@ The System Center Configuration Manager console has an XML-based architecture th ## Accessibility -When developing console extensions, they should be based on designs with accessibility considerations. For example, you can make use of color, layout, intelligent default values, sound, and exposing appropriate keyboard focus. By using various accessibility techniques, you will make it easier for users with disabilities to use your software. For additional information about how you can develop applications for accessibility, see [Designing Accessible Applications](http://go.microsoft.com/fwlink/?LinkId=272471). +When developing console extensions, they should be based on designs with accessibility considerations. For example, you can make use of color, layout, intelligent default values, sound, and exposing appropriate keyboard focus. By using various accessibility techniques, you will make it easier for users with disabilities to use your software. For additional information about how you can develop applications for accessibility, see [Designing Accessible Applications](https://go.microsoft.com/fwlink/?LinkId=272471). ## See Also diff --git a/sccm/develop/core/servers/console/executable-action.md b/sccm/develop/core/servers/console/executable-action.md index 0e11d927ed3..29e36190e34 100644 --- a/sccm/develop/core/servers/console/executable-action.md +++ b/sccm/develop/core/servers/console/executable-action.md @@ -22,7 +22,7 @@ In System Center Configuration Manager, the executable action runs a program or ## Sample Executable Action XML ``` - DefaultHomeTab ContextMenu http://go.microsoft.com/fwlink/?LinkId=67307 + DefaultHomeTab ContextMenu https://go.microsoft.com/fwlink/?LinkId=67307 ``` Other elements and attributes are documented in [ActionDescription](https://msdn.microsoft.com/library/microsoft.configurationmanagement.adminconsole.schema.actiondescription.aspx). diff --git a/sccm/develop/core/servers/console/group-action.md b/sccm/develop/core/servers/console/group-action.md index eb77a6dc82f..4ec593b8697 100644 --- a/sccm/develop/core/servers/console/group-action.md +++ b/sccm/develop/core/servers/console/group-action.md @@ -29,7 +29,7 @@ In System Center Configuration Manager, the Group action creates a menu group, a ```       DefaultContextualTab     ContextMenu         DefaultContextualTab     ContextMenu   - http://go.microsoft.com/fwlink/?LinkId=67307 + https://go.microsoft.com/fwlink/?LinkId=67307 diff --git a/sccm/develop/core/understand/about-configuration-manager-queries.md b/sccm/develop/core/understand/about-configuration-manager-queries.md index 5c644dcaaff..c0ab58980d8 100644 --- a/sccm/develop/core/understand/about-configuration-manager-queries.md +++ b/sccm/develop/core/understand/about-configuration-manager-queries.md @@ -14,7 +14,7 @@ ms.collection: M365-identity-device-management You can create and run the queries that are accessible in the System Center Configuration Manager console under **Queries**. The queries can be used to locate objects in a System Center Configuration Manager site that match your query criteria. These objects include items such as specific types of computers or user groups. Queries can return most types of Configuration Manager objects, including sites, collections, packages, and saved queries themselves. However, queries are most useful for extracting information that is related to resource discovery, inventory data, and status messages. > [!NOTE] -> For information about using Queries in System Center Configuration Manager, see [http://go.microsoft.com/fwlink/?LinkId=133894](http://go.microsoft.com/fwlink/?LinkId=133894). +> For information about using Queries in System Center Configuration Manager, see [https://go.microsoft.com/fwlink/?LinkId=133894](https://go.microsoft.com/fwlink/?LinkId=133894). ## SMS_Query Configuration Manager queries are defined by `SMS_Query` object instances. The query is a WQL query and is defined in the `Expression` property. For more information about WQL, see [Configuration Manager Extended WMI Query Language](../../../develop/core/understand/extended-wmi-query-language.md). diff --git a/sccm/develop/core/understand/configuration-manager-sdk-samples.md b/sccm/develop/core/understand/configuration-manager-sdk-samples.md index 8b6237081fb..0f03be22570 100644 --- a/sccm/develop/core/understand/configuration-manager-sdk-samples.md +++ b/sccm/develop/core/understand/configuration-manager-sdk-samples.md @@ -14,7 +14,7 @@ ms.collection: M365-identity-device-management The System Center Configuration Manager Software Development Kit (SDK) ships with the following sample projects. Each sample has a readme file that explains how the sample works. > [!IMPORTANT] -> The complete System Center Configuration Manager SDK (documentation, samples, and supporting libraries) is available for download from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=248167). +> The complete System Center Configuration Manager SDK (documentation, samples, and supporting libraries) is available for download from the [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=248167). > > Always use the MSDN library for the most up-to-date documentation. @@ -98,9 +98,9 @@ The System Center Configuration Manager Software Development Kit (SDK) ships wit > [!IMPORTANT] > The Management Point Interface information for Configuration Manager can also be used for System Center Configuration Manager. However, the Configuration Manager Client Messaging SDK (included with the System Center Configuration Manager SDK download), may be a better option for most users. > -> For information about the Configuration Manager Management Point Interface, see [Configuration Manager Management Point Interface](http://go.microsoft.com/fwlink/?LinkId=255152). +> For information about the Configuration Manager Management Point Interface, see [Configuration Manager Management Point Interface](https://go.microsoft.com/fwlink/?LinkId=255152). > -> For information about the Configuration Manager endpoint messages in XML format, see [About Configuration Manager Management Point Interface Messages](http://go.microsoft.com/fwlink/?LinkId=255153). +> For information about the Configuration Manager endpoint messages in XML format, see [About Configuration Manager Management Point Interface Messages](https://go.microsoft.com/fwlink/?LinkId=255153). ## Configuration Manager Operating System Deployment The following samples are in the %*Program Files*%\Microsoft System Center 2012 R2 Configuration Manager SDK\Samples\OperatingSystemDeployment folder. diff --git a/sccm/develop/core/understand/connecting-to-configuration-manager-with-windows-powershell.md b/sccm/develop/core/understand/connecting-to-configuration-manager-with-windows-powershell.md index 5655a07bf0c..fa0d8d3be56 100644 --- a/sccm/develop/core/understand/connecting-to-configuration-manager-with-windows-powershell.md +++ b/sccm/develop/core/understand/connecting-to-configuration-manager-with-windows-powershell.md @@ -174,7 +174,7 @@ In the [Configuration Manager Windows PowerShell Basics](../../../develop/core/u You can get a Configuration Manager site by using either a site name or a site code. RELATED LINKS - Online Version: http://go.microsoft.com/fwlink/?LinkID=263855 + Online Version: https://go.microsoft.com/fwlink/?LinkID=263855 Set-CMSite REMARKS diff --git a/sccm/develop/core/understand/getting-started-with-configuration-manager-and-windows-powershell.md b/sccm/develop/core/understand/getting-started-with-configuration-manager-and-windows-powershell.md index 8e8016bd480..e844368dd18 100644 --- a/sccm/develop/core/understand/getting-started-with-configuration-manager-and-windows-powershell.md +++ b/sccm/develop/core/understand/getting-started-with-configuration-manager-and-windows-powershell.md @@ -35,24 +35,24 @@ In System Center Configuration Manager, Windows PowerShell allows you to manage **Books:** There are numerous books available for PowerShell. A few example books are listed below. -- [Learn Windows PowerShell in a Month of Lunches](http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080/ref=sr_1_1?s=books&ie=UTF8&qid=1383160508&sr=1-1&keywords=PowerShell) +- [Learn Windows PowerShell in a Month of Lunches](https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080/ref=sr_1_1?s=books&ie=UTF8&qid=1383160508&sr=1-1&keywords=PowerShell) - [Windows PowerShell Step by Step](https://www.amazon.com/Windows-PowerShell-Step-3rd/dp/0735675112/ref=sr_1_1?s=books&ie=UTF8&qid=1472588703&sr=1-1&keywords=Windows+PowerShell+step+by+step) -- [Windows PowerShell Cookbook: The Complete Guide to Scripting Microsoft's Command Shell](http://www.amazon.com/Windows-PowerShell-Cookbook-Scripting-Microsofts/dp/1449320686/ref=pd_sim_b_3) +- [Windows PowerShell Cookbook: The Complete Guide to Scripting Microsoft's Command Shell](https://www.amazon.com/Windows-PowerShell-Cookbook-Scripting-Microsofts/dp/1449320686/ref=pd_sim_b_3) **Videos:** There are numerous videos available for PowerShell. A few example videos are listed below. -- [Channel9: Windows PowerShell Crash Course](http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/WSV321-R) +- [Channel9: Windows PowerShell Crash Course](https://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/WSV321-R) - [Channel9: What's New in PowerShell v5](https://channel9.msdn.com/Blogs/Taste-of-Premier/Whats-New-in-PowerShell-v5) -- [YouTube: PowerShell in a Nutshell](http://www.youtube.com/watch?v=vvCtUwHN2XI) +- [YouTube: PowerShell in a Nutshell](https://www.youtube.com/watch?v=vvCtUwHN2XI) **Forums/Sites:** There are numerous forums/sites available for PowerShell. A few example forums/sites are listed below. - [Microsoft: Scripting](https://technet.microsoft.com/scriptcenter/default) -- [Microsoft: Windows Server\Windows PowerShell](http://social.technet.microsoft.com/Forums/windowsserver/home?forum=winserverpowershell) +- [Microsoft: Windows Server\Windows PowerShell](https://social.technet.microsoft.com/Forums/windowsserver/home?forum=winserverpowershell) -- [MVP Kaido Järvemets: Configuration Manager PowerShell SDK](http://cm12sdk.net/) +- [MVP Kaido Järvemets: Configuration Manager PowerShell SDK](https://cm12sdk.net/) diff --git a/sccm/develop/core/understand/getting-started-with-configuration-manager-programming.md b/sccm/develop/core/understand/getting-started-with-configuration-manager-programming.md index b5451cf3e1e..3193ebe2ec2 100644 --- a/sccm/develop/core/understand/getting-started-with-configuration-manager-programming.md +++ b/sccm/develop/core/understand/getting-started-with-configuration-manager-programming.md @@ -23,28 +23,28 @@ To get started with programming for System Center Configuration Manager, it’s - [Fundamentals of System Center Configuration Manager](https://technet.microsoft.com/library/mt622643.aspx) -- [TechNet Virtual Labs](http://go.microsoft.com/fwlink/?LinkId=329809) (See: Virtual Lab: Introduction to Configuration Manager 2012 SP1) +- [TechNet Virtual Labs](https://go.microsoft.com/fwlink/?LinkId=329809) (See: Virtual Lab: Introduction to Configuration Manager 2012 SP1) ### More Resources **Books:** There are numerous books available for Configuration Manager. A few example books are listed below. -- [System Center 2012 Configuration Manager: Mastering the Fundamentals](http://www.amazon.com/System-Center-2012-Configuration-Manager/dp/9197939048) +- [System Center 2012 Configuration Manager: Mastering the Fundamentals](https://www.amazon.com/System-Center-2012-Configuration-Manager/dp/9197939048) -- [System Center 2012 Configuration Manager (SCCM) Unleashed](http://www.amazon.com/System-Center-Configuration-Manager-Unleashed/dp/0672334372/ref=sr_1_1?s=books&ie=UTF8&qid=1382812114&sr=1-1&keywords=System+Center+2012+Configuration+Manager+%28SCCM%29+Unleashed) +- [System Center 2012 Configuration Manager (SCCM) Unleashed](https://www.amazon.com/System-Center-Configuration-Manager-Unleashed/dp/0672334372/ref=sr_1_1?s=books&ie=UTF8&qid=1382812114&sr=1-1&keywords=System+Center+2012+Configuration+Manager+%28SCCM%29+Unleashed) -- [Microsoft System Center 2012 Configuration Manager: Administration Cookbook](http://www.amazon.com/Microsoft-System-Center-Configuration-Manager/dp/1849684944/ref=sr_1_1?s=books&ie=UTF8&qid=1382812164&sr=1-1&keywords=Microsoft+System+Center+2012+Configuration+Manager%3A+Administration+Cookbook) +- [Microsoft System Center 2012 Configuration Manager: Administration Cookbook](https://www.amazon.com/Microsoft-System-Center-Configuration-Manager/dp/1849684944/ref=sr_1_1?s=books&ie=UTF8&qid=1382812164&sr=1-1&keywords=Microsoft+System+Center+2012+Configuration+Manager%3A+Administration+Cookbook) **Videos:** There are numerous videos available for Configuration Manager. A few example videos are listed below. -- [Channel 9: Microsoft System Center 2012 Configuration Manager Overview](http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/MGT309) +- [Channel 9: Microsoft System Center 2012 Configuration Manager Overview](https://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/MGT309) -- [YouTube: Technical Deep Dive: System Center Configuration Manager 2012 Technical Overview](http://www.youtube.com/watch?v=qLACm3910_A) +- [YouTube: Technical Deep Dive: System Center Configuration Manager 2012 Technical Overview](https://www.youtube.com/watch?v=qLACm3910_A) **Forums:** There are numerous forums available for Configuration Manager. A few example forums are listed below. -- [TechNet: Configuration Manager 2012 - General](http://social.technet.microsoft.com/Forums/home?forum=configmanagergeneral) +- [TechNet: Configuration Manager 2012 - General](https://social.technet.microsoft.com/Forums/home?forum=configmanagergeneral) -- [windows-noob.com: Configuration Manager 2012](http://www.windows-noob.com/forums/index.php?/forum/92-setup-sccm-2012/) +- [windows-noob.com: Configuration Manager 2012](https://www.windows-noob.com/forums/index.php?/forum/92-setup-sccm-2012/) ## Architectural Understanding Configuration Manager is multi-tiered, distributed management system. It’s important to understand the general architecture of Configuration Manager. Below is a link to an overview of the Configuration Manager architecture. @@ -131,7 +131,7 @@ To get started with programming for System Center Configuration Manager, it’s **Policy Spy:** A policy viewer that helps you review and troubleshoot the policy system on System Center 2012 Configuration Manager clients. - Client Spy and Policy Spy are both tools contained in the [System Center 2012 Configuration Manager Toolkit](http://www.microsoft.com/download/details.aspx?id=29265) + Client Spy and Policy Spy are both tools contained in the [System Center 2012 Configuration Manager Toolkit](https://www.microsoft.com/download/details.aspx?id=29265) ## Basic Configuration Manager Program Example Below is link to a very simple Configuration Manager program showing some basic operations common to many Configuration Manager programs: diff --git a/sccm/develop/core/understand/introduction-to-wbemtest.md b/sccm/develop/core/understand/introduction-to-wbemtest.md index 77276c3fc62..273daa9a22e 100644 --- a/sccm/develop/core/understand/introduction-to-wbemtest.md +++ b/sccm/develop/core/understand/introduction-to-wbemtest.md @@ -77,17 +77,17 @@ If you spend much time around Configuration Manager you become aware that much o ### More Resources **Books:** There are numerous books available for WMI. A few example books are listed below. -- [Developing WMI Solutions: A Guide to Windows Management Instrumentation](http://www.amazon.com/gp/product/0201616130/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=1535523722&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=1578702607&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=05X3A23E6YKTXGZ0P9NZ) +- [Developing WMI Solutions: A Guide to Windows Management Instrumentation](https://www.amazon.com/gp/product/0201616130/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=1535523722&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=1578702607&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=05X3A23E6YKTXGZ0P9NZ) -- [Windows Management Instrumentation](http://www.amazon.com/Windows-Management-Instrumentation-Matthew-Lavy/dp/1578702607) +- [Windows Management Instrumentation](https://www.amazon.com/Windows-Management-Instrumentation-Matthew-Lavy/dp/1578702607) -- [Microsoft® Windows® Scripting with WMI: Self-Paced Learning Guide](http://www.amazon.com/Microsoft-Windows-Scripting-WMI-Self-Paced/dp/0735622310/ref=sr_1_5?ie=UTF8&qid=1383150816&sr=8-5&keywords=wmi+books) +- [Microsoft® Windows® Scripting with WMI: Self-Paced Learning Guide](https://www.amazon.com/Microsoft-Windows-Scripting-WMI-Self-Paced/dp/0735622310/ref=sr_1_5?ie=UTF8&qid=1383150816&sr=8-5&keywords=wmi+books) **Videos:** There are numerous videos available for WMI. A few example videos are listed below. -- [YouTube: WMI Powershell Introduction](http://www.youtube.com/watch?v=5qZfs4j73IQ) +- [YouTube: WMI Powershell Introduction](https://www.youtube.com/watch?v=5qZfs4j73IQ) -- [YouTube: What is WMI and how to enable remote WMI ?](http://www.youtube.com/watch?v=Nlf3IuTY9wA) +- [YouTube: What is WMI and how to enable remote WMI ?](https://www.youtube.com/watch?v=Nlf3IuTY9wA) **Other:** Other resources for WMI are listed below. diff --git a/sccm/develop/core/understand/sms-provider-fundamentals.md b/sccm/develop/core/understand/sms-provider-fundamentals.md index 076bc2cb111..f27d7eeef2d 100644 --- a/sccm/develop/core/understand/sms-provider-fundamentals.md +++ b/sccm/develop/core/understand/sms-provider-fundamentals.md @@ -20,7 +20,7 @@ You use the SMS Provider to access and modify System Center Configuration Manage ### WMI Object Model Management applications and scripts work with WMI through the WMI Object Model. The object model defines the programming interface to WMI. - For more information about WMI, see [Windows Management Instrumentation](http://go.microsoft.com/fwlink/?LinkId=276770). + For more information about WMI, see [Windows Management Instrumentation](https://go.microsoft.com/fwlink/?LinkId=276770). The main elements of the WMI Object Model are shown in the following table: diff --git a/sccm/develop/core/understand/windows-powershell-basics.md b/sccm/develop/core/understand/windows-powershell-basics.md index a17eea71d2e..d7e7e65fbab 100644 --- a/sccm/develop/core/understand/windows-powershell-basics.md +++ b/sccm/develop/core/understand/windows-powershell-basics.md @@ -14,7 +14,7 @@ ms.collection: M365-identity-device-management # Windows PowerShell Basics System Center 2012 Configuration Manager SP1 introduced native PowerShell support. Windows PowerShell is Microsoft's approach to automation and is being implemented across all System Center products. This topic will introduce you to some of the basics of using Windows PowerShell with Configuration Manager. - First, you need to make sure that Windows PowerShell 3.0 or later is installed. If Windows PowerShell 3.0 or later is not installed, you can download the latest version of Windows PowerShell as part of the [Windows Management Framework 5.0](https://www.microsoft.com/en-us/download/details.aspx?id=50395). + First, you need to make sure that Windows PowerShell 3.0 or later is installed. If Windows PowerShell 3.0 or later is not installed, you can download the latest version of Windows PowerShell as part of the [Windows Management Framework 5.0](https://www.microsoft.com/download/details.aspx?id=50395). To get started: diff --git a/sccm/develop/core/understand/wmi-configuration-manager-provider-fundamentals.md b/sccm/develop/core/understand/wmi-configuration-manager-provider-fundamentals.md index 838b1ec6f6d..426db51e09b 100644 --- a/sccm/develop/core/understand/wmi-configuration-manager-provider-fundamentals.md +++ b/sccm/develop/core/understand/wmi-configuration-manager-provider-fundamentals.md @@ -12,7 +12,7 @@ manager: dougeby ms.collection: M365-identity-device-management --- # WMI Configuration Manager Provider Fundamentals -Windows Script Host-based applications and scripts work in Windows Management Instrumentation (WMI) through the WMI Object Model, which defines the programming interface to WMI. A number of WMI object types are used when manipulating System Center Configuration Manager objects. For more information about the WMI Object Model, see [Windows Management Instrumentation](http://go.microsoft.com/fwlink/?LinkId=276770). +Windows Script Host-based applications and scripts work in Windows Management Instrumentation (WMI) through the WMI Object Model, which defines the programming interface to WMI. A number of WMI object types are used when manipulating System Center Configuration Manager objects. For more information about the WMI Object Model, see [Windows Management Instrumentation](https://go.microsoft.com/fwlink/?LinkId=276770). In simple Configuration Manager scripts, you use the following WMI object types: @@ -32,18 +32,18 @@ Windows Script Host-based applications and scripts work in Windows Management In For more information about using VBScript and WMI, see [Objects overview](/sccm/develop/core/understand/configuration-manager-objects-overview). ## SWbemLocator - The [SWbemServices](http://go.microsoft.com/fwlink/?LinkId=276771)object is used to create an authenticated connection to the SMS Provider. You use the [ConnectServer](http://go.microsoft.com/fwlink/?LinkId=276772) method to make the connection to the SMS Provider. This method is particularly useful if you need to pass user credentials to a remote Configuration Manager server during connection. You can also use the Windows Script Host [GetObject](http://go.microsoft.com/fwlink/?LinkId=276773) method to create an authenticated connection. The type of object that is returned by `GetObject` depends on the parameters that are passed to it. See [How to Connect to a Configuration Manager Provider Using Managed Code](../../../develop/core/understand/how-to-connect-to-an-sms-provider-by-using-managed-code.md) and [How to Connect to a Configuration Manager Provider Using WMI](../../../develop/core/understand/how-to-connect-to-an-sms-provider-in-configuration-manager-by-using-wmi.md) for examples that show how to use either `SWbemLocator` or `GetObject` in your connection script. + The [SWbemServices](https://go.microsoft.com/fwlink/?LinkId=276771)object is used to create an authenticated connection to the SMS Provider. You use the [ConnectServer](https://go.microsoft.com/fwlink/?LinkId=276772) method to make the connection to the SMS Provider. This method is particularly useful if you need to pass user credentials to a remote Configuration Manager server during connection. You can also use the Windows Script Host [GetObject](https://go.microsoft.com/fwlink/?LinkId=276773) method to create an authenticated connection. The type of object that is returned by `GetObject` depends on the parameters that are passed to it. See [How to Connect to a Configuration Manager Provider Using Managed Code](../../../develop/core/understand/how-to-connect-to-an-sms-provider-by-using-managed-code.md) and [How to Connect to a Configuration Manager Provider Using WMI](../../../develop/core/understand/how-to-connect-to-an-sms-provider-in-configuration-manager-by-using-wmi.md) for examples that show how to use either `SWbemLocator` or `GetObject` in your connection script. ## SWbemServices - The [SWbemServices](http://go.microsoft.com/fwlink/?LinkId=276771) object represents an authenticated connection to a SMS Provider, and it is the object that you use to retrieve Configuration Manager objects. You receive an `SWbemServices` object as the return value of the `SWbemLocator` function `ConnectServer` or, alternatively, as the return value when the `GetObject` method is used to connect to the SMS Provider. `SWbemServices` has several methods, but you use only the [Get](http://go.microsoft.com/fwlink/?LinkId=276774), [ExecQuery](http://go.microsoft.com/fwlink/?LinkId=276775), and [InstancesOf](http://go.microsoft.com/fwlink/?LinkId=276776) methods for retrieving objects. + The [SWbemServices](https://go.microsoft.com/fwlink/?LinkId=276771) object represents an authenticated connection to a SMS Provider, and it is the object that you use to retrieve Configuration Manager objects. You receive an `SWbemServices` object as the return value of the `SWbemLocator` function `ConnectServer` or, alternatively, as the return value when the `GetObject` method is used to connect to the SMS Provider. `SWbemServices` has several methods, but you use only the [Get](https://go.microsoft.com/fwlink/?LinkId=276774), [ExecQuery](https://go.microsoft.com/fwlink/?LinkId=276775), and [InstancesOf](https://go.microsoft.com/fwlink/?LinkId=276776) methods for retrieving objects. `Get` returns a single instance of a Configuration Manager object (`SWbemObject`). `ExecQuery` and `InstancesOf` return Configuration Manager objects in a collection (`SWbemObjectSet`) of Configuration Manager objects. ## SWbemObjectSet - The [SWbemObjectSet](http://go.microsoft.com/fwlink/?LinkId=276777) object represents a collection of Configuration Manager objects. You can use it to enumerate through the collection and read individual instances of the Configuration Manager object (`SWbemObject`) that you are interested in. You typically get a `SWbemObjectSet` object returned to you from the `SWbemServices` retrieval functions. + The [SWbemObjectSet](https://go.microsoft.com/fwlink/?LinkId=276777) object represents a collection of Configuration Manager objects. You can use it to enumerate through the collection and read individual instances of the Configuration Manager object (`SWbemObject`) that you are interested in. You typically get a `SWbemObjectSet` object returned to you from the `SWbemServices` retrieval functions. ## SWbemObject - The [SWbemObject](http://go.microsoft.com/fwlink/?LinkId=276778) object allows you to access the properties and other information for a Configuration Manager object. + The [SWbemObject](https://go.microsoft.com/fwlink/?LinkId=276778) object allows you to access the properties and other information for a Configuration Manager object. ## See also diff --git a/sccm/develop/mdm/how-to-configure-mobile-device-client-agent-settings.md b/sccm/develop/mdm/how-to-configure-mobile-device-client-agent-settings.md index 9a35562fba7..935083fdcc8 100644 --- a/sccm/develop/mdm/how-to-configure-mobile-device-client-agent-settings.md +++ b/sccm/develop/mdm/how-to-configure-mobile-device-client-agent-settings.md @@ -15,7 +15,7 @@ ms.collection: M365-identity-device-management You configure the Mobile Device Client Agent settings, in System Center Configuration Manager, by modifying the site control file. > [!IMPORTANT] -> This topic only applies to the Mobile Device Legacy Client. For addition information on the Mobile Device Legacy Client platforms, see the Mobile Device Legacy Client section of the [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=272885). +> This topic only applies to the Mobile Device Legacy Client. For addition information on the Mobile Device Legacy Client platforms, see the Mobile Device Legacy Client section of the [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=272885). ### To configure the Mobile Device Client Agent settings diff --git a/sccm/develop/mdm/how-to-create-software-distribution-packages-for-mobile-devices.md b/sccm/develop/mdm/how-to-create-software-distribution-packages-for-mobile-devices.md index 9008d25bc31..6b478023d8d 100644 --- a/sccm/develop/mdm/how-to-create-software-distribution-packages-for-mobile-devices.md +++ b/sccm/develop/mdm/how-to-create-software-distribution-packages-for-mobile-devices.md @@ -21,7 +21,7 @@ System Center Configuration Manager device management enables mobile device soft - [How to Create an Advertisement](../../develop/core/servers/configure/how-to-create-an-advertisement.md) > [!IMPORTANT] -> This topic only applies to the Mobile Device Legacy Client. For addition information on the Mobile Device Legacy Client platforms, see the Mobile Device Legacy Client section of the [Supported Configurations for Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=272885). +> This topic only applies to the Mobile Device Legacy Client. For addition information on the Mobile Device Legacy Client platforms, see the Mobile Device Legacy Client section of the [Supported Configurations for Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=272885). ## Packages Packages for mobile devices in System Center Configuration Manager generally represent a software application to be installed on a mobile device, but they might also contain individual files, updates, or even an individual command. diff --git a/sccm/develop/osd/about-configuration-manager-custom-action-client-applications.md b/sccm/develop/osd/about-configuration-manager-custom-action-client-applications.md index 3fffdd5b500..280d40334b6 100644 --- a/sccm/develop/osd/about-configuration-manager-custom-action-client-applications.md +++ b/sccm/develop/osd/about-configuration-manager-custom-action-client-applications.md @@ -59,7 +59,7 @@ CommandLine("smsswd.exe /run:PackageID abc.exe [any abc.exe command line args]" ### Environment The MOF file should specify the operating environment with the [SMS_TaskSequence_Action Server WMI Class](../../develop/reference/osd/sms_tasksequence_action-server-wmi-class.md)`SupportedEnvironment` property. The available environments are Windows PE (`WinPE`), full operating system (`FullOS`), or both environments (`WinPEandFullOS`). - The choice of environment depends on the circumstances. For example, pre-operating install configuration will likely be done in the Windows PE environment. For more information, see [http://go.microsoft.com/fwlink/?LinkID=110498](http://go.microsoft.com/fwlink/?LinkID=110498). Updates to currently installed operating systems will use the full operating system environment. For example, software or driver installation. Operating system environment agnostic tasks such as reboots or the creation of network connections, can be performed by using both environment settings. + The choice of environment depends on the circumstances. For example, pre-operating install configuration will likely be done in the Windows PE environment. For more information, see [https://go.microsoft.com/fwlink/?LinkID=110498](https://go.microsoft.com/fwlink/?LinkID=110498). Updates to currently installed operating systems will use the full operating system environment. For example, software or driver installation. Operating system environment agnostic tasks such as reboots or the creation of network connections, can be performed by using both environment settings. ### Processing During processing, you access the task sequence variables defined by the MOF file by using the `TSEnvironment` COM automation object. For more information, see [How to Use Task Sequence Variables in a Running Configuration Manager Task Sequence](../../develop/osd/how-to-use-task-sequence-variables-in-a-running-task-sequence.md). @@ -74,7 +74,7 @@ CommandLine("smsswd.exe /run:PackageID abc.exe [any abc.exe command line args]" |0|Success| |Non-zero|Failure| - If a reboot is required after the application finishes, the `SMSTSRebootRequested` environment variable should be set. For more information, see [http://go.microsoft.com/fwlink/?LinkId=110499](http://go.microsoft.com/fwlink/?LinkId=110498). For information about setting environment variables, see [How to Use Task Sequence Variables in a Running Configuration Manager Task Sequence](../../develop/osd/how-to-use-task-sequence-variables-in-a-running-task-sequence.md). + If a reboot is required after the application finishes, the `SMSTSRebootRequested` environment variable should be set. For more information, see [https://go.microsoft.com/fwlink/?LinkId=110499](https://go.microsoft.com/fwlink/?LinkId=110498). For information about setting environment variables, see [How to Use Task Sequence Variables in a Running Configuration Manager Task Sequence](../../develop/osd/how-to-use-task-sequence-variables-in-a-running-task-sequence.md). ## Deployment To be used by System Center Configuration Manager, the custom action application must be available from a Configuration Manager package. The administrator can create the package by using either the Configuration Manager console or by using a programming language. For more information, see [How to Create a Package](../../develop/core/servers/configure/how-to-create-a-package.md). @@ -102,12 +102,12 @@ string PackageIDForAbcExe; - The package identifier is provided by using the `/run` command-line parameter to Smsswd.exe. ## Pre-Network Partition and Pre-Partition Setup - If you need to configure disk or network connectivity before you have a disk partition and before you have network connectivity, you will need to create an application to perform these tasks. Your application should be placed in a custom boot image by using the Windows Assessment and Deployment Kit. For more information, see TechNet documentation for the Windows Assessment and Deployment Kit ([http://go.microsoft.com/fwlink/?LinkId=111704](http://go.microsoft.com/fwlink/?LinkId=111704)). + If you need to configure disk or network connectivity before you have a disk partition and before you have network connectivity, you will need to create an application to perform these tasks. Your application should be placed in a custom boot image by using the Windows Assessment and Deployment Kit. For more information, see TechNet documentation for the Windows Assessment and Deployment Kit ([https://go.microsoft.com/fwlink/?LinkId=111704](https://go.microsoft.com/fwlink/?LinkId=111704)). > [!NOTE] > Adding files to the boot image file can increase the minimum RAM requirements and can, due to low memory conditions, cause task sequences to fail in unexpected ways. - You will then need to import the image into System Center Configuration Manager as a custom image. For more information, see How to Add a Boot Image to Configuration Manager ([http://go.microsoft.com/fwlink/?LinkId=111706](http://go.microsoft.com/fwlink/?LinkId=111706)). + You will then need to import the image into System Center Configuration Manager as a custom image. For more information, see How to Add a Boot Image to Configuration Manager ([https://go.microsoft.com/fwlink/?LinkId=111706](https://go.microsoft.com/fwlink/?LinkId=111706)). The application, any supporting files, and the custom SMSTS.INI should be placed in the Windows folder. diff --git a/sccm/develop/osd/about-operating-system-deployment-driver-management.md b/sccm/develop/osd/about-operating-system-deployment-driver-management.md index f7e3989a877..324b9e57594 100644 --- a/sccm/develop/osd/about-operating-system-deployment-driver-management.md +++ b/sccm/develop/osd/about-operating-system-deployment-driver-management.md @@ -12,7 +12,7 @@ manager: dougeby ms.collection: M365-identity-device-management --- # About Operating System Deployment Driver Management -In System Center Configuration Manager, the driver catalog helps manage the cost and complexity of deploying an operating system in an environment that contains different types of computers and devices. By storing device drivers in the driver catalog and not with each individual operating system image, the number of operating system images that is needed is greatly reduced. For more information about the driver catalog, see [http://go.microsoft.com/fwlink/?LinkId=110504](http://go.microsoft.com/fwlink/?LinkId=110504). +In System Center Configuration Manager, the driver catalog helps manage the cost and complexity of deploying an operating system in an environment that contains different types of computers and devices. By storing device drivers in the driver catalog and not with each individual operating system image, the number of operating system images that is needed is greatly reduced. For more information about the driver catalog, see [https://go.microsoft.com/fwlink/?LinkId=110504](https://go.microsoft.com/fwlink/?LinkId=110504). > [!NOTE] > Before a driver can be used, it must be added to a driver package. For more information, see [How to Create a Driver Package for a Windows Driver in Configuration Manager](../../develop/osd/how-to-create-a-driver-package-for-a-windows-driver.md). diff --git a/sccm/develop/reference/core/clients/client-classes/asset-intelligence-client-wmi-classes.md b/sccm/develop/reference/core/clients/client-classes/asset-intelligence-client-wmi-classes.md index 2aa7669cf0e..06912457d8c 100644 --- a/sccm/develop/reference/core/clients/client-classes/asset-intelligence-client-wmi-classes.md +++ b/sccm/develop/reference/core/clients/client-classes/asset-intelligence-client-wmi-classes.md @@ -32,9 +32,9 @@ In System Center Configuration Manager, the Asset Intelligence client Windows Ma ## Remarks Classes related to the asset intelligence client WMI classes are: -- `SoftwareLicensingProduct` class. Specific to Windows Vista. For more information, see the Microsoft TechNet article, [Windows Vista Volume Activation 2.0 Technical Attributes](http://go.microsoft.com/fwlink/?LinkId=99938). +- `SoftwareLicensingProduct` class. Specific to Windows Vista. For more information, see the Microsoft TechNet article, [Windows Vista Volume Activation 2.0 Technical Attributes](https://go.microsoft.com/fwlink/?LinkId=99938). -- `SoftwareLicensingService` class. Specific to Windows Vista. For more information, see the Microsoft TechNet article, [Windows Vista Volume Activation 2.0 Technical Attributes](http://go.microsoft.com/fwlink/?LinkId=99938). +- `SoftwareLicensingService` class. Specific to Windows Vista. For more information, see the Microsoft TechNet article, [Windows Vista Volume Activation 2.0 Technical Attributes](https://go.microsoft.com/fwlink/?LinkId=99938). - `Win32_USBDevice` class. Tracks devices connected to USB ports. diff --git a/sccm/develop/reference/core/servers/configure/sms_package-server-wmi-class.md b/sccm/develop/reference/core/servers/configure/sms_package-server-wmi-class.md index b6e86b1365a..c9eb818f29d 100644 --- a/sccm/develop/reference/core/servers/configure/sms_package-server-wmi-class.md +++ b/sccm/develop/reference/core/servers/configure/sms_package-server-wmi-class.md @@ -555,4 +555,4 @@ Class SMS_Package : SMS_PackageBaseclass [SMS_PackageBaseclass Server WMI Class](../../../../../develop/reference/core/servers/configure/sms_packagebaseclass-server-wmi-class.md) [GetPDFData Method in Class SMS_PDF_Package](../../../../../develop/reference/core/servers/configure/getpdfdata-method-in-class-sms_pdf_package.md) [How to Create a Package](../../../../../develop/core/servers/configure/how-to-create-a-package.md) - [PowerShell Cmdlet: New-CMPackage](http://go.microsoft.com/fwlink/?LinkId=309284) + [PowerShell Cmdlet: New-CMPackage](https://go.microsoft.com/fwlink/?LinkId=309284) diff --git a/sccm/develop/reference/core/servers/configure/sms_packagebaseclass-server-wmi-class.md b/sccm/develop/reference/core/servers/configure/sms_packagebaseclass-server-wmi-class.md index 51cc46d54b6..673a70e262b 100644 --- a/sccm/develop/reference/core/servers/configure/sms_packagebaseclass-server-wmi-class.md +++ b/sccm/develop/reference/core/servers/configure/sms_packagebaseclass-server-wmi-class.md @@ -542,4 +542,4 @@ For more information, see [Configuration Manager Server Development Requirements ## See Also [How to Create a Package](../../../../../develop/core/servers/configure/how-to-create-a-package.md) -[PowerShell Cmdlet: New-CMPackage](http://go.microsoft.com/fwlink/?LinkId=309284) +[PowerShell Cmdlet: New-CMPackage](https://go.microsoft.com/fwlink/?LinkId=309284) diff --git a/sccm/develop/reference/osd/sms_bootimagepackage-server-wmi-class.md b/sccm/develop/reference/osd/sms_bootimagepackage-server-wmi-class.md index ebb16e3458b..202ee736d47 100644 --- a/sccm/develop/reference/osd/sms_bootimagepackage-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_bootimagepackage-server-wmi-class.md @@ -575,7 +575,7 @@ Class SMS_BootImagePackage : SMS_PackageBaseclass |256| |512| - For additional information see [Windows PE Servicing Command-Line Options](http://go.microsoft.com/fwlink/?LinkId=272891). + For additional information see [Windows PE Servicing Command-Line Options](https://go.microsoft.com/fwlink/?LinkId=272891). This information applies to System Center 2012 Configuration Manager SP1 or later, and System Center 2012 R2 Configuration Manager or later. diff --git a/sccm/develop/reference/osd/sms_driver-server-wmi-class.md b/sccm/develop/reference/osd/sms_driver-server-wmi-class.md index 8c4c75b9679..4b3f9fb31c5 100644 --- a/sccm/develop/reference/osd/sms_driver-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_driver-server-wmi-class.md @@ -593,7 +593,7 @@ Class SMS_Driver : SMS_ConfigurationItemBaseClass For more information about both the class qualifiers and the property qualifiers included in the Properties section, see [Configuration Manager Class and Property Qualifiers](../../../develop/reference/misc/class-and-property-qualifiers.md). - Configuration Manager uses a driver catalog to manage the different computers, devices, and associated Windows device drivers that it supports. For more information, see [About the Driver Catalog](http://go.microsoft.com/fwlink/?LinkID=110504). + Configuration Manager uses a driver catalog to manage the different computers, devices, and associated Windows device drivers that it supports. For more information, see [About the Driver Catalog](https://go.microsoft.com/fwlink/?LinkID=110504). You can create an `SMS_Driver` object by using the [CreateFromINF Method in Class SMS_Driver](../../../develop/reference/osd/createfrominf-method-in-class-sms_driver.md) and [CreateFromOEM Method in Class SMS_Driver](../../../develop/reference/osd/createfromoem-method-in-class-sms_driver.md) methods. You use [CreateFromINF Method in Class SMS_Driver](../../../develop/reference/osd/createfrominf-method-in-class-sms_driver.md) to create an `SMS_Driver` Object from a Windows driver INF file. For more information see, How to Import a Windows Driver Described by an INF File into Configuration Manager. You use [CreateFromOEM Method in Class SMS_Driver](../../../develop/reference/osd/createfromoem-method-in-class-sms_driver.md) to create an `SMS_Driver` object from a Txtsetup.oem file. diff --git a/sccm/develop/reference/osd/sms_tasksequence_applydataimageaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_applydataimageaction-server-wmi-class.md index 3b3a1fd643f..c9ab6d216d7 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_applydataimageaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_applydataimageaction-server-wmi-class.md @@ -123,7 +123,7 @@ Class SMS_TaskSequence_ApplyDataImageAction : SMS_TaskSequence_Action Index of the image in the WIM file applied to the target computer. Possible index values are 1 through 2147483647. For more information, see the note in Remarks. - The task sequence variable associated with this property is OSDDataImageIndex. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDDataImageIndex. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `ImagePackageID` Data type: `String` @@ -172,7 +172,7 @@ Class SMS_TaskSequence_ApplyDataImageAction : SMS_TaskSequence_Action `true` (default) to wipe the contents of the destination partition before the image is applied. - The task sequence variable associated with this property is OSDWipeDestinationPartition. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDWipeDestinationPartition. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). ## Remarks Class qualifiers for this class include: diff --git a/sccm/develop/reference/osd/sms_tasksequence_applydriverpackageaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_applydriverpackageaction-server-wmi-class.md index ba8f7f5b95f..a3b31fa6855 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_applydriverpackageaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_applydriverpackageaction-server-wmi-class.md @@ -185,7 +185,7 @@ Class SMS_TaskSequence_ApplyDriverPackageAction : SMS_TaskSequence_Action > [!NOTE] > This property is required by the action. However it is not used when deploying the Windows Vista operating system. - The task sequence variable associated with this property is OSDAllowUnsignedDriver. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDAllowUnsignedDriver. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). ## Remarks Class qualifiers for this class include: diff --git a/sccm/develop/reference/osd/sms_tasksequence_applynetworksettingsaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_applynetworksettingsaction-server-wmi-class.md index b605d57a5e4..6e3a936e0b5 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_applynetworksettingsaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_applynetworksettingsaction-server-wmi-class.md @@ -55,7 +55,7 @@ Class SMS_TaskSequence_ApplyNetworkSettingsAction : SMS_TaskSequence_Action [SMS_TaskSequence_NetworkAdapterSettings Server WMI Class](../../../develop/reference/osd/sms_tasksequence_networkadaptersettings-server-wmi-class.md) objects representing settings for the adapters installed on the target computer. This property must be global so that it is visible in finalize mode. - The task sequence variable associated with this property is OSDAdapter. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDAdapter. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Condition` Data type: `SMS_TaskSequence_Condition` @@ -129,7 +129,7 @@ Class SMS_TaskSequence_ApplyNetworkSettingsAction : SMS_TaskSequence_Action Password of the account used when the user joins a Windows domain. Set this property if `NetworkJoinType` is set to 0. - The task sequence variable associated with this property is OSDJoinPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDJoinPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `DomainUsername` Data type: `String` @@ -140,7 +140,7 @@ Class SMS_TaskSequence_ApplyNetworkSettingsAction : SMS_TaskSequence_Action Account used when the user joins a Windows domain. Set this property if `NetworkJoinType` is set to 0. - The task sequence variable associated with this property is OSDJoinAccount, which specifies the network account that should be used to add the target computer to a Windows domain. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDJoinAccount, which specifies the network account that should be used to add the target computer to a Windows domain. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Enabled` Data type: `Boolean` @@ -192,7 +192,7 @@ Class SMS_TaskSequence_ApplyNetworkSettingsAction : SMS_TaskSequence_Action Size of the array indicated by the `Adapters` property. This property must be global so that it is visible in finalize mode. - The task sequence variable associated with this property is OSDAdapterCount. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDAdapterCount. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). OSDAdapterCount diff --git a/sccm/develop/reference/osd/sms_tasksequence_applyoperatingsystemaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_applyoperatingsystemaction-server-wmi-class.md index 87cebe83fae..4a2ba8dacba 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_applyoperatingsystemaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_applyoperatingsystemaction-server-wmi-class.md @@ -64,7 +64,7 @@ Class SMS_TaskSequence_ApplyOperatingSystemAction : SMS_TaskSequence_Action The name of the answer file specified in the `ConfigFilePackage` property. For more information, see the Remarks section later in this topic. - The task sequence variable associated with this property is OSDConfigFileName. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDConfigFileName. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `ConfigFilePackage` Data type: `String` @@ -147,7 +147,7 @@ Class SMS_TaskSequence_ApplyOperatingSystemAction : SMS_TaskSequence_Action Index of the image in the WIM file applied to the target computer. The value of this property can be between 1 and 2147483647. This property is required if `ImagePackageID` is set. For more information, see the Remarks section later in this topic. - The task sequence variable associated with this property is OSDImageIndex. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDImageIndex. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `ImagePackageID` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_applywindowssettingsaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_applywindowssettingsaction-server-wmi-class.md index 9d3eadd22c9..348e5ac1d7a 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_applywindowssettingsaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_applywindowssettingsaction-server-wmi-class.md @@ -53,7 +53,7 @@ Class SMS_TaskSequence_ApplyWindowsSettingsAction : SMS_TaskSequence_Action Local administrator password. The name can be between 0 and 255 characters in length. This property must be set, but it is ignored if the `RandomAdminPassword` property is set to `true`. - The task sequence variable associated with this property is OSDLocalAdminPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDLocalAdminPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `ComputerName` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_autoapplyaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_autoapplyaction-server-wmi-class.md index 4b1051b7170..e07ce76d438 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_autoapplyaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_autoapplyaction-server-wmi-class.md @@ -135,7 +135,7 @@ Class SMS_TaskSequence_AutoApplyAction : SMS_TaskSequence_Action `true` to configure the Windows operating system to allow unsigned device drivers to be installed. The default value is `false`. - The task sequence variable associated with this property is OSDAllowUnsignedDriver. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDAllowUnsignedDriver. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). > [!NOTE] > This property is required by the task sequence action. Unattended installation of unsigned drivers is done on versions of Windows where this is allowed. diff --git a/sccm/develop/reference/osd/sms_tasksequence_capturenetworksettingsaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_capturenetworksettingsaction-server-wmi-class.md index 69357fae2b4..7e508c88c98 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_capturenetworksettingsaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_capturenetworksettingsaction-server-wmi-class.md @@ -82,7 +82,7 @@ Class SMS_TaskSequence_CaptureNetworkSettingsAction : SMS_TaskSequence_Action `true` (default) to migrate TCP/IP, DNS, and WINS settings for network adapters. - The task sequence variable associated with this property is OSDMigrateAdapterSettings. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateAdapterSettings. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `MigrateNetworkMembership` Data type: `Boolean` @@ -93,7 +93,7 @@ Class SMS_TaskSequence_CaptureNetworkSettingsAction : SMS_TaskSequence_Action `true` to migrate workgroup or domain membership information as part of operating system deployment. The default value is `false`. - The task sequence variable associated with this property is OSDMigrateNetworkMembership. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateNetworkMembership. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Name` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_capturesystemimageaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_capturesystemimageaction-server-wmi-class.md index 4c53cc87cc7..03c5e107f9c 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_capturesystemimageaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_capturesystemimageaction-server-wmi-class.md @@ -61,7 +61,7 @@ Class SMS_TaskSequence_CaptureSystemImageAction : SMS_TaskSequence_Action Password of the account specified by the `CaptureUsername` property. - The task sequence variable associated with this property is OSDCaptureAccountPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDCaptureAccountPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `CaptureUsername` Data type: `String` @@ -72,7 +72,7 @@ Class SMS_TaskSequence_CaptureSystemImageAction : SMS_TaskSequence_Action A Windows account name that has permissions to the network share where the captured image will be stored, specified by `CaptureDestination`. This name is specified in "domain\username" format. To set this property, you must have write access to the destination folder. - The task sequence variable associated with this property is OSDCaptureAccount. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDCaptureAccount. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Condition` Data type: `SMS_TaskSequence_Condition` diff --git a/sccm/develop/reference/osd/sms_tasksequence_captureuserstateaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_captureuserstateaction-server-wmi-class.md index 5a525a36208..f0d995fc9d7 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_captureuserstateaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_captureuserstateaction-server-wmi-class.md @@ -80,7 +80,7 @@ Class SMS_TaskSequence_CaptureUserStateAction : SMS_TaskSequence_Action `true` (default) to allow the capture user state action to proceed even if some files cannot be captured. This property is required. - The task sequence variable associated with this property is OSDMigrateContinueOnLockedFiles. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateContinueOnLockedFiles. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Description` Data type: `String` @@ -164,7 +164,7 @@ Class SMS_TaskSequence_CaptureUserStateAction : SMS_TaskSequence_Action `true` to skip encrypted files. The default value is `false`. - The task sequence variable associated with this property is OSDMigrateSkipEncryptedFiles. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateSkipEncryptedFiles. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `SupportedEnvironment` Data type: `String` @@ -204,7 +204,7 @@ Class SMS_TaskSequence_CaptureUserStateAction : SMS_TaskSequence_Action The ID of the Configuration Manager package that contains USMT binaries. This property is required. - The task sequence variable associated with this property is _OSDMigrateUsmtPackageID. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is _OSDMigrateUsmtPackageID. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). ## Remarks Class qualifiers for this class include: diff --git a/sccm/develop/reference/osd/sms_tasksequence_capturewindowssettingsaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_capturewindowssettingsaction-server-wmi-class.md index f0d6d482b55..a82a974cc92 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_capturewindowssettingsaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_capturewindowssettingsaction-server-wmi-class.md @@ -83,7 +83,7 @@ Class SMS_TaskSequence_CaptureWindowsSettingsAction : SMS_TaskSequence_Action `true` (default) to migrate the computer name. - The task sequence variable associated with this property is OSDMigrateComputerName. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateComputerName. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `MigrateRegistrationInfo` Data type: `Boolean` @@ -94,7 +94,7 @@ Class SMS_TaskSequence_CaptureWindowsSettingsAction : SMS_TaskSequence_Action `true` (default) to migrate information about the registered owner or organization. - The task sequence variable associated with this property is OSDMigrateRegistrationInfo. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateRegistrationInfo. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `MigrateTimeZone` Data type: `Boolean` @@ -105,7 +105,7 @@ Class SMS_TaskSequence_CaptureWindowsSettingsAction : SMS_TaskSequence_Action `true` (default) to migrate information about the time zone. - The task sequence variable associated with this property is OSDMigrateTimeZone. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateTimeZone. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Name` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_connectnetworkfolderaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_connectnetworkfolderaction-server-wmi-class.md index c0840d17fa8..d0ceb37ea77 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_connectnetworkfolderaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_connectnetworkfolderaction-server-wmi-class.md @@ -102,7 +102,7 @@ Class SMS_TaskSequence_ConnectNetworkFolderAction : SMS_TaskSequence_Action Password to use to connect to the network share. - The task sequence variable associated with this property is SMSConnectNetworkFolderPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is SMSConnectNetworkFolderPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Path` Data type: `String` @@ -140,7 +140,7 @@ Class SMS_TaskSequence_ConnectNetworkFolderAction : SMS_TaskSequence_Action Account that should be used to connect to the network share. - The task sequence variable associated with this property is SMSConnectNetworkFolderAccount. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is SMSConnectNetworkFolderAccount. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). ## Remarks Class qualifiers for this class include: diff --git a/sccm/develop/reference/osd/sms_tasksequence_convertdiskaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_convertdiskaction-server-wmi-class.md index 769e5095be2..0ee13ac521d 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_convertdiskaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_convertdiskaction-server-wmi-class.md @@ -72,7 +72,7 @@ Class SMS_TaskSequence_ConvertDiskAction : SMS_TaskSequence_Action The physical disk number to convert. - The task sequence variable associated with this property is OSDConvertDiskIndex. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDConvertDiskIndex. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Enabled` Data type: `Boolean` diff --git a/sccm/develop/reference/osd/sms_tasksequence_installsoftwareaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_installsoftwareaction-server-wmi-class.md index ccdf7a65070..fd11951aa86 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_installsoftwareaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_installsoftwareaction-server-wmi-class.md @@ -120,7 +120,7 @@ Class SMS_TaskSequence_InstallSoftwareAction : SMS_TaskSequence_Action The program in the package to install. This property is required if `PackageID` is not set to `null`. - The task sequence variable associated with this property is _SMSSWDProgramName. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is _SMSSWDProgramName. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `SupportedEnvironment` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_installupdateaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_installupdateaction-server-wmi-class.md index b424eebd6ae..c2f64686649 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_installupdateaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_installupdateaction-server-wmi-class.md @@ -116,7 +116,7 @@ Class SMS_TaskSequence_InstallUpdateAction : SMS_TaskSequence_Action - All. Install all software updates for the computers targeted by this task sequence action. - The task sequence variable associated with this property is SMSInstallUpdateTarget. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is SMSInstallUpdateTarget. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Timeout` Data type: `UInt32` diff --git a/sccm/develop/reference/osd/sms_tasksequence_joindomainworkgroupaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_joindomainworkgroupaction-server-wmi-class.md index 8e939ebf2c8..25f7b1aa8dc 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_joindomainworkgroupaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_joindomainworkgroupaction-server-wmi-class.md @@ -96,7 +96,7 @@ Class SMS_TaskSequence_JoinDomainWorkgroupAction : SMS_TaskSequence_Action Password of the account specified by `DomainUsername`. Set this property if the `Type` property is set to 0. - The task sequence variable associated with this property is OSDJoinPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDJoinPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `DomainPassword` might be required to disjoin from the computer's domain. @@ -109,7 +109,7 @@ Class SMS_TaskSequence_JoinDomainWorkgroupAction : SMS_TaskSequence_Action Account that should be used by the target computer to join a Windows domain, with appropriate domain join rights. Set this property if the `Type` property is set to 0. - The task sequence variable associated with this property is OSDJoinAccount. For more information, see [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDJoinAccount. For more information, see [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `DomainUserName` may be required to disjoin from the computer's domain. @@ -174,7 +174,7 @@ Class SMS_TaskSequence_JoinDomainWorkgroupAction : SMS_TaskSequence_Action |0|Domain| |1|Workgroup| - The task sequence variable associated with this property is OSDJoinType. For more information, see [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDJoinType. For more information, see [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `WorkgroupName` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_prepareosaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_prepareosaction-server-wmi-class.md index 3154d522352..3e9af4dc8a7 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_prepareosaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_prepareosaction-server-wmi-class.md @@ -46,7 +46,7 @@ Class SMS_TaskSequence_PrepareOSAction : SMS_TaskSequence_Action `true` to build a mass-storage device driver list. The default value is `false`. - The task sequence variable associated with this property is OSDBuildStorageDriverList. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDBuildStorageDriverList. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Condition` Data type: `SMS_TaskSequence_Condition` @@ -93,7 +93,7 @@ Class SMS_TaskSequence_PrepareOSAction : SMS_TaskSequence_Action `true` to keep the current product activation flag or reset it. The default value is `false`. - The task sequence variable associated with this property is OSDKeepActivation. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDKeepActivation. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Name` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_rebootaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_rebootaction-server-wmi-class.md index 0b163f13045..aa50f896734 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_rebootaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_rebootaction-server-wmi-class.md @@ -92,7 +92,7 @@ Class SMS_TaskSequence_RebootAction : SMS_TaskSequence_Action The number of seconds that a user-defined message is displayed to the user before the computer restarts. Specify 0 seconds (default) to indicate that no reboot message should be displayed. - The task sequence variable that is associated with this property is SMSRebootTimeout. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable that is associated with this property is SMSRebootTimeout. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Name` Data type: `String` diff --git a/sccm/develop/reference/osd/sms_tasksequence_restoreuserstateaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_restoreuserstateaction-server-wmi-class.md index 30e3aa8bf0b..e5a74fbd90e 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_restoreuserstateaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_restoreuserstateaction-server-wmi-class.md @@ -78,7 +78,7 @@ Class SMS_TaskSequence_RestoreUserStateAction : SMS_TaskSequence_Action `true` (default) if user state restoration should continue even if some files cannot be restored. - The task sequence variable associated with this property is OSDMigrateContinueOnRestore. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateContinueOnRestore. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Description` Data type: `String` @@ -116,7 +116,7 @@ Class SMS_TaskSequence_RestoreUserStateAction : SMS_TaskSequence_Action Password for the local user account to reset for restored local user profiles. - The task sequence variable associated with this property is OSDMigrateLocalAccountPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateLocalAccountPassword. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `LocalAccounts` Data type: `Boolean` @@ -127,7 +127,7 @@ Class SMS_TaskSequence_RestoreUserStateAction : SMS_TaskSequence_Action `true` to restore the local computer account. The default value is `false`. - The task sequence variable associated with this property is OSDMigrateLocalAccounts. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is OSDMigrateLocalAccounts. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Mode` Data type: `String` @@ -178,7 +178,7 @@ Class SMS_TaskSequence_RestoreUserStateAction : SMS_TaskSequence_Action ID of the task sequence package containing the USMT program. - The task sequence variable associated with this property is _OSDMigrateUsmtRestorePackageID. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is _OSDMigrateUsmtRestorePackageID. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). ## Remarks Class qualifiers for this class include: diff --git a/sccm/develop/reference/osd/sms_tasksequence_runcommandlineaction-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_runcommandlineaction-server-wmi-class.md index 035cce9fd87..ff2d3c04036 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_runcommandlineaction-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_runcommandlineaction-server-wmi-class.md @@ -88,7 +88,7 @@ Class SMS_TaskSequence_RunCommandLineAction : SMS_TaskSequence_Action `true` if the execution engine disables Wow64 file redirection and 64-bit registry redirection when the task sequence is evaluating file, folder, and registry conditions on a 64-bit operating system. The default value is `false`. - The task sequence variable associated with this property is SMSTSDisableWow64Redirection. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + The task sequence variable associated with this property is SMSTSDisableWow64Redirection. For more information, see the MSDN documentation for [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). `Enabled` Data type: `Boolean` diff --git a/sccm/develop/reference/osd/sms_tasksequence_variableconditionexpression-server-wmi-class.md b/sccm/develop/reference/osd/sms_tasksequence_variableconditionexpression-server-wmi-class.md index 2de04e3d039..185cb750e54 100644 --- a/sccm/develop/reference/osd/sms_tasksequence_variableconditionexpression-server-wmi-class.md +++ b/sccm/develop/reference/osd/sms_tasksequence_variableconditionexpression-server-wmi-class.md @@ -85,7 +85,7 @@ Class SMS_TaskSequence_VariableConditionExpression : SMS_TaskSequence_ConditionE `Value` - false - For more information about task sequence variables, see [Operating System Deployment Task Sequence Variables](http://go.microsoft.com/fwlink/?LinkId=100711). + For more information about task sequence variables, see [Operating System Deployment Task Sequence Variables](https://go.microsoft.com/fwlink/?LinkId=100711). ## Requirements diff --git a/sccm/develop/sum/how-to-configure-the-wsus-settings.md b/sccm/develop/sum/how-to-configure-the-wsus-settings.md index 26f40e6fcab..b0f94153ff9 100644 --- a/sccm/develop/sum/how-to-configure-the-wsus-settings.md +++ b/sccm/develop/sum/how-to-configure-the-wsus-settings.md @@ -28,7 +28,7 @@ You configure the Windows Server Update Services (WSUS) component settings, in S The following example method configures various Windows Server Update Services (WSUS) component settings by using the [SMS_SCI_Component](../../develop/reference/core/servers/configure/sms_sci_component-server-wmi-class.md) class to connect to the site control file and change properties. > [!NOTE] -> For configuration related information and values, see the Configuring Software Updates section of the System Center Configuration Manager documentation at [http://go.microsoft.com/fwlink/?LinkId=111682](http://go.microsoft.com/fwlink/?LinkId=111682). +> For configuration related information and values, see the Configuring Software Updates section of the System Center Configuration Manager documentation at [https://go.microsoft.com/fwlink/?LinkId=111682](https://go.microsoft.com/fwlink/?LinkId=111682). For information about calling the sample code, see [Calling Configuration Manager Code Snippets](../../develop/core/understand/calling-code-snippets.md). diff --git a/sccm/mdm/deploy-use/configure-intune-subscription.md b/sccm/mdm/deploy-use/configure-intune-subscription.md index a959af9cf73..a4427fbe786 100644 --- a/sccm/mdm/deploy-use/configure-intune-subscription.md +++ b/sccm/mdm/deploy-use/configure-intune-subscription.md @@ -29,7 +29,7 @@ The Intune subscription does the following: ## To create the Microsoft Intune subscription -1. If you haven't already, sign up for a Microsoft Intune account at [Microsoft Intune](http://go.microsoft.com/fwlink/?LinkID=258216). After creating your Intune account, you do not need to add any users to the Intune account or perform additional settings configurations. +1. If you haven't already, sign up for a Microsoft Intune account at [Microsoft Intune](https://go.microsoft.com/fwlink/?LinkID=258216). After creating your Intune account, you do not need to add any users to the Intune account or perform additional settings configurations. 2. In the Configuration Manager console, click **Administration**. diff --git a/sccm/mdm/deploy-use/confirm-dns.md b/sccm/mdm/deploy-use/confirm-dns.md index 2f683f2b73c..e041fc7dcd7 100644 --- a/sccm/mdm/deploy-use/confirm-dns.md +++ b/sccm/mdm/deploy-use/confirm-dns.md @@ -28,14 +28,14 @@ If necessary, take the following steps to satisfy any dependencies external to C When you set up single sign-on, your users can sign in with their corporate credentials to access the services in Intune. For more information, see the following topics: - - [Prepare for single sign-on](http://go.microsoft.com/fwlink/?LinkID=271124) - - [Plan for and deploy AD FS 2.0 for use with single sign-on](http://go.microsoft.com/fwlink/?LinkID=271125) + - [Prepare for single sign-on](https://go.microsoft.com/fwlink/?LinkID=271124) + - [Plan for and deploy AD FS 2.0 for use with single sign-on](https://go.microsoft.com/fwlink/?LinkID=271125) 3. Deploy and configure directory synchronization. Directory synchronization lets you populate Intune with synchronized user accounts. The synchronized user accounts and security groups are added to Intune. Failure to enable Directory Synchronization is a common cause of devices not being able to enroll when setting up Configuration Manager MDM with Microsoft Intune. - For more information, see [Directory integration](http://go.microsoft.com/fwlink/?LinkID=271120) in the Active Directory documentation library. + For more information, see [Directory integration](https://go.microsoft.com/fwlink/?LinkID=271120) in the Active Directory documentation library. 4. Optional, not recommended: If you are not using Active Directory Federation Services, reset users' Microsoft Online passwords. diff --git a/sccm/mdm/deploy-use/create-configuration-items-for-windows-8.1-and-windows-10-devices-managed-without-the-client.md b/sccm/mdm/deploy-use/create-configuration-items-for-windows-8.1-and-windows-10-devices-managed-without-the-client.md index a80b405ce95..e0383437df6 100644 --- a/sccm/mdm/deploy-use/create-configuration-items-for-windows-8.1-and-windows-10-devices-managed-without-the-client.md +++ b/sccm/mdm/deploy-use/create-configuration-items-for-windows-8.1-and-windows-10-devices-managed-without-the-client.md @@ -320,7 +320,7 @@ On the **Allowed and Blocked Apps list** page, specify the following information |-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Blocked apps list** | Select this option if you want to specify a list of apps that users are not allowed to install. | | **Allowed apps list** | Select this option if you want to specify a list of apps that users are allowed to install. Any other apps are blocked from installing. | -| **Add** | Adds an app to the selected list. Specify a name of your choice, optionally the app publisher, and the URL to the app in the app store.

To specify the URL, from the Windows Store, search for the app you want to use.

Open the app’s page, and copy the URL to the clipboard. You can now use this as the URL in either the allowed or blocked apps list.

**Example:** Search the store for the **Skype** app. The URL you use is ****. | +| **Add** | Adds an app to the selected list. Specify a name of your choice, optionally the app publisher, and the URL to the app in the app store.

To specify the URL, from the Windows Store, search for the app you want to use.

Open the app’s page, and copy the URL to the clipboard. You can now use this as the URL in either the allowed or blocked apps list.

**Example:** Search the store for the **Skype** app. The URL you use is ****. | | **Edit** | Let’s you edit the name, publisher and URL of the selected app. | | **Remove** | Deletes the selected app from the list. | | **Import** | Imports a list of apps you have specified in a comma-separated values file. Use the format, application name, publisher, app URL in the file. | diff --git a/sccm/mdm/deploy-use/create-configuration-items-for-windows-phone-devices-managed-without-the-client.md b/sccm/mdm/deploy-use/create-configuration-items-for-windows-phone-devices-managed-without-the-client.md index e74102e1ce5..cfcbf27d916 100644 --- a/sccm/mdm/deploy-use/create-configuration-items-for-windows-phone-devices-managed-without-the-client.md +++ b/sccm/mdm/deploy-use/create-configuration-items-for-windows-phone-devices-managed-without-the-client.md @@ -289,7 +289,7 @@ Use the System Center Configuration Manager**Windows Phone** configuration item |Setting|More information| |**Blocked apps list**|Select this option if you want to specify a list of apps that users will not be allowed to install.| |**Allowed apps list**|Select this option if you want to specify a list of apps that users are allowed to install.| -|**Add**|Adds an app to the selected list. Specify a name of your choice, optionally the app publisher, and the URL to the app in the app store.

To specify the URL, from the Windows Phone Store page, search for the app you want to use.

**Example:** Search the store for the **Skype** app. The URL you use will be http://www.windowsphone.com/en-us/store/app/skype/c3f8e570-68b3-4d6a-bdbb-c0a3f4360a51.

For the company portal app, or line of business apps, you do not have to specify a full URL, only the app GUID.| +|**Add**|Adds an app to the selected list. Specify a name of your choice, optionally the app publisher, and the URL to the app in the app store.

To specify the URL, from the Windows Phone Store page, search for the app you want to use.

**Example:** Search the store for the **Skype** app. The URL you use will be https://www.windowsphone.com/en-us/store/app/skype/c3f8e570-68b3-4d6a-bdbb-c0a3f4360a51.

For the company portal app, or line of business apps, you do not have to specify a full URL, only the app GUID.| |**Edit**|Let’s you edit the name, publisher and URL of the selected app.| |**Remove**|Deletes the selected app from the list.| |**Import**|Imports a list of apps you have specified in a comma-separated values file. Use the format, application name, publisher, app URL in the file.| diff --git a/sccm/mdm/deploy-use/enroll-hybrid-windows.md b/sccm/mdm/deploy-use/enroll-hybrid-windows.md index 2f7423359a6..da6c04ebb0d 100644 --- a/sccm/mdm/deploy-use/enroll-hybrid-windows.md +++ b/sccm/mdm/deploy-use/enroll-hybrid-windows.md @@ -55,7 +55,7 @@ Two factors determine how you can simplify Windows device enrollment: Automatic enrollment lets users enroll either company-owned or personal Windows 10 PCs and Windows 10 mobile devices in Intune by adding a work or school account and agreeing to be managed. Simple as that. In the background, the user's device registers and joins Azure Active Directory. Once registered, the device is managed with Intune. **Prerequisites** -- Azure Active Directory Premium subscription ([trial subscription](http://go.microsoft.com/fwlink/?LinkID=816845)) +- Azure Active Directory Premium subscription ([trial subscription](https://go.microsoft.com/fwlink/?LinkID=816845)) - Microsoft Intune subscription diff --git a/sccm/mdm/deploy-use/import-pfx-certificate-profiles.md b/sccm/mdm/deploy-use/import-pfx-certificate-profiles.md index b26b41d90f6..92f1268bb70 100644 --- a/sccm/mdm/deploy-use/import-pfx-certificate-profiles.md +++ b/sccm/mdm/deploy-use/import-pfx-certificate-profiles.md @@ -33,7 +33,7 @@ To learn more, see [Certificate profile prerequisites](../../protect/plan-design System Center Configuration Manager allows you to import certificate credentials and then provision personal information exchange (.pfx) files to user devices. PFX files can be used to generate user-specific certificates to support encrypted data exchange. > [!TIP] -> A step-by-step walkthrough describing this process is available in [How to Create and Deploy PFX Certificate Profiles in Configuration Manager](http://blogs.technet.com/b/karanrustagi/archive/2015/09/01/how-to-create-and-deploy-pfx-certificate-profiles-in-configuration-manager.aspx). +> A step-by-step walkthrough describing this process is available in [How to Create and Deploy PFX Certificate Profiles in Configuration Manager](https://blogs.technet.com/b/karanrustagi/archive/2015/09/01/how-to-create-and-deploy-pfx-certificate-profiles-in-configuration-manager.aspx). ## Create, import, and deploy a Personal Information Exchange (PFX) certificate profile @@ -79,7 +79,7 @@ Imported certificates are later deployed to enrolled devices. ### Deploy a Create PFX Script -Use the [Configuration Manager SDK](http://go.microsoft.com/fwlink/?LinkId=613525) to deploy a Create PFX Script. +Use the [Configuration Manager SDK](https://go.microsoft.com/fwlink/?LinkId=613525) to deploy a Create PFX Script. The Create PFX Script added in Configuration Manager 2012 SP2 adds an SMS_ClientPfxCertificate class to the SDK. This class includes the following methods: diff --git a/sccm/mdm/deploy-use/ios-hybrid-enrollment-using-apple-configurator.md b/sccm/mdm/deploy-use/ios-hybrid-enrollment-using-apple-configurator.md index c96868ce270..060f698e9f7 100644 --- a/sccm/mdm/deploy-use/ios-hybrid-enrollment-using-apple-configurator.md +++ b/sccm/mdm/deploy-use/ios-hybrid-enrollment-using-apple-configurator.md @@ -26,7 +26,7 @@ The following procedure is recommended for dedicated iOS devices that will have - Device serial numbers - [How to get an iOS serial number](https://support.apple.com/en-us/HT204308) -- Mac computer with [Apple Configurator 2.0](http://go.microsoft.com/fwlink/?LinkId=518017) +- Mac computer with [Apple Configurator 2.0](https://go.microsoft.com/fwlink/?LinkId=518017) - USB cables for connecting devices to your Mac computer diff --git a/sccm/mdm/deploy-use/manage-mobile-devices-with-exchange-activesync.md b/sccm/mdm/deploy-use/manage-mobile-devices-with-exchange-activesync.md index 04c597dc4a5..71aed03126b 100644 --- a/sccm/mdm/deploy-use/manage-mobile-devices-with-exchange-activesync.md +++ b/sccm/mdm/deploy-use/manage-mobile-devices-with-exchange-activesync.md @@ -106,7 +106,7 @@ Use the Exchange Server connector in System Center Configuration Manager when yo - **Set-ActiveSyncOrganizationSettings** > [!NOTE] - > The following Exchange Server management roles include these cmdlets: Recipient Management, View-Only Organization Management, and Server Management. For more information about management role groups in Microsoft Exchange Server 2010, see [Understanding Management Role Groups](http://go.microsoft.com/fwlink/p/?LinkId=212914). + > The following Exchange Server management roles include these cmdlets: Recipient Management, View-Only Organization Management, and Server Management. For more information about management role groups in Microsoft Exchange Server 2010, see [Understanding Management Role Groups](https://go.microsoft.com/fwlink/p/?LinkId=212914). > [!TIP] > If you try to install or use the Exchange Server connector without the required cmdlets, you will see an error logged with the message `Invoking cmdlet failed` in the EasDisc.log file on the site server computer. diff --git a/sccm/mdm/deploy-use/protect-apps-using-mam-policies.md b/sccm/mdm/deploy-use/protect-apps-using-mam-policies.md index 877f1ae802a..9dd29d3a563 100644 --- a/sccm/mdm/deploy-use/protect-apps-using-mam-policies.md +++ b/sccm/mdm/deploy-use/protect-apps-using-mam-policies.md @@ -122,7 +122,7 @@ To apply restrictions to an app, the app must incorporate the Microsoft Intune A |**Require corporate credentials for access**|Requires that the user must enter their corporate sign-in information before they can access the app.| |**Require device compliance with corporate policy for access**|Allows the app to be used only when the device is not jailbroken or rooted.| |**Recheck the access requirements after (minutes)**|Specifies the time period before the access requirements for the app are rechecked after the app is launched (in the **Timeout** field).

In the **Offline grace period** field, if the device is offline, specifies the time period before the access requirements for the app are rechecked.| -|**Encrypt app data**|Specifies that all data that is associated with this app is encrypted, including data that's stored externally, such as data stored on SD cards.

**Encryption for iOS**

For apps that are associated with a Configuration Manager mobile application management policy, data is encrypted at rest using device-level encryption that's provided by the OS. This is enabled through a device PIN policy that must be set by the IT admin. When a PIN is required, the data is encrypted per the settings in the mobile application management policy. As stated in Apple documentation, [the modules that are used by iOS 7 are FIPS 140-2 certified](http://support.apple.com/en-us/HT202739).

**Encryption for Android**

For apps that are associated with a Configuration Manager mobile application management policy, encryption is provided by Microsoft. Data is encrypted synchronously during file I/O operations according to the setting in the mobile application management policy. Managed apps on Android use AES-128 encryption in CBC mode utilizing the platform cryptography libraries. The encryption method is not FIPS 140-2 certified. Content on the device storage is always encrypted.| +|**Encrypt app data**|Specifies that all data that is associated with this app is encrypted, including data that's stored externally, such as data stored on SD cards.

**Encryption for iOS**

For apps that are associated with a Configuration Manager mobile application management policy, data is encrypted at rest using device-level encryption that's provided by the OS. This is enabled through a device PIN policy that must be set by the IT admin. When a PIN is required, the data is encrypted per the settings in the mobile application management policy. As stated in Apple documentation, [the modules that are used by iOS 7 are FIPS 140-2 certified](https://support.apple.com/en-us/HT202739).

**Encryption for Android**

For apps that are associated with a Configuration Manager mobile application management policy, encryption is provided by Microsoft. Data is encrypted synchronously during file I/O operations according to the setting in the mobile application management policy. Managed apps on Android use AES-128 encryption in CBC mode utilizing the platform cryptography libraries. The encryption method is not FIPS 140-2 certified. Content on the device storage is always encrypted.| |**Block screen capture** (Android devices only)|Specifies that the screen capture capabilities of the device are blocked when using this app.| |**Disable contact sync**| Beginning with version 1710, this option prevents the app from saving data to the native Contacts app on the device. If you choose No, the app can save data to the native Contacts app on the device.| |**Disable printing**| Beginning with version 1710, this option prevents the app from printing work or school data. | diff --git a/sccm/mdm/deploy-use/set-up-your-subscription-with-lookout.md b/sccm/mdm/deploy-use/set-up-your-subscription-with-lookout.md index 176eec2c7be..ca7ae5da5f1 100644 --- a/sccm/mdm/deploy-use/set-up-your-subscription-with-lookout.md +++ b/sccm/mdm/deploy-use/set-up-your-subscription-with-lookout.md @@ -136,7 +136,7 @@ If you no longer want to receive email notifications, set the notifications to O ## Configure threat classification -Lookout mobile threat defense classifies mobile threats of various types. The [Lookout threat classifications](http://personal.support.lookout.com/hc/articles/114094130693) have default risk levels associated with them. These settings can be changed at any time to suit your company requirements. +Lookout mobile threat defense classifies mobile threats of various types. The [Lookout threat classifications](https://personal.support.lookout.com/hc/articles/114094130693) have default risk levels associated with them. These settings can be changed at any time to suit your company requirements. ![screenshot of the policy page showing threat and classifications](media/lookout-threat-classification.png) diff --git a/sccm/mdm/deploy-use/troubleshoot-lookout-integration.md b/sccm/mdm/deploy-use/troubleshoot-lookout-integration.md index bb65f34f78a..2c42f4317b5 100644 --- a/sccm/mdm/deploy-use/troubleshoot-lookout-integration.md +++ b/sccm/mdm/deploy-use/troubleshoot-lookout-integration.md @@ -25,7 +25,7 @@ Lookout MTP is configured to allow only users from a configured Azure AD group You can contact Lookout Support through on the following methods: * Email: enterprisesupport@lookout.com -* Login to the [MTP Console](http://aad.lookout.com), and navigate to the **Support** module. +* Login to the [MTP Console](https://aad.lookout.com), and navigate to the **Support** module. * Go to: https://enterprise.support.lookout.com/hc/requests and make a support request. ### Unable to sign in diff --git a/sccm/mdm/deploy-use/wipe-lock-reset-devices.md b/sccm/mdm/deploy-use/wipe-lock-reset-devices.md index 00abfd792c6..7f840dff364 100644 --- a/sccm/mdm/deploy-use/wipe-lock-reset-devices.md +++ b/sccm/mdm/deploy-use/wipe-lock-reset-devices.md @@ -159,7 +159,7 @@ The data and apps that EFS selective wipe currently supports are: - Work folders. -- Files and folders encrypted by EFS. For more information, see [Best practices for the Encrypting File System](http://support.microsoft.com/kb/223316). +- Files and folders encrypted by EFS. For more information, see [Best practices for the Encrypting File System](https://support.microsoft.com/kb/223316). ### Best practices for selective wipe diff --git a/sccm/mdm/get-started/set-up-certificates-on-premises-mdm.md b/sccm/mdm/get-started/set-up-certificates-on-premises-mdm.md index c73543f1c21..41bc9864098 100644 --- a/sccm/mdm/get-started/set-up-certificates-on-premises-mdm.md +++ b/sccm/mdm/get-started/set-up-certificates-on-premises-mdm.md @@ -25,7 +25,7 @@ System Center Configuration Manager On\-premises Mobile Device Management requir As an alternative for non-domain joined devices, you can use the root of a well-known public CA (like Verisign or GoDaddy) to issue the server certificate, which avoids having to manually install a certificate on the device, because most devices natively trust connections to servers using the same root of the public CA. This is a useful alternative for user-enrolled devices in which it is not feasible to install the certificates trusted through the site CA on each device. > [!IMPORTANT] -> There are many ways to set up the certificates for trusted communications between devices and the site system servers for On\-premises Mobile Device Management. The information provided in this article is given as an example of one way to do it. This method requires you to be running a server in your site with Active Directory Certificate Services role and the Certification Authority and Certification Authority Web Enrollment role services installed. See [Active Directory Certificate Services](http://go.microsoft.com/fwlink/p/?LinkId=115018) for more information and guidance on this Windows Server role. +> There are many ways to set up the certificates for trusted communications between devices and the site system servers for On\-premises Mobile Device Management. The information provided in this article is given as an example of one way to do it. This method requires you to be running a server in your site with Active Directory Certificate Services role and the Certification Authority and Certification Authority Web Enrollment role services installed. See [Active Directory Certificate Services](https://go.microsoft.com/fwlink/p/?LinkId=115018) for more information and guidance on this Windows Server role. To set up the Configuration Manager site for the SSL communications required for On\-premises Mobile Device Management, follow these high-level steps: diff --git a/sccm/mdm/understand/whats-new-hybrid-archive.md b/sccm/mdm/understand/whats-new-hybrid-archive.md index 5f4bf635fd2..24e657b7e70 100644 --- a/sccm/mdm/understand/whats-new-hybrid-archive.md +++ b/sccm/mdm/understand/whats-new-hybrid-archive.md @@ -154,7 +154,7 @@ The following additional hybrid features are also included in version 1702 of Co - **New MDM server address for Windows devices** - The MDM server address for enrolling Windows and Windows Phone devices has changed from manage.microsoft.com to enrollment.manage.microsoft.com. Notify your user to use enrollment.manage.microsoft.com as the MDM server address if prompted for it while enrolling a Windows or and Windows Phone device. This update also requires any CNAME in DNS that redirects EnterpriseEnrollment.contoso.com to manage.microsoft.com to be replaced with a CNAME in DNS that redirects EnterpriseEnrollment.contoso.com to EnterpriseEnrollment-s.manage.microsoft.com. For additional information about this change, visit http://aka.ms/intuneenrollsvrchange. + The MDM server address for enrolling Windows and Windows Phone devices has changed from manage.microsoft.com to enrollment.manage.microsoft.com. Notify your user to use enrollment.manage.microsoft.com as the MDM server address if prompted for it while enrolling a Windows or and Windows Phone device. This update also requires any CNAME in DNS that redirects EnterpriseEnrollment.contoso.com to manage.microsoft.com to be replaced with a CNAME in DNS that redirects EnterpriseEnrollment.contoso.com to EnterpriseEnrollment-s.manage.microsoft.com. For additional information about this change, visit https://aka.ms/intuneenrollsvrchange. ### New in Configuration Manager Technical Preview 1702 @@ -233,7 +233,7 @@ The following additional hybrid features are also included in version 1702 of Co Microsoft has released a new [Company Portal app for Windows 10 devices](https://www.microsoft.com/store/apps/9wzdncrfj3pz). This app, which leverages the new Windows 10 Universal format, provides an updated user experience that is identical across all Windows 10 devices, PC and Mobile alike, while still enabling all the same functionality provided by previous Company Portal apps. - The new app leverages platform features like single sign-on (SSO) and certificate-based authentication on Windows 10 devices. The app is available as an upgrade to the existing Windows 8.1 Company Portal and Windows Phone 8.1 Company Portal installs from the Windows Store. For more details, go to the [Intune Support Team Blog](http://aka.ms/intunecp_universalapp). + The new app leverages platform features like single sign-on (SSO) and certificate-based authentication on Windows 10 devices. The app is available as an upgrade to the existing Windows 8.1 Company Portal and Windows Phone 8.1 Company Portal installs from the Windows Store. For more details, go to the [Intune Support Team Blog](https://aka.ms/intunecp_universalapp). The new Company Portal app also displays any Windows Store for Business applications marked **Available** in the Configuration Manager console. @@ -369,7 +369,7 @@ The following new feature introduced in September 2016 is available for hybrid d - **iOS 10 support** - If you have profiles or configuration items targeted to all iOS platforms, these will also be pushed to iOS 10. We’ve also released an update to Configuration Manager version 1606 that allows you to target profiles and configuration items to individual iOS platforms including iOS 10. You can install the update with the Configuration Manager admin console at **Administration > Overview > Cloud Services > Updates and Servicing**. You can find more information about the update at [http://support.microsoft.com/kb/3192616](http://support.microsoft.com/kb/3192616). + If you have profiles or configuration items targeted to all iOS platforms, these will also be pushed to iOS 10. We’ve also released an update to Configuration Manager version 1606 that allows you to target profiles and configuration items to individual iOS platforms including iOS 10. You can install the update with the Configuration Manager admin console at **Administration > Overview > Cloud Services > Updates and Servicing**. You can find more information about the update at [https://support.microsoft.com/kb/3192616](https://support.microsoft.com/kb/3192616). ## August 2016 @@ -542,7 +542,7 @@ No new hybrid features have been introduced in June 2016 for Configuration Manag - **New apps available for management with MAM policies** - The Microsoft Word, Excel, and PowerPoint apps for Android can now be associated with MAM policies on devices that are not enrolled with Intune. For a full list of supported apps, go the Microsoft Intune mobile application gallery on the [Microsoft Intune application partners](https://www.microsoft.com/en-us/server-cloud/products/microsoft-intune/partners.aspx) page. + The Microsoft Word, Excel, and PowerPoint apps for Android can now be associated with MAM policies on devices that are not enrolled with Intune. For a full list of supported apps, go the Microsoft Intune mobile application gallery on the [Microsoft Intune application partners](https://www.microsoft.com/server-cloud/products/microsoft-intune/partners.aspx) page. - **Android Company portal app: End user toast notifications** @@ -570,7 +570,7 @@ No new hybrid features have been introduced in June 2016 for Configuration Manag - **Windows Store for Business apps** - The [Windows Store for Business](https://www.microsoft.com/en-us/business-store) is where you can find and purchase apps for your organization, individually or in volume. By connecting the store to Configuration Manager, you can manage volume-purchased apps from the Configuration Manager console. For more information, see [Windows Store for Business apps](/sccm/core/get-started/capabilities-in-technical-preview-1605#BKMK_WSFB) in [Capabilities in Technical Preview 1605 for System Center Configuration Manager](/sccm/core/get-started/capabilities-in-technical-preview-1605). + The [Windows Store for Business](https://www.microsoft.com/business-store) is where you can find and purchase apps for your organization, individually or in volume. By connecting the store to Configuration Manager, you can manage volume-purchased apps from the Configuration Manager console. For more information, see [Windows Store for Business apps](/sccm/core/get-started/capabilities-in-technical-preview-1605#BKMK_WSFB) in [Capabilities in Technical Preview 1605 for System Center Configuration Manager](/sccm/core/get-started/capabilities-in-technical-preview-1605). - **General improvements for volume-purchased apps** diff --git a/sccm/mdt/samples-guide.md b/sccm/mdt/samples-guide.md index 68639da3e40..d1e60289545 100644 --- a/sccm/mdt/samples-guide.md +++ b/sccm/mdt/samples-guide.md @@ -1164,7 +1164,7 @@ SkipSummary=YES Powerusers001=WOODGROVEBANK\PilarA CaptureGroups=YES SLShare=\\WDG-MDT-01\UserData$\Logs -Home_page=http://www.microsoft.com/NewComputer +Home_page=https://www.microsoft.com/NewComputer ``` ## Calling Web Services in MDT diff --git a/sccm/mdt/sccm-guide.md b/sccm/mdt/sccm-guide.md index c0c2c67f1a9..44f8323379b 100644 --- a/sccm/mdt/sccm-guide.md +++ b/sccm/mdt/sccm-guide.md @@ -170,8 +170,8 @@ manager: dougeby |Windows 8.1 distribution files from the product media|E:\Source$\Windows_8-1| |Device drivers required for the reference and target computers (WDG-REF-01 and WDG-CLI-01)|E:\Source$\Drivers| |SQL Server 2008 R2 from the product media|E:\Source$\SQL2008R2| - |SQL Server 2008 R2 SP1, available at [http://www.microsoft.com/download/details.aspx?id=26727](http://www.microsoft.com/download/details.aspx?id=26727)|E:\Source$\SQL2008R2SP1| - |SQL Server 2008 R2 SP1 CU6, available at [http://support.microsoft.com/kb/2679367](http://support.microsoft.com/kb/2679367)|E:\Source$\SQL2008R2SP1CU6| + |SQL Server 2008 R2 SP1, available at [https://www.microsoft.com/download/details.aspx?id=26727](https://www.microsoft.com/download/details.aspx?id=26727)|E:\Source$\SQL2008R2SP1| + |SQL Server 2008 R2 SP1 CU6, available at [https://support.microsoft.com/kb/2679367](https://support.microsoft.com/kb/2679367)|E:\Source$\SQL2008R2SP1CU6| |Configuration Manager from the product media|E:\Source$\ConfigMgr| ### Step 1-4: Install the AD DS Server Role diff --git a/sccm/mdt/toolkit-reference.md b/sccm/mdt/toolkit-reference.md index 3af65ce056d..7dd7cc3bbf3 100644 --- a/sccm/mdt/toolkit-reference.md +++ b/sccm/mdt/toolkit-reference.md @@ -137,7 +137,7 @@ manager: dougeby |None|None| #### Configure ADDS - This task sequence step configures the target computer as an Active Directory® Domain Services (AD DS) domain controller. For more information about the settings listed in the following tables and which this task sequence step can configure, see the Microsoft Help and Support article, [Unattended promotion and demotion of Windows 2000 and Windows Server 2003 domain controllers](http://support.microsoft.com/kb/223757). + This task sequence step configures the target computer as an Active Directory® Domain Services (AD DS) domain controller. For more information about the settings listed in the following tables and which this task sequence step can configure, see the Microsoft Help and Support article, [Unattended promotion and demotion of Windows 2000 and Windows Server 2003 domain controllers](https://support.microsoft.com/kb/223757). The unique properties and settings for the **Configure ADDS** task sequence step type are: @@ -257,7 +257,7 @@ manager: dougeby | **Name** | **Description** | |------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Orchestrator Server** | Type the URL for the Orchestrator web service, which includes the server name. The Orchestrator web service can use either Hypertext Transfer Protocol (HTTP) or HTTP over Secure Sockets Layer (HTTPS). The Orchestrator web service defaults to port 81.

The Orchestrator web service supports multiple runbook servers. By default, a runbook can run on any runbook server. A runbook can be configured to specify which runbook servers should be used to run the runbook.

Note:

The Orchestrator web service supports the ability to run a runbook on a specific runbook server. This feature is not supported in MDT.

Specify the URL in any of the following formats:

- ***servername***. When using this format, the URL defaults to:

`http://:81/Orchestrator2012/Orchestrator.svc`

- ***servername:port***. When using this format, the URL defaults to:

`http:///Orchestrator2012/Orchestrator.svc.`

- http://*servername:port. When using this format, the URL defaults to:

`http:///Orchestrator2012/Orchestrator.svc.`

- **http://servername:port. When using this format, the URL defaults to:

`https:///Orchestrator2012/Orchestrator.svc.`

- *http://*servername:port*/Orchestrator2012/Orchestrator.svc. When using this format, MDT assumes that you are providing the fully qualified URL, because the value ends with .svc.

- **https://servername:port/Orchestrator2012/Orchestrator.svc**. When using this format, MDT assumes that you are providing the fully qualified URL, because the value ends with .svc. | -| **Runbook** | Click **Browse**, and then select the name of the Orchestrator runbook that this task sequence should run.

Note:

To successfully browse for Orchestrator runbooks, install the [ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2](http://www.microsoft.com/download/details.aspx?displaylang=en&id=2343). | +| **Runbook** | Click **Browse**, and then select the name of the Orchestrator runbook that this task sequence should run.

Note:

To successfully browse for Orchestrator runbooks, install the [ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2](https://www.microsoft.com/download/details.aspx?displaylang=en&id=2343). | | **Automatically provide runbook parameters** | Select this option to automatically provide the Orchestrator runbook input parameter values( which assumes that the runbook parameter values are task sequence variables). For example, if a runbook has an input parameter named **OSDComputerName**, then the **OSDComputerName** task sequence variable value is passed to the runbook.

Note:

This option works only for input parameters that are valid task sequence variable names and do not contain spaces or other special characters. Although spaces and other special characters are supported as Orchestrator parameter names, they are not valid task sequence variable names. If you need to pass values to parameters with spaces or other special characters, use the **Specify explicit runbook parameters** option.

The other option is **Specify explicit runbook parameters**.

Note:

The values provided for the runbook input parameters to the Orchestrator web service are formatted as XML. Passing values that contain data that is or resembles XML-formatted data may cause errors. | | **Specify explicit runbook parameters** | Select this option to explicitly provide the Orchestrator runbook input parameters.

You must configure the following settings for each input parameter that the Orchestrator runbook requires:

- **Name**. This is the name of the input runbook parameter.

Note:

If you change the parameters for an existing Orchestrator runbook, you need to browse (reselect) for the runbook again, because MDT only retrieves the parameter list when initially adding the Orchestrator runbook.

- **Value**. This can be a constant or a variable, such as a task sequence variable or an environment variable. For example, you can specify a value of **%OSDComputerName%**, which will pass the value of the **OSDComputerName** task sequence variable to the runbook input parameter. | | **Wait for the runbook to finish before continuing** | This check box controls whether the task sequence step will wait for the runbook to finish before proceeding to the next task sequence step.

If this check box is:

- **Selected**, then the task sequence step will wait for the runbook to finish before proceeding on to the next task sequence step.

When this check box is selected, the task sequence step will poll the Orchestrator web service for the runbook to finish. The amount of time between polls starts at 1 second, then increases to 2, 4, 8, 16, 32, and 64 seconds between each poll. Once the amount of time reaches 64 seconds, the task sequence step continues to poll every 64 seconds.

- **Cleared**, then the task sequence step will not wait for the runbook to finish before proceeding to the next task sequence step.

Note:

This check box must be selected if the runbook returns output parameters. | @@ -9493,7 +9493,7 @@ Table 4 lists the Windows operating systems that MDT supports and their correspo ### ZTIAuthorizeDHCP.wsf This script uses the Netsh tool to configure the target computer so that it is an authorized DHCP server in AD DS. - For more information about authorizing DHCP servers, see [How to Use Netsh.exe to Authorize, Unauthorize and List DHCP Servers in Active Directory](http://support.microsoft.com/kb/303351). + For more information about authorizing DHCP servers, see [How to Use Netsh.exe to Authorize, Unauthorize and List DHCP Servers in Active Directory](https://support.microsoft.com/kb/303351). |**Value**|**Description**| |-|-| @@ -10994,9 +10994,9 @@ Table 4 lists the Windows operating systems that MDT supports and their correspo Obtain the latest version of the WUA stand-alone installer for: -- x86 versions (WindowsUpdateAgent30-x86.exe) at [http://go.microsoft.com/fwlink/?LinkID=100334](http://go.microsoft.com/fwlink/?LinkID=100334) +- x86 versions (WindowsUpdateAgent30-x86.exe) at [https://go.microsoft.com/fwlink/?LinkID=100334](https://go.microsoft.com/fwlink/?LinkID=100334) -- x64 version (WindowsUpdateAgent30-x64.exe) at [http://go.microsoft.com/fwlink/?LinkID=100335](http://go.microsoft.com/fwlink/?LinkID=100335) +- x64 version (WindowsUpdateAgent30-x64.exe) at [https://go.microsoft.com/fwlink/?LinkID=100335](https://go.microsoft.com/fwlink/?LinkID=100335) Windows 7 and later include the most recent version of WUA, so no upgrade is necessary. @@ -14001,7 +14001,7 @@ Update-MDTMedia -Path "DS001:\Media\MEDIA001" - [Windows Presentation Foundation](https://msdn.microsoft.com/library/ms754130.aspx) version 4.0 -- [Microsoft Prism](http://compositewpf.codeplex.com/) version 4.0 +- [Microsoft Prism](https://compositewpf.codeplex.com/) version 4.0 - [Microsoft Unity Application Block](http://unity.codeplex.com/) (Unity) version 2.1 diff --git a/sccm/mdt/troubleshooting-reference.md b/sccm/mdt/troubleshooting-reference.md index 3b1a682712d..bb5539dffe4 100644 --- a/sccm/mdt/troubleshooting-reference.md +++ b/sccm/mdt/troubleshooting-reference.md @@ -19,12 +19,12 @@ manager: dougeby > In this document, *Windows* applies to the Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 operating systems unless otherwise noted. MDT does not support ARM processor–based versions of Windows. Similarly, *MDT* refers to MDT 2013 unless otherwise stated. > [!NOTE] -> The Microsoft Diagnostics and Recovery Toolset (DaRT) contains powerful tools for recovering and troubleshooting client computers that do not start or have become unstable. You can use DaRT to determine the cause of a crash, restore lost files, and so on. You can also use DaRT as a troubleshooting tool when developing and deploying a Windows operating system. For example, if a built image fails to start correctly, you can start the client computer containing the image by using ERD Commander—a diagnostic environment. Then, you can explore the client computer’s hard disk, view the event log, remove updates, change operating system settings, and so on. DaRT is part of the Microsoft Desktop Optimization Pack for Software Assurance. To learn more about DaRT, see [http://www.microsoft.com/windows/enterprise/products-and-technologies/mdop/dart.aspx](http://www.microsoft.com/windows/enterprise/products-and-technologies/mdop/dart.aspx). +> The Microsoft Diagnostics and Recovery Toolset (DaRT) contains powerful tools for recovering and troubleshooting client computers that do not start or have become unstable. You can use DaRT to determine the cause of a crash, restore lost files, and so on. You can also use DaRT as a troubleshooting tool when developing and deploying a Windows operating system. For example, if a built image fails to start correctly, you can start the client computer containing the image by using ERD Commander—a diagnostic environment. Then, you can explore the client computer’s hard disk, view the event log, remove updates, change operating system settings, and so on. DaRT is part of the Microsoft Desktop Optimization Pack for Software Assurance. To learn more about DaRT, see [https://www.microsoft.com/windows/enterprise/products-and-technologies/mdop/dart.aspx](https://www.microsoft.com/windows/enterprise/products-and-technologies/mdop/dart.aspx). ## Understanding Logs Before effective troubleshooting of MDT can begin, you must have a clear understanding of the many .log files used during an operating system deployment. When you know which log files to research for what failure condition and at what time, issues that were once mysterious and difficult to understand may become clear and understandable. - The MDT log file format is designed to be read by Trace32, which is part of the System Center Configuration Manager 2007 Toolkit V2, available for download from the [Microsoft Download Center](http://www.microsoft.com/download/details.aspx?id=9257). The logs can also be read by the Configuration Manager Trace Log Tool (CMTrace) that is available with System Center 2012 Configuration Manager and later versions. Use these tools whenever possible to read the log files, because it makes finding errors much easier. + The MDT log file format is designed to be read by Trace32, which is part of the System Center Configuration Manager 2007 Toolkit V2, available for download from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=9257). The logs can also be read by the Configuration Manager Trace Log Tool (CMTrace) that is available with System Center 2012 Configuration Manager and later versions. Use these tools whenever possible to read the log files, because it makes finding errors much easier. The rest of this section details the log files created during deployment as well as during Windows Setup. This section also provides examples of when to use the files for troubleshooting. @@ -271,7 +271,7 @@ The action "Zero Touch Installation - Validation" failed with exit code 5001 This information indicates that a networking problem may exist on the target computer or between the target computer and the server on which the deployment share resides. These problems might include network drivers not being installed properly or a mismatch in speed and duplex settings. - **Possible Solution 2:** Use the Microsoft Exchange Server Error Code Look-up utility. This command-line utility is valuable in assisting with error code translation. It is available for download from the [Microsoft Download Center](http://www.microsoft.com/download/details.aspx?id=985). + **Possible Solution 2:** Use the Microsoft Exchange Server Error Code Look-up utility. This command-line utility is valuable in assisting with error code translation. It is available for download from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=985). ### Review of Sample Logs MDT creates log files that you can use to troubleshoot problems in the MDT deployment process. The following sections provide examples of how to use the MDT log files to troubleshoot the deployment process: @@ -387,7 +387,7 @@ Figure 2. NTFS data streams #### Blocked SQL Server Browser Requests **Problem:** During the MDT deployment process, information can be retrieved from Microsoft SQL Server® databases. However, errors might be generated that relate to an improperly configured firewall on the database server. - **Possible Solution:** The Windows Firewall in Windows Server helps prevent unauthorized access to computer resources. However, if the firewall is configured incorrectly, attempts to connect to a SQL Server instance may be blocked. To access an instance of SQL Server that is behind the firewall, configure the firewall on the computer that is running SQL Server. For more information on configuring firewall ports for SQL Server, see the Microsoft Support article [How do I open the firewall port for SQL Server on Windows Server 2008?](http://support.microsoft.com/kb/968872) + **Possible Solution:** The Windows Firewall in Windows Server helps prevent unauthorized access to computer resources. However, if the firewall is configured incorrectly, attempts to connect to a SQL Server instance may be blocked. To access an instance of SQL Server that is behind the firewall, configure the firewall on the computer that is running SQL Server. For more information on configuring firewall ports for SQL Server, see the Microsoft Support article [How do I open the firewall port for SQL Server on Windows Server 2008?](https://support.microsoft.com/kb/968872) #### Named Pipe Connections **Problem:** During the MDT deployment process, information can be retrieved from SQL Server databases. However, errors might be generated that relate to broken SQL Server connections. These can be caused by not enabling named pipe connections in Microsoft SQL Server. @@ -435,7 +435,7 @@ Figure 2. NTFS data streams 13. Close the SQL Server Configuration Manager console. - For additional information, [How to enable remote connections in SQL Server 2008](http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx). + For additional information, [How to enable remote connections in SQL Server 2008](https://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx). ##### Enable Named Pipe Connections in SQL Server 2005 To enable named pipe connections in SQL Server 2005, perform the following steps: @@ -462,7 +462,7 @@ Figure 2. NTFS data streams 9. Close SQL Server 2005 Surface Area Configuration. - For additional information, see the Microsoft Support article [How to configure SQL Server 2005 to allow remote connections](http://support.microsoft.com/kb/914277) + For additional information, see the Microsoft Support article [How to configure SQL Server 2005 to allow remote connections](https://support.microsoft.com/kb/914277) ### Deployment Scripts Review MDT\-related problems and solutions: @@ -599,7 +599,7 @@ Figure 2. NTFS data streams The second phase of this protocol takes place between the client computer and a boot server and uses the DHCP message format as a convenient format for communication. This second phase is otherwise unrelated to the standard DHCP services. The next few pages outline the step\-by\-step process during PXE client computer initialization. - For more information on troubleshooting PXE boot\-related issues in Windows Deployment Services running in Legacy or Mixed mode, see the Microsoft Support article [Description of PXE Interaction Among PXE Client, DHCP, and RIS Server](http://support.microsoft.com/kb/244036). + For more information on troubleshooting PXE boot\-related issues in Windows Deployment Services running in Legacy or Mixed mode, see the Microsoft Support article [Description of PXE Interaction Among PXE Client, DHCP, and RIS Server](https://support.microsoft.com/kb/244036). Review the following solutions for PXE boot issues: @@ -955,7 +955,7 @@ ERROR - Unable to create ADODB.Connection object, impossible to query SQL Server ### Microsoft Support Microsoft provides Premier and Professional level support for Microsoft Deployment Toolkit. - Professional level support: [http://support.microsoft.com/](http://support.microsoft.com/) + Professional level support: [https://support.microsoft.com/](https://support.microsoft.com/) Premier level support: [https://premier.microsoft.com/](https://premier.microsoft.com/) @@ -967,22 +967,22 @@ ERROR - Unable to create ADODB.Connection object, impossible to query SQL Server - Microsoft-hosted blogs - - [MDT Team blog](http://blogs.technet.com/b/msdeployment/) + - [MDT Team blog](https://blogs.technet.com/b/msdeployment/) - - [Configuration Manager Team blog](http://blogs.technet.com/b/configmgrteam/) + - [Configuration Manager Team blog](https://blogs.technet.com/b/configmgrteam/) - - [Michael Niehaus’ blog](http://blogs.technet.com/b/mniehaus/) (Michael Niehaus writes on Windows and Microsoft Office deployment.) + - [Michael Niehaus’ blog](https://blogs.technet.com/b/mniehaus/) (Michael Niehaus writes on Windows and Microsoft Office deployment.) - Microsoft-hosted newsgroups and forums: The following newsgroups and forums are available with support from Microsoft employees, industry peers, and Microsoft Valued Professionals: - - [Configuration Manager - Operating System Deployment](http://social.technet.microsoft.com/Forums/home?forum=configmanagerosd) + - [Configuration Manager - Operating System Deployment](https://social.technet.microsoft.com/Forums/home?forum=configmanagerosd) - - [Windows 8 Installation, Setup, and Deployment](http://social.technet.microsoft.com/Forums/windows/home?forum=w8itproinstall) + - [Windows 8 Installation, Setup, and Deployment](https://social.technet.microsoft.com/Forums/windows/home?forum=w8itproinstall) - Deployment-related information sources from outside Microsoft: - [DeployVista.com](http://www.deployvista.com/) - - [myITforum.com](http://www.myitforum.com/) + - [myITforum.com](https://www.myitforum.com/) diff --git a/sccm/mdt/user-driven-installation-developers-guide.md b/sccm/mdt/user-driven-installation-developers-guide.md index 8b1d75d57b3..63a5c91c891 100644 --- a/sccm/mdt/user-driven-installation-developers-guide.md +++ b/sccm/mdt/user-driven-installation-developers-guide.md @@ -57,7 +57,7 @@ Figure 1. Relationship between the UDI Wizard and UDI Wizard Designer - [WPF](https://msdn.microsoft.com/library/ms754130.aspx) version 4.0 - - [Microsoft Prism](http://compositewpf.codeplex.com/) version 4.0 + - [Microsoft Prism](https://compositewpf.codeplex.com/) version 4.0 - [Microsoft Unity Application Block](http://unity.codeplex.com/) (Unity) version 2.1 diff --git a/sccm/mdt/user-driven-installation-guide.md b/sccm/mdt/user-driven-installation-guide.md index 020ce4d544c..324f97bba35 100644 --- a/sccm/mdt/user-driven-installation-guide.md +++ b/sccm/mdt/user-driven-installation-guide.md @@ -183,8 +183,8 @@ manager: dougeby |Windows 8.1 distribution files from the product media|E:\Source$\Windows_8-1| |Device drivers required for the reference and target computers (WDG-REF-01 and WDG-CLI-01)|E:\Source$\Drivers| |SQL Server 2008 R2 from the product media|E:\Source$\SQL2008| -|SQL Server 2008 R2 SP1, available at [http://www.microsoft.com/download/en/details.aspx?id=26727](http://www.microsoft.com/download/en/details.aspx?id=26727)|E:\Source$\SQL2008R2SP1| -|SQL Server 2008 R2 SP1 CU6, available at [http://support.microsoft.com/kb/2679367](http://support.microsoft.com/kb/2679367)|E:\Source$\SQL2008R2SP1CU6| +|SQL Server 2008 R2 SP1, available at [https://www.microsoft.com/download/en/details.aspx?id=26727](https://www.microsoft.com/download/en/details.aspx?id=26727)|E:\Source$\SQL2008R2SP1| +|SQL Server 2008 R2 SP1 CU6, available at [https://support.microsoft.com/kb/2679367](https://support.microsoft.com/kb/2679367)|E:\Source$\SQL2008R2SP1CU6| |System Center 2012 R2 Configuration Manager from the product media|E:\Source$\ConfigMgr| |Office Professional Plus 2010 32-bit Volume Licensing version from the product media|E:\ Source$\OfficeProPlus2010| diff --git a/sccm/osd/deploy-use/deploy-windows-to-go.md b/sccm/osd/deploy-use/deploy-windows-to-go.md index c2680ff7e34..8c07326d421 100644 --- a/sccm/osd/deploy-use/deploy-windows-to-go.md +++ b/sccm/osd/deploy-use/deploy-windows-to-go.md @@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management This topic provides the steps to provision Windows To Go in System Center Configuration Manager. Windows To Go is an enterprise feature of Windows 8 that enables the creation of a Windows To Go workspace that can be booted from a USB-connected external drive on computers that meet the Windows 7 or Windows 8 certification requirements, regardless of the operating system running on the computer. Windows To Go workspaces can use the same image enterprises use for their desktops and laptops and can be managed the same way. - For more information about Windows To Go, see [Windows To Go feature overview](http://go.microsoft.com/fwlink/p/?LinkId=263433). + For more information about Windows To Go, see [Windows To Go feature overview](https://go.microsoft.com/fwlink/p/?LinkId=263433). ## Provision Windows To Go Windows To Go is an operating system stored on a USB-connected external drive. You can provision the Windows To Go drive much like you provision other operating system deployments. However, because Windows To Go is designed to be a user-centric and highly mobile solution, you must take a slightly different approach to provisioning these drives. diff --git a/sccm/osd/deploy-use/upgrade-windows-to-the-latest-version.md b/sccm/osd/deploy-use/upgrade-windows-to-the-latest-version.md index 00471eb093a..b46f2d641ec 100644 --- a/sccm/osd/deploy-use/upgrade-windows-to-the-latest-version.md +++ b/sccm/osd/deploy-use/upgrade-windows-to-the-latest-version.md @@ -60,7 +60,7 @@ For more information, see [Windows 10 upgrade paths](https://docs.microsoft.com/ - An earlier version of Windows Server 2016 - An earlier version of Windows Server 2019 -For more information about Windows Server supported upgrade paths, see [Windows Server 2016 supported upgrade paths](https://docs.microsoft.com/windows-server/get-started/supported-upgrade-paths#upgrading-previous-retail-versions-of-windows-server-to-windows-server-2016) and [Windows Server Upgrade Center](http://aka.ms/upgradecenter). +For more information about Windows Server supported upgrade paths, see [Windows Server 2016 supported upgrade paths](https://docs.microsoft.com/windows-server/get-started/supported-upgrade-paths#upgrading-previous-retail-versions-of-windows-server-to-windows-server-2016) and [Windows Server Upgrade Center](https://aka.ms/upgradecenter). ## Plan diff --git a/sccm/osd/get-started/customize-boot-images.md b/sccm/osd/get-started/customize-boot-images.md index 4c9ae841f57..34b4a209f28 100644 --- a/sccm/osd/get-started/customize-boot-images.md +++ b/sccm/osd/get-started/customize-boot-images.md @@ -32,7 +32,7 @@ Each version of Configuration Manager supports a specific version of the Windows Windows PE 3.11 and Windows PE 5 - 1 You can only add a boot image to Configuration Manager when it is based on Windows PE 3.1. Install the Windows AIK Supplement for Windows 7 SP1 to upgrade Windows AIK for Windows 7 (based on Windows PE 3) with the Windows AIK Supplement for Windows 7 SP1 (based on Windows PE 3.1). You can download Windows AIK Supplement for Windows 7 SP1 from the [Microsoft Download Center](http://www.microsoft.com/download/details.aspx?id=5188). + 1 You can only add a boot image to Configuration Manager when it is based on Windows PE 3.1. Install the Windows AIK Supplement for Windows 7 SP1 to upgrade Windows AIK for Windows 7 (based on Windows PE 3) with the Windows AIK Supplement for Windows 7 SP1 (based on Windows PE 3.1). You can download Windows AIK Supplement for Windows 7 SP1 from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=5188). For example, when you have Configuration Manager, you can customize boot images from Windows ADK for Windows 10 (based on Windows PE 10) from the Configuration Manager console. However, while boot images based on Windows PE 5 are supported, you must customize them from a different computer and use the version of DISM that is installed with Windows ADK for Windows 8. Then, you can add the boot image to the Configuration Manager console. @@ -60,7 +60,7 @@ Each version of Configuration Manager supports a specific version of the Windows 1. Install the Windows ADK on a computer that does not have another version of Windows AIK or Windows ADK, and does not have any Configuration Manager components installed. -2. Download Windows ADK for Windows 8.1 from the [Microsoft Download Center](http://www.microsoft.com/download/details.aspx?id=39982). +2. Download Windows ADK for Windows 8.1 from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=39982). 3. Copy the boot image (wimpe.wim) from the Windows ADK installation folder (for example, <*Installation path*>\Windows Kits\\<*version*>\Assessment and Deployment Kit\Windows Preinstallation Environment\\<*x86 or amd64*>\\<*locale*>) to a destination folder on the computer from which you will customize the boot image. This procedure uses C:\WinPEWAIK as the destination folder name. @@ -180,9 +180,9 @@ Each version of Configuration Manager supports a specific version of the Windows #### To customize a boot image that uses Windows PE 3.1 -1. Install the Windows AIK on a computer that does not have another version of Windows AIK or Windows ADK, and does not have any Configuration Manager components installed. Download Windows AIK from the [Microsoft Download Center](http://www.microsoft.com/download/details.aspx?id=5753). +1. Install the Windows AIK on a computer that does not have another version of Windows AIK or Windows ADK, and does not have any Configuration Manager components installed. Download Windows AIK from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=5753). -2. Install the Windows AIK Supplement for Windows 7 with SP1 on the computer from step 1. Download Windows AIK Supplement for Windows 7 SP1 from the [Microsoft Download Center](http://www.microsoft.com/download/details.aspx?id=5188). +2. Install the Windows AIK Supplement for Windows 7 with SP1 on the computer from step 1. Download Windows AIK Supplement for Windows 7 SP1 from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=5188). 3. Copy the boot image (wimpe.wim) from the Windows AIK installation folder (for example, <*InstallationPath*>\Windows AIK\Tools\PETools\amd64\\) to a folder on the computer from which you will customize the boot image. This procedure uses C:\WinPEWAIK as the folder name. diff --git a/sccm/osd/get-started/customize-operating-system-images.md b/sccm/osd/get-started/customize-operating-system-images.md index 6e7113a9226..2220d62f831 100644 --- a/sccm/osd/get-started/customize-operating-system-images.md +++ b/sccm/osd/get-started/customize-operating-system-images.md @@ -90,7 +90,7 @@ Operating system images in System Center Configuration Manager are WIM files and > [!IMPORTANT] > The [Prepare Windows for Capture](../understand/task-sequence-steps.md#BKMK_PrepareWindowsforCapture) task sequence step attempts to reset the local administrator password on the reference computer to a blank value before Sysprep runs. If the Local Security policy **Password must meet complexity requirements** is enabled, this task sequence step fails to reset the administrator password. In this scenario, disable this policy before you run the task sequence. - For more information about Sysprep, see [System Preparation (Sysprep) Technical Reference](http://go.microsoft.com/fwlink/?LinkId=280286). + For more information about Sysprep, see [System Preparation (Sysprep) Technical Reference](https://go.microsoft.com/fwlink/?LinkId=280286). - **Appropriate tools and scripts required to mitigate installation scenarios** diff --git a/sccm/protect/deploy-use/certificate-infrastructure.md b/sccm/protect/deploy-use/certificate-infrastructure.md index 98dd3820db3..c8e5ad81f1d 100644 --- a/sccm/protect/deploy-use/certificate-infrastructure.md +++ b/sccm/protect/deploy-use/certificate-infrastructure.md @@ -30,7 +30,7 @@ Use these steps to configure your infrastructure for SCEP, or PFX certificates. ### To install and configure the Network Device Enrollment Service and dependencies -1. On a server that is running Windows Server 2012 R2, install and configure the Network Device Enrollment Service role service for the Active Directory Certificate Services server role. For more information, see [Network Device Enrollment Service Guidance](http://go.microsoft.com/fwlink/p/?LinkId=309016) in the Active Directory Certificate Services library on TechNet. +1. On a server that is running Windows Server 2012 R2, install and configure the Network Device Enrollment Service role service for the Active Directory Certificate Services server role. For more information, see [Network Device Enrollment Service Guidance](https://go.microsoft.com/fwlink/p/?LinkId=309016) in the Active Directory Certificate Services library on TechNet. 2. Check, and if necessary, modify the security permissions for the certificate templates that the Network Device Enrollment Service is using: @@ -40,7 +40,7 @@ Use these steps to configure your infrastructure for SCEP, or PFX certificates. - For the SCEP Service account that the Network Device Enrollment Service application pool uses: **Read** and **Enroll** permissions. - This requirement is not specific to System Center Configuration Manager but is part of configuring the Network Device Enrollment Service. For more information, see [Network Device Enrollment Service Guidance](http://go.microsoft.com/fwlink/p/?LinkId=309016) in the Active Directory Certificate Services library on TechNet. + This requirement is not specific to System Center Configuration Manager but is part of configuring the Network Device Enrollment Service. For more information, see [Network Device Enrollment Service Guidance](https://go.microsoft.com/fwlink/p/?LinkId=309016) in the Active Directory Certificate Services library on TechNet. > [!TIP] > To identify which certificate templates the Network Device Enrollment Service is using, view the following registry key on the server that is running the Network Device Enrollment Service: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MSCEP. @@ -65,7 +65,7 @@ Use these steps to configure your infrastructure for SCEP, or PFX certificates. - Set the **MaxRequestBytes** key to **16777216**. - For more information, see article [820129: Http.sys registry settings for Windows](http://go.microsoft.com/fwlink/?LinkId=309013) in the Microsoft Knowledge Base. + For more information, see article [820129: Http.sys registry settings for Windows](https://go.microsoft.com/fwlink/?LinkId=309013) in the Microsoft Knowledge Base. 6. On the same server, in Internet Information Services (IIS) Manager, modify the request-filtering settings for the /certsrv/mscep application, and then restart the server. In the **Edit Request Filtering Settings** dialog box, the **Request Limits** settings should be as follows: @@ -75,7 +75,7 @@ Use these steps to configure your infrastructure for SCEP, or PFX certificates. - **Maximum query string (Bytes)**: **65534** - For more information about these settings and how to configure them, see [Requests Limits](http://go.microsoft.com/fwlink/?LinkId=309014) in the IIS Reference Library. + For more information about these settings and how to configure them, see [Requests Limits](https://go.microsoft.com/fwlink/?LinkId=309014) in the IIS Reference Library. 7. If you want to be able to request a certificate that has a lower validity period than the certificate template that you are using: This configuration is disabled by default for an enterprise CA. To enable this option on an enterprise CA, use the Certutil command-line tool, and then stop and restart the certificate service by using the following commands: @@ -85,7 +85,7 @@ Use these steps to configure your infrastructure for SCEP, or PFX certificates. 3. **net start certsvc** - For more information, see [Certificate Services Tools and Settings](http://go.microsoft.com/fwlink/p/?LinkId=309015) in the PKI Technologies library on TechNet. + For more information, see [Certificate Services Tools and Settings](https://go.microsoft.com/fwlink/p/?LinkId=309015) in the PKI Technologies library on TechNet. 8. Verify that the Network Device Enrollment Service is working by using the following link as an example: **https://server.contoso.com/certsrv/mscep/mscep.dll**. You should see the built-in Network Device Enrollment Service webpage. This webpage explains what the service is and explains that network devices use the URL to submit certificate requests. diff --git a/sccm/protect/deploy-use/create-windows-firewall-policies.md b/sccm/protect/deploy-use/create-windows-firewall-policies.md index 03f2dab93d5..bf8df82effe 100644 --- a/sccm/protect/deploy-use/create-windows-firewall-policies.md +++ b/sccm/protect/deploy-use/create-windows-firewall-policies.md @@ -35,7 +35,7 @@ Firewall policies for Endpoint Protection in System Center Configuration Manager 5. On the **Profile Settings** page of the wizard, configure the following settings for each network profile: > [!IMPORTANT] - > If you want to deploy Windows Firewall policies to computers running Windows Server 2008 and Windows Vista Service Pack 1, you must first install [Hotfix KB971800](http://go.microsoft.com/fwlink/p/?LinkId=231239) on these computers. + > If you want to deploy Windows Firewall policies to computers running Windows Server 2008 and Windows Vista Service Pack 1, you must first install [Hotfix KB971800](https://go.microsoft.com/fwlink/p/?LinkId=231239) on these computers. > [!NOTE] > For more information about network profiles, see the Windows documentation. diff --git a/sccm/protect/deploy-use/endpoint-definitions-wsus.md b/sccm/protect/deploy-use/endpoint-definitions-wsus.md index d983ad997e2..d7ce70eb623 100644 --- a/sccm/protect/deploy-use/endpoint-definitions-wsus.md +++ b/sccm/protect/deploy-use/endpoint-definitions-wsus.md @@ -87,7 +87,7 @@ ms.collection: M365-identity-device-management 10. In the **Automatic Approvals** dialog box, select the check box for the newly created rule and then click **Run rule**. > [!NOTE] -> To maximize performance on your WSUS server and client computers, decline old definition updates. To accomplish this task, you can configure automatic approval for revisions and automatic declining of expired updates. For more information, see [Microsoft Knowledge Base article 938947](http://go.microsoft.com/fwlink/p/?LinkId=204078). +> To maximize performance on your WSUS server and client computers, decline old definition updates. To accomplish this task, you can configure automatic approval for revisions and automatic declining of expired updates. For more information, see [Microsoft Knowledge Base article 938947](https://go.microsoft.com/fwlink/p/?LinkId=204078). > > [!div class="button"] > [Next step >](endpoint-antimalware-policies.md) diff --git a/sccm/protect/deploy-use/endpoint-protection-client-faq.md b/sccm/protect/deploy-use/endpoint-protection-client-faq.md index 9a8a6afd5e6..c9b722c2362 100644 --- a/sccm/protect/deploy-use/endpoint-protection-client-faq.md +++ b/sccm/protect/deploy-use/endpoint-protection-client-faq.md @@ -140,7 +140,7 @@ To remove all unwanted or potentially harmful items that Windows Defender detect - Make sure your antivirus and antispyware software, Windows Defender, is using the latest updates again potential threats (see How do I keep virus and spyware definitions up to date?). Also make sure you're always using the latest version of Windows Defender. -- Only download updates from reputable sources. For Windows operating systems, always go to [Microsoft Update](http://go.microsoft.com/fwlink/?LinkID=96304) (http://go.microsoft.com/fwlink/?LinkID=96304) and for other software always use the legitimate websites of the company or person who produces it. +- Only download updates from reputable sources. For Windows operating systems, always go to [Microsoft Update](https://go.microsoft.com/fwlink/?LinkID=96304) (https://go.microsoft.com/fwlink/?LinkID=96304) and for other software always use the legitimate websites of the company or person who produces it. - If you receive an e-mail with an attachment and you're unsure of the source, then you should delete it immediately. Don't download any applications or files from unknown sources, and be careful when trading files with other users. diff --git a/sccm/protect/deploy-use/find-a-pfn-for-per-app-vpn.md b/sccm/protect/deploy-use/find-a-pfn-for-per-app-vpn.md index 0e8a311289f..9291994216e 100644 --- a/sccm/protect/deploy-use/find-a-pfn-for-per-app-vpn.md +++ b/sccm/protect/deploy-use/find-a-pfn-for-per-app-vpn.md @@ -65,11 +65,11 @@ Here is the information retrieved for OneNote: ## Find a PFN if the app is not installed on a computer -1. Go to https://www.microsoft.com/en-us/store/apps +1. Go to https://www.microsoft.com/store/apps 2. Enter the name of the app in the search bar. In our example, search for OneNote. 3. Click the link to the app. Note that the URL that you access has a series of letters at the end. In our example, the URL looks like this: -`https://www.microsoft.com/en-us/store/apps/onenote/9wzdncrfhvjl` -4. In a different tab, paste the following URL, `https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products//applockerdata`, replacing `` with the app id you obtained from https://www.microsoft.com/en-us/store/apps - that series of letters at the end of the URL in step 3. In our example, example of OneNote, you'd paste: `https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfhvjl/applockerdata`. +`https://www.microsoft.com/store/apps/onenote/9wzdncrfhvjl` +4. In a different tab, paste the following URL, `https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products//applockerdata`, replacing `` with the app id you obtained from https://www.microsoft.com/store/apps - that series of letters at the end of the URL in step 3. In our example, example of OneNote, you'd paste: `https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfhvjl/applockerdata`. In Edge, the information you want is displayed; in Internet Explorer, click **Open** to see the information. The PFN value is given on the first line. Here's how the results look for our example: diff --git a/sccm/protect/deploy-use/introduction-to-certificate-profiles.md b/sccm/protect/deploy-use/introduction-to-certificate-profiles.md index 82017776b6e..c6bcbc1d857 100644 --- a/sccm/protect/deploy-use/introduction-to-certificate-profiles.md +++ b/sccm/protect/deploy-use/introduction-to-certificate-profiles.md @@ -60,7 +60,7 @@ To deploy certificate profiles that use SCEP, install the certificate registrati PFX certificates also require a certificate registration point. Also specify the certificate authority (CA) for the certificate and the relevant access credentials. Starting with version 1706, you may specify either Microsoft or Entrust as certificate authorities. -For more information about how the Network Device Enrollment Service supports a policy module so that Configuration Manager can deploy certificates, see [Using a Policy Module with the Network Device Enrollment Service](http://go.microsoft.com/fwlink/p/?LinkId=328657). +For more information about how the Network Device Enrollment Service supports a policy module so that Configuration Manager can deploy certificates, see [Using a Policy Module with the Network Device Enrollment Service](https://go.microsoft.com/fwlink/p/?LinkId=328657). Depending on the requirements, Configuration Manager supports deploying certificates to different certificate stores on various device types and operating systems. The following devices and operating systems are supported: diff --git a/sccm/protect/deploy-use/troubleshoot-endpoint-client.md b/sccm/protect/deploy-use/troubleshoot-endpoint-client.md index a73c9d73d6e..324c34908a4 100644 --- a/sccm/protect/deploy-use/troubleshoot-endpoint-client.md +++ b/sccm/protect/deploy-use/troubleshoot-endpoint-client.md @@ -90,7 +90,7 @@ If you encounter problems with Windows Defender or Endpoint Protection, contact 2. If the error message that you received contains the code 0x80072f8f, the problem is most likely caused by an incorrect date or time setting on your computer. -3. To reset your computer's date or time setting, follow the steps in [Fix broken desktop shortcuts and common system maintenance tasks](http://go.microsoft.com/fwlink/?LinkId=155579) (http://go.microsoft.com/fwlink/?LinkId=155579). +3. To reset your computer's date or time setting, follow the steps in [Fix broken desktop shortcuts and common system maintenance tasks](https://go.microsoft.com/fwlink/?LinkId=155579) (https://go.microsoft.com/fwlink/?LinkId=155579). ### Step 4: Rename the Software Distribution folder on your computer diff --git a/sccm/protect/deploy-use/windows-defender-advanced-threat-protection.md b/sccm/protect/deploy-use/windows-defender-advanced-threat-protection.md index cdb73911f78..45b42d7b5aa 100644 --- a/sccm/protect/deploy-use/windows-defender-advanced-threat-protection.md +++ b/sccm/protect/deploy-use/windows-defender-advanced-threat-protection.md @@ -16,7 +16,7 @@ ms.collection: M365-identity-device-management *Applies to: System Center Configuration Manager (Current Branch)* -Starting with version 1606 of Configuration Manager (current branch), Endpoint Protection can help manage and monitor [Microsoft Defender Advanced Threat Protection (ATP)](http://aka.ms/technet-wdatp) (formerly known as Windows Defender ATP). Microsoft Defender ATP helps enterprises detect, investigate, and respond to advanced attacks on their networks. Configuration Manager or Microsoft Intune policies can help you onboard and monitor managed Windows 10, version 1607 (build 14328) or later. +Starting with version 1606 of Configuration Manager (current branch), Endpoint Protection can help manage and monitor [Microsoft Defender Advanced Threat Protection (ATP)](https://aka.ms/technet-wdatp) (formerly known as Windows Defender ATP). Microsoft Defender ATP helps enterprises detect, investigate, and respond to advanced attacks on their networks. Configuration Manager or Microsoft Intune policies can help you onboard and monitor managed Windows 10, version 1607 (build 14328) or later. Microsoft Defender ATP is a service in the [Windows Defender Security Center](https://securitycenter.windows.com). By adding and deploying a client onboarding configuration file, Configuration Manager can monitor deployment status and Microsoft Defender ATP agent health. Microsoft Defender ATP is supported on PCs running the Configuration Manager client or managed by Microsoft Intune, but Intune hybrid MDM-managed computers are not supported. diff --git a/sccm/protect/plan-design/prerequisites-for-certificate-profiles.md b/sccm/protect/plan-design/prerequisites-for-certificate-profiles.md index 492d3e6a2bd..fe2fc785b81 100644 --- a/sccm/protect/plan-design/prerequisites-for-certificate-profiles.md +++ b/sccm/protect/plan-design/prerequisites-for-certificate-profiles.md @@ -23,10 +23,10 @@ Certificate profiles in System Center Configuration Manager have external depend |Dependency|More information| |----------------|----------------------| -|An enterprise issuing certification authority (CA) that is running Active Directory Certificate Services (AD CS).

To revoke certificates the computer account of the site server at the top of the hierarchy requires *Issue and Manage Certificates* rights for each certificate template used by a certificate profile in Configuration Manager. Alternatively, grant Certificate Manager permissions to grant permissions on all certificate templates used by that CA

Manager approval for certificate requests is supported. However, the certificate templates that are used to issue certificates must be configured for **Supply in the request** for the certificate subject so that System Center Configuration Manager can automatically supply this value.|For more information about Active Directory Certificate Services, see your Windows Server documentation.

For Windows Server 2012: [Active Directory Certificate Services Overview](http://go.microsoft.com/fwlink/p/?LinkId=286744)

For Windows Server 2008: [Active Directory Certificate Services in Windows Server 2008](http://go.microsoft.com/fwlink/p/?LinkId=115018)| +|An enterprise issuing certification authority (CA) that is running Active Directory Certificate Services (AD CS).

To revoke certificates the computer account of the site server at the top of the hierarchy requires *Issue and Manage Certificates* rights for each certificate template used by a certificate profile in Configuration Manager. Alternatively, grant Certificate Manager permissions to grant permissions on all certificate templates used by that CA

Manager approval for certificate requests is supported. However, the certificate templates that are used to issue certificates must be configured for **Supply in the request** for the certificate subject so that System Center Configuration Manager can automatically supply this value.|For more information about Active Directory Certificate Services, see your Windows Server documentation.

For Windows Server 2012: [Active Directory Certificate Services Overview](https://go.microsoft.com/fwlink/p/?LinkId=286744)

For Windows Server 2008: [Active Directory Certificate Services in Windows Server 2008](https://go.microsoft.com/fwlink/p/?LinkId=115018)| |Use the PowerShell script to verify, and if needed, install the prerequisites for the Network Device Enrollment Service (NDES) role service and the Configuration Manager Certificate Registration Point.

|The instruction file, readme_crp.txt, is located in ConfigMgrInstallDir\cd.latest\SMSSETUP\POLICYMODULE\X64.

The PowerShell script, Test-NDES-CRP-Prereqs.ps1, is in the same directory as the instructions.

The PowerShell script must be run locally on the NDES server.| -|The Network Device Enrollment Service (NDES) role service for Active Directory Certificate Services, running on Windows Server 2012 R2.

In addition:

Port numbers other than TCP 443 (for HTTPS) or TCP 80 (for HTTP) are not supported for the communication between the client and the Network Device Enrollment Service.

The server that is running the Network Device Enrollment Service must be on a different server from the issuing CA.|System Center Configuration Manager communicates with the Network Device Enrollment Service in Windows Server 2012 R2 to generate and verify Simple Certificate Enrollment Protocol (SCEP) requests.

If you will issue certificates to users or devices that connect from the Internet, such as mobile devices that are managed by Microsoft Intune, those devices must be able to access the server that runs the Network Device Enrollment Service from the Internet. For example, install the server in a perimeter network (also known as a DMZ, demilitarized zone, and screened subnet).

If you have a firewall between the server that is running the Network Device Enrollment Service and the issuing CA, you must configure the firewall to allow the communication traffic (DCOM) between the two servers. This firewall requirement also applies to the server running the System Center Configuration Manager site server and the issuing CA, so that System Center Configuration Manager can revoke certificates.

If the Network Device Enrollment Service is configured to require SSL, a security best practice is to make sure that connecting devices can access the certificate revocation list (CRL) to validate the server certificate.

For more information about the Network Device Enrollment Service in Windows Server 2012 R2, see [Using a Policy Module with the Network Device Enrollment Service](http://go.microsoft.com/fwlink/p/?LinkId=328657).| -|If the issuing CA runs Windows Server 2008 R2, this server requires a hotfix for SCEP renewal requests.|If the hotfix is not already installed on the issuing CA computer, install the hotfix. For more information, see article [2483564: Renewal request for an SCEP certificate fails in Windows Server 2008 R2 if the certificate is managed by using NDES](http://go.microsoft.com/fwlink/?LinkId=311945) in the Microsoft Knowledge Base.| +|The Network Device Enrollment Service (NDES) role service for Active Directory Certificate Services, running on Windows Server 2012 R2.

In addition:

Port numbers other than TCP 443 (for HTTPS) or TCP 80 (for HTTP) are not supported for the communication between the client and the Network Device Enrollment Service.

The server that is running the Network Device Enrollment Service must be on a different server from the issuing CA.|System Center Configuration Manager communicates with the Network Device Enrollment Service in Windows Server 2012 R2 to generate and verify Simple Certificate Enrollment Protocol (SCEP) requests.

If you will issue certificates to users or devices that connect from the Internet, such as mobile devices that are managed by Microsoft Intune, those devices must be able to access the server that runs the Network Device Enrollment Service from the Internet. For example, install the server in a perimeter network (also known as a DMZ, demilitarized zone, and screened subnet).

If you have a firewall between the server that is running the Network Device Enrollment Service and the issuing CA, you must configure the firewall to allow the communication traffic (DCOM) between the two servers. This firewall requirement also applies to the server running the System Center Configuration Manager site server and the issuing CA, so that System Center Configuration Manager can revoke certificates.

If the Network Device Enrollment Service is configured to require SSL, a security best practice is to make sure that connecting devices can access the certificate revocation list (CRL) to validate the server certificate.

For more information about the Network Device Enrollment Service in Windows Server 2012 R2, see [Using a Policy Module with the Network Device Enrollment Service](https://go.microsoft.com/fwlink/p/?LinkId=328657).| +|If the issuing CA runs Windows Server 2008 R2, this server requires a hotfix for SCEP renewal requests.|If the hotfix is not already installed on the issuing CA computer, install the hotfix. For more information, see article [2483564: Renewal request for an SCEP certificate fails in Windows Server 2008 R2 if the certificate is managed by using NDES](https://go.microsoft.com/fwlink/?LinkId=311945) in the Microsoft Knowledge Base.| |A PKI client authentication certificate and exported root CA certificate.|This certificate authenticates the server that is running the Network Device Enrollment Service to System Center Configuration Manager.

For more information, see [PKI certificate requirements for System Center Configuration Manager](../../core/plan-design/network/pki-certificate-requirements.md).| |Supported device operating systems.|You can deploy certificate profiles to devices that run iOS, Windows 8.1, Windows RT 8.1, Windows 10, and Android operating systems.| diff --git a/sccm/protect/plan-design/security-and-privacy-for-certificate-profiles.md b/sccm/protect/plan-design/security-and-privacy-for-certificate-profiles.md index a139cf390db..75c430f42f9 100644 --- a/sccm/protect/plan-design/security-and-privacy-for-certificate-profiles.md +++ b/sccm/protect/plan-design/security-and-privacy-for-certificate-profiles.md @@ -22,7 +22,7 @@ ms.collection: M365-identity-device-management |Security best practice|More information| |----------------------------|----------------------| -|Identify and follow any security best practices for the Network Device Enrollment Service, which includes configuring the Network Device Enrollment Service website in Internet Information Services (IIS) to require SSL and ignore client certificates.|See [Network Device Enrollment Service Guidance](http://go.microsoft.com/fwlink/p/?LinkId=309016) in the Active Directory Certificate Services library on TechNet.| +|Identify and follow any security best practices for the Network Device Enrollment Service, which includes configuring the Network Device Enrollment Service website in Internet Information Services (IIS) to require SSL and ignore client certificates.|See [Network Device Enrollment Service Guidance](https://go.microsoft.com/fwlink/p/?LinkId=309016) in the Active Directory Certificate Services library on TechNet.| |When you configure SCEP certificate profiles, choose the most secure options that devices and your infrastructure can support.|Identify, implement, and follow any security best practices that have been recommended for your devices and infrastructure.| |Manually specify user device affinity instead of allowing users to identify their primary device. In addition, do not enable usage-based configuration.|If you click the **Allow certificate enrollment only on the users primary device** option in a SCEP certificate profile, do not consider the information that is collected from users or from the device to be authoritative. If you deploy SCEP certificate profiles with this configuration and a trusted administrative user does not specify user device affinity, unauthorized users might receive elevated privileges and be granted certificates for authentication.

**Note:** If you do enable usage-based configuration, this information is collected by using state messages that are not secured by System Center Configuration Manager. To help mitigate this threat, use SMB signing or IPsec between client computers and the management point.| |Do not add Read and Enroll permissions for users to the certificate templates, or configure the certificate registration point to skip the certificate template check.|Although Configuration Manager supports the additional check if you add the security permissions of Read and Enroll for users, and you can configure the certificate registration point to skip this check if authentication is not possible, neither configuration is a security best practice. For more information, see [Planning for certificate template permissions for certificate profiles in System Center Configuration Manager](../../protect/plan-design/planning-for-certificate-template-permissions.md).| diff --git a/sccm/sum/deploy-use/manage-express-installation-files-for-windows-10-updates.md b/sccm/sum/deploy-use/manage-express-installation-files-for-windows-10-updates.md index 5dae0b9d6b6..2c8589e484c 100644 --- a/sccm/sum/deploy-use/manage-express-installation-files-for-windows-10-updates.md +++ b/sccm/sum/deploy-use/manage-express-installation-files-for-windows-10-updates.md @@ -21,7 +21,7 @@ To learn how to use Configuration Manager to manage update content to stay curre > [!IMPORTANT] -> The OS client support is available in Windows 10, version 1607, with an update to the Windows Update Agent. This update is included with the updates released on April 11, 2017. For more information about these updates, see [support article 4015217](http://support.microsoft.com/kb/4015217). Future updates leverage express for smaller downloads. Prior versions of Windows 10, and Windows 10 version 1607 without this update don't support express installation files. +> The OS client support is available in Windows 10, version 1607, with an update to the Windows Update Agent. This update is included with the updates released on April 11, 2017. For more information about these updates, see [support article 4015217](https://support.microsoft.com/kb/4015217). Future updates leverage express for smaller downloads. Prior versions of Windows 10, and Windows 10 version 1607 without this update don't support express installation files. ### Enable the site to download express installation files for Windows 10 updates diff --git a/sccm/sum/deploy-use/manage-office-365-proplus-updates.md b/sccm/sum/deploy-use/manage-office-365-proplus-updates.md index b617ff12d29..97d21d4b00e 100644 --- a/sccm/sum/deploy-use/manage-office-365-proplus-updates.md +++ b/sccm/sum/deploy-use/manage-office-365-proplus-updates.md @@ -42,8 +42,8 @@ For previous Configuration Manager versions, you must take the following steps t - The computer that runs the Office 365 Installer must have Internet access. - The user that runs the Office 365 Installer must have **Read** and **Write** access to the content location share provided in the wizard. - If you receive a 404 download error, copy the following files to the user %temp% folder: - - [releasehistory.xml](http://officecdn.microsoft.com/pr/wsus/releasehistory.cab) - - [o365client_32bit.xml](http://officecdn.microsoft.com/pr/wsus/ofl.cab) + - [releasehistory.xml](https://officecdn.microsoft.com/pr/wsus/releasehistory.cab) + - [o365client_32bit.xml](https://officecdn.microsoft.com/pr/wsus/ofl.cab) ### Deploy Office 365 apps using Configuration Manager version 1806 or higher: Starting in Configuration Manager 1806, the Office Customization Tool is integrated with the Office 365 Installer in the Configuration Manager console. When creating a deployment for Office 365, you can dynamically configure the latest Office manageability settings. @@ -242,7 +242,7 @@ To change the update channel after you enable Office 365 clients to receive upda > [!Note] > The Office 365 Installation Wizard was introduced in Configuration Manager version 1702 and provides an easy way to create Office 365 apps. -- [Download the Office 2016 Deployment Tool](http://aka.ms/ODT2016) from the Microsoft Download Center. +- [Download the Office 2016 Deployment Tool](https://aka.ms/ODT2016) from the Microsoft Download Center. - Review the [configuration options for the Office Deployment Tool](https://technet.microsoft.com/library/jj219426.aspx). You can create an application just as you would with any other application in Configuration Manager from **Software Library** > **Overview** > **Application Management** > **Applications**. For details, see [Create and deploy an application](/sccm/apps/get-started/create-and-deploy-an-application). diff --git a/sccm/sum/deploy-use/office-365-dashboard.md b/sccm/sum/deploy-use/office-365-dashboard.md index 3b0df8d69f8..b4aeaa057d5 100644 --- a/sccm/sum/deploy-use/office-365-dashboard.md +++ b/sccm/sum/deploy-use/office-365-dashboard.md @@ -70,7 +70,7 @@ By default, the scanning agent looks at the most recently used (MRU) files list - Macro-enabled Office file formats, such as Excel macro-enabled workbooks (.xlsm) or Word macro-enabled document (.docm) - Older Office formats that don't indicate whether there's macro content. For example, an Excel 97-2003 workbook (.xls). -If you need a more detailed evaluation, deploy the **Office Readiness Toolkit**. This tool analyzes the code within a macro file. It checks if there are any potential compatibility concerns. For example, the file uses a function that changed in a more recent version of Office. After you run the Office Readiness Toolkit, Configuration Manager can use its results. This additional data enhances the device readiness calculation. For more information, see [Use the Readiness Toolkit to assess application compatibility for Office 365 ProPlus](http://aka.ms/readinesstoolkit). +If you need a more detailed evaluation, deploy the **Office Readiness Toolkit**. This tool analyzes the code within a macro file. It checks if there are any potential compatibility concerns. For example, the file uses a function that changed in a more recent version of Office. After you run the Office Readiness Toolkit, Configuration Manager can use its results. This additional data enhances the device readiness calculation. For more information, see [Use the Readiness Toolkit to assess application compatibility for Office 365 ProPlus](https://aka.ms/readinesstoolkit). ## Office 365 ProPlus upgrade readiness dashboard diff --git a/sccm/sum/get-started/manage-settings-for-software-updates.md b/sccm/sum/get-started/manage-settings-for-software-updates.md index 49d6ed922de..ef6d39c31f0 100644 --- a/sccm/sum/get-started/manage-settings-for-software-updates.md +++ b/sccm/sum/get-started/manage-settings-for-software-updates.md @@ -36,7 +36,7 @@ There are specific group policy settings that are used by Windows Update Agent ( When the software update point is created for a site, clients receive a machine policy that provides the software update point server name and configures the **Specify intranet Microsoft update service location** local policy on the computer. The WUA retrieves the server name that is specified in the **Set the intranet update service for detecting updates** setting, and then it connects to this server when it scans for software updates compliance. When a domain policy is created for the **Specify intranet Microsoft update service location** setting, it overrides the local policy, and the WUA might connect to a server other than the software update point. If this happens, the client might scan for software update compliance based on different products, classifications, and languages. Therefore, you should not configure the Active Directory policy for client computers. ### Allow Signed Content from Intranet Microsoft Update Service Location group policy -You must enable the **Allow signed content from intranet Microsoft update service location** Group Policy setting before the WUA on computers will scan for software updates that were created and published with System Center Updates Publisher. When the policy setting is enabled, WUA will accept software updates that are received through an intranet location if the software updates are signed in the **Trusted Publishers** certificate store on the local computer. For more information about the Group Policy settings that are required for Updates Publisher, see [Updates Publisher 2011 Documentation Library](http://go.microsoft.com/fwlink/p/?LinkId=232476). +You must enable the **Allow signed content from intranet Microsoft update service location** Group Policy setting before the WUA on computers will scan for software updates that were created and published with System Center Updates Publisher. When the policy setting is enabled, WUA will accept software updates that are received through an intranet location if the software updates are signed in the **Trusted Publishers** certificate store on the local computer. For more information about the Group Policy settings that are required for Updates Publisher, see [Updates Publisher 2011 Documentation Library](https://go.microsoft.com/fwlink/p/?LinkId=232476). ### Automatic updates configuration Automatic Updates allows security updates and other important downloads to be received on client computers. Automatic Updates is configured through the **Configure Automatic Updates** Group Policy setting or through the Control Panel on the local computer. When Automatic Updates is enabled, client computers will receive update notifications and, depending on the configured settings, the client computers will download and install the required updates. When Automatic Updates coexists with software updates, each client computer might display notification icons and popup display notifications for the same update. Also, when a restart is required, each client computer might display a restart dialog box for the same update. diff --git a/sccm/sum/tools/updates-publisher.md b/sccm/sum/tools/updates-publisher.md index 0f7971218c8..04cafb8ce72 100644 --- a/sccm/sum/tools/updates-publisher.md +++ b/sccm/sum/tools/updates-publisher.md @@ -28,7 +28,7 @@ Using Updates Publisher, you can: After you publish updates to an update server, you can then use System Center Configuration Manager to detect and deploy those updates to your managed devices. > [!TIP] -> The previous version, [System Center Updates Publisher 2011](http://go.microsoft.com/fwlink/?LinkId=848111), remains in support. This updated version retains the same functionality, but supports additional operating systems, new features to simplify some tasks, and has an updated user interface. +> The previous version, [System Center Updates Publisher 2011](https://go.microsoft.com/fwlink/?LinkId=848111), remains in support. This updated version retains the same functionality, but supports additional operating systems, new features to simplify some tasks, and has an updated user interface. ## Workspaces When you open Updates Publisher, it defaults to the Overview node of the *Updates Workspace.* diff --git a/sccm/sum/understand/software-updates-introduction.md b/sccm/sum/understand/software-updates-introduction.md index 05886286683..cb3195605bd 100644 --- a/sccm/sum/understand/software-updates-introduction.md +++ b/sccm/sum/understand/software-updates-introduction.md @@ -270,7 +270,7 @@ For an example scenario that shows how you might deploy software updates in your For more information about how Configuration Manager manages embedded devices that use write filters, see [Planning for client deployment to Windows Embedded devices](../../core/clients/deploy/plan/planning-for-client-deployment-to-windows-embedded-devices.md). ## Extend software updates in Configuration Manager - Use System Center Updates Publisher to manage software updates that are not available from Microsoft Update. After you publish the software updates to the update server and synchronize the software updates in Configuration Manager, you can deploy the software updates to Configuration Manager clients. For more information about Updates Publisher, see [Updates Publisher 2011](http://go.microsoft.com/fwlink/p/?LinkId=252947). + Use System Center Updates Publisher to manage software updates that are not available from Microsoft Update. After you publish the software updates to the update server and synchronize the software updates in Configuration Manager, you can deploy the software updates to Configuration Manager clients. For more information about Updates Publisher, see [Updates Publisher 2011](https://go.microsoft.com/fwlink/p/?LinkId=252947). ## Next steps [Plan for software updates](../plan-design/plan-for-software-updates.md) diff --git a/template.md b/template.md index 6cb3f0e09cb..94fbaa8fdb2 100644 --- a/template.md +++ b/template.md @@ -204,7 +204,7 @@ This is an example of `in-line code`. ### Channel 9 - + ### Youtube