Hi,The deployment manifest <soultion> tag has an attribute "DeploymentServerType", which takes either WebFrontEnd and ApplicationServer(not sure whats the default value though)<Solution DeploymentServerType = "WebFrontEnd/ApplicationServer" ResetWebServer = "TRUE" SolutionId = "GUID">Forall my server farm, I have done MOSS installation of type "complete" for all my servers. Then as per requirement I have enabled different services(WEF, search, index, CA) on different servers. In this case, how does the deplyment solution knows which serversare a WEFs and which are application servers? Does it determine bt type of services running on a system or installation type(complete/WFE)?Thanks,San

Honestly, I usually leave that attribute out. It is optional. I think the default is WebFrontEnd, but I am not competely certain. If you are just doing standard development of features or whatever, I think it is safe to leave out. It will deploy to any server on your farm that is marked as a web front end when you attached it to the farm.Thanks,CoreyCorey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth

Hi Corey,Idid the same thing, left that attribute out and the package got deployed in allthe servers in my server farm, which I did not want. I wanted that tobe deployed only two 2 WFEs ..What actually I wanted to know is, how the deployment package knows which servers are WFEs and which are application servers?Thanks...San

anyway I need to test this in VMs to know about this ...

I've spent some time looking at this and will post my findings shortly. What doesn't make sense is when you select ApplicationServer it appears that features do not get installed.