- This topic is empty.
-
Posts
-
I have one X90L that isn’t checking into WDM. I have 3 others working correctly. I have captured an image using the USB Imaging utility and all of them were imaged from that image.
If I delete the others from WDM, they do the reboots and check right back into WDM. This one was in WDM in the past, but after I deleted it it doesn’t check back in anymore.
I reimaged it yesterday, still not checking in. If I connect to the http:///Hserver.dll?&V99 from the device, I get the correct connection string, so it can obviously see the WDM server.
Very strange. Any ideas?Hi,
go to Configuration Manager-Preferences-Logging Preferences and set all to debug level.
Now start the failing X90 and look in the WDM log (Systemtray icon). Do you see any message that the X90 tries to check in? Maybe something like “Existing device checked in….”?
I assume that the X90 is still somehow in the DB and therefore the unit is not created again.
Verifiy the checkin with a working device.CG
In the Web Services Log I am seeing:
Existing Device: CheckinIt looks like a new line every 15 minutes.
The device still isn’t showing up in WDM.
And that “device” is the missing X90?
Are you using MSDE or some MS SQL server as a DB? Do you have any management console installed to alter the WDM DB?CG
Yes, that is the “missing” device. We are using 4.7.1 with a SQL database.
Only using standard WDM console.Cool, then it looks like my first tought.
I will check to find a way to delete this device from the DB to let it recheck-in as a new device.
What does standard SQL mean? Do you have some SQL management tool running?CG
MS SQL database on a SQL 2005 server.
Managed using SQL Enterprise Manager.Great. Open the Enterprise Manager and go to the RapportDB.
Open the “Client” table and search for the “missing” X90.
Delete this line and open WDM console again.CG
I don’t see the “missing” device listed in the Device table.
I see the 3 other X90L’s.Okay, I found out from my Wyse rep that I need to run c:windowssetupPrep4Man.cmd before imaging it.
This is basically a Sysprep procedure. My guess is that the device checks into WDM using the Windows SID and since the original device (that the image was captured from) was in the database, it didn’t think it was new.The only issue I have now is that I had a manual Wifi connection created in the image and this process wipes that out.
Although the Wyse rep is right that you should always run prep4man, this will not fix it. Devices are checking in to WDM using the MAC address not the SID. You can prove this by deleting all X90 and then start the missing one. If it is a SID issue the missing unit should appear. But I doubt.
CG
That fixed the issue with the device not showing up in WDM.
But now I reimaged 4 devices with an image that had been prepared using the prep_4_man.bat file.
Now they all “replace” each other in WDM. Something in the image retains a unique setting that messes up WDM.The last device to check in is the only one listed in WDM.
Wow, it is getting even stranger each time.
Can you confirm that each unit has definitely a different MAC address? Check locally.
After reimaging them after executing pre4man, did you see the Windows Setup routine?Which firmware and which BIOS are you using?
CG
v5.02 B618
BIOS is Ver1.00PARTTBL (as listed in WDM)
When I go into the BIOS it’s listed as 1.0E-0512-0207.
(This is the latest BIOS on the Wyse site)It appears that the image I captured using the USB utility is also capturing the MAC address of the wireless NIC. When I push the image to another device, it checks into WDM and kicks out the other device that has that same wireless MAC address (I am running these devices using only the wireless NIC).
After the new device does it’s reboots, it comes up with the correct MAC address, but then I have to reboot the original device and have it check back in again.
- You must be logged in to reply to this topic.