Fred, There were no changes in Windows computer name management between 4.6.4 and 4.8.1: Agent set computer name using WMI Win32_ComputerSystem class, name is permanent and applied with a next reboot.
Maybe EC2Config, or some other tool resets it? Check that you don't have "Set Computer Name" checked in EC2Config service settings. Regards, Marat On Thursday, August 11, 2016 at 12:37:43 AM UTC+3, Fred Sawyer wrote: > > Hello Group, > > I have been trying to track down an issue where Windows Server 2008R2 and > Server 20012R2 images in AWS running Scalarizr agent version 4.8.0 and > 4.8.1 are unable to be renamed without reverting back to the original > dynamic name after a reboot. We have some older systems (spun up a month > of two ago) were we were able to rename the system and the rename stuck > with the system after multiple reboots. I believe these systems were > originally were lunched under Scalarizr agent 4.64 or 4.6.6. > > At this point I have narrowed it down to the Scalarizr being responsible > for renaming the system after a name change. Being new to Scalr I am not > sure if: > 1. This is a known expected behavior > 2. There is a setting on the agent that controls this behavior > 3. There is a setting server side that controls this behavior > 4. Possible bug in the new Scalarizr agent or a bug in the old Scalarizr > agent > > Our goal is to let our end users rename a system to something a bit more > friendly then the dynamic name given to the system during first boot after > being packaged up in the sysprep process. Can any one help me with this? > > Thanks, > > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
