Hot answers tagged

5

You should pass the same user name as OldUser and as NewUser, note the IgnoreSID parameter. This will get new SID from AD for that account and update that in userinfo tables. Move-SPUser -Identity "DOMAIN\OldUser" –NewAlias "DOMAIN\NewUser" -IgnoreSID Source


4

Here is an article I wrote a while back to pull together resources for supporting multiple domains. http://www.mikeoryszak.com/sharepoint/supporting-multiple-active-directory-domains


4

This isn't possible with private site collections on SharePoint Online currently. This is because of the SSL requirement (in the E plans) for private site collections. There isn't a way to upload an SSL cert to SharePoint Online so that it can serve requests for that domain and HTTPS. You can map your vanity domain to your SharePoint Online public web ...


4

There is no white listing functionality that exists in SharePoint Online like that. Your option would be to Allow both external users who accept sharing invitations and anonymous guest links or individually manage access. I would rather do the latter. It isn't too much effort to add external users as necessary. My best practice is to create a new group on ...


3

How about using the following function, Microsoft.SharePoint.Utilities.SPUtility.ResolveWindowsPrincipal()? It has the following parameters:- webAppType: Microsoft.SharePoint.Administration.SPWebApplication inputType: System.String scopesType: Microsoft.SharePoint.Utilities.SPPrincipalType inputIsEmailOnlyType: System.Boolean There are two overloads, ...


3

As Steve B said, there's no problem having TFS on another domain. It will prompt you for credentials. We typically develop on SharePoint VMs that are also their own domains - thus they are completely independent. We have no problem with using TFS on our company domain, though it does help if you use Windows's option to remember your credentials. See ...


3

In general, security groups are used for permissions, but distributions are not. You can overcome this by mail-enabling security groups. In this manner, they can be used both for permissions and audiences. PLUS for an Exchange admin, you don't have the hassle of dealing with multiple groups with the same members for the two purposes.


3

I would try this way. if I know the Central Admin of sharePoint then I will check it from servers in the farm, which will list all the SharePoint Servers in that farm. Another approach, build a PowerShell script which will check and list if any of the servers in the domain has "SharePoint timer Service Installed". something like this http://www.experts-...


2

I'm not an AD expert, but we experienced something similar recently. We solved it by making the group a universal security group. Possibly also Global scope would work.


2

I use UserProfile to access this type of data. http://msdn.microsoft.com/en-us/library/microsoft.office.server.userprofiles.userprofile.aspx here's some sample code of using it with people picker private UserProfile GetExistingEmployee(string CurrentWebSiteURL) { UserProfile profile = null; using (SPSite site = new SPSite(CurrentWebSiteURL)) { ...


2

You can install SP2010 on DC but it is not recommended. If you don't have possibility to add more servers then you can go with the following architecture: SharePoint Server 2010 and Applications on one server. Domain controller and Microsoft SQL Server 2008 running on another You can even deploy SharePoint Server 2010/SQL Server in a single server farm ...


2

From the research I did, it appears that I do not need anything special for SharePoint Foundation website to run on an internet facing site. However, I need valid licenses for Sql Server and Windows Server. I also need to abide by Microsoft's EULA. Hope this answers the question for someone else.


2

You either have to add an entry for 'devsite' to your network DNS or modify the hosts file on all of the machines to point to the actual IP address of your dev machine. The 127.0.0.1 address would only work on the machine itself.


2

The root of the problem is that my computer is not on the same domain as the SharePoint server. This means that my InfoPath form will not establish a full trust with the server and therefore be unable to retrieve the data it needs. Once the form is published onto the site it resides on the same domain and this problem is eliminated. But man is it annoying ...


2

Do you have a lot of content in your SharePoint databases? What is your view on detaching content database, remove SharePoint API, install SharePoint with fresh install and connect content databases again?


2

This will break SharePoint. You'll have to re-install it (and preferably not on a DC).


2

You need a different certificate, wildcard certificate i.e *.contoso.com will only apply for 1st level, that means domain1.contoso.com or domain2.contoso.com but if you use in this case apps.domain1.contoso.com will bring you that error. http://blogs.msdn.com/b/kaushal/archive/2013/06/13/working-with-wild-card-certificates.aspx Hope that helps you


2

Yes you have to extend the WebApplication, this will create a new IIS site responding to the new URL, but serving up the same content and then you can assign the proper certificate to that on each web front end server. And you of cause also need to make the DNS point at the same IP.


2

SharePoint is able to use Windows Authentication as it is running on IIS. As a rule of thumb, the machine should be joined to the domain prior to running any enterprise level software install. Both SQL Server and SharePoint have ways to change the domain they are on, but they are not short processes. It is easier to install correctly the first time. ...


2

There is no supported way to redirect your public SharePoint site to another URL. Instead, you can manage DNS to make your public SharePoint site listen to requests for your domain - www.abc.com. Unfortunately this is not what you ask for.


2

Most probably the problem does not come from the SharePoint configuration, but from the SMTP relay you use. Do you use IIS 6.0 as the local SMTP? Does it then forward the email to an Exchange server or else? The local SMTP relay or the Exchange server configurations have to be investigated first.


2

I highly suggest you build a new SharePoint farm at d2 using the same farm topology. Then process migration from old to new farm. There are a lot of resource about migration but none (almost) for domain change. SharePoint is so tightly bind with domain name and it is very risky to change.


2

You can't add users to a AD domain group from SharePoint, you would have to have permission in your AD to edit the group. You can add AD groups to SharePoint groups, but you can't manage the AD group within SharePoint. Get a domain admin to add them or see if your AD group can be converted to an email enabled security group, then you can manage it from ...


2

You can use below snippet Get-SPUser -Web http://server/sites/yoursite | Where { $_.IsDomainGroup } AD group is treated as a special user. So this can be find using the filter IsDomainGroup $SPWebApp = Get-SPWebApplication https://*******.com/ foreach ($SPSite in $SPWebApp.Sites) { write-host -foregroundcolor green "Working on Site Collection: ...


1

It seems that there is no way to force standalone install after uninstall (except reinstalling the Operating System). I gave up and used the Complete install.


1

$farm = Get-SPFarm $farm.MigrateGroup($.oldlogin, $.newlogin) worked for me. I followed article: http://blogs.msdn.com/b/sowmyancs/archive/2012/01/07/migrate-users-groups-powershell-script.aspx?PageIndex=2


1

The actual Move-SPUser cmdlet works fine on individual users so I generally had success with that, however for AD Groups I found I couldn't use Move-SPUser on those, so I ended up having to re-nest groups with different names inside of the SharePoint groups. The main hassle with this was that I ended up creating AD groups with the same name as the ones that ...


1

When you say that it logs you in as admin instead - are you saying you should be allowed access anonymously or authenticated but just a lower priv account? I recently had an issue where we got challenged at root but okay if we went in direct at a lower level URL. Turned out I needed to switch anonymous access at the site collection AND web app level on then ...


1

If you want the additional users on the different domain to use Windows authentication,then yes you will need a trust relationship between the domains. You could also use Forms Based Authentication for the subset group if the trust is not an option for you.


1

It will not break the installation, but you may want to consider creating a new farm. It is possible to do a migration, but given the number of service accounts that have to be reconfigured it would probably be easy to configure a new farm and re-attach the databases to bring in the content.



Only top voted, non community-wiki answers of a minimum length are eligible