Adding Windows Server 2012 R2 to a Windows Server 2012 Cluster.... Supported?

Hi all;
Any ideas?
Thanks
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Hi,
no this is not supported.
The easiest way to see is if you run cluster validation when adding a new 2012 R2 node.
Microsoft supports a failover cluster solution only if the complete configuration (servers, network, and storage) can pass all tests in the Validate a Configuration Wizard.
In this step it checks for compatibility. Here you can see if it works or not
Regards
Eric
Eric Berg -- http://www.ericberg.de -- MCSE: Private Cloud MCSE: Server Infrastructure MCSE: Desktop Infrastructure

Similar Messages

Windows Server 2012 R2 Fax Service - Windows 7 Client "You do not have permissions to complete this operation. Contact your fax administrator for more assistance"

First I have tried all sorts of searches and and all I come up with is things related to Windows Server 2008.
1. I have Fax Service running on my 2012 R2 File and Print Server.
a. It can send faxes from the logged in domain user
b. It does not need to receive faxes because we have another machine for that
2. I have added the domain user I am using on the Windows 7 machine to the Accounts List in Fax Manager
3. I can not seem to find any logging saying that there is a security problem (Event Log, etc...)
Please point me in the correct direction as I need to have my staff use Print to Fax from our Practice Management Application.

Hi Shawn,
à
You do not have permissions to complete this operation. Contact your fax administrator for more assistance
From the error message, please check if share the Fax on the server. Meanwhile, please also check if assign
correct permissions in Security tab under Fax properties.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
1. Fax Sharing is enabled and can see the Shared Fax Printer on other machines.
2. At least 2 domain groups that the Windows 7 user is in are in the Security Section, set to be able to fax. One othem can manage fax.

SCCM 2012 SP1 SUP on Windows Server 2012

Hi sccm guys,
I'm having Troubles to get the SUP role working on my Windows Server 2012. I'm using SCCM 2012 SP1. I installed (and did not configure) the WSUS role from the Server Manager. I Chose to install the DB on the local SQL instance (no WID instance).
Then I added the SUP role to the Server and configured it with the seperate wsus Administration site (Ports 8530 and 8531).
WSUS gets configured partially (Proxy Settings and "Products and Classification" Options only for Office and Windows)
The folowing error pops up in the wcm.log
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
Any clues?
Cheers
Sebastian Bammer

Also did not fix my issue. A round of my logs:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Verify Upstream Server settings on the Active WSUS Server
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:14 a.m.
3556 (0x0DE4)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:16 a.m.
3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Starting WSUS category sync from upstream...
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
3556 (0x0DE4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:29:26 a.m. 3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:41 a.m.
3556 (0x0DE4)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Using DOMAIN\Administrator credentials for network connections
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Subscription contains categories unknown to WSUS.
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Done using DOMAIN\Administrator credentials
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
3556 (0x0DE4)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCM01.domain SITE=AKL PID=1544 TID=3556 GMTDATE=Mon Jan 14 19:29:42.723 2013 ISTR0="SCCM01.domain" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER
15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
Thanks Christoph

Can Crystal Server 2011 run on a Windows 2012, R2 server?

Hey,
I purchased Crystal Server 2011 in April 2013. Unfortunately, due to a heavy workload I'm just now ready to install it in a test environment. Will Crystal Server 2011 run on a Windows 2012, R2 server?

If you update your CR Server to SP 5, then yest, it is supported on WIN 2012.
See the PAM.
To get SP5 you will have to loin to the SAP Market Service Place.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada

Errro while installing sql server 2012 express edition on Windows 8 -64 version

Hi,
Im trying to install sql server 2012 express edition on windows 8 machine(64 bit),however im getting same error every time.
The following error has occurred:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337
i've googled and checked all prerequisite which is already installed.so not finding the reason behind this error.
it would be great if any one can help on resolving this error.
Thanks in advance
Regards
Ritesh

Hi ,
Thanks for help. here is the log summary text
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068051679
Start time:                    2014-02-05 12:30:44
End time:                      2014-02-05 12:36:21
Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name:                  IDEA-PC
Machine processor count:       4
OS version:                    Future Windows Version
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication
1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Developer Edition
10.50.1600.1    No
SQL Server 2008 R2
Management Tools - Complete              1033                 Developer Edition    10.50.1600.1
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Developer Edition    10.50.1600.1
No
SQL Server 2008 R2
Client Tools Backwards Compatibility     1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Client Tools SDK                         1033
Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Integration Services                     1033                 Developer Edition
10.50.1600.1    No
Package properties:
Description:                   Microsoft SQL Server 2012 Service Pack 1
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         c:\b33170cf028067db5b8335d2\x64\setup\
Installation edition:          Express
Product Update Status:
None discovered.
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      true
AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Disabled
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CLTCTLRNAME:                   <empty>
CLTRESULTDIR:                  <empty>
CLTSTARTUPTYPE:                0
CLTSVCACCOUNT:                 <empty>
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 <empty>
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    true
ENU:                           true
ERRORREPORTING:                false
FEATURES:                      SQLENGINE, REPLICATION, SNAC_SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 <empty>
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLFASHION
INSTANCENAME:                  SQLFASHION
ISSVCACCOUNT:                  NT AUTHORITY\Network Service
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
NPENABLED:                     0
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
ROLE:                          AllFeatures_WithDefaults
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  Latin1_General_CI_AI
SQLSVCACCOUNT:                 NT Service\MSSQL$SQLFASHION
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           idea-pc\lenovo
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
TCPENABLED:                    0
UIMODE:                        AutoAdvance
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Component name:                SQL Server Common Files
Component error code:          2337
Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Component name:                SQL Server Common Files
Component error code:          2337
Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
Feature:                       SQL Client Connectivity
Status:                        Passed
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\SystemConfigurationCheck_Report.htm

Issue installing SQL Server 2012(with SP1) on windows 7 Error result: -2067529718

When running the installation, it suddenly stops without any error popup.
I ran the installation from the command prompt and this is what I get:
An error occurred during the SQL Server 2012 Setup operation.
Error result: -2067529718
Result facility code: 1220
Result error code: 10
I recently uninstalled SQL Server 2012 SP1, because the SQL server service was not starting up, it would just hang in there with no response. I tried many things to get that issue fixed, finally I decided to uninstall and start fresh but I couldn't since
I was getting an error stating that I needed Windows 7 SP1(which was already installed). I downloaded the
microsoft fix it tool which fixed the issue.
On the control panel/Programs and features, I still see that SQL Server 2012 is listed if I click to uninstall again it tells me:
An error occurred while trying to uninstall Microsoft SQL Server 2012. it may have already been uninstalled. do you want to remove Microsoft SQL Server 2012 from the Programs and features list?
if I click yes, eventually it will be listed again.
currently I'm not able to install SQL server again and besides the info provided there are not error messages (I also copied the installation files to disk).
UPDATE: it appears that the sql server was not completely removed from the system, I still see listed the SQL server(SQLExpress) and server browser services on the SQL server configuration manager.
Thanks.

1) First Reboot your server and try again for the installation.
2) If first fail again than Take a backup of Registry first for safe side and then delete the entries of SQL server 2012 if found take a reboot again and try to install again.
One more thing if installation created any file then move/Delete that also before installation.

Installing Sql Server 2012 Enterprise edition on Windows 7

Hello,
I have a desktop with 1 TB Hard Disk and 8GB RAM. It has Windows 7 installed. I want this to be used as staging server at my work. I installed the SQL Server 2012 Enterprise edition. While installing I used service accounts as default when prompted
which I normally do while installing on a desktop. But now I want this to be used as a server where people can access this box as they do on a sql server machine .i.e. connect to server using SSMS and get to databases on the server and also remote
desktop into this machine. So, Is it fine to install with default service accounts?
Also how can I connect to this newly installed sql server box from another desktop using SSMS?
Thank You.

Hello,
Installation of SQL server 2012 Enterprise edition on Client machine(Win 7) is not supported( you can install ) .See below for Hardware and Software requirements for SQL Server 2012.You cannot claim support from Microsoft and I guess statging
is also important.
http://msdn.microsoft.com/en-us/library/ms143506.aspx
Now to your main question.To connect
Makes sure Browser service is running
Make sure you make exception in firewall for SQL Server services and incoming connections
Make sure you specify correct instance name when connecting from remote
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Upgrade from Windows Server 2012 Active Directory to Windows Server 2012 R2 Active Directory

We are currently running Windows Server 2012 Active Directory and would like to upgrade to Windows Server 2012 R2 AD. Is it OK to just do an in-place upgrade, or is it advisable to build new domain controllers on R2? Are there any guides or articles anyone
can recommend?

Hi Ginandtonic,
To upgrade DC(Domain Controller) from windows server 2012 to windows server 2012 r2, please refer to these articles:
Upgrade from windows Server 2012 to 2012 R2
Upgrade Active Directory from 2012 to 2012 R2
I hope this helps.
Best Regards,
Anna

Why do I need to install RSAT on Windows 8.1 for accessing Hyper-V Server 2012 R2?

Since Windows 8.1 has Hyper-V Platform and Hyper-V Manager built in to it, if I just enable the Hyper-V Manager on my Windows 8.1 client machine I should be able to access the standalone Hyper-V Server 2012 R2 (which I'm planning to install on my 2nd machine)
right?
Then why every article I found on this suggests to install RSAT on my client machine?

Hi Nero,
RSAT is used for these server/client can not enable hyper-v role to manage the corresponding hyper-v server .
Please refer to following supported OS list of
client hyper-v :
Windows 8 Pro 64-bit Edition
Windows 8 Enterprise 64-bit Edition
Windows 8.1 Pro 64-bit Edition
Windows 8.1 Enterprise 64-bit Edition
Best Regards
Elton JI
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.

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

Windows Server 2012 RDS CALS on Windows Server 2008 R2 Licensing Server

Hi,
at the moment we are installing the first couple of Windows Server 2012 in our infrastructure.
Some of them have installed RDS.
Now we are wondering whether it is possible to use our existing Windows Server 2008 R2 licensing server for serving the licenses we have (yes we to have new Windows Server 2012 RDS CALS) or whether we have to install a new host based on Windows Server 2012.
We tried to add the new license to the 2008 R2 licensing server, but it is not possible. The licensing manager's error message: "The license code contains invalid characters or not enough characters."
Is there any other way?
Thanks and regards
Matthias

Hi matt_will_fix_it,
How about Windows 2012 R2 ?
Will a Windows 2012 RD Licensing server provide licences to a Windows 2012 R2 server?
I have not tested it, but it should work. Server 2012 R2 requires the same RDS CAL version as Server 2012. If you try it and have an issue please reply back.
-TP

Windows 7 Enterprise 32 bit and Windows Server 2012 64 bit successful dual boot.

Client Windows 7 Enterprise 32 bit SP1, Windows Server 2012 64 bit successfully install for dual boot. Even deleted Windows 7 Enterprise from msconfig, moved Windows Server 2012 partition, for dual boot installed Windows 8.1 64 bit (now posting from),
deleted Windows Server 2012 from msconfig, moved Windows 8.1 partition, just for knowledge.

Hi,
After referring to your post, I can understand you are trying to install 32 bit and 64 bit OS on same system. Are you trying to perform that? Here providing you thread link for detail.
dual boot windows 32 bit and 64 bit at same pc
Hope it helps to understand!
Regards.

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

Windows 2008 R2 Remote Desktop Service Role pickup 2012 RDS License Server.

I am installing Citrix onto a Windows 2008 R2 server as part of this I need to setup the RDS Role on the same box and then point it to the Windows RDS License server.
Our plan is to have a Windows 2012 License server for RDS Licenses i.e. install 2012 RDS Licenses.
I was wondering if it was possible for a 2008 R2 RDS role to pick up 2012 RDS Licneses from a Windows 2012 RDS Server?
Many thanks,
Steve

Hi Steve,
Thank you for posting in Windows Server Forum.
Yes, agree with TP’s comment. You can also check below interoperability matrix link for details.
RDS and TS CAL Interoperability Matrix
http://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Can't upgrade Windows Server 2008 R2 Enterprise to Windows Server 2012 R2 Standard

Even though the "Windows Server Installation and Upgrade" TechNet article (DN627667) claims that I can upgrade Windows Server 2008 R2 SP1 to Windows Server 2012 R2 Standard, it seems I can't. I get an error message saying "Windows 2008
R2 Enterprise cannot be upgraded to Windows Server 2012 R2 Standard (Server Core Installation). You can choose to install a new copy of Windows..." What might be causing this issue? Thanks for any input! :)

Hi,
Firstly, for retail versions, Windows Server 2008 R2 Enterprise with SP1 can be upgraded to Windows Server 2012 R2 Standard/Datacenter.
I assume you are running Windows Server 2008 R2 retail version, right?
In addition, it seems that in earlier version than Windows Server 2012,
once you install the server in Core or with GUI mode, you could not switch to the other. The only option was to rebuild the server from scratch.
Did you install Windows Server 2008 R2 in GUI? If yes, I recommend you to upgrade it to Windows Server 2012 R2 in GUI
mode to see if the issue persists. If it succeed and you want to run in server core, you can just remove the graphical shell and convert your Windows Server 2012 R2 to Server Core.
Best regards,
Susie
Thanks for replying Susie. The 2008 R2 software is the one provided by Microsoft for Action Pack subscribers, so I'm assuming it's not retail. That's another thing, I think I should be installing the GUI as my 2008 has a GUI, not just the server core. For some
reason I missed that and clicked on the server core only install!

Windows 2012 Remote desktop session host server not detecting RD licensing server

Hi,
We have a customer server which is Windows 2012. We installed RDS session host server role and configured it to use RD licensing server as per the
https://support.microsoft.com/kb/2833839?wa=wsignin1.0
After configuring, when I open RD license diagonser tool, it says, RD license server is not available. Also shows, credential not available. When I enter the credential by clicking, provide credentials, it does not get applied. I see no event logs related
to RD service. However, I see the below event log which points to RD licensing server.
DCOM was unable to communicate with the computer <RD license server> using any of the configured protocols; requested by PID 273c (C:\Windows\system32\mmc.exe).
Please help in fixing the issue.
Thanks,
Umesh

Hi Umesh,
Thanks for your comment.
During your configuration, have you specified RD License server for RDSH to use?
You can also specify a license server for the RD Session Host server to use by applying the Group Policy under below path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
Use the specified Remote Desktop license servers – Provide the FQDN of the license servers to use
Also this setting can be specified by below method.
To configure the license server on RDSH/RDVH:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj.SetSpecifiedLicenseServerList("License.contoso.com")
Note “License” is the name of the License Server in the environment
To verify the license server configuration on RDSH/RDVH:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj.GetSpecifiedLicenseServerList()
More information.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
In addition you can refer this article for reference.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Adding Windows Server 2012 R2 to a Windows Server 2012 Cluster.... Supported?

Similar Messages

Maybe you are looking for