A follow-up to last weeks post...
From my co-worker:
"Last week I blogged on the deployment of the Disconnected Web Client.
Today's post discusses the issues that could arise on the Installation
of the Disconnected Web Client. If you have deployed in Application
Architect and ran the sync server, then the remote users should be able
to run sync, apply the changes, and open the personal web server and
then the SLXClient. They are now using the Disconnected Web client
against a remote database. They will need to sync back to the
production server. What happens when the SLXClient does not open on the
remote computer? Well it could be that the deployment did not put the
required files in the slxLogs\PortalDeployments folder. If that folder
is empty and the SLXClient is grayed out on the remote then run the
Disconnected Web Client deployment again, run the sync server again and
have the remote run sync as well. If the remote ran a sync and the
SLXClient attempts to open and returns an error "Could not load file or
assembly 'Sage.SalesLogix.Web', or one of it's components. then something
has not installed correctly. We compared the folder structure on two
different remote computers and found that the SLXClient Bin folder was
missing on one system. To correct, copy the entire SLXClient folder
from the working computer to the other system and edit the
connection.config file to point to the correct system. Reinstalling and
repairing the installation did nothing."
-Brianna