- This topic is empty.
-
Posts
-
I am using WDM 4.5.3 to manage 700+ V90 series devices with XPe. When I re-image a device, the device name changes to the name of the device I pulled the image from. This is causing much grief as we do quarterly updates on our devices, and having to rename them all back to our corporate standard names is a nightmare. I am working with Wyse on this issue and they have had me try several different fixes, but none have worked, so far. Does anyone out there have any suggestions?
Simple – DO NOT RENAME THEM!
😀
So here is how it works, the units are set up to re-name themselves XPE008064XXXXXX where XXXXXX is based on the MAC address of the unit. This ensures the name is always different and avoids issues with duplicate names.
Seriously, if possible stick with this and allow the naming convention to stick.
If you do rename the device BEFORE you pull the image the name change process is set up not the run and therefore you end up with duplicate names – this is by design as there are cases where an image need to be pulled and the name kept.
If you REALLY need to change names here is what I would do as a few options, I would add first this is assuming the devices are non-domain members.
Option 1:
Don’t change the name before pulling the image, use Wyse Device manager to re-name remotely after deployment.Option 2:
Don’t change the name before pulling the image. Create a VBS script to run once from the “run once” section of the registry to change the name. This way if the script fails at least you do not have duplicate names. So here is the flow – push a new device image out, it boots and disables the write filter (this always happens on first boot anyway) and the changename.vbs runs.You will need to provide a mechanism for the script to generate a unique name based on your standard but without knowing what this is I can not help much.
I hope this helps,
Cheers,
-TTI don’t know what Wyse already ask you to tet but have you tried one of these before pulling the new image?
1. From a command prompt run “xwfile /d hostname.arc”. This deletes the computer name from the wfs, and thus should trigger a rename.
2. If that does not work, you can rename the client MINWITHNET, which is an internal command to trigger the client to rename to default XPE at next boot.CG
thinkthin – The advice to not rename the devices is not a viable solution. The 700+ devices that I am updating have unique names that identify the location of the device within our organization and are already joined to our domain. If re-imaging the devices changes the device name, they all then need to be renamed manually and then re-joined to the domain. The master that the image is pulled from has the unique name ‘XPE(MAC Address)’ and all the devices that are re-imaged from this master have the same duplicate XPE(MAC Address) name. 700+ devices with the same name that then have to be renamed and rejoined to the domain is the problem. I have pulled several images from several devices and have had the same results.
IConfGen- Yes, I have done the “xwfile /d hostname.arc”, and that does not change the outcome.
In the past, the unique device names were maintained after the re-imaging process and no manual renaming of the devices or rejoining to the domain was necessary. According to Wyse, this is the way it is supposed to work, but it is suddenly not working in our case. This is a new snag that we are experiencing. I am not interested in a ‘band-aid’ approach to fix the problem; I want it to work as it is designed. Is there anyone out there that has had the same problem and come up with a solution?
I guess you have done modifications to the image, didn’t you?
Have you done anything with the ClientCleanUp service or NetXclean?CG
Do you see the same thing with images from wyse.com? Could be something in the image. You are right, it should keep the old name during the image process. This could mean a corrupt hostname.arc in your image is conflicting, or a setting in your imaging files.
Any chance you’ve got a laptop or VM you can install a different WDM server to rule out an issue with your server?
-k
- You must be logged in to reply to this topic.