Endeca Windows Server 2012 compatibility (IAP 6.1.1/MDEX 6.2.1)

Hello,
I currently try to deploy Endeca ITL HOST on Windows Server 2012 RTM.
I get an error when doing a Baseline_update action: "Forge.run()" and there are just an empty log to help...
Windows Server 2008 R2 is working fine for me. Does anybody knows Endeca compatibility issues using Windows server 2012 ?
My Endeca version is 6.1.1 with MDEX 6.2.1
Does someone already succeded this operation ? (even with the lastest Endeca version)
Thanks,
Gregory

The component Forge.exe is not working with Windows Server 2012 (c++ runtime error)
It Looks to be the main problem.
Does someone knows how to make it works ? changing manifest maybe ?
Thanks

Similar Messages

Windows Server 2012 compatibility with Thales nShield Connect HSM

Looking for any information on possible incompatibility between Windows Server 2012 (standard/R2, etc.) and Thales nShield Connect PCIe HSM
Configuring an offline Root CA with Server 2012. Works fine until HSM is added
Also interested in new Thales nShield Edge USB HSM (which Thales claims is ideal for supporting offline CAs -- experiencing same problems)

They'll know more over here.
https://www.thales-esecurity.com/support-landing-page
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Windows server 2012 compatibility

Hello,
I have a big problem. I installed a new windows 2012 server STD with Exchange 2013 and I encountred differents problems about backup compatibillty. I bougt the backup exec 2012 product it does not compatible with them.
We wish to backup on the tape (powervault LTO5).
Do you have any suggestion ? (downgrade to wondows server 2008 R2 with Exchange 2010 ??).
Thanks for your assistance.
Kind regards
Guillaume

Hello,
Backup Exec 2012 can backup remote Windows 2012 servers but cannot be installed on Windows 2012 and BE 2012 SP2 will backup Exchange 2013 but doesnot support GRT.
Backup Exec 2014 which is in the works to be released will provide all the features you are wanting and if you quickly register to be a part of the Beta program you can have access to these abilities even sooner.
Note: the Beta is full and will close by tomorrow so hurry if you want to be a part. Here is the link:
https://symbeta.symantec.com/callout/?callid=082D2918EC924087AA1F7FB1AE66B8E6
Lenora Moss Technical Support Engineer, SMB Partner Support, Symantec Corporation www.symantec.com

SQL Server 2008 R2 Standard - Compatibility issues with Windows Server 2012 R2

Hello,
We used as a test a box on which we installed Windows Server 2012 R2 and SQL Server 2008 R2 Standard Edition. No Service pack was installed. It worked perfect.
Now we try to do it on another box and all of the sudden there is compatibility issue when we try to instal SQL Server. We can still install SQL Server by clicking "Continue without getting help".
Where can this come from? If it is hardware related what are the thing I should look at?
Thanks all

Hello,
Adding to Shanky suggestion, you can perform a slipstream installation of SQL Server 2008 R2 + SP3 to make SQL Server
2008 R2 compatible with the newer operating system, as explained on the following post.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
https://support.microsoft.com/en-us/kb/955392/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2012 Standard compatibility with Windows Server 2012 R2 Standard

Hi,
Is SQL Server 2012 Standard compatibility with Windows Server 2012 R2 Standard.
In volume licensing portal Windows Server 2012 R2 Standard is not provided in the list of OS supported for SQL server 2012.

Hi Ajit,
Besides other post, please also note that
Service Pack 1 or
a later update is needed for the support of SQL 2012 on Windows Server 2012 R2.
For more details about how to use SQL Server in Windows Server 2012 R2, please review the following KB article.
http://support.microsoft.com/en-us/kb/2681562
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SAP Mobile Platform 3 compatibility with windows server 2012

Dear All,
As per SAP release notes Window Server 2012 is compatible with SMP 3.0 but after installation i see that the SMP3 Services are always into the hung state meaning they neither start nor stop. They are always in the starting state. Whereas it runs fine with Windows Server 2008 R2. When we force kill all the process running with SMP3 Service we can stop it but it doesn't start at all.
Has anyone faced this issue till now.
Thanks

Hi Rakshit,
I guess Eric Solberg, Mustafa Saglam can answer better.
Rgrds,
JK
PS: Raise a SAP ticket.
Message was edited by: jitendra kansal

Windows server 2012 R2 compatibility with UCS C220 M3S

Hello,
Anyone knows if i can install Windows server 2012 R2 in UCS C220 M3s ?
Best regards,
Pedro Sérvolo

Ciao Pedro
Please use this utility:
http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
I don't know you talk about standalone, UCS managed, which version,.......

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.

SharePoint server 2013 Search Service App 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.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

ProClarity 6.3 PAS install fails on Windows Server 2012

We are trying to install PAS 6.3 on Windows Server 2012 and the install fails with the following error
The following requirements are missing:
Windows Server 2003 SP1
We have successfully installed on Windows Server 2008 R2, so it really isn't a Windows Server 2003 SP1 issue.
Has anyone successfully installed on Windows Server 2012? Is there a way to force the installer not to check for the OS?
Thanks.
Kevin

I have a PAS server running in Windows 2012, by doing exactly the same pre-requisites that you do in Windows 2008 r2 (iis, Framework, SQL ADO 2005 / 2008). With the Windows Server 2003 SP1 message you can avoid it by doing a really simple thing that
is right click the setup file --> properties, and head to the "Compatibility Tab" and run it with compatibility mode Windows 7, also run it with Admin permissions. This let you pass by the message and let you install the product. Remember, after the
installation, you need to check all the IIS config, folder permissions, that you did in Windows 2008 x64 installation. Also, the App pool needs to work with .NET 2.0 not 4.0.
Good luck!
Byron
BNavas

App cannot run on Windows Server 2012 R2

I have an application that runs well on Windows Server 2012. The application has two editions 32-bit and 64-bit, both are from the same code base.
However, on Windows Server 2102 R2, the x64 version of the application works, but the 32-bit version does not run. Invoking the 32-bit of the application generates the "This app cannot run on you PC" message.
I tried the compatibility troubleshooting, and it does not help.
Any suggestion on what could be the problem?
Thanks.
jwang

<moved from Downloading, Installing, Setting Up to Photoshop General Discussion>

Attempted to perform an unauthorized operation error while installing SQL Server 2008 R2 Enterprise edition on Windows Server 2012 R2 standard VM server

I've been trying fresh installation of SQL Server 2008 R2 enterprise on Windows Server 2012 R2 standard VM server several times for two weeks, but always get the error "Attempted to perform an unauthorized operation". At first, I attempted
to install all features, but failed several times. So I decided to try install just Database Engine service, and still fail at the SqlBrowserConfigAction_Install_ConfigNonRC_Cpu32, with the error "Attempted to perform an unauthorized operation".
I remote login to server with my admin domain account. This account is in server local Administrators group. I
1. Right-click on setup.exe file | properties | Compatibility tab | select compatibility to Windows 8.Then click OK.
2. Right-click on setup.exe file | Run as Administrator, to start the Installation Center.
I have the document of my installation steps and zip file of the installation logs, if you need to take a look.
Appreciate for any help!
ntth

Hi ntth,
"Attempted to perform an unauthorized operation"
The above error is always related to the Windows account SID mapping. I recommend you login into Windows using another Windows account which has administrative privileges and run SQL Server setup using that Windows account.
Besides, please note that we need to apply SQL Server 2008 R2 Service Pack 2 or a later update when installing SQL Server Windows Server 2012 R2. For more information, please review this
KB article.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Is Windows Server 2012 compatible with HP Officejet pro 8600 plus printers

Hello,
I am wondering whether HP officejet pro 8600 plus printers compatible with Windows server 2012 - I have the driver installed on the server and deployed - installation of the driver and all was successful but it won't print from the server or on a user's computer from the deployed printers list. No error message comes up, I just click print and nothing happens. If I install it individually on the user computers - it seems to print as a 'network printer' but won't print from the server, and if it can not print from the server then it can not print from the deployed printers list. I was looking up on driver compatibility list online earlier and could not find Windows Server 2012 mentioned on the list - only server 2008 and below.
Essentially what I am trying to find out is whether this officejet pro 8600 plus printer is compatible with our server.
Many thanks,
Michael Peters

Hello Michael, and welcome to the HP Forums.
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial issue. You can do this at the HP Commercial Forums.
I hope this helps!
Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
Jamieson
I work on behalf of HP
"Remember, I'm pulling for you, we're all in this together!" - Red Green.

Windows Server 2012 Storage Spaces Simple RAID 0 VERY SLOW reads, but fast writes with LSI 9207-8e SAS JBOD HBA Controller

Has anyone else seen Windows Server 2012 Storage Spaces with a Simple RAID 0 (also happens with Mirrored RAID 1 and Parity RAID 5) virtual disk exhibiting extremely slow read speed of 5Mb/sec, yet write performance is normal at 650Mb/sec in RAID 0?
Windows Server 2012 Standard
Intel i7 CPU and Motherboard
LSI 9207-8e 6Gb SAS JBOD Controller with latest firmware/BIOS and Windows driver.
(4) Hitachi 4TB 6Gb SATA Enterprise Hard Disk Drives HUS724040ALE640
(4) Hitachi 4TB 6Gb SATA Desktop Hard Disk Drives HDS724040ALE640
Hitachi drives are directly connected to LSI 9207-8e using a 2-meter SAS SFF-8088 to eSATA cable to six-inch eSATA/SATA adapter.
The Enterprise drives are on LSI's compatibility list. The Desktop drives are not, but regardless, both drive models are affected by the problem.
Interestingly, this entire configuration but with two SIIG eSATA 2-Port adapters instead of the LSI 9207-8e, works perfectly with both reads and writes at 670Mb/sec.
I thought SAS was going to be a sure bet for expanding beyond the capacity of port limited eSATA adapters, but after a week of frustration and spending over $5,000.00 on drives, controllers and cabling, it's time to ask for help!
Any similar experiences or solutions?

Has anyone else seen Windows Server 2012 Storage Spaces with a Simple RAID 0 (also happens with Mirrored RAID 1 and Parity RAID 5) virtual disk exhibiting extremely slow read speed of 5Mb/sec, yet write performance is normal at 650Mb/sec in RAID 0?
Windows Server 2012 Standard
Intel i7 CPU and Motherboard
LSI 9207-8e 6Gb SAS JBOD Controller with latest firmware/BIOS and Windows driver.
(4) Hitachi 4TB 6Gb SATA Enterprise Hard Disk Drives HUS724040ALE640
(4) Hitachi 4TB 6Gb SATA Desktop Hard Disk Drives HDS724040ALE640
Hitachi drives are directly connected to LSI 9207-8e using a 2-meter SAS SFF-8088 to eSATA cable to six-inch eSATA/SATA adapter.
The Enterprise drives are on LSI's compatibility list. The Desktop drives are not, but regardless, both drive models are affected by the problem.
Interestingly, this entire configuration but with two SIIG eSATA 2-Port adapters instead of the LSI 9207-8e, works perfectly with both reads and writes at 670Mb/sec.
I thought SAS was going to be a sure bet for expanding beyond the capacity of port limited eSATA adapters, but after a week of frustration and spending over $5,000.00 on drives, controllers and cabling, it's time to ask for help!
Any similar experiences or solutions?
1) Yes, being slow either on reads or on writes is a quite common situation for storage spaces. See references (with some of the solutions I hope):
http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/a58f8fce-de45-4032-a3ef-f825ee39b96e/
http://blogs.technet.com/b/askpfeplat/archive/2012/10/10/windows-server-2012-storage-spaces-is-it-for-you-could-be.aspx
http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/64aff15f-2e34-40c6-a873-2e0da5a355d2/
and this one is my favorite putting a lot of light on the issue:
http://helgeklein.com/blog/2012/03/windows-8-storage-spaces-bugs-and-design-flaws/
2) Issues with SATA-to-SAS hardware is also very common. See:
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/5d4f68b7-5fc4-4a3c-8232-a2a68bf3e6d2
StarWind iSCSI SAN & NAS

[Forum FAQ]How to upgrade Windows Server 2008 R2 with a GUI to Windows Server 2012 Server Core

We found that some customers willing to upgrade Windows Server 2008 R2 GUI to Windows Server 2012 Server Core recently. This article provides detailed steps to perform the upgrade.
Analysis
Upgrading from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 with Server Core directly
is not supported. If you do that, you will receive the error message below(Figure 1) in Compatibility report:
Figure 1.
In these scenario, you can upgrade to Windows Server 2012 firstly. After the upgrade process is completed, you can switch freely between Server Core and Server with a GUI modes.
Produces
You can follow the steps below to perform an upgrade from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 Server Core mode:
1. Upgrade to Windows Server 2012 with a GUI mode
1) Firstly, please boot into Windows Server 2008 R2 with a Windows Server 2012 installation DVD inserted.
2) Select the operating system you want to install with a GUI mode.
We can see 2 options (Server Core Installation or Server with a GUI) for each operating system version. (Figure 2)
Figure 2.
Note: Please make sure you have enough disk space on system partition. Or you will get such an error in Compatibility report.(Figure 3)
Figure 3.
After the Compatibility check, the installation will continue. It will take several minutes until upgrading is done.(Figure 4)
Figure 4.
2. Switch the GUI mode to Server Core
Method 1: Using Server Manager
1) Open Server Manager, click
Manger and select “Remove Roles and Features” to start the
Remove Roles and Features Wizard.
2) In Features,
uncheck the box next to the “User Interfaces and Infrastructure” option, and then click “Next”. (Figure 5)
Figure 5.
Now tick the “Restart the destination Server automatically if required” box, then click “Remove”. (Figure 6)
Figure 6.
Method 2: Using Windows PowerShell
There are multiple ways to remove the GUI via Windows PowerShell, we introduce the way of using the ServerManager module.
You can also run the commands in Windows PowerShell with an administrator to remove the GUI feature:
“Import-Module ServerManager”
“Uninstall-Windowsfeature Server-Gui-Shell –Restart”
or
“Uninstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra –Restart”
It will take a period of time to remove the GUI feature and reboot. When the system boots up, you will get into the Windows Server 2012 with Server Core mode. (Figure 7)
Figure 7.
More information:
Switch between Full and Server Core in Windows Server 2012 using PowerShell 3.0
http://blogs.technet.com/b/puneetvig/archive/2012/10/16/switch-between-full-and-core-in-windows-server-2012-using-powershell-3-0.aspx
Windows Server Installation and Upgrade
http://technet.microsoft.com/en-us/windowsserver/dn527667.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi,
Brian is right, for mange the Server 2008r2 sp1 we recommend use the Windows 7 or 7.1 platform.
More information:
Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=7887
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.

Endeca Windows Server 2012 compatibility (IAP 6.1.1/MDEX 6.2.1)

Similar Messages

Maybe you are looking for