Anyone have experience with this ts variable? I am having trouble getting it to work and have a couple of questions.
Does the computer need to be in a collection that is targeted for several task sequences and then this variable is used to chose one of them without asking the user for which of the assigned TSes to run? Or can the variable be used to run a task sequence that is not targeted to the computer in question? I am using a pre-execution hook to assign this variable, but I get the no task sequences available error. I thought I read in the documentation that this variable is to be used to run task sequences independently of assignments, but clearly I am doing something wrong. If I have to add the computer to a collection or multiple collections (which is newly problematic in ConfigMgr 2012 - takes forever for direct adds to show up in the target collection) what is the point of the variable? Doing bare metal fresh installs. I've been using web services to add the computer to sccm and to the target collection for the chosen task sequence. This is pretty slow and takes about 60-90!seconds for the computer to show up in the collection and find an assigned task sequence. I was hoping to speed the process by just defining what ts deployment to run, but it looks like instill need to make sure the computer is in the target collection, so I can't figure out what is gained by this new variable. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
