Noob alert: Window's renaming issue

[Fred Sawyer]

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,

   

[Marat Komarov]

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

[Fred Sawyer]

Hello Marat,

Thanks for the quick response.  So let me give a little background and why I believe the name change is being kicked off by the Sclarizr agent.  We created our Windows AMI's more then 4 months ago and have not updated them.  The same AMI's have been in play and we use to be able to re-name a new instance with out issue.  Those same AMI's are still in play.  I did look into the EC2Config and that is not it, plus I believe if it was the EC2Config the system would be getting re-named with a new dynamic name and not set back to the name the system originally spun up with.  I have also ruled out Salt as a possible source of the issue by disabling the service.  Here are the steps I took on both Server 2008 and Server 2012

Server 2008

WIN-IQQHM9EDOGV -> rename01, rebooted 

When logging back in system name has been changed to rename01

Pending name change back to WIN-IQQHM9EDOGV

Reboot to clear pending name change back to WIN-IQQHM9EDOGV

Log back in, stop Scalarizr and Scalr Update Client

Set Scalr Update Clint to manual

rename system to rename01 -> reboot

Log back in, system name is rename01 no pending name change

reboot

Log back in system name is still rename01

set scalr update client to automatic and reboot

Log back in have pending name change back to WIN-IQQHM9EDOGV 

Server 2012

WIN-6BP2QTV64P3 -> rename to rename02, rebooted

When logging back in system name has been changed to rename02

Pending name change back to WIN-6BP2QTV64P3

Reboot to clear pending name change back to WIN-6BP2QTV64P3

Log back in, stop Scalarizr and Scalr Update Client

Set Scalr Update Clint to manual

rename system to rename02 -> reboot

Log back in, system name is rename02 no pending name change

reboot

Log back in system name is still rename02

set scalr update client to automatic and reboot

Log back in have pending name change back to WIN-6BP2QTV64P3

So it seems to me the cause and effect of the behavior is when the Scalr Update Client is set to automatic, the system will revert to the original name post sys prep.  But with the Scalr Update Client set to manual the system name change sticks, regardless of the number of reboots.  Since you mentioned Windows computer name management, is there some sort of settings or config file I can check that is related to Scalr server side or someplace on the client?   

[Marat Komarov]

Fred,

Scalarizr maintains server computer name persistence. If hostname was not configured in Scalr, then during initialization we get current computer name from OS and store it in Scalr. That's why you see computer name reset to initial value.

So the general rule is manage compute name through Advanced FarmRole settings in Scalr, or apply it in OS before Scalarizr startup.

Regards,

Marat 

[Fred Sawyer]

Thanks Marat, that is exactly what I was looking for.  What's odd is we had Windows system being spun up for at least two months where users were able to rename the systems from the system with out the Scalarizr agent reverting the name.  Either way now that I know how this is suppose to work we will notify our end users.  Thanks again!