My current assignment is with a client that has a system consisting of multiple components where each component is a separate .EXE. This wouldn’t be so bad except for the configuration problem that is created. Each component has its own config file and there is a requirement for some consistency between the config files for some values. In addition, the system is deployed to multiple environments and clients.
Configuration is a nightmare and we’re still doing it manually.
This past week, one of the team members thought of the idea of using aliases instead of referring to actual machine names (for file and application location). The thought was that we could define the aliases in the Hosts file and reference the loopback address (127.0.0.1).
Using the Hosts file works well for HTTP but has no affect on UNC paths.
Luckily this client has an infrastructure group and they were able to help us out. They identified four registry entries that have to be changes in order to create aliases for the local machine.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new Multi-String value called OptionalNames. Enter one or more aliases, one per line.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new DWORD value called DisableStrictNameChecking and set to 1.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new DWORD value called DisableLoopBackCheck and set to 1.
Add a new Multi-String Value BackConnectionHostNames. Enter one or more aliases, one per line.
You’ll have to cycle the machine for the configuration to take affect.