Find version SCCM Client
Hi,
I'd like to query an SCCM client via Powershell in order to know the client version.
When I do that via
Invoke-Command -ComputerName $computername -ScriptBlock {Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{8864FB91-94EE-4F16-A144-0D82A232049D}" -Name "DisplayVersion"}
It returns no SP (.1000) whereas CU4 is 5.00.7958.1501.
When I look at the client it does have CU4 and there is no reboot pending (rebooted the machine, not sure if it is needed for CU4?).
Please advise.
J.
Jan Hoedt
Get-WmiObject -NameSpace Root\CCM -Class Sms_Client | Select-Object ClientVersion
Torsten Meringer | http://www.mssccmfaq.de
Similar Messages
-
Collection query for specific SCCM client version - Parameters?
Good morning,
I need to upgrade my older clients as I recently upgraded SCCM to SP2. I can't seem to find the parameters in query builder to populate a collection with a specific SCCM client version. Can anyone help me out or point me in the right direction? I can't find anything using "The Google". You'd think lots of people would want this that there'd be a default query in SCCM already. Thanks.Here is a query of all clients running sp1 version:
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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version = "4.0.6221.1000"
JonL -
Problems with SCCM client instalaltion after upgrade to R2 version
Hi,
Few days ago, I have upgraded SCCM 2012 Sp1+CU3 to SCCM 2012 R2. I see now manyy issies in component manager with SMS_EXECUTIVE and SMS_MP_CONTROL_MANAGER. Reaon of this is automatically process of installation SCCM client in latest version. This same
issue apppear when I trying install SCCM manually. In both cases I have got in ccmsetup.log this:
CcmCreateEmbeddedClientState. Creates the client state file, which is needed for write filter handing.
CcmCreateEmbeddedClientStateRollback. Rolls back the action of creating the client state file.
RegisterExtensionInfo. Registering extension servers
WriteRegistryValues. Writing system registry values
Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls. Verify that you have sufficient access to that key, or contact your support personnel.
Rollback. Rolling back action:
Computer where I want install SCCM client, my adm account, Primary site server or NT SERVICE\TrustedInstaller has full right to this registry key but log file record is always this same.
AV and Firewall turned off.
What next?Hi Torsten,
I have checked client.msi.log and there is this same:
Note: 1: 1401 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls 3: 5
Product: Configuration Manager Client -- Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls. System error . Verify that you have sufficient access to that key, or
contact your support personnel.
Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls. System error . Verify that you have sufficient access to that key, or contact your support personnel.
User policy value 'DisableRollback' is 0
Machine policy value 'DisableRollback' is 0
InstallFinalize. Return value 3. -
Hi All,
What is best practice for automatic installing of SCCM 2012 client Patches
(using Patch switch) during installation of SCCM 2012 clients? The challenge is that now there are two versions of clients and updates (x86 and x64).
I need information for:
OSD
Client Push Installation
Thank you in advance.
Regards,Not everything that can be or is supported or not supported is documented (or ever can be):
http://technet.microsoft.com/en-us/magazine/jj643252.aspx
Your expectation here needs to be adjusted. No one recommended contacting support. William just mentioned that *if* you have an issue and needed to contact support, they may decline to help you because you've done something explicitly unsupported.
For clientpatch, here's the specific documentation noting it as unsupported:
http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx
Additionally, I've also been in contact with the sustained engineering folks responsible for the CUs and they've reinforced the statement.
What can happen? Who knows? Microsoft does not test against unsupported configurations and features -- that's the definition of unsupported. It's not tested so no one really knows. They did find a couple of explicit issues (outlined in that post above) so
know that at least those exist and probably more since it is, as mentioned, abandoned code.
Why does it matter what can happen though? If the folks who write and support the code tell you shouldn't do it, you are simply asking for problems by doing it. Ultimately, you're asking a question that has no defined answer (except "bad"/unsupported things)
that really doesn't matter if you follow the explicit guidance. If you don't, as William points out, that's a risk for you take and an answer for you to discover.
Jason | http://blog.configmgrftw.com -
Hello,
I am using SCCM 2012 R2 with CU3 and I identified an issue for some SCCM clients installed on 2012/2012R2 servers.
The client keeps being resinstalled everyh 5/6 hours.
I believe it's because of the ccm evaluation failing.
I found could find the following infos :
- The task sequence "Configuration Manager Maintenance" fails with the result "The last run of the task was terminated by the user. (0x41306)"
- Error messages in the Winodws\CCM\Logs\CcmEval.log
Fail to get integer from registry CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Fail to get MPFailCount from registry, restart counting from 0 CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Client is set to use HTTPS when available. The current state is 448. CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Client is set to use HTTPS when available. The current state is 448. CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:58240AB1-F3B5-4FEA-ADDD-0C40D0F857D6";
DateTime = "20150125091322.843000+000";
HostName = "host.contoso.com";
HRESULT = "0x00000000";
ProcessID = 40384;
StatusCode = 0;
ThreadID = 29568;
CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Client's current MP is http://host.contoso.com CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
MP check succeeded CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Send previous report if needed. CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Fail to get time from registry CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Can't determine whether previous sent succeed, assume sent failed CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Fail to get string from registry CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
There is no previous report sent CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Fail to get time from registry CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Can't determine whether previous sent succeed, assume sent failed CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Previous send is not complete, need to send report this time. CcmEval 1/25/2015 4:13:22 AM 29568 (0x7380)
Begin to send client health status report CcmEval 1/25/2015 4:13:23 AM 29568 (0x7380)
Successfully sent client health status as a state message. CcmEval 1/25/2015 4:13:23 AM 29568 (0x7380)
==========[ ccmeval finished normally in process 40384 ]========================== CcmEval 1/25/2015 4:13:24 AM 29568 (0x7380)
- I don't see any error messages in the ccmsetup-ccmeval.log
- I see new events in the CLient.msi.log every 5/6 hours when the install restarts automatically.
I also identified the MSIInstaller event in the event viewer.
I used the client Push to install the client so I first deploy the version 5.00.7958.1000 then install the update CU3.
I already tried to uninstall/reinstall the client but it's still the same.
Please, let me know if you already experienced the same issue and found a solution.
Thank you.couple of blogs on the same issue ...worth taking look at them
https://social.technet.microsoft.com/Forums/en-US/b10db3de-38c0-44b4-a4a2-11c9d5999083/client-is-uninstalling-itself-every-5-hours?forum=configmanagerdeployment
http://www.systemcentercentral.com/sccm-2012-r2-client-agent-uninstalling-and-installing-itself-every-5-hours/
https://kickthatcomputer.wordpress.com/2015/01/13/configmgr-client-constantly-reinstalling-every-5-hours/#more-1772
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr -
SCCM client not registering on some machines
Hello,
I am running across a strange problem that is only affecting some machines. We are imaging via OSD task sequence, 2012 R2 and some machines do not register properly with SCCM. When I say not registering, I mean it doesn't get its Site code and
missing most of its actions. Most machines that we image work fine, but the odd one doesn't register using the same task sequence that we use on other PC's. When I watch the task sequence steps go through I noticed that right after the installing SCCM
client step it boots right into windows. Basically skipping the steps we have set afterwards, the next step is to install some software (adobe reader, SCEP, and a few others).
I also noticed it seems to happen more often with certain model machines. I have an HP Z420 and an HP Folio 9470m. These consistently fail to register everytime I image.
I've tried quite a few fixes I found online, but nothing has worked as of yet. The most recent fix I tried was to delete the hardware inventory and then rebuild it. That did not work. Entering SMSMP= in the Setup Windows and Config manager step also did
not work. I also tried entering in our DNS server into the registry under the CCM directory. It appears something is happening during the client install (or not happening). But why only certain machines? Most work fine.
Our fix is to simply re-install the client after imaging, this solution has been working for us but I want to find a more permanent solution.
Any ideas?Jason,
We have this line in the Setup Config Manager,
PATCH=C:\_SMSTaskSequence\OSD\PNS00002\Updates\configmgr2012ac-r2-kb2970177-x64.msp
Keep in mind, that this same task sequence works fine with most other machines. It almost appears to be model specific. Certain models definitely have more issues registering than others.
I'm still fairly new to SCCM, so if you need more from the logs let me know.
==========[ ccmsetup started in process 2176 ]========== ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Running on platform X64 ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Launch from folder C:\_SMSTaskSequence\OSD\PNS00002\ ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
CcmSetup version: 5.0.7958.1000 ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Ccmsetup command line: "C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PNS00002 /config:MobileClient.TCF /status:524 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Command line: "C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PNS00002 /config:MobileClient.TCF /status:524 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Copying config file from C:\_SMSTaskSequence\OSD\PNS00002\MobileClient.TCF to folder C:\WINDOWS\ccmsetup\. Return result: 0x0 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
SslState value: 224 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPPORT: 80 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSPORT: 443 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSSTATE: 224 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSCERTNAME: ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
FSP: ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMFIRSTCERT: 1 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Config file: C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Retry time: 10 minute(s) ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MSI log file: C:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MSI properties: INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Source List: ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
C:\_SMSTaskSequence\OSD\PNS00002 ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MPs: ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
None ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
No version of the client is currently detected. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Updated security on object C:\WINDOWS\ccmsetup\. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Downloading file C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Downloading C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 16% complete (262144 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 32% complete (524288 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 48% complete (786432 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 64% complete (1048576 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 81% complete (1310720 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 97% complete (1572864 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 100% complete (1614520 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Download complete. ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Running as user "SYSTEM" ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Detected 118178 MB free disk space on system drive. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Checking Write Filter Status. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Unexpected row count (0) retrieved from AD. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Failed to get site version from AD with error 0x80004005 ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
SiteCode: PNS ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
SiteVersion: ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
An MP does not exist on this machine. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Client (5.00.7958.1000) is installed and is the same or lower version. Initiating repair. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Repairing version 5.00.7958.1000 of the client with product code {8864FB91-94EE-4F16-A144-0D82A232049D} ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
No features were excluded and will be excluded. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:19:50 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Running installation package
Package: C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log: C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties: REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:19:50 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Next retry in 1 minute(s)... ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:20:50 PM 2452 (0x0994)
Running installation package
Package: C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log: C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties: REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:20:50 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:20:50 PM 2452 (0x0994)
Next retry in 1 minute(s)... ccmsetup 7/21/2014 12:20:51 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Running installation package
Package: C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log: C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties: REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:21:51 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
A Fallback Status Point has not been specified. Message with STATEID='313' will not be sent. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
InstallFromManifest failed 0x80070663 ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994) -
Locked SCCM Client Package waiting for prestaged content, Cant use Client Push
Hi there,
I am having an issue with client push. When initiated the client is unable to find the client install package on the DP. The CCMSETUP log file on the client reads "MP xxxxx.xxx.com didnt return DP locations for client package with the expected
version". This could be caused by a boundry issue but the boundry information is set up correctly, and published into AD.
The SCCM Client on the site server is not getting replicated properly to the DP's that we have setup and I think that this is causing the issue. The reason why its not gettiog to the DP is due to this error: "Distribution Manager is waiting for Package SG100001
content to be prestaged on the distribution point" when we look at the content status of the SCCM client Package.
We are unable to change the prestaged distribution point settings "automatic" as the package is the locked as its the SCCM client installation package and its waiting for us to prestage it on the DP. I have tried prestaging it, but it didnt
work
Any ideas as I have been stuck for two days on this now...
Thanks in advanced.
GeorgeTorsten you were right, The solution was as follows for anyone else having the same issue.
As soon as you create a DP it appears that the client installation package automatically tries to distribute to the DP. If you created the DP as "Enabled for Prestage" while doing the setup then the SCCM client package will just wait for you to
copy it manually. To reslove this I had to remove the "Enabled for Prestage Content" from the DP then go into the SCCM client Package, content location tab, select the DP and redistribute the package to the DP.
Checking the Distribution Manager and PkgXferMgr.log assisted me in monitoring the content transfer to the new location.
Thanks for your assistance.
George
George, I too concur that this fixed the issue.
I had the same problem with my SCCM 2012 R2 CU4, where i updated the distribution point for the Configuration Manager Client Package. Thanks a million! -
PKI SCCM Client Certificate Template not viewable by Windows 7 and Server 2008 workgroup machines.
Hello everyone,
I’m having issues with workgroup computers, not domain systems when I request a certificate.
It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. In 2003 server I can request a certificate manually with certutil and it see the certificate template. I copy over the exact command
on windows 7 and it can’t see the certificate template.
I have the following configuration:
CA Enterprise
I have created the SCCM Client Certificate
I have created the SCCM Web Server Certificate
I have created the SCCM Distribution Point Certificate
GPO is configured
SCCM 2012 R2 CU2 configured to do HTTP and HTTPS
Installed SCCM Client Certificate
Installed SCCM Web Server Certificate
Installed Distribution Point Certificate
Deployed to a domain computer good on PKI
Workgroup Computers:
I’m having issues with deploying certificates
Windows 7 –
(ERROR) not successful
Windows Server 2008 R2 –
(ERROR) not successful
Windows Server 2003 - successful
Windows XP – successful
How I’m getting the certs for the clients is by utilizing the following scripts from this URL.
http://www.ithierarchy.com/ITH/node/48
I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following:
Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req
Error --- Template not found.
SCCMClientCertificate (this is my template)Just to give an update on what’s happening with this. I found out this format is unsupported by MS with Windows Vista and newer OS’s.
Instead you must utilize two other additional roles on the CA to have this work. The caviate is, I’m down to the testing and it’s not working as in the document. I have MS Support
working with me to resolve this issue since it was written by MSFT.
http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
and use this doc for similar workgroup computers for rolling out certs. This was written for RT devices, however, it should work once I get to that point.
http://blogs.technet.com/b/pki/archive/2012/12/11/certificate-for-winrt-devices-and-non-domain-member-devices.aspx -
Need help with a simple Rename/Join Domain/Install SCCM Client Task Sequence
Good morning everyone,
I need to create a very simple task sequence that will run an .exe that we have created that renames the computer based on a prefix-serialnumber...then restarts, adds it to our domain, restarts, and then installs the SCCM client.
1) run rename program
2) join to domain
3) install sccm client
Can someone help me with the steps that will be required for this?
Thank you very much!
**note, these will not be formatted/have an OS installation ran on it with this task sequence. The situation is that we are receiving 400+ custom configured laptops, and we're going to have to rename/join/install sccm on each...trying to simplify
this
any recommendations are greatly appreciated!Narcoticoo : Which boot image am i supposed to be using to insure that it boots into Standard Windows, NOT WinPE? I have a standard x86 package / boot image i've been using. If it boots up with this, it goes into WinPE (correct me if I'm wrong,
for this seems to be what happens each time it boots off the boot image...it does not go into windows standard/full)
When I go into properties of the one i'm using, and take the check off of "Use a boot image", where it will not boot to WinPE, it will not even show up in my list of available task sequences for
1) when I PXE boot to try the task sequence, or
2) when I try to make stand-alone media for this task sequence as you have suggested
When I run the standalone media, the only log files I find are the following with errors:
PackageID = 'MPS0014E' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
BaseVar = '', ContinueOnError='' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
ProgramName = 'MPHS - Rename Computer' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
SwdAction = '0002' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
IsSMSV4PlusClient() == true, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,332)
InstallSoftware 12/8/2014 12:28:36 PM
2344 (0x0928)
Configuration Manager client is not installed
InstallSoftware 12/8/2014 12:28:36 PM
2344 (0x0928)
Process completed with exit code 2147500037
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Failed to run the action: Install Package.
Unspecified error (Error: 80004005; Source: Windows)
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Failed to run the action: Install Package. Execution has been aborted
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Do not send status message in full media case
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Failed to run the last action: Install Package. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Do not send status message in full media case
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,866)
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)
Task Sequence Engine failed! Code: enExecutionFail
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)
Task sequence execution failed with error code 80004005
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608) -
ODBC Error: Could't find Oracle Instant Client in present directory.
I am getting the following error when I try to run odbc_install.exe with the Oracle 10g Instant Client Lite version 2:
Could't find Oracle Instant Client in present directory.
The 10g Instant Client Lite version (including the missing MFC71.DLL and MSVCR71.DLL files) is in the directory. What am I missing here??Can you detail your configuration? What files are in the directories? Environment variables?
-
SCCM Client Push Installation Wizard does not install the client. CCMSetup folder - not created
Hello,
I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always
the same - no SCCM client is installed on any computer.
The computers are running 32-bit Windows XP SP2.
The Windows firewall is disabled.
The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method
is not enabled.
The domain is AD WIndows 2000.
The SCCM server is running Windows 2003 R2 SP2 64bit Standard.
The AD schema has been extended.
MP, and SLP are installed and published. (MP is published in DNS as well.)
FSP is installed.
MP, SLP and FSP are running on the same server.
SQL 2005 server is running locally.
System management container is created and all rights and permissions delegated.
With the Push installation account I can access C$ share on the client computer from the SCCM server.
RPC, Remote registry, WMI services are running on the client machines.
All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.
All computers are in the same IP subnet which is listed in the boundaries.
Yet, the client is not being installed.
No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot
what the is the issue. I do not see anything helpful in the ccm.log on the server.
I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the
SCCM server / console.
What else I should check / try? I really want to push agents via the wizard.
Thank you,
PeterHi Wally,
I have changed 2 things:
1. Enabed automatic push installation (so I am not usign the wizard any more)
2. Changed the IP subnet to IP ranges in the site boundairies.
After runnignt the discovery, I was able to see some activities in the ccm.log. A ccmsetup folder is now created but the agent is still not instaleld. Here is the ccmsetup.log
==================================
<![LOG[==========[ ccmsetup started in process 3140 ]==========]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:8853">
<![LOG[Version: 4.0.5931.0000]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:1913">
<![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3937">
<![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3946">
<![LOG[CCMHTTPPORT: 80]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7851">
<![LOG[CCMHTTPSPORT: 443]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7866">
<![LOG[CCMHTTPSSTATE: 0]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7884">
<![LOG[CCMHTTPSCERTNAME: ]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7912">
<![LOG[FSP: HFXDBSSOM.CORP.EASTLINK.CA]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7927">
<![LOG[CCMFIRSTCERT: 0]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7969">
<![LOG[Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4341">
<![LOG[Retry time: 10 minute(s)]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4342">
<![LOG[MSI log file: ]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4343">
<![LOG[MSI properties: INSTALL="ALL" SMSSITECODE="PHX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="HFXDBSSOM.CORP.EASTLINK.CA" CCMFIRSTCERT="0"]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4344">
<![LOG[Source List:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4352">
<![LOG[ \\HFXDBSSOM.corp.eastlink.ca\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4359">
<![LOG[ \\HFXDBSSOM\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4368">
<![LOG[MPs:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4371">
<![LOG[ HFXDBSSOM.corp.eastlink.ca]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4386">
<![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="0" thread="3108" file="ccmsetup.cpp:8692">
<![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:9169">
<![LOG[State message with TopicType 800 and TopicId {A450B407-619B-4777-B77E-C3352753B58A} has been sent to the FSP]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="3108" file="fsputillib.cpp:730">
<![LOG[Running as user "SYSTEM"]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:2534">
<![LOG[Detected 24292 MB free disk space on system drive.]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:465">
<![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:511">
<![LOG[Client OS is not Windows XP Embedded]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:548">
<![LOG[Successfully ran BITS check.]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:6948">
<![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="3" thread="2600" file="ccmsetup.cpp:5813">
<![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="09:45:08.760+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:9169">
<![LOG[State message with TopicType 800 and TopicId {3BFABF82-FB74-43FB-8A4A-6DFDEAEAC25C} has been sent to the FSP]LOG]!><time="09:45:08.776+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="2600" file="fsputillib.cpp:730">
==============================================================
There are two red errors I am concerned about:
"Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)
and
"Failed to download 'WindwosXP-KB923845-x86-ENU.exe' from http://HFXDBSSOM.corp.eastlink.ca/CCM_Client/i386/BITS25 with error code 0x80004005).
What should I do to resolve these errors?
Thanks,
Peter -
Trying to deploy SCCM Client upgrade...
A few days ago I upgraded our SCCM 2007 R2 Site Server with SP2. I did this in preparation for Windows 7 support and deployment. Anyhow, I decided to release the client upgrade via software distribution using the same package that I include with my image deployment (data source is \\server\sms_001\client )
Yesterday, I created an advertisement to distribute the SCCM client upgrade to my entire network but today System Center Console is reporting that out of 1148, 996 have not yet started, 0 succeeded, and 149 have failed. We're a school so most of our computers are off. The issue is that of the computers that are on 149 have failed with 0 reporting a success....or so they say.
I checked a few of my clients and the ccmsetup.log indicates that installation has in fact succeeded. However, what the "status of a specific advertisement" report is telling me is that the client failed with the "last status message name" column indicating "Program Failed (unexpected restart)". It shows the same thing for all clients that have reported a failure.
The software package program function is configured to run the following and I'm not using any client options: "CCMSETUP.EXE /noservice SMSSITECODE=AUTO"
Any ideas why the client appears to have been upgraded but reporting a failure?
Below is the execmgr.log:
Policy arrived for parent package 00100006 program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010949.649000+000";
MachineName = "ADMIN-OFF-TSEC";
ProcessID = 1976;
SiteCode = "001";
ThreadID = 3784;
execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Requesting content from CAS for package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Successfully created a content request handle {36479D3C-24C9-4844-BED1-2AB2B0BDD0F1} for the package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Program Advanced Client Silent Upgrade change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from NotExist to AdvancedDownload execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Mandatory execution requested for program Advanced Client Silent Upgrade and advertisement 00120025 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Creating mandatory request for advert 00120025, program Advanced Client Silent Upgrade, package 00100006 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010950.555000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
PackageVersion = "4";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1348;
execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Successfully raised SoftDistWaitingContentEvent event for program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingDependency to WaitingContent execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Content is available for program Advanced Client Silent Upgrade. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingContent to NotifyExecution execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Notify user mandatory program Advanced Client Silent Upgrade is about to run execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Manager timer has been fired. execmgr 12/22/2009 8:15:25 PM 1736 (0x06C8)
Executing program CCMSETUP.EXE /noservice SMSSITECODE=AUTO in Admin context execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from Running to NotifyExecution execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Checking content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System for use execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Executing program as a script execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Command line = "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO, Working Directory = C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Created Process for the passed command line execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\ccmsetup.exe\" /noservice SMSSITECODE=AUTO";
DateTime = "20091223011525.457000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 3500;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\";
execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raised Program Started Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Request in running or report status found for program Advanced Client Silent Upgrade package 00100006 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Service stopped while program Advanced Client Silent Upgrade is running execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
OpenProcess failed for process 1396, error 80070057 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Can not continue monitoring the program after service restart because the process exited. Assume failed execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Looking for MIF file to get program status execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramUnexpectedRebootEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223011911.783000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 3636;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1700;
execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raised Program Unexpected Reboot Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)This KB article covers the upgrade of the client via hotfixes:
http://support.microsoft.com/kb/2477182
An important thing to note is that the Program needs the following set:
After Running: Program Restarts Computer; this is needed to ensure that any status MIF files are collected after a restart of the client service (ccmexec.exe). No actual restart of the computer should occur.
This enables the SCCM client to detect that it re-started and to process the MIF files for status messages.
Installing the following updates one at a time normally is sucessful:
KB2761938
KB2516517
KB2815223
Other updates such as KB2276865 fail with the Unexpected Reboot Event error (possibly because the MIF is not written correctly) but it has been superseeded by KB2815223 wich is OK. -
WMI issues in VMware based Machine Windows 2008 R2 Servers affecting SCCM Clients
Dear
Brothers,<o:p></o:p>
I came to
an observation particularly in dealing with Windows 2008R2 Servers Vmware Based
Virtual Machines with SCCM Clients.<o:p></o:p>
Observation:<o:p></o:p>
1. Windows
2008R2 Virtual Machine with Vmware Tools installed (Also depending in the
entries of WMI, I supposed). <o:p></o:p>
When the SCCM Server Pushes the client on this Servers, I found out that the SCCM Client
seems to be installed perfectly but when I tried to perform a remote WMI Query
and the response is displayed below (The RPC Server is unavailable).<o:p></o:p>
Now, I know that this kind of issues is something to do about DCOM Configuration
for Remote Access right?
Well, sad to say the settings has been checked, trippled checked actually to make sure it is correct with the correct permissions required and proven correct up to the last settings.
I even compare the settings to those in some Windows Servers with Working WMI Remote Access.
=========
What I have observed is that when we make a VMware Systems and install the
VMware Tools (see picture below) first before installing the
SCCM Client and the issue regarding WMI Remote access issues happens (The RPC Server is unavailable).
I proved it by creating a new VM Machine, then conduct installation in this order
SCCM Client first and then the
VMware Tools by this way so far the WMI Remote access works perfectly.
Now the Question:
Since we have atleast 70 VM Servers in production with this issue, and I proven that the VMware Tools is something to do with this issue, somehow now I need to resolved this in a logical manner.
For some of us who can guide me to resolved the issue without uninstalling the VMware Tools and fixing the WMI settings and let the SCCM Client work.
Regards,We also have this issue. Nearly all of our terminal servers. I have to run a script to fix the issue and then reboot. It works, but only for a few days and then it starts all over again...
::to fix "not found" wmi error
::to fix .net calls to wmi repository
::to fix "initialization failure" error
net stop winmgmt
c:
cd c:\windows\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
mofcomp exwmi.mof
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
mofcomp exmgmt.mof
For the Update on this case Microsoft didn't find out direct connection of WMI issue to any contributors, however the clients
from Microsoft and and 3rd party application such as VMware is highly dependent on WMI for its total function.
Things that we have learned:
1. Your script is the primary solution as recommended as well by Microsoft, but this is to restore the WMI to its healthy State.
Is the error gone?
no definitely not.
Note: The WMIDiagnostic tool does not help to isolate at all, not even Microsoft is validating the credibility of its generated Logs from this tool.
2. You need to apply the Hotfixes recommended by Microsoft to eliminate the WMI repository to increase its capacity which contributes to the Service to stall. Deliver the Patches via SCCM or any means of your patch deployment.
3. Don't forget to reboot the Affected Server every Hotfix installation, this seems fix the issue. For 3 months now the usual system who got the WMI issue most of the time is no longer encountering the WMI errors. So far this is the solution, what causes
the issue? according to Microsoft the cause is the absence of the patches. -
SCCM client is connecting to the wrong SCCM site
We have a domain controller say TEST1, on which we have 4 SCCM servers. The SCCM’s have the following site codes
PR1, PR1, PR3 and PR4
We had a Group Policy for client installation created for site ‘PR1’, under ‘Group Policy Management' console in Active directory.
On all sites we have enabled ‘Client Push Installation’. All discovered same computers from TEST1 domain controller.
Now from any SCCM (say ‘PR2’) if we try to push client, the SCCM client machine points to the site code ‘PR1’ only.
Now we have removed the Group Policy and ran ‘gpupdate’.
In Active Directory we don’t see the site information of ‘PR1’ any more.
In the ‘PR1’ site we have removed the overlapping boundaries. We still see the problem.
We want to get the clients of PR2 site connect to the same, and install client successfully. Any help on this would be really
helpful.
Below is an extract of ‘LocationServices.log’ of an SCCM client of ‘PR2’ site
LSRefreshSiteCode: Group Policy Updated the assigned site code <PR1>, which is different than the existing assigned site code
<>. Will attempt re-assignment. LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Won't send client assignment fallback status point message because last assignment message was sent too recently.
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Processing GroupPolicy site assignment.
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Assigning to site 'PR1'
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
LSIsSiteCompatible : Verifying Site Compatibility for <PR1>
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Attempting to retrieve lookup MP(s) from AD
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
No lookup MP(s) from AD
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Attempting to retrieve lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Using default DNS suffix test1.test.com
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Attempting to retrieve default management points from DNS
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Failed to retrieve DNS service record using _mssms_mp_pr1._tcp. test1.test.com lookup. DNS returned error 9003
LocationServices
3/12/2014 11:31:13 PM
3920 (0x0F50)
No lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:13 PM
3920 (0x0F50)
Failed to resolve 'SMS_SLP' from WINS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
LSGetLookupMP: Failed to resolve lookup MP from WINS with 87D00215. Check if it is published
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
LSGetSiteVersionFromAD : Failed to retrieve version for the site 'PR1' (0x80004005)
LocationServices
3/12/2014 11:31:17 PM 3920 (0x0F50)
Attempting to retrieve lookup MP(s) from AD
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
No lookup MP(s) from AD
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Attempting to retrieve lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Using default DNS suffix test1.test.com
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Attempting to retrieve default management points from DNS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Failed to retrieve DNS service record using _mssms_mp_PR1._tcp. test1.test.com lookup. DNS returned error 9003
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
No lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Failed to resolve 'SMS_SLP' from WINS
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)
LSGetLookupMP: Failed to resolve lookup MP from WINS with 87D00215. Check if it is published
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)
LSIsSiteCompatible : Failed to get Site Version from all directories
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)
Won't send a client assignment fallback status point message because the last assignment error matches this one.
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)Hi,
The GPO writes the value of the site name the client should use and the values are not removed when you remove the GPO, so you need to clear the registry from those keys to be able to assign it PR2.
http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
SCCM Client Downloads Packages from DP on different subnet
Hi
When I deploy a package to PC, SCCM client finds two DPs (DP1 & DP2). I've checked log files...
DP1 is on the same subnet that client, but SCCM client downloads packages from DP2, but DP2 is different subnet.
With SCCM 2007, this was not by this way....SCCM client download packages from local DP (if was posible..)In CM2012, client content location is defined with two catagories like preferred distribution point and fallback distribution point. These gets listed by MP based on the Boundary configuration and the package deployment methods. If package deployed to look
only preferred distribution points, then that particular preferred (a boundary mapped )DP only listed by MP.
More information of these preferred vs fallback is explained in below article..
http://sccmguru.wordpress.com/2012/05/08/how-preferred-distribution-points-and-fallback-is-working-in-configuration-manager-2012/
Based on your question above, I believe the boundary configuration is not mapped to the DP and could be the case here. Thanks,
Thanks SRee
Maybe you are looking for
-
Macbook Pro 2.16 15" won't go past gray screen
My MBP 2.16 15" that was running on Snow Leopard stop loading past the gray screen. I was able to recover the data via connected to my imac. So I can see the orginal hard drive just fine. So my first guess was a bad hard drive so I bought a SSD and p
-
Converting word documents to pages
when receiving word documents with linked text boxes the conversion to pages does not let me see the second or subsequent text boxes; I can view them using "open with" but I can't edit and send back. There must be a solution for this; a lot of my wor
-
How to avoid client opening for maintainig char value for POreleasestrategy
Hello Experts I have configured Purchase Order release strategy in our development client. I have released all transport requests for PO release in our quality client. But after releasing transport requests , value in characteristics like PO value wa
-
Post Author: dufernandes CA Forum: .NET Hi there, My problem is the following: I'm using MS Visual Studio 2005 with the standard version of Cyrstal Reports. I wish to design a bar chart along with a line chart (that represents the goal of the data be
-
Hi all ! I was wondering if someone has a good example of implementing Webservices with the CFNetwork ? The main idea is to have a rails application on a laptop that could communicate with an iphone/ipod touch for exchanging data. Thanks !