{"id":3098,"date":"2011-08-30T11:56:40","date_gmt":"2011-08-30T09:56:40","guid":{"rendered":"https:\/\/ingmarverheij.com\/2011\/08\/place-all-objects-in-a-res-workspace\/"},"modified":"2011-08-30T11:56:40","modified_gmt":"2011-08-30T09:56:40","slug":"place-all-objects-in-a-res-workspace","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/place-all-objects-in-a-res-workspace\/","title":{"rendered":"Place all objects in a RES Workspace"},"content":{"rendered":"

Author<\/strong>: Ingmar Verheij<\/a><\/p>\n

\"RESAfter an upgrade<\/strong> from RES PowerFuse 7 to RES Workspace Manager 2011 all objects where not bound to a workspace. One of the benefits<\/strong> of Workspace Manager 2011 is the ability to control multiple<\/strong> environments (like mobile workers with laptops and central workers on terminal servers) from the same database<\/strong>. <\/p>\n

These different environments are collected in a workspace<\/strong>, hence the name Workspace Manager.<\/p>\n

<\/p>\n

After the migration of the first PowerFuse 7 database (in my case the terminal server database), another database has to be migrated to Workspace Manager 2011 and consolidated<\/strong> in the same database. The environments are then separated<\/strong> using the workspaces.<\/p>\n

\"Context<\/a>This required me to reconfigure all objects <\/strong>to apply only for the \u2018Terminal Server\u2019 workspace.<\/p>\n

After creating the workspace in the Context > Workspace-containers node, the objects had to be reconfigured<\/strong>. Reconfiguring the objects can be done in three ways:<\/p>\n

    \n
  1. Manually<\/strong> filtering the access-control per objects (which are thousands); <\/li>\n
  2. Using building blocks<\/strong>. <\/li>\n<\/ol>\n

    Since I\u2019m not a monk<\/strong>, I\u2018d rather not change each object individually<\/strong>. Most objects can easily be altered using an automated<\/strong> process using building blocks. There is only a little <\/p>\n

     <\/p>\n

    Building blocks<\/h4>\n

    From the RES Workspace Manager Administration Guide<\/a>:<\/p>\n

    \"LEGO\u201cBuilding Block stores<\/strong> information about the configuration settings of a RES Workspace Manager site. A Building Block can be imported<\/strong> back into its original site to recreate these settings as a backup solution. A Building Block can also be imported into a different environment in order to copy<\/strong> the settings. This makes Building Blocks useful for change management, and data exchange.<\/em><\/p>\n

    A Building Block is an XML<\/strong> file that can be edited<\/strong> manually. This makes it possible to use a Building Block as a template: before importing a Building Block into another site, you can replace site-specific information such as server names with the information applicable in the target environment\u201d<\/em><\/p>\n

    <\/em><\/p>\n

    First step : Exporting<\/h4>\n

    So the first step is to export<\/strong> all objects in the database that are specific for the terminal servers to a building block. Objects<\/strong> that are specific to terminal servers are for instance the applications, printers, user registry or global authorized files.<\/p>\n

    Exporting to a building block can only be done from the RES Workspace Manager Console<\/strong>. If you right click on any position in the left pane<\/strong> you can select the option \u2018Select items for Building Blocks\u2019. This will enable you to (de)select<\/strong> the nodes in the treeview<\/strong> you want to export to a building block. After selecting the nodes<\/strong> to export, right click again in the left pane and select \u2018Create Building Blocks of selected items\u2019. <\/p>\n

    You can export<\/strong> the building blocks in multiple files (one for each object) or in a single file. In this case it\u2019s best to export into a single<\/strong> file (easier to edit multiple objects).<\/p>\n

    \"RES<\/a>\"RES<\/a>\"RES<\/a>\"Building<\/a><\/p>\n

    \"Create<\/a>\"Building<\/a><\/p>\n

     <\/p>\n

    Second step : Importing into workspace<\/h4>\n

    Now import <\/strong>the building block you\u2019ve just exported. The objects can merge <\/strong>with existing objects (based on the GUIDs). During the import you\u2019ll be able to import all objects in a specific<\/strong> workspace, for instance \u2018Terminal Servers\u2019. <\/p>\n

    \"RES<\/a>\"Import<\/a>\"Import<\/a>\"Import<\/a>\"Import<\/a><\/p>\n

    Most<\/strong> objects (like applications, printers and user registry) are now placed in a workspace<\/strong>. Other objects, like security management settings, are not<\/strong>. One of the objects that wasn\u2019t places in a workspace where the \u2018Global Authorized files\u2019. Although these are \u2018global\u2019, they are specific<\/strong> for the terminal server workspace.<\/p>\n

     <\/p>\n

    Third step: Edit building blocks<\/h4>\n

    Building Blocks are saved as a XML<\/strong> file and can easily be edited. Binding an object to a specific workspace is relatively easy, if you know what option<\/strong> needs to be set. Fortunately RES is very consequent<\/strong> in naming settings in the XML file, so assigning an object to a workspace is done in the same way for each<\/strong> object.<\/p>\n

    A building block for a \u2018Global Authorized File\u2019 that is not linked to a workspace has the following structure<\/strong>:<\/p>\n

    <respowerfuse>
        <version>9.5.1.10<\/version>
        <buildingblock>
            <appguardauthorizedfiles>
                <item>
                    <authorizedfile>c:\\windows\\system32\\cmd.exe<\/authorizedfile>
                    <process>explorer.exe<\/process>
                    <operation>rx<\/operation>
                    <guid>{D87C6D37-F314-445F-BC53-08A0B7A94706}<\/guid>
                    <enabled>yes<\/enabled>
                <\/item><\/p>
            <\/appguardauthorizedfiles><\/p>
        <\/buildingblock>
    <\/respowerfuse><\/p><\/pre>\n
    A workspace can be linked to the object by adding<\/strong> the following lines in the <item>  section.<\/p>\n
    <workspacecontrol>      <workspace>{A427D917-15B7-44B7-9F83-1413DDE40E7E}<\/workspace>\n
    <\/workspacecontrol><\/pre>\n
    The GUID<\/strong> of the workspace can not<\/strong> be found in the RES Workspace Manager Console. By exporting a workspace to a building block, or a object linked to the workspace, the GUID can be easily<\/strong> be found in the XML file.<\/p>\n
    So all you have to do is add<\/strong> the three lines to each item. Doing this manually is a tedious job, I\u2019d rather choose an automate solution. For this I\u2019ve used InfoRapid Search & Replace<\/a> using the following settings:<\/p>\n
    Search for<\/strong> : <\/item><\/p>\n
    In files<\/strong>:  security_global_authorized_files.xml (the building block you\u2019ve exported)<\/p>\n
    Search Method <\/strong>: Exact phrase matching<\/p>\n
    Replace with <\/strong>: <workspacecontrol>\\n<workspace>{A427D917-15B7-44B7-9F83-1413DDE40E7E}<\/workspace>\\n<\/workspacecontrol>\\n<\/item><\/p>\n
    \"Search<\/a>\"Search<\/a>\"Search<\/a>\"Search<\/a><\/p>\n
    After the changes are made, and the file is saved, the building block needs to be imported<\/strong> (as described in the previous step).<\/p>\n
     <\/p>\n
    If you want to edit other<\/strong> objects in the XML file (the building block), here are some object names:<\/p>\n
    Composition \\ Applications \\ Managed Applications : <\/application>
    \n  
    Composition \\ Applications \\ E-mail Settings : <\/instantmapi><\/p>\n
    Composition \\ Applications \\ Data Sources : <\/instantdatasource><\/p>\n
    Composition \\ Files and Folders \\ Drive and Port Mappings : <\/mapping><\/p>\n
    Composition \\ Files and Folders \\ Drive Substitutes : <\/substitute><\/p>\n
    Composition \\ Files and Folders \\ Folder Synchronization : <\/foldersync><\/p>\n
    Composition \\ Files and Folders \\ User Home Directory : <\/advhomedir><\/p>\n
    Composition \\ Files and Folders \\ User Profile Directory : <\/profilemaintenance><\/p>\n
    Composition \\ Printer : <\/printermapping><\/p>\n
    Composition \\ User Settings : <\/profile><\/p>\n
    Composition \\ Other \\ User Registry : <\/registry><\/p>\n
    Composition \\ Other \\ Execute Commands : <\/exttask><\/p>\n
    Composition \\ Other \\ Environment Variables : <\/variable><\/p>\n
    Security \\ Global Authorized Files : <\/item><\/p>","protected":false},"excerpt":{"rendered":"
    Author: Ingmar Verheij After an upgrade from RES PowerFuse 7 to RES Workspace Manager 2011 all objects where not bound to a workspace. One of the benefits of Workspace Manager 2011 is the ability to control multiple environments (like mobile workers with laptops and central workers on terminal servers) from the same database. These different […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[291],"tags":[373,374,372],"class_list":["post-3098","post","type-post","status-publish","format-standard","hentry","category-workpace-manager","tag-building-block","tag-import","tag-workspace-manager"],"_links":{"self":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/3098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/comments?post=3098"}],"version-history":[{"count":0,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/posts\/3098\/revisions"}],"wp:attachment":[{"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/media?parent=3098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/categories?post=3098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ingmarverheij.com\/en\/wp-json\/wp\/v2\/tags?post=3098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}