The affiliation is based on the image owner, not the user making the reservation. Affiliation id 1 is "Local", so admin or some other local user you created is probably the image owner. If a product key is set for the image owner's affiliation it will use it. If not, it will try to use a product key for the Global affiliation. If neither is set then activation will fail.
There are a few reasons it's based on image owner... The computers are activated when they are reloaded which is not necessarily when a user makes a reservation. This is mainly because the activation commands are pretty slow. It would slow down the process for the user if it is activated when a reservation is made. You may also have an image reloaded and sit for an extended period before a reservation is assigned to it. This could cause the activation grace period to expire and the computer would go into reduced functionality mode. In most cases, images are rarely shared between affiliations so the image owner's affiliation is the same as the reservation user. -Andy On Thu, Oct 11, 2012 at 2:40 PM, Yannick Charbonneau <[email protected]> wrote: > Hi All, > > > > We have now built a Windows 7 Base Image, we have configured 2 affiliations > with Volume Keys. > > > > When users make reservations for Windows 7, the registration always seems to > fail. > > > > If I put in a key for the Global Affiliation, then it works. But I want to > use the key per affiliation. > > > > It appears to always want to use affiliation=1. I checked my users and they > have varying affiliations. > > > > Am I missing something? > > > > Thanks > > > > Yanik
