I had created another question a little time back (https://www-secure.symantec.com/connect/forums/sep-manager-deployment) and am now in the process of setting up one SEP manager to control policy for multiple sites, using group update, network location awareness and set up IIS to handle the client install. I have all this set up. NLA is driving me nuts. I have a "Default Group" under My Company. I deploy the sylink.xml file using this group, then move clients to other policy groups as needed, so that I can control when the updated client will deploy. Works fine in my initial site.
In my second site, I have all of 4 computers. I set up a seperate group, and deployed my default group sylink. Somehow, the client is automatically going right into the group I intend to move them into. Fine, but only 1 machine shows! If I reboot that machine and hit refresh in the console, I see a different machine, and so on. Under client information, I see one hostname, which changes, depending on which client machine is running, but see 1 contant IP address, and the user who is logged into that computer with that IP address.
I decided to try importing an AD OU with these machines and set policies to the OU as opposed to using a Group. Now I see all 4 machines, 3 of them "Offline", and 1 exhibiting the same behavior when I was using the group - computer name changing based on which client connects first.
I read one other lengthy post about another admin having clients show offline, and shrinking the DB was the fix for that situation. I tried that, no go. I'm out of solutions. Ready to scrap the concept of 1 manager, and placing 1 manager in each site.
Joel