Again, the OSDComputerName is not the issue, it's the WMI query looking for the ComputerSystem name.
From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Wednesday, May 13, 2015 6:36 AM To: [email protected] Subject: RE: [mssms] OSD - WMI query for computer name not working as expected We use a script at the beginning of the TS that pops up to prompt for the computer name and set the OSDComputerName variable. Save as a .vbs set env = CreateObject("Microsoft.SMS.TSEnvironment") Name = inputbox("Enter the name for the new computer" ,"Prompt for Computer Name:",env("_SMSTSMachineName"),400,0) env("OSDComputerName") = Name From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, May 13, 2015 2:07 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD - WMI query for computer name not working as expected Really...? You should change that. Really... From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Mittwoch, 13. Mai 2015 01:30 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD - WMI query for computer name not working as expected No MDT here, so I believe that's not an option. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Tuesday, May 12, 2015 4:15 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD - WMI query for computer name not working as expected I don't have that many rules, simply computer name patter, but I use customsettings.ini and a userexit script to set the OU variable (can't remember the exact name) and let the regular domain join step do that using the variable. So, the script defines the variable, the step uses it. No (complicated) conditions required. -roland From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Dienstag, 12. Mai 2015 19:12 To: [email protected]<mailto:[email protected]> Subject: [mssms] OSD - WMI query for computer name not working as expected We have a domain join step that evaluates conditions based on an HTA the tech fills out before imaging begins. Depending on these conditions, the computer joins the domain and is placed in the appropriate OU. There are 3 main conditions we evaluate: OSDRole - TS variable, can be lab, staff, etc. OSDBusinessArea - Another TS variable, based on department These evaluate fine in our conditions when joining the domain. But the other condition does a WMI query for the computer name. Unfortunately, at this point in the imaging process, the computer name in WMI is MININT-XXXXXXX, so it evaluates as FALSE. [cid:[email protected]] Do we need to move this step down further in our TS? I don't know how else to evaluate the computer name (OSDComputerName is available, but there is no "LIKE" statement). [cid:[email protected]] Any help appreciated! Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com<http://www.henryford.com> for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
