WSUS server role on Windows Server 2012 R2 - Supported SQL Configurations

According to
this page the supported SQL configurations for WSUS on Windows Server 2012/2012 R2 stop at SQL Server 2012 SP1, but there is no mention of SQL Server 2012 SP2 being supported.
However, both the SCCM 2012 R2
supported configuration page and this announcement state that SQL Server 2012 SP2 is fully supported on SCCM 2012 R2 with no
known limitations. Bearing in mind a big part of SCCM is to perform software updates which in turn requires WSUS to be installed...
... Is SQL Server 2012 SP2 supported on WSUS 4.0 (aka WSUS server role on Windows Server 2012 R2)?

The only thing that mattered for the versions mentioned on TechNet probably is the date the articles are published. I'm no Microsoft employee so I cannot guarantee you support even if I trace back some Microsoft article that explains the lifecycle of MS
products and support.
Fact is that MDT uses a database, SQL is a database server. SQL server has all kinds of compatibility modes to support databases dating multiple versions back.
Another fact is that a Service pack is an
update to the software (be it a large one) Microsoft will not break compatibility with their own products (and may others that relay on SQL server) by an update.
And a last fact is that in general, updates are required when you need support. After all, updates fix issues, and engineers generally don't like ghosthunting a bug that has already been patched.
MCP/MCSA/MCTS/MCITP

Similar Messages

Installing terminal server role on windows server 2012 to use for Windows server 2008 R2 machines.

Dear
Our current setup is as follows :-
Active Driectory is in Windows Server 2003.
Citrix Xenapp version 5.6 with all Xenapp servers in Windows Server 2003
Now we are upgrading our Citrix farm to 6.5 and all Xen app servers into Windows Server 2008R2.
We did the configuration and testing; everything works fine except the terminal server is not configured which gives the pop always for the expiry date.
We do have license for 2012 terminal server which is not possible to downgrade for some reason and managent need to install new Windows Server 2012 for terminal server and activte the licenses.
My question is :-
1 Whether Windows Server 2008 R2 will get RDS cal license from Windows Server 2012 terminal server (RDS CAL license is of windows server 2012).
2. What is the role and features I need to activate in Server 2012 in order to use for Citrix 6.5 (only applicable fetaure for getting the RDS cal license.)
3. Whether I can add this 2012 server into domain. Is it possible to add 2012 server into Windows Server 2003 AD.
Your early reply is highly appreciated.

Thanks Jeremy..
I got exactly the right answers I am lookoing for ..
I successfully activated the terminal service on the newly created Windows 2012 Server and installed the retail license pack we had of 50+50+25 keys . It later shows the 125 keys successfully applied.
when I tried to link the Xenapp (Windows Server2008R2) to the license server, it first gives me error that session host service role is not installed on the ternial server. So I installed that role also in the terminal server.
But now its anothee error as below.
RDS Cals are not available for this Remote Desktop Session host server, and licensing Diagnostic has identified licensing problems for the RD session host server.
1. Is it wrong I did by installing session host server role into the terminal server (but really it gave me error like 'session host server role is not running on the license server' when I tried to link the license server).
2. Is it the problem that Windows Server 2008 R2 will not get license from 2012 RDS CAL license.
3. whether Clearing house will take time to update the license.
Your reply is highly appreciated. I need to know whether any other way I can link the Windows Server 2008 R2 Servers (Xenapp) to the license server.

How uninstall WSUS server role from Windows Server 2008 R2 with database hosted on remote SQL server?

Hello,
I'm looking to uninstall the WSUS server role 3.0 from Windows Server 2008 R2 SP1. The thing is the database is hosted on a remote MS SQL server. I want to remove the database as well. I would like help for figuring out what I need to do to completely remove
WSUS and its database.
Any kind of help is appreciated! Thanks

Hi,
WSUS offers limited support for running database software on a computer that is separate from the computer where the rest of WSUS is installed. This section offers step-by-step
instructions for how to install WSUS in this configuration.
If you meet the uninstall issue with the normal uninstall, please post the detail information for us but if you just want to manage the WSUS related SQL data, you can refer
the following KB then delete corresponding database.
In the general procedure, you will create the related WSUS database as below::
Run WSUS Setup from the command line, using the SQLINSTANCE_NAME=servername\instancename command-line option, where servername is the name of the remote computer, and instancename
is the name of the SQL Server instance that you will use for WSUS.
More information:
Choose the Database Used for WSUS 3.0
http://technet.microsoft.com/en-us/library/cc708452(v=ws.10).aspx
Appendix B: Configure Remote SQL
http://technet.microsoft.com/en-us/library/cc708595(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cannot install WINS Server Role on Windows Server 2008 R2 Standard x64

Hi,
We are trying to install WINS Server Feature on a brand new Windows Server 2008 R2 Standard x64 (Virtual Machine). It seems that WINS is getting installed and right at the very end it gives an error 0x80070002.
We have tried rebooting the server multiple times , DNS/DHCP roles have been installed successfully as
well . It is just the WINS server feature that we are unable to install on this server.
Can someone point us to right direction. Are there any pre requisites we need to ensure before installing this feature. Are there any alternate ways to install
the WINS feature .. if yes please let us know.

The error indicates a File was not found:
C:\Users\Mark\Documents\Tools>err 0x80070002
# for hex 0x80070002 / decimal -2147024894
COR_E_FILENOTFOUND
corerror.h
# MessageText:
DIERR_NOTFOUND
dinput.h
DIERR_OBJECTNOTFOUND
dinput.h
STIERR_OBJECTNOTFOUND
stierr.h
# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x2
# for hex 0x2 / decimal 2
ERROR_FILE_NOT_FOUND
winerror.h
# The system cannot find the file specified.
# 5 matches found for "0x80070002"
I would check a few things:
1) Is the OS activated (Control Panel/System)
2) Is the OS fully patched and has it been rebooted since it was patched?

Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.

We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

[Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

As we all know,
the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
Essentials Experience role in Server Manager or via Windows PowerShell.
In this article, we introduce the steps to install and configure Windows
Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
Before installing the Windows Server Essentials Experience Role, please use
Get-WindowsFeature
PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
Figure 1.
Part 1: Install Windows Server Essentials Experience role locally
Add Windows Server Essentials Experience role
Run Windows PowerShell as administrator, then type
Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
Figure 2.
Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
(Figure 3)
Figure 3.
2. Configure Windows Server Essentials Experience role
(1) In an existing domain environment
Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
Figure 4.
After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
Server Essentials:
Start-WssConfigurationService –Credential <Your Credential>
Note: The type of
Your Credential should be as: Domain-Name\Domain-User-Account.
You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
Figure 5.
Next, you can type the password for the domain account. (Figure 6)
Figure 6.
After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
Figure 7.
By the way, you can use
Get-WssConfigurationStatus
PowerShell cmdlet to
get the status of the configuration of Windows Server Essentials. Specify the
ShowProgress parameter to view a progress indicator. (Figure 8)
Figure 8.
(2) In a non-domain environment
Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
Figure 9.
After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
Figure 12.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Part 2: Install and configure Windows Server Essentials Experience role remotely
In an existing domain environment
In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
Add-WindowsFeature -Name ServerEssentialsRole
-ComputerName xxx -Credential DomainName\DomainAccount
Figure 13.
After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
Figure 14.
After the installation completes, it will return the result as below:
Figure 15.
Next, please use the
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
Enter-PSSession –ComputerName
xxx –Credential DomainName\DomainAccount (Figure 16)
Figure 16.
Then, please configure Server Essentials Role via
Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
Figure 17.
After your credential is accepted, it will update and prepare your server. (Figure 18)
Figure 18.
After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
Figure 19.
2. In a non-domain environment
In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
below:
Sevrer1: 192.168.1.54
Server2: 192.168.1.53
Run
Enable-PSRemoting –Force on Server1. (Figure 20)
Figure 20.
Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
to
add the TrustedHosts entry:
Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
(Figure 21)
Figure 21.
Next, we can use
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
Figure 22.
After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
Figure 23.
From figure 24, we can see that the installation is completed.
Figure 24.
Then you can use
Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
The figure below shows the status of Windows Server Essentials.
Figure
25.
Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
Figure 26.
More information:
[Forum
FAQ] Introduce Windows Powershell Remoting
Windows Server Essentials Setup Cmdlets
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
Thanks a lot.

Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks.

Project Server 2013 on Windows Server 2012 R2

Can we install Project Server 2013 on Windows Server 2012 R2? Is it supported? I searched a bit but couldn't find any concrete information if it is supported or not.

From the article:
http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx
Today, aligned with the SharePoint Conference, we’re announcing availability
of a slipstreamed SharePoint Server 2013 with SP1. SharePoint administrators
will be able to use this updated installer to deploy on Windows Server 2012 R2.
which I got linked from the following
http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx

Unable to install Essentials Role on Windows Server Technical Preview (VHD)?

Hi
Having a problem trying to install Essentials Role on Windows Server Technical Preview (VHD)
After reboots, AD installs, I get Configuration encountered some issues in Results wizard.
Updating an preparing your server... 68% completed then it fails with following error.
"An error occurred while configuring Windows Server Essentials. Please try again."
Trying again same error.
Anyone able to get this installed?
TIA

Hi,
I did the same test without any problem.
You could try it again to check the result.
If it does not help, please refer to this kb article:
http://support.microsoft.com/kb/2914651
Regards.
Vivian Wang

Migration of Windows Small Business Server 2003 to Windows Server 2012 Essentials

Hi,
I am trying to migrate Windows Small Business Server 2003 to Windows Server 2012 Essentials by following the steps given in the link below:
http://technet.microsoft.com/en-us/library/jj200112.aspx
I have looked at other threads on the forum but none of them have been too helpful.
The issue: When
I run the Migration Preparation Tool on the Source Server, it runs successfully and does not report any errors. However, when I try installing Windows Server 2012 Essentials on the Destination Server, it displays an error that says 'Source
Server not prepared for migration: After you run the Migration Preparation Tool successfully on your source Server, click retry'.
The Source Server has 2 network adapters-one for the local network and the other for connection to the internet and the router is set as the default gateway this adapter.
Since it is mentioned in the documentation - 'configure your Source Server to use one network adapter', I'm wondering if this is the issue and I need to make changes in this configuration?
On running the Microsoft IT Environment Health Scanner tool it
reported an error - 'DNS Server listening on multiple addresses' and a warning ‘Domain Controller listening on multiple addresses’. Both point to the same solution KB 272294 (http://support.microsoft.com/kb/272294).
But it did not remove the errors.
Other steps performed:
As per the steps, I performed a backup, installed recent service packs and synchronized the source server time with external source.
On running the Best Practices Analyser. It shows 3 warnings.
- The threshold for the Allocated Memory alert is set to the default value. However the server has more than 2 GB of RAM installed.
- Microsoft Outlook Client not installed" Text="Microsoft Outlook Client is not installed in the ClientApps folder. You must run Windows SBS integrated setup.
- The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000. The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000.
I also ran the Ran netdiag.exe, dcdiag.exe commands
and no failures were reported.
The Event Viewer does not show any errors.
Not sure to what extent these warnings would affect the migration.
Any help would be appreciated. Thanks!

The SBS2003 needs to use one NIC only so you'll need to change that before starting. If it is the premium version and has ISA server installed, that will need to be removed first. See:
http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
-- Al

Not able to install Exchange Server 2013 on Windows Server 2012

I got an error while installing exchange server 2013 on windows server 2012 : "The registry key "SOFTWARE\Microsoft\Exchange Server\v15\Pickup" does not exist under "HKEY_LOCAL_MACHINE " any related solutions highly appreciated
thanks :

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Migrating From Window Server 2003 to Window Server 2012 for Web server deployment and Developmemt Machine is on Window Server 2008

Hi Microsoft Team,
We need your urgent advice and that is also on priority:
Issue Description: We need to migrate from
WINDOW SERVER 2003 to WINDOW SERVER 2012 while the development activity will be carried
under WINDOW SERVER 2008 as DEVELOPMENT BOX.
.NET Framework Version: 3.5 ( For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
IIS Version: 7.5 (For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
Need your quick advice Is that configuration feasible for Development and
Deployment (Web Server).
Highly appreciate your response as this will depend which product we need to buy also if you feel any showstopper or concern. Please let us know.

Hi,
As suggested by Tim, in order to get better assistance, we can ask for help in the following IIS forum.
IIS Forum
http://forums.iis.net/
In addition, regarding migrating from Windows Server 2003 to Windows Server 2012, the following blog can be referred to for more information.
Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Best regards,
Frank Shen

Exchange Server 2013 In Windows Server 2012 - unable to logon EXchange Administrator Center (EAC)

Hi All,
I Just installed Exchange Server 2013 in Windows Server 2012 and trying to connect Dynamics CRM 2013 (DNS).
The Installations Success full but unable to load the EAC page by using the following URL
https://servername:port/owa/auth/logon.aspx
I have cross checked in Exchange/owa/auth folder don't have the "logon.aspx" file
But the auth folder have the "logoff.aspx"
I installed many time freshly in separate WS-2012 but it not contains that logon.aspx
I want access the Exchange Administrator Center
Please Help me to solve it
IIS Exchange (Missing of logon.aspx)
SRKD0808

Hi All,
I sorted out this problem
Actually we have to run these 2 commands in Domain Control, But what i did I just run this
1) setup /PrepareSchema /IAcceptExchangeServerLicenseTerms
Command in Domain Control we don't need to run the 2nd command, Because I already try to installed exchange 2013 very first time it success and after some modifications
it gone.
That time it will ask you to provide Organization name, Once you give that it will create the Organization name in Domain control and it will save the settings when
you install first time
Because of this reason It is failing to run these 2 command
Finally what i did I just revert back my Domain control snapshot & Exchange server as well
Then i started freshly Installation in DC and Exchange server 2013 successfully installed
URL http://servername/ecp/default.aspx
Whole Process will be here
Exchange Server 2013 Step by Step Installation In Windows Server 2012
SRKD0808

Window SBS server 2008 and window server 2008 R2 on the same domain

Hi all,
I am a person only work for linux system. Recently i work for my company that using microsoft technologie. So i have a lot of trouble. Could you please help me and below are my big troble that i have met:
In my system, i have the first window SBS server 2008 run on our domain. However my organization growth up and we have more than 150 users and mailbox of exchange server 2007. So i do not want to use my sbs server 2008 anymore.
I am going to install a window server 2008 R2 64 bit and join it into the same domain with sbs server 2008. It will be replicate the username, dns, OU and group policy...After that i will tranfer FSMO role to new server and i will demote then remove the
sbs server.
My boss say that i should not use this solution because window server sbs can not run with any other kinds of window server 2008 (R2, standard, enterprise...) and it will automatically shutdown the main server after a couple of days.
Someone have experience can help me. I am so confuse now

Maybe this will also help to better understand the steps involved:
Transition from Small Business Server to Standard Windows Server
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Migrating away from SBS 2011
http://social.technet.microsoft.com/Forums/en-US/07c58cc4-7d6d-419a-b1a0-439c2cc0c48d/migrating-away-from-sbs-2011?forum=smallbusinessserver
Migrating from SBS 2008 to Windows Server 2012 R2 (NOT Essentials and with NO Exchange)
http://social.technet.microsoft.com/Forums/en-US/1276d2d3-a8f2-4786-82f3-4308a2affb11/migrating-from-sbs-2008-to-windows-server-2012-r2-not-essentials-and-with-no-exchange?forum=smallbusinessserver
And remember, as long as you don't move the PDC to one of the new DCs, you can leave the SBS 2008 up indefinitely. But I would remove Exchange 2007 off it right away once I've migrated the mailboxes and public folders, otherwise
you will get yourself into an Exchange coexistence scenario which is much more complex to configure and support because of the CAS differences, changing the URLs on the old one to "legacy.domain.com," getting a new UC/SAN cert with the correct
names on it, and more. Believe me, you really don't want to coexist them. The only time I've coexisted Exchange versions is during large migrations, such as 500 or more. Otherwise, I just migrate the mailboxes over a weekend and get it done with.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

WSUS server role on Windows Server 2012 R2 - Supported SQL Configurations

Similar Messages

Maybe you are looking for