Workgroup client cannot discovered SCCM 2012 R2
Hi,
I have enabled the Network Discovery in SCCM 2012 R2, and defined the subnet of clients that I want to manage. Then IP subnet boundaries has been created. When I see
Devices in Assets and Compliance, the workgroup clients cannot discovered.
Communication between the workgroup clients with SCCM server is no issue in the network, by ping and mapping folder share in both is good. Windows firewall on all workgroup clients has configured to allow port File and Printer Sharing and WMI.
How I can discovered all Workgroup clients?
Thanks
Regards, Bar Waelah
Hi Bar Waelah,
I think you need to configure the Maximum hops on the bottom of SNMP Tab.
For more details, please check the Limiting Network Discovery.
http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_NetworkDisc
You could also specify the IP Address or NetBIOS name of the device in SNMP Devices.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Similar Messages
-
Lync 2013 x64 silent client deployment via SCCM 2012 SP1
Greetings everyone!
I ran into a problem with Lync 2013 x64 silent deployment.
I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
Added them as applications to sccm software library.
Deployment of Lync 2013 x86 application was a success with over than 80% compliance.
But all Lync 2013 x64 automatic installations finish with different errors.
I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
My membership query-rules for this collection:
Office 2013 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
Office 2010 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
The same configuration works with Lync 2013 x86 deployment, except other setup folders.
When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
sites with deployment point.
Thanks in advance.Hi,
Here are some tips and tricks for your reference.
Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Previously blocked client computers - now cannot install SCCM 2012 R2 client
Hello,
I have a Primary Site on SCCM 2012 R2. New installation of 2012 R2, not upgrade from SCCM 2007. My environment is pretty small for now, having added just few dept computers in the company.
We are using SCCM for Endpoint Security antivirus deployment. Some time ago I had not configured the Discovery methods correctly and the scep client started to install on few machines on which it was not supposed to be installed. I removed the clients then
(both remote and local uninstallation) but since the sccm client was getinng installed again - I had to Block these few machines. Now the problem is that I cannot install the scep client on these computers that have previously been blocked. I am sure the previous
block is the reason because these are about 6-7 machines and only they do not install. All others do install scep client. The installation process goes smooth on these problematic machines, ccmsetup folder gets created in C:\Windows, I follow the ccmsetup.log
and it says " <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="12:33:56.415-180" date="10-08-2014" component="ccmsetup" context="" type="1" thread="3992"
file="ccmsetup.cpp:10875"> " at the end of the log which is what it is supposed to show when installation goes ok, then Ccmexec.exe process continues running but folder Microsoft Security Client in C:\Program Files never gets
created and no scep client gets installed.
I tried deleting the computers from the sccm console and discovering them anew - did not help. Tried even renaming the comp locally, after having it deleted from sccm console, then adding it anew hoping sccm will regard it as a new resource-again no good.
All these computers have the Approve, Block and Unblock buttons greyed out/inactive in console.
Has anyone had this same problem? Any ideas what can be done. Thank you.
Regards,
HristoHi,
were you ever able to fix this?
I'm running in a similar issue here.
One single client was blocked, then deleted, lateron recreated (imported manually name and MAC address).
Now the client is unable to register itself in SCCM 2012 R2 (no CU yet).
Tried the usual stuff: uninstalled SCCM client, remove the entries of CCMsetup and SMS from registry, deleted the SMS certs from the computer personal
store and deleted the smscfg.ini from C:\Windows. Then re-installed the SCCM client
Client logs look fine, except ClientIDManagerStartup.log:
<![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:F295F120-9C99-4D10-82B7-027FDD86B5F6 ...]LOG]!><time="14:46:11.555-60" date="01-12-2015" component="ClientIDManagerStartup" context=""
type="1" thread="6320" file="regtask.cpp:1609">
<![LOG[[RegTask] - Server rejected registration request: 3]LOG]!><time="14:46:12.616-60" date="01-12-2015" component="ClientIDManagerStartup" context="" type="3" thread="6320" file="regtask.cpp:1675">
On the server:
Begin validation of Certificate [Thumbprint 12923BCACDAE5B89547A25E54BF11E533163742F] issued to 'SMS' MP_RegistrationManager 12.01.2015 14:31:10 8600 (0x2198)
Completed validation of Certificate [Thumbprint 12923BCACDAE5B89547A25E54BF11E533163742F] issued to 'SMS' MP_RegistrationManager 12.01.2015 14:31:10 8600 (0x2198)
Encountered database error while verifying headers for client 'GUID:F3063334-69B4-471F-B158-56782E499F4A' (0x87d00238). MP_RegistrationManager 12.01.2015 14:31:10 8600 (0x2198)
CCMValidateAuthHeaders failed (0x87d00238) to validate headers for client 'GUID:F3063334-69B4-471F-B158-56782E499F4A'. MP_RegistrationManager 12.01.2015 14:31:10 8600 (0x2198)
A client is trying to re-register with an administrator revoked certificate: SMSID='GUID:F295F120-9C99-4D10-82B7-027FDD86B5F6'. MP_RegistrationManager 12.01.2015 14:31:10 8600 (0x2198)
MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 12.01.2015 14:31:10 8600 (0x2198)
We are using HTTP for client communication.
Any ideas appreciated.
Michael -
Client Install Issue - SCCM 2012 R2 - Manual Deploy Installed ok
Hello, I have sccm 2012 configured with 2,000 machine approx. It is been used mainly as a Software Deployment tool for now. On checking a recent IE10 upgrade, I noticed that there is a number of machines that do not have the client installed (and thus did
not upgrade IE). I picked 1 machine, searched in SCCM - had no client. I checked all relevant settings:
Boundary for Client in question - ok
Local Client Settings (ip,dns,no firewall, ping sccm ok and vice versa etc).
Once i right clicked to deploy the client, it installed no problem. I checked the ccmsetup log file and the only info it had was from the time that the client was manually deployed (I will attach the log below anyway). I am really puzzled as to why the client
did not install and if this is the issue why IE is not upgrading (it is hard to pinpoint as there are 250 sites approx). The automatic install task works no problem on other machines once the machine goes online.
Any help, would be great. Here is the log (I am fairly new to SCCM btw):
SCCM 2012 R2 - Windows 7 SP1 32 Bit
==========[ ccmsetup started in process 7196 ]========== ccmsetup 05/02/2015 16:28:39 4100 (0x1004)
Running on platform X86 ccmsetup 05/02/2015 16:28:39 4100 (0x1004)
Launch from folder C:\Windows\ccmsetup\ ccmsetup 05/02/2015 16:28:39 4100 (0x1004)
CcmSetup version: 5.0.7958.1401 ccmsetup 05/02/2015 16:28:39 4100 (0x1004)
In ServiceMain ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
SslState value: 224 ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
CCMHTTPPORT: 80 ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
CCMHTTPSPORT: 443 ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
CCMHTTPSSTATE: 224 ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
CCMHTTPSCERTNAME: ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
FSP: COLSCCM01.LC-UK.ORG ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
CCMFIRSTCERT: 1 ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Retry time: 10 minute(s) ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
MSI properties: INSTALL="ALL" SMSSITECODE="COL" FSP="COLSCCM01.LC-UK.ORG" SMSCACHESIZE="10240" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"
ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Source List: ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
\\COLSCCM01.lc-uk.org\SMSClient ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
\\COLSCCM01.LC-UK.ORG\SMSClient ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
MPs: ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
COLSCCM01.lc-uk.org ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
No version of the client is currently detected. ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Sending Fallback Status Point message to 'COLSCCM01.LC-UK.ORG', STATEID='100'. ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
Params to send FSP message '5.0.7958.1401 Deployment ' ccmsetup 05/02/2015 16:28:39 500 (0x01F4)
State message with TopicType 800 and TopicId {19607F6A-0C46-488C-B28D-36640FB0DF94} has been sent to the FSP FSPStateMessage 05/02/2015 16:28:40 500 (0x01F4)
Running as user "SYSTEM" ccmsetup 05/02/2015 16:28:40 500 (0x01F4)
Detected 434753 MB free disk space on system drive. ccmsetup 05/02/2015 16:28:40 500 (0x01F4)
Checking Write Filter Status. ccmsetup 05/02/2015 16:28:40 500 (0x01F4)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 05/02/2015 16:28:40 500 (0x01F4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=COL))' ccmsetup 05/02/2015 16:28:40 500 (0x01F4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F0308201D8A00302010202104A263F5C34E3AAAA4C178EF33CA94377300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134303630383134343831315A180F32313134303531363134343831315A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100A4FF6866BC9622545F811F8008ABDC534E96C9699A3354E990CADB04B1399B29EB80FB844425DEEDD9FE680C57AA0FE05D42CF1D431BB69080D4E7ED91A8255739089A83E4836F28B09331C100B0BAD81AD795EFD01C9ECF8DCE2BE03B52EE3AC35E7003B728E0FA56F145279301189388F3FC90A6C3DA5342C61230550C2B79DECB64AC0958C6DE2D5BF83C3EA29126E231FBEAADBD632F65AF41AC3267DB3986929C46A08AF0BF925A40E15A346B38219CC62C6C0BAC8990C05EA04037458F1853E251D8C16946F845D46CB47884D9EB00543AC8B02A7C099B53F7DE1EBD11AA1272476E5AAF55B2CC38122B62C751D988C81A07D06F87A9F7980D2B3560A90203010001A3383036301E0603551D11041730158213434F4C5343434D30312E6C632D756B2E6F726730140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100A0DE29D627EB45EF2D0074AD578B62CE9007918B4316351DB2DBEFF2D0DF52C0FF58B6DE3405C88572ECCFAF2A7B335B234FE7D1E5B0FDA20548FEFE4B9E6AFB45E77627EDB70E2378A3135FB1FC34C2308F0FBD1ADD890DD08D8D6081B73FFF86DE87DBF678A7CAD73AE32BF6EB3B9D1E4E0380D7FBE3E9F9EF49339031636F2B3CC60989B8443B91F9F69F5837025B6CAE64E2D1837FAF712186A02567EA87F9E82FD170C4DEA61DC61C16226450FCBE062948F2219FB5801DF3AF73443349421A7228F5E1372B5CA165D8ABAB9D1B3FEAF22705A473AAAB034C2A289AA7A507550050D6516C2D7BECDE5686F17CC66FBB7D2C439F15644EBF9EF7E8402109</SiteSigningCert></SecurityConfiguration><RootSiteCode>COL</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=COL FSP=colsccm01.lc-uk.org SMSCACHESIZE=10240</CommandLine> </CCM><FSP> <FSPServer>COLSCCM01.lc-uk.org</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState"
Value="0" /></Capabilities><Domain Value="lc-uk.org" /><Forest Value="lc-uk.org" /></ClientOperationalSettings>' ccmsetup 05/02/2015 16:28:41 500
(0x01F4)
Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
The MP name retrieved is 'COLSCCM01.lc-uk.org' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup
05/02/2015 16:28:41 500 (0x01F4)
MP 'COLSCCM01.lc-uk.org' is compatible ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Retrieved 1 MP records from AD for site 'COL' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Retrived site version '5.00.7958.1000' from AD for site 'COL' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
SiteCode: COL ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
SiteVersion: 5.00.7958.1000 ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Only one MP COLSCCM01.lc-uk.org is specified. Use it. ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Searching for DP locations from MP(s)... ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Current AD site of machine is Millbank LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Local Machine is joined to an AD domain LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Current AD forest name is lc-uk.org, domain name is lc-uk.org LocationServices 05/02/2015 16:28:41 500 (0x01F4)
DhcpGetOriginalSubnetMask entry point is supported. LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Begin checking Alternate Network Configuration LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Finished checking Alternate Network Configuration LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Adapter {743579BD-D66A-4BF9-B487-2AAC075B9473} is DHCP enabled. Checking quarantine status. LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Adapter {8F25ACE0-AE8A-45DD-BF3D-F1315E2B9974} is DHCP enabled. Checking quarantine status. LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Adapter {8AE4D673-90E8-4FCF-AE50-79474ADC6190} is DHCP enabled. Checking quarantine status. LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Adapter {9AA2CA9C-0C0A-48E3-B67E-F9E574AE9DB2} is DHCP enabled. Checking quarantine status. LocationServices 05/02/2015 16:28:41 500 (0x01F4)
Sending message body '<ContentLocationRequest SchemaVersion="1.00">
<AssignedSite SiteCode="COL"/>
<ClientPackage/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
UseInternetDP="0">
<ADSite Name="Millbank"/>
<Forest Name="lc-uk.org"/>
<Domain Name="lc-uk.org"/>
<IPAddresses>
<IPAddress SubnetAddress="10.103.38.0" Address="10.103.38.10"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Sending message header '<Msg SchemaVersion="1.1"><ID>{57972056-54D4-461F-B818-D3420A0B5C51}</ID><SourceHost>LCD14572</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:LCD14572:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>COLSCCM01.lc-uk.org</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:41Z</SentTime><Body
Type="ByteRange" Offset="0" Length="1084"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 05/02/2015
16:28:41 500 (0x01F4)
CCM_POST 'HTTP://COLSCCM01.lc-uk.org/ccm_system/request' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Content boundary is '--aAbBcCdDv1234567890VxXyYzZ' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Received header '<Msg SchemaVersion="1.1">
<ID>{48D22538-0FEA-44E6-AAD2-1829DDED2223}</ID>
<SourceID>GUID:A5143C3E-EA22-4B93-BFF5-B8B859F869F5</SourceID>
<SourceHost>COLSCCM01</SourceHost>
<TargetAddress>direct:LCD14572:LS_ReplyLocations</TargetAddress>
<ReplyTo>MP_LocationManager</ReplyTo>
<CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
<Priority>3</Priority>
<Timeout>600</Timeout>
<TargetHost>LCD14572</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:39Z</SentTime><Body
Type="ByteRange" Offset="0" Length="2378"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019106092A864886F70D010702A08201823082017E020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015D30820159020101303630223112301006035504031309434F4C5343434D3031310C300A06035504031303534D5302106A638C8D6A89DE904525D14326BE4DB0300906052B0E03021A0500300D06092A864886F70D01010105000482010027BAE95F5B0DD9F75743E1E40A189091900F78F19367C2A8328F823C63F24229608E7CF02FF2FE76FC61C6A61EF0FE8F19AC75755B88124B13964AE58F971DAB67E47B4DDCAA943B4C27F7AF9B5A0AD1DE956A3AACA26965F5FDAC8659E6263DBB55E025FB305C665AC1AA49972CC937A757EC14F1097DA27AB9998D7CAE332EC135A937A80285C87448AD7B4F4ED059063BCB5032920C65CE16FD32475CD395B279021F62E5C3B534697EDCD68A98D2A654379CCA17056F7B4FAB0346242CE56681F405DB9700FD766FDBD584BB69A4AC088BF3B971BE8B05B723701A22B9D76BB5C063F1BD32B56DB7B3BDC6D827E3D90106F3C1145E04B0629528EA24BD37</Property><Property
Name="AuthSenderMachine">COLSCCM01;COLSCCM01.lc-uk.org;</Property><Property Name="MPSiteCode">COL</Property></Hook></Hooks><Payload Type="inline"/></Msg>' ccmsetup
05/02/2015 16:28:41 500 (0x01F4)
Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="COL" MasterSiteCode="COL"
SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002" Signature="http://COLSCCM01.lc-uk.org/SMS_DP_SMSSIG$/COL00002"/><ADSite
Name="Millbank"/><IPSubnets><IPSubnet Address="10.20.0.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>COLSCCM01.lc-uk.org</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage
FullPackageID="COL00002" FullPackageVersion="2" FullPackageHash="DB3D5D115FC93F6275817FB9791864D98D4AF6897339B9D4AB1C0DE456C240A8" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false"
LastModifiedTime="30376953;932870912" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>' ccmsetup 05/02/2015
16:28:41 500 (0x01F4)
Found local location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Discovered 1 local DP locations. ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Got 401 challenge Retrying with Windows Auth... ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' ccmsetup 05/02/2015 16:28:41 500 (0x01F4)
Using DP location http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002 ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab' ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Got 401 challenge Retrying with Windows Auth... ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab' ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Retrieved client version '5.00.7958.1000' and minimum assignable site version '5.00.7845.1000' from manifest ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.7845.1000' ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Site version '5.00.7958.1000' is compatible. Client deployment will continue. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' passed site version check. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Successfully loaded ccmsetup manifest file. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1401' ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Running from temp downloaded folder or manifest is not newer than ccmsetup. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/vcredist_x86.exe' is applicable. Add to the list. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'x64/vcredist_x64.exe' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/vc50727_x86.exe' is applicable. Add to the list. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'x64/vc50727_x64.exe' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/WindowsUpdateAgent30-x86.exe' is applicable. Add to the list. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'x64/WindowsUpdateAgent30-x64.exe' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/msxml6.msi' is applicable. Add to the list. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'x64/msxml6_x64.msi' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/msrdcoob_x86.exe' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'x64/msrdcoob_amd64.exe' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'pkgmgr.exe' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'dism.exe' is applicable. Add to the list. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'wimgapi.msi' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'x64/MicrosoftPolicyPlatformSetup.msi' is not applicable. ccmsetup 05/02/2015 16:28:42 500 (0x01F4)
Item 'i386/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list. ccmsetup 05/02/2015 1Hi, Yes i had a look at the log yesterday. there are errors initially, but then the install completes. I can copy the whole log here, the machine in question is LCD14572. If you could take a look would be great. Still doesnt explain why i had to manually
push the client though:
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154539 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:05:58 3648 (0x0E40)
Execute query exec [sp_CP_GetPushMachineName] 2097154539 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:05:58 3648 (0x0E40)
Received request: "2097154539" for machine name: "LCD15000" on queue: "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:05:58 3648 (0x0E40)
Stored request "2097154539", machine name "LCD15000", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:05:58 3648 (0x0E40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 1 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:05:58 3648 (0x0E40)
----- Started a new CCR processing thread. Thread ID is 0x12d8. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Getting a new request from queue "Retry" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Found CCR "2097154540.ccr" in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
======>Begin Processing request: "2097154539", machine name: "LCD15000" SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 4824 (0x12D8)
Execute query exec [sp_IsMPAvailable] N'COL' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 4824 (0x12D8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 4824 (0x12D8)
---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 4824 (0x12D8)
Execute query exec [sp_CP_GetPushRequestMachine] 2097154540 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Successfully retrieved information for machine LCD14589 from DB SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154540 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154540 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Execute query exec [sp_CP_GetPushMachineName] 2097154540 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Received request: "2097154540" for machine name: "LCD14589" on queue: "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Stored request "2097154540", machine name "LCD14589", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 1 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:00 3648 (0x0E40)
----- Started a new CCR processing thread. Thread ID is 0x1d10. There are now 2 processing threads SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Getting a new request from queue "Retry" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Found CCR "2097154542.ccr" in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
======>Begin Processing request: "2097154540", machine name: "LCD14589" SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 7440 (0x1D10)
Execute query exec [sp_IsMPAvailable] N'COL' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 7440 (0x1D10)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 7440 (0x1D10)
---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 7440 (0x1D10)
Execute query exec [sp_CP_GetPushRequestMachine] 2097154542 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Successfully retrieved information for machine LCD14571 from DB SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154542 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154542 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Execute query exec [sp_CP_GetPushMachineName] 2097154542 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Received request: "2097154542" for machine name: "LCD14571" on queue: "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Stored request "2097154542", machine name "LCD14571", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 1 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:02 3648 (0x0E40)
----- Started a new CCR processing thread. Thread ID is 0x1768. There are now 3 processing threads SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:04 3648 (0x0E40)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:04 3648 (0x0E40)
Getting a new request from queue "Retry" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:04 3648 (0x0E40)
Sleeping for 60 minutes for queue "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:04 3648 (0x0E40)
======>Begin Processing request: "2097154542", machine name: "LCD14571" SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:04 5992 (0x1768)
Execute query exec [sp_IsMPAvailable] N'COL' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:05 5992 (0x1768)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:05 5992 (0x1768)
---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:05 5992 (0x1768)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:21 4824 (0x12D8)
---> The device LCD15000 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:21 4824 (0x12D8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:21 4824 (0x12D8)
---> Attempting to connect to administrative share '\\LCD15000.lc-uk.org\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:21 4824 (0x12D8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:23 7440 (0x1D10)
---> The device LCD14589 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:23 7440 (0x1D10)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:23 7440 (0x1D10)
---> Attempting to connect to administrative share '\\LCD14589.lc-uk.org\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:23 7440 (0x1D10)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:26 5992 (0x1768)
---> The device LCD14571 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:26 5992 (0x1768)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:26 5992 (0x1768)
---> Attempting to connect to administrative share '\\LCD14571.lc-uk.org\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:26 5992 (0x1768)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> The device LCD15000.lc-uk.org does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> The device LCD15000 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> ERROR: Unable to access target machine for request: "2097154539", machine name: "LCD15000", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47
4824 (0x12D8)
Execute query exec [sp_CP_SetLastErrorCode] 2097154539, 53 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
Stored request "2097154539", machine name "LCD15000", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 2 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
Execute query exec [sp_CP_SetLatest] 2097154539, N'02/05/2015 16:06:47', 2 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
<======End request: "2097154539", machine name: "LCD15000". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:47 4824 (0x12D8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> The device LCD14589.lc-uk.org does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> The device LCD14589 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> ERROR: Unable to access target machine for request: "2097154540", machine name: "LCD14589", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51
7440 (0x1D10)
Execute query exec [sp_CP_SetLastErrorCode] 2097154540, 53 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
Stored request "2097154540", machine name "LCD14589", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 2 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
Execute query exec [sp_CP_SetLatest] 2097154540, N'02/05/2015 16:06:51', 2 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
<======End request: "2097154540", machine name: "LCD14589". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:51 7440 (0x1D10)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
---> The device LCD14571.lc-uk.org does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035) SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
---> The device LCD14571 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
---> ERROR: Unable to access target machine for request: "2097154542", machine name: "LCD14571", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55
5992 (0x1768)
Execute query exec [sp_CP_SetLastErrorCode] 2097154542, 53 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
Stored request "2097154542", machine name "LCD14571", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 2 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
Execute query exec [sp_CP_SetLatest] 2097154542, N'02/05/2015 16:06:55', 2 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
<======End request: "2097154542", machine name: "LCD14571". SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:06:55 5992 (0x1768)
CCR count in queue "Retry" is 3. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:07:42 6564 (0x19A4)
Sleeping for 634 seconds... SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:07:43 6564 (0x19A4)
Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:47 4824 (0x12D8)
--- This thread is terminating due to inactivity SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:47 4824 (0x12D8)
----- Terminated CCR processing thread. There are now 2 processing threads SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:47 4824 (0x12D8)
Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:51 7440 (0x1D10)
--- This thread is terminating due to inactivity SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:51 7440 (0x1D10)
----- Terminated CCR processing thread. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:51 7440 (0x1D10)
Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:55 5992 (0x1768)
--- This thread is terminating due to inactivity SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:55 5992 (0x1768)
----- Terminated CCR processing thread. There are now 0 processing threads SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:16:55 5992 (0x1768)
Sleeping for 1 seconds... SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:16 6564 (0x19A4)
The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:17 6564 (0x19A4)
Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Default MP: COLSCCM01.lc-uk.org SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Certificate Store: SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Checking configuration information for server: COLSCCM01.LC-UK.ORG. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Checking configuration information for server: COLSCCM01.LC-UK.ORG. SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Fallback Status Point: COLSCCM01.lc-uk.org SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Install on DC: False SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:18:18 6564 (0x19A4)
Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:23:39
2876 (0x0B3C)
Execute query exec [sp_CP_GetNewPushMachines] N'COL' SMS_CLIENT_CONFIG_MANAGER 05/02/2015 16:28:09 2876 (0x0B3C)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154468, 1 SMS_CLIENT_CONF -
Monitor model (Desktop Monitor) was not loaded in the client resource explorer | SCCM 2012
Hi Everyone,
We have SCCM 2012 installed and configured. More than 2000+ computers have been installed SCCM client and manageable by SCCM server.
The inventory (Desktop Monitor) was not loaded in the client resource explorer (For some clients it got inventoried). Is there are possibilities that the Max file size might get exceeded the actual limit for the hardware inventory
which has to be increased in the registry?
Please provide us a solution.
Thanks in advance,
Iniyan GSee dataldr.log on the site server. It would show .mif files that exceeded the file size. InventoryAgent.logon the client might also help.
Torsten Meringer | http://www.mssccmfaq.de -
Client manageability in SCCM 2012
Hi All
I am Planning to have test SCCM 2012 environment and for that i need few architecture suggestions. Kindly suggest me on the same so that i can implement an effective infrastructure design.
Total Number of Clients to Support - 58000
First Draft version of design consist of 1 Primary Site and 3 Seconadry Sites. Kindly confirm if 1 primary and 3 secondary site will be able to cater 58000 clients. As per my understanding secondary site supports 5000 clients and Primary sites can support
25000 Clients.
Also confirm that clients under secondary site will be considered as client of primary site (linit of 25000) or seperately counted (25k +5K).
Regards
Regards SureshKent's book talks about a limitation of 50 000 when using a local SQL server.
Kent's book does state this.
Note that the Technet article states the following (from the link supplied by John):
Client group 1 includes Windows Server and client.
Site type
Configuration Manager version
Client group 1
Client group 2
Client group 3
Stand-alone primary site, with a local site database, or a remote site database
System Center 2012 Configuration Manager with no service pack 1
100,000
50,000 4
25,000
System Center 2012 Configuration Manager with SP1
100,000 2
50,000 4
25,000
System Center 2012 R2 Configuration Manager
100,000 2
50,000 4
25,000
Child primary site with a local site database
System Center 2012 Configuration Manager with no service pack 1
50,000
50,000 4
25,000
System Center 2012 Configuration Manager with SP1
50,000 2
50,000 4
25,000
System Center 2012 R2 Configuration Manager
50,000 2
50,000 4
25,000
Child primary site with a remote site database
System Center 2012 Configuration Manager with no service pack 1
100,000
50,000 4
25,000
System Center 2012 Configuration Manager with SP1
100,000 2, 3
50,000 4
25,000
System Center 2012 R2 Configuration Manager
100,000 2, 3
50,000 4
25,000
Secondary site
Any version 1
5,000 5
Cheers
Paul | sccmentor.wordpress.com -
How to manage Forefront Endpoint Prorection Security Client 2010 with SCCM 2012
Hi
I've sucessfully installed System Center Configuration Manager 2012
and now I 'd like to push/deploy Forefront Endpoint Protection Client 2010 on client machines.I also know that Microsoft embedded Forefront Endpoint Protection in SCCM 2012 so that you can manage FEP from single SCCM 2012 console.Now
when I try to push FEP client on client machines using Default Client Settings
then I've found that all Endpoint Protection settings are greyed out !
Do I need to install Forefront Endpoint Protection 2010 or 2012 Server (which is beta) with SCCM 2012, in order to deploy FEP client or is there a workaround or solution to resolve this ?
Thanks
SohailHi,
Endpoint Protection 2012 is builtin in SCCM 2012, you simply add the Site Role called Endpoint Protection either on your CAS if you have one of those or on your Primary site Server. FEP is no longer a standalone installer and it is a released product and
no longer Beta.
Then the Endpoint Protection Client Settings will no longer be greyed out and you can deploy the System Center 2012 Endpoint Protection client.
http://technet.microsoft.com/en-us/library/hh508760.aspx
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
Improvements for Client Remediation in SCCM 2012 R2
Hello,
Is there any information available about Client Remediation improvements in SCCM 2012 R2 over previous versions?If by previous version you mean ConfigMgr 2007, then yes, they added a health feature that runs as a scheduled task.
Remember though that nearly all agent health issues in ConfigMgr are not ConfigMgr's doing, they are the result of WMI. So really, it's about the OS you are using. If you are on XP (God help you) you are pretty much always going to have WMI issues for a
variety of reasons (including stupid user tricks). If you are on Win 7, then you're better off but you should also deploy KB2775511. Win 8, to my knowledge, is pretty solid as far as WMI goes.
Jason | http://blog.configmgrftw.com -
Lync 2013 client deployment via SCCM 2012 forcing restart
All,
I am attempting to deploy the Lync 2013 x86 client via SCCM 2012 to 158 machines running the Office 2010 suite. My package runs, and the installs complete but they are forcing a restart after the install even though I have gone in to everything that I can
think of to tell the install not to force a restart. I am a newb in the ways of SCCM so I have been self teaching, and I may have missed something.
I have gone into the config.xml and changed the value SETUP_REBOOT to NEVER.
In the program properties I have RUN set as HIDDEN, and AFTER RUNNING set to NO ACTION REQUIRED.
Is there something that I am missing to stop the users machine from restarting after the install completes?Great, unfortunately it will be because files (usually shared DLLs) are in use as Office is opened, despite it being an older version.
Agree it's not optimal, I usually just tell clients that they will need to reboot, or that it will push out overnight (when I schedule it) and their computer will restart, so make sure they save everything.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta) -
Cannot install SCCM 2012 SP1 CU4
Hi,
I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
Anybody experiencing the same behavior ?The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file? .
CU4 was released this week:
http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!) -
Win 7 Client cannot access Win 2012 share by domain name
Hello Everyone,
We have Windows 2012 R2 Server configured as Domain cum File Server Role,
There are 20 Win7 Clients / Domain Users who access and used their specific folder on server with \\Servername\Foldername
After some hour (not fixed) for some users (not specific) the server path goes unavailable, but the same folder is accessible with IP address like \\192.168.1.1\Foldername. and after rebooting Win7 Client we can again access the server folder with name.
This happen to any users anytime and the same time other users can access their folder by name,
Please help me on this issue..
Thanks in Advance> After some hour (not fixed) for some users (not specific) the server
> path goes unavailable, but the same folder is accessible with IP address
> like \\192.168.1.1\Foldername. and after rebooting Win7 Client we can
> again access the server folder with name.
This is a kerberos issue.
By default, tickets (especially the TGT which is issued at logon) have a
live time of 8 hours or so (can be adjustet). If this ticket expires and
cannot be renewed (due to a lack of connectivity to a DC or whatever
infrastructure issue), Kerberos fails and ressources cannot be accessed
via name.
IP on the other hand always uses NTLM and thus still works.
How the Kerberos Version 5 Authentication Protocol Works:
https://technet.microsoft.com/library/cc772815.aspx
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :)) -
SCCM 2012 Distribution Point server in a workgroup as well as the clients
HI,
It is possible to have a distribution point set up by SCCM 2012 R2 which resides in a workgroup to manage workgroup users.
Basically, SCCM 2012 R2 is setup within a domain and a forest, The clients in the workgroup resides in a DMZ. The server in the DMZ is also within the workgroup.
For some reasons, at this time, it is not possible to add the server to the Active Directory to push it the distribution point role and therefore managing thoses clients within the workgroup.
Is there a way to set up the distribution point role to a server in a workgroup?
Thank you
Ehttps://technet.microsoft.com/en-us/library/gg682077.aspx?f=255&MSPPError=-2147217396#BKMK_SupConfigWorkgroups
Jason | http://blog.configmgrftw.com | @jasonsandys -
Installing and Managing SCCM 2012 R2 client in workgroup
Hi,
I'm trying to install sccm 2012 r2 client on a workgroup workstation, but i can't manage to put the client working.
Already tried this solutions
http://blogs.technet.com/b/anilm/archive/2012/05/06/managing-workgroup-clients-in-configuration-manager-2012.aspx
http://eskonr.com/2013/08/sccm-configmgr-2012-manage-workgroup-computers-for-deploymentremote-tools-etc/
if i use this commands to install the client the client don't install.
ccmsetup.exe /source:C:\client SMSSITECODE=PRI SMSMP=sgcmcen.cm12lab.com DNSSUFFIX=cm12lab.com
if i use this one same happens
Ccmsetup.exe /mp:sccmserver SMSSITECODE=XXX FSP=sccmserver DNSSUFFIX=dnssuffix
If i use this one the client gets installed and the site code assigned but nothing more. It shows at the sccm console, but don't receive informations from sccm i think
Ccmsetup.exe /mp:sccmserver SMSSITECODE=XXX SMSSLP=sccmserver DNSSUFFIX=dnssuffix
on the client, clicking in Site tab and configure settings, the site code is there, clicking in Find Site returns error saying that cant find the site. on the locationservices log i'm getting
Policy prevents failover to WINS for lookup
Unable to retrieve AD Site membership
No Location reply received from xxxxxx.domain.xxx
No location reply received from xxxxxx
thks in advanceIt should work just by:
Copy the client files (the whole directory) to the workgroup computer (c:\tmp\Client)
Run ccmsetup.exe /source:c:\tmp\Client SMSSITECODE=PRI SMSMP=sgcmcen.cm12lab.com DNSSUFFIX=CM12LAB.COM
Examine %windir%\ccmsetup\logs\ccmsetup.log for more information if the client doesn't install at all, possible causes might be corrupted WMI, lack of BITS (if running Windows 2003 server).. in these cases you could run WMIDiag (http://www.microsoft.com/en-us/download/details.aspx?id=7684)
to get more info on the errors and how to fix them.
Couple of checks:
DNS is working correctly both ways? Workgroup machine can find ConfigMgr server and ConfigMgr server can find workgroup machine by name? You can test this by running
nslookup <target.fqdn> on both
Workgroup computer is in the boundary / boundary group that has a site server assigned -
Support for Internet based client Management - SCCM 2012
Hi There,
My Company wants to go for Internet based client Management in SCCM 2012 SP1 R2 and here is the design I'm proposing. I'm getting a bit confused at one point and need suggestion....
Everything would work on HTTPS ( PKI Certificate based )... LAN and Internet.
1 Primary ( with non-client facing roles installed ) on LAN with two site systems.
- One Site System configured for INTRANET support only with MP, DP and SUP -> To support LAN users ( Allow
Intranet-only connections )
- One Site System configured for INTERNET support only with MP, DP and SUP -> To support Internet users ( Allow
Internet-only connections )
The INTERNET facing site system is in DMZ network connected to parent Primary via Firewall.
We want internet clients to talk to ONLY DMZ SCCM Site System and no connection to corporate LAN. We cannot open any ports for internet based clients to LAN.
If this is the supported scenario, then why we need to put the Internet FQDN in the Primary server Site System property. This server would not be available to internet. It should only be my DMZ SCCM server client should connect for MP, DP and SUP and only
this DMZ server should be accessible to client over internet.
Also, what least ports should be opened between :
- Parent Primary and its internet facing site system kept in DMZ
- DMZ Site system and internet clients.
Thanks in advance for your suggestions.
SamThe FQDN has only to be specified on the Internet facing site system. You can leave this field blank on the primary site Server.
Ports to Open:
Internet --> DMZ Site Server:
TCP Port 443
TCP Port 80, if Fallback Status Point is installed
DMZ Site Server --> Primary Site:
TCP 135, 49152-65535
TCP 445
TCP 135, 24158 (fixed with
http://msdn.microsoft.com/en-us/library/bb219447(v=vs.85).aspx )
TCP 80, 443
If you have some other roles installed, please consult this page:
http://technet.microsoft.com/en-us/library/hh427328.aspx
Cheers,
Thomas Kurth
Netree AG, System Engineer
Blog:
http://netecm.netree.ch/blog | Twitter:
| LinkedIn:
| Xing:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
Best practice for client migration from SMS 2003 to SCCM 2012 R2?
Can anyone advise what the most recommended method is for migrating SMS 2003 clients (Windows 7) to SCCM 2012 R2?
Options are:
1. SMS package to deploy ccmclean.exe to uninstall SMS 2003 client. Deploy SCCM 2012 R2 client via SCCM console push.
2. Simply push SCCM client from console installing over existing SMS 2003 client.
I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
3. Use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean and then install the SCCM client.
Appreciate any feedback. Thank you.Hi,
>>I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
I haven't seen any official document records the option 2 method. There is only upgrading from SCCM 2007 to SCCM 2012 directly.
I think you could use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean.exe. Then use SCCM 2012 to discover these computers and push clients to them.
Best Regards,
Joyce
Maybe you are looking for
-
My phone has stopped being recognised by my computer help??
It's been a couple of days since I've synced my iPhone 5 and I've just tried and my pc doesn't even recognise my phone. I've tried rebooting my phone, using different USB ports and I've reinstalled iTunes but still no joy. I'm running windows 8 on my
-
Mp3 play but video not play my phone my Email add. [email protected] Moderator's note: E-mail address was removed. Please don't publish your personal contact information on a public forum.
-
how to put continuos (desired format) of dates in numbers spreadsheet and how to do it? please reply asap i need it..
-
K430 with OneKey 4.0 has no option to make a recovery disk
What are my options on this machine to make a recovery disk and backup in case of a hard drive failure? Also noticed OneKey 4.0 won't recognize external hard drives greater than 1TB. Why? Solved! Go to Solution.
-
Firewire Audio interface problems in Windows XP
I am a happy user of boot camp with Windows XP and have up til now not had any problems. I have two firewire devices, one hard drive, one audio interface. The hard drive has both firewire 400 and 800 connectivity and works perfectly using both. But I