I am aware that having the variable of DomainJoin will prevent the capture dialog from appearing when running the task. The problem is, even when the options are greyed out due to the domain settings not being applied from a different setting in the workflow
it still breaks the task.
E.G.
I am using the database, and have my workflow as such:
[Settings]
Priority=Model, TaskSequenceID, LSettings, CRoles, RApps, LApps, MMApps, MMSettings, Default
Properties=MyCustomProperty
DataBase:
Location Settings: Overall settings for Domain join, wizard skips, etc info per gateway
Role Apps: Apps per role
Make/Model Apps: Apps specific to a piece of hardware
CustomSettings INI:
Model/Task Sequence/Default: I have tried to null out the DomainJoin settings with these variables by adding workgroup join by task ID, Model, etc and nothing seems to work. I've verified in other tasks
that these settings take place of what's in the DB, but the DB settings are still there, greyed out and causing an issue.
[X86SYSANDCAP]
JoinDomain=
JoinWorkgroup=WORKGROUP
[VMware Virtual Platform]
JoinDomain=
JoinWorkgroup=WORKGROUP
As shown below the model/TS specify the workgroup (1st pic is normal deploy, 2nd is cap) but the greyed out settings are still having an effect. Skip Capture is set to NO at each level, and when I remove the Domain from the DB it shows up correctly.
Not sure what to do besides removing the domain everytime I want to do a capture, which seems a bit unreasonable and I don;t want my T1s in the DB.