SCCM 2012 R2 CU3 UPGRADE BROKE REMOTE ADMIN CONSOLE CONNECTIVITY

I installed SCCM 2012 R2 CU3 on my site server but it broke a couple things. I've never had problems with SCCM upgrades before. The admin console works if you log into the site server and run it from there but not when you try it from anywhere else (another
server or a workstation). When you open the admin console on the site server it does have the new version of 5.00.7958.1401. Of the five suggestions that appear when your console won't connect, here's what I know:
1) the remote machines can all ping the site server (call it server 01)
2) we know it's not my account that's a problem as I can open the console on the site server itself
3) This problem happens on server 02, which I put the new admin console on. It also happens with other machines which still have the CU2 console
4) Yes, I'm an admin role, shown by logging into the console on the site server
5) I have another network where everything works. I have not put CU3 on it yet, of course. The WMI permissions on Root, Root\SMS, and Root\SMS\site_ABC are identical on both site servers yet it works on non-upgraded one and not on the upgraded one.
WMI info-I can WMI connect from the site server to these other machines but not WMI connect from the other machines to the site server: not root, SMS, or SMS\site_ABC, nor cimv2, even though the permissions match what is on the working network.
When I launch the console from the site server entries about loading the console loading ok are in SMSAdminUI.log, but when I try to launch the console from other machines no entries are made, even though I changed the SmsAdminSNapIN value to VERBOSE.
I checked DCOM permissions and they are the same on both networks.
Another issue that appeared with this upgrade: I can install the client upgrade to CU3 on other machines but on the site server it fails with "Internal Error 2503" and when you click OK it you get "Internal Error 2502".
Ben JohnsonWY

I'd suspected this WMI problem was only affecting our Server 2012 boxes. I compared RSOPs and noticed the ones having this problem were all under the same OU and getting few GPOs. Our GPO person found a GPO that has somehow become unlinked. He relinked
it. After a gpo update AND a reboot these machines start working again. So CU3 did not cause this WMI after all.
And yes, the CU2 consoles won't connect to a CU3 site server, you have to run the console upgrade.
I fixed the "internal error 2503/2502" by doing this: open task manager, click details, end the explorer task (screen will look blank at first). Click File and select "start new task", enter "explorer.exe' and click the run as admin
button. The msp for CU3 client installed and the screen looks normal again. I only saw this error on the site server and have never seen it before.
Ben JohnsonWY

Similar Messages

Thin Client reporting issues since SCCM 2012 R2 CU3 upgrade.

Please forgive me, I'm a SCCM newbie. I'm having an issue with my Thin Clients reporting back to SCCM since I upgraded to 2012 R2 CU3.
The only pertinent thing I find in any log is "RegTask: Failed to get registration state. Error: 0x8009000b" "GetRegistrationState failed (0x8009000b)" in the ClientIDManagerStartup.log
If anybody has any tips, I would be more than appreciative.

I have not run into this before, but have you validated that your management point is healthy?
This thread has a couple things to try as well:
https://social.technet.microsoft.com/Forums/en-US/0d2e369d-cd93-4145-8db3-e9943c99a4ae/client-property-set-to-no-application-deployment-not-working-issue-with-registering-to-mp?forum=configmanagergeneral
Jeff

Reports Visible on SCCM Server but not in the Remote Admin console

Hello All,
I have a little issue with reports not showing up on my admin console. Odd things is that when I log into the sccm server the reports are visible and can be run without issue. How can I get the reports to show up in my admin console. I have included screenshots.

First off can you access the report in the native web interface remotely?
BTW I don't recommend accessing the report via the console too much overhead.
http://be.enhansoft.com/post/2013/09/10/Should-Configuration-Manager-SSRS-or-ASP-Reports-be-Accessed-from-the-Browser-or-the-Console.aspx
http://www.enhansoft.com/

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

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

SCCM 2012 SP1 - R2 Upgrade Incl Windows ADK for Windows 8.1 Update

Hi All
I Need some advice
We are preparing for the upgrade SCCM 2012 SP1 -> SCCM 2012 R2
Quick steps:
1 Uninstall ADK 8.0
2 Install ADK 8.1
3 Upgrade SCCM 2012 SP1 -> SCCM 2012 R2
4 Install CU1 SCCM 2012 R2
5 Upgrade Clients to SCCM 2012 R2
6 Upgrade Clients to SCCM 2012 R2 CU1 with WSUS (SCUP)
But today I read the following article
http://blogs.technet.com/b/configmgrteam/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-configmgr-osd.aspx
How does this update fit in the upgrade process (add step 7 and install this update on the SCCM Server) , or is it better to leave this update because windows PE5.1 is not supported yet.
I hope someone can give me some good advice
regards and thx in advance
Johan

Hi All
So I can also use the ADK 8.1 Update with the installation , so my quick steps will be than for the upgrade SCCM 2012 SP1 -> SCCM 2012 R2
1 Uninstall ADK 8.0
2 Install the ADK 8.1 UPDATE
3 Upgrade SCCM 2012 SP1 -> SCCM 2012 R2
4 Install CU1 SCCM 2012 R2
5 Upgrade Clients to SCCM 2012 R2
6 Upgrade Clients to SCCM 2012 R2 CU1 with WSUS (SCUP)
Regards
Johan

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)

SCCM 2012 R2 CU3 PXE issue

Hi,
I have a SCCM 2012 R2 CU3 lab where pxe is not working, the clients are able to connect to SCCM server but the download gets stuck on the boot image & then it fails with the following error :-
Don't find any specific error related to this deployment in SMSPXE.log.
Thanks,
Pranay.

I've had some issues various places with NICs and the TFTP process. One fix I implemented was to add the following registry entry:
Location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSTFTP
Name: MaximumBlockSize
Type: (REG_DWORD)
Value range: 512–1456
Base: (Decimal)
I set it to 1024, but you need to determine what value works for your environment.
This is documented here:
http://support.microsoft.com/kb/975710/en-us
Jeff

New-CMVhd error Not Found - SCCM 2012 R2 CU3

When trying to execute New-CMVhd via powershell in SCCM 2012 R2 CU3 I get a "Not Found" error.
This happens in our production and pre-production environments.
Using the Console wizard works fine.
Command is:
New-CMVhd -Path "\\machine\D$\Windows2012R2Server_SCCM.vhd" -Name "Windows2012R2Server_SCCM" -Version "1.0" -VHDSize 100 -TaskSequencePackageId "XXX00123" -DistributionPointServerNames "server.contso.com" -Description "Built with Deploy Server To VHD Task Sequence." -Verbose
Output:
VERBOSE: Performing the operation "New" on target "Vhd: New".
VERBOSE: Executing WQL query: Select * From SMS_TaskSequencePackageReference_All where PackageID='XXX00123'
VERBOSE: Query options: None
VERBOSE: Executing WQL query: Select * From SMS_DistributionPointInfo where Name='server.contoso.com'
VERBOSE: Query options: None
VERBOSE: Query 'Select * From SMS_DistributionPointInfo where Name='server.contoso.com'' processed 1
results.
VERBOSE: Executing WQL query: SELECT Distinct tspr.RefPackageID FROM SMS_TaskSequencePackageReference_All AS tspr WHERE
tspr.PackageID='XXX00123' and tspr.RefPackageID Not In (SELECT PackageID FROM SMS_Package AS p WHERE
p.PkgSourceFlag=1)
VERBOSE: Query options: None
New-CMVhd : Not found
At line:1 char:1
+ New-CMVhd -Path \\machine\D$\Windows2012R2Server_SCCM.vhd -Name "Windows201 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Confi...s.NewVhdCommand:NewVhdCommand) [New-CMVhd], WqlQueryExc
eption
+ FullyQualifiedErrorId : UnhandledExeception,Microsoft.ConfigurationManagement.Cmdlets.Osd.Commands.NewVhdCommand
Can anyone else reproduce this? I have a feeling it will be a premier support call to Microsoft :-(
Thanks

Hi,
Pls try to run the following command to import CM powershell module and change the path to be the CM server before your new-cmvhd command:
import-module 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1'
Set-Location CMserver:\
“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.”

Hardware Requirements for a SCCM 2012 CAS with SQL Server Remote

The hardware requirements for a CAS server with SQL Server Enterprise locally installed are:
16 cores (Intel Xeon L5520 or comparable CPU)
64 GB of RAM
1.5 TB of disk space for the operating system, Configuration Manager, SQL Server, and all database files.
Does anyone know what the hardware requirements are if SQL Server Enterprise is remote from the CAS server? It's not listed. -Shane

Even though I am going to be strung up for even saying this, I do agree there is a use for a CAS outside of 100,000 users. If you do indeed have distinct admins managing their own images and apps in remote
locations then I see the benefit of a CAS. A remote ConfigMgr console connecting to a primary site would perform poorly. Admin A at the primary site would not experience any issues but Admin B would be in for a lot of work and waiting. Any
time Admin B needed to add an app or image it would have to be copied up to the remote primary site and then distributed back down. This is not the best scenario.
There are scenarios in company merger situations (and others I am sure) where the management of both locations has not been consolidated down to one location yet and is not going to be done as part of the deployment or upgrade. If you had a 2007 environment
it is going to be very hard to convince the admin at the remote location that this upgrade is going to be a good thing for him/her. There is an option for the remote admin to RDP into a server in the primary site but the image and apps still need
to be distributed down to the remote location. During testing this can be very time consuming.
I do agree that adding a CAS adds additional complexity but in some cases such as the one I described it is the right decision.
Thank you for the reply. And i totally agree that in some cases a design like that is a necessary evil (but not by our personal wants).
We had that design with 2007 (implemented before my time), and as you predicted EU admins complained about difficulty using the console RDP-ed into a box close to the primary site. The bandwidth to and from different regions is out of scope for me so I do what
I can with what I have. We too will be moving forward with a CAS hierarchy.
Administratively the other IT depts in other regions operate on their own. I dont handle any of the EU computers on a day to day basis whatsoever, etc. We're not merging but our IT shops operate with near independence.

SCCM 2012 R2 -CU3 fails at 'Create Software Update Catalog'

Hi
I am trying to upgrade SCCM 2012 R2 CU1 to CU3 (skipping CU2) but the upgrade fails in the middle with following message in the log
Task 'Create Software Update Catalog' completed, state is 'failed' ExceptionText: Error: Setup detected an unexpected problem during installation. Error message: A valid file name is required.
Parameter name: fileName
I have checked following article but it does not fixed mine.
https://social.technet.microsoft.com/Forums/en-US/05ddea79-ca6c-4958-bd54-ceac4b787dd9/problem-installing-sccm-2012-r2-hotfix-kb2905002-wdsosd-slowness-issue?forum=configmanagerosd
Already uninstalled CU3 and reinstalled it with no luck so I was wondering anyone has any ideas as what might be causing it?
Thanks

** RESOLVED **
After attempting several times and uninstalling when it failed, finally it got installed successfully.
Since I was skipping CU2 so I thought to install that as well before installing CU3. However, the CU2 also failed at Admin Console update. Re started installing CU3 but this time I choose not to create deployment packages for client, server and console.
Not sure if that fixed it or CU2 but I am glad its over now. After installing CU3 successfully, ran the installer again to create all required deployment packages for console, client and server.
All looks good now.

SCCM 2012 R2 CU2 Admin Console Connects But Closes In A Few Seconds

I built a new SCCM 2012 R2 CU2 suite on Server 2012 R2. There are four servers: site server, secondary DP, WSUS/SUP, and a SQL server. On the first three the SCCM Admin Console will open. But when logged into the SQL server, the Admin Console opens
for a couple seconds, then closes. The SQL box can connect via wbemtest to
\\server\root\sms\site_ABC. I have checked all the items that show on the screen when your console won't connect. There are no errors in the smsprovl.log on the site server. I think this problem is on the SQL server.
This is one of three problems I've had a lot of difficulty with on this network. I'm making separate threads for all three
Ben JohnsonWY

I have been able to verify this problem generates 4 entries in Event Viewer/System logs. In the order they get generated by first in time:
1st - A fatal error was generated and sent to a remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 43. The Windows Schannel error state is 552.
2nd - The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting was (the IP of the SQL server). The
SSL connection request has failed. The attached data contains the server certificate.
3rd - DCOM was unable to communicate with the server servername.fqdn using any of the configured protocols; requested by PID 3cb8 (C:Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe)
4th - an exact repeat of the 3rd entry.
Ben JohnsonWY

SCCM 2012 R2 CU3 & Intel AMT firmware versions

Hi,
We are in the process of implementing out-of-band management for Intel AMT Computers and have managed to get everything working on some older test computers. Today we realized that the current OOB functionality in SCCM 2012 is seriously limited as it officially
supports AMT firmwares up only to 6.1. The reason for this is that SCCM OOB uses a depricated SOAP interface and not the newer WS-Management interface. Some newer firmwares we have tested seem to support SOAP (like 8.1.40) but atleast 9.x is no longer supported.
Because of this the OOB of SCCM 2012 is not suitable for any real production environment since it does not support the newer firmwares.
We know that Intel offers an add-on to circumvent this limitation, but we would prefer using only "native" SCCM functionality.
Does anybody have an idea when is Microsoft going to add support for recent Intel AMT firmwares and make OOB usable for real-world environments?
Thanks!

When I called CSS about this they told me to use the Intel stuff. I agree with Jason, my opinion is that this feature will not be upgraded.
John Marcum | Microsoft MVP - Enterprise Client Management
My blog: System Center Admin | Twitter:
@SCCM_Marcum | Linkedin:
John Marcum

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 R2 CU3 UPGRADE BROKE REMOTE ADMIN CONSOLE CONNECTIVITY

Similar Messages

Maybe you are looking for