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

Similar Messages

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

Install SQL Server 2012 SP1 on a Windows Server 2012 R2 Failover Cluster - hangs at "Running discovery on remote machine" on VMWare VSphere 5.5 Update 1

Hi,I'm trying to install SQL Server 2012 SP1 on the first node of a Windows Server 2012 R2 failover cluster.The install hangs whilst displaying the "Please wait while Microsoft SQL Server 2012 Servce
Pack 1 Setup processes the current operation." message.The detail.txt log file shows as follows:(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached PID (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider
: NormalizePid is normalizing input pid (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached
PID (01) 2014-07-17 15:36:35 Slp: Completed Action: FinalCalculateSettings, returned True (01) 2014-07-17 15:36:35 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True (01) 2014-07-17 15:36:35 Slp: ---------------------------------------------------------------------- (01) 2014-07-17 15:36:35 Slp: Running Action: RunRemoteDiscoveryAction (01) 2014-07-17 15:36:36 Slp: Running discovery on local machine (01) 2014-07-17 15:36:36 Slp: Discovery on local machine is complete (01) 2014-07-17
15:36:36 Slp: Running discovery on remote machine: XXX-XXX-01After about 4 hours and 10 minutes, the step seems to time out and move on, however it doesn't seem to have discovered what it needs to and the setup subsuently fails

Hi,
Sorry Information you provided did not helped can you post content of both summary file and details,txt file on shared location for analysis.
Can you download Service pack again and try once more
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Exchange Server 2013 SP1 Install on Windows Server 2012 R2

I am trying to install Exchange 2013 SP1 onto a Windows Server 2012 R2. I get an error message that the operating system is not supported. I have installed all the prerequisite.

Does that mean that you can't install Exchange 2013 Sp1 with a Remote Desktop Role together included with Server 2012 R2?
Or is it possible to restore the Remote Desktop Role afterwards?
You can't install any build of Exchange 2013 on any server that has the RDS Role installed. So in other words, this is not a "limitation" with Exchange 2013 SP1 and Windows Server 2012 R2.
Additional Reading, check out: Exchange OWA/Activesync conflicting with RD Gateway
role
Martina Miskovic

Upgrading Windows Server 2012 Essential Eval to Windows Server 2012 R2 Retail

I need to upgrade from Windows Server 2012 Essential Eval version to Windows Server 2012 R2 Retail. What would be the easiest way to upgrade if license $$ is not an issue? The Server is a DC. Would the following works:
1. Upgrade from Windows Server 2012 Essential Eval to Windows Server 2012 Essential Retail
2. Do a conversion from Windows Server 2012 Essential Retail to Windows Server 2012 Standard Retail (I suppose this just require several command line to enable the 2012 Standard)
3. Do an in-place upgrade from Windows Server 2012 Standard to Windows Server 2012 R2 Standard (there is no need to do migration, am I right?)
Thanks.

I just did a simulation using Hyper V. It seems that I'm able to do the upgrade sequence as described but I'm not sure whether there are any side effect that not yet surface out. Here is the details steps that I took:
1. Under Windows Server 2012 Essential Eval
convert the Windows Server Essential 2012 Eval to Windows Server Standard 2012 using the following command in an elevated command prompot
dism /online /set-edition:ServerStandard /productkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /accepteula
press "y" and return to restart as prompted
the productkey could be retail key or the KMS client keys (just for installation not for activiation)
2. After reboot, the system become Windows Server 2012 Standard
using admin account to login
add admin account to the Enterprise Admins group and Schema Admins group if not already done so, logout and login again
mount the Windows Server 2012 R2 Standard disk in, say, drive d:
in an elevated command prompt, go the following:
cd d:\support\adprep
.\adprep.exe /forestprep
.\adprep.exe /domainprep
double click on d: in explore to run the Windows Server 2012 R2 Standard setup
follow the instruction to complete the in-place upgrade from Windos Server 2012 to Windows Server 2012 R2
3. After reboot into Windows Server 2012 R2 Standard, go to the charms bar, select setting -> server info, it will mention the server is not activated, click on Activate Windows and key in the Windows Server 2012 R2 Standard retail key

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

SharePoint 2013 with sp1 install on windows server 2012 R2

Hi All:
excuse me I have a question about sharepoint installation. I install sharepoint 2013 with sp1 on windows server 2012 R2，but i always got "Configuring Application Server Role, Web Server (IIS) Role"
message. I refer to this article <http://support.microsoft.com/kb/2765260>. I still got this message ... Which I did wrong step ?? I have been troubled for a long time, thanks to the help ...

Hi TiM,
According to your description, my understanding is that you got an error when you installed the prerequisites for SharePoint 2013 SP1 on Windows 2012 R2.
Please make sure that you have installed .NET Framework 3.5 on Windows Server 2012 R2, and enable .NET Framework 3.5 by using the Add Roles and Features Wizard.
Here is a blog you can refer to:
http://blog.migrationking.com/2013/11/how-to-install-net-framework-35-on.html
Reference:http://social.technet.microsoft.com/Forums/en-US/55589deb-cddf-445f-be41-b4c97f06ff4d/sharepoint-2013-sp1-on-windows-2012-r2?forum=sharepointgeneral
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Upgrade from Windows Server 2008 SP1 STD to Windows Server 2012 STD

Hi,
tried to upgrade Windows Server 2008 SP1 STD(OEM) to Windows Server 2012 STD but received message in Compatability Report
SAYING:
"Upgrades to this build have been disabled"
Both OS are English and X64.
Cant get arround this... any idea´what the problem is?

Hi
Try upgrading to SP2 and then you can do the upgrade, supported list below:
http://blogs.technet.com/b/askcore/archive/2012/10/23/upgrading-to-windows-server-2012-part-1.aspx
Hope this helps. Please 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.

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

Hyper-V 2012 High Availability using Windows Server 2012 File Server Storage

Hi Guys,
Need your expertise regarding hyper-v high availability. We setup 2 hyper-v 2012 host in our infra for our domain consolidation project. Unfortunately, we don't have hardware storage that is said to be a requirement that we can use to create a failover cluster
for hyper-v host to implement HA. Here's the setup:
Host1
HP Proliant L380 G7
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Host2
Dell PowerEdge 2950
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Storage
Dell PowerEdge 6800
Windows Server 2012 Std
File and Storage Services installed
I'm able to configure the new feature about Shared Nothing Live Migration - i'm able to move VM's back and fort between my hosts without storage. But this is planned and proactive approach. My concern is to have my hyper-v host to become highly available in
the event of system failure. If my host1 dies, the VMs should go/move to host2 and vice versa. In setting this up, i believe i need to enable the failover clustering between my hyper-v hosts which i already did but upon validation, it says "No disks
were found on which to perform cluster validation tests." Is it possible to cluster it using just a regular windows file server? I've read about SMB 3.0 and i've configured it as well i'm able to save VMs on my file server, but i don't think that my hyper-v
hosts are already highly available.
Any feedback and suggestions or recommendation is highly appreciated. Thanks in advance!

Hi Guys,
Need your expertise regarding hyper-v high availability. We setup 2 hyper-v 2012 host in our infra for our domain consolidation project. Unfortunately, we don't have hardware storage that is said to be a requirement that we can use to create a failover cluster
for hyper-v host to implement HA. Here's the setup:
Host1
HP Proliant L380 G7
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Host2
Dell PowerEdge 2950
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Storage
Dell PowerEdge 6800
Windows Server 2012 Std
File and Storage Services installed
I'm able to configure the new feature about Shared Nothing Live Migration - i'm able to move VM's back and fort between my hosts without storage. But this is planned and proactive approach. My concern is to have my hyper-v host to become highly available in
the event of system failure. If my host1 dies, the VMs should go/move to host2 and vice versa. In setting this up, i believe i need to enable the failover clustering between my hyper-v hosts which i already did but upon validation, it says "No disks were
found on which to perform cluster validation tests." Is it possible to cluster it using just a regular windows file server? I've read about SMB 3.0 and i've configured it as well i'm able to save VMs on my file server, but i don't think that my hyper-v hosts
are already highly available.
Any feedback and suggestions or recommendation is highly appreciated. Thanks in advance!
Your shared storage is a single point of failure with this scenario so I would not consider the whole setup as a production configuration... Also setup is both slow (all I/O is travelling down the wire to storage server, running VMs from DAS is ages faster)
and expensive (third server + extra Windows license). I would think twice about what you do and either deploy a built-in VM replication technologies (Hyper-V Replica) and apps built-in clustering features that does not require shared storage (SQL Server and
Database Mirroring for example, BTW what workload do you run?) or use some third-party software creating fault tolerant shared storage from DAS or investing into physical shared storage hardware (HA one of course).
Hi VR38DETT,
Thanks for responding. The hosts will cater a domain controller (on each host), Web filtering software (Websense), Anti-Virus (McAfee ePO), WSUS and an Auditserver as of the moment. Is the Hyper-V Replica somewhat give "high availability" to VMs or Hyper-V
hosts? Also, is the cluster required in order to implement it? Haven't tried that but worth a try.

Windows Server 2012 Essentials upgrade to Windows Server 2012 Standard

I've just upgraded a Windows Server 2012 Essentials to Standard via the Powershell command. The server restarted and is now Standard version. However I've noticed in the services that one particular service fails.
silsvc <Failed to Read Description. Error Code: 2 >
C:\Windows\system32\silsvc.exe
It is set to automatic.
I guess this is part of the essentials license and hasn't been removed. I would like to keep the Essentials Features however on a VM I replicated the same problem but when I removed Essentials features this service also got removed.
Is it ok to just disable this service? because I want to keep the Essentials features. Is it going to cause any issues?

Hello,
What is the procedure to migrate to standard essentials without losing programs?
Can you help me?
actually I have windows server 2012 essentials and I want to upgrade to standard

Not able to install SharePoint Foundation 2013 SP1 on a Windows Server 2012 R2

I am very new working with SharePoint and Server 2012. I had and am having a lot of problems installing SharePoint Foundation 2013. I get over the typical errors as download all prerequisites from the Internet, installing the Farms, etc.
After I completed all the installations steps, and the installation has finished I tried to open SharePoint 2013 Central Administration but I can't access to it.
Does anyone has a suggestion?

HI Sofia,Did you run the PSCONFIG wizard after the succesful completion of installation.If not,please run.Find the below link that gives more details on the installations.
http://expertsharepoint.blogspot.de/2013/11/detailed-sharepoint2013-installation-i.html
http://expertsharepoint.blogspot.de/2013/10/installation-of-sharepoint-2013-on.html
Anil Avula[Microsoft Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

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

SCCM 2012 using SUP to Windows 2012 R2 WSUS

I have the following environment setup:
1. Windows Server 2012 R2 with SCCM 2012 SP1
2. Windows Server 2012 R2 with WSUS installed
3. Windows Server 2008 R2 with SQL Server 2012 SP1
I am trying to connect SCCM to the WSUS server as a SUP. I have reinstalled and configured countless times. I've tried Sebastian's steps near the middle-end of this http://social.technet.microsoft.com/Forums/windowsserver/en-US/29135ae5-5f0c-49d9-b7ad-f4d5e9664a33/sccm-2012-sp1-sup-on-windows-server-2012?forum=configmanagerdeployment
I keep seeing an error in the WCM.log that the WSUS version is not supported. The WSUS version on the Windows 2012 R2 server is 6.3.9600.16384
Permissions should not be an issue. I have configured a Domain account and have added as a local administrator and also the WSUS Admin group. Firewall is not an issue as ports are open.
Do I have to switch my WSUS server to 2008 R2? Or remove it entirely and let SCCM install it as a SUP? This is environment is entirely from scratch.

I was finally able to get this to work. My logs were continuously showing that SCCM2012 was looking for WSUS 3.0 SP2 (+ KB). I installed WSUS locally on the SCCM 2012 server and added a SUP there. I was then able to successfully add the
remote WSUS server and it seems to be working now.

SharePoint 2013 Enterprise with SP1 on Windows Server 2012??????? What am I missing?

Hi there,
As per MS - SharePoint 2013 Enterprise SP1 is compatible with Windows Server 2012 R2.
I have Windows Server 2012 R2 installed - now it does not let me install SharePoint 2013 Enterprise (Standard without SP1).
AND SP1 can ONLY be installed AFTER SharePoint 2013 Enterprise is installed.
So how to install SharePoint 2013 Enterprise with SP1 on Windows Server 2012?
Thanks.

You can download it at the Microsoft Volume Licensing Service Center:
https://www.microsoft.com/Licensing/servicecenter/default.aspx
or at the Microsoft Developer Network:
http://msdn.microsoft.com/
Please note that if you do not have access to either, you will have to work with the vendor who sold you SharePoint 2013 to get you a new ISO with SP1, or you will have to find a way to make a slipstreamed version on your own. I'm really hoping you
have VLSC or MSDN access, as this will make things much easier for you.

SCCM 2012 SP1 SUP on Windows Server 2012

Similar Messages

Maybe you are looking for