Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am a Domain Admin and am trying to support BYOD with computers that will also be domain connected. The problem is that once I domain join a PC, the "zone" changes to "domain", while Homegroups require to be set to "home" in order to work correctly.

How can I get HomeGroup connected machines "talk" to each other while domain connected?

In this scenario, imagine a HomePC that is VPN'ed into work, and a work desktop both running Windows 7 Enterprise or Ultimate. I would like the user's files to be replicated between home and work, (but off our file server).

share|improve this question

It is by design that a domain joined PC cannot connect to a HomeGroup on the same network as that would allow the circumvention of domain-specified security policies and the like (as well as cause confusion about what sort of authentication the machine should use on that network).

This TechNet article tells you how to configure domain joined PCs for use in a homegroup when at home, which you might be able to extend the PCs you're trying to use this method on by adding another NIC... but that would surely complicate things unnecessarily for what you're trying to achieve.

I think you might need to look at a better way for the remote machine to access files - have you tried using Offline Files against the file share? Saving Windows Credentials to the Credential Manager should suffice for authentication purposes.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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