Hello, I am currently seeing a limitation of SCCM 2007 with the number of IPs assigned to a server. The number seems to be around 1,500 addresses. Can anyone else validate this or know of a way to work around this? SCCM sees the servers; it just spends so much time in WMI getting all of the IP info and then dies before it can send the data back to the Parent SCCM Server. Any information would be greatly appreciated! Regards, YarrokonRegards, Yarrokon

what wmi query are you referring to? heartbeat? hardware inventory? or do you mean for boundaries?Standardize. Simplify. Automate.

Sherry, Thank you for your response. We have a server type where we have a large number of internal IP's on them. They all work with SCCM just fine; reporting in, getting windows updates, having jobs pushed to them until they reach around 1,500 IP's. At this number, everything STOPS, for patching they are now showing up as Compliant State Unknown, SCCM does not see that they have the agent installed, even though it is installed and works just fine. We remove a bunch of the IP's and it starts communicating with SCCM again. So, we know the issue is IP related and is around 1,500 address's on a NIC, but we are attempting to find a way around this. We are using SCCM 2007 R2 (We are also prepping for SCCM2012, but would love to fix this). We have noticed WMI using a lot of mem / resources when attempting to "check-in" to the parent server. We can only assume is going through the IP list and then eventually times out or dies. We are not seeing any WMI or SMS errors within the System or Application event logs either.Regards, Yarrokon

I can honestly say this is a new one for me, 1500 IP addresses on one server! Wow.. Your best bet, particularly if you can reproduce the error, is to contact CSS (MS support) directly and work with them on the error. If it is an error with the CM07 (or CM12) then they are the only ones that can fix this for you. http://www.enhansoft.com/

Sherry, Thank you for your response. We have a server type where we have a large number of internal IP's on them. They all work with SCCM just fine; reporting in, getting windows updates, having jobs pushed to them until they reach around 1,500 IP's. At this number, everything STOPS, for patching they are now showing up as Compliant State Unknown, SCCM does not see that they have the agent installed, even though it is installed and works just fine. We remove a bunch of the IP's and it starts communicating with SCCM again. So, we know the issue is IP related and is around 1,500 address's on a NIC, but we are attempting to find a way around this. We are using SCCM 2007 R2 (We are also prepping for SCCM2012, but would love to fix this). We have noticed WMI using a lot of mem / resources when attempting to "check-in" to the parent server. We can only assume is going through the IP list and then eventually times out or dies. We are not seeing any WMI or SMS errors within the System or Application event logs either. Regards, Yarrokon This is pretty rare, most customers have nothing like that amount of IP's on one NIC. What OS do you see this in, W2K8, W2K3? Assuming WMI is entirely stable and has the latest rollups applied etc ... then you've butting up against what seems to be a WMI performance ceiling. Whether this is influenced by your hardware, or WMI's configuration I wouldn't know. If you have a second NIC already installed (server class, I expect dual or quad NIC) then as an easy test you could keep 1,500 IP's on NIC1 and add 1 IP to NIC2 then see how it all performs. If multiple NICs work, its probably due to the working sets in memory for WMI that were causing the issue. There are WMI optimisations you can make in the registry, but unless you really know what you are doing I wouldn't recommend it. If I had a support contract with MS and could raise a CSS ticket, I would go that route to get a proper fix for this.

It could be possible that the resulting inventory file on those servers is too large. The limit, by default, is 5 MB. You can increase this size by making a registry edit. HKLM\Software\Microsoft\SMS\Components\SMS_Inventory_Dataloader\Max MIF SizeNicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile

Out of curiosity, why so many IPs on one server?Nicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile

We are using Windows 2008 SP2 with a dual NIC system in teaming mode. I actually wrote a bat script to add / remove the IP's to the system. There are no concerns with making changes in the registry for WMI, its not hard to replace one of the systems if it gets nuked, takes about an hour.Regards, Yarrokon

Searching some of the other logs (I'm not the SCCM guy here, he is gone...) I do see that the Inventory Logs are picking up data and checking in just fine, but do see a number of items I think should not be having issues. I ran a hardware check-in from one of the problem servers, opened up the inventory log and pulled out all of the warnings / errors I could see in Trace32. An educated guess would make me think that "Collection: Class "Win32_PatchState" does not exist out." would be my issue... Collection: Class "Win32_TSIssuedLicense" does not exist out.Failed to get IWbemService Ptr for \\localhost\root\Microsoft\appvirt\client Namespace: 8004100EFailed to enumerate instances of Application: 8004100ECollection: Class "SMS_ActiveSyncConnectedDevice" does not exist out.Failed to get IWbemService Ptr for \\localhost\root\vm\VirtualServer Namespace: 8004100EFailed to enumerate instances of VirtualMachine: 8004100ECollection: Class "Win32_PatchState_Extended" does not exist out.Failed to get IWbemService Ptr for \\localhost\root\Microsoft\appvirt\client Namespace: 8004100EFailed to enumerate instances of Package: 8004100ECollection: Class "Win32_ServerComponent" does not exist out.Collection: Class "Win32_PatchState" does not exist out.Collection: Class "Win32_ScanPackageVersion" does not exist out.Collection: Class "Win32_TSLicenseKeyPack" does not exist out.Collection: Class "Win32_Vulnerability_Detail" does not exist out.Collection: Class "Win32_Vulnerability" does not exist out.Collection: Class "SMS_ActiveSyncService" does not exist out.Inventory: 14 Collection Task(s) failed.Inventory: Successfully sent report........ Looking at your registry entry, I can not determine if the value data is in bytes?Regards, Yarrokon

Ok, going to do some more reading, TY. I knew some of the errors were not realted to what the system was but I did have a concern about the Patch State and Scan Package warnings.Regards, Yarrokon

This should give u enough information to TroubleShoot the issue that you are encountering. http://social.technet.microsoft.com/Forums/is/configmgrsum/thread/a34d4ae7-e9d9-4f26-abf6-c1e31a26567e

We are using Windows 2008 SP2 with a dual NIC system in teaming mode. I actually wrote a bat script to add / remove the IP's to the system. There are no concerns with making changes in the registry for WMI, its not hard to replace one of the systems if it gets nuked, takes about an hour. Regards, Yarrokon I was in WMI recently tinkering, this was why and it may help you out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx Go on, tell us what you have 1,500 IP's on a bonded NIC for? :-) It sounds exciting.

This should give u enough information to TroubleShoot the issue that you are encountering. http://social.technet.microsoft.com/Forums/is/configmgrsum/thread/a34d4ae7-e9d9-4f26-abf6-c1e31a26567e Hi Arvind, I would like to ask kindly how this posting is related to the OP problem?

We are using Windows 2008 SP2 with a dual NIC system in teaming mode. I actually wrote a bat script to add / remove the IP's to the system. There are no concerns with making changes in the registry for WMI, its not hard to replace one of the systems if it gets nuked, takes about an hour. Regards, Yarrokon I was in WMI recently tinkering, this was why and it may help you out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx Go on, tell us what you have 1,500 IP's on a bonded NIC for? :-) It sounds exciting. NOM, NOM, NOM... That was a good read, TY!Regards, Yarrokon

We are using Windows 2008 SP2 with a dual NIC system in teaming mode. I actually wrote a bat script to add / remove the IP's to the system. There are no concerns with making changes in the registry for WMI, its not hard to replace one of the systems if it gets nuked, takes about an hour. Regards, Yarrokon I was in WMI recently tinkering, this was why and it may help you out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx Go on, tell us what you have 1,500 IP's on a bonded NIC for? :-) It sounds exciting. NOM, NOM, NOM... That was a good read, TY! Regards, Yarrokon Thought you'd get a rise off that and I hope it helps!

We are using Windows 2008 SP2 with a dual NIC system in teaming mode. I actually wrote a bat script to add / remove the IP's to the system. There are no concerns with making changes in the registry for WMI, its not hard to replace one of the systems if it gets nuked, takes about an hour. Regards, Yarrokon I was in WMI recently tinkering, this was why and it may help you out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx Go on, tell us what you have 1,500 IP's on a bonded NIC for? :-) It sounds exciting. NOM, NOM, NOM... That was a good read, TY! Regards, Yarrokon Did this fix the issue for you Yarrokon?

We have provided a ton of data to Microsoft, and though they don't have a resolution they do believe it is a possible error with WMI/SCCM 2007 as they do see some of the issue in 2012, but not the exact same issue. The fix for 2012 does not fix 2007, the answer at this time seems to be upgrade to 2012 and make the necessary WMI changes, we will see. Thank you all so much for your help and links, I've learned much in this thread.Regards, Yarrokon

We have provided a ton of data to Microsoft, and though they don't have a resolution they do believe it is a possible error with WMI/SCCM 2007 as they do see some of the issue in 2012, but not the exact same issue. The fix for 2012 does not fix 2007, the answer at this time seems to be upgrade to 2012 and make the necessary WMI changes, we will see. Thank you all so much for your help and links, I've learned much in this thread. Regards, Yarrokon And learn we did too, thanks for coming back and congratulations ahead of time for considering the move to CM2012 ;-) It is so worth it.