Search the Community

Currently using Config manager 2012 and clients are running windows 7 enterprise 64bit. The new computers have been created in AD via a powershell script and imported into config manager. Computers have been allocated into collections to specify which software they receive. Within these collections there are collection variables assigned that are used within the task sequence to determine if software in installed or not. when we start imaging we enter the computer name that matches the name within Config manager. Problem: Whenever the new computers are imaged they do not recognize the collection variables set so the software does not install. Then once the client registers with the config manager server it removes it is removed from all collection that it was previously allocated. Can clients that do not have an active status hold a collection variable? Why are they being removed from collections when the Config manager client registers with the server? How can this problem be resolved without imaging the same computer twice and forcing a refresh of the collection memberships?? Can you force a client heartbeat discovery during a task sequence before software is installed?? Any other suggestions on solving this problem would be greatly appreciated How do i get unknown computers to receive collection variables if they call into collections?