Machines not Joining Domain SCCM 2012 R2 CU4

SCCM 2012 R2 CU4
Recent change CU1-4
This was all working until recently. The SMSTS log shows no failures. The Netsetup.log has no entries. The Panther\setupact.log shows a few odd things " [msoobe.exe] Failed to open event to start up services [0x80070002]" but then appears
to proceed fine.
The account used for Domain join is not locked out. I have no log telling me why it is not working. I have refreshed the drivers on the DP just incase the NIC driver got corrupt, though it appears to be fine in device manager and works.
I am just lost as I don't have any log that shows me any real failures and since SCCM passes the Domain Join off to the OS I don't know where else to look.

Is this a duplicate of
https://social.technet.microsoft.com/Forums/en-US/9122cebc-11b9-4f81-a5d7-3a14667f874c/smts-not-correct-showing-code-0-for-programs-while-none-get-installed-no-domain-join?forum=configmanagerosd#d5670eeb-55de-493c-abf1-eec9397d7081 ?
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

SMS Provider Locations Do Not Match - Problem installing SCCM 2012 R2 CU4

I have an SCCM 2012R2 CU1 site that has been upgraded from SCCM 2012 non-SP1, so I have gone from 2012 to 2012SP1 through CU5 and then to R2 and then to CU1.
Over the course of the life of this site, which has more than 10k clients and 10 Site Systems, we have installed roles, removed roles, moved roles and removed Site Systems.
I have also installed and removed SMS providers . . . which is where my issues begin.
The site properties in the console list 6 SMS Providers and even lists an SMS provider on a server that was retired and is no longer a Site System. When I query WMI using the following VBS script it only returns the *ACTUAL* SMS Provider locations,
2 of the 6 listed in the GUI.
On Error Resume Next
Const ForReading = 1, ForWriting = 2, ForAppending = 8
strComputer = "."
Set oFS = CreateObject("Scripting.FileSystemObject")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\sms")
If Err.Number <> 0 Then
WScript.Echo "Cannot connect to WMI"
WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
End If
Set oLog = oFS.OpenTextFile("C:\Temp\SMS_ProvList.log",ForAppending, True)
If Err.Number <> 0 Then
WScript.Echo "Could not create output file"
WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
End If
Set colItems = objWMIService.ExecQuery("SELECT * FROM SMS_ProviderLocation",,48)
count = 0
For Each objItem in colItems
count = count + 1
oLog.WriteLine "-----------------------------------"
oLog.WriteLine Now()
oLog.WriteLine "Provider instance " & count & " : " & objItem.Machine
oLog.WriteLine "NamespacePath : " & objItem.NamespacePath
oLog.WriteLine ""
Next
I have a test environment which has also gone through some growth over its lifetime and has had the same changes to SMS Providers made. When I first attempted to install SCCM 2012 R2 CU4 in this test environment the installer continually failed the
prerequisite checker when querying the CU level of the SMS Providers. The only way that I could get past that issue was by running a site maintenance task via the CM installer and installing an SMS Provider at the location that had previously been an
SMS Provider but I had uninstalled that role.
I do not want to have to do that in my production environment, and would not even be able to do so if I wanted as I have retired one of the servers listed and cannot re-provision that machine.
Any CM12 gurus out there with suggestions? This strikes me as a standard MS problem when having multiple development teams working on a product/update and not having a standard location to check for configuration information (This is exactly the problem
when configuring DNS suffixes via GPO and not manually setting the GUI to match).
Thanks!
Josh Gerner
Cornell University.

The issue I have is that I cannot find the WMI class that holds the SMS Providers that are returned by the GUI.
I actually engaged MS Premier for a SCCM 2012 RAAS about 2 years ago and that was when the discrepancy first reared it's head. The support person that I worked with couldn't give me a way of cleaning those entries at that point which is when I started
logging the locations to be sure that my maintenance task was really installing or removing the SMS Providers.
Josh Gerner

After installing SCCM 2012 R2 CU4, I show a Distribution Point warning that won't clear.

I recently installed SCCM 2012 R2 CU4 on a LAB environment, and nowhere is it more important to wait until all requisite site roles are reinstalled before doing anything else.
I did, and still do, have an warning/ error on the Site components that shows up on one of the child primary sites after the CU4 installation.
Distribution Manager has not tried to install IIS component of operating system to distribution point “[“Display=\\SCxxx\”]MSWNET:[“SMS_SITE=xxx”]\\xxx\”. You should install and configure IIS manually. Please ensure RDC is also enabled.
IIS is installed, RDC is enabled, but I get this error. What could be the real issue?

Hi,
So you have tried to reinstall IIS conponents and DP?
Have you checked the distmgr.log? Anything helpful?
Best Regards,
Joyce
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]

After SCCM 2012 R2 CU4 update Client won't report status message back

We had SCCM 2012 R2 CU3, just updated it to CU4 (all site servers and clients) last week.
Right after the clients received the CU4 update (no reboot), I saw these started popping up the event log:
The ConfigMgr Client encountered a certificate for Management Point SCCM that could not be verified.
I checked online and it has to do with trusted root key mismatch, but there was no site change. The only thing we did was upgrading from CU3 to CU4.
Right now the symptom is that all these clients do not report status messages back to the MP so we have no idea how our deployments would go.

i am having what i think is a similar issue. i upgraded to CU4 and the only clients to report back in are my SCCM site server and my only DP server. no clients have reported in since. i checked a few clients and they did get the CU4 client update
and installed it but they are not reporting back
I have pretty much the same situation.
A successfully upgrade to SCCM 2012 r2 cu4 on the primary site.
Deployed the cu4 to a few computers which was successfully. Later I also deployed the cu4 to the primary site server and it turned out to be the only computer reporting back with the proper client version.
There is no errors or warnings in the event logs which could explain this strange issue. As far as I can tell the clients is operational but they are just not reporting back with the proper client version. A quick look at the sccm client
logs has also not revealed the root cause.
Any ideas would be appreciated a lot.
Per Dahl Christiansen

SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
Today I migrated one of the DP's which seems to work well.
However all my packages shows now the status "unknown" for this migrated DP.
This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
Any idea how to solve this ? R2 install ?

Some additional information:
I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
share......then i guess i can remove the content from the "old" distribution point share ????
I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
--> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
--> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
will become available Successful and the package will become available on the distribution point share
But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
Any help, ideas, tips, hints, recommendations ?
My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

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)

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

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

MDT TS not joining domain

Hi,
I'm experiencing something weird. my MDT 2010 U1 TS doesn't join HP Compaq 6200 & ProBook 6460b to the domain when I deploy Win 7 x64. It works for x86.
I'm using drivers packages and my WinPE have all drivers (same version x86 and x64). I didn't enter my domain informations in the CS.ini, I only use the "Apply Network Settings step for the domain. It's configured correctly with the SCCM account to use to join
the domain. My computers account are created manually in a OU before do the OSD (not a container). I did F8 during the TS and the computer have an IP and I'm able to ping it all the time during
Here is the log in advertisement status in SCCM:
Severity   Type   Site code   Date / Time   System   Component   Message ID   Description
Information   Milestone   CTX   07/06/2012 9:30:05 AM   COMPVALERIE   Task Sequence Engine   11134   The task sequence execution engine successfully
completed the action (Apply Network Settings) in the group (PostInstall) with exit code 0 Action output: ==============================[ OSDNetSettings.exe ]=========================== Command line: "osdnetsettings.exe" configure Setting %SystemRoot%
to "D:\Windows" Loading existing answer file "D:\Windows\panther\unattend\unattend.xml" Configuring global network settings Join type: 0 Joining domain: sa.domain.com Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64" DNS domain:
DNS domain search order: IP filter sec enabled: false No adapters found in environment. Performing global configuration only. Writing configuration information to D:\Windows\panther\unattend\unattend.xml Successfully saved configuration information
to D:\Windows\panther\unattend\unattend.xml Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings finished: 0x00000000.
For some others computers able to join the domain, I have the same results in the advertisment status log file.
Here is some log from the BDD.log:
Loaded D:\Windows\panther\unattend\unattend.xml   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
Merge specified, but D:\_SMSTaskSequence\WDPackage\Control\\Unattend.xml wasn't found, unable to merge   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
Property UPGRADE is now = false   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
Property ComputerName is now = COMPVALERIE   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for FullName   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for OrgName   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for ProductKey   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for JoinDomain   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for MachineObjectOU   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for JoinWorkgroup   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
No value found for DomainAdmin   zticonfigure   07/06/2012 9:30:06 AM   0 (0x0000)
Here is the netsetup.log file:
ï»¿06/01/2012 09:53:29:714 -----------------------------------------------------------------
06/01/2012 09:53:29:714 NetpDoDomainJoin
06/01/2012 09:53:29:714 NetpMachineValidToJoin: 'COMPVALERIE'
06/01/2012 09:53:29:714    OS Version: 6.1
06/01/2012 09:53:29:714    Build number: 7601 (7601.win7sp1_gdr.110622-1506)
06/01/2012 09:53:29:714    ServicePack: Service Pack 1
06/01/2012 09:53:29:807    SKU: Windows 7 Enterprise
06/01/2012 09:53:29:807 NetpGetLsaPrimaryDomain: status: 0x0
06/01/2012 09:53:29:807 NetpMachineValidToJoin: status: 0x0
06/01/2012 09:53:29:807 NetpJoinWorkgroup: joining computer 'COMPVALERIE' to workgroup 'WORKGROUP'
06/01/2012 09:53:29:807 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
06/01/2012 09:53:29:838 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x0
06/01/2012 09:53:29:838 NetpValidateName: name 'WORKGROUP' is valid for type 2
06/01/2012 09:53:29:979 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
06/01/2012 09:53:30:057 NetpJoinWorkgroup: status: 0x0
06/01/2012 09:53:30:057 NetpDoDomainJoin: status: 0x0
Now the thing weird is the smsts.log file:
Found network adapter "Bluetooth Device (Personal Area Network)" with IP Address 0.0.0.0.   TSMBootstrap   07/06/2012 9:45:23 AM   2292 (0x08F4)
Found network adapter "Intel(R) Centrino(R) Advanced-N 6205" with IP Address 0.0.0.0.   TSMBootstrap   07/06/2012 9:45:23 AM   2292 (0x08F4)
Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 0.0.0.0.   TSMBootstrap   07/06/2012 9:45:23 AM   2292 (0x08F4)
During the TS a I did F8 and it get a IP address and I'm able to ping the servers but why in the log I don't see an IP ? What do I need to fix this ?
And Why the netsetup.log file see WORKGROUP instead of the domain ?

Hi,
Have been struggling with this is issue for months! Have only just this minute got it to work. Thought I would share how I got it to work, just in case other people may find it helpful.
We here use SCCM 2012 R2, and deploy images using SCCM Task Sequences. For months now we have not been able to get our HP Probook 6560b's to finish installing and join to the domain. The task sequence would finish and show a Windows 7 login screen for a
local account.
Having tried a matter of many different ways it has worked using the driver, as mentioned above by Olivierdsm2 and MattGrimley.
First I downloaded the HP Driver pack for the Probook 6560b. I made them all into folders corresponding to Driver Category, Audio, Chipset, Network. Making sure any EXE's are unzipped to show raw INF form if applicable. I then made sure the Network driver
was removed and replaced with the one mentioned by Olivierdsm2 and MattGrimley. The Intel(R) 82579LM Gigabit Network Connection v11.15.16.0.
I created a new Virtual Machine on our Hyper-V server, with a clean Windows 7 image. I installed all software required for the image such as Office 2010, and then completed Windows updates. I then used Sysprep to generalize the image and make it OOBE. I
added the WinPE iso to the CD Tray in Hyper-V and as the VM shut down it booted into WinPE. I then used DiskPart to list the volumes, just so I could see which Drive letter corresponds to each partition, as I will need these details for next command lines.
I then exited Diskpart and entered into Image X to capture the WIM. I captured the WIM to local drive and then copied over to my computer where I used DISM to mount the WIM and then to apply the HP drivers from the folder location mentioned above. Making
sure to use the Recurse switch so it adds drivers from within the folders. It imported successfully and then commited the changes so the WIM was unmounted.
I then copied the WIM to my SCCM server and imported it to the Operating System Images section. making sure I distributed the content. I added the WIM to my Task Sequence and named it so it was specific to the Probook 6560b. I changed the task sequence by
deleting auto install or apply drivers, as these are now in the image itself. So I will only install this task sequence to Probook 6560b's.
Having done all the steps I then made the task sequence available to PXE and Media and ran the installation on the Probook laptop, and it actually FAILED!!
The network driver didn't actually install from DISM. Logged into Laptop and on Device Manager the network driver wasn't installed. I then installed the Network Driver "The Intel(R) 82579LM Gigabit Network Connection v11.15.16.0 " manually from the laptop
and it then installed ok. I followed the same steps above to Sysprep, and capture image with ImageX. Then once I added the image to SCCM and to the task sequence, I ran the installing again to the laptop and IT WORKED!!! The laptop came on, and it was joined
to the domain!
I did this from Hyper-V as I read that this will create an image that doesn't have too many drivers from the reference image device. I don't know if this still would work capturing straight from the laptop itself, but when I did try this before I logged
in locally to check the driver version and it was always an up to date driver, which must be why it never worked before. I think our drivers and driver packages from SCCM must have the newer drivers as to why this didn't work from there. But I'm just happy
this now works and we can save time not having to do things manually.
Hopefully this may help anyone with similar issue who is in difficulty with this. Would never have got it to work if I hadn't come across this forum entry. Even if it is for MDT. Could not find any other site that helped with this issue.
thanks,
Don

OSD Task Sequence - Will Not Join Domain

Good Afternoon!
I have had much experience with SCCM 2007, but am still getting used to SCCM 2012. Today, I set up and deployed my first test OSD deployment.
Everything worked fine except one little thing - the computer did not join to the domain.
Below is what I've tried to get this resolved...
- Verified credentials in TS were correctly entered
- Tested and was able to join the same computer TS was run on to the domain using the same credentials (including their formatting) which are in the TS.
- Checked the NetSetup.log in C:\Windows\Debug - It didn't exist. After joining the domain manually in the step above, it did, though.
- I didn't see anything that stood out in the smsts.log.
I'll be happy to attach any log files if needed. Any suggestions? THanks!
Ben K.

Hi Torsten,
there is no netsetup.log. As stated earlier in this topic, I'm also convinced that the phase where it goes wrong has nothing to do with SCCM. It looks like the hardware installation phase is somehow skipped.
The difference between version v01 and v05 are feature installations and software installations. We are building a thick image. It has now grown to approx. 30 GB. Nothing's really special about the image. Except the large application installations.
We capture the image with a SCCM Capture task, which has always done his job right. :)
I'm now going to recapture the image. I hope this was just a small bug with the last capture. I use TSMBAutorun to capture to an image. Since I am at a customer now and this is my last day over here, I cannot guarantee to give feedback on the status
of the capture and imaging task. If possible, I will post the result in this topic.
If you found this post helpful, please “Vote as Helpful”.
If it answered your question, please “Mark as Answer”.
Christian Gude | www.itexperience.net

Cannot install SCCM 2012 SP1 CU4

Hi,
I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
Anybody experiencing the same behavior ?

The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file? .
CU4 was released this week:
http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Query for collection is not function on SCCM 2012 R2

Hi,
I have a System Center 2012 R2 Config Manager as single management point. The SCCM is already have Endpoint Protection Point role installed. Then I need to create a new collection that contain all SCEP clients, to as deployment target of a rule and policy.
I've try to create a query-based collection, with the following query language :
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where SMS_G_System_INSTALLED_SOFTWARE.ProductName = "System Center 2012 Endpoint Protection"
But after the collection is created, none of the emerging client that have SCEP installed.
Earlier I have apply this query on the SCCM 2012 SP1 environtment, and it is work. But now I have migrate to the SCCM 2012 R2, and this query is seems not function on R2 version.
Is there difference query language between SCCM 2012 SP1 and R2?
Thanks.
Regards, Bar Waelah

Hi,
I saw System Center 2012 Endpoint Protection is under Installed Applications (64) node when I open Resource Explorer on a computer that installed System Center 2012 Endpoint Protection.
So I edited your query, then these computers appeared on the collection.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceID
= SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like "System Center 2012 Endpoint Protection"
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.

SCCM 2012 SP1 CU4 ccmsetup runs with SMS Agent Host on the "Service" mmc after upgrading the client to CU4.

Dear Brothers,
I have an issue with two (2) of my Site Servers, I have below scenarioa and explained issue details:
Scenario:
1. Server1: Windows 2012 Server, CAS, SCCM 2012 Hierarchy Roles: Management Point, DP, SUP, Component Server.
2. Server2: Windows 2008 R2 Server, Secondary Site Role, SCCM 2012 Hierarchy Roles: Management Point, DP, Component Server.
Issue:
After updating the SCCM 2012 Client to CU4 on the actual Site Server, the "ccmsetup" appears also with "SMS Agent Host"
at the Service MMC. Which I believed this is very unusual behavior.
The Client however it seems properly installed and working please see below details:
Questions: I believed the Client installations are still running on the background, even though the Client tends to look working on the Control Panel.
1. How can I resolved this issue?
2. Should I need to perform a total Client uninstallation, even depth till removing entries in the Registry levels?
3. Or this is a normal behavior for the scenario?
Advance thanks for your future replies, my brothers in technology.

Dear Brother,
2 Weeks since I installed the CU4, it seems a little bit to long isn't it? for both the ccmsetup and the SMS Host Agent Services to exist, for the errors on the ccmsetup.log there are some errors after uninstallation since I am trying to removed
the issue .
CCMsetup.log
==========[ ccmsetup started in process 5376 ]========== 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on platform X64 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\cache\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Launch from folder C:\Windows\ccmsetup\ 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup version: 5.0.7804.1500 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on OS (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 3 7/1/2014 7:14:45 PM 4104 (0x1008)
Ccmsetup command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
SslState value: 224 7/1/2014 7:14:45 PM 4104 (0x1008)
Detected client version 5.00.7804.1500 from WMI. 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Another instance of ccmsetup is already running. 7/1/2014 7:14:45 PM 4104 (0x1008)
Task 'Configuration Manager Client Upgrade Task' does not exist 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup is exiting with return code 3 7/1/2014 7:14:45 PM 4104 (0x1008)
MSI: Action 19:15:20: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. 7/1/2014 7:15:20 PM 5628
(0x15FC)
MSI: Action 19:15:20: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:20: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-
1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.
2. Checks the desktop client version and gets the installation direcotry.
3. Stops remote control and other desktop components.
4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.
5. Saves information needed for migration and uninstalls the desktop components followed by clean up. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:31: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Action 19:15:31: InstallFiles. Copying new files 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Internal Error 2902. ixfAssemblyCopy 7/1/2014 7:15:32 PM 5628 (0x15FC)
MSI: Action 19:15:32: Rollback. Rolling back action: 7/1/2014 7:15:32 PM 5628 (0x15FC)
File C:\Windows\ccmsetup\configmgr2012ac-sp1-kb2882125-x64.msp installation failed. Error text: ExitCode: 1603
Action: InstallFiles.
ErrorMessages:
Internal Error 2902. ixfAssemblyCopy
7/1/2014 7:15:33 PM 5628 (0x15FC)
A Fallback Status Point has not been specified. Message with STATEID='301' will not be sent. 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\client.msi 7/1/2014 7:15:33 PM 5628 (0x15FC)
CcmSetup failed with error code 0x80070643 7/1/2014 7:15:33 PM 5628 (0x15FC)
Regards,

SCCM 2012 R2 CU4, how can we make sure clients without any CU upgrade will continue to communicate?

Hi,
We're about to upgrade the SCCM 2012 R2 server from CU1 to CU4. However no clients were ever upgraded (don't even have CU1). Is there any way(matrix or other) we can assure ourselves clients will keep on communicating (f.e. for SCCM R2 CU4, clients need at
least to be at CU1)?
Please advise.
J.
Jan Hoedt

Go through each one and see for yourself. Note that they are cumulative so you only need to deploy the latest. CU4 contains all the others. The issues that are fixed are listed.
CU4
https://support.microsoft.com/en-us/kb/3026739?wa=wsignin1.0
CU3
https://support.microsoft.com/en-us/kb/2994331
CU2
https://support.microsoft.com/en-us/kb/2970177
CU1
https://support.microsoft.com/en-us/kb/2938441
It's always better to use the latest version where possible.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

What Will I Miss The Most Not Joining Domain

Friend of my has a company where some of the machines are not joined to the domain and users just login with local account. I asked why and they provided two reasons:(a) Some take their machines home so it's easier to just have one login. I pointed out, if they are not connected to VPN, could they not just login via: .\username instead or {domain name}\username ? Why is that so hard?(b) These machines are Windows 8 standard. How hard to upgrade to Win 8 Pro?It seems to me that the biggest drawback of not being joined to the domain is lack of access to network resources (folders) that have user/group security? But then I see you can view the network and login to network shares without using a machine joined to the domain.What are the other big advantages of having the workstation domain joined? Ability to enforce group machine policies?...
This topic first appeared in the Spiceworks Community

Friend of my has a company where some of the machines are not joined to the domain and users just login with local account. I asked why and they provided two reasons:(a) Some take their machines home so it's easier to just have one login. I pointed out, if they are not connected to VPN, could they not just login via: .\username instead or {domain name}\username ? Why is that so hard?(b) These machines are Windows 8 standard. How hard to upgrade to Win 8 Pro?It seems to me that the biggest drawback of not being joined to the domain is lack of access to network resources (folders) that have user/group security? But then I see you can view the network and login to network shares without using a machine joined to the domain.What are the other big advantages of having the workstation domain joined? Ability to enforce group machine policies?...
This topic first appeared in the Spiceworks Community

Machines not Joining Domain SCCM 2012 R2 CU4

Similar Messages

Maybe you are looking for