![]() ![]() However, there’s one last piece of the puzzle we’ve not been talking about yet and that’s the requirements of triggering the schedule for the task sequence deployment. This will help us mimic the behavior required for our goal of re-running a task sequence deployment (previously known as assignment back in the days). With this in mind, we can take advantage of these two properties and directly change the local policy and set it as mandatory and always rerun, even if that was not the original configuration made in the ConfigMgr console when it was deployed. Each instance has two properties that we need to be aware of: It may not be known by every ConfigMgr admin, but many of us know that the ConfigMgr client keeps track of it’s policy locally in WMI, more specifically in the root\ccm\policy\machine\actualconfig you can explore the different set of policies that’s currently in effect. Within a class named CCM_TaskSequence, there exists an instance of each advertisement for task sequences. Given this method is a well known and working one, I wanted to explore if there was a way where I did not have to restart the ConfigMgr client, and simply enforce the task sequence to run straight away. My previous solution consisted of removing the WMI object referring to the schedule for the task sequence deployment and restart the ConfigMgr client forcing it to pull down policies and check against it’s local policy and re-running the deployment. Recently, while developing a solution for a Windows 10 servicing project I needed a solution to rerun a task sequence at a given time. ![]() I’ve written about this topic previously and also written a small PowerShell based tool to help administrators ease the pain of rerunning a task sequence. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |