So, it looks like the problem you're having is that the DFS namespace isn't available when the primary DFS server is down. This is probably because the referral list for the namespace still points to the old server.
To fix this, you'll need to update the referral list to include the new DFS server. Here are the steps:
- Open the DFS Management console on the new DFS server.
- Go to "Namespaces" and select the namespace that's not available when the primary DFS server is down.
- Right-click on the namespace and choose "Properties."
- In the "Namespace Servers" tab, click "Add."
- Choose the new DFS server from the list and click "OK."
- Click "OK" to close the namespace properties window.
- Wait for DFS replication to occur to make sure the new DFS server is fully synced with the old server.
Once you've done all this, the referral list for the namespace should include the new DFS server. That means clients can access the DFS namespace even if the primary DFS server is down.
Oh, and one more thing: if you're getting rid of the old DFS server, you'll need to remove it from the referral list for all the namespaces it was served before you can retire it completely.