Hi,

How may coexist ZTI and LTI? By deploying directly from SCCM it is possible to run full zti. This is the best. Is it also possible using a GUI to deploy computers on LTI and just use it when need without interfering with ZTI?

I know I may not be clear... :(

Thanks,

The task sequence will do what you tell it to do.

If you make a Zero touch installation task sequence it will run what you tell it. 

If you make a zero touch installation but you have 1 section that look for something specific on the computer and start the UDI than it will do this only for the computer that have the requirement.

So to answer yes you can have a task sequence that on some device it run whit out user interaction and on some device it ask for some info using UDI

• Edited by Frederick Dicaire 17 hours 54 minutes ago

Hi,

Do you speak french Frederick? :)

What I was meaning is running the same TS in ZTI or LTI if need. So if a tech conclude the need to reinstall a computer immediately, then it restart the computer then F12 then get an interface to start a reinstallation and select what he is wanting.

Yes i speak French :)

But not sure i understand the term ZTI = Zero touch installation:ZTI is a fully automated deployment scheme in which installation requires no user interaction whatsoever and LTI = light touch installation deployments require limited user interaction. .

So still a bit confuse on what you need exactly. If you are using PXE and you want to use ZTI at some point you will need to clear the PXE flag this can be done automatically by SCCM using some sort os script (Jorgen as a great one). 

So in your example you might need to have the tech clear the PXE flag on the computer before rebooting and if the bios of the device as boot from network first you would have nothing to do.

If you are using unkown computer for your deployment you would need to make sure the computer is not know in SCCM for this t work

Hi,

I fully agree with you with ZTI. Implementing full ZTI is the best. But under some circumstance, the tech will not have a console but may need reinstalling the OS then he may need a way to start it directly from the computer. Then specify to not use USMT or use USMT just to reinstall data from another computer or just any other parameters. Doesn't it happens?

Well you can't have the same task sequence if what you want is for the tech to press a magic key during the TS and have new option like the use of USMT or NOT.

The only way to achieve something like this would be to script something that look to see if a windows is install and if so promp the UDI.

You could use some of the variable about OS refresh and the way the pc was booted to define if the UDI appear.

So in short if the decision to use USMT depend on something SCCM is not aware of than NO you can't have 1 single TS. 

Because SCCM is a machine and it does what we tell him to do. If a customer say i need my data back and another one say i don't need it SCCM will not know unless you have a mechanic to make him aware.

• Marked as answer by FRacine 17 hours 4 minutes ago

At the end of the day, you should be aware of two things:

1.  A task sequence itself can be referred to as ZTI or LTI, but neither is  really a feature.  It's really just marketing and is commonly used to denote if the task sequence will ask a user a question or not.  It's actually 100% possible to have a single task sequence behave as either ZTI or LTI depending on what it detects on the computer, what OU it's in, or some other variable.

2.  Making a task sequence available to run is a completely independent process to the task sequence it self.  You can make the same sequence be usable from PXE, Software Center, bootable USB, etc.

When you consider both of those, you'll realize the answer to your questions is just a frustrating "yes".  What I *think* you're asking for is the ability to occasionally override your default ZTI install with a LTI install to adapt to special circumstances.  I think the easiest way to pull this off is to build a default ZTI task sequence, then a second LTI task sequence, and finally decide the best way to make it available for use should you "need" LTI.  For example, give them a USB stick to boot from and not make it available on PXE as that people who need the bypass can bring it up easily.

If you want to get fancier, integrate with MDT and add a custom variable for "LTI".  Then you can use a singular task sequence and give your admin team access to the MDT workbench.  Said team simply adds exceptions for computers as they need to use LTI.

There are lots of ways to handle the problem.

 

• Edited by Justin.King 16 hours 59 minutes ago

Hi,

Great answer. You did understand. May be I am wrong but I believe it happens regurlarly peoples would override the ZTI. But how corporation are handling it? Does those corporations never have that need?

huge business have process that are define. They build the task sequence to follow those process.

Like Justin said having 2 or 3 task sequence to choose from upon starting the computer is not a big deal for most people. 

if you have process or way of doing things that are not streamlined no way to have only 1 ts that fits all the case.

The task sequence will do what you tell it to do.

If you make a Zero touch installation task sequence it will run what you tell it. 

If you make a zero touch installation but you have 1 section that look for something specific on the computer and start the UDI than it will do this only for the computer that have the requirement.

So to answer yes you can have a task sequence that on some device it run whit out user interaction and on some device it ask for some info using UDI

• Edited by Frederick Dicaire Friday, September 11, 2015 1:52 PM

Well you can't have the same task sequence if what you want is for the tech to press a magic key during the TS and have new option like the use of USMT or NOT.

The only way to achieve something like this would be to script something that look to see if a windows is install and if so promp the UDI.

You could use some of the variable about OS refresh and the way the pc was booted to define if the UDI appear.

So in short if the decision to use USMT depend on something SCCM is not aware of than NO you can't have 1 single TS. 

Because SCCM is a machine and it does what we tell him to do. If a customer say i need my data back and another one say i don't need it SCCM will not know unless you have a mechanic to make him aware.

• Marked as answer by FRacine Friday, September 11, 2015 2:42 PM

At the end of the day, you should be aware of two things:

1.  A task sequence itself can be referred to as ZTI or LTI, but neither is  really a feature.  It's really just marketing and is commonly used to denote if the task sequence will ask a user a question or not.  It's actually 100% possible to have a single task sequence behave as either ZTI or LTI depending on what it detects on the computer, what OU it's in, or some other variable.

2.  Making a task sequence available to run is a completely independent process to the task sequence it self.  You can make the same sequence be usable from PXE, Software Center, bootable USB, etc.

When you consider both of those, you'll realize the answer to your questions is just a frustrating "yes".  What I *think* you're asking for is the ability to occasionally override your default ZTI install with a LTI install to adapt to special circumstances.  I think the easiest way to pull this off is to build a default ZTI task sequence, then a second LTI task sequence, and finally decide the best way to make it available for use should you "need" LTI.  For example, give them a USB stick to boot from and not make it available on PXE as that people who need the bypass can bring it up easily.

If you want to get fancier, integrate with MDT and add a custom variable for "LTI".  Then you can use a singular task sequence and give your admin team access to the MDT workbench.  Said team simply adds exceptions for computers as they need to use LTI.

There are lots of ways to handle the problem.

 

• Edited by Justin.King Friday, September 11, 2015 2:47 PM