|
Hi Jason, I feel your pain. We originally started out with a root domain and then a number of our divisions decided to establish their own child domains under it. That was a few years ago. Now, they have also felt the pain when confronted by their local users who have accounts in both the child domains and in the root domain and they can’t keep the accounts straight! They are slowly migrating back to the root domain where each user only needs the one account and has the ability (if authorized) to access resources both in the root and child domains. The migrations are not easy. I look forward to the day when we are a fully collapsed domain. Tell your Director of Technology he is on the wrong track and that going back and doing it the right way later is going to be long and painful. Better to do it right the first time (and stick to your guns on the OU model!). Just my $.02
Mike Thommes
-----Original Message-----
Hi everyone. I have been migrating remote sites from Netware to Win2k3 for the last 2 months. I have been recently vetoed by the Director of Technology and I am being forced to migrate all sites into child domains as opposed to the OU model I had initially started. I have a DFS share where I keep all msi applications deployed through GPOs. I want to retain this structure as the MSIs are reusable from site to site. The problem I am having is creating the DFS share. Every time I attempt to create the DFS I get “The request is not supported” Error on the final setup page for DFS.
Does anyone know if there is something I need to enable in order to create a DFS share between child and parent domains? It worked fine under the OU model so I am thinking that the change from OU to child domain model has maybe left some crap behind that could be causing this as well. Anyone have any ideas?
Thanks in advance, J |
Title: RE: [MVP-Directory Services] October MVP Awards
- RE: [ActiveDir] DFS and child domains Thommes, Michael M.
- RE: [ActiveDir] DFS and child domains Almeida Pinto, Jorge de
