![res software workspace manager res software workspace manager](http://4.bp.blogspot.com/-L5HCl489aC4/UKgwvktgRCI/AAAAAAAAAVw/82M26hjlYcM/s1600/RES_custom+interface.png)
- #RES SOFTWARE WORKSPACE MANAGER HOW TO#
- #RES SOFTWARE WORKSPACE MANAGER UPDATE#
- #RES SOFTWARE WORKSPACE MANAGER UPGRADE#
- #RES SOFTWARE WORKSPACE MANAGER WINDOWS#
Import the values starting with DB from the key mentioned earlierĤ. Link these GPO’s to the corresponding Active Directory Organizational Unitsģ. So with XenDesktop 7.x for example this would be the ‘ Citrix Desktop Service‘-service.Ģ. This is to solve the problem of your users connecting to the desktop when the ROW service is not running yet. Keep in mind though, that you might want to change the startup type of your ‘virtual desktop’ service to ‘delayed start’ also. Or, better yet, add it to your Master VM/vDisk creation process (assuming you have such a thing in place, but you know you should). In this case you should alter the service in the Master VM (MCS) or vDisk (PVS). Because after each reboot the setting would be back to default. When using Citrix XenDesktop (Machine Creation Services or Provisioning Services) for your image deployment, it wouldn’t be an option to go down the GPO road for the service. You would set this in the GPO under Computer Configuration -> Preferences -> Control Panel Settings -> Services. You could include this in the same policy, but the machine would require an extra reboot for the service to actually start in a ‘delayed’ manner. To work around this you need to change the startup type of the RES ONE Workspace Agent service to Automatic (Delayed Start). So when the service starts the registry settings might not be there yet.
#RES SOFTWARE WORKSPACE MANAGER WINDOWS#
However, when a Windows machine boots the RES ONE Workspace Agent service starts at about the same time as when the GPO is applied. With it you can connect to a machine that is connected to the specific database and copy the registry values from there. The easiest approach is to use the Registry Wizard. You can do this in the GPO under Computer Configuration -> Preferences -> Windows Settings -> Registry. These need to be added for each database to the corresponding GPO. HKEY_LOCAL_MACHINE\SoftwareWow6432Node\RES\Workspace Manager (64-bit)Īll values that start with the letters DB are needed for the database connection. HKEY_LOCAL_MACHINE\Software\RES\Workspace Manager (32-bit) ROW puts the database connection information in the registry under the following key: We created three Group Policy Objects that are each linked to the matching Active Directory Organizational Unit (one for each environment).
![res software workspace manager res software workspace manager](https://markswinkels.nl/wp-content/uploads/2014/03/RESDB_06.png)
For the customer we used three databases (Development, Acceptance and Production) instead of four (Development is also used for testing). The solution is pretty simple, but it does requires some common sense.
#RES SOFTWARE WORKSPACE MANAGER HOW TO#
While this approach sounds a bit obscure, I’m writing about it because a customer has this exact approach and with the right amount of discipline it can work very well (The discipline to keep the databases in sync with each other, which is harder than you might think).īut back to business, how to control de database connection. Also, when you create a new image for your virtual desktop you might want to put that through the DTAP process as well. This way, you can perform the upgrades in DTAP order and remove the risk of downtime on the production environment.īut how do you control which machines connect to which database? You don’t want to create different images for each database and you probably don’t want to change it manually whenever you boot your machines. That means a dedicated ROW database for each environment. The only viable solution to use DTAP is on the database level.
#RES SOFTWARE WORKSPACE MANAGER UPDATE#
The DTAP approach on the Workspace Container level doesn’t work in these situations since the update is on a higher level.
![res software workspace manager res software workspace manager](https://static.ivanti.com/sites/marketing/media/images/blog/2018/07/jon.rolls.blog.png)
#RES SOFTWARE WORKSPACE MANAGER UPGRADE#
So how would you use the DTAP approach in this situation? Sometimes when you upgrade the database also gets an update. This should suit you for about 90% of all your workspace related changes.īut what if you want to test a new ROW Service Release? Or even an upgrade to a complete new version? While I have RES in really high regard, most new versions do usually have some quirks in them and because of this, testing is in order. You could create a DTAP setup on that level. RES ONE Workspace (ROW from here on) of course has the very useful Workspace Containers.
![res software workspace manager res software workspace manager](https://robbeekmans.net/wp-content/uploads/2014/02/1-1.jpg)
It also reduces the risk of downtime when developing or testing the new application.Ĭan you use this approach in combination with RES ONE Workspace? This method defines specific steps in the development of a new application or an update of a current one. After that de customer/(key-)users can approve of it in the Acceptance environment and when successful it can be deployed in de Production environment. The version is then tested in the Testing environment. An application gets developed for the specific organization in the Development environment. When implementing software, an organization usually wants to go for the DTAP approach (Development, Testing, Acceptance and Production).