Where Guids depend on a particular environment.įorefront TMG (as his old brother, ISA Server) uses two SQL instances: MSFW and ISARS. HKLM\IsaStg_Cache\Arrays\\msFPCIntrArrayAddress The following registry values should be changed in the registry to the new IP-address: By the way, check the object Domain Controller, and make sure that addresses of the domain controllers are correct.Īs we found out later, not all settings Forefront TMG shows in the management console. Here, 200.100.100.50 is IP-address of the external connection. Actually, it necessary to check values of all underlying objects, but in my case three of them contains addresses from the old network: Array Servers, Managed Server Computers, and Remote Management Computers. On the right-hand side click the tab Tasks, choose the horizontal tab Network objects, and expand the node Computer Sets. Log to server, start Forefront TMG Management Console, expand the tree Forefront TMG (TMGServer), and click Firewall Policy. And now, we should change the following settings of Forefront TMG.ġ.
We changed the virtual network connection, and changed IP-address of Local Area Connection to 192.168.2.2 (and all other settings). Its first static IP-address is 192.168.1.2, and newly assigned address is 192.168.2.2. Let the server, where Forefront TMG is deployed, is called TMGServer. The reasons are obvious – we moved the virtual server with deployed Forefront TMG 2010 from subnet 192.168.1.x to the (test) subnet 192.168.2.x. Recently, I saw the following entry in Event log of the test external server:
0 kommentar(er)
