I honestly don't know :) From: [email protected] [mailto:[email protected]] On Behalf Of Dylan Tusler Sent: Friday, 10 July 2009 10:21 AM To: [email protected] Subject: RE: Changing a TFS Server Name
When I referred to the "Manage Permissions" screen, I meant the page you go to in a document library or list in Sharepoint to manage security on that page (actual link in our system is "Permissions for this document library" for example.) However we were having issues with many other links. If I accessed the site via the FQDN, this was never a problem. But if I went in with the new short name (http://tfs1 instead of http://ourserver.network.internal) then accessing the permissions page resulted in being transferred to a new url (http://ourserver/someotherstuff) that was the server name without the FQDN. Well, I did some more digging this morning in the Sharepoint admin site (http://tfs1:17014 or something, in our location.) Once I managed to log in, under Operations and Alternate Access Mappings, I discovered there was a "Default" mapping of http://ourserver to http://ourserver This would only be meaningful within one of our domains, and wouldn't work in any of the others. So I changed it to a "default" mapping of http://tfs1 to http://tfs1 That seems to have resolved the permissions issue above, along with some other issues that had to do with http://tfs1/Sites/MyProject failing to automatically redirect to http://tfs1/Sites/MyProject/default.aspx and instead redirecting to http://ourserver/Sites/MyProject/default.aspx I still have my ATUri set to the FQDN, and don't know why I can't change that, or whether it will be a problem. However, for the moment, all is quiet. Incidentally, I noticed in several places that the reference to the FQDN is cached locally on client machines that use Team Explorer. The old URL works fine, so it's not a priority to clean everyone's caches. Will these fix themselves in time though? Or will they someday require a manual intervention? Dylan. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Mitch Denny Sent: Friday, 10 July 2009 10:03 AM To: [email protected] Subject: RE: Changing a TFS Server Name Not exactly - it can be hard to figure out what is going on when environment changes are at play. Actually - just re-reading what you have written here - what Manage Permissions screen are you talking about? Screenshot. From: [email protected] [mailto:[email protected]] On Behalf Of Dylan Tusler Sent: Friday, 10 July 2009 9:10 AM To: [email protected] Subject: RE: Changing a TFS Server Name I tried using the tfsadminutil configureconnections command to make this change. After remapping the relevant urls, everyone started getting a load of "TF30045: The instance information has not been configured or is not available for this Team Foundation Server." errors. I set the ATUri and PublicATUri back to the old vlaues and the errors went away. I left the other urls as they were changed. Phew! Can anyone explain what happened there? Dylan. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Mitch Denny Sent: Thursday, 9 July 2009 4:21 PM To: [email protected] Subject: RE: Changing a TFS Server Name Hi Dylan, You might need to use TFSAdminUtil to change some of the values in the service registry. OR put domain suffixes on the local machines (if I understand correctly). From: [email protected] [mailto:[email protected]] On Behalf Of Dylan Tusler Sent: Thursday, 9 July 2009 3:35 PM To: [email protected] Subject: Changing a TFS Server Name We have a TFS server that previously has been accessed via a fully qualified domain name eg: http://ourserver.org.internal:8080 This still works, but new access has been set up for a new domain and a new shorter name has been established that is accessible from everywhere on all our networks eg: http://tfs1:8080 I'm looking to fully purge TFS of references to the old domain, but I can't remember where the information on doing this lives. Searched MSDN and all I came up with was the same old guides to migrating TFS, but we're not doing that. It is staying put, but the name of the server can be changed. Some parts of TFS still remember the old server name, and so they don't work so well in the new domain. Also some bits of sharepoint react oddly if you access the sharepoint site with the new domain. For instance, opening a "manage permissions" screen, which causes the url to change from: http://tfs1/Sites/ProjectName/SomeOtherGuff... to http://ourserver/Sites/ProjectName/SomeOtherGuff... which doesn't work, as it is not a fully qualified domain name. ta Dylan Tusler Team Leader - Development, Data and Integration Unit Information and Communications Services Branch Sunshine Coast Regional Council ph: +61 (0)7 5441 8202 "Your Technology Solutions Partner" ****************************************************************************************** To find out more about the Sunshine Coast Council, visit your local council office at Caloundra, Maroochydore, Nambour or Tewantin. Or, if you prefer, visit us on line at www.sunshinecoast.qld.gov.au This email, together with any attachments, is intended for the named recipient(s) only. Any form of review, disclosure, modification, distribution and or publication of this email message is prohibited without the express permission of the author. Please notify the sender immediately if you have received this e-mail by mistake and delete it from your system. Unless otherwise stated, this email represents only the views of the sender and not the views of the Sunshine Coast Regional Council. ******************************************************************************************* mail5.2.13 ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists
