Currently, when using the USMT steps for capture and restore in a Task Sequence, it is not possible to customize the encryption strength to anything besides the default 3DES, since the "/encrypt" is hard coded into the Task Sequence Step. Adding /encrypt:"encryptionstrength" to the "OSDMigrateAdditionalCaptureOptions" TS variable causes the step to fail.
Please add an option to customize the encryption strength for USMT during OSD.1 vote
Take the OU path from 'Network Settings" and turn it into a variable e.g. _SMSMachineOUpath
I use dynamic variables to determine the OU based on location and device so my Domain OU path has OU=%devicetype%,OU=Location,OU=workstations,DC=Contoso,DC.com
so it would be nice to have the actual value in a variable that I can reference later say in a script to move existing object to the above created OU. I can see the full path in the SMSTS.log, but not in a variable. Also removing the LDAP:\ from the start could be handy in some situations I guess.1 vote
Vlad ask to pass this on:
He can try at the beginning of TS to add steps to set variables that I listed in my reply to the same strings that he entered in the UI of Network Settings step? Which will result in Network Settings step take the values from these global variables (not from UI, even though they may be the same). But it will also have a side effect that these variables will be available during task sequence for whatever he wants to user them for.
I’ll have a bit of time at the weekend. I’ve a couple of ideas about removing the LDPA:\\ you mentioned. Can you describe the scenario you want to address, please?
Would be nice to filter OSD Task sequences with custom global condition (Run only on the specified platforms).1 voteNoted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
I’m intrigued by this idea. Can you add more details / context?
Task Sequence Steps - Add ability to run step under specific account already stored in "Administration > Security > Accounts"
The ability to run a step under a specific account is fantastic but if it had the functionality to select from a list of the service accounts already being used by Configuration manager, then updating all task sequences when you change the password would be a much simpler task.1 vote
When reimaging a machine it would be most helpful if the machine would retain the name it already has. It greatly annoying that it gets renamed to "Desktop- something or another". Other imaging solutions have this ability (Acronis) without having to do it in some convoluted way; why can't SCCM? Thanks,1 vote
On SCCM/MDT integration OSD deployment the MDT Deployment Toolkit its downloaded for gathering information among other tasks, but because of multiple reboots during OSD the deployment toolkit is downloaded multiple times which causes delays during OSD, it will be great if we could download and cache the Deployment Toolkit during the OSD build to be re-use to improve deployment overall time. This way the Task Sequence knows the package is local and there is no need to re-download the files.1 vote
So one could choose image with voice command -"Computers, install main image"1 vote
add additional statuses to Task Sequence Deployment, so we can see if content was already downloaded when this feature is selected. Similar experience to Application Required deployment. Right now it requires lot of administrative work to check if WS is ready to start TS.1 vote
When utilizing the "Download Package Content" TS step and choosing to download to "Configuration Manager client cache", the data is first downloaded to the temporary folder smstasksequence. After that the data is copied to the Client Cache folder (%windir%\ccmcache) and as a last step the data is removed from the smstasksequence folder.
This process means that before the data in _smstasksequence is deleted, 2 copies of all data reside on the disk.
This results in the need for extra free space (2x the data) for the running TS.
A move instead of copy and delete might be a better option.1 vote
SCCM-MDT TS: Add Step Number before each step in the SCCM/MDT TS to help with trackign TS Reporting.
This would help with troubleshooting TS, if in the actual TS, to the left, it lists by number each step.1 vote
we have 10 Task Sequences accross 10 countries, and 10 test task sequences that show up in the same list. It would be nice to be able to easily hide deployments that are only for testing, and not production. If at the beginning of a T.S. , user domain credentials could be entered, and that would determine T.S. availability. Or they could be greyed out if not to be run by that user.1 vote
Thanks for your feedback, updating Status to Noted. See https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
As the comment notes – task sequences can be deployed hidden and launched with the Deployment ID or similar.
I'm seeing an issue with verifying the account used for joining the domain in a task sequence. Despite choosing a domain and OU, when I click verify it is defaulting to Users > Contoso1 vote
Thanks for the feedback item. Updating status to Noted – see https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
We’ve tested this multiple times across releases and it works as expected each time.
Can you provide any more info on your environment to give some clue why this may occur. It may be you’ll need to engage with CSS to solve this
I would like to se some telemetry / insights where client is going to push its USMT data before deployment starts. Need to know if disk space is sufficient on USMT stores.
As clients roam the network, I cannot predict where yesterday's clients are going to push their USMT data today when deployment starts.1 vote
We have had situations where the PXE Reponder service errors and stops listening to PXE requests WITHOUT the service stopping.
For example, if the service starts and the machine doesnt yet have an ip address.
PXE: No valid IP addresses.
PXE::StartPXEServer failed; 0x80070490
BUT the service keeps running!
Suggest that the service should stop in this case so that other monitoring tools can detect and remediate the service failing.1 votestarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started – see https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Our 2001 Technical Preview released today and contains changes to address the PXE responder service stopping on failure,
For more info:
The default window is too small to see the window pane contents properly. It always needs to be enlarged. Either make it larger as a default or allow the user to set the size and retain it across sessions.1 vote
Thanks for the feedback, updating status to Noted
See – https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
It would be nice to have a button for extra information which shows a list of all the steps in a T.S with a Green tick for success, yellow for skipped, Orange for failed but continued, and Red for failed and ended the TS, along with exit codes.
Having the option to export logs automatically to either a network drive or USB key would make troubleshooting remote deployments so much easier.1 vote
Would be nice to have a way to see what updates are applicable to the images, not just crossed referenced with only downloaded updates.1 vote
It would be great to have the ability to customize the USMT without being burdened with XML configuration. Although this could remain as an option being able to restrict themes from migrated and restrict pulling over the registry would be great. Sometimes with the registry you can often pull problems over with the migration.1 vote
When Task Sequence condition evaluation fails for any particular step, set the TS variable SMSTSLastActionSucceeded to false. OR create a separate variable SMSTSLastEvaluationSucceeded to control this.1 vote
when editing an existing task sequence and creating new conditions based on variable values, why not add an auto lookup or list of all Task Sequence variables existing in this same task sequence. it will make condition creation more easy and less error possible. Most easy to pick up existing variables in task sequence1 vote
- Don't see your idea?