Hot answers tagged

7

You will have to run a STSADM script to move users from the OLD-AD to the NEW-AD, like this: STSADM –o migrateuser –oldlogin OLDDOMAIN\user1 –newlogin NEWDOMAIN\user1 –ignoresidhistory This will do just fine on SharePoint Foundation. But if you have a User Profile Service Application, you may run into trouble. My experience tells me it doesn't work ...


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


5

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 ...


4

Both addresses are valid; every object gets a @.onmicrosoft.com address.


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

This should do the trick SPWeb theSite = Microsoft.SharePoint.WebControls.SPControl.GetContextWeb(Context); SPUser theUser = theSite.CurrentUser; string strUserName = theUser.LoginName.ToLower(); string strUserName = strUserName.IndexOf('|') > -1 ? strUserName.Split('|')[1] : strUserName


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-...


3

I have found the answer guys use Remove-SPWebApplicationAppDomain


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: ...


2

The users from the old domain are still part of the site collection in something called User Information List. This list populates the people picker. You would have to delete the old users from the User Information List which can be found in http://SiteCollectionURL/_catalogs/users. When you have deleted the users from the User Information List, and the ...


2

Depends on how you're migrating content, but if you're using a 3rd party tool, you would need to use the tool's user mapping feature (e.g. map DOMB\JDoe to DOMA\JDoe). If using the built-in database attach approach, you would need to use: $user = Get-SPUser -Identity 'i:0#.w|domb\jdoe' -Web http://webUrl #Site Collection where the user is present Move-...


2

It would be better to go ahead and architect out the new 2013 farm, get it built, and proceed with the database attach upgrade. It will not impact the links of the site unless your URL changes. Your URL shouldn't have to change unless you are using the server name as the URL. (a lot of the links will automatically upgrade themselves anyway, but manually ...


2

First add the AD group into a SharePoint group. You can set the group setting "Who can view the membership of the group" in SP-Group-Settings to "Group Members". Then only members of the group can see the members of that group. Luckily you can ask if the current-user has the right to view a groups membership. So if the user can view the membership of the ...


1

The quick answer is yes to both. Here is a good read about SharePoint app domains: SharePoint 2013 Apps Domain vs Subdomains Towards the end, it shows you how to change the url to the app domain, which, should address your second question.


1

I'm investigating this myself at the moment - I had a similar issue. What it turned out in my case is that I created a few site collections a year ago while on contract at a client (as site administrator). Since then I left, and I assume my AD account was either suspended or deleted. On my return I had the same login credentials, but I suspect that my AD ...


1

Changing tenant URL for SharePoint Online is not possible (not right now at least). Only way to change change the URL of the private site collection (as in your case), is to cancel the old current Office 365 subscription and start with a new one. You'd have to look into ways to migrate content from domainA to domainB perhaps using some 3rd party migratio ...


1

URL: The App Model depends on the fact that each App has it's own domain. This ensures that Apps are isolated from the host SharePoint site collection and from other Apps. It also helps prevent cross-site scripting. Link to access App: Users access an App the way they would access a List or Library, from a link in Site Contents. Master page: Even though ...


1

Had the same issue and logged a call with MS. They said there is no documentation on the setup and configuration for this. In the end we Recreated our Farm so that it was in the same domain. Some helpful links that might help you: Configure People Picker in SharePoint 2013 SharePoint 2013: “Sorry, we’re having trouble reaching the server. “


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