- This topic is empty.
29. January 2008 at 14:58 #889
we have about 130 Wyse devices right now but using wdm only local (not in our network) mainly because we use another pxe-server with enteo netinstall (osd) in our network.
IÂ´m working on it to change this, but this will take some time until bosses decide to spent some money for the help from wyse.
But my main problem is that the wdm 4.5.2 installation creates a second entry in the database after pushing a new image (which we have modified) onto a device. This second entry has a wrong mac-address (always the same wrong mac address).
If I delete both entries and reboot the device then only one correct entry is created then.
Does anyone has seen this even in older versions ?
We had this from time to time with older wdm-versions too.
Thx 4 hlp (cause german support seems not to be a help)29. January 2008 at 15:05 #11508ConfGenKeymaster
- Total Post: 11007
- Jedi Master
What devices with which builds are you seeing this on?29. January 2008 at 15:17 #11509
Had this problems with 941GXL and with V90L.
Always updated older versions with the new one (941GXL Version to 546 and V90L Version to 576).
At this moment I did a test and upgraded same three devices a second time with the new Image and nothing like that happend.
Seems as this only happens when upgrading older versions to an actual (modified) image taken from a configured device per pxe.
Second entry is created after first boot of new image after image is applied.
Could it be that there is something wrong on that image ?
Had this problem even with other new created Image (actual image modified with our company settings).
Actual I update a 941GXL with Image 3.010.431.512 to 4.010.546.512 and have this strange effect.
One entry with correct mac-adress and Imageable=yes and one entry with wrong mac-adress with Imageable=no. Everything else is the same (including Name).
Deleting the wrong entry causes a restart of the device but the good entry stays correct.
Updating this device a second time does not show this effect.31. January 2008 at 1:48 #11551karazielMember
- Total Post: 74
- Back Stage Pass
young grasshoppers…gather near…
The HAgent on XPe uses NetBIOS to determine the MAC address.
If you’ve disabled NetBIOS support (manually under TCP settings, or via Option Tag) you’ll see results like this as it can’t determine the MAC and generates a random value for the MAC to maintain a unique ID.
Alternately, if you happen to have Dual NICs (fiber or wireless addon) then that it could be reporting that MAC instead. Only have 1 NIC enabled at a time.
-k31. January 2008 at 6:30 #11557
The WDM and the new devices are not in our network, just connected over a switch.
Its not a random mac-adress which is wrong, always the same one.
IÂ´m using just the internal NICs.
Today tried and updated three devices at once.
No error. Everything fine. I have changed nothing.
Will try if this happens only when i upgrade one device next time.
But thx 4 trying to help.31. January 2008 at 7:01 #11558
Eventually found the problem.
Enabled automatic upgrade of hagent and so the devices are getting the actual hagent 220.127.116.11 from WDM.
Since then the actual Image (Build 546) for 941GXL had hAgent 18.104.22.168 and the actual Image (Build 576) for the V90L had hAgent 22.214.171.124.
Think with the actual hagent 126.96.36.199 this problem seems not to appear.
Will test this later.31. January 2008 at 7:42 #11560ConfGenKeymaster
- Total Post: 11007
- Jedi Master
Cool, thanks for the update28. May 2008 at 20:13 #13095BasMember
- Total Post: 4
I have experienced the same problem with a sticky MAC address. Every time I send an image to a thinclient (in my case v90LE XPE), the discovered record in WDM(4.5.3) gets an additional record with the same devicename and a ghost MAC address. This is very annoying because only the new record can be used tot send jobs to. The MAC address is owned by the thinclient that I used to build my image.
I have a separate development environment where I create images. At first I thought that because I connected (only once) the development Thinclient to the production network I corrupted the WDM database in some way. After removing the developement Thinclient and reinstaling WDM with a clean database I still had the problem. So I suspected that my image in some way stored the MAC address of the development thinclient.
After building a new image from scratch (wyse build 596) the problem went away. My original image was also based on build 596 so probably something went wrong during the building process but I don’t know what?
Hope this is some help.
- You must be logged in to reply to this topic.