Hot answers tagged active-directory
7
Most likely it is because the browser is not detecting that the subsite is in the proper domain. in IE, this is accomplished by making sure that everything that is *.intranetdomain.com is in the "Local Intranet" zone, which is usually done via Policy. It can also be done manually by going to Tools-Options-Internet settings-Security-Local ...
6
Here is a working way of doing it:
Backup all content databases
Uninstall SharePoint
Migrate server to new domain
Reinstall SharePoint
Restore content databases
Change site collection admins (there are still in the old domain)
Use Move-SPUser to migrate users from old domain to the new one
As you can see, this is not something simple, so you may include ...
6
I didn't want to take credit for answering my own question so i did it as an edit but the following resolved MY issue:
UPDATE: The issue had to do with the fact that the Security Token Service was not functioning properly. I'm still not sure that i'm clear on how to correctly change managed service accounts, passwords, etc. But I DID get it working. I guess ...
5
Have you already set up synchronization from AD and got that working?
You need to
upload images to AD. I use PowerShell for this
$photo = [byte[]](Get-Content C:\abc.jpg -Encoding byte)
Set-ADUser myUser -Replace @{thumbnailPhoto=$photo}
setup mapping in User Profile to thumbnailPhoto
run Update-SPProfilePhotoStore -MySiteHostLocation http://my ...
5
SPUtility.ResolvePrincipal can do this - but I can't guarantee that it'll be fast.
It should be something like:
SPPrincipcalInfo user = SPUtility.ResolvePrincipal( webApp, null, "email", SPPrincipalType.User, SPPrincipalSource.Windows, true);
UserProfileManager profileManager = new UserProfileManager(serviceContext);
if ...
5
As you need to move your SQL servers, this can and will be treated as a simple SQL server move, which requires a farm migration. This is because the domain name of the SQL server changes.
For farm migration, you can find instructions at http://technet2.microsoft.com/Office/en-us/library/42511e01-ecdd-4dc5-b06f-35aaada8a5d81033.mspx?mfr=true. Make sure you ...
4
The User Directory Web Part from Bamboo might do this for you.
http://store.bamboosolutions.com/pc-41-1-user-directory-web-part-release-13.aspx
Otherwise, you can roll your own if you have development capability. There are tutorials out there to do this, such as here: http://sharepointrookie.wordpress.com/2008/07/13/display-site-members-from-ad-groups/
4
I believe that James is wright on. When you build a WSS instance it will pull in details from AD. However, changes after the fact don't update the user properties in WSS 3. This is supported in MOSS 2007 and greater. I used a product that was able to overcome this limitation. Here is a link
Simego
4
You can use AD security groups for setting permissions on Sharepoint sites, lists and items. Some additional recommendations can be found at http://technet.microsoft.com/en-us/library/cc261972.aspx
It is possible with some simple permissions planning. You can create Sharepoint group HelpDesk and then set this group to have admin permissions on every site. ...
4
You can't use distribution groups for security in SharePoint. If you're doing this with Group A, then this likely explains the difference you see for this group's members.
SharePoint does treat AD groups as SPUser objects within the farm so sometimes it can be hard to trace a user's permissions. That said, if they are a member of a security group and you ...
4
Where is your code running? Web part, application page etc?
Regardless, you can probably do something similar to the following
try
{
//first get the SPGroup you want to add users to
SPGroup addToGroup = SPContext.Current.Web.AssociatedVisitorGroup;
//now loop through each entity in your user picker
foreach (PickerEntity entity in ...
4
If you just want to add all users, just add NT AUTHORITY\authenticated users
If you want to add every user individually, you have to get users (maybe as Principals) from AD, and add them to a group in SharePoint.
var principal...
var loginName = @"MYDOMAIN\" + principal.SamAccountName;
var name = principal.DisplayName;
...
4
What that usually means is that your Active Directory isn't configured or managed the way that SharePoint expects. Grab your AD guy and have him sit next to you while you go to Central Admin -> Applications -> Service Applications -> User Profile Service. On the dropdown next to your default AD connection, there will be an option called "Edit Connection ...
4
Why not just create an AD group called something like 'MYDOMAIN\eCommerceBuyers'. Grant that group the desired permissions in SharePoint and then on the eCommerce side, simply add the users to the 'MYDOMAIN\eCommerceBuyers' domain group?
That bypasses the need for the two systems to communicate at all and lets you centrally manage membership outside of ...
4
I think System.DirectoryServices requires an manual reference to System.DirectoryServices.dll which can be done just by right clicking your project in solution explorer -> Add Reference -> in .NET Tab,
select "System.DirectoryServies.AccountManagement".
Now, you should be able to import System.DirectoryServies.AccountManagement namespace.
If you still ...
4
The below code access current user's department and manager from AD:
SPSite _site = SPContext.Current.Site;
ServerContext serverContext = ServerContext.GetContext(_site);
UserProfileManager myUserProfile = new UserProfileManager(serverContext);
UserProfile currentUserProfile = myUserProfile ...
3
Of course, you could.
Some key articles for you to start with:
SPSecurity.RunWithElevatedPrivilegies - this will allow you to elevate privilegies for current user
SPFieldUserValue and SPFieldUserValueCollection - these classes will help you to extract values from "Person or group" column.
SPWeb.EnsureUser method - will help you to ensure that AD user is ...
3
SharePointBoost sells several web parts for working with Active Directory including the Site User Directory part that does exactly what you are talking about. From their site:
I am NOT affiliated with them in anyway, but I like their stuff :)
There is also an opensource project on CodePlex (http://adselfservice.codeplex.com/) with a Profile Manager and a ...
3
I've planned something similar, that we are testing now. We have SP deployed in its own network space with dedicated AD deployment with a one way trust back to the production AD. External users are added to the SharePoint AD while internal users are authenticated via production AD.
With this setup you only need one authentication provider, you can use ...
3
You need to implement single sign on (SSO). Robert Bogue has a good step by step.
http://www.thorprojects.com/blog/archive/2008/08/02/moss-single-sign-on-setup-step-by-step.aspx
3
Users are stored on User Profile Service(UPS) and in User Information List.
Users get stored on the User Profile Service when you do a UPS sync which imports user profiles from Active Directory. Normally, this is how it's setup. You can add, update, or delete the user profiles manually.
Users get stored on the User Information List only when they access ...
3
This can be achieved by using Search Scopes.
You will have to create a custom search scope (Eg:"People Search") in Search settings of the site.
Add a rule for the scope and select Property Query as the scope rule type.
If you have an AD property that is set for users coming from the phone system, select that property and select the value that is brought ...
3
You can have User profile synchronization and schedule the synchronization incremental timer job with the frequency you need.
3
Open ADSIEdit and open the properties of a user in your environment that has this information completed. Scroll down the list of properties until you find the one that has that information in it. Once you find it, look at the property name. It often is not what it is labeled in the ADUC forms. This is the name of the property you want. Once you have this ...
3
Considering the fact that there could be lots of users in Active Directory, I reckon that the best approach here will be to use SharePoint search, sort by Hire date descending, and select only top N users. Then, you can display results, for example using DataViewWebPart.
It is not an easy way to achieve the goal, but it is preferrable. Here are some links ...
3
Don't think you can do it with a calculated column, but you can use a list workflow to set a text field.
Add a Set Field in Current Item action. Configure the value with User Profiles as data source and select the Name field from source. Then match the Account Name field (only option available) to the column with your User ID (assuming that the user id is ...
3
I guess there is a problem with the profile synchronization.
I would recommend to start the profile synchronization manually and check if there is a problem
3
You will need to load it from the User Profiles and not the SPUser object.
SPServiceContext svcContext = SPServiceContext.GetContext(site);
UserProfileManager profileManager = new UserProfileManager(svcContext);
UserProfile profile = profileManager.GetUserProfile(accountname);
string department = profile["department"].Value;
3
You also can use the SPUser and SPUserCollection Object to iterate through all user profiles
using Microsoft.SharePoint;
using Microsoft.Office.Server.UserProfiles;
using Microsoft.Office.Server;
using System.Web;
here is the code:
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite siteCollection = new ...
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible
