I have a question on a large implementation I'm doing next week. Customer is switching over to Unity server and will have about 15 unified messaging clients. The other 900+ users will be voice mail only. I'm trying to decide if I want to integrate with their existing Exchange site (and clutter their GAL), or set this up on a separate domain/exchange org.<br><br>If I set this up on a separate exchange organization, is there a way to accommodate the unified messaging clients (SMTP forward of email)? Or should I integrate with their existing exchange box and use Roger Newton's method to hide these 900+ boxes from the GAL?<br><br>Thanks, and hope this makes some sense.<br><br>Brent<br><br>
Actually, the best solution is to hang tight (we're talking days here) for Unity 2.4.6. We support hiding users in the directory in that build (which is huge!). It requires Exchange SP4 be applied, but you can then integrate with their existing Exchange install and select to hide the voice mail only users (via the Exchange administration console) such that they wont show up in the GAL.
One more question. Importing users from Reparte. I've exported the users to a extensio.rpt file, used the export utility to format this into a CSV file. Today, I distilled this file, matching existing users in Exchange to the CSV file. I removed the existing users from the CSV file and ended up with a list of voice mail only users ready to import. (Here's the question). Is it possible with the stand-alone import utility to create these users without creating NT domain accounts? I don't see how unless there is a header field that the import utility would see and skip the domain acct creation.
I've also stripped all the symbols (-/.$&) from the export list. Repartee is a little more liberal than Unity on Subscriber names. Now checking for possible duplicate NT aliases.
Unfortunately there's no way to create voice mail only users without NT accounts using the CSV import... there's an option to do this from the SA when creating new users but not for the stand alone import.
you'll have to remove those links manually if you don't want them to have NT accounts.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.