(imported topic written by SY57_Jim_Montgomery)
Hey guys,
Glad to see 8.0 has been pushed out. I’m reading through the documents now, and it looks just great!
Something I’m stumbling on is how sites and domains interact and differ. Can I get a picture or an explanation showing how these work, and how one might manage them in an enterprise?
Thanks,
–Jim
(imported comment written by SystemAdmin)
Hi Jim,
Domains can contain content from multiple sites. Computers are still subscribed to individual sites. The domains allow us to organize the interface in a way that makes sense for the content.
I’m going to use Patch Management as an example, as most of our users are subscribed to some content related to this domain. Let’s say you are subscribed to the Patches for Windows, Updates for Windows Applications sites, and Patches for Mac,. You subscribe your Windows machines to the first two sites, and your Mac machines to the last site. You can do this in the sites node under the “All Patch Management” folder in the Patch Management domain, or the sites nodes in BigFix Management and All Content.
The content from these sites (and any other Patch sites to which you are subscribed) are displayed under the Patch Management domain. The Application Vendors node will show you content related to any application, regardless of which site it comes from. For example, the “Apple” node will contain iTunes patches for both Mac and Windows operating systems. The OS Vendors folder will break down both application and OS patches by Operating system. So the Microsoft node will contain all OS and Application patches that apply to Windows machines.
Hope this helps.
(imported comment written by SY57_Jim_Montgomery)
Your explanation helps a lot. Thanks.
And now for some follow up. 
Do I define my custom fixlets to belong to a particular domain or set of domains? If something doesn’t have a domain assigned (like custom content I import from my older version) which domain does it show up in?
–Jim
(imported comment written by SystemAdmin)
You can assign a fixlet to a single domain, and in that domain it will appear in the "All
Domain Name
"->“Custom Content” node. In addition, the “All Content” domain contains every fixlet and task you create in any domain (as well as your pre-8.0 custom content). The domain attribute defaults to the domain you are currently viewing.
(imported comment written by SystemAdmin)
We recently upgraded to v8. It looks like all our 7.2 custom sites were automatically put into the Bigfix Management Domain. My NMOs seem to have trouble with custom sites now. Do I need to change custom sites to the All Content domain for NMOs to use them successfully?
I’ve read the help files on Domains, however the examples were about the stock external Bigfix domains. Is there documentation on how custom sites and domains interact? Some best practices, etc.?
(imported comment written by BenKus)
Hey JonL,
Domains are simply a way to categorize and view Fixlet sites… but Fixlet sites (and custom sites) should continue to work exactly the same as they did in previous versions (this includes the permissions scheme which is site-based and not domain-based). Can you give more info on the issue you are seeing with your NMOs and custom sites?
Ben
(imported comment written by SystemAdmin)
I have a custom site and a NMO that has Read/Write access to it. It worked perfectly prior to 8.0 upgrade. After the 8.0 upgrade, the NMO can create custom content in the custom site and computers in that site report it as relevant. If the NMO takes an action on his custom task in the custom site to computers in that site, the target agents ignores the action. The action ID is not displayed in the client log. Now if I, as MO, issue an action on the same custom task that the NMO created, targeting the same machines, they immediately execute the action. The NMO action remains “not reported”.
(imported comment written by SystemAdmin)
I noticed that custom sites from 7.x come over into 8.0 in domain Bigfix Management by default. Is that normal/expected behavior?
I even tried changing the domain of the custom site to All Content, then rerunning the experiment in my previous post with the same result.
Is there a bug in the way custom site actions are issued for NMOs in v8.0?
(imported comment written by BenKus)
Hi Jon,
I don’t know of any bug, but I don’t think it is related to domains… Sounds like you might need a support call to look into this…
Ben
(imported comment written by SystemAdmin)
Is anyone else having issues with NMO actions in custom sites after upgrading to v8.0? The scenario (3 posts up) I listed can be easily reproduced in my environment.
(Ben, I did send debug logs and screen shots of the reproduction to Weylan.)