I just rolled out a slx754 web system with nt authentication enabled. At the last minute a request was made to change the server name to saleslogix on the url line for all clients. So we added DNS entry for "SalesLogix" to point to the ip in question and that worked. At this point our custom salesorders appeared to be working with sdata, the slxclient appears fine and slxwebrpt is working (note slxwebrpt is on a separate server).

Is this all i need to do? Are there "issues" I should watch for from other modulues ?

We have seen messages popup from the Desktop Manager "Could not process SendSLX message: Creating a proxy instance failed Inner exception: The remote server returned an error: (500) Internal Server Error."

Unless your Customizations include Absolute Links with References to the SERVER name (which would be a very poor design), using a DNS alias works fine.

Desktop Manager should work fine as well, but you may need to ensure you have the right path and that that instance is working properly.

And, since this is a per client setting, you may need to review each client that is generating errors.