Today, we will discuss an easy way to set the bandwidth throttling end time using the Settings Catalog in Intune. As we know, the Settings Catalog is an essential feature in Intune, making policy creation easy and efficient. So here implementing a policy for Bandwidth Throttling End Time.
Bandwidth refers to the amount of data a network can transmit at once. The Bandwidth Throttling End Time is one of the policies associated with the Background Intelligent Transfer Service (BITS). In the process of bandwidth throttling, the end time helps administrators limit the amount of bandwidth that Background Intelligent Transfer Service.
It can use for file transfers during specified time intervals. This analysis discusses the bandwidth throttling end time policy. This policy enables administrators to establish an end time for bandwidth throttling of background transfers.
This policy setting does not affect foreground transfers. This policy is based on the 24-hour clock. In this post, let’s begin by setting the end time for bandwidth throttling through the settings catalog.
Table of Contents
What is the Importance of Bandwidth Throttling End Time?
This policy sets the end time for bandwidth throttling used by Background Intelligent Transfer Service (BITS) for background transfers. It doesn’t affect foreground transfers and uses a 24-hour clock.
You can set a bandwidth limit for specific times. For example, limit it to 10 Kbps from 8:00 AM to 5:00 PM and use all available bandwidth the rest of the day.
Easy Way to Set Bandwidth Throttling End Time – CSP Details
In the previous section, we discussed a brief overview of Bandwidth and Bandwidth Throttling End Time using the Settings Catalog via Intune. In this policy creation time, we have to aware about the CSP details that means Configuration Service Provider. This will allow the admins to configure different settings on devices. Each policy has different CSP details. You can check it for the CSP details of the Bandwidth Throttling End Time.
| Scope | Editions | Applicable OS |
|---|---|---|
| User (Not Applicable) | Pro | Windows 10, version 1809 [10.0.17763] and later |
| Device | Enerprise | |
| Education | ||
| Windows SE | ||
| loT Enterprise / loT Enterprise LTSC |
For Device: ./Device/Vendor/MSFT/Policy/Config/BITS/BandwidthThrottlingEndTime
- VPN Bandwidth Control via BITs Throttling for SCCM DP | Client
- How Predictive Bandwidth Harvesting Solves SCCM ConfigMgr WAN Issues
- How to Allow Adding Non Microsoft Accounts Manually Using Intune Setting Catalog
How it Works on Intune
Now, we will explore how to create these settings through Intune and examine the processes we have to deal with. First, we must log in to the Microsoft Intune Admin Center using our credentials.
- Navigate through Device> Configuration> Create (New Policy).
- In the Create Profile window Set platform as Windows 10 and later and the Profile type as Setting catalog.
Create Profile With Basics
Whenever we create a policy, it is essential to assign a proper name to it, as this will help us identify the policy later. Thus, we need to follow a few basic steps. First, we should set the name and description of the policy. I have added a name and a description for the policy, and you will notice that the platform field is automatically filled by default.
- After this, click on Next.
Configuration Settings- Settings Picker
The next section is about configuration settings, which are very important for adding settings to the policy. When you click on Configuration Settings, you will see a hyperlink labeled “Add Settings.” Click on this hyperlink, and a window titled Settings Picker window will appear. In this window, you can select a category; I chose the “BITS” category.
- After selecting the category, you will see a variety of settings available.
- I selected “Bandwidth Throttling End Time” policy.
After selecting the setting name, you can close the Settings Picker window. Now, you will be on the configuration settings page. Here, you can enter the end time, which is set to 17 by default. You can choose a time between 0 and 24. For example, if I set the end time to 15 hours, then click on the Next button.
- This policy specifies the bandwidth throttling end time that Background Intelligent Transfer Service (BITS) uses for background transfers.
- This policy setting does not affect foreground transfers.
- This policy is based on the 24-hour clock. Value type is integer.
- Default value is 17 (5 PM). Supported value range: 0 – 23You can specify a limit to use during a specific time interval and at all other times.
- For example, limit the use of network bandwidth to 10 Kbps from 8:00 A. M. to 5:00 P. M. , and use all available unused bandwidth the rest of the day’s hours.
- Using the three policies together (BandwidthThrottlingStartTime, BandwidthThrottlingEndTime, BandwidthThrottlingTransferRate), BITS will limit its bandwidth usage to the specified values. You can specify the limit in kilobits per second (Kbps).
- If you specify a value less than 2 kilobits, BITS will continue to use approximately 2 kilobits. To prevent BITS transfers from occurring, specify a limit of 0.
- If you disable or do not configure this policy setting, BITS uses all available unused bandwidth. Note: You should base the limit on the speed of the network link, not the computer’s network interface card (NIC).
- This policy setting does not affect peer caching transfers between peer computers (it does affect transfers from the origin server); the Limit the maximum network bandwidth used for Peercaching policy setting should be used for that purpose.
- Consider using this setting to prevent BITS transfers from competing for network bandwidth when the client computer has a fast network card (10Mbs), but is connected to the network via a slow link (56Kbs).
Note: The value type is an integer, with the default value set to 17 (5 PM). The supported range is 0 to 23.
Scope Tags
Next is the Scope Tag, The scope tag is a part of the policy creation process, allowing you to set the scope tag for the policy, this option is mandatory. So I skip this section and click on the Next.
Assignments
The next section is assignments, which is very important, Just like a configuration settings. We are creating a policy for specified groups, correct? This assignments section allows us to add groups to the policy. In the Included Groups section, there is an option to Add Group.
Click on that option, and you will see a list of suggested groups. You can either select a group from the suggestions or search for the specific group you want. After selecting the desired group, click “Next” to proceed.
Review + Create
The final stage is the Review + Create option. In this step, you can finalize the policy. This session includes all the details provided for the policy. You’ll be able to view the basic details, configuration details, platform details, and more.
After reviewing all the information, simply click the “Create” button. This action will help the policy creation process. Once you click Create, you will receive a notification confirming that the policy has been successfully created.
Monitor Status
Monitoring the status of policies is very important. It helps you understand whether a policy has been created or not. Typically, policy creation takes about 8 hours. As you may know, we can use the company portal’s sync option to achieve faster results.
After syncing you can check if a policy has been created, navigate to the Device> Configuration, search for the policy you created, and click on it. It will show you an overview of the policy’s status, you can check the the screenshot.
Client Side- Verification
To check the client side verification through the Event Viewer. Navigate to the Application and Service Logs: Microsoft > Windows >Select the Device Management Enterprise Diagnostics Provider. Click on “Admin” to view the number of events.
You can filter the logs based on the last hour or the last 12 hours to see the policy creation details. Look for Event ID 813, which provides information about policy creation.
- The Intune event ID 813 ensures that a string policy is applied to Windows 10 or 11 devices, showing the exact value of the enforced policy.
| Policy Details |
|---|
| MDM PolicyManager: Set policy int, Policy: (Bandwidth ThrottlingEndTime), Area: (BITS), EnrollmentID requesting merge: (B1E9301C-8666-412A-BA2F-3BF8A55BFA62), Current User: (Device), Int: (0xF), Enrollment Type: (0x6), Scope: (0x0). |
Need Further Assistance or Have Technical Questions?
Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Author
Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.