Hi All there..it's me again and again
During my SQL Server 2008 setup, i received this 3 following warning. Unfortunately this is only warning not failed
Below are the warning :
1 .Rule "Distributed Transaction Coordinator (MSDTC) clustered" generated a warning. The MSDTC service is not clustered. Some features of SQL Server will fail to work when clustered if the MSDTC service is not clustered and bla bla bla
2. Rule "Microsoft .NET Application Security" generated a warning. the computer cannot access the internet. there might be delays in starting a .NET application like management Studio. If navigate to
http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl and are prompted to download the
MicrosoftRootAuthority.crl file you should not have .NET security validation issues. It is not necassasry to download the MicrosoftRootAuthority.crl file.
3. Rule "Network binding order" generated a warning. The domain network is not the first bound network. This will cause domain operation to run slowly and can cause timeouts that result in failure. Use the Window network advanced configuration to change the binding order
For warning no.1, am i supposed to configure MSDTC Resources just like in Clustering win server 2003? Meaning do i need to create "MS DTC IP address", "MS DTC Network Name" and "MS DTC"??
For warning no.2, i have no idea what am i supposed to do
For warning no.3, i did change the binding order by doing placing the Public NIC above Hearbeat NIC under the tab "Adapter and binding" in "Advance Setting" option for both nodes....
TQVM for assisting me in advance
During my SQL Server 2008 setup, i received this 3 following warning. Unfortunately this is only warning not failed
Below are the warning :
1 .Rule "Distributed Transaction Coordinator (MSDTC) clustered" generated a warning. The MSDTC service is not clustered. Some features of SQL Server will fail to work when clustered if the MSDTC service is not clustered and bla bla bla
2. Rule "Microsoft .NET Application Security" generated a warning. the computer cannot access the internet. there might be delays in starting a .NET application like management Studio. If navigate to
http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl and are prompted to download the
MicrosoftRootAuthority.crl file you should not have .NET security validation issues. It is not necassasry to download the MicrosoftRootAuthority.crl file.
3. Rule "Network binding order" generated a warning. The domain network is not the first bound network. This will cause domain operation to run slowly and can cause timeouts that result in failure. Use the Window network advanced configuration to change the binding order
For warning no.1, am i supposed to configure MSDTC Resources just like in Clustering win server 2003? Meaning do i need to create "MS DTC IP address", "MS DTC Network Name" and "MS DTC"??
For warning no.2, i have no idea what am i supposed to do
For warning no.3, i did change the binding order by doing placing the Public NIC above Hearbeat NIC under the tab "Adapter and binding" in "Advance Setting" option for both nodes....
TQVM for assisting me in advance