Setup AD integration With SGD

Question

I'm in the process of setting up a test for use of SGD within our organisation. I want to get rid of our current remote access procedure of using PPTP/VPN clients and give the user a complete browser experience. As part of this test I have a Solaris 10 VM running v4.20.983 of the SGD software. My question is now, is there a step by step guide I can follow to configure SGD with Windows 2003 AD integration so I can present remote users with a Windows Terminal Services session within a browser. This session would be a full desktop and not just a remote application?
TIA.

Answer 1

Many thanks for the clarification. Here's the last portion of the jserver log file with some warning errors etc:
2010/02/03 18:52:39.430     (pid 13528)     server/ldap/warningerror     #1265223159430
Sun Secure Global Desktop Software (4.5) WARNING:
Directory Service Error from host
Active Directory(ldap://172.16.0.5:3268::wm-exchange1.wmnet.local[/172.16.0.5]:[Down])
Message:
Socket timed out: connect timed out
SGD will retry this directory server and if another failure is detected, SGD will failover to the next available directory server.
To troubleshoot this error:
- Verify that this host is contactable.
- Verify that the LDAP service is available.
2010/02/03 18:52:39.430     (pid 13528)     server/ad/warningerror     #1265223159431
Sun Secure Global Desktop Software (4.5) WARNING:
Failed to connect to the global catalog
Active Directory(ldap://172.16.0.5:3268::wm-exchange1.wmnet.local[/172.16.0.5]:[Down]).
Reason
Socket timed out: connect timed out
Global catalog
Active Directory(ldap://172.16.0.5:3268::wm-exchange1.wmnet.local[/172.16.0.5]:[Down])
cannot be used to retrieve data from the forest.
To help troubleshoot this warning,
- Verify that this global catalog is available on the network.
- Verify that SGD can resolve the global catalog's hostname via DNS.
- Verify that SGD can connect to port 3268 on the global catalog.
- Verify that this server is a global catalog for the forest.
2010/02/03 18:52:54.640     (pid 13528)     server/ad/warningerror     #1265223174640
Sun Secure Global Desktop Software (4.5) WARNING:
DNS lookup failed to find wm-sgd1
Reason:
javax.naming.ServiceUnavailableException: DNS server failure [response code 2]; remaining name 'wm-sgd1'
wm-sgd1
cannot be used by SGD.
Make sure the DNS server contains a valid entry for this host.
2010/02/03 18:52:54.640     (pid 13528)     server/ad/warningerror     #1265223174641
Sun Secure Global Desktop Software (4.5) WARNING:
Active Directory service discovery failed
Failed to get IP addresses for the peer DNS name
Current state:
Looking up Global Catalog DNS name: _gc._tcp.WMNET.local. - HIT
Looking for GC on server: Active Directory(ldap://172.16.0.5:3268::wm-exchange1.wmnet.local[/172.16.0.5]:[Up]) - ERROR
Looking for GC on server: Active Directory(ldap://192.168.1.200:3268::wm-office1.wmnet.local[/192.168.1.200]:[Up]) - HIT
Checking for CN=Configuration: DC=WMNET,DC=local - MISS
Checking for CN=Configuration: CN=Configuration,DC=WMNET,DC=local - HIT
Looking up domain root context: DC=WMNET,DC=local - HIT
Looking up site context: CN=Sites,CN=Configuration
Searching for sites: (&(objectClass=site)(siteObjectBL=*)) - HIT
Looking up addresses for peer DNS: wm-sgd1 - HIT
Failed to discover Active Directory Site, Domain and server data.
Make sure the DNS server contains the Active Directory service
records for the forest. Make sure a Global Catalog server is available.
2010/02/03 18:52:54.645     (pid 13528)     server/ldap/warningerror     #1265223174645
Sun Secure Global Desktop Software (4.5) WARNING:
LDAP call failed:
null lookupLink-.../_ldapmulti/forest/("DC=WMNET,DC=LOCAL")
Call took 35386ms.
Reason:
javax.naming.NameNotFoundException: Failed to get IP addresses for the peer DNS name.
The call to the directory server failed.
Check the operation was correct, the LDAP configuration is valid, and the
LDAP server is still running.