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

Similar Messages

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

Issue with SCCM 2012 SP1 U5 upgrade and client published version

Recently we upgraded our SCCM server to SP1 U5, and our published and available client version is still at 5.00.7804.1000 instead of 5.00.7804.1600. We ran the hotfix to upgrade it and it looked like everything had went through. Does this not also
upgrade the client? It doesn't seem like you can run the hotfix again after you've already installed it once to repair either. Is there another way to update the published version inside the console? We have it as a package right now to deploy to all the systems
but I was hoping we could upgrade the internal one and let it run more automatically. Any advice would be greatly appreciated.

More info:
How to update ConfigMgr clients automatically… in SP1
http://configmgrblog.com/2012/12/03/how-to-update-configmgr-clients-automatically-in-sp1/
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.

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

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.

How to Custom Report using sql server report builder for SCCM 2012 SP1

Hi ,
I am new to database, if i want to create a manual report using sql server report builder for SCCM 2012 SP1, what step should i take.
i want to create a report in which computer name, total disk space, physical disk serial no come together. i already added class (physical disk serial no.) in hardware inventory classes. refer snapshot

Hi,
Here is a guide on how to create custom reports in Configuration Manager 2012, it is a great place to start, change to the data you want to display instead.
http://sccmgeekdiary.wordpress.com/2012/10/29/sccm-2012-reporting-for-dummies-creating-your-own-ssrs-reports/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

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

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

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

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

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

SCCM 2012 Client Communication Issue with SCCM 2007

My Clients was installed SCCM 2007 client version but somehow those clients reporting to SCCM 2012 Server
Note : My SCCM 2007 Server still active mode . and the SCCM 2007 client IP boundaries was not added into SCCM 2012 server
But still communicating to SCCM 2012 , what is the root cause ?
Best Regard's Krishna

Either, during the client installation the client was manually assigned to the ConfigMgr 2012 site (by specifying the site code), or during the client installation the client was auto assigned to the ConfigMgr 2012 site (that can only happen when there
is an overlap in the boundaries and that doesn't have to be the same type of boundary).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Adobe Creative Cloud Enterprise Deployment Issues using SCCM 2012 R2

Hi,
I have been trying to deploy Adobe Creative Cloud Enterprise to Windows 8.1 machines that are identical, using SCCM 2012 R2.
The Adobe package seems fine, because it seems to deploy successfully to some machines. And SCCM 2012 R2 has been configured correctly, as I can deploy other software using it, and again, it deploys Adobe CC successfully to some of the machines.
I have tried comparing the package that is downloaded on the test machine/client machine, with the original package on the distribution point, using Beyond Compare, and there are no differences.
I have contacted Adobe Enterprise Support, and they asked me to send to them log files from Event Viewer, the msi installer, and other Adobe logs, from the machine that failed the deployment. However, after Adobe studying them, they told me that they could not identify any problems... Strange, because I could have sworn that I saw error 1603 pop up over 20 times on different machines indicating that the 'Set-up.dat' file had a problem with it.
After all the testing on over 20 identical machines (same hardware/same software), using different configurations on SCCM 2012 R2 and the client machines, I still can't seem to have a reliable solution to deploying Adobe CC.
The fact that it deploys successfully on one machine and fails on another, or sometimes deploy to two machines and fail on another (simultaneously), is something that I don't understand.
Another thing is that, if I retry the deployment 10-15 times after it failed the first time, it might go through...
Adobe Enterprise Support asked me if they could remote into a machine that failed the deployment to have a look at it and I agreed to that option, but it seems like my issue has been ignored because they never got back to me.
Has anyone had this kind of problem or anything similar before?
I need to be able to deploy this remotely to 100+ machines. So installing manually is not an option.
Any help is appreciated.
This was posted in the wrong section a few days ago. I'm hoping I can get some help here.
Case Number: 1862659812
UPDATE: I spoke to Adobe Customer Support and after 1.5 hours on the phone with a remote session going on, problem was still not solved or identified. Additional log files have been sent and now I'm waiting for a call back.

Hi Robert,
We seem to be having a very similar issue. Our installs would randomly fail with error code 1603 and an error message about a fault in Set-up.dat. Failure rate was near 95% on our 900 machines. Adobe Support and Karl having been looking into our issues but so far no solution has been found.
Having done a lot of investigating we've managed to deploy our package using a schedule task running as a domain admin. This is a nasty solution and we don't intend on using this permanently, but we needed to get the package out.
Are you seeing any of the following:
Entries in PDApp.log:
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The Bootstrapper Process is (5).Stopping the installation process.
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The return code from the Adobe Installer Process is (33).Stopping the uninstallation process.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to find the pdb database.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to get the local payload database handle.
Event Log:
Faulting application name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Faulting module name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Exception code: 0xc0000005
Fault offset: 0x000d7c52
Faulting process id: 0xb40
Faulting application start time: 0x01d072a073861622
Faulting application path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Faulting module path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Report Id: c86d9216-de93-11e4-8284-782bcb99e284
Faulting package full name:
Faulting package-relative application ID:
Installer Log
Indicates it can't find the Media_db. We noticed that the folder C:\Program Files (x86)\Common Files\Adobe\caps doesn't get created on the machines were the install fails, so error message is correct in that there isn't a Media_db.db. Sysinterals Process Monitor seems to show that the setup tried to create the folder/files but they don't actually get created. Copying a Media_db into the folder from another machine seems to allow the installation to almost finish, but unsurprisingly you end up with problems later on.

Perms to specific reports folder in sccm 2012

Have set up access to certain reports based on security settings in sccm so accounts in specific AD group can access certain sccm reports via ssrs reporting web site. Utilized the very useful information in the links below. I have a request for
the group to access the network folder reports, but that means I would have to give RUN REPORT perms to the SITE permission in the security role, as that is the only group that includes the network folder. I don't want to give them access to the
rest of the stuff it includes, such as client push, client status, replication traffic, etc., as that would just cause confusion among the customer base. I don't want to give them anymore than they need. I tried giving the group rights to the individual
reports in the network folder, but the problem is that since there is no access to the folder itself without doing the above, they can't get to the reports. I could give them rights to the folder via SSRS but then SCCM would just overwrite that 15 minutes
later. Does anyone have any suggestions on this one? Thanks. : )
http://skamie.wordpress.com/2010/06/24/ssrs-and-uac/
http://blog.coretech.dk/kea/creating-the-reporting-user-role-in-configmgr-2012/
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/8525cfa6-aaa4-4d34-a296-a9a8cb76e5a3/

I'm not concerned about giving them more rights, I'm concerned about giving them access to reports that they don't need access to, otherwise there would be widespread confusion and misunderstanding. This, in turn, would generate anxiety-based
calls to the support desks, that I would like to avoid. I'm not trying to hide anything from them, I just don't want to cause undue worry and confusion. Make sense?
So don't give them access to reports that you don't want them to have. Here is a blog that will tell you how to grant access to one report.
http://be.enhansoft.com/post/2013/11/07/How-to-Grant-Permission-to-a-Single-SCCM-2012-SSRS-Report.aspx
http://www.enhansoft.com/

Thin Client reporting issues since SCCM 2012 R2 CU3 upgrade.

Similar Messages

Maybe you are looking for