Just like with Windows Telemetry, you will need to assign this policy to a security group. After a while your devices will sync with Intune and configuration changes will be applied automatically.
It might take up to 48 hours for information to appear in the OMS portal. For this to work, Windows diagnostic data and data sharing also need to be enabled. You can find the Update compliance solution in the overview of the OMS portal.
Upon clicking the tile, you will be redirected to the Update Compliance workspace. Windows 10 devices is up to date on feature updates whenever it has the latest applicable feature update installed.
Feature updates are delivered more frequently than with previous Windows releases. Both Office ProPlus and Windows 10 updates will deliver their major updates semi-annually, around April and September. This approach makes patching simpler and reduces unexpected issues resulting from patching. Also read the comments below the Microsoft article. The article writes, and I quote:. There is no other information or error codes to work with.
I can imagine not everyone will or can update their articles as quick as Microsoft does and hope by leaving it here, it may still help someone troubleshoot this problem. Scope is dynamic. This value is set and controlled by the MDM server. On the device, you can confirm everything is working by checking your settings and registry. Your Windows Telemetry diagnostics data level is stored at:. Let your analytics be your guide here. In general, focus on posts that are backed by some good-looking metrics, such as:.
In addition to a metrics-driven selection approach, you should also consider content relevancy and trending topics. In fact, depending on your content strategy and marketing goals, updating content for the sake of these two variables may actually trump a metrics-driven approach from time to time.
For instance, we recently found that a lot of our prospects and customers were asking questions about local search. While we'd already published a post about this very topic, it had become a little outdated and buried on our blog. Rather than create a new post from scratch and risk rubbing Google the wrong way with duplicate content , we decided to update and republish that original post -- even thought our metrics may not have indicated it was a good target for updating.
Okay, once you've identified the posts you want to update, it's time to actually update them! Here are some best practices to consider. Rather than publishing an additional article on your blog -- which could result in a ding from search engines for duplicate content -- modify the original article. While you may be tempted to update the post's URL slug, it's important to keep the URL the same, even if your software automatically creates a redirect.
Redirects will remove some of the link value, so it's best to just keep it as is. If you feel compelled to update the post's title, try to avoid changing it drastically from the original. While the URL is more important to keep the same than the title, if you really need to change the title, do your best to keep your keywords in there. It's a great idea to add a little editor's note at the bottom of your updated post -- if for no other reason, then for transparency's sake.
This is particularly a good idea if your post has accumulated a lot of comments; your readers will be confused if the publish date is current, but there are comments from months or years ago. Here's an example of what we typically include at the end of our republished posts:. Review the post's meta description. Is it still accurate? Can you update it to make it a little catchier? Remember, meta descriptions don't affect the ranking of your content, but they can impact its clickthrough rate from search.
Make sure your meta description is both an accurate reflection of what's within the post, and enticing enough to get searchers to click through to your content from search results. By now, you should have an awesomely updated piece of content that's ready for publishing.
While the process of actually publishing your content will vary depending on the blogging software you use, I'm going to share some tips for doing it using HubSpot's Blogging tool. Okay -- maybe I got a little bit ahead of myself. Before you publish your new post, it's a good idea to create a record of the post's "before" stats. That way, you can compare it to the post's performance after you've republished it to understand how your update affected its overall performance. Over time, this might also give you a better idea about which posts are worth targeting for updates.
The following are the data and stats I keep track of before and after I republish:. Are you incorporating updated blog posts into your blogging strategy? Share your tips and experiences in the comments below. Originally published Sep 9, AM, updated February 01 Subscribe to Our Blog Stay up to date with the latest marketing, sales, and service tips and news. Thank You! You have been subscribed. Note: For the purposes of this blog, the last patch Tuesday was December I set the ApprovedStates property to NotApproved because I only want to see updates that are required by the clients that are not already approved for installation.
This will tell the filter to look for only updates that are required by the clients, but have not been installed yet. This works fine for us because these updates are new to us and because we only want those for the most recent patch Tuesday. First, I am going to show you the Administration Console and look at all updates that are required by the clients on the network since patch Tuesday.
This is shown in the image that follows. Note the number of updates 30 and some of the titles listed here. Although not all of the updates are listed in the image, I will show you a couple of methods that we can use to pull the exact same information by using Windows PowerShell!
This method, as you can probably tell, will allow us to view the number of updates that are returned by using the previously configured Update Scope. I am going to expand on this slightly by using another method similar to one I showed you yesterday for the Computer Target Scope. This will return a little more information about the updates, as you will see. That is pretty cool, but we want to see those updates as well.
Sure enough, we can use the GetUpdates method and supply our Update Scope object to pull this information. And there you have it! You can compare the screenshots and you will see that the titles in the console match the titles from our query. Now I will show you how to view the update approvals by using the Update Scope object and the GetUpdateApprovals method. To make this work and to provide some useful information, I will make a couple of adjustments to the existing Update Scope.
This revision is shown here. Now we can use this scope in the method and pull some information. This technique is shown in the code that follows. Let us clean this up a little so it is more readable and not just a bunch of GUIDs. The code that follows produces an easier to read output.
The last two things I will show you in this blog are a couple of methods that require the Update Scope object and the Computer Target Scope object to work properly. They provide some nice reporting features similar to what you would see in the Administration Console. This method gets per-computer summaries for each of the specified computers, summed across all of the specified updates.
One thing you do not have available in the console is the DownloadedCount , which our previous code nicely displayed. The following code uses this method. Note: I changed the Update Scope to what I had at the beginning of this blog. This is so I can more accurately compare the output here with what is in the Administration Console. Now compare the previous image, with the console shown here , and you will see that they match up as planned.
So there you have it. This weekend I will talk about update 2.
0コメント