All Activity
This stream auto-updates
- Today
-
You don't need four primaries just because you have four sites. You might need remote DPs, but definitely not site. -
i have 4 sites thats why i need 4 primary for each site - Yesterday
-
For 2000 computers, you only require a single primary site. Having multiple primary in no way helps with reporting. Having 4 primary with a CAS is a HUGE overhead and will have LOTS of problems and require a big team to manage.
-
There is no way the IBM has created SW that is only used for the personal market. I would call "Bull" on that statement and push them again. Otherwise have you company drop it as it is NOT enterprise software and therefore should NOT be used within a Enterprise.
-
@Bignat - I think I just figured it out - create a bat file with only the install_acs_xx.js /QS in (or whatever you want) and deploy it for a user, not for a system. This works, the only downside now is, you will see the installation status go to failed as soon as you hit install, but for me it continued and installation ran just fine. See if I can bypass that one.
-
i have near to 2000 computers, and i use CAS for reporting purposes and as single administration point. how the CAS server would affect the hirarecy below 150k client ?
-
@Kingskawn Can you share how you solved this. I had a PS script from Reddit that did install v1.1.8.2 in the past, but does not work anymore with v1.1.8.5 I get Java language exceptions when launching, and the installation stops. @GarthMJ - I spoke to IBM last week and their answer is: we do not support mass deployments, nor do we support you on distributing it. When running as admin in CMD, all runs fine, but running under SYSTEM account. it's a true pain.
-
ZTISCCM.logZTIGather.logwpeinit.logsmsts-20201119-163751.logsmsts.logdism.logBDD.log OK, I managed to pull logs from one of the machines giving the "Inaccessible Boot Device". I found them in c:\smstslog, and the folder structure I saw on C makes me think a lot of the software I include in the OSD was successfully installed. Let me know if you need anything else to look at. As I mentioned, I usually kick off OSD's by booting to a flash drive, so making a TS a required deployment is new to me. Thanks for anything you can come up with! -
Let start with do you have over 150,000 computers? aka why have a CAS at all? This is begging for trouble.
-
well, first of all, thank you so much for the response, i appreciate it. secondly, the client is installed already from site1 which causes no problems, but when i try to uninstall the client and install it from another site "its resident site " it fails with errors' invalid namespace, unable to find wmi Root/ccm, cant find DP location from MP as u can see in the below screenshots the AD site for this client is GizaWH this site has a site code which is GWH when i try to install the client from the site i face the above issues no installtion happens. but when i installed from RDC site it worked fine no issues, how i can fix the other sites client push ?
-
First off you only need a CAS if you have over 150000 computers. having one otherwise will cause you lots of problems As such, take the time to move the cas if you don't ahve 150,000 computers. Secondly the CM client installed correctly, you can see that from the ccm.log. Lastly ccmsetup.log does seem like it has finished yet.
-
Hello, I have a CAS and 4 primary sites under, Site1,Site2,Site3,Site4 when i implemented site 1 i was able to push agent to the clients through the CM consle without any issue and still do , then i implemented the other 3 primary site, - each site is a MP and DP configured. - AD Schema is extended - Client push account is configured - the 3 sites has permissions on Management system container -the 3 sites has permission on the site 1 and the CAS - MP and DP is healthy as it shown on the components - Boundaries is configured now, i cant reassign site code for any client from the console or even from the client config manager in the control panel when i try to push a client from any site [ Site2,3,4] i face a bunch of errors below site server ccm.log Received request: "16778835" for machine name: "GIZA_TEST" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:31 PM 7468 (0x1D2C) Stored request "16778835", machine name "GIZA_TEST", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:31 PM 7468 (0x1D2C) Execute query exec [sp_CP_SetPushRequestMachineStatus] 16778835, 1 SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:31 PM 7468 (0x1D2C) ----- Started a new CCR processing thread. Thread ID is 0x8314. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 7468 (0x1D2C) Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 7468 (0x1D2C) Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 7468 (0x1D2C) Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 7468 (0x1D2C) ======>Begin Processing request: "16778835", machine name: "GIZA_TEST" SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) Execute query exec [sp_IsMPAvailable] N'GWH' SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> Attempting to connect to administrative share '\\Giza_Test.kazyon.com\admin$' using account 'KAZYON\SCCM' SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> NetUseAdd succeeded! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> Connected to administrative share on machine Giza_Test.kazyon.com using account 'KAZYON\SCCM' SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0xFFFF) SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> Attempting to make IPC connection to share <\\Giza_Test.kazyon.com\IPC$> with Kerberos authentication SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> SspiEncodeStringsAsAuthIdentity succeeded for IPC$ authentication! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> SspiExcludePackage succeeded for IPC$ authentication! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> SspiMarshalAuthIdentity succeeded for IPC$ authentication! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> NetUseAdd succeeded for IPC$ authentication! SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> Searching for SMSClientInstall.* under '\\Giza_Test.kazyon.com\admin$\' SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:33 PM 33556 (0x8314) ---> System OS version string "10.0.18362" converted to 10.00 SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:34 PM 33556 (0x8314) ---> Mobile client on the target machine has the same version, and 'forced' flag is turned on. SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:34 PM 33556 (0x8314) ---> Creating \ VerifyingCopying existence of destination directory \\Giza_Test.kazyon.com\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:34 PM 33556 (0x8314) ---> Copying client files to \\Giza_Test.kazyon.com\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:34 PM 33556 (0x8314) ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:34 PM 33556 (0x8314) ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:36 PM 33556 (0x8314) ---> ForceReinstall flag is set to true SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:36 PM 33556 (0x8314) ---> Updated service "ccmsetup" on machine "Giza_Test.kazyon.com". SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:36 PM 33556 (0x8314) ---> Started service "ccmsetup" on machine "Giza_Test.kazyon.com". SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) ---> Deleting SMS Client Install Lock File '\\Giza_Test.kazyon.com\admin$\SMSClientInstall.GWH' SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) Execute query exec [sp_CP_SetLastErrorCode] 16778835, 0 SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) ---> Completed request "16778835", machine name "GIZA_TEST". SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) Deleted request "16778835", machine name "GIZA_TEST" SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) Execute query exec [sp_CP_SetPushRequestMachineStatus] 16778835, 4 SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) Execute query exec [sp_CP_SetLatest] 16778835, N'11/23/2020 11:20:37', 89 SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) <======End request: "16778835", machine name: "GIZA_TEST". SMS_CLIENT_CONFIG_MANAGER 23/11/2020 1:20:37 PM 33556 (0x8314) client ccmsetup.log ==========[ ccmsetup started in process 784 ]========== ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) Running on platform X64 ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) Detected client installed with version '5.00.8790.1007' ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) Launch from folder C:\Windows\ccmsetup\ ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) CcmSetup version: 5.0.8790.1008 ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 11/23/2020 1:20:37 PM 3972 (0x0F84) In ServiceMain ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 0 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) [GIZA_TEST] Running on 'Microsoft Windows 10 Pro Education N' (10.0.18362). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /ignoreskipupgrade /config:MobileClient.tcf ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /ignoreskipupgrade /config:MobileClient.tcf ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) SslState value: 224 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMHTTPPORT: 80 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMHTTPSPORT: 443 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMHTTPSSTATE: 224 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMHTTPSCERTNAME: ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) FSP: ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMCERTSTORE: MY ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMFIRSTCERT: 1 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMPKICERTOPTIONS: 1 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) MANAGEDINSTALLER: 0 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Client is set to use HTTPS when available. The current state is 224. ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) CCMCERTID: SMS;38E37AC75F3E0DA1857A4AD9A70739B9D4437CD4 ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Begin searching client certificates based on Certificate Issuers ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Completed searching client certificates based on Certificate Issuers ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Begin to select client certificate ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) There are no certificates in the 'MY' store. ccmsetup 11/23/2020 1:20:37 PM 3644 (0x0E3C) Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=GWH))' ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) OperationalXml '<ClientOperationalSettings><Version>5.00.8790.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><PKICertOptions>1</PKICertOptions><SiteSigningCert>308202F3308201DBA003020102021034552D770844239D40715EBECECFE34E300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3230313131363137343831385A180F32313230313032343137343831385A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100CF3772E46F1D24DF73824E6E3AA7C7C361703FEA308D31D1EB307463B7D88CAA8CE608F9EE5DEC2C54D851777C59C48BD87F73C588A3C349B50F3474FF42C6FC58EB43E8B8EA1131397BF4233AF9187B7AE94F3860613F58FC4A012EB848A5E5A9E24543C4E85C26B3D87A2E78F60934C744848997099EF191E266ABC95782CAFA021843D39BE7DD06E3E8A50FCCB68406AC5953B77A05AB19F71D92039E2C21758CA47162CDEAD4E5957BCAFDD7ED392BBA664EF417C4BE9068B52A6406E57D037A667BA815E62D9EC82B5B7B069063945B36CC1809495F9E9A5A5D0F662845FEFF329F9B11FEF9B173F62982AF46898D4631E3C35584A779374B8714C0E9110203010001A33B303930210603551D11041A3018821647697A612D5343434D30312E6B617A796F6E2E636F6D30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100394AE5115594042F99EBA4E7B6FD4CC97000ECB3ECE69E660FEF4A57B598E2F2C81EE18F2C763B6FC962AA488936C21A48913B8BDA0202C3573C6E9A6F03D70789F1F93DADE201C6091E69C32BEC18D76C330E19E34ADCC3A6D2CFD9C4678E899DCD6C76E3E002866ACEDF464379B96BB915A252D237E61BA61BD5102E83DD3D655EB393EA21B8289053590631D147FCAFDB3FAD7EEAE5601A2A976F5678FF3763D9ABA8AD986F511C2D66000E5AC4B3DB7898B6F9833ED03447A8A99050BD835294CED1EA21B8E99F72370AC6C5A1C56BB37477C62223EACF24BF758388CBD6CDD2C2EC4D37C1E9F5C8A77632F2234D8322FC01A4A25188F14AAA9B08297232</SiteSigningCert></SecurityConfiguration><RootSiteCode>CAS</RootSiteCode><CCM> <CommandLine>MP=Giza-sccm01.kazyon.com SMSSITECODE=GWH</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="kazyon.com" /><Forest Value="kazyon.com" /><AADConfig Version="1.0"><Tenants></Tenants></AADConfig></ClientOperationalSettings>' ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) The MP name retrieved is 'Giza-SCCM01.kazyon.com' with version '8790' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) MP 'Giza-SCCM01.kazyon.com' is compatible ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Retrieved 1 MP records from AD for site 'GWH' ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) No AAD tenants information found. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Persisted AAD on-boarding info. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) FromAD: command line = MP=Giza-sccm01.kazyon.com SMSSITECODE=GWH ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Local Machine is joined to an AD domain ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Current AD forest name is kazyon.com, domain name is kazyon.com ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Domain joined client is in Intranet ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) CMPInfoFromADCache requests are throttled for 01:07:08 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Found MP http://Giza-SCCM01.kazyon.com from AD ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Successfully refresh bootstrap information from AD. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Begin searching client certificates based on Certificate Issuers ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Completed searching client certificates based on Certificate Issuers ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Begin to select client certificate ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) There are no certificates in the 'MY' store. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Retry time: 10 minute(s) ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) MSI properties: CCMCERTID="SMS;38E37AC75F3E0DA1857A4AD9A70739B9D4437CD4" CCMCERTSTORE="MY" CCMFIRSTCERT="1" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMPKICERTOPTIONS="1" INSTALL="ALL" MANAGEDINSTALLER="0" MP="Giza-sccm01.kazyon.com" SMSSITECODE="GWH" smsmplist="Giza-SCCM01.kazyon.com" ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Source List: ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) \\Giza-SCCM01.kazyon.com\SMSClient ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) \\GIZA-SCCM01.KAZYON.COM\SMSClient ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) MPs: ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Giza-SCCM01.kazyon.com ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) http://Giza-SCCM01.kazyon.com ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) MapNLMCostDataToCCMCost() returning Cost 0x1 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Detected client version 5.00.8790.1007 from WMI. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Task 'Configuration Manager Client Retry Task' does not exist ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Updated security on object C:\Windows\ccmsetup\. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 0 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) [5.00.8790.1007] Params to send '5.0.8790.1008 Deployment Error: 0x0, ' ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) <ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" BaselineCookie="" Platform="2" Langs=""/></ClientDeploymentMessage> ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Raised pending client deployment state message. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Detected 25715 MB free disk space on system drive. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Client OS Version 6.2 Service Pack 0.0 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Running as user "SYSTEM" ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Checking Write Filter Status. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) SiteCode: GWH ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) SiteVersion: 5.00.8790.1000 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Searching for a valid online MP... ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Checking the URL 'http://Giza-SCCM01.kazyon.com/CCM_Client/ccmsetup.cab' ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) MapNLMCostDataToCCMCost() returning Cost 0x1 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Client is not on internet ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Client is set to use webproxy if available. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) ccmsetup: Host=Giza-SCCM01.kazyon.com, Path=/CCM_Client, Port=80, Protocol=http, CcmTokenAuth=0, Flags=0x4101, Options=0xe0 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Created connection on port 80 ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Trying without proxy. ccmsetup 11/23/2020 1:20:38 PM 3644 (0x0E3C) Raising event: instance of CCM_CcmHttp_Status { ClientID = "GUID:1834F673-DDE5-424B-9A97-2C470D2B95B8"; DateTime = "20201123112039.127000+000"; HostName = "Giza-SCCM01.kazyon.com"; HRESULT = "0x00000000"; ProcessID = 784; StatusCode = 0; ThreadID = 3644; }; ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Failed to submit event to the Status Agent. Attempting to create pending event. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Raising pending event: instance of CCM_CcmHttp_Status { ClientID = "GUID:1834F673-DDE5-424B-9A97-2C470D2B95B8"; DateTime = "20201123112039.127000+000"; HostName = "Giza-SCCM01.kazyon.com"; HRESULT = "0x00000000"; ProcessID = 784; StatusCode = 0; ThreadID = 3644; }; ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Successfully submitted pending event to WMI. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Found a valid online MP 'http://Giza-SCCM01.kazyon.com'. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Searching for DP locations from MP(s)... ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) CCMSETUP bootstrap from Internet: 0 ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Current AD site of machine is GizaWH LocationServices 11/23/2020 1:20:39 PM 3644 (0x0E3C) DhcpGetOriginalSubnetMask entry point is supported. LocationServices 11/23/2020 1:20:39 PM 3644 (0x0E3C) Begin checking Alternate Network Configuration LocationServices 11/23/2020 1:20:39 PM 3644 (0x0E3C) Finished checking Alternate Network Configuration LocationServices 11/23/2020 1:20:39 PM 3644 (0x0E3C) Adapter {E859C6F2-31D4-4137-8EB4-ACB6B581D0CA} is DHCP enabled. Checking quarantine status. LocationServices 11/23/2020 1:20:39 PM 3644 (0x0E3C) Sending message body '<ContentLocationRequest SchemaVersion="1.00" BGRVersion="1"> <AssignedSite SiteCode="GWH"/> <ClientPackage RequestForLatest="0" DeploymentFlags="4098"/> <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseAzure="1" DPTokenAuth="1" UseInternetDP="0"> <ADSite Name="GizaWH"/> <Forest Name="kazyon.com"/> <Domain Name="kazyon.com"/> <IPAddresses> <IPAddress SubnetAddress="10.101.104.0" Address="10.101.104.50"/> </IPAddresses> </ClientLocationInfo> </ContentLocationRequest> ' ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Sending location request to 'Giza-SCCM01.kazyon.com' with payload '<ContentLocationRequest SchemaVersion="1.00" BGRVersion="1"> <AssignedSite SiteCode="GWH"/> <ClientPackage RequestForLatest="0" DeploymentFlags="4098"/> <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseAzure="1" DPTokenAuth="1" UseInternetDP="0"> <ADSite Name="GizaWH"/> <Forest Name="kazyon.com"/> <Domain Name="kazyon.com"/> <IPAddresses> <IPAddress SubnetAddress="10.101.104.0" Address="10.101.104.50"/> </IPAddresses> </ClientLocationInfo> </ContentLocationRequest> ' ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) MapNLMCostDataToCCMCost() returning Cost 0x1 ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Client is not on internet ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Client is set to use webproxy if available. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) ccmsetup: Host=Giza-SCCM01.kazyon.com, Path=/ccm_system/request, Port=80, Protocol=http, CcmTokenAuth=0, Flags=0x14101, Options=0xe0 ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Created connection on port 80 ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Trying without proxy. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Raising event: instance of CCM_CcmHttp_Status { ClientID = "GUID:1834F673-DDE5-424B-9A97-2C470D2B95B8"; DateTime = "20201123112039.424000+000"; HostName = "Giza-SCCM01.kazyon.com"; HRESULT = "0x00000001"; ProcessID = 784; StatusCode = 0; ThreadID = 3644; }; ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Failed to submit event to the Status Agent. Attempting to create pending event. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Raising pending event: instance of CCM_CcmHttp_Status { ClientID = "GUID:1834F673-DDE5-424B-9A97-2C470D2B95B8"; DateTime = "20201123112039.424000+000"; HostName = "Giza-SCCM01.kazyon.com"; HRESULT = "0x00000001"; ProcessID = 784; StatusCode = 0; ThreadID = 3644; }; ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Successfully submitted pending event to WMI. ccmsetup 11/23/2020 1:20:39 PM 3644 (0x0E3C) Received message '<ContentLocationReply SchemaVersion="1.00" BGRVersion="1"><BoundaryGroups BoundaryGroupListRetrieveTime="2020-11-23T11:20:39.360"><BoundaryGroup GroupID="67108865" GroupGUID="45dd48df-4213-4101-856a-29fb77650b1b" GroupFlag="0"/></BoundaryGroups><ContentInfo/><Sites><Site><MPSite SiteCode="GWH" MasterSiteCode="GWH" SiteLocality="FALLBACK"/><LocationRecords/></Site></Sites><ClientPackage IsStagingPackage="false" BaselineCookie="2020-07-08T18:20:18.053" FullPackageID="RDC00003" ExpectedPackageVersion="1" FullPackageVersion="1" FullPackageHash="5F184099858EE67D0450B96AC62F9EE Could you please enlighten me how to fix this issue. thanks in advance.
- Last week
-
Introduction I'm writing this post to catalog problems I recently faced while doing Windows Autopilot installations, we use a very slim enrollment Status Page (ESP) configuration with only one app marked as required (Microsoft Edge Chromium). The remaining applications are a mix of Win32 apps and the all important Microsoft Office 365 suite. This suite was configured with the following apps. Excel, OneDrive Desktop, OneNote, Outlook, PowerPoint, Teams, Word This worked well since about mid-February 2020. However, starting week 46, I started noticing the following error on newly delivered HP computers with Windows 10 version 1909 (and some office components preinstalled) after clicking the Microsoft Outlook icon soon after Windows Autopilot had completed. It looks ominous. Clicking OK and trying again, the problem looked even worse, you'd see something like this, outlook prompting you to choose a Profile. followed by a Script error, stating Class not registered on Line 278. Choose Yes or No had pretty much the same effect, Outlook was well and truly broken. If you clicked on the Account Information in Outlook you'd see something like this. A Metered connection warning followed by a Upgrade in Progress warning. The first is definitely a red-herring as the Network card was not in a state that was metered. When checking the version of office installed on affected machines I could see it was as shown below, Office version 2011. The interesting thing to note is that Computers that had a clean image of Windows 10 version 1909 with no Office installed previously did not exhibit this problem, it only affected factory image(s) of HP computers with Windows 10 version 1909 factory image and those images come with a version of Microsoft Office installed (in the Nordics), namely Microsoft Office 365 ProPlus version 1908 (Build 11929.20394). Troubleshooting Based on the above I knew that clean installs of Windows 10 1909 did not have the issue (even though they subsequently got the Office 2011 version installed before the user logged on). I initially suspected that security software or a device configuration profile were to blame, and went through the time consuming task of excluding a computer from each profile, and then resetting it to verify the behavior. Excluding a device from an assignment takes precedence over including a device so it was a good way of testing Windows Autopilot without certain settings or configurations, to rule them out. Below you can see I've excluded a group (containing my test device) from a Device Configuration profile, to verify if that was the issue. trying this didn't help, but it at least ruled out the following from being part of the problem. Device Configuration Profiles Win32 based Security based apps (such as Azure Information protection, Crowdstrike, Symantec DLP) Armed with that knowledge I recreated the Office Suite settings in my own test tenant, and ran a Windows Autopilot build, to my surprise the HP failed starting outlook the exact same way as in Production, so that completely ruled out everything other than the version of Office installed on the HP. Next I turned to logging options within Office/Outlook to see if that would help, but in reality it just generated .ETL files that I'm still analyzing in order to root-cause this issue. The breakthrough came when looking at the settings of the Office suite in Endpoint Manager. The version of Office that gets installed is based on your settings in the Office Suite, and we had been using these settings without problem since February 2020. The really important bit was the update channel, shown below. The update channel we were using was Current Channel (Preview). You can get details of the update channels here. According to Microsoft: ... three primary update channels: Current Channel Monthly Enterprise Channel Semi-Annual Enterprise Channel We recommend Current Channel, because it provides your users with the newest Office features as soon as they are ready. But what is the difference between Current Channel and Current Channel (Preview). According to Microsoft: To become familiar with the new features coming in the next feature release of Current Channel, we recommend that you use Current Channel (Preview). There isn’t a set release schedule for Current Channel (Preview). In general, a new version of Current Channel (Preview) with new features is released at least a week or more before that new version is released to Current Channel. There might be several releases of Current Channel (Preview), with non-security updates, before that version is released to Current Channel. You should deploy Current Channel (Preview) to a small, representative sample of users in your organization. This can help you identify any possible issues for your organization before those new features are released more broadly to your users that have Current Channel. We also encourage you to use Current Channel (Preview) so that you can identify any possible issues that you want us to fix before that version is released to Current Channel. This can help reduce the number of non-security updates that are needed for Current Channel. And this pretty much matched what we were doing, so now that we had this knowledge, but still had no root-cause for the Outlook (and Word/Excel issues). The Resolution I decided to change the Update Channel from Current Channel (Preview) to Current Channel. This decision was based on the fact that the Preview channel may contain changes that are incompatible with our image in some way, which is odd because we are using the factory installed HP image. Once I made the change, and re-tested Windows Autopilot the difference was clear. Now Outlook worked as expected without issue (and Word/Excel issues disappeared also), however the version of Office installed was Version 2010 instead of Version 2011 that we got in the Current Channel (Preview). This didn't matter too much but of course it meant that some cool new cloud friendly features in Version 2011 were now no longer available on newly installed Windows Autopilot machines. The versioning used by Microsoft for Office is somewhat confusing, in the Office Account screen you'll see the version info, here you can see it's listed as Current Channel, Version 2010 (the version without the problem). So version 2010 relates to year 20, month 10, or the October release of Office 365. That would of course mean that version 2011 is the November release. Summary Sometimes living on the edge means you will fall over. I know that changing from Current Channel (Preview) to Current Channel might only delay the problem until the Current Channel update channel migrates to the new version of office next month, so we may actually encounter this problem again, and soon. So to conclude, if any of you have come across this exact issue (I have searched and found similar problems with "Library not registered", but the advice within them didn't apply here), then please get in touch with me. In the meantime I will look through the gathered ETL traces to see if they provide any clue as to why Office was so broken on these new devices in order to root-cause the problem. Links used in this blog post Github script, Metered - https://gist.github.com/nijave/d657fb4cdb518286942f6c2dd933b472 Update Channels - https://docs.microsoft.com/en-us/deployoffice/overview-update-channels Office Versions - https://docs.microsoft.com/en-us/officeupdates/current-channel
-
Thanks for the reply! I will try to get the SMSTS logs and post them. Might be fun with the inaccessible boot device, but should work to boot to a flash drive and get to it from the command prompt (maybe?) At any rate, I've attached screenshots of my steps under "Format Disks" in the TS. Haven't changed the BIOS/UEFI settings on the actual machines, and the same TS worked just fine after kicking it off from a flash drive. Scott
-
get-windowsupdatelog on the machine in question will allow you to see where the updates is being downloaded from -
Well, when the person in the example above clicked on the toast notification, the KB it showed as pending install was one of the ones also showing as pending install in the SW center, so I don't think so. But I'll keep checking. -
hi Scott and welcome the first thing i'd suggest you do is grab the smsts*.log files on one of the affected computers and zip them up and upload here so we can take a look, that will hopefully reveal what went wrong any additional info you can add, such as hardware that was affected and whether or not there's any changes to BIOS/UEFI setup in the task sequence ?
-
yup that should improve things try it however are you sure your computers are only getting updates from ConfigMgr and not somewhere else ?
-
Yeah. Reading further at https://docs.microsoft.com/en-us/mem/configmgr/core/clients/deploy/device-restart-notifications, I think that's my problem. I need to set that to Yes. Does that sound correct? What I want is for users to get this popup instead:
-
Here's the settings. What's odd is I'm pretty sure most of my people do get an SCCM dialog box, NOT a Toast notification. Maybe I need to switch that last one to a Yes?
-
scjsorrell changed their profile photo
-
Hello, I recently deployed an OS task sequence to a device collection and all of the computers came up with "Inaccessible Boot Device" afterward. This is the first time I have tried pushing an OSD as a required deployment to computers that are already powered up and running Windows. The OSD works fine with booting to media, and this same OSD worked fine on these computers after I circled back around to reload them via bootable media. The computers showed up in AD with the automatically generated name, so I believe the OSD was successful, maybe just missing some drivers? Has anyone run into this before, or can you suggest a course of action? Thanks for any help you can offer! Scott
-
have you configured anything in Client Settings for notifications ?
-
are you referring to the TPM hash ? if so read here TPM password hash Previous MBAM clients don't upload the TPM password hash to Configuration Manager. The client only uploads the TPM password hash once. If you need to migrate this information to the Configuration Manager recovery service, clear the TPM on the device. After it restarts, it will upload the new TPM password hash to the recovery service. Uploading of the TPM password hash mainly pertains to versions of Windows prior to Windows 10. Windows 10 by default does not save the TPM password hash so therefore does not normally upload the TPM password hash. For more information, see About the TPM owner password.
-
My windows update deployments are set with User Experience/User Notifications set to "Display in Software Center, and only show notifications for computer restarts." Some (but not all?) of my users are reporting that they're getting a non-SCCM Windows notification. When the installation takes place they get the regular notification from SCCM that they will be rebooted in X minutes, which is all I want. I don't want them to get the regular Windows notification. Am I missing something obvious? How do I suppress these?
-
Hi, We need to Migrate Bitlocker from MABAM to SCCM (Mbam integrate) but I can't seem to find information on if it will move the TPM key to SCCM or not. We are running SCCM 2002 (soon to be upgraded to 2009) MBAM server is 2.3 (We are in process of upgrading this to 2.5) We would like to integrate MBAM with SCCM but also migrate recover key + TPM key. I know recovery key will be moved but will the TPM key moved too, if not how do I move the TPM key without re-encrypting the drive.
