Learn Dynamics 365 Finance and Operations(Axapta)

There seems to be quite some vagueness when it comes to Ax and AOS clustering. A few statements to (hopefully) clear things up a bit: Single AOS The simplest configuration is an Ax implementation with one single AOS server. Extra AOS servers can be added in scenarios where you want to increase availability or scale up the Ax environment to handle a larger number of users/connections. Several possibilities from that point on: AOS side by side By default multiple AOS's in a single Ax environment will exist side by side. They do know about each others existence, sync their caches, try not to hamper each other too much,  … A user connects to a specific AOS as defined in his client configuration. In case there is more than one AOS defined in the configuration the first available will be used. Adding all available AOS's to one client config file would probably be a smart thing to do. If you only add one node of the cluster to your config file, and this one node is down, y

INTRODUCTION The standard lookup system in Axapta is based on the use of table field or data type relations. These specify a link between a particular data type, or particular table field, and a corrsponding field in another table containing the base (reference) data. Generally, relations are made on the datatype (EDT) in the AOT, and will then automatically apply to any table field using that EDT. For example, in the standard application, the CustAccount EDT has a relation specified to CustTable.CustAccount. This means that any table field using the CustAccount EDT will be automatically given a lookup icon which allows the user to select from the list of accounts in CustTable. It is possible to further restrict the values which will appear in the lookup by specifying a "Related fixed field" relations on the datatype. In this case, only those values satisfying the relation will be shown in the lookup. See the Dimension datatype for an example of this (each Array Element

Very helpful information on indexes http://sumitsaxfactor.wordpress.com/2011/05/05/info-on-indexes/

Installing sharepoint http://www.programminghelp.com/software/installing-sharepoint-services-on-small-business-server-2003/ Error Prompted while running SharePoint Products and Technologies Configuration Wizard   Failed and displayed error “Failed to register SharePoint Services. An exception of the System.Runtime.InteropServices.COMException was thrown. Additional exception information: Could not access the Search service configuration database Did this following steps and the configuration finished successfully. 1.       On the Start menu, click Run. In the Open box, type regedit and then click OK.   2.       In the Registry Editor, navigate to the following subkey, and then delete it:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\Services\Microsoft.SharePoint.Search.Administration.SPSearchService Run the SharePoint Products and Technologies Configuration Wizard again.