Well... the account you installed Unity under should have been made a subscriber during setup and added to the Administrator class of service. You can't import someone who's already a subscriber. I suspect maybe you imported the "Unity Messaging System" account... that doesn't hurt anything, but normally you wouldn't want to do that. An import cannot change properties on an existing user...
If you accidentially changed the COS of the administration account you should just be able to fire up the SA as another administrator and change their COS on the profile page.
If you simply don't have any users associated with an admin COS any longer, the easiest way to get around this is to fire up the Exchange administrator and associate the NT account you're logged in as with the "Example Administrator" Exchange account. By default we don't create an NT account for this guy... this will let you into the system so you can patch up the COS reference.
If your deleted the admin COS iteself and there isn't another administrator cos in the system... well... that's a problem. You'll need to contact support and they can use some tools to create an admin COS for you and associate a user with it so you can get into your system. The SA does prevent you from deleting a COS if there are folks associated with it but now and again this does come up.
Jeff Lindborg
Unity Product Architect
Active Voice
jlindborg@activevoice.com
http://members.home.net/jlindborg
