This content has been marked as final. Show 4 replies
Please check the service properties for the PortalDesktopService at the SubOrganization and User level. The properties for DefaultContainer and DesktopType should match the values you have at the root level. You may also be prompted to create a service template for the desktop service. Just click yes if prompted in the amconsole.
Thanks for the response.
The problem is when I created the sub-organization, the display profile for that sub-organization is empty. How many ever sub-organization I create the display profile is empty. The display profile for the Organization that is the root suffix appears when I view it using the Edit tab on the Portal Server Configuration under Service Configuration.
Also when I create a user under the root suffix, that user's display profile also is empty. I am not sure why this behavior. Please let me know if there is any way to get this working.
What you are describing is the expected behavior. The display profile does not get populated automatically. You can create a display profile for you sub organization, or you can change the COS Priority to HIGHER. This will allow your sub organization to have a lower priority than the root suffix, hence your users in the root suffix will use the dp from the root.