<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Workspace ONE Exchange Config in Digital Workspace Members</title>
    <link>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2913657#M23</link>
    <description>&lt;P&gt;If you have SEG integrated in your WS1 console which acts as a proxy for your on-premise exchange server, you can still keep it, else you can use a Direct Integration using Powershell to combat non-compliant/unmanaged devices accessing the email on 0365.&lt;/P&gt;&lt;P&gt;The best way to migrate is as below:&lt;/P&gt;&lt;P&gt;- SInce not all users will be migrated over night you would need to ask the list of users from the exchange admin&lt;/P&gt;&lt;P&gt;-Create another Assignment (O365 asisgnment) in for the same Boxer app - pointing it to Office365 (if Direct) else point is to the SEG URL if your still going to use SEG&lt;/P&gt;&lt;P&gt;-Create a smartGroup -O365-users. Add the users to this SG manually. As you keep getting the list of users from exhange team, you keep adding them to this group&lt;/P&gt;&lt;P&gt;- Make O365-Users SG, as assignment group for the new assignment&lt;/P&gt;&lt;P&gt;- Use O365-Users SG as a exclusion in the main (existing) Boxer assignment&lt;/P&gt;&lt;P&gt;-Make sure the&amp;nbsp;O365 asisgnment is over(above) the old (exising) Boxer Assignment&lt;/P&gt;&lt;P&gt;As users migrate, you just add them to the SG. The old assignment is removed and&amp;nbsp; they are asigned with new Boxer configuration.&lt;/P&gt;&lt;P&gt;They will have to authenticate to get access to the migrated mailbox&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jun 2022 20:05:04 GMT</pubDate>
    <dc:creator>Imran309</dc:creator>
    <dc:date>2022-06-10T20:05:04Z</dc:date>
    <item>
      <title>Workspace ONE Exchange Config</title>
      <link>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2909452#M16</link>
      <description>&lt;P&gt;Hi All, we are looking for some data about Exchange Hybrid Config using Boxer. While the users are being migrated from Exchange on-prem to O365, the users to be seemlessy moved in Boxer.&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 12:22:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2909452#M16</guid>
      <dc:creator>vignesh_condo</dc:creator>
      <dc:date>2022-05-17T12:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: Workspace ONE Exchange Config</title>
      <link>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2910959#M20</link>
      <description>&lt;P&gt;Hi, I tackled this same setup when I first deployed WS1.&amp;nbsp; I still use Boxer today for all iOS devices and now my users have all been migrated to O365.&lt;/P&gt;&lt;P&gt;I started by utilizing SEG (v2) to connect Boxer with on-prem Exchange.&amp;nbsp; I have now moved to Powershell for O365.&amp;nbsp; You can manage which configuration you utilize within the Boxer assignments.&amp;nbsp; Both can exist at the same time, just utilize assignment groups to control who is using which assignment.&lt;/P&gt;&lt;P&gt;Below I've added some helpful links.&amp;nbsp; Let me know if you have more specific questions.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/2203/WS1-Secure-Email-Gateway/GUID-AWT-INTRO-SEG.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/2203/WS1-Secure-Email-Gateway/GUID-AWT-INTRO-SEG.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/context?id=memOverview" target="_blank"&gt;https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/context?id=memOverview&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 19:43:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2910959#M20</guid>
      <dc:creator>trobertson</dc:creator>
      <dc:date>2022-05-24T19:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: Workspace ONE Exchange Config</title>
      <link>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2913657#M23</link>
      <description>&lt;P&gt;If you have SEG integrated in your WS1 console which acts as a proxy for your on-premise exchange server, you can still keep it, else you can use a Direct Integration using Powershell to combat non-compliant/unmanaged devices accessing the email on 0365.&lt;/P&gt;&lt;P&gt;The best way to migrate is as below:&lt;/P&gt;&lt;P&gt;- SInce not all users will be migrated over night you would need to ask the list of users from the exchange admin&lt;/P&gt;&lt;P&gt;-Create another Assignment (O365 asisgnment) in for the same Boxer app - pointing it to Office365 (if Direct) else point is to the SEG URL if your still going to use SEG&lt;/P&gt;&lt;P&gt;-Create a smartGroup -O365-users. Add the users to this SG manually. As you keep getting the list of users from exhange team, you keep adding them to this group&lt;/P&gt;&lt;P&gt;- Make O365-Users SG, as assignment group for the new assignment&lt;/P&gt;&lt;P&gt;- Use O365-Users SG as a exclusion in the main (existing) Boxer assignment&lt;/P&gt;&lt;P&gt;-Make sure the&amp;nbsp;O365 asisgnment is over(above) the old (exising) Boxer Assignment&lt;/P&gt;&lt;P&gt;As users migrate, you just add them to the SG. The old assignment is removed and&amp;nbsp; they are asigned with new Boxer configuration.&lt;/P&gt;&lt;P&gt;They will have to authenticate to get access to the migrated mailbox&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 20:05:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Digital-Workspace-Members/Workspace-ONE-Exchange-Config/m-p/2913657#M23</guid>
      <dc:creator>Imran309</dc:creator>
      <dc:date>2022-06-10T20:05:04Z</dc:date>
    </item>
  </channel>
</rss>

