New answers tagged

-3

start task manager, and end-task called MSOSYNC.EXE


2

Yes, unfortunately this is default behavior. But there are ways around it. You can’t rename AppPools in the IIS, but you can create another AppPool and move the applications to the new AppPool. It’s a tedious work and you shouldn’t do this unless it’s absolutely necessary. Instead, fire up you SharePoint Management shell and type: ...


0

The solution to this problem: In Windows Server2012 R2 ServerManagerCMD.exe does not exist, but the setup needs it. I made a copy of C:\Windows\system32\ServerManagerCmd.exe and renamed it to ServerManagerCMD.exe. After this 'fix' all prerequisites are successfully installed.


5

You also need .NET Framework 3.5 installed. Check under features that its available. If not, follow the guide How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2



Top 50 recent answers are included