Citrix recently released desktop server v1.0. I finally got some time to try it.
class="MsoNormal" style="margin: 0in 0in 0pt">I get a general error the first time I tried over RDP session. Then I tried again. This time I installed it over a RDP console session (mstsc with /console option). And the installation worked. I am not sure if it is a problem with installing it on regular RDP connection yet. But it is safer to install on a console session anyway.
class="MsoNormal" style="margin: 0in 0in 0pt">The CDS team did a great job of simplifying the single server install. The install only asks some simple questions and the rest is fully automated including Database and web interface installs. It is much easier than desktop broker installation.
class="MsoNormal" style="margin: 0in 0in 0pt">One thing to note if you install over RDP session, you may not be able to RDP to it after the server is rebooted if you haven configured a license server yet. I had to finish the installation at console.
class="MsoNormal" style="margin: 0in 0in 0pt">Also the admin guide and readme documents can be downloaded on line only. You can find the links to such documents on auto run screen. Please see this blog post for more details about this topic. This may be the start of new way of delivering documents.
class="MsoNormal" style="margin: 0in 0in 0pt">http://citrixcommunity.com/blogs/techpub/archive/2007/03/09/Accessing-Citrix-documentation-_2D00_-your-thoughts.aspx
Now install was complete, I tried to log in to web interface and authentication failed. The event log shows the following errors: "The servers sent HTTP headers indicating that an error occurred: "401" "Unauthorized". This message was reported from the XML Service at address "http://:80/scripts/wpnbr.dll [com.citrix.xml.NFuseProtocol.RequestCapabilities]". This XML Service could not be contacted and will be temporarily removed from the list of active services. [Log ID: a89f530d] All of the configured XML Services for farm "Farm1" failed to respond to this XML transaction. [Log ID: 3cfa1d2d]" Looks like XML service problem, doesn?t it? Fortunately I have access to my friends in engineering team. Someone helped me figured it out. Turned out I need to add local user groups read/execute permission to c:\inetpub\script directory. I am not sure how it got into this state yet. I hope it is just me who is experiencing this problem. But I?ve reported this problem to engineering team.