bgade
New Member
Posts: 4
|
Post by bgade on Jul 17, 2019 13:15:12 GMT
I'm seeing an issue on some of my machines where XWiredLANConnected isn't set and the UI++.log doesn't show that it found a wired NIC, even though the wired NIC is present and connected and shows as such in WMI. If I boot the machine into a boot image and run the same steps the issue doesn't appear, so it appears to be something wrong only in FullOS and not on every machine. Has anyone else seen this? Does anyone know how the DefaultValues action gathers data? This is happening on Win10 1703 and 1803 using UI++ 2.11.1.2.
Here's the relevant section of the UI++ XML:
<ActionGroup Name="Pre-Flight and System Information">
<Action Type="DefaultValues" ValueTypes="Asset,Net,VM" ShowProgress="True">
<Text Type="Asset" Value="Retrieving Asset information" />
<Text Type="Net" Value="Retrieving Networking information" />
<Text Type="VM" Value="Retrieving Virtualization information" />
</Action>
<Action Type="Input" Name="SystemInfo" Title="System Info" ShowCancel="True">
<InputInfo NumberofLines="1">Make: %XHWManufacturer%</InputInfo>
<InputInfo NumberofLines="1">Model: %XHWModel%</InputInfo>
<InputInfo NumberofLines="1">Serial Number: %XHWSerialNumber%</InputInfo>
<InputInfo NumberofLines="1">MAC Address: %XMACAddress%</InputInfo>
</Action>
<Action Type="Preflight" Title="Preflight (Physical)" ShowCancel="True" Condition='InStr ("%XHWChassisType%" & ",", "Virtual") < 1'>
<Check Text="At least 8GB RAM" CheckCondition='%XHWMemory% >= 7500' />
<Check Text="Connected to Power" CheckCondition='"%XOnBattery%" = "False"' />
<Check Text="Connected to Wired Network" CheckCondition='"%XWiredLANConnected%" = "True"' />
</Action>
<Action Type="Preflight" Title="Preflight (Virtual)" ShowCancel="True" Condition='InStr ("%XHWChassisType%" & ",", "Virtual") > 0'>
<Check Text="At least 4GB RAM" CheckCondition='%XHWMemory% >= 3500' />
<Check Text="Connected to Power" CheckCondition='"%XOnBattery%" = "False"' />
<Check Text="Connected to Wired Network" CheckCondition='"%XWiredLANConnected%" = "True"' />
</Action>
</ActionGroup>
|
|
bgade
New Member
Posts: 4
|
Post by bgade on Jul 17, 2019 18:31:12 GMT
Update: I'm wondering if this is a localization issue. I don't see this problem occur on English machines but I've seen it on machines configured for Korean and Japanese so far.
Jason, can you provide some background on how the DefaultValues action gathers data?
Relevant section of the U++ log from a test VM (one wired NIC, no Wi-Fi, Win10 1803 Japanese):
<![LOG[ + Set the task sequence variable 'XOnBattery' to the value 'False']LOG]!><time="03:29:27.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="tsvar.cpp">
<![LOG[ * Getting wireless network information...]LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="actiondefaultvalues.cpp">
<![LOG[ * Loading wireless networking libraries...]LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="actiondefaultvalues.cpp">
<![LOG[ * Loading wireless networking info...]LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="actiondefaultvalues.cpp">
<![LOG[ + Set the task sequence variable 'XWLANDisconnected' to the value 'True']LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="tsvar.cpp">
<![LOG[ * Getting network information...]LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="actiondefaultvalues.cpp">
<![LOG[ + Set the task sequence variable 'XIPGateway' to the value '172.30.84.1']LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="tsvar.cpp">
<![LOG[ + Set the task sequence variable 'XIPAddress' to the value '172.30.85.60']LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="tsvar.cpp">
<![LOG[ + Set the task sequence variable 'XIPSubnetMask' to the value '255.255.254.0']LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="tsvar.cpp">
<![LOG[ + Set the task sequence variable 'XMACAddress' to the value '00:50:56:B1:4E:DD']LOG]!><time="03:29:28.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="tsvar.cpp">
<![LOG[ * Getting virtualization information...]LOG]!><time="03:29:29.000+-540" date="07-18-2019" component="UI++" context="" type="1" thread="9992" file="actiondefaultvalues.cpp">
|
|
|
|
Post by Jason on Jul 25, 2019 21:21:34 GMT
The determination of a wired LAN connection is a bit of an inference and is initially based on this WMI query:
SELECT Name FROM Win32_NetworkAdapter WHERE NetConnectionStatus=2 And NetEnabled='True' And AdapterType='Ethernet 802.3' And PhysicalAdapter='True'
|
|
bgade
New Member
Posts: 4
|
Post by bgade on Jul 26, 2019 2:17:27 GMT
Thanks Jason, that enabled me to find the issue. Testing on a VM configured for Japanese reveals that it is indeed a localization issue. AdapterType displays as "イーサネット 802.3", which causes the query to return zero results. Any way this can be addressed in a future release? Maybe changing it from "AdapterType='Ethernet 802.3'" to "AdapterType LIKE '%802.3'"? I tested that variant and the NIC was returned as expected.
|
|
|
|
Post by Jason on Jul 26, 2019 3:03:26 GMT
Yep, adding this to my backlog now.
|
|
bgade
New Member
Posts: 4
|
Post by bgade on Sept 23, 2019 18:50:57 GMT
|
|
|
|
Post by Jason on Oct 2, 2019 1:26:55 GMT
Well AdapaterTypeID = 1 is for token ring but checking for 0 may work as well. I'll have to validate.
|
|
