SCCM 2012 Sp1 CU3 support Windows 2012 R2 deployment?

Hi,
Sorry for so basic question, but I have read few docuemnts, blogs and official materials and I'm a bit confused.
In our organization we have SCCM Sp1 CU3. We are planning create and next deploy Windows 2012R2 Server images. On some documentations there is CU3 supports only application managment, inventory and so on. but there is nothing about image deployment.
So, my question is - I have to upgrade SCCM 2012 Sp1 CU3 to SCCM2012R2 to capture, build and deploy Windows 2012R2 system?
Thank you.

Yes, you do. See what's new with ConfigMgr 2012 R2
http://technet.microsoft.com/en-us/library/dn236351.aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2. We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012. The deployment went as
expected. Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP. I am afraid to find out what time we are looking at for remote DP's.
The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3. We are using the same package source files. Previous to a successful deployment we were
seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment? Our previous deployment time for office was a little over an hour (not five hours). Any suggestions where to look to improve
the deployment time?
I am expected to deploy this in one week and have been working on these issues for weeks.

I see now that you are using a combination of scripts and ConfigMgr package/program.
The AppEnforce.log file is for use with the new ConfigMgr Application model.
Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
Office 2013.
This is how you do it
http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

CCMSETUP not updating on SCCM 2012 SP1 CU3/CU4 primary site

I have a SCCM 2012 SP1 CU3 primary site and i can't upgrade the local installed SCCM Client.
The error I get in ccmsetup.log is:
<![LOG[MSI: Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002]LOG]!><time="15:44:22.408-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:300">
<![LOG[MSI: Action 15:44:22: Rollback. Rolling back action:]LOG]!><time="15:44:22.562-60" date="02-08-2014" component="ccmsetup" context="" type="0" thread="2496" file="msiutil.cpp:314">
<![LOG[File C:\windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterHostingConfiguration.
ErrorMessages:
Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002
]LOG]!><time="15:45:00.798-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:872">
<![LOG[Client installation has failed too many times. Ccmsetup will now abort.]LOG]!><time="15:45:00.830-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7941">
<![LOG[Successfully deleted the ccmsetup service]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2496" file="ccmsetup.cpp:3320">
<![LOG[InstallFromManifest failed 0x80070643]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7086">
<![LOG[CcmSetup failed with error code 0x80070643]LOG]!><time="15:45:05.832-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2324" file="ccmsetup.cpp:10544">
I have this on my primary and secondary servers as well.
Is upgrading to R2 recommended and will that solve this issue ?
When googling to this issue i found that there is a solution for this: remove MP, upgrade Client, install MP.
But this is my primary and secondary and on secondary i am not allowed to remove the MP. It is hardcoded enabled.

Try the following steps to specify the hotfix when installing the client.
1. Open an elevated command prompt.
2. Run a command line similar to the following – if CU3 has already been installed, the MSP file below should be on the site server, in the
\\servername\SMS_SITE\Client\hotfix folder:
\ccmsetup.exe PATCH=\Configmgr2012ac-sp1-kb2882125-x64.msp
Juke Chou
TechNet Community Support

New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

Hi,
I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400. But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
and not 5.00.7804.1400.
For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client?
Thanks,
Nick

Hi,
Here's some good information to look over:
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing)

Part of a migration project from SCCM 2007 to 2012 SP1 CU3 - Updates no longer working and reporting not correct

Been working on a migration from 2007 sp1 to 2012 sp1 cu3. I first installed directly to sp1 but realized we had a few 8.1 clients being built so I added the cu3 mid-stream. I moved over two small subnets and pushed out some clients.
I was able to push out updates from the 2012 server for OS realted updates to a collection. After CU3 I tried to do the same process with Office 2013 updates and it just seems to sit there with the enforcement state showing unknown in the report.
Also I checked the version of client on the machines and they have the CU3 version but when I run a report to show client versions it does not show these machines with the latest version but version for sp1. It's almost like my management point
is not working. (just guessing). I checked in the component status and everything is showing green. I tried a wbemtest on one of the clients in the collection for the targeted updates and that is coming back with acceptable results.
Not sure where to look next.
I am not real proficient in 2012 yet and still bumping my way along. Any help reviewing specific logs, etc. would be appreciated. I have been searching for a solotion for several days now.

Hi,
1.Please make sure the update deployment is show up on the Deployment tab(Assets and Compliance -> Overview -> Devices -> the specific client properties)
2.Check PolicyAgent.log on the client to see whether the specific client have received the deployment policy. If not, try to run the Actions about software updates on the Configuration Manager Properties from the client.
3.Examine UpdatesDeployment.log, UpdatesHandler.log. UpdatesStore.log on the client.
Best Regards,
Joyce Li
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

Problem with update SCCM client to Sp1 CU3 on Windows 2008 server

Hi all,
I have problem with update SCCM client on Windows 2008 Server to 2012 Sp1 CU3. I have sent to deployment package with update (SP1 Cumulative Update 3 - server update) on four servers and after few minutes I have got in Monitoring\Deployment details four
this same errors in "Asset Details":
USER Message ID
Status type Description
NT\AUTHORITY\SYSTEM 1006
Error 3003
I love that types of error... which is har to find answer on google :-( I have tried but I haven't find any constructive :-( Did you met with something similar? Which log I should check (sorry - I'm still noob in SCCM2012) to update actual SCCM Client SP1
(5.00.7804.1000) to SP1 CU3 (5.00.7804.1400)?
Thank you.

I see in fodler with CU3 updates, are four packages:
- SP1 Cumulative update 3 - x64 client update
- SP1 Cumulative update 3 - x86 client update
- SP1 Cumulative update 3 - server update
- SP1 Cumulative update 3 - console update
It will be stupid but... maybe I should deploy x64 client update package?

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.

Migrate 2012 SP1 CU3 Primary Server to a new machine?

Because of some issues I am having with my current primary site server, I would like to bring up a new server and decommission the old.
The old server is running on 2008 R2 and the new server will run on 2012 R2.
Right now, I have two servers running CM 2012 SP1 CU3. I plan to upgrade the entire hierarchy to 2012 R2 before I decommission the old server.
Primary Site Server Site System Roles – Distribution Point, Endpoint Protection Point, Management Point, Reporting Services Point, Site Server, Site System
Second Server Roles – Application Catalog, Distribution Point, Fallback Status Point, Management Point, Site System, Software Update Point, State Migration Point
Can someone please help me understand the process that I should follow to make this successful?
1 - Bring up the new server
2 - Configure all settings on the new server
3 – Install Site System Roles on the new server
4 – Add SMS Provider to the new server
5 – Uninstall Site Server Roles from old server
What am I not thinking about?
Is there a better way to do this?
Thanks for any help

Hi,
For the Second Server with roles that could be an option to install a new server, and move the roles to that server.
For the Primary Site server there is no possibiltity to setup a new Primary Site server and transfer the role to that server as you can with the other roles. The way to do that would be to do a backup of Configuration Manager on the Server running 2008
r2 and restore it on the server running Server 2012 r2 as an inplace OS upgrade is not supported on a primary site server either.
You haven't mentioned where you SQL server is located either if it is local or remote.
If you have issued you could also install a new Primary Site and Migrate the objects from the old Primary Site and then reassign the clients to the new site.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Microsoft SharePoint Foundation 2010 Supports Windows 2012 R2 ?

Hello,
I have a requirement to install Self Service Portal on one dedicated Server and found that Both the Web Content Server and SharePoint Web Parts on One Computer. I want to use Microsoft Sharepoint 2010 Foundation Server as it is free.
My query is this - Does Microsoft SharePoint 2010 supports Windows 2012 R2 OS.
Below link has a details till Windows 2012 Server but not with Windows 2012 R2
http://www.microsoft.com/en-in/download/details.aspx?id=24983
Please answer.
Thanks,
Ankur

HI,
for installing SharePoint Server 2010 Fondation on Windows Server 2012 R2 Version, you Need the SP2 for SharePoint fondation.
for confirmation see this link:
https://support.microsoft.com/kb/2724471/?wa=wsignin1.0
thanks
diramoh

Reports not Generated after moving SCCM 2012 SP1 DB on SQL 2012 SP1 cluster

Hi all,
i have moved my SCCM 2012 SP1 DB on SQL 2012 SP1 Failover Cluster,this cluster is a two node cluster.the DB was moved fine and the DB configuration in SCCM Site maintenance was also done successfully.After the migration process,SCCM was working fine created
few collections & packages, then checked the DB on cluster & they were updated successfully.
but when i tried to install report server on my SCCM machine,again there was no instance displayed after entering the cluster name.
I searched this & come across this post :-
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b/
which says to install report server on the cluster node machine which is currently running the Reporting Service.I tried to install the report server & the instance was detected this time.it was installed successfully.
But when i tried to generate reports I got this error :-
Permissions are fine as i have added SCCMadmin & sccm machine in the local admin of both the nodes.
Please Help.
Thanks,
Pranay.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
If you look at your second screenshot the Remote errors is not enabled. Use this blog to enable them.
http://www.enhansoft.com/blog/enabling-remote-errors-in-sql
If changing the data source on the report fixed it for a single report. It means that your shared Datasource is having problems. Reset the username and password within CM12 console and this should fix it for every report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 SP1 CU3 - Client Install on SiteServer (PrimarySite)

We have an issue with SCCM 2012 Client deployment on our primary site all other clients are installing correctly the error is attached.
I have tried various ways to install client push even tried the SP1 Client using ccmsetup /source and this also fails at the same point.
I have done self service google and discovered this
http://www.mail-archive.com/[email protected]/msg03811.html
Anyone any ideas????

80041002=
Not found
Source: Windows Management (WMI)
Also, 1603 is a MSI exit code meaning fatal error occurred.
Have you verified you are running the SP1 sccm client and not RTM on the machine is question?
Justin Chalfant | My Blog |
LinkedIn | Please mark as helpful/answer if this resolved your post
Thanks, we have checked the error codes.
We have tested the client install onto the primary server in three different sites, on different networks/labs/environments with the same result.
Yes we have verified we are running SP1 CU3 and that the client files are the correct versions.
To eliminate the probable cause of CU3 updates being at fault, we have obtained the Client folder from the SP1 ISO (the later released updated SP1 ISO), with the exact same error.

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

How do I add my Custom Workflow Activity to FIM 2010 R2 SP1 installed on Windows 2012 server?

Hellos.
I have tried and failed to add my custom.dll into the Windows Server 2012 GAC.
We have a version of FIM 2010 R2 Sp1 running on Windows Server 2008 R2 and that was no problem. There seemed to be a gacutil.exe present on the system which added my assembly.
I cannot find gacutil.exe on the Windows 2012 Server.
I have downloaded and installed Windows SDK for Windows 8. However, when I try the gacutil.exe /i <myCustom.dll> nothing seems to happen.
Are there any guidelines how to add custom workflow activities to FIM when installed on a Windows Server 2012 system?
TIA
*HH

Well yes. It is fine when FIM is hosted on Windows Server 2008 R2.My difficulty is that I am using FIM 2010 R2 Sp1 and Windows Server 2012. No GACutility executable.
However, the problem has been resolved. Powershell can be used to modify the assemblies.
I opened a RunAs Administrator PS session. My assembly is in folder c:\Temp
Using Windows Explorer I browsed the folder c:\windows\assembly and noted the System.EnterpriseServices entries: version (2.0.0.0) and public key token (b03f5f7f11d50a3a)
(My version is 2.0.0.0 because when installing FIM and SharePoint 2013 the instructions I used suggested setting .Net version to be 2.0)
These powershell commands got me going...
PS C:\temp> [System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")
GAC Version Location
True v4.0.30319 C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50...
PS C:\temp> $publish = New-Object System.EnterpriseServices.Internal.Publish
PS C:\temp> $publish.GacInstall("c:\temp\RunPowershellLibrary.dll")
PS C:\temp>
PS C:\temp>
PS C:\temp> iisreset
Amazingly I can see the assembly RunPowershellLibrary in my Windows 2012 GAC. :-)
Also, what is more cheering is that the custom activity actually works with FIM 2010 R2 Sp1.

MacBook Pro 15" Mid 2012 says only supports Windows 7

Hi there,
I have Windows 8 already running on my MacBook Pro 15" Mid 2012 and now I am trying to install the latest drivers. But when I download the drivers via the Boot Camp Assistant it claims my MacBook only supports Windows 7.
I did the manual download on the Windows side of life, but it fails to install, shortly after hitting setup. I guess, it checks the modell and fails.
Also, maybe or maybe not, unrelated in the MacBook's about me it claims to be a 13", where as in the system report it shows the correct information.
Any idea would be appreciated...
Thanks,
Thomas

https://discussions.apple.com/message/21540547#21540547
projectRelentless has some work arounds that may help here specifically:
If you want, try and click setup in this latest BootCamp support set, and you will get another sad error claiming x64 is not supported, something awful to that nature. Awww man, this far, only to get let down. Nope. We are going to fix that. And this is where ErikVanD's post pointed me to what we do next.
It was said to navigate in the BootCamp 5.0.5033 folder to something of the effect of BootCamp/Drivers/Apple and run the MSI file "BootCamp" (MSI file will say Windows Installer in its description, and not necessarily MSI for anyone not too savy with Windows) **note - NOT .bootcamp (notice the period in the front) and it should work and install the new Windows 8 support for your MBP...but in my case it didn't, which is why im posting how i fixed this. Your setup may somehow be different, but mine gave me an error say it "needs elevated permissions to run, use setup.exe instead. We tried that remember! And it gave us the x64 not supported error. Oh man! Blabbing aside, this file needs to be ran as an administrator, which yeah your the only user, but Windows is funny like that. Normally youd just right click, and select run as administrator, but out the box, that option isnt there when you right click, only install, repair, open with etc. Here's the next trick, you need to add a registry file to enable running as an administrator, dont be afraid, this is an old trick, and really easy.
Open notepad in Windows, and create a new doc, call it Add_MSI_run_as_administrator.reg
Paste this following code into the new doc
Windows Registry Editor Version 5.00
HKEY_CLASSES_ROOT\Msi.Package\Shell\runas] "HasLUAShield"="" [HKEY_CLASSES_ROOT\Msi.Package\shell\runas\Command] @=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\ 00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\ 73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\ 00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
Or download the file already made from my company server at http://www.theprojectdev.com/public/pub.html **i put this there as a courtesy to help others like me, its just a complete reg file, so either create your own through copy and pasting above or download it. Either way, put it on your desktop.
Now double click the new registry file, and allow/ok it to do its thing.
Once done, you can discard the file from your desktop, or keep, your choice.
Guess What!? Now we can do the impossible! Lets revisit that solution from before by going to the newest BootCamp 5.0.5033, and navigate to BootCamp/drivers/Apple and select that tricky BootCamp MSI file that wouldnt allow us to run, this time RIGHT CLICK it. Because of our new registry entry we placed, we now have an option to "Run as Administrator" Click that option.
WooHoo! We have done what coudnt be done, BootCamp will now walk you through the installer, and add all the great support for Windows 8
Boot Camp Support Software 5.0.5033
http://support.apple.com/downloads/DL1638/en_US/BootCamp5.0.5033.zip

SCCM 2012 Sp1 CU3 support Windows 2012 R2 deployment?

Similar Messages

Maybe you are looking for