New answers tagged active-directory
3
It is not recommended that this be done for production deployments, primarily because of security concerns. If somebody were to compromise some of the admin accounts for SharePoint they could conceivably also take control of your domain and do a lot of harm.
For non-production environments and domains, this is fine and is frequently done (myself ...
1
It's not recommended, but possible. Check this video, should be useful for you:
http://www.youtube.com/watch?v=n0UVmSSG4dk
1
I hope this isn't production, it's not a supported practice to install AD on a SharePoint server. However, the error message you're receiving should be as simple as required services not running. Check Services and IIS and make sure everything is running. You might not be able to run them since they might be using accounts that no longer exist. When you ...
0
I fixed the issue by creating a new web application under a new account from central administration and creating my target site collection under the new web application.
For the site collection the primary administrator was the new account and the secondary administrator was the domain administrator account that I would be using in Visual Studio to deploy ...
0
As @BennySkogberg mentioned, you need to specify a UPN explicitly for the users you want to change. You will probably want to setup the Forest or Organisational Unit (tenanted) with a UPN Suffix. Once you have set the suffix, you should be able to select it under the user's Account name.
You can use ADSI Edit to modify the uPN Suffix property, or use ...
1
I don't know why this happens but I've seen it before. So much so that when I built my code on top of this I put a try catch in and had it do the command a second time before I was convinced that I didn't work as expected.
2
Not directly from within SharePoint, at least not without close collusion with your AD administrators as well as some aggressive scripting. Besides, you would only be protecting SharePoint and it sounds like this is really a much larger issue that affects the whole company.
A better approach would be to look at your firewall or routing hardware and see if ...
0
you can manually manage the list of users who are allowed to access the site. Instead of using All Authenticated Users create a new Group, insert all of the employees into it, and when they leave/are terminated you can remove them from it.
0
Unfortunately, I don't think you can have your desired setup and you have to fully enable FBA authentication on zone1.
If your issue is merely avoiding confusion about authentication (not presenting a choice of 2 authentication providers), then I would suggest using the OrbitOne SharePoint Auto SignIn solution at http://spautomaticsignin.codeplex.com.
I ...
0
Ok, so it turns out the problem was with the auto-magical feature of reading domain information from the server.
When the previous PDC failed and the domain was transferred to another DC, it looks like the synchronization between the other DC's and the DC that sharepoint was installed on failed.
Force removing the DC from the domain, cleaning up the ...
Top 50 recent answers are included
