{"id":356,"date":"2019-03-25T17:30:27","date_gmt":"2019-03-25T20:30:27","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/"},"modified":"2019-06-14T13:00:52","modified_gmt":"2019-06-14T16:00:52","slug":"configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/","title":{"rendered":"Configuring Remote Domains in machines that are not part of a Microsoft network domain."},"content":{"rendered":"<p align=\"justify\"><span><strong>1) Introduction<\/strong><\/p>\n<p>When you configure a Client Remote Domain in Studio, E3 Studio of the Client machine will access the files on the Server Domain in the path indicated by the Client Domain. This path might be a folder created locally on the Client Domain machine, or it might be a folder sharing of the Server Domain on the remote machine, accessed via network. In this case, the sharing must be remotely accessible by the SYSTEM user. When the machines belong to a Microsoft network domain, the SYSTEM user has permissions to access the sharing, without problems. However, when the machines only belong to the same workgroup this permission needs to be explicitly defined.<\/p>\n<p>From version 3.0 on, where Remote Domain functionality is available, E3 Server always runs as a service on SYSTEM account. Services that use the SYSTEM account start without credentials on system context, that is, without user and password authentication. These services, running without a Microsoft network domain and that want to access network resources will be denied because of the lack of credentials and because they are using a null session.<\/p>\n<p>Those settings may vary a little depending on the installed Windows version. In this article the settings will apply to Windows 2000, Windows 2003, Windows XP and Windows Vista.<\/p>\n<p><strong>2) General Settings<\/strong><\/p>\n<p>The following settings must be done on the machine that runs the Domain Server.<\/p>\n<p>If Windows 2000, 2003 or Vista is installed on the machine, follow these procedures:<\/p>\n<p><\/span><\/p>\n<div align=\"justify\">\n<p>&nbsp;<\/p>\n<ul>\n<li>Access <strong>Administrative Tools &#8211; Local Security Policy<\/strong>.<\/li>\n<li>On the next window, access <strong>Local Policies &#8211; Security Options<\/strong>.<\/li>\n<li>Disable Network access: <strong>Restrict anonymous Access to Named Pipes and Shares<\/strong> option.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<\/div>\n<p>&nbsp;<\/p>\n<p align=\"\">\n<img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura1.PNG\" alt=\"\" width=\"550\" height=\"389\" align=\"bottom\" border=\"0\" \/><\/p>\n<p>&nbsp;<\/p>\n<div align=\"justify\">\n<p>&nbsp;<\/p>\n<ul>\n<li>Enable <strong>Accounts: Guest account status<\/strong> option.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<\/div>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/pt-br\/images\/ID91\/Figura7.PNG\" alt=\"\" width=\"500\" height=\"302\" align=\"bottom\" border=\"0\" \/><\/p>\n<p align=\"justify\">\n<span id=\"anchor_div\" style=\"width: 1px; height: 1px;\">\u00a0<\/span>If the Server Domain machine uses Windows XP, the settings must be done directly on Windows Registry. In this case, follow these procedures:<\/p>\n<ul>\n<li>Access the key <em>HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices Lanmanserverparameters<\/em>.<\/li>\n<li>Create a variable named <em>RestrictNullSessAccess<\/em>, of type DWORD, and set its value to 0.<\/li>\n<\/ul>\n<p align=\"justify\">\n<img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura2.PNG\" alt=\"\" width=\"549\" height=\"381\" align=\"bottom\" border=\"0\" \/><\/p>\n<p>This Windows Registry setting may also be done on Window 2000, 2003 and Vista.<\/p>\n<p>According to Microsoft, the key <em>RestrictNullSessAccess<\/em> specifies if the server will restrict the access to the system for users logged without user and password authentication. Possible values are:<\/p>\n<ul>\n<li>\n<div align=\"justify\">0 &#8211; No authentication access is allowed and all users can access shared resources.<\/div>\n<\/li>\n<li>\n<div align=\"justify\">1 &#8211; No access allowed without authentication. Users without authentication will only be able to access directories listed on NullSessionShares variable.<\/div>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p align=\"justify\">\n<p>In any of these cases, you must restart the machine in order to make changes effective.<\/p>\n<p>Besides, you must configure the sharing and the <em>NTFS<\/em> to accept anonymous user access (<em>ANONYMOUS LOGON<\/em>) or network user (<em>NETWORK<\/em>). This is done the following way:<\/p>\n<ul>\n<li>\n<div align=\"justify\">Select the folder that contains the Server Domain, that must be already shared.<\/div>\n<\/li>\n<li>\n<div align=\"justify\">Right-click on it and select <strong>Properties<\/strong> option.<\/div>\n<\/li>\n<li>\n<div align=\"justify\">On Sharing tab, click on [Permissions] button.<\/div>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p align=\"justify\">\n<img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura3.PNG\" alt=\"\" width=\"330\" height=\"424\" align=\"bottom\" border=\"0\" \/>\n<\/p>\n<ul>\n<li>\n<div align=\"justify\">Add the <em>NETWORK<\/em> or <em>ANONYMOUS LOGON<\/em> user, allowing reading access to the folder and then clicking on [OK] button.<\/div>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p align=\"justify\">\n<img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura4.PNG\" alt=\"\" width=\"327\" height=\"394\" align=\"bottom\" border=\"0\" \/>\n<\/p>\n<ul>\n<li>\n<div align=\"justify\">Access <strong>Security<\/strong> tab and again add <em>NETWORK<\/em> or <em>ANONYMOUS LOGON<\/em> user (the same added on <strong>Sharing<\/strong> tab), then click on [OK] button.<\/div>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p align=\"\">\n<img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura5.PNG\" alt=\"\" width=\"372\" height=\"478\" align=\"bottom\" border=\"0\" \/><\/p>\n<p>Another way of allowing access to this sharing is to include the folder that contains the Server Domain on the directory list of <em>NullSessionShares<\/em> variable. This variable is available on <em>HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanserverparameters<\/em>. This option works, but it is more limited, because folder name is recorded directly on Windows Registry and any changes to Remote Domain settings may require the same changing on Windows Registry.<\/p>\n<p><img loading=\"lazy\" title=\"\" src=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura6.PNG\" alt=\"\" width=\"460\" height=\"323\" align=\"bottom\" border=\"0\" \/><\/p>\n<p><strong>3) Other concerns<\/strong><\/p>\n<p>On machines running Windows XP, the firewall is normally enabled. For this communication between the machines to work correctly at runtime, the firewall must be correctly configured or disabled.<\/p>\n<p>In some cases the <strong>Security<\/strong> tab may not be visible along with the <strong>Sharing<\/strong> tab on folder properties. This occurs because in some Windows versions, like XP, for example, running without belonging to a Microsoft network domain, the simplified sharing mode is enabled by default. In this case you must change the sharing mode by changing the ForceGuest variable on registry key:<\/p>\n<p><em>HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLSA<\/em><\/p>\n<p>The variable must be set to 0.<\/p>\n<p><strong>4) Other information<\/strong><\/p>\n<p><a href=\"http:\/\/support.microsoft.com\/kb\/289655\">http:\/\/support.microsoft.com\/kb\/289655<\/a><br \/>\n<a href=\"http:\/\/support.microsoft.com\/kb\/325874\">http:\/\/support.microsoft.com\/kb\/325874<\/a><br \/>\n<a href=\"http:\/\/support.microsoft.com\/kb\/132679\/EN-US\/\">http:\/\/support.microsoft.com\/kb\/132679\/EN-US\/<\/a><br \/>\n<a href=\"http:\/\/support.microsoft.com\/kb\/122702\/EN-US\/\">http:\/\/support.microsoft.com\/kb\/122702\/EN-US\/<\/a><br \/>\n<a href=\"http:\/\/support.microsoft.com\/kb\/246261\/\">http:\/\/support.microsoft.com\/kb\/246261\/<\/a><br \/>\n<a href=\"http:\/\/www.microsoft.com\/technet\/prodtechnol\/windows2000serv\/reskit\/regentry\/58643.mspx?mfr=true\">http:\/\/www.microsoft.com\/technet\/prodtechnol\/windows2000serv\/reskit\/regentry\/58643.mspx?mfr=true<\/a><br \/>\n<a href=\"http:\/\/technet2.microsoft.com\/windowsserver\/en\/library\/2b8bdf70-becc-41f7-b305-88300df0892d1033.mspx?mfr=true\">http:\/\/technet2.microsoft.com\/windowsserver\/en\/library\/2b8bdf70-becc-41f7-b305-88300df0892d1033.mspx?mfr=true<\/a><\/p>\n<p><strong>5) Conclusion<\/strong><\/p>\n<p>Until Windows NT it was allowed that a service using a <em>SYSTEM<\/em> account or a normal account to access resources on a local or remote machine. On later versions of Windows, this access fails if the <em>SYSTEM<\/em> account is used. The solution presented on this article grants access again.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>1) Introduction When you configure a Client Remote Domain in Studio, E3 Studio of the Client machine will access the files on the Server Domain in the path indicated by&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0},"categories":[760],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v19.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Configuring Remote Domains in machines that are not part of a Microsoft network domain. - Elipse Knowledgebase<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Configuring Remote Domains in machines that are not part of a Microsoft network domain.\" \/>\n<meta property=\"og:description\" content=\"1) Introduction When you configure a Client Remote Domain in Studio, E3 Studio of the Client machine will access the files on the Server Domain in the path indicated by&hellip;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\" \/>\n<meta property=\"og:site_name\" content=\"Elipse Knowledgebase\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/elipsesoftware\" \/>\n<meta property=\"article:published_time\" content=\"2019-03-25T20:30:27+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-06-14T16:00:52+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura1.PNG\" \/>\n<meta name=\"author\" content=\"Elipse Software\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Elipse Software\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\"},\"author\":{\"name\":\"Elipse Software\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87\"},\"headline\":\"Configuring Remote Domains in machines that are not part of a Microsoft network domain.\",\"datePublished\":\"2019-03-25T20:30:27+00:00\",\"dateModified\":\"2019-06-14T16:00:52+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\"},\"wordCount\":1607,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\"},\"articleSection\":[\"Remote Domains\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\",\"url\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\",\"name\":\"[:pt]Configuring Remote Domains in machines that are not part of a Microsoft network domain.[:en]Configuring Remote Domains in machines that are not part of a Microsoft network domain.[:] - Elipse Knowledgebase\",\"isPartOf\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#website\"},\"datePublished\":\"2019-03-25T20:30:27+00:00\",\"dateModified\":\"2019-06-14T16:00:52+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"In\u00edcio\",\"item\":\"https:\/\/kb.elipse.com.br\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Configuring Remote Domains in machines that are not part of a Microsoft network domain.\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/kb.elipse.com.br\/#website\",\"url\":\"https:\/\/kb.elipse.com.br\/\",\"name\":\"Elipse Knowledgebase\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/kb.elipse.com.br\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\",\"name\":\"Elipse Software\",\"url\":\"https:\/\/kb.elipse.com.br\/\",\"sameAs\":[\"http:\/\/www.facebook.com\/elipsesoftware\"],\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png\",\"contentUrl\":\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png\",\"width\":161,\"height\":58,\"caption\":\"Elipse Software\"},\"image\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87\",\"name\":\"Elipse Software\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g\",\"caption\":\"Elipse Software\"},\"url\":\"https:\/\/kb.elipse.com.br\/en\/author\/webmasterelipse-com-br\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Configuring Remote Domains in machines that are not part of a Microsoft network domain. - Elipse Knowledgebase","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/","og_locale":"en_US","og_type":"article","og_title":"[:pt]Configuring Remote Domains in machines that are not part of a Microsoft network domain.[:en]Configuring Remote Domains in machines that are not part of a Microsoft network domain.[:] - Elipse Knowledgebase","og_description":"1) Introduction When you configure a Client Remote Domain in Studio, E3 Studio of the Client machine will access the files on the Server Domain in the path indicated by&hellip;","og_url":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/","og_site_name":"Elipse Knowledgebase","article_publisher":"http:\/\/www.facebook.com\/elipsesoftware","article_published_time":"2019-03-25T20:30:27+00:00","article_modified_time":"2019-06-14T16:00:52+00:00","og_image":[{"url":"http:\/\/kb.elipse.com.br\/images\/ID91\/Figura1.PNG"}],"author":"Elipse Software","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Elipse Software","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#article","isPartOf":{"@id":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/"},"author":{"name":"Elipse Software","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87"},"headline":"Configuring Remote Domains in machines that are not part of a Microsoft network domain.","datePublished":"2019-03-25T20:30:27+00:00","dateModified":"2019-06-14T16:00:52+00:00","mainEntityOfPage":{"@id":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/"},"wordCount":1607,"commentCount":0,"publisher":{"@id":"https:\/\/kb.elipse.com.br\/#organization"},"articleSection":["Remote Domains"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/","url":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/","name":"[:pt]Configuring Remote Domains in machines that are not part of a Microsoft network domain.[:en]Configuring Remote Domains in machines that are not part of a Microsoft network domain.[:] - Elipse Knowledgebase","isPartOf":{"@id":"https:\/\/kb.elipse.com.br\/#website"},"datePublished":"2019-03-25T20:30:27+00:00","dateModified":"2019-06-14T16:00:52+00:00","breadcrumb":{"@id":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"In\u00edcio","item":"https:\/\/kb.elipse.com.br\/en\/"},{"@type":"ListItem","position":2,"name":"Configuring Remote Domains in machines that are not part of a Microsoft network domain."}]},{"@type":"WebSite","@id":"https:\/\/kb.elipse.com.br\/#website","url":"https:\/\/kb.elipse.com.br\/","name":"Elipse Knowledgebase","description":"","publisher":{"@id":"https:\/\/kb.elipse.com.br\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kb.elipse.com.br\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/kb.elipse.com.br\/#organization","name":"Elipse Software","url":"https:\/\/kb.elipse.com.br\/","sameAs":["http:\/\/www.facebook.com\/elipsesoftware"],"logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/","url":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png","contentUrl":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png","width":161,"height":58,"caption":"Elipse Software"},"image":{"@id":"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87","name":"Elipse Software","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g","caption":"Elipse Software"},"url":"https:\/\/kb.elipse.com.br\/en\/author\/webmasterelipse-com-br\/"}]}},"_links":{"self":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/356"}],"collection":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/comments?post=356"}],"version-history":[{"count":2,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/356\/revisions"}],"predecessor-version":[{"id":7265,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/356\/revisions\/7265"}],"wp:attachment":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/media?parent=356"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/categories?post=356"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/tags?post=356"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}