|
Post by bigmac on Dec 6, 2022 12:37:41 GMT
We have a MDT task sequence that is calling UI++ to set the computername, language settings and applications. This is working fine and I can see the variables stored during the task sequence. The issue we are facing is the Apply Network Settings domain join step where if we use UI++ the machine is not joining the domain. If we revert back to using UDI and MDT it works fine. I am currently using UI++ version 3.0.3.0. Our machine names have dashes in the name and I have enclosed the variable in double quotes as detailed in the following article. uiplusplus.configmgrftw.com/docs/actionconfig/variables.htmlHere is my config <!-- Task Sequence variables. --> <Action Type="TSVar" Name="OSDComputerName" >"%ZZComputerName%"</Action> Any advise or guidance as to why the domain join doesnt work when using UI++. Thanks
|
|
|
Post by bigmac on Dec 13, 2022 7:57:53 GMT
Does anyone have any updates or can provide some advice. Thanks
|
|
krys
New Member
Posts: 11
|
Post by krys on Dec 22, 2022 20:23:24 GMT
Tried this out today for kicks, couldn't replicate, will need more information on the rest of your implementation, maybe something TS related and how it's consuming the OSDComputerName variable? Here's a section of my script, we tightly control workstation names as you can see, with a check if imaging a virtual machine, and then uppercase the whole thing for visual preference. Anyways, this joined domain correctly with the Hypen, you can see the screenshot for the hostname used. <Action Type="TSVar" Name="OSDComputerNameVM" Condition='"%SystemSuffix%" = "V"'>"%RegionPrefix%%ZZBuildID%%ZZComputerName%%SystemSuffix%%PartSNVM%"</Action> <Action Type="TSVar" Name="OSDComputerName" Condition='"%SystemSuffix%" = "V"'>UCase("%OSDComputerNameVM%")</Action>
|
|