From Smart Office 10.0.3 all settings files are located in the GDBC database instead of the file system. Sometimes an administrator needs to change a setting without opening the Smart Office client. In Smart Office 10.0.5 there is an external tool called SettingsTool.exe that can be used to access the settings files on the server. Continue reading
When using Smart Office in many office locations it can be a good idea to create a Smart Office installation point at every location, especially if the network bandwidth between the locations is slow. Continue reading
In LSO 9.1.3 we moved the server to the Grid. There is a discovery service for LSO SDK applications (features) and Mashups that have a need to communicate with a Lawson Grid application. The discovery service reduces the configuration that needs to be added to the feature or mashup, e.g. no System Profile information needed in the manifests. This also means that there will be less work for the installer/administrator to configure installed applications. The discovery service can be used to retrieve the base URL to the Lawson Grid Application. Continue reading
As you all know Smart Office is installed with the help of Lifecycle Manager (LCM), but do you know that fixes to Smart Office are delivered through Customer Correction Self Service (CCSS) and downloaded and applied through the LCM client? Continue reading
The display name in Smart Office is used in a couple of places. First of all it shows the logged in user at the top of the Canvas. This post describes the display name and it’s usages and configuration.
In Smart Office 10.0.4 settings files and pre-defined widgets definitions have been moved into the GDBC database instead of reside as files on disk. At the same time as using a database instead of files increases the possibilities on new functionality in Smart Office it also reduces the simplicity of viewing configuration files.
With the new Import/Export Manager administration tool it is possible to export all settings files, pre-defined widget definition file and also M3 and S3 links files (even if they are still located in the file system). Continue reading
The content of this article will describe changes made to Smart Office 10.0.4 from an installation and configuration view. Continue reading
In version previous to Smart Office 10.0.4 the possibility to connect Smart Office settings to users or groups of users existed but had to be done through Active Directory with group polices. Adding new group polices can be a bit tricky and sometimes the trickiest part is to get access to the Active Directory it self.
In Smart Office 10.0.4 there is a new way that let you create different settings values and connect them to user(s) and/or group(s) of users. Continue reading
Why is it so hard to get Lawson Smart Office to work well with a desktop virtualized environment? I will try to answer that question is this article.
What is a desktop virtualized environment? You can read one definition on Wikipedia, http://en.wikipedia.org/wiki/Desktop_virtualization but explained briefly it is an application that makes it possible to execute other applications like they where installed locally but in fact they are executed on a server somewhere and only the “screen” is transferred to the client machine. That means no code from the application is actually executed on the client machine. Continue reading
Lawson Smart Office is using the Microsoft technology ClickOnce when installing on client machines. ClickOnce have some advantages and some disadvantages compared to other client installation techniques.
- Easy to install
- Automatic client updates.
- Possibility to have side by side installations of different versions of Smart office.
- Always installs as per user and never for all users on a machine. Continue reading