Hi Forum<br><br>When trying to access SAWEB from a PC that doesn't belong to the domain, one are even so often requested to do a new logon. <br>How can that be prevented, or how does one do a correct logon when the PC one are using doesn't belong to the same NT domain as the unity server.<br><br>Peter Lillelund<br><br>
IE will try to use windows authentication to access protected areas. If the account you're using to get into the SA doesn't have a matching domain account (I think the passwords also have to be the same), IE will prompt you for authentication. Unity isn't even in the picture yet -- IIS knows the web page you're trying to view is protected, and it doesn't know who you are yet, so it asks you. A possible solution would be to create matching domain accounts in Unity's domain. However, there are security reasons for not doing it this way, so it's a decision for the domain admin to make.
Another partial work around (although you'll still be asked to authenticate the first time you load a page with the media master control on it) is to have the Unity domain trust the domain with your users in it. Not ideal...
in general the best practice is to have Unity installed into the same domain your users are signing into. If there's some reason why this is undesirable, then users will simply have to authenticate when they attach to the SA. This doesn't have anything to do with Unity, it's Windows challange and response security. You can't hack up the SA/AA web pages to skip authenticating either (I've been asked).
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.