Cristopher
My feedback
-
1,746 votesstarted ·
AdminBob Mac Neill
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.See https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1905#bkmk_tsdt
& https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Group-applications-into-a-single-deployment-in-ConfigMgr/ba-p/624318Cristopher
supported this idea
·
-
9 votesCristopher
commented
I'm trying to troubleshoot a warning status on a remote DP and also can't find a way to increase the size of smsdpmon.log. This is troublesome because the log gets overwritten before the content validation process can finish.
-
350 votesCristopher
supported this idea
·
Cristopher
commented
There are several 3rd party workarounds for notifying user of progress during an in-place OS upgrade but a supported native solution would be best.
-
136 votes
Apologies – my error – reverting status back to noted. This request is not addressed in 1905 Technical Preview.
Cristopher
supported this idea
·
Cristopher
commented
If I had any more votes I'd gladly use them on this. We're constantly getting burned by this. I'm willing to be the majority of SCCM installs are limited to a single time zone. Let us default everything to client local time, please!
-
824 votesCristopher
commented
For those of you following this, here's a great blog series to assist with 802.1x deployments covering various scenarios.
http://www.asquaredozen.com/2018/07/29/configuring-802-1x-authentication-for-windows-deployment/Cristopher
commented
Fingers crossed that 2017 will bring some support to WinPE and SCCM task sequences so that we can do some OSD on a network that uses 802.1x security.
Cristopher
commented
We're headed backwards here. The latest WinPE 10 (version 1607) broke the dot3svc service. https://social.technet.microsoft.com/Forums/en-US/win10itprosetup/thread/93f32a23-7558-4742-91ab-ba0e7801ed0e/#3853df61-8dcf-4560-8b01-27da4fcca235 Those of you who are in an 802.1x environment, help me make some noise on this please.
Cristopher
commented
We have 802.1x on our network and in order to achieve a successful operating system deployment we have had to implement hacks upon hacks into our process. I've gone through 2 dozen iterations of our boot image trying to get the script "just right" and it is still not 100% functional. Because of this, most of our deployments are still done on an isolated network segment where 802.1x is disabled.
Cristopher
supported this idea
·
-
5 votesCristopher
commented
You can submit changes to the docs via GitHub. Also, there are lots of bloggers who have multi-part posts on how to set up co-management. Look up scconfigmgr.com and anoopcnair.com guides.
-
7 votesCristopher
commented
You can also compress the IIS logs folder to greatly reduce the size on disk.
Cristopher
commented
We use a scheduled task to clean up IIS logs on a monthly basis. A native function would be nice.
-
1 voteCristopher
commented
IP address is visible in the device properties. Just double-click and filter by "address" to see it. You could also just ping the device's host name.
-
2 votes
-
5 votesCristopher
commented
-
7 votesCristopher
commented
-
18 votesCristopher
shared this idea
·
-
187 votesCristopher
commented
More and more applications would greatly benefit from this. Last year I packaged Adobe Acrobat Pro DC and had to set it to run when no user is logged in because it simply killed explorer.exe. It would be nice if I could prevent the user from simply logging back in before the installation completes.
Cristopher
commented
Our previous deployment solution, CA ITCM, had this feature. It was called logon shield. It was clunky, to say the least. If anything went wonky during an application install nobody could log back on to the PC indefinitely. Someone would have to be physically present to power cycle the machine.
As much as I'd love to see this feature integrated into Configmgr, it has to be very well though-out. Have it time out when the deployment times out. -
20 votes
Thanks for the suggestion and comments. Updating status to Noted
https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
Cristopher
commented
Packages can have a scheduled content update set up in the Configmgr GUI. Applications can have content updated for their deployment types via powershell. We use Task Scheduler to schedule these scripts over night so that they do not interfere w/ running Task Sequences.
-
11 votesNoted ·
AdminMark Silvey - ConfigMgr Product Team
(Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager)
responded
Scott – How would you like it streamlined? What would you do if you could have anything?
Cristopher
commented
The automatic creation of an Application would be nice. We use the app model to deploy/upgrade the Admin Console after upgrades. However something similar to the automatic client upgrade would be extremely helpful too. We frequently string the Admin Console application together with a package for a hotfix inside a task sequence because the hotfix packages are auto-generated when the KB is installed on the site server.
-
32 votesCristopher
commented
I would almost say take this a step further and request the ability to apply a separate maintenance window to PCs if nobody is logged on.
-
10 votesCristopher
commented
I wanted to vote on this but I already ran out. :-\
-
0 votesCristopher
commented
Copy/paste keyboard shortcut doesn't work but right-click paste does work for MAC address entry.
-
14 votesCristopher
commented
I like it.
-
3 votesCristopher
commented
Client upgrade is automatic now so there is no longer a need for this request.
Cristopher
commented
The application model also has the benefit of detection methods. This eliminates the need for an outdated clients collection, which is cumbersome. Just deploy the latest client to everybody and it won't re-install if they already have it.
I found a way to preserve the log files. Use Powershell to output them to another location as they're being created. You'll get duplicate entries but it will all be there in the end.
This led me to a rogue entry in WMI and I was able to fix the yellow bang on my DP status.
$DPserver = "YourDP"
$timeout = New-TimeSpan -Minutes 500 #just over 8 hours
$sw = [diagnostics.stopwatch]::StartNew()
while($sw.elapsed -lt $timeout){
$log = Get-Content -Path "\\$DPserver\d$\SMS_DP$\sms\logs\smsdpmon.log" -Force
$log | Out-File -FilePath "C:\Temp\smsdpmon-combined.log" -Append -Force -Encoding utf8
Start-Sleep -Seconds 1200 # loop every 20 minutes
}