OSDCOMPUTERNAME issue

bartada
New Member

Posts: 9

OSDCOMPUTERNAME issue May 24, 2019 12:59:39 GMT

Quote

Post by bartada on May 24, 2019 12:59:39 GMT

I'm having an issue where I can't get the OSDCOMPUTERNAME value to name properly. It names with a "Win-" in front and random afterwards like it does during sysprep. I know its because of the OSDJoinDomainOUName value has 2 underscores in it. I know this because different OU's name properly. I have tried to make the OU wrapped in quotes and also the underscores wrapped in quotes but it has not worked. Here is what the OSDJoinDomainOUName looks like:
Works:
<Action Type="TSVar" Name="OSDJoinDomainOUName" Condition='"%OSDLocation%" = "CAM"'>LDAP://OU=Windows 10,OU=HRAL,OU=Workstations,OU=Machines,OU=HRA,OU=Development,OU=my company,DC=am,DC=mds,DC=my company,DC=com</Action>
Doesn't work:
<Action Type="TSVar" Name="OSDJoinDomainOUName" Condition='"%OSDLocation%" = "CAI"'>LDAP://OU=Windows 10,OU=__Computers Container,OU=HRI,OU=Development,OU=my company,DC=am,DC=mds,DC=my company,DC=com</Action>

Here is the computer name:

<Action Type="TSVar" Name="OSDComputerName" >"%OSDCompCode%%OSDLocation%%OSDSystemType%%OSDAssetTag%%OSDPurpose%"</Action>

Anyone know how I can fix this? Thanks!

Jason Administrator Posts: 485	OSDCOMPUTERNAME issue May 24, 2019 21:18:00 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Jason on May 24, 2019 21:18:00 GMT Where exactly in your task sequence are you running UI++? Have you reviewed the log to validate that the variable is being set per your expectations?

bartada New Member Posts: 9	OSDCOMPUTERNAME issue May 28, 2019 13:11:36 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by bartada on May 28, 2019 13:11:36 GMT It's before apply operating system. The UI++ log have the variables set correctly. I'm stumped.

bartada New Member Posts: 9	OSDCOMPUTERNAME issue May 28, 2019 13:47:42 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by bartada on May 28, 2019 13:47:42 GMT Also, I looked at the setupact.log in the panther folder and it has the "WIN-" name.

bartada New Member Posts: 9	OSDCOMPUTERNAME issue May 29, 2019 16:20:40 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by bartada on May 29, 2019 16:20:40 GMT Jason, do you have a lab you can test this in? Specifically the OU join that has underscores in it.

Jason Administrator Posts: 485	OSDCOMPUTERNAME issue May 29, 2019 22:09:52 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Jason on May 29, 2019 22:09:52 GMT > before apply operating system That's not early enough. It needs to be before the Apply OS settings task as this task is responsible for updating the unattend.xml.

bartada New Member Posts: 9	OSDCOMPUTERNAME issue May 30, 2019 11:41:13 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by bartada on May 30, 2019 11:41:13 GMT It's right after I set TS variables. Attachments:

Jason
Administrator

Posts: 485

OSDCOMPUTERNAME issue May 30, 2019 12:58:08 GMT

Quote

Post by Jason on May 30, 2019 12:58:08 GMT

Have you dumped the variables right before the Apply OS Settings tasks?

Are you sure that your Apply OS Settings tasks are even running? WHy have four of these btw instead of just populating the timezone variable?

Also, I don't see a Setup Windows and ConfigMgr task in that TS -- is it farther down?

On a side note, there' no reason to copy CMTrace anywhere anymore as it's part of the boot image now (has been since like 1602) and is also part of the client installation (since 1802 I think).

bartada New Member Posts: 9	OSDCOMPUTERNAME issue May 30, 2019 17:01:37 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by bartada on May 30, 2019 17:01:37 GMT I think I see the issue. I will test and get back to you.

bartada
New Member

Posts: 9

OSDCOMPUTERNAME issue May 30, 2019 17:08:47 GMT

Quote

Post by bartada on May 30, 2019 17:08:47 GMT

How would you use the timezone variable? I'm doing something like this:
www.systemcenterdudes.com/collection-variables-task-sequence/
It might not work because we have 2 imaging locations and then the equipment is shipped to remote sites.

bartada New Member Posts: 9	OSDCOMPUTERNAME issue May 30, 2019 19:41:18 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by bartada on May 30, 2019 19:41:18 GMT I changed the Apply Window Setting and it resolved my issue. Thanks for the hint!

Jason
Administrator

Posts: 485

OSDCOMPUTERNAME issue May 31, 2019 19:49:51 GMT

Quote

Post by Jason on May 31, 2019 19:49:51 GMT

For the timezone, simply set the task sequence variable OSDTimeZone to the proper value before the Apply Windows Settings task. Note that I'm assuming that was the purpose for you having multiple Apply Windows Settings tasks. And if so, and you simply set the OSDTimeZone variable, you only need a single task as the value you set for this variable (considered a run-time value) will take precedence over the value set in the task sequence editor (considered a design-time value).

OSDCOMPUTERNAME issue

Post by bartada on May 24, 2019 12:59:39 GMT

Post by Jason on May 24, 2019 21:18:00 GMT

Post by bartada on May 28, 2019 13:11:36 GMT

Post by bartada on May 28, 2019 13:47:42 GMT

Post by bartada on May 29, 2019 16:20:40 GMT

Post by Jason on May 29, 2019 22:09:52 GMT

Post by bartada on May 30, 2019 11:41:13 GMT

Post by Jason on May 30, 2019 12:58:08 GMT

Post by bartada on May 30, 2019 17:01:37 GMT

Post by bartada on May 30, 2019 17:08:47 GMT

Post by bartada on May 30, 2019 19:41:18 GMT

Post by Jason on May 31, 2019 19:49:51 GMT