first install of unity. All was working fine until we tried to create a user. Created what we thought was a new user but since then we hav'nt been able to get back in to unity admin - keep getting the following message:<br>'class of service prohibits you from accessing the unity web pages'.<br>It seems we made a change to our service account rather than created a new user.<br>have tried to create a new unity service account as per article in this forum but stll can't get in. Is this a reinstall?<br><br>
You shouldn't need to reinstall... there are several methods to gain access to a system in this state.
1. Try to use the Example Administrator account. Assign your Nt account to the Example Administrator Exchange account and get in that way. You may have to wait for a little while after doing the assignment such that the directory syncronizer picks up the change.
2. Failing that you can use ConfigMgr found under the \commserver directory to rebuild the default database which includes remaking the Example Administrator account, rebuilding the default COS objects etc... this also includes rebuilding the opening greeting so if you have a custom opening greeting recorded you will lose it. Here's a link that explains how to use ConfigMgr (you only need to run the DOH configuration scripts again).
3. you can use DohPropTest to force an admin COS assignment to any mail user in the system. You will need a password to do this so you will need to call TAC if you get this far. Normally #1 or #2 will do the trick for you.
does it say "too many sessions open already" perhaps? If you open and close the SA without using the "logout" link in the lower left you'll "burn" an active web session for X minues (20 by default). If you have 5 sessions active we wont let another SA session open and you'll get this message.
I'm guessing if you wait around for a bit, the sessions will clear and you can get it then. If not, try forcing the IIS Admin service to cycle (this will also stop the FTP and WWW services which you'll need to start after cycling IIS).
Unity 3.0 solves the session burning issue since it requires IE 5.5 which has better handling of session destruction (i.e. it lets us do some cleanup before it pulls the rug out from under us like IE 5.0 does) which we took advantage of. But in 2.x, always remember to terminate your SA session by hitting the "logout" link.
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.