Using an alias for the /MS Collection Server Name
Was asked by our architect why we didn’t use a DNS alias name instead of the server name for pointing Forefront clients to the collections server. I couldn’t think of a good reason why not as it would make furture tasks some what easier.
The client get the name of the server from the Forefront policy if it’s not stipulated anyway, so I put in a DNS alias and fired a couple of client installs off using the alias rather than the server name.
So rather than using server1.chrismohan.com I used forefront.chrismohan.com.
So far, so good and the client machines are working and reporting as normal.

Leave a Reply