So let me set the scenario best I can. We have 1 site with 2 servers the main server running 2006 with the latest hotfix rollup applied. The other is an IBCM external management point server. What we have noticed is the following behavior
1. Machines stop showing up all together within the Configuration Manager even thought hey have the agent installed and it is pointed correctly.
2. After a discovery is ran (Against AD) the machines will show back up but show they have never had an agent installed
3. If you reinstall the agent the machines will go away again.
4. Using direct rules to build a collection and then deploying an application the application is being pushed out to multiple computers that are not within the collection. We know they are being pushed out because the application we are installing as a dashboard that shows computers installed it etc
5. A computer that is supposed to be in the collection disappears and is replaced by another one that is NOT in the direct rule for the membership.
6. The computer displayed incorrectly in the collection is on a different subnet and it shows the incorrect primary user as well as the incorrect currently logged on user
Any help/guidance etc would be amazing. This is a new environment we have been standing up over the last month so it is very possible we might have missed something etc
1. Machines stop showing up all together within the Configuration Manager even thought hey have the agent installed and it is pointed correctly.
2. After a discovery is ran (Against AD) the machines will show back up but show they have never had an agent installed
3. If you reinstall the agent the machines will go away again.
4. Using direct rules to build a collection and then deploying an application the application is being pushed out to multiple computers that are not within the collection. We know they are being pushed out because the application we are installing as a dashboard that shows computers installed it etc
5. A computer that is supposed to be in the collection disappears and is replaced by another one that is NOT in the direct rule for the membership.
6. The computer displayed incorrectly in the collection is on a different subnet and it shows the incorrect primary user as well as the incorrect currently logged on user
Any help/guidance etc would be amazing. This is a new environment we have been standing up over the last month so it is very possible we might have missed something etc
