Teams for Virtualized Desktop Infrastructure - Microsoft Teams (2023)

  • Article
  • 21 minutes to read
  • Applies to:
    Microsoft Teams

This article describes the requirements and limitations for using Microsoft Teams in a virtualized environment.

What is VDI?

Virtual Desktop Infrastructure (VDI) is a virtualization technology that hosts a desktop operating system and applications on a central server in a data center. This enables users to have a complete and personalized desktop experience with a fully secure and compliant centralized source.

Teams in a virtualized environment support chat and collaboration. And with Azure Virtual Desktop, Citrix and VMware platforms, calling and meeting capabilities are also supported.

Teams also supports multiple configurations in virtual environments. These include VDI, dedicated, shared, persistent, and non-persistent modes. Features are constantly evolving and being added regularly, and functionality will expand over time.

Using Teams in a virtualized environment can be slightly different than using Teams in a non-virtualized environment. For example, some advanced features may not be available in a virtualized environment and video resolution may vary.

Follow the guidelines in this article to ensure the best user experience.

monitoring

For details on Teams VDI on different platforms, seeTeams features by platform.

Teams in VDI components

Using Teams in a virtualized environment requires the following components.

  • virtualization broker: the resource and connection manager for virtualization providers like Azure
  • virtual desktop: The virtual machine (VM) stack running Teams
  • skinny customer: The device with which the user is physically interacting
  • Teams-Desktop-App: Die Teams-Desktop-Client-App

Teams on VDI requirements

Virtualization Vendor Requirements

The Teams desktop app has been validated by leading virtualization solution providers. With many vendors in the industry, we recommend checking with your virtualization solution vendor to ensure you meet the minimum requirements.

Teams on VDI with audio/video (AV) optimization is currently certified with Azure Virtual Desktop, Citrix, and VMware. Review the information in this section to ensure that you meet all of the requirements for proper functionality.

Certified platforms for teams

The following platforms have virtual desktop infrastructure solutions for teams.

platformsolution
Teams for Virtualized Desktop Infrastructure - Microsoft Teams (1)Azure Virtual Desktop,Windows 365
Teams for Virtualized Desktop Infrastructure - Microsoft Teams (2)Citrix Virtual Apps and Desktops
Teams for Virtualized Desktop Infrastructure - Microsoft Teams (3)VMware-Horizon

Azure Virtual Desktop

Azure Virtual Desktop provides AV optimization for teams in VDI. For more information on requirements and installation, seeUse Teams on Azure Virtual Desktop.

Windows 365

Windows 365 uses the AV optimization provided by Azure Virtual Desktop to ensure optimal Teams experiences from cloud PCs. For more information on requirements and installation, seeDon't use a cloud PC in Teams.

Citrix Virtual Apps and Desktops are required

Citrix Virtual Apps and Desktops (formerly known as XenApp and XenDesktop) provides AV optimization for VDI teams. Powered by Citrix Virtual Apps and Desktops, Teams on VDI supports calling and meeting capabilities in addition to chat and collaboration.

You can download the latest version of Citrix Virtual Apps and Desktops fromSite en downloads Citrix. (You must login first.) The required components are grouped inCitrix Workspace (CWA) applicationand Virtual Delivery Agent (VDA) by default. You don't need to install any additional components or plugins on the CWA or VDA.

For the latest server and client requirements, seeOptimization for Microsoft TeamsArticle on the Citrix website.

Requirements for VMware Horizon Workspace and Desktop

VMware Horizon is a modern platform for securely delivering virtual desktops and applications in the hybrid cloud. To provide a great end-user experience, VMware Horizon offers media optimization for teams. This optimization improves overall productivity across virtual desktops and apps, and enhances the user experience when calling and meeting with Teams.

You can download the latest version of VMware Horizon fromDownloads VMwarePage. The required media optimization components are part of Horizon Agent and Horizon Client by default, and no additional plugins need to be installed to use the Teams optimization feature.

For the latest requirements and instructions for configuring Media Optimization for Teams, seeConfigure media optimization for Microsoft TeamsArticle on the VMware website.

Install or update the Teams desktop app on VDI

You can deploy Teams desktop app for VDI using a per-machine installation or a per-user installation using the MSI package. The decision on which approach to use depends on whether you are using a persistent or non-persistent configuration and your organization's associated functional requirements.

In a dedicated persistent setup, the installation works per machine and per user. However, for a non-persistent setup, Teams requires one installation per machine to run efficiently. see thenon-persistent configurationSection.

With per-machine installation, automatic updates are disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. Automatic updates are enabled with per-user installation.

Important

Keep the Teams desktop app up-to-date in your VDI environment. Versions of the Teams desktop app with release dates older than 90 daysRelease date of the current versionare not supported. Unsupported Teams desktop app versions show users a lock page and prompt them to update your app.

For most VDI deployments, we recommend that you deploy Teams using per-machine installation. To update to the latest version of Teams, start with the uninstall procedure, followed by deploying the latest version of Teams.

For Teams AV optimization to work properly in VDI environments, the thin client device must have internet access. If Internet access is not available on the thin client device, the optimization will fail to initialize. This means the user is in an unoptimized media state.

Dedicated persistent configuration

In a dedicated persistent configuration, users' local operating system changes are persisted after users log off. For persistent configuration, Teams supports per-user, per-machine installation.

Below is the recommended minimum VM configuration.

ParameterWorkstation operating systemserver operating system
vCPU2 Core4, 6 or 8 cores
It's important to understand the underlying non-uniform memory access (NUMA) configuration and configure your VMs accordingly.
BEAT4GB512MB to 1GB per user
Save on computer8GB40GB to 60GB

non-persistent configuration

In a non-persistent configuration, users' local operating system changes are not persisted after users log off. These configurations are typically shared multi-user sessions. The VM configuration varies depending on the number of users and available physical server resources.

For a non-persistent setup, the Teams desktop app must be installed per machine on the golden image. This ensures an efficient launch of the Teams app during a user session. For more information, seeInstall or update the Teams desktop app on VDISection.

Using Teams in a non-persistent configuration also requires a profile cache manager for efficient run-time data synchronization of Teams. Efficient data synchronization ensures that the appropriate user-specific information (such as a user's data, profile, or settings) is cached during the user's session. Make sure the data in these two folders is synced:

  • C:\Users\username\AppData\Local\Microsoft\IdentityCache (%LocalAppData%\Microsoft\IdentityCache)
  • C:\Users\username\AppData\Roaming\Microsoft\Teams (%AppData%\Microsoft\Teams)

monitoring

A mobile folder (or, if you're using folder redirection, a cache manager) is required to ensure that the Teams app has the data and runtime files needed to run the app. This is necessary to mitigate network latency issues or network outages that would otherwise cause application errors and a slow experience due to unavailable data and files.

There are a variety of cache manager solutions, such as:FSLogixGenericName. Consult your cache manager vendor for specific configuration instructions.

Teams cached content exclusion list for non-persistent configuration

Delete the following from the Teams cache folder,%AppData%/Microsoft/Teams. Excluding these items helps reduce the size of the user cache to further optimize your non-persistent configuration.

  • .txt files
  • Media Stack Folder
  • %AppData%\Microsoft\Teams\meeting-addin\Cache

Microsoft 365 Apps for enterprise considerations

Consider the following when deploying Teams with Microsoft 365 Apps for enterprise over VDI.

New Teams deployments through Microsoft 365 Apps for enterprise

Before deploying Teams through Microsoft 365 Apps for enterprise, you must first uninstall any existing Teams apps if they were deployed using per-machine installation.

Teams through Microsoft 365 Apps for enterprise is installed on a per-user basis. For more information, seeInstall or update the Teams desktop app on VDISection.

Teams deployments through Microsoft 365 Apps for business updates

Teams is also added to existing installations of Microsoft 365 Apps for enterprise. Because Microsoft 365 Apps for enterprise installs Teams on a per-user basis, seeInstall or update the Teams desktop app on VDISection.

Using Teams with per-machine install and Microsoft 365 Apps for enterprise

Microsoft 365 Apps for enterprise doesn't support Teams per-machine installations. To use per-machine installation, you must exclude Teams from Microsoft 365 Apps for business. see theDeploy the Teams desktop app on the VMeHow to delete Teams deployment via Microsoft 365 Apps for enterprisesections.

How to delete Teams deployment via Microsoft 365 Apps for enterprise

For more information about Teams and Microsoft 365 Apps for enterprise, seeHow to exclude teams from new installations of Microsoft 365 for enterprise appseUse Group Policy to control Teams installation.

Deploy the Teams desktop app on the VM

⁠1. Download the Teams MSI package corresponding to your VDI VM OS by using one of the links below:-32-Bit-Version-64-Bit-Version> [!NOTE]> For information on government clouds, seeBulk install Teams using Windows Installer (MSI)for the download links for the MSI files.

  1. Install the MSI on the VDI VM by running one of the following commands:

    • Install per user (default)

      msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSERS=1

      This process is the default installation that installs Teams%Application Data%user folder. At this point, the setup of the golden image is complete.

      Important

      Teams will not work correctly when installed per user in a non-persistent configuration.

    • Installation per machine

      reg add "HKLM\SOFTWARE\Microsoft\Teams" /v IsWVDEnvironment /t REG_DWORD /d 1 /f

      This process adds a required registry key to the computer that informs the Teams installer that it's a VDI instance. Without them, the installer throws an error message stating, "Installation failed. Unable to install for all users if no VDI environment is detected."

      msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1

      This process installs Teams%Program Files(x86)%Folder on a 64-bit operating system and for the%Program Files%Folders on a 32-bit operating system. At this point, the setup of the golden image is complete.

      Important

      Per-machine Teams installation is required for non-persistent configurations.

      When the next interactive sign-in session begins, Teams will launch and ask for credentials.

      monitoring

      These examples also use theALLBENUTZER=1Parameter. By setting this parameterMachine-wide installer for teamsappears inprograms and functionsnoSwitchboardis onapplications and functionsnoWindows settingsfor all computer users. All users can uninstall Teams if they have admin credentials.

      It is important to understand the difference betweenALLBENUTZER=1eALLUSER=1. ÖALLBENUTZER=1parameter can be used in non-VDI and VDI environments, while parameterALLUSER=1The parameter is only used in VDI environments to specify a per-machine installation.

  2. Uninstall the MSI from the VDI VM. There are two ways to uninstall Teams.

    • Script makes PowerShellMission: You can use the...Cleanup of Teams deploymentPowerShell script to uninstall Teams and remove Teams folder for a user. Run the script for each user profile that has Teams installed on the computer.

    • command line: Run the following command.

      msiexec /passive /x <path_to_msi> /l*v <uninstall_logfile_name>

      This process uninstalls Teams from%Program Files(x86)%folder or%Program Files%Folder depending on the operating system environment.

Teams on VDI performance considerations

There are a variety of virtualized installation configurations, each with a different focus on optimization. For example, a setting might focus on user density. Consider the following when planning to optimize your configuration based on your organization's workload requirements.

  • Minimum requirements: Some workloads may require configuration with resources above minimum requirements. For example, workloads for developers using applications that require more computing resources.
  • dependencies: This includes infrastructure dependencies, workload, and other environmental considerations outside of the Teams desktop app.
  • Disabled features in VDI: Teams disables GPU-intensive resources for VDI, which can help improve transient CPU utilization. The following features are disabled:
    • CSS animation for teams
    • Giphy-Autostart

VDI teams with calls and meetings

In addition to chat and collaboration, Teams on VDI is available with calling and meetings with supported virtualization vendor platforms. Supported features are based on WebRTC media stack implementation and virtualization provider. The following diagram gives an overview of the architecture.

Teams for Virtualized Desktop Infrastructure - Microsoft Teams (4)

Important

If you're currently running Teams without AV optimization over VDI and using features not yet supported for optimization (e.g. give and take control when sharing apps), you need to set your virtualization vendor policies to allow Teams -Redirect is disabled. This means Teams media sessions will not be optimized. Contact your virtualization vendor for steps to set policies to disable Teams redirection.

network requirements

We recommend that you assess your environment to identify any risks and requirements that may impact your overall cloud voice and video deployment. Use theNetwork assessment tool for Skype for Businessto test if your network is Teams ready.

For more information on preparing your network for Teams, seePrepare your organization's network for Teams.

Migrate from Skype for Business on VDI to Teams on VDI

When moving from Skype for Business on VDI to Teams on VDI, in addition to the differences between the two apps, there are some differences when implementing VDI as well. Some features that are currently not supported in Teams VDI included with Skype for Business VDI are as follows:

  • Platform-specific policy to disable some AV features in VDI
  • Give and take control when sharing apps
  • Mute chat screen sharing
  • Simultaneously send and receive video and screen sharing

Teams in Chrome browser vs Teams desktop app for VDI

Teams on Chrome browser does not replace the Teams desktop app for AV-optimized VDI. The chat and collaboration experience works as expected. When media is required, there are some experiences that may not live up to what users expect in the Chrome browser:

  • The audio and video streaming experience may not be optimal. Users may experience lag or reduced quality.
  • Device settings are not available in browser settings.
  • Device management is done through the browser and requires various settings in the browser's website settings.
  • Device settings may also need to be configured in Windows device management.

Teams in VDI with chat and collaboration

If your organization only wants to use chat and collaboration features in Teams, you can set user-level policies to turn off calling and meeting features in Teams.

Set policies to disable calling and meeting functionality

You can set policies using the Teams admin center or PowerShell. Policy changes may take a few hours to take effect. If you don't see the changes for a specific account right away, try again in a few hours.

Calling Policies: O teams inclui o installedBan callsCalling policy in which all calling features are disabled. Assign theBan callsPolicy for all users in your organization using Teams in a virtualized environment.

Meeting Policies: O teams inclui o installedAllOffMeeting policy in which all meeting features are disabled. Assign theAllOffPolicy for all users in your organization using Teams in a virtualized environment.

Assign policies using the Teams admin center

to assignBan callscalling policy and theAllOffMeeting policy for a user:

  1. In the left navigation of the Teams admin center, go touser.
  2. Select the user by clicking to the left of the username, then clickEdit Settings.
  3. Do the following:
    1. Undercalling policy, CliqueBan calls.
    2. Undersession policy, CliqueAllOff.
  4. CliqueUse.

To assign a policy to multiple users at once:

  1. In the left navigation of the Teams admin center, go touserand then browse the users or filter the view to show the users you want.
  2. no(check mark), select the users. To select all users, click the button(tick) at the top of the table.
  3. CliqueEdit Settings, make your changes, and clickUse.

Or you can also do the following:

  1. In the left navigation of the Teams admin center, go to the policy you want to assign. For example:
    • Go toVoice>Calling Policiesand then clickBan calls.
    • Go tosessions>Meeting Policiesand then clickAllOff.
  2. Selectmanage users.
  3. nomanage usersDashboard, search for the user by display name or username, select the name and clickAdd to. Repeat this step for each user you want to add.
  4. When you are finished adding users, clickointment .

Assign policies with PowerShell

The following example shows how to use theGrant-CsTeamsCallingPolicyassign theBan callsCalling policy for a user.

Grant-CsTeamsCallingPolicy -PolicyName DisallowCalling -Identity "id de e-mail do usuário"

For more information on using PowerShell to manage calling policies, seeSet-CsTeamsCallingPolicy.

The following example shows how to use theGrant-CsTeamsMeetingPolicyassign theAllOffMeeting policy for a user.

Grant-CsTeamsMeetingPolicy -PolicyName AllOff -Identity "Benutzer-E-Mail-ID"

For more information about using PowerShell to manage meeting policies, seeSet-CsTeamsMeetingPolicy.

Migrate Teams to VDI with chat and collaboration to streamline Teams with calls and meetings

If you have an existing implementation of Teams on VDI with chat and collaboration where you have defined user-level policies to disable calling and meetings functionality and you are moving to Teams with AV optimization, you must define policies to Enable the calling and meeting features for Teams on VDI users.

Set policies to enable calling and meeting features

You can use the Teams admin center or PowerShell to define and assign calling and meeting policies for your users. It may take some time (a few hours) for policy changes to take effect. If you don't see the changes for a specific account right away, try again after a few hours.

Calling Policies: Calling policies in Teams control which calling features are available to users. Teams includes the built-inallow callsCalling policy in which all calling features are enabled. To enable all call features, assign theallow callsPolitics. Or create a custom calling policy to enable desired calling features and assign them to users.

Meeting Policies: Meeting policies in Teams control the types of meetings users can create and the features available to meeting attendees scheduled by users in your organization. Teams includes the built-inAll aboveMeeting policy with all meeting features enabled. To enable all meeting features, assign theAll abovePolitics. Or create a custom meeting policy to enable desired meeting features and assign users to it.

Assign policies using the Teams admin center

to assignallow callscalling policy and theAll aboveMeeting policy for a user:

  1. In the left navigation of the Teams admin center, go touser.
  2. Select the user by clicking to the left of the username, then clickEdit Settings.
  3. Do the following:
    1. Undercalling policy, Cliqueallow calls.
    2. Undersession policy, CliqueAll above.
  4. CliqueUse.

To assign a policy to multiple users at once:

  1. In the left navigation of the Teams admin center, go touserand then browse the users or filter the view to show the users you want.
  2. no(check mark), select the users. To select all users, click the button(tick) at the top of the table.
  3. CliqueEdit Settings, make your changes, and clickUse.

Or you can also do the following:

  1. In the left navigation of the Teams admin center, go to the policy you want to assign. For example:
    • Go toVoice>Calling Policiesand then clickallow calls.
    • Go tosessions>Meeting Policiesand then clickAll above.
  2. Selectmanage users.
  3. nomanage usersDashboard, search for the user by display name or username, select the name and clickAdd to. Repeat this step for each user you want to add.
  4. When you are finished adding users, clickointment .

Assign policies with PowerShell

The following example shows how to use theGrant-CsTeamsCallingPolicyassign theallow callsCalling policy for a user.

Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity "Benutzer-E-Mail-ID"

For more information on using PowerShell to manage calling policies, seeSet-CsTeamsCallingPolicy.

The following example shows how to use theGrant-CsTeamsMeetingPolicyassign theAll aboveMeeting policy for a user.

Grant-CsTeamsMeetingPolicy -PolicyName AllOn -Identity "Benutzer-E-Mail-ID"

For more information about using PowerShell to manage meeting policies, seeSet-CsTeamsMeetingPolicy.

Control fallback mode in Teams

If users connect from an unsupported endpoint, they are in fallback mode where the AV is not optimized. You can disable or enable fallback mode by setting one of the following registersDWORDValues:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\DisableFallback
  • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Teams\DisableFallback

To disable fallback mode, set the value to1. To enable only audio, set the value to2. If the value does not exist or is set to0(zero), fallback mode is enabled.

This feature is available in Teams version 1.3.00.13565 and later.

Disable audio and video settings for VDI

Teams VDI policies are available in the Teams module. These policies are active and enforced in non-optimized VDI environments.

  • New-CsTeamsVdiPolicy
  • Grant-CsTeamsVdiPolicy
  • Remove-CsTeamsVdiPolicy
  • Set-CsTeamsVdiPolicy

monitoring

This only applies to non-optimized environments.

Connect to Microsoft Teams PowerShell, among others

Follow the instructions inInstall the Microsoft Teams PowerShell moduleto connect to the Microsoft Teams PowerShell module. Then run the following command to confirm that all VDI cmdlets are available:

Get-Command -Substantiv *VDI*

Set policies to restrict calling features

If users whose VDITurn off calls and meetingspolicy is set$truesign in to Teams on VDI, they cannot:

  • make calls.
  • Attend meetings.
  • Chat Screen Sharing.

All call types must be disabled.

monitoring

This only applies to non-optimized environments.

New-CsTeamsVdiPolicy -Identity DisableCallsAndMeetingsTrue -DisableCallsAndMeetings $true -DisableAudioVideoInCallsAndMeetings $false<# Atribuir politica #>$user = 'meganb@jvteams.xyz'Grant-CsTeamsVdiPolicy -Identity $user -PolicyName DisableCallsAndMeetingsTrue aplicate aplicada -Identität $user | FL UserPrincipalName, *vdi*<# Heute als Politik #>Get-CsTeamsVdiPolicy | FT-ID*, deaktiviert*

If users whose VDIDisable AudioVideoInCallsAndMeetingspolicy is set$trueDo not enter teams no VDI, these are:

  • You can share the chat screen.
  • Can join a meeting, share a screen, and cast audio to a phone.
  • You cannot make person-to-person VDI audio and video calls.

monitoring

This only applies to non-optimized environments.

$PolName = "DisableCallsAndMeetingsAV"New-CsTeamsVdiPolicy -Identity $PolName -DisableCallsAndMeetings $false -DisableAudioVideoInCallsAndMeetings $trueGrant-CsTeamsVdiPolicy -Identity $user -PolicyName $PolName<# Please wait a while for the policy to be applied #>Get-CSOnlineUser -identity $ user | FL UserPrincipalName, *vdi*<# Post cleanup #>$cleanup = $falseif($cleanup){ "Cleaning up" # Unassign user policy Grant-CsTeamsVdiPolicy -Identity $user -PolicyName $null Get-CSOnlineUser -identity $ user | FL UserPrincipalName, *vdi* # Remove policies Get-CsTeamsVdiPolicy | ?{$_.identity -ne 'Global'} | remove-csTeamsVdiPolicy}

Known issues and limitations

Client deployment, installation and configuration

  • When installed per machine, Teams on VDI is not automatically upgraded in the same way as non-VDI Teams clients. You need to update the VM image by installing a new MSI as described inInstall or update the Teams desktop app on VDISection. You must uninstall the current version to upgrade to a newer version.
  • In Citrix environments, if the user disconnects from the virtual machine while Teams is running, Teams updates can cause the user to be in a non-AV-optimized state when reconnecting. We recommend that users log out of Teams before disconnecting from the Citrix Virtual Machine to avoid this scenario.
  • Teams must be deployed per user or per machine. Deploying Teams per user and per machine at the same time is not supported. To migrate from Per Computer or Per User to either mode, follow the uninstall and redeployment procedure for each mode.
  • Azure Virtual Desktop does not currently support Linux-based clients.
  • Rapid tenant switching can lead to call-related issues in VDI, e.g. B. unavailable screen sharing. Restarting the client fixes these issues.

notifications

  • The notification of the number of messages and the presence of the Windows taskbar are not supported on a Windows Server 2016 host.

calls and meetings

The following calling and meeting features are not supported:

  • HID buttons and LED controls between the Teams app and devices for Citrix and VMware
  • Background blur and effects for Citrix and VMware
  • Roles as producer and presenter of broadcast and live events
  • Location-Based Routing (LBR)
  • Ringtone for PSTN calls
  • Common system audio/computer sound
  • Media bypass for direct routing
  • Check the zoom

monitoring

We are working to add calling and meeting functionality that is currently only available in non-VDI environments. This could include more administrative control over quality, additional screen sharing scenarios, and advanced features recently added to Teams. Contact your Teams representative to learn more about upcoming features.

The following are known issues and limitations for calls and meetings:

  • Interoperability with Skype for Business is limited to audio calls; There is no video mode.
  • The resolution of the incoming and outgoing video stream is limited to 720p resolution.
  • Teams doesn't switch to using the last audio device selected by a user when the device is disconnected and reconnected.
  • Live events are not optimized.
  • Release the output screen:
    • Application sharing is not supported for VMware and AVD/W365.
  • Giving control and taking control:
    • Not supported during an app sharing session.

For known Teams issues not related to VDI, seeSupport teams in your organization.

Troubleshooting

Troubleshooting Citrix components

Teams crashes or the Teams login screen is blank

This is a known issue with Citrix VDA versions 1906 and 1909. To work around this issue, add the following registryDWORDvalue and put it on204(hexadecimal).

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\SfrHook\Teams.exe

Then restart the VDA. For more information, see this Citrix support article.Troubleshooting HDX optimization for Microsoft Teams.

  • Bulk install Teams using Windows Installer (MSI)
  • PowerShell Overview for Teams
  • Use Microsoft Teams on Azure Virtual Desktop
Top Articles
Latest Posts
Article information

Author: Maia Crooks Jr

Last Updated: 10/17/2022

Views: 6635

Rating: 4.2 / 5 (63 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Maia Crooks Jr

Birthday: 1997-09-21

Address: 93119 Joseph Street, Peggyfurt, NC 11582

Phone: +2983088926881

Job: Principal Design Liaison

Hobby: Web surfing, Skiing, role-playing games, Sketching, Polo, Sewing, Genealogy

Introduction: My name is Maia Crooks Jr, I am a homely, joyous, shiny, successful, hilarious, thoughtful, joyous person who loves writing and wants to share my knowledge and understanding with you.