Search the Community

I am trying to setup a test sccm server running the tech preview with a site code of TP1 in the same domain as my main lab sccm server with a site code of RYK. When I install the client on a windows 10 pc from the TP1 sccm console after a while it will be assigned to the RYK site. My boundaries for site RYK are setup as such: 10.0.0.2-10.0.0.99 (clients) 10.10.0.20-10.10.0.24 (servers a) 10.10.0.26-10.10.0.99 (servers b) so here i am excluding the IP of 10.10.0.25 which is the TP1 site server. My boundary group for my main RYK site is called production and it contains the three boundaries listed above. I do have another boundary which is my AD site but there are no site systems in it and its not a member of any boundary groups, My boundaries for site TP1 are setup as such: 10.0.0.200-10.0.0.210 (test clients) 10.10.0.25-10.10.0.25 (cm02 TP1 server) this site server also has a boundary which is my AD site the same as above and it also does not contain any members or is a member of any boundary groups VM-PC08 has an manual ip of 10.0.0.201 and is joined to the home.local domain, both site servers RYK (10.10.0.24) and TP1 (10.10.0.25) are members of the home.local domain as well. How can i run a production version of sccm along side a test tech preview version of sccm and have my clients assigned to the correct site. when I installed the client on vm-pc08 initially it was assigned to TP1 but after a while it moved to RYK. As you can see my boundaries and groups don't overlap so in theory that shouldn't be an issue but what am i missing? Client push is disabled on both sites. My clients get installed via a OSD TS on the RYK site and manually from the console in TP1

Hi Guys, I just finished installing 1 Primary and 4 Secondary Sites. I have all the Boundaries setup properly using Forest Search and IP Subnet Boundaries for corresponding Secondary Sites. When I look at my Devices I can see 750 devices which all assigned to Primary site instead of they assigned in to their own Site. My questions: 1- Is this normal? 2- When we deploy package or OSD those clients set to My Primary Site will they download the content from Primary Site or Their Own Site?? Capture 4 picture Shows the DLC Site Client Push Settings... Regards, Gokhan

Hey Guys / Niall - So I manage an environment of ~10,000 workstations and ~900 servers on a single domain. A few months ago, we acquired a new company which has their own SCCM environment on a different domain. Finally, I am wrapping up a build of SCCM on a 3rd domain. The plan is to migrate all clients from the two old domains onto the new one. I have a couple of questions about this procedure so wanted to post to get opinions... 1. Migrate Many Clients to New Site Prior to Domain Change The main question is that their current plan is to migrate the domain on workstations a department at a time over a six month period. While doing so, they want to use my script to migrate each of the workstations' SCCM client while changing the domain. The last thing i want is to have 3 separate and constantly changing environments to manage, so am trying to find the best way to potentially migrate the clients from both old domains to the new one before (like few months in some cases) the domains on the workstations are changed. There's currently a one-way trust between the new domain and both old ones and don't know if I can get them to make it more flexible. Basically, I'm curious what I would need to do in order to achieve the goal above. My experience tells me the below would be needed - at least in theory: Add scope of system's OUs / containers in old domain to discovery on new site Script executed per system to change the site of the client to the new site The SCCM Network Service account to have local admin rights on all workstations (per old domain) Specific DNS records modified / changed to point to the FQDN of the new primary instead of the old ones (per old domain) Is the above all that would be required, know of any helpful posts related to this, or any suggestions / thoughts? 2. Migration of Packages, Applications, etc with New Source Path I'll be moving a lot of packages and such over to the new environment, but am now using a new "master" share for the sources of all packages, applications, etc. It's simple to migrate an SCCM package from one site to a new one, but when doing so; it retains the same source path for it. Does anyone know of a PowerShell script or overlooked options which would allow me to change just the first part of the source path for migrated packages when moving to the new site? If capable of copying the source content during the migration, that would be ideal; but if not copying it would still be faster than changing each manually. I'm considering simply exporting certain packages, then importing them back in. Will have to play with that a bit more to see how it would work. Suggestions? All 3 sites run SCCM 2012 R2 SP1 CU4. We cannot go to current branch yet due to numerous legacy apps on workstations which don't play nice with .NET 4+. Most site servers (especially on the new environment) run Windows 2012 R2. Any suggestions or comments would be appreciated. Thanks!!

Hello sorry for my english i'm french . I have been trying for several days to install an SCCM push client, but remotely through a FortiGate. So the problem is that the clients seem to have settled into the machine: Capture task manager Capture of SCCM files present: Capture of the ccmsetup.log LOG File: And then I put the Configuration Manager capture where I don't see the PC as clients: Do you have any ideas how to solve the problem?

Hi Team, I have been facing an strange issue. After the machine built by OSD TS, client isn't visible as online in Console and I don't think client is getting policies applied. Validated Firewall ports (80,443,10123) and all are fine. Any clue or troubleshoot approach would be much appreciated. I have attached policyagent.log. Note: To test this tried to install a client on Site Server using clientpush, it installed and shows as online and all the configurations getting applied. PolicyAgent.log

Hi, We have this behavior when upgrading the Config Manager client and i'm just curious if someone recognizes it and dealt with it before. This is what happens; After a Client upgrade of the Config Manager client to 1910 some desktops fall into sleep mode, they shouldn't because their powersettings are set with Collection based power scheme. If you reboot the device everthing works again. With the upgrade to 1810 i noticed something similiar, client temporary unaware of settings, with surpressed reboots for workstations on the Deployment of Software Updates. These devices had pending reboots and rebooted directly after the upgrade of the client. It was not supressed at that time. The upgrade of the client is done via the build in Pre-production Client Deployment collection. I'm now thinking of another approach next time. Create a custom deployment of the CCM client with triggered communication between client and server. But you'd expect this as something default... Is there a way to prevent this?

I am in need of help here. We have recently discovered that all of our client are showing as inactive since 7/10/2020. The only thing we had back then was the certificate authority renewal of certificates for all computers. we have renew all certificates on all the computers and servers but no luck on sccm. I have updated the certificate inside the distribution point with the new certificate and still showing inactive on all clients/servers. I have tried switching between HTTP and HTTPS as well in the distribution point under administration > server and site roles and nothing. Rebooted the server also and no changes. all certificates as well on the mmc certificate console panel are updated as well.

A lot of my clients are stuck showing long since deleted deployments in Software Center. I've run all of the "client notification" options multiple times, and still the old deployed applications exist. I have also gone through the entire console and deleted all old revisions of any application. They are still there. Any suggestions??

Hello everyone, I am having a new issue on an existing SCCM implementation where the client does not install correctly. It looks like what most people have termed 'stuck in provisioning mode'. The version is correct in control panel but it shows "none" for valid certificate. This would obviously cause communication issues because we allow only SSL encryption. We do deploy our own certificate via Group Policy and I believe that is working correctly and installing om the clients. I have walked through the ccmexec logs on the client and see no real helpful information. It looks like WMI is working correctly. The true odd part is that if you try to open software center - before you get the failure message, it shows a rather old version of software center with the tabs across the top and not down the side like the newest version that we are currently deploying. This seems odd to me because its a new image, and I believe that the only version of the client on the deployment share is the newest version. It seems like after numerous reboots (gpupdates?)and many hours it will eventually correct itself , but nowhere near acceptable. Any thoughts are very appreciated. AJ

We started with Config Manager 1702. Since then we upgraded to 1706. The new client version is 5.00.8540.1007. We enabled Hierarchy Settings Properties of our site to Upgrade all clients using the production client within 4 days. One month later half of our computers are still showing "Client Version Reported from DDR" as 5.00.8498.1711 with Compliance Status of "Not Compliant." We are a Windows 7 and Windows 10 mixed environment. Can anyone shed some light as to what might be going on here and why this occurred? Thanks!

Hi, I am hoping someone here has had a similar issue or can at least point me in the right direction to get my clients installing completely with usable components. The environment: SCCM 2012 Current Branch 1606 (5.00.8412.1307) - installed on a single machine (small production environment) Client version on server (5.00.8412.1307) Client computers: Windows 10 - all machines were recently updated to Windows 10, some via a SCCM TS, others via a USB SCCM TS. In either case, the same image was used. The problem: Newly installed machines are not receiving a usable SCCM client. The CCM clients are reporting in to the MP, but if you attempt to run any action or component, or send any distribution to the machine - you receive a failure. Using Right Click Tools, I generate the "SCCM-error-RCT.jpg" message. If you run the action on the local client, I receive an "The selected cycle cannot start." popup. (SCCM-Client.png) First attempt to resolve is to repair the client - did not work. Reinstalling the client also did not work. Uninstalling, clearing the CCMsetup & SMS registry keys, rebooting and then reinstalling, did not work. Installing a lower client version (5.00.8325.1000) to force an update, did not work. Installs were down as push installs, as local EXE, as local MSI. All installs were with /forceinstall and predefined SMS site code and MP parameters. They were all accepted. In addition - performing the above actions caused a secondary problem: The CCM client is unable to complete its install. The base application installs, but components are not installed (Actions-tab.png & General-tab.png) Going through the logs (CCMSetup.log) I can see that the install is rolling back the installed components. My issue - I cannot see "why" its doing this. Is it rights based? - the client install account has the correct local admin access to the machines, and full access to the \Clients\ folder on the DP Does the system have the needed rights in AD? - yes - it has delegated control to system management and the schema was correctly extended Is the DNS correctly setup? - yes, Ip and names resolve to the correct MP Are Boundaries correct? - I am only using AD defined boundaries and yes, these are correct. Affected machines: 98% of all my machines. If anyone can give me some advice on where to look - I'd greatly appreciate it! Below is an excerpt from the last CCM client deployment to a test machine. Last trial was to install the older client (5.00.8325.1000) through Admin command prompt from a local source folder. ==========[ ccmsetup started in process 848 ]========== ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Launch from folder c:\Temp\Current Branch 2012 Client - no updates\ ccmsetup 21.09.2016 09.52.14 4208 (0x1070) CcmSetup version: 5.0.8325.1001 ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Running on 'Microsoft Windows 10 Enterprise' (10.0.10586). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Ccmsetup command line: ccmsetup.exe /forceinstall SMSSITECODE=SiteCode SMSCACHESIZE=10000 SMSMP=SiteServer ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Command line: ccmsetup.exe /forceinstall SMSSITECODE=SiteCode SMSCACHESIZE=10000 SMSMP=SiteServer ccmsetup 21.09.2016 09.52.14 4208 (0x1070) SslState value: 224 ccmsetup 21.09.2016 09.52.14 4208 (0x1070) No version of the client is currently detected. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Task 'Configuration Manager Client Retry Task' does not exist ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Updated security on object C:\Windows\ccmsetup\. ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Params to send '5.0.8325.1001 Deployment Error: 0x0, ' ccmsetup 21.09.2016 09.52.15 4208 (0x1070) A Fallback Status Point has not been specified and no client was installed. Message with STATEID='100' will not be sent. ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Failed to send status 100. Error (87D00215) ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Successfully deleted existing ccmsetup.exe ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Downloading file c:\Temp\Current Branch 2012 Client - no updates\ccmsetup.exe ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Downloading c:\Temp\Current Branch 2012 Client - no updates\ccmsetup.exe to C:\Windows\ccmsetup\ccmsetup.exe ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 14% complete (262144 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 29% complete (524288 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 43% complete (786432 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 58% complete (1048576 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 73% complete (1310720 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 87% complete (1572864 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 100% complete (1790136 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Download complete. ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Successfully created the ccmsetup service ccmsetup 21.09.2016 09.52.21 4208 (0x1070) ==========[ ccmsetup started in process 3376 ]========== ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Launch from folder C:\Windows\ccmsetup\ ccmsetup 21.09.2016 09.52.22 4888 (0x1318) CcmSetup version: 5.0.8325.1001 ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Successfully started the ccmsetup service ccmsetup 21.09.2016 09.52.22 4208 (0x1070) In ServiceMain ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to connect to policy namespace. Error 0x8004100e ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Deleted file C:\Windows\ccmsetup\ccmsetup.exe.download ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Task 'Configuration Manager Client Upgrade Task' does not exist ccmsetup 21.09.2016 09.52.22 4208 (0x1070) CcmSetup is exiting with return code 0 ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Running on 'Microsoft Windows 10 Enterprise' (10.0.10586). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"c:\Temp\Current Branch 2012 Client - no updates" "/forceinstall" "SMSSITECODE=SiteCode" "SMSCACHESIZE=10000" "SMSMP=SiteServer" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"c:\Temp\Current Branch 2012 Client - no updates" "/forceinstall" "SMSSITECODE=SiteCode" "SMSCACHESIZE=10000" "SMSMP=SiteServer" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) SslState value: 224 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPPORT: 80 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPSPORT: 443 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPSSTATE: 224 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPSCERTNAME: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Lookup MP: SiteServer ccmsetup 21.09.2016 09.52.22 1588 (0x0634) FSP: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMFIRSTCERT: 1 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Config file: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Retry time: 10 minute(s) ccmsetup 21.09.2016 09.52.22 1588 (0x0634) MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 21.09.2016 09.52.22 1588 (0x0634) MSI properties: SMSSITECODE="SiteCode" SMSCACHESIZE="10000" SMSMP="SiteServer" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="SiteServer" CCMFIRSTCERT="1" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Source List: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) c:\Temp\Current Branch 2012 Client - no updates ccmsetup 21.09.2016 09.52.22 1588 (0x0634) MPs: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) None ccmsetup 21.09.2016 09.52.22 1588 (0x0634) No version of the client is currently detected. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Task 'Configuration Manager Client Retry Task' does not exist ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Updated security on object C:\Windows\ccmsetup\. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Params to send '5.0.8325.1001 Deployment Error: 0x0, ' ccmsetup 21.09.2016 09.52.22 1588 (0x0634) A Fallback Status Point has not been specified and no client was installed. Message with STATEID='100' will not be sent. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to send status 100. Error (87D00215) ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Detected 105754 MB free disk space on system drive. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Client OS Version 6.2 Service Pack 0.0 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to get UWF_Filter instance. UWF Feature not installed. HRESULT=0x80041010 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Running as user "SYSTEM" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Checking Write Filter Status. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=SiteCode))' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) OperationalXml '<ClientOperationalSettings><Version>5.00.8412.1307</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202EF308201D7A00302010202105A31A88AAEF19AB84601CE2604217FB7300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3136303630313037333534355A180F32313136303530393037333534355A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100DBA6E68CE03ADCF273A8B20BA8729C367C14904FAEBCC6C8A7DFDDAF41EBE1D277F53625B776C88DFA0A95AA4CF1354978F2F3CF6F2F78753A91D156849C20548BEA51EBC9DD40CFE626F998AD64E5AD35057C5FF61FA0E52616E6EC3A2C4EF8BE3EC720189AE891AE8623B017CF714915E559A5B347E1B9006B962DFCDEB594B1D8E2C4339DF581243D68A901A0860A2016F515D60F8BD199188FB0699394C56D84F20275AADE1105AAA55E1093004A557CCD569FF22CA34F926DAD1B196603A263A1E1CED9BA8383CC8A99EB8A001956A78E8649371905269BD17E0DFD183319C1B2220E6E97C29EE228577A49CCD980EC09849A134123585469071B6BEF6D0203010001A3373035301D0603551D110416301482126B672D7363636D30312E6B672E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010046359CD1D5D90C32640FA5FEA36238A92F68DF6DA6A3ED3CCB2F9D250E7E2CA57ACBA317D3C5EB7EC7E4BD4410B60E5A7BFF1944B267FF08668580D2A7B9F524F74F27197856D939A6CF958A707DAECB2D31AD1F2F765F125B3C19DC92EF44D033F0AD490BBCF2A56734A6FD1926F8F2B5EF0F6D7DE1107505CD27CCF97EE02EA00D5C24106C2254F63269D654789E58ED61440347C67E77C08BE8AF1C298CA82558E81D6136A43B83402215C4AAC1B081E4C08025E6C266F9AD804932C94233E0B9DC19872A4EEC3E990349FEE01840AB46ADDA36EC19EFA07499F158E0CEAF4C370AEB8B2F8BF9DF1355BA920DB3DDB77DDEE1C0B486B1B92C6BFC44EE99A4</SiteSigningCert></SecurityConfiguration><RootSiteCode>SiteCode</RootSiteCode><CCM> <CommandLine>SMSSITECODE=SiteCode SMSCACHESIZE=10000 SMSMP=SiteServer</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="kg.local" /><Forest Value="kg.local" /></ClientOperationalSettings>' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) The MP name retrieved is 'SiteServer' with version '8412' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) MP 'SiteServer' is compatible ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Retrieved 1 MP records from AD for site 'SiteCode' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Retrived site version '5.00.8412.1307' from AD for site 'SiteCode' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) SiteCode: SiteCode ccmsetup 21.09.2016 09.52.23 1588 (0x0634) SiteVersion: 5.00.8412.1307 ccmsetup 21.09.2016 09.52.23 1588 (0x0634) No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Downloading file ccmsetup.cab ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Determining source location... ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Found accessible source: c:\Temp\Current Branch 2012 Client - no updates ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Found available source c:\Temp\Current Branch 2012 Client - no updates\ ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Downloading c:\Temp\Current Branch 2012 Client - no updates\ccmsetup.cab to C:\Windows\ccmsetup\ccmsetup.cab ccmsetup 21.09.2016 09.52.23 1588 (0x0634) File download 100% complete (9745 of 9745 bytes). ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Deleted file C:\Windows\ccmsetup\ccmsetup.cab ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Download complete. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Ccmsetup.cab manifest has been changed. Force to download client.msi and necessary pre-reqs again. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Successfully loaded ccmsetup manifest file. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Checking if manifest version '5.00.8325.1000' is newer than the ccmsetup version '5.0.8325.1001' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Running from temp downloaded folder or manifest is not newer than ccmsetup. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/vcredist_x86.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/vcredist_x64.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/vc50727_x86.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/vc50727_x64.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/WindowsUpdateAgent30-x86.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/WindowsUpdateAgent30-x64.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/msxml6.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/msxml6_x64.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/msrdcoob_x86.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/msrdcoob_amd64.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'pkgmgr.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'dism.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'wimgapi.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/MicrosoftPolicyPlatformSetup.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/WindowsFirewallConfigurationProvider.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/Silverlight.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/wic_x86_enu.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/wic_x64_enu.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/NDP452-KB2901907-x86-x64-AllOS-ENU.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'SCEPInstall.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/client.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/client.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Default CSP Type is 24 ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Discovering whether item 'i386/vcredist_x86.exe' exists. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Detected item 'i386/vcredist_x86.exe' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Discovering whether item 'x64/vcredist_x64.exe' exists. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Detected item 'x64/vcredist_x64.exe' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Discovering whether item 'x64/vc50727_x64.exe' exists. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Upgrade code '{A8D19029-8E5C-4E22-801

Is it possible to have a task sequence that skips the client install sccm 2012 R2? The client install package takes very long to deploy none of the hotfixes help the issue. I would just like to put it in the base image and skip that step. is there anyway to put in a step that exits winpe and continues on without that step?

Hello WN community! I have a bit of stumper I was hoping to get some feedback on! Let me know what you think... Scenario: We're running SCCM 2012 now for a little over a year, problem free. We've noticed however, that randomly (about 10 out of 1000 clients) the SCCM Client is reporting that the PKI certificate is none. What's stranger still, is that in the ClientIDManagerStartup.log, it doesn't appear to have an issue detecting and selecting the PKI certificate... Directly after the client selects the Cert, the ClientIDManagerStartup.log fills up with this repeating for ages I have ran a repair on the client, same result. I checked to see if perhaps the clients were stuck in provisioning mode, and they're not. Sort of at a loss of what to check next! Any help would be greatly appreciated. Thanks

Server details: Windows Server 2012 R2 - fully updated SCCM v 1606 Console version: 5.0.8412.1205 Site version: 5.0.8412.1000 Deploy workstation: Windows 10 Enterprise v1607 Hello, I have been trying to install the SCCM Client onto my workstations for the better part of two days now, attempting to deploy it via GPO. No matter what I try, I always get the same four errors in my Windows Logs/System. They come in a list of 4 entries, right in a row At this point I'm ready to pull my hair out. I'm really really unsure what my settings should really look like. I've googled and googled these errors, and I've tried every configuration change that I can see being recommended, and I don't get any changes at all. Right now, here's how I have it set up: Group Policy with Computer Configuration-Policies-Software Settings-Software installation package that has my client.msi for the source. I have tried the client.msi file from two different locations: \\sccm_server\SMS_mysite\Client\i386\client.msi and \\domain.local\NETLOGON\. For the first one (from my sccm_server), at first there were no read permissions to the Client folder (for Everyone, or Authenticated Users, or any other blanket group), so I granted them. I got that idea from this technet discussion. I tried NETLOGON because that's how I install LAPS (which works great). Figure I might as well give it a shot. I imported both templates into the group policy. Site Assignment has my site code, retry interval set to 5, retry duration set to 1. Client Deployment Settings, I've tried LOTS of things here. I've tried leaving it not configured, I've tried different variations on CCMSetup.exe with different switches like /logon, SMSSITECODE=mysitecode, MP=sccm_server, etc. I'm very unconfident on what should ACTUALLY be here. In SCCM, under Software Update-Based Client Installation Properties, I have check marked the box for 'Enable software update-based client installation'. I have extended my AD Schema as suggested in step 14 of this guide. In fact, I followed this guide for setting up my SCCM and deploying W10 via PXE. My setup should be nearly identitcal. When I try to check my workstation for C:\Windows\system32\CCM\ for logs, the CCM folder does not exist. I've searched all over C:\Windows for any CCM files or folders, and I find none. Please, help me here. Thank you.

HI I am having some issues install the sccm client on a LOT of devices, i don't know if its down to the current build (not Mine) or AD or something else. I have included the 2 log files. any help much appreciated. thanks guy, ccmsetup.log client.msi.log

Hey After OSD the clients are not registred: ClientIDManagerStartup.log <![LOG[RenewalTask: Client hasn't been registered yet. Reseting registration to pick up new changes.]LOG]!><time="20:48:08.684-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3696" file="regtask.cpp:2394"> <![LOG[GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE]LOG]!><time="20:48:12.135-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="ccmid.cpp:215"> <![LOG[Computed HardwareID=2:D6891E1AEEAFED56B15A2F0BB819353073C4F574 Win32_SystemEnclosure.SerialNumber=6331-1010-7429-5416-9992-6607-34 Win32_SystemEnclosure.SMBIOSAssetTag=6331-1010-7429-5416-9992-6607-34 Win32_BaseBoard.SerialNumber=6331-1010-7429-5416-9992-6607-34 Win32_BIOS.SerialNumber=6331-1010-7429-5416-9992-6607-34 Win32_NetworkAdapterConfiguration.MACAddress=00:15:5D:02:1B:24]LOG]!><time="20:48:12.181-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="ccmid.cpp:476"> <![LOG[[RegTask] - Sleeping for 60 seconds ...]LOG]!><time="20:48:12.197-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="regtask.cpp:1450"> <![LOG[Sleeping for 295 seconds before refreshing location services.]LOG]!><time="20:48:16.205-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="regtask.cpp:197"> <![LOG[GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE]LOG]!><time="20:53:12.346-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="ccmid.cpp:215"> <![LOG[Computed HardwareID=2:D6891E1AEEAFED56B15A2F0BB819353073C4F574 Win32_SystemEnclosure.SerialNumber=6331-1010-7429-5416-9992-6607-34 Win32_SystemEnclosure.SMBIOSAssetTag=6331-1010-7429-5416-9992-6607-34 Win32_BaseBoard.SerialNumber=6331-1010-7429-5416-9992-6607-34 Win32_BIOS.SerialNumber=6331-1010-7429-5416-9992-6607-34 Win32_NetworkAdapterConfiguration.MACAddress=00:15:5D:02:1B:24]LOG]!><time="20:53:12.393-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="ccmid.cpp:476"> <![LOG[[RegTask] - Sleeping for 60 seconds ...]LOG]!><time="20:53:12.408-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="regtask.cpp:1450"> <![LOG[[RegTask] - Client registration is pending. Sending confirmation request for GUID:9F64D1DE-D0B3-46E4-BB04-7FE84618FF0D ...]LOG]!><time="20:54:12.420-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="regtask.cpp:1763"> <![LOG[[RegTask] - Sleeping for 60 seconds ...]LOG]!><time="20:54:12.498-120" date="07-01-2017" component="ClientIDManagerStartup" context="" type="1" thread="3752" file="regtask.cpp:1450"> MP_RegistrationManager.log Processing Registration request from Client 'GUID:9F64D1DE-D0B3-46E4-BB04-7FE84618FF0D' MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) Begin validation of Certificate [Thumbprint 23F06AA75F586D1671A5F60AEC9D67BF29E6E631] issued to 'SMS' MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) Completed validation of Certificate [Thumbprint 23F06AA75F586D1671A5F60AEC9D67BF29E6E631] issued to 'SMS' MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) Verifying message signature for client 'GUID:9F64D1DE-D0B3-46E4-BB04-7FE84618FF0D' failed with 0x80090006. MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) CCMValidateAuthHeaders failed (0x80090006) to validate headers for client 'GUID:9F64D1DE-D0B3-46E4-BB04-7FE84618FF0D'. MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) MP Reg: Failed to verify RegistrationHint, 0x80090006, Registration Hint was not signed with the associated private key whose public key was registered with the SMSID (GUID:9F64D1DE-D0B3-46E4-BB04-7FE84618FF0D). MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 01-07-2017 20:47:56 9840 (0x2670) Processing Registration request from Client 'GUID:9F64D1DE-D0B3-46E4-BB04-7FE84618FF0D' MP_RegistrationManager 01-07-2017 20:47:58 9840 (0x2670) Begin validation of Certificate [Thumbprint 23F06AA75F586D1671A5F60AEC9D67BF29E6E631] issued to 'SMS' MP_RegistrationManager 01-07-2017 20:47:58 9840 (0x2670) Completed validation of Certificate [Thumbprint 23F06AA75F586D1671A5F60AEC9D67BF29E6E631] issued to 'SMS' MP_RegistrationManager 01-07-2017 20:47:58 9840 (0x2670) After a reboot of the client - its able to register. Why does it say "Issued to 'SMS'"? After the reboot it says "Issued to '%ComputerName%'" Let me know if ou need more logs. Thx in advance Mike

OK, I am encountering an issue when attempting to manually push the client. (Right click on the object and click "Install Client") This issue occurs on every system. I've verified that using my client installation account I am using is a member of the local administrators group on each system, and I've also verified that I can browse to the admin$ using explorer and connecting via the particular account. I also can connect to the registry, etc. Any suggestions or tips for resolving this issue? Thanks

Hey Guys / Niall - I'm in need of assistance with an issue, please. Our company is moving all systems over to a new domain over the next few months. One other change will be that the new domain will have a new SCCM environment. Since I'd rather not manage multiple environments, the plan is to migrate all workstations over to the new SCCM environment over about a week's time before migrating the domain on the systems. I've already built the new environment and all site servers on the new domain so was ready to start client migration. Changing a system to the new SCCM site and new domain works great - however - changing the client to the new SCCM site while retaining the old domain is not working. Overall, I have ~10,000 workstations on our current domain which are members of the existing SCCM site. I'm needing to migrate the clients to a new SCCM site which is on a new domain, but without changing the domain. I'm using a VBS file to change the client's site code to the new environment. Once I do, communication isn't correct, though. Client's log files show: ClientIDManagerStartup.log RegTask: Failed to refresh MP. Error: 0x8000ffff LocationServices.log: There is no AMP for site code "BCD". LsRefreshManagementPointEx failed with 0x8000ffff Failed to refresh security settings over AD with error 0x87d00215 Failed to refresh security settings over MP with error 0x8000ffff The New SCCM environment's console shows the hostname of the test system plus shows that it's a member of the old domain. It shows that "No" client is installed on the system both prior to and after the test to migrate it. Finally, below are the things I've configured in preparation prior to the test: A two-way trust exists between the old and new domains Boundary added in New SCCM environment (ip range) for test system which is assigned to a Boundary group /w assigned site code & MP SRV record added to old domain so that new site code resolves and points to FQDN of the new SCCM server's primary server Discovery methods configured to scan for systems in the old domain Both SCCM sites are HTTP (not HTTPS) Any suggestions? Thanks!!

We are currently installing the client onto Windows 10 machines, with some Server 2012 virtual machines, we have has success with some installing without issue, but on the machines that fail the logs show this: <![LOG[updated security on object C:\Windows\ccmsetup\.]LOG]!><time="09:32:00.721-660" date="03-02-2017" component="ccmsetup" context="" type="0" thread="8640" file="ccmsetup.cpp:9560"> <![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time="09:32:00.721-660" date="03-02-2017" component="ccmsetup" context="" type="2" thread="8640" file="state.cpp:171"> <![LOG[Params to send '5.0.8412.1004 Deployment Error: 0x0, ']LOG]!><time="09:32:00.721-660" date="03-02-2017" component="ccmsetup" context="" type="0" thread="8640" file="state.cpp:208"> <![LOG[sending Fallback Status Point message to 'PV-SCCM.PV.LOCAL', STATEID='100'.]LOG]!><time="09:32:00.721-660" date="03-02-2017" component="ccmsetup" context="" type="1" thread="8640" file="state.cpp:277"> <![LOG[<ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" Platform="2"/></ClientDeploymentMessage>]LOG]!><time="09:32:00.721-660" date="03-02-2017" component="ccmsetup" context="" type="1" thread="8640" file="statedetails.cpp:115"> <![LOG[state message with TopicType 800 and TopicId {4A7F6E22-4190-4538-9D98-CA3FED59C386} has been sent to the FSP]LOG]!><time="09:32:00.773-660" date="03-02-2017" component="FSPStateMessage" context="" type="1" thread="8640" file="fsputillib.cpp:783"> <![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time="09:32:00.842-660" date="03-02-2017" component="ccmsetup" context="" type="2" thread="8640" file="state.cpp:171"> <![LOG[Params to send '5.0.8412.1004 Deployment Error: 0x87d00264, ']LOG]!><time="09:32:00.842-660" date="03-02-2017" component="ccmsetup" context="" type="0" thread="8640" file="state.cpp:208"> <![LOG[sending Fallback Status Point message to 'PV-SCCM.PV.LOCAL', STATEID='328'.]LOG]!><time="09:32:00.842-660" date="03-02-2017" component="ccmsetup" context="" type="1" thread="8640" file="state.cpp:277"> <![LOG[<ClientDeploymentMessage ErrorCode="-2016411036"><Client Baseline="1" Platform="2"/></ClientDeploymentMessage>]LOG]!><time="09:32:00.842-660" date="03-02-2017" component="ccmsetup" context="" type="1" thread="8640" file="statedetails.cpp:115"> <![LOG[state message with TopicType 800 and TopicId {9C4BEB8F-63A2-4294-9E6F-CCAA7D99C942} has been sent to the FSP]LOG]!><time="09:32:00.882-660" date="03-02-2017" component="FSPStateMessage" context="" type="1" thread="8640" file="fsputillib.cpp:783"> <![LOG[Failed to connect to policy namespace. Error 0x8004100e]LOG]!><time="09:32:00.885-660" date="03-02-2017" component="ccmsetup" context="" type="3" thread="7468" file="localpolicy.cpp:367"> <![LOG[Failed to revoke client upgrade local policy. Error 0x8004100e]LOG]!><time="09:32:00.885-660" date="03-02-2017" component="ccmsetup" context="" type="3" thread="7468" file="localpolicy.cpp:394"> <![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="09:32:00.885-660" date="03-02-2017" component="ccmsetup" context="" type="1" thread="7468" file="ccmsetup.cpp:10927"> We have Symantec installed, which we have tried with it enabled, disabled, installed, uninstalled. Still the same error occurs. Any ideas please ?

Hello all! Long time visitor and browse often, haven't posted much (if at all) since registering. Thanks for a great site with lots of great discussions! Here is my situation: I am working on implementing an automated way to get all our laptops onto Bitlocker. We run a Dell shop here, so I have tasks that are automating the process (which work beautifully), but for some reason my hardware inventory schedule that I have assigned to my test collections don't appear to be running on the clients assigned to that collection. The laptop that I am doing testing with does everything it's supposed to fine far as the task sequencing goes when it gets into the collection, but thus far I've only been able to get it to move collections by manually kicking off a hardware inventory on it - for some reason the schedule doesn't seem to be running the hardware inventory like I would expect (IE a TPM status change). Could anyone give me some direction to start troubleshooting this? I'm including screens of my current Client Settings. Thanks much! Chad Edit: Sorry, just realized this probably would have been better placed in Troubleshooting, tools, and tips.

Hi there, Recently we upgraded from SCCM 2012 to 1606 Current Branch. Most clients are updated successfully. I have some of them that are Failed. As show here: However, when I look at the details, it's hard to understand why. The correct client version should be: 5.00.8412.1307 In this screenshot you can see some clients that have the Failed status. Client Version Reported From DDR has the correct version. Client Version Reported From FSP/MP has the wrong ersion. Many of the clients in that list both have wrong version and all of them have a different reason for the failure. Some of those are: 0x80072ee7,Unknown Error (-2147012889) - Failed to download file over WINHTTP at address. 0x80004005,Unspecified error - Invalid ccmsetup command line. 0x80200065,Unknown Error (-2145386395) - Failed to download files through BITS at address. 0x80004005,Unspecified error - Failed to find an available source. 0x00000000,Success - Cannot install prerequisite file 0x00000000,Success - Failed to find an available source. And so on... How to tackle these issues? What is your experience with client upgrades? I don't use Client Push... I've let CM deploy the new version automatically after the upgrade.

[RESOLVED, SEE POST BELOW] Hello, I am having an issue manually installing the SCCM Client on a handful of workstations. I have it pushing out via GPO, as well as installing during my PXE task sequence. The GPO worked for about 90% of the workstations in my environment, but it didn't for a handful, so I decided to just go do it manually on those workstations. It worked for me perfectly on the first one I tried. However, every one after that, it will not install. Please see my attached log files to see if you can help me out. I get the same errors at the bottom of each one. This is an excerpt from the bottom of the log: <![LOG[Failed to download client files by BITS. Error 0x800704dd]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="ccmsetup.cpp:6814"> <![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="2" thread="192" file="state.cpp:171"> <![LOG[Params to send '5.0.8412.1004 Deployment Error 0x800704dd. Path http://cbsCM01.cb.local/SMS_DP_SMSPKG$/CBS00002']LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="0" thread="192" file="state.cpp:208"> <![LOG[A Fallback Status Point has not been specified and no client was installed. Message with STATEID='309' will not be sent.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="state.cpp:222"> <![LOG[Failed to send status 309. Error (87D00215)]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="state.cpp:235"> <![LOG[Failed to download from DP 'http://cbsCM01.cb.local/SMS_DP_SMSPKG$/CBS00002', error 0x800704dd.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="2" thread="192" file="ccmsetup.cpp:1388"> <![LOG[Enumerated all 1 DP locations but none of them is good. Fallback to MP.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="2" thread="192" file="ccmsetup.cpp:11481"> <![LOG[Cost settings successfully set on '{E2CD69D0-4F42-4D47-BE77-0D7E1D24EF81}'.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="0" thread="192" file="ccmutillib.cpp:5781"> <![LOG[Using branch cache option.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:6639"> <![LOG[Adding file 'HTTP://cbsCM01:80/CCM_Client/i386/vcredist_x86.exe' to BITS job, saving as 'C:\Windows\ccmsetup\vcredist_x86.exe'.]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:6670"> <![LOG[Failed to download client files by BITS. Error 0x800704dd]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="ccmsetup.cpp:6814"> <![LOG[Failed to connect to policy namespace. Error 0x8004100e]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="localpolicy.cpp:367"> <![LOG[Failed to revoke client upgrade local policy. Error 0x8004100e]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="3" thread="192" file="localpolicy.cpp:394"> <![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:9772"> <![LOG[CcmSetup failed with error code 0x800704dd]LOG]!><time="09:26:52.580+480" date="12-14-2016" component="ccmsetup" context="" type="1" thread="192" file="ccmsetup.cpp:10927"> I worked with my network engineer, who tells me the workstations have full access to this server. I even tried putting a workstation on the same VLAN as the server, and still get the same error. Timeline is: 0. The GPO for Client deployment worked for ~90% of the workstations in my environment. 1. I try to manually install the client on my own workstation. It works without a problem. 2. I try to manually install the client on another workstation where it is missing. I get the error as shown in the log below. 3. I try 3 other workstations that don't have the client, they all give the same error as the 'FAILED' log 4. I move the workstation to the same VLAN as the SCCM server, and still get the same error Any assistance would be greatly appreciated. FAILED-ccmsetup.log SUCCESS-ccmsetup.log

Hi, We have around 500 machines deployed across multiple sites which we have noticed that around 60% of these are now showing inactive. As a comparison, I have found 2 machines, one active, one inactive, both from the same site in the same boundary, to try and figure out why they may be inactive. I Have attached multiple logs for both machines, does anyone have any insight into what may be causing this? We are currently running on 2012 R2 SP1. server 2012 R2 Any other suggestions on where to begin to look or if there are any other server/client logs to go through, would be great . (ACTIVE) CAS.log (ACTIVE) CcmExec.log (ACTIVE) ClientIDManagerStartup.log (ACTIVE) StatusAgent.log (INACTIVE) CAS.log (INACTIVE) CcmExec.log (INACTIVE) ClientIDManagerStartup.log (INACTIVE) StatusAgent.log

Hello All, I am wondering if anybody has a step-by-step for implementing the IBCM for CM? I've read a lot of different articles, but none of them seemed to have all the pieces? Basic idea is to obtain the ability to manage portable devices (laptops) while those devices are off of the domain. EX. teacher laptops that need to be managed via CM while on summer break. There is NO AD in the DMZ. I can open needed ports on the firewall for communication between Primary site server/MP and MP in DMZ. We've got CM1511 fully functional within the domain. Client checks, dns, OSD, WSUS, etc all work great while on the domain. I am looking to put a MP in the DMZ to manage these portable devices, but I am lacking the knowledge to fully implement this solution. Any pointers to a complete guide would be VERY much appreciated.