Thank you for your request. We are publishing information in a Knowledge Base article as Microsoft’s updates/patching practices evolve:
Over the coming releases, we will be revamping our targeting and scheduling pages. This a great example of where we will extend your ability to control what you are targeting and when it should be delivered.
This request is under review for a future release. Please continue to vote to voice your support.
Thank you for posting this request. We encourage others to “vote it up” for consideration in a future release.
Note that as of SMA 8.0, you can manually archive users, but the understanding on this request is that we automate it and that is what is under review.
Planned for an upcoming release
4 votesRichb shared this idea ·
97 votesRichb commented
Requested Sept. 2013, Planned Jan. 2015. New versions have come but this feature is still missing. We have not allowed field techs to modify the software license asset records so therefore they cannot update any asset records! Summer 2016 and still waiting.
Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.
We will add a “clear activity” feature, but such does not exist at the moment. You can stop following things and they will stop resulting in updates to your feed, but right now you can’t remove items from the feed.
We are working on a major update to the profile area that will make it easier to manage what you are following.
A good suggestion, thanks!
There are a couple of ways to approach this – I think the current thinking would be to add a “type” to each script and allow users to define them and then use the View By function. Thoughts?