Hey gang, we setup our ConfigMgr 2007 R2 DPs to stream SFTs.
We recently decommissioned one of those DPs... and so to redirect
clients that might still load SFTs from the decommissioned server, we
setup a DNS record for another ConfigMgr 2007 R2 streaming DP.
IPCONFIG /flushdns, or restart the PC, and away we go, right?! The idea
is that clients "think" they are streaming from old server, but DNS
redirects to new server.
While the IIS logs show that clients are now attempting to load SFTs
(the new DNS record makes this happen), clients are now getting prompted
for credentials (IIS status 401 and 404 messages listed in the IIS logs
of the server that the DNS record points to).
So far unloading the VApp and publishing it again has been to only fix.
Seems a bit of a hassle, any chance there's a more stream-lined fix?
Thanks for the feedback, Al
