PeterNic
12-02-2011, 04:13 PM
Just like with Linux appliances, by default the AppLogic APK sets the host name of the appliance to match the appliance instance name (role). This helps when you have 20 terminal windows open - makes it easy to remember where you are.
Since in Windows a reboot is needed to change the machine name, if you change the instance name of the appliance, on the next start, the appliance will go into maintenance mode and automatically go through a reboot.
Sometimes this is not what you want - e.g., if you want tighter control over the hostnames and/or are using Active Directory.
You can turn off the automatic hostname set up by editing the /lib/applogic/applogic_init script -- change
APK_HOSTNAME_UPDATE=yes
to
APK_HOSTNAME_UPDATE=no
This will ensure that APK will leave the Windows machine name (hostname) alone.
Another note on specifying the hostname when using the Windows VDS templates - the hostname should be just a simple name (e.g., mybox), not a fully qualified domain name (mybox.mycompany.com). It should also be 15 characters or less.
Best regards,
- Peter
Since in Windows a reboot is needed to change the machine name, if you change the instance name of the appliance, on the next start, the appliance will go into maintenance mode and automatically go through a reboot.
Sometimes this is not what you want - e.g., if you want tighter control over the hostnames and/or are using Active Directory.
You can turn off the automatic hostname set up by editing the /lib/applogic/applogic_init script -- change
APK_HOSTNAME_UPDATE=yes
to
APK_HOSTNAME_UPDATE=no
This will ensure that APK will leave the Windows machine name (hostname) alone.
Another note on specifying the hostname when using the Windows VDS templates - the hostname should be just a simple name (e.g., mybox), not a fully qualified domain name (mybox.mycompany.com). It should also be 15 characters or less.
Best regards,
- Peter