naxgenie.blogg.se - Osdcomputername sccm

But further down at the Post Install another gather runs and runs the customsettings.ini file. There is of course probably a more automated way of achieving what you are looking for, but if you don't mind importing bare metal systems into the desired collections then this should work a treat and give you the outcome you are looking for. Also at the start of my Task sequence which is integrated with MDT and SCCM 2012 R2 there is a gather which doesn't run the rules of the customsettings file. The beauty about this will be that all the groups (roles to be installed) can be attached to the one TS and the collection and task sequence variables look after what gets installed. So for example if you create a group in your TS called deploy IIS role and below this the steps you need to actually configure this role and on the root (the group folder itself) you add a task sequence variable of InstallWebServerRole and set to true also then when you deploy this task sequence out to this collection it will check against the conditions and see that the imported system is indeed a member of IIS servers collection and the conditions set match each other so the IIS role will get installed on this system. Then in your Task sequence create groups and at the root of each group put a task sequence variable to match that of the collection variable.

The Print server collection have a collection variable like InstallPrintManagement and set to true.

The IIS server collection have a collection variable like InstallWebServerRole and set to True.

If your systems are bare metal systems you could use the import computer configuration method and specify which collection to add them to.Īt the collection level you could create collection variables for example: for example you could have collections like so: Not sure of your Asset design, but you could create collections based on roles.