As LinusH said, you can set up IWA to be compatible with your Unix servers.  See this document: http://support.sas.com/documentation/cdl/en/bisecag/63082/HTML/default/viewer.htm#n1d1zo1jsf2o0en1ehu4c4simfky.htm   It's nice if users have to change password every 30 days or so, but I think setup is more complicated and likely involves third-party software (like Quest Authentication Services).   IMHO, it's alot easier to set up PAM authentication.  Users would have to change password in their EG profile when they change their network password, though. ... View more

My pleasure! Good luck! ... View more

It sounds like it's working properly. Can you validate the Workspace server in SMC? Also, I'm checking my Object Spawner files and here's what I found... The original "ObjectSpawner.sh" script was configured with the actual hostname of server on which we performed the installation/configuration of the app server (i.e. compute01.mydomain.com). However, our SAS consultant/installer had me make a backup of this file, then modify ObjectSpawner.sh. We replaced every reference of the actual server name with "$HOSTNAME". Then we updated "ObjectSpawner_usermods.sh" so had this line: USERMODS=" -dnsmatch $HOSTNAME.mydomain.com -conversationport 8599 $JREOPTIONS" Note that "mydomain.com" should be changed to whatever is applicable for your organization. Also note that this works for us because we are using a shared file system between all the nodes. Our config directory is shared. Hope this helps. ... View more

I'm not sure if you need the "$HOSTNAME". I don't recall if we added this or not.     Are your workspace servers configured to be grid-launched?  You may not actually have a problem.  You should be able to check the object spawner logs to see if it's attempting to spawner servers on the other nodes.  Depending on load-balancing settings you have it the servers may not spawn on other nodes until after a certain threshold is met.     ... View more

I'll have to check when I get back to work tomorrow, but these are the options that SAS Tech Support provided me when I had a similar issue. ... View more

Unless 8599 is specifically being used for some other service 8599 should work. The object spawner itself typically listens on port 8591 by default, as is shown in your grep output, but I think once the object spawner receives a request there is then additional communcication between LSF and other object spawners until it decides which grid node on which to start the workspace server. All that to say, I think anywhere between 8592 and 8599 should work unless you have other services using those ports ... View more

It should install automatically, assuming it's in your plan file and license (though I think it's always bundled with EBI). ... View more

Glad you got it fixed! ... View more