You have a couple of options for dealing with wanting to open the AA while logged into the domain as an account other than the one associated with your Unity account.
The first option is pretty straight forward and is what TAC normally reccomends for this type of thing. Setup their IE interfaces such that they are prompted to authenticate when they attach to the AA... They'll get a dialog asking for their name, domain and password which will be the login name for the domain Unity is installed in and they should get in. Yeah, this is a little annoying and they'll have to know a separate login name and PW but it works and is how this issue is documented for work around.
The second option is a little hairier but might be more to the customer's liking (but more work for you). You can create associations between their domain account (the one they log into the domain with) and their voice mail account you created. You can use the GrantUnityAccess tool to do this... You pass in the Domain\Alias for the login account and then the alias of the subscriber you want that domain account associated with in Unity. It's a command line tool and can be scripted, you can find it in the \commserver root directory and if you run it it'll spit out all the options for it. For instance I created a JLINDBORG account in CORPDOMAIN and a VM-JLINDBORG account in UNITYDOMAIN. I made the VM-JLINDBORG account a subscriber in Unity and then logged into the CORPDOMAIN domain as JLINDBORG. Attempting to open the web page fails as expected. Then on the local Unity server (in UNITYDOMAIN) run:
"GrantUnityAccess -u CORPDOMAIN\jlindborg -s vm-jlindborg"
and you should be able to get into the AA for that user without having to manually authenticate.
This is intended for help desk type applications that require a single account to have SA admin access to many Unity boxes on the same network but would work for this as well.
