Panu Saukko
My feedback
-
1 votePanu Saukko
shared this idea
·
-
1 votePanu Saukko
shared this idea
·
-
2 votesPanu Saukko
shared this idea
·
-
7 votesPanu Saukko
shared this idea
·
-
66 votesPanu Saukko
commented
It would be great to have an option to upgrade clients even when they are not part of a boundary and use DPs from default site boundary or even from Cloud DP (optionally). If you have a client installed, you want to keep it up-to-date.
-
488 votesPanu Saukko
commented
As IT service provider, you want to co-manage clients from multiple Intune tenants using one ConfigMgr hierarchy. It is just too expensive to implement a separate ConfigMgr site for each Intune customer you are managing.
Panu Saukko
supported this idea
·
-
12 votesPanu Saukko
shared this idea
·
-
2 votesPanu Saukko
shared this idea
·
-
4 votes
Agreed – I’d filed the same item in our database a while back. Updating status to Noted – see https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
Pannu – I’ll circulate that feedback for Run Task Sequence
Chad – Collapsible Groups were added in our 1703 Tech Preview – https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1703
Thanks all!
Panu Saukko
commented
And there should be a different icon for Run Task Sequence step.
-
20 votesPanu Saukko
shared this idea
·
-
2 votesPanu Saukko
shared this idea
·
-
If each ConfigMgr TP build does not get its own full install, provide a way to reset the expiration.
2 votesPanu Saukko
supported this idea
·
Noticed a similar issue with user accounts' passwords in SCCM: you cannot have "%%" in your password. This was tested with NAA password. The password confirmation succeeds in ConfigMgr console, but if NAA has "%%" in its password, DP will log audit messages "incorrect username or bad password", when NAA is used.