Bill732
asked on
Question about domain discovery
Hello,
I have a newbie question about domain discovery.
The short story is that I am setting up a development sharepoint server on my pc running windows 2008 r2 and hyper V virtual servers. At a previous employment I set this up following the popular guidelines suggesting creating Active Directory and using specific AD accounts for the different sharepoint services etc. But, at my new employment I was told not to set up Active Directory on my development box because then PCs in the company will discover it. They said to use local accounts instead.
Could you please explain this to me? Usually I can find lots of info on the net about stuff like this, but I haven't found much on this. Is the concern justified? How does it work?
FYI, my pc and virtual dev servers do not join the company domain.
Thanks very much,
-Bill
I have a newbie question about domain discovery.
The short story is that I am setting up a development sharepoint server on my pc running windows 2008 r2 and hyper V virtual servers. At a previous employment I set this up following the popular guidelines suggesting creating Active Directory and using specific AD accounts for the different sharepoint services etc. But, at my new employment I was told not to set up Active Directory on my development box because then PCs in the company will discover it. They said to use local accounts instead.
Could you please explain this to me? Usually I can find lots of info on the net about stuff like this, but I haven't found much on this. Is the concern justified? How does it work?
FYI, my pc and virtual dev servers do not join the company domain.
Thanks very much,
-Bill
If you create a private network on your VMs that are not accessible by anyone outside of your PC then iot matters not if you create an AD server as well as a sharepoint server. But clear it first before you do it :D
sharepoint account setup: http://technet.microsoft.com/en-us/library/cc263445.aspx
"I was told not to set up Active Directory on my development box" what do you mean by this? Set up AD... are you saying that you do not want to make the Dev server a member server of the production windows domain?
Also, what is the fear of discovery? Fear that Sharepoint with get discovered by the client... content on the servers in the production domian being crawled by the sharepoint server? The dev box being found in a browse list of client machines in the production domain?
Also, what is the fear of discovery? Fear that Sharepoint with get discovered by the client... content on the servers in the production domian being crawled by the sharepoint server? The dev box being found in a browse list of client machines in the production domain?
ASKER
I don't mean making the Dev server a member of the production domain. I mean following the typical SharePoint Development environment box suggestions (like in the link you sent). I can either create a virtual DC like Scott Hillier recommends in his Apress book. Or adding AD roll on the virtual dev sharepoint server etc. Just so I can create the different sharepoint service accounts just in my development environment.
I don't understand why I was told that would be a problem. The person here at work told me, "You don't want your development domain to be discovered by PCs in the company." I don't see how that could happen - or what that means exactly.
I don't understand why I was told that would be a problem. The person here at work told me, "You don't want your development domain to be discovered by PCs in the company." I don't see how that could happen - or what that means exactly.
ASKER
A guy here told me that on his PC that he uses as his personal sharepoint development server, he just uses one local account for all the sharepoint services. I had never done that before and didn't find anyone out there on net suggesting that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I would think, as Neilsr wrote, that a private network is not accessible outside my PC. If that is true, then I would rather follow best practices in setting up the development sharepoint server.
I'm thinking that if use the one local account approach it will cause problems when I go to deploy web parts, etc. into the QA environment. I'm probably wrong about that because they've being using this approach for years.
I thought I would ask others like you about it. I guess I'll ask the guys here more about it too.
I'm thinking that if use the one local account approach it will cause problems when I go to deploy web parts, etc. into the QA environment. I'm probably wrong about that because they've being using this approach for years.
I thought I would ask others like you about it. I guess I'll ask the guys here more about it too.
ASKER
Oh, I was writing while you were Neilsr. OK, I'm glad to get confirmation about that. Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to both of you. I really appreciate the explanations.