I have a setup with two CM servers (I know, 3 would be better...) and want to designate one as the publishing/task server. I have read this question and answer Setting up multiple CM servers but my scenario is slightly different in that the CM servers use DFS to synch the file systems.

Must I disable DFS and use different configs for each server, or is it possible to use the same config on both servers (they are named CM01 and CM02):

<setting name="Publishing.PublishingInstance">
  <patch:attribute name="value">CM02</patch:attribute>

1 Answer 1


There is no need to disable the DFS. Because the Job Server (publishing/task) will mainly deals with Sitecore Items while the DFS is used for the files synchronization.

One thing to keep in mind is that when using the DFS, you will have a master server along with slave servers. So, file deployment should be performed on the Master Server so that it gets synchronized on the slave servers.

  • So do you confirm that it is harmless for the CM02 machine to have the Publishing.PublishingInstance setting set to itself. Nov 29, 2016 at 12:23
  • Yes. But just make sure that your scalability setting is setup properly. Nov 29, 2016 at 12:25
  • The Scalability config will need to be different. The Instance Name (Different from PublishingInstance) must be different for each server. Nov 29, 2016 at 13:17
  • 1
    @PeteNavarra AFAIK if the InstanceName field is left blank, then Sitecore defaults to Machine Name + IIS SiteName (see here newguid.net/sitecore/2012/…). Nov 29, 2016 at 13:31
  • 1
    Yep, you are correct. In that case you'll want to make sure your publishing instance also includes the appropriate machine name and iis sitename. I saw CM02 in the question thinking you needed to use custom instance names. =) Nov 29, 2016 at 13:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.