Ok so I have started drilling into the New Microsoft System Center Virtual Application Server Branch Configuration Guide. Its change slightly from the old softricity days and this is to help us develop some of our core developing plans. Now I have some views that I would have liked to have seen in the Branch office guide, however the chaps are working pretty flat out for 4.5 which there should be some great great improvements! As I say this is a part 1……… with Part 2 coming out with 4.5 🙂
There are essentially two designs that are supported inside of Microsoft SoftGrid Application Virtualization: the Non-Centralized Branch and the Centralized Branch Hub. The differences between these two models are simply where the database exists.
An Non-Centralized Branch includes a local database and a replicated copy of the content, but is managed as separate entities from a central management console. The figure below shows an Non-Centralized Branch:
Non-Centralized Branch Architecture
Connection to the Microsoft SoftGrid database is a dependency for the MSCVAS and needs to be available when the server starts operation. Currently, the MSCVAS database does not support replication. In the Non-Centralized Branch model, the MSCVAS database is placed locally in the branch, either on the branch server itself or on another server if more than a single branch server is being used at the remote location. In this situation, the application records must be either directly imported or copied through the MSCVAS management console application record copy feature.
The metering database in this model will only collect data for the local applications that are connected to the server. Centralized metering in native Microsoft SoftGrid Application Virtualization is not supported for the Non-Centralized Branch model at this time.
The Centralized Branch Hub is characterized by a single, centralized database which the branch servers use via a direct connection over the WAN. SoftGrid content is replicated to all sites. Since the database is centralized, all publishing information is centralized. The figure below shows a Centralized Branch Hub:
Centralized Branch Hub Architecture
Connection to the Microsoft SoftGrid database is a dependency for the MSCVAS and needs to be available when the server starts operation. Currently, the MSCVAS database does not support replication. The centralized database model keeps the database at a foundation site and the remote servers connect over the WAN. In this model, only one database is maintained and the metering information is centralized. Due to the MDO capabilities of the Microsoft SoftGrid Virtual Application system, if the WAN link drops, the users may continue to use the applications already in cache.