Deploying Across Domains

Hot Topic

Including CSV files
A Puzzle?
Integrate FxCop warnings and errors in visual studio developer edition
deploy/schema compare scripts - Option for checking IF EXISTS
application has compatibility issue running on Windows Vista
TF20033: You do not have permission to modify work items in the area
Calculate Emailaddress from multiple textboxes.
Click event
Select/Open Tree Node
Arrays???????

VS Team System

How to end loadtest when test completes
Set Dialog box control programmatically
FXCop looks for references.. Why..???
SerialPort 101 for a beginner
Security Problem with Importing a New Work Item Type
C#.net
Branching Strategy For Dynamic Environment
How to get access to the selected workitems in a query result document?
Delete content of txt file
QueryLabels error

Deploying Across Domains

A common scenario is to keep qa/production boxes out of the development domain.  I set up my TeamBuild service to run under a local user account and set up the same local username/password account on the boxes I need to touch as part of the deployment (TFS, QA and Prod box).  My build process copies the compiled files over and creates the virtual directory appropriately using the Web Deployment Project's dll -- specifically the CreateVirtualDirectory task.  However, my CreateVirtualDirectory task (not my copy operation) is failing in the situation where I'm using this local user account strategy between two boxes not in the same domain.  Is it something the CreateVirtualDirectory task is not doing; I'm not doing; or something inherently impossible about doing this programmatically from teambuild  

 

The error I get is "could not connect to server".  Thoughts

 

    

Answer this question

Deploying Across Domains

  • Crax123

    I'm not sure, but I'm guessing the problem is that the network service account is a machine account and there's no trust relationship between the machines in this situation. You may need to use a domain account.

    Buck



  • Duncan McC

    Somebody with some networking experience please educate me on this. Can you use a "network account" without setting up a trust between the domains -- which is why I thought you have production items in separate domains -- because we don't want things/hackers that infect one domain infecting the other, etc... It seems like this should work if I'm able to copy files from one machine to the other using this mechanism -- clearly it's not using domainName\userAccount for that. What is special about creating the virtual directory through code vs. copying files onto that machine through code I am able to connect to the box through the mmc snap-in.


  • xlordt

    Thank you for your replies both of you. I figured out what was happening by using the SDC Create virtual task rather than the WDP create virtual directory task because it was more verbose with the errors. As it turns out, there was no default web site on the QA box I was building to, and the WDP task assumes this. The mechanisms I described above does work.

  • Michael Barrett

    I am not sure if what you describe is "impossible". But I would definitely suggest using a network account, perhaps something created specifically for Team Build.

    My guess is that the local user names are actually different, because of the difference in Domain. Domain users get the name <domain>\<username>. Perhaps local users get a similar "fully qualified" name.

    Please let us know how you get it working.

    Thanks, Jason
  • Deploying Across Domains
Answer this question