Change the issuer name in the OpenIDConnect recognition document on Windows Server 2016 ADFS

I set up ADFS on a Windows Server 2016 and the identification document looks something like this: https://ad.nexgen.am/adfs/.well-known/openid-configuration

You can see that the name of the exhibitor is given in capital letters "AD", which leads to my OpenId client reporting an error: The name of the exhibitor does not match the authorization.

As mentioned here, the issuer name distinguishes between upper and lower case: https://stackoverflow.com/questions/43626944/getting-discoveryclient-fails-with-issuer-name-does-not-match-authority

For some reason, the OIDC client doesn't seem to like the authority URL in uppercase, and I feel that it will be converted to lowercase. Everything works fine when I tell the OIDC client not to validate the issuer name, but it seems like a hack to me.

An attempt was made to change the ADFS service properties through the user interface and to set the "Federation Service Name" and "Federation Service ID", which does not appear to update the issuer in the discovery document.

I understand that the computer name is in uppercase, which is why this happens, but I really don't want to go there as this is a domain controller and have read horror stories about renaming a domain controller.

Any other suggestions?

2016 – Export SharePoint blog posts to SharePoint online pages OR Word / PDF

SharePoint 2016 offered the blog site template for sharing knowledge and other material. This content can be a problem when migrating to SharePoint Online. How do I export the content and transfer it to SharePoint Online Modern Pages or to PDF / Word documents?

Sure, you could do it by hand and waste dozens of hours. But it would be nice to have a path by automatically exporting and importing the content.

Upgrade / Migration / Site -> Question about the site collection in Sharepoint 2010 and Sharepoint 2016

Hope for a few thoughts / instructions on how to approach this. I am in the middle of a project to upgrade / migrate an SP2010 environment to SP2016. Because of the gaps in the versions, the approach is to deploy an SP2016 environment, build the required topology, and then actually migrate the content from the old environment to the new environment using a migration tool (most likely Sharegate).

Existing use is fairly simple (there isn't much customization), but the volume data isn't trivial – it's at least a few hundred GB, currently all in a single content database. For this reason, it makes sense to reorganize a little as part of the migration and, for example, to ensure that website collections have their own database.

However, the question / guidance: There is a sub-site of the main site collection with a lot of content, and I would like to move this to a separate site collection so that your data can go to a separate content database. However, the problem is that the URLs must remain unchanged after the migration because they are linked to another system.

I will try to illustrate! At the moment there is an SP2010 server that we call SP2010SERVER. There is a CNAME in DNS that points to (for example, AFAIK configured with AAM) SHAREPOINT. At the moment you can search the content in SP2010SERVER with the DNS name of SHAREPOINT. There is a subsite that we call SUBSITE1, and the URLs for this are, for example, http: // sharepoint / subsite1. (Note: there are many other subsites and site collections with managed paths, etc.)

We have the new SP2016 server; That is called SP2016SERVER. When you are done, you should change the DNS record so that SHAREPOINT now points to SP2016SERVER.

I have to move the current SUBSITE1 to my own site collection in the new environment, keeping the URL of http: // sharepoint / subsite1. Migrating the content to the root site of a new site collection is fairly trivial in my opinion, but the question is how to keep the URL. I can't use a managed path (afaik) because, for example, I configured "subsite1" as a managed path that still needs a site collection name after the path.

I saw the hostname (d) site collections as a possible solution. In this case, you might be able to provide a URL for the site collection, but I haven't used it before, and all examples typically use some kind of subdomain.domain.tld. Enter setup.

Would that work for my needs? If not, are there alternative solutions or options?

I imagine I could do the same with some kind of IIS magic / redirection, etc., but hoped to avoid this if possible.

Thank you for all thoughts / help!

Performance – SQL Server 2016 – unexpected privileged time bursts

MS SQL 2016 SP2 CU8 + Always on.

1 CLR module (occasional use, no correlation with the problem)

I am looking for methods to find the reason for such behavior. DBCC FREEPROCCACHE solves. After about 10 such "solution attempts" I have to initiate failover. If not, query processing may stop.

I tried not to remove all plans, but only some from the cache. I don't have any steady progress here yet.

Does anyone know a way to analyze privileged time usage? And – yes – privileged time is consumed by the sqlserver service, confirmed.

The current workaround runs FREEPROCCACHE when the privileged time is at least 7% greater for the 10 seconds and the weekly manual failover. But this approach is not good enough for me.

Typical reproduction

Active Directory – Where can I find the "Create Computer Object" permission in Windows Server 2016?

I'm trying to pre-deploy the cluster name object for the cluster I'm creating. I look at the steps provided here (https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731002(v= ws .10)? Redirectedfrom = MSDN # to-prestage-a-cluster-name-account), but in the Permission Entry window (Active Directory Users and Computers> CNO> Properties> Security> Advanced> there is no permission to create a computer object Add)

These are all of the permissions listed in the window

I'm just wondering if this was renamed to a completely different permission in Windows Server 2016.

I have used the local and domain administrator accounts and I still cannot find the authorization.

Thank you in advance for your help.

Upgrade – Migrate a SharePoint 2013 subsite to 2016

What is the error you get when performing content database migration? Please let him know here. You can also refer to the following article for general troubleshooting for content database migration:

SharePoint migration: basic tips and tricks in the migration project

As a second approach, you can use a third-party migration tool such as Sharegate, Metalogix or Microsoft SharePoint.

Sharegate and Metalogix trial is available, you can download it and Microsoft SharePoint Migration Tool is a free version, you can use it too.

Sharepoint server – SP 2016 configuration failed – error creating the configuration database

I installed SharePoint 2016 on Windows Server 2016 with SQL Server 2016. I ran the configuration wizard to create a single server farm, but the wizard was unable to create the configuration database. Then I tried the PowerShell, where I got the same error:

12/12/2017 13:42:40 9 ERR An exception
of type Microsoft.SharePoint.SPException was raised. additionally
Exception information: The language is not supported on the server.
Microsoft.SharePoint.SPException: The language is not supported on the
Server. —> System.Runtime.InteropServices.COMException: The language
is not supported on the server. at the
Microsoft.SharePoint.Library.SPRequestInternalClass.CreateSite (Guid
gApplicationId, String bstrUrl, Int32 lZone, Guid gSiteId, Guid
gDatabaseId, Guid gSiteSubscriptionId, String bstrDatabaseServer,
String bstrDatabaseName, String bstrDatabaseUsername, String
bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32
nLCID, string bstrOwnerLogin, string bstrOwnerUserKey, string
bstrOwnerName, String bstrOwnerEmail, String
bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String
bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean
bADAccountMode, Boolean bHostHeaderIsSiteName, Int32
iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32
iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32
iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32
iSprocsVersionBuild, Int32 iSprocsVersionRevision, String
bstrSiteSchemaVersion, Boolean bCreateFromMaster, String
bstrDenyPermMaskGroupId)
Microsoft.SharePoint.Library.SPRequest.CreateSite (Guid gApplicationId,
String bstrUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, Guid
gSiteSubscriptionId, String bstrDatabaseServer, String
bstrDatabaseName, String bstrDatabaseUsername, String
bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32
nLCID, string bstrOwnerLogin, string bstrOwnerUserKey, string
bstrOwnerName, String bstrOwnerEmail, String
bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String
bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean
bADAccountMode, Boolean bHostHeaderIsSiteName, Int32
iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32
iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32
iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32
iSprocsVersionBuild, Int32 iSprocsVersionRevision, String
bstrSiteSchemaVersion, Boolean bCreateFromMaster, String
bstrDenyPermMaskGroupId) — end of inner exception batch tracking —
at Microsoft.SharePoint.SPGlobal.HandleComException (COMException
comEx) at Microsoft.SharePoint.Library.SPRequest.CreateSite (Guid
gApplicationId, String bstrUrl, Int32 lZone, Guid gSiteId, Guid
gDatabaseId, Guid gSiteSubscriptionId, String bstrDatabaseServer,
String bstrDatabaseName, String bstrDatabaseUsername, String
bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32
nLCID, string bstrOwnerLogin, string bstrOwnerUserKey, string
bstrOwnerName, String bstrOwnerEmail, String
bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String
bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean
bADAccountMode, Boolean bHostHeaderIsSiteName, Int32
iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32
iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32
iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32
iSprocsVersionBuild, Int32 iSprocsVersionRevision, String
bstrSiteSchemaVersion, Boolean bCreateFromMaster, String
bstrDenyPermMaskGroupId)
Microsoft.SharePoint.Administration.SPSiteCollection.AddInternal (SPSiteCollectionAddParameters
param) around
Microsoft.SharePoint.Administration.SPSiteCollection.Add (SPSiteCollectionAddParameters
param) around
Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance (SqlConnectionStringBuilder
administrationContentDatabase, SPWebService adminService, IdentityType
identityType, String farmUser, SecureString farmPassword)
Microsoft.SharePoint.Administration.SPFarmFactory.CreateAdministrationWebService (SPFarm
farm, SqlConnectionStringBuilder administrationContentDatabase,
IdentityType (IdentityType, String farmUser, SecureString farmPassword)
at the
Microsoft.SharePoint.Administration.SPFarmFactory.CreateBasicServices (SPFarm
farm) at Microsoft.SharePoint.Administration.SPFarmFactory.Create ()
at the
Microsoft.SharePoint.Administration.SPFarm.Create (SqlConnectionStringBuilder
configurationDatabase, SqlConnectionStringBuilder
administrationContentDatabase, SqlConnectionStringBuilder
siteMapDatabase, IdentityType identityType, String farmUser,
SecureString farmPassword, SecureString masterPassphrase) under
Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb ()
at the
Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run ()
at the
Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask ()

Do you remember 2016 when the liberal media said Trump didn't stand a chance and he won?

The reason we think you are stupid is because you don't seem to notice that we all live in the same country. They cheer for things that will ruin our country because they will make the liberals cry. BUT YOU ALSO LIVE HERE.

For example, if you cheer for Obamacare's lifting because you think it will harm people you don't like, you are so stupid that you don't realize that YOU are losing benefits that you now have in terms of health care , Become smarter.

Map a network drive from Windows 10 to Windows 2016 Server

Sounds like your client can't authenticate to your domain. Make sure your domain controller is reachable, the firewalls are properly configured, DNS is working properly for your AD (on both sides), and test access to file sharing from your client through the UNC path (\SERVERNAME.FQDN.TLC).

Just open the server (\servername) all available shared folders are displayed. If you see it but cannot open it, the NTFS rights for this user are incorrect.