Category: Blog

Your blog category

Managing Exchange Mailbox Quota: A Comprehensive Guide

In the realm of email administration, managing mailbox quotas in Microsoft Exchange is a critical task that ensures the smooth functioning of an organization’s communication system. Mailbox quotas are used to control the size of mailboxes, which in turn helps manage the growth of mailbox databases and prevents the system from being overwhelmed by excessively large individual mailboxes.

Here’s a step-by-step guide on how to effectively manage mailbox quotas in Exchange Server.

Understanding Mailbox Quotas

Before diving into the configuration process, it’s essential to understand what mailbox quotas entail. Essentially, there are three types of quotas:

  • Issue Warning Quota: This is the threshold at which Exchange will notify the user that their mailbox is nearing its maximum size.
  • Prohibit Send Quota: Once the mailbox reaches this size, the user will no longer be able to send emails.
  • Prohibit Send/Receive Quota: At this point, the user will not be able to send or receive emails.

Setting Up Mailbox Quotas

To configure mailbox quotas, administrators can use the Exchange Admin Center (EAC) or the Exchange Management Shell. The process is as follows:

1. Using the EAC:

  • Navigate to Recipients > Mailboxes.
  • Select the mailbox you wish to configure.
  • Click ‘Edit’ and then go to the ‘Mailbox Usage’ section.
  • Click ‘More options’ and customize the settings for the selected mailbox.

2. Using the Exchange Management Shell:

  • Connect to the Exchange Management Shell.
  • Use the `Set-Mailbox` cmdlet to configure the quotas. For example:

 

Set-Mailbox User@domain.com -ProhibitSendQuota 25GB -ProhibitSendReceiveQuota 25GB -IssueWarningQuota 24GB

 

  • To verify the settings, use the `Get-Mailbox` cmdlet followed by `Select *quota*` to list the quotas attached to the mailbox.

Best Practices for Mailbox Quota Management

  • Regular Monitoring: Keep an eye on mailbox sizes and growth trends to adjust quotas proactively.
  • User Education: Inform users about the quota system and encourage them to regularly archive or clean up their mailboxes.
  • Policy Communication: Clearly communicate the mailbox quota policies to avoid confusion and ensure compliance.

Customizing Quotas for Exchange Online

For Exchange Online, the mailbox size is determined by the subscription license associated with it. To increase or customize the mailbox size:

  • Assign a different subscription license that allows a larger mailbox size.
  • Use PowerShell cmdlets to set custom quotas for a single user or all users within an organization.

Conclusion

Effectively managing mailbox quotas is vital for maintaining the efficiency and reliability of an organization’s email system. By following the outlined steps and best practices, administrators can ensure that mailboxes remain within acceptable size limits, thus preventing potential disruptions in email services.

For more detailed instructions and additional management tasks related to user mailboxes, refer to below YouTube video where I explained this in detail and also shared few examples on how to manage the quota on Exchange Server. Remember, a well-managed email system is the backbone of seamless corporate communication.

Download the PowerShell Cmdlets used during this video from here.


This guide aims to provide a clear understanding of how to manage Exchange mailbox quotas. Whether you’re a seasoned IT professional or new to Exchange Server, these insights will help you maintain an organized and efficient email system.

Installing Exchange Server 2019 Core on Windows Server 2022

The integration of Exchange Server 2019 Core with Windows Server 2022 brings forth a powerful combination for businesses seeking robust email and collaboration solutions. This guide aims to provide a step-by-step approach to installing Exchange Server 2019 Core on Windows Server 2022, ensuring a smooth and efficient setup process.

Prerequisites

Before initiating the installation process, certain prerequisites must be met:

  • A Windows Server 2022 instance must be up and running.
  • Active Directory Domain Services (AD DS) should be installed and configured.
  • The server should have a static IP address to maintain consistent network communication.

Step 1: Prepare Windows Server 2022

Ensure that your Windows Server 2022 is configured correctly. This includes setting up the correct regional settings, configuring the network settings with a static IP address, and joining the server to the Active Directory domain.

Step 2: Install Required Features and Roles

  • Exchange Server 2019 Core requires specific roles and features to be installed on Windows Server 2022. These include:
  • .NET Framework 4.8 or later
  • Visual C++ Redistributable Packages for Visual Studio 2013
  • Unified Communications Managed API 4.0

You can install these prerequisites using PowerShell or through the Server Manager interface.

Step 3: Prepare Active Directory

Before installing Exchange Server, you must prepare your Active Directory environment. This involves extending the AD schema to include Exchange-specific classes and attributes, creating Exchange system objects in the AD, and preparing each domain where Exchange will be installed.

Step 4: Install Exchange Server 2019 Core

With the prerequisites in place, you can proceed to install Exchange Server 2019 Core. Mount the Exchange installation media and launch the setup. During the setup, you will select the roles to be installed, agree to the license terms, and configure other settings as prompted.

Step 5: Post-Installation Configuration

After the installation, perform post-installation tasks such as configuring Exchange services, setting up mailboxes, and verifying that the Exchange Administrative Center is accessible.

Step 6: Verify the Installation

To confirm that Exchange Server 2019 Core has been installed successfully, use the Exchange Management Shell or the Exchange Administrative Center to check the server’s status and functionality.

Completed - Exchange Core Installation

 

Conclusion

Installing Exchange Server 2019 Core on Windows Server 2022 requires careful planning and execution. By following the steps outlined in this guide, IT professionals can ensure a successful deployment, providing their organizations with a stable and secure email and collaboration platform.

For more detailed instructions and best practices, refer to the below YouTube video. Happy installing!

Download the Cmdlets used on this video from here.

 

Managing email address policies in Exchange Server 2019

Managing email address policies in Exchange Server 2019 involves creating, modifying, and applying policies that define the rules for generating email addresses for recipients within your Exchange organization. Here’s a step-by-step guide to managing these policies:

  1. Access the Exchange Admin Center (EAC): Sign in to the EAC to begin the process of managing your email address policies.
  2. Navigate to Mail Flow: Once logged in, go to the ‘Mail flow’ section and then to ‘Email address policies’.
  3. Create a New Policy: Click the ‘+’ icon to add a new email address policy. You’ll need to provide a unique name for the policy and configure the email address format. This includes setting up the primary SMTP email address and any additional proxy addresses.
  4. Specify Recipient Filters: Define which recipients the policy applies to by setting up recipient filters. This ensures that only the intended users receive the email addresses generated by the policy.
  5. Set the Priority: If you have multiple policies, you’ll need to specify the order in which they are applied. This is important if a recipient qualifies for more than one policy.
  6. Apply the Policy: After creating the policy, you must apply it to the recipients. This can be done immediately or scheduled for a later time.
  7. Modify Policies as Needed: Existing policies can be edited or removed as your organization’s needs change. This allows for flexibility and adaptability in managing recipient email addresses.

Custom SMTP email address templates:

If you don’t want to use default SMTP email address templates, you can specify a custom SMTP email address template as well. When creating a custom SMTP email address template, you can use the variables listed in the following table to specify values for the local part of the email address.
Variable Value
%d Display Name
%g Given Name (First Name)
%i Middle initial
%m Exchange Alias
%rxy Replace all occurrences of X with Y
%rxx Remove all occurrences of X
%s Surname (last name)
%ng The first n letters of the first name. For example, %2g uses the first two letters of the first name.
%ns The first n letters of the last name. For example, %2s uses the first two letters of the last name.

For detailed instructions and information on the settings available for each step, you can watch my YouTube video below.

Download the PowerShell cmdlets used on the video from here.

 

Adding Active Directory RSAT Tools on Windows 10

Remote Server Administration Tools (RSAT) are a set of tools that IT administrators can use to manage Windows Server from a remote computer. For Windows 10 users, adding RSAT is a straightforward process that enhances their administrative capabilities, especially when managing Active Directory (AD) environments.

Here’s a step-by-step guide to adding Active Directory RSAT Tools on Windows 10:

  • Open Settings: Click on the Start menu and select ‘Settings’.
  • Access Optional Features: Navigate to ‘Apps’ and then click on ‘Optional features’.
  • Add a Feature: Click on ‘Add a feature’ at the top of the page.
  • Search for RSAT: In the search box, type ‘RSAT’ to find all the available RSAT tools.
  • Select Your Tools: Choose the specific RSAT tools you need. For Active Directory management, you might select ‘RSAT: Active Directory Domain Services and Lightweight Directory Services Tools’.
  • Install: Click ‘Install’ to add the selected tools to your system.

Once installed, you can access the RSAT tools from the Start menu, under ‘Windows Administrative Tools’. It’s important to note that RSAT tools are only supported on Windows 10 Professional, Enterprise, or Education editions.

For those who prefer using PowerShell, RSAT tools can also be installed via command line. Here’s an example PowerShell command to install all RSAT tools:

Get-WindowsCapability -Name RSAT* -Online | Add-WindowsCapability –Online

And to install a specific RSAT tool, such as Active Directory Domain Services tools, you would use:

Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools

By adding RSAT tools to your Windows 10 system, you enhance your ability to manage and maintain your AD environment efficiently, without the need for direct access to your servers. This not only streamlines administrative tasks but also provides a level of convenience and flexibility for IT professionals.

For more detailed instructions, kindly watch my YouTube Video below.

Enabling Active Directory Certificate Services (ADCS)

Active Directory Certificate Services (ADCS) is a critical component in a Windows Server environment, providing public key infrastructure (PKI) functionality to authenticate and secure information. If you’re looking to enable ADCS on Windows Server 2022, here’s a step-by-step guide to get you started.

Step 1: Pre-Installation Requirements

Before installing ADCS, ensure that your server has a static IP address, is named appropriately, and is joined to the domain. You’ll need to have membership in both the Enterprise Admins and the root domain’s Domain Admins group, which is the minimum requirement to complete the installation process.

Step 2: Installing ADCS via Server Manager

  • Log in as a member of both the Enterprise Admins group and the root domain’s Domain Admins group.
  • Open Server Manager, click ‘Manage’, and then select ‘Add Roles and Features’.
  • Proceed through the wizard until you reach ‘Select Server Roles’.
  • In ‘Roles’, select ‘Active Directory Certificate Services’. When prompted, add the required features.
  • Continue through the wizard, reading the provided information carefully, and then confirm your installation selections.

Step 3: Configuring ADCS

After the installation, you’ll need to configure ADCS on the destination server. This involves specifying the type of CA, such as Enterprise Root CA, and setting up role services like Certification Authority.

Step 4: Using PowerShell for Installation

For those who prefer using PowerShell, the following commands can be used to install and configure ADCS:

Add-WindowsFeature Adcs-Cert-Authority -IncludeManagementTools

Install-AdcsCertificationAuthority -CAType EnterpriseRootCA

 

After running these commands, you’ll have successfully installed the ADCS role on your Windows Server 2022.

Conclusion

Setting up ADCS is a straightforward process that can be accomplished either through the Server Manager or PowerShell. It’s an essential step in managing certificates within your network, ensuring secure communication and authentication across your organization’s IT infrastructure.

 

For more detailed instructions and additional configurations, you can refer to my YouTube Video Below.

 

Removing the Last Exchange 2013 Server

The decommissioning of an Exchange 2013 server is a critical task for IT administrators as they move towards newer versions of Exchange Server. With the end of support for Exchange Server 2013, it’s essential to ensure a smooth transition without disrupting the organizational workflow. Here’s a comprehensive guide to help you remove the last Exchange 2013 Server from your environment.

Preparation for Decommissioning

Before you begin the removal process, it’s crucial to prepare your environment. This involves ensuring that all services and data have been migrated to the newer Exchange Server, such as Exchange Server 2016 or 2019. You should also update any third-party applications and reconfigure them to work with the new Exchange infrastructure.

Inventory and Upgrade

Make a list of all applications that interact with your Exchange 2013 servers. Contact the providers of these applications to confirm they are supported on the newer version of Exchange Server you’re migrating to.

Client Access Server (CAS) Role

Review all client connectivity namespaces to ensure they are routing to the latest Exchange server(s) in your environment. This includes Outlook Anywhere, Autodiscover, and other Exchange virtual directories. If the new Exchange environment uses the same namespaces, you can reuse the existing SSL certificate. Otherwise, a new certificate with the appropriate names will be required.

Review Service Connection Point Objects

Run the command
Get-ExchangeServer | Where-Object {$_.AdminDisplayVersion -like “Version 15.0*” -and $_.IsClientAccessServer -eq $true} | Get-ClientAccessService | Format-Table Name, FQDN, AutoDiscoverServiceInternalUri -AutoSize
to obtain the value of the Autodiscover service connection point (SCP), which is used by internal clients to look up connection information from Active Directory.

Uninstalling Exchange 2013

Once you’ve confirmed that all services are running on the new server and all data has been migrated, you can proceed to uninstall Exchange 2013. From the Exchange Server 2013, open Add/Remove Programs or run `appwiz.cpl` from the command line. Locate Microsoft Exchange Server 2013 and click on Uninstall. Follow the prompts to complete the uninstallation process.

 

Post-Removal Steps

After removing Exchange 2013, monitor your environment to ensure that all clients and services are operating as expected. Check the logs and validate that there are no connections attempting to route through the decommissioned server.

Conclusion

Removing the last Exchange 2013 Server is a significant step in modernizing your organization’s email infrastructure. By following these steps, you can ensure a seamless transition and maintain the integrity of your communication systems.

Remember, it’s always recommended to have a backup and a rollback plan before making any significant changes to your server infrastructure. Decommissioning an Exchange server is a complex process that requires careful planning and execution. If you encounter any issues or have specific questions, consulting with a certified Exchange professional is advisable. Happy decommissioning!
For more detailed information, watch my YouTube video and download all the commands used on the video Here.

 

Installing Exchange Server 2019: A Step-by-Step Guide

Exchange Server 2019 is Microsoft’s latest release of their flagship messaging and collaborative software, designed for enterprise-level organizations to manage emails, calendars, tasks, and contacts. This guide provides a comprehensive walkthrough for IT professionals on installing Exchange Server 2019.

Preparation

Before beginning the installation process, it’s crucial to ensure that your system meets all the necessary prerequisites:

  • System Requirements: Verify that your server hardware, operating system, and software meet the Exchange Server 2019 system requirements.
  • Active Directory: The server must be a member of an Active Directory domain, and the account used for installation should have the appropriate permissions, including membership in the Enterprise Admins and Schema Admins groups if this is the first Exchange server in the organization.
  • Windows Server: Install the necessary Windows Server features and updates. For Exchange Server 2019, Windows Server 2019 is recommended.
  • Exchange ISO: Download the latest version of Exchange Server 2019 from the Microsoft Volume Licensing Service Center or the official Microsoft website.

Installation Steps

  1. Mount the ISO: Right-click the downloaded Exchange Server 2019 ISO file and select ‘Mount’. This will create a virtual DVD drive on your system.
  2. Setup Wizard: Navigate to the virtual DVD drive and run ‘Setup.exe’ as an administrator. This will launch the Exchange Server Setup wizard.
  3. Updates and License Agreement: Choose whether to check for updates during the installation and accept the license terms.
  4. Server Role Selection: Select the roles that the server will perform. Typically, this will be the Mailbox role, which includes the management tools.
  5. Installation Path: Choose the installation location for Exchange Server 2019.
  6. Readiness Checks: The setup will perform checks to ensure that your system meets all the prerequisites for installation.
  7. Installation: Proceed with the installation. This process may take some time, and the server may need to be restarted several times.
  8. Finalization: After installation, open the Exchange Admin Center (EAC) to verify that the installation was successful and that all services are running properly.

 

Post-Installation Configuration

After successfully installing Exchange Server 2019, you’ll need to configure the server settings, mail flow, and client access. This includes setting up virtual directories, databases, and transport rules.

Conclusion

Installing Exchange Server 2019 requires careful planning and attention to detail. By following the steps outlined in this guide and ensuring all prerequisites are met, IT professionals can successfully deploy Exchange Server 2019 in their organizations, paving the way for efficient and secure communication.

Remember, after installing Exchange on a server, do not change the server’s name, as this is not supported and can lead to significant issues.

This guide aims to provide a clear path to installing Exchange Server 2019, but always consult the official documentation for the most up-to-date and detailed information.

For more detailed instructions on How to Install Exchange Server 2019, watch my YouTube Video below.
Download all the commands used on this video Here.

Removing the Default Exchange Server Database

When you install a new Exchange Server, it automatically creates a default mailbox database. However, there may be various reasons why an administrator would want to remove this database, such as applying naming conventions, setting up a Database Availability Group (DAG), or splitting storage for better performance. Removing the default database is not as straightforward as deleting a file; it requires a series of steps to ensure that the system remains stable and functional.

1. Verify No User Mailboxes Exist

Before attempting to remove any database, confirm that no user mailboxes are present. Use the PowerShell command in the Exchange Management Shell (EMS):

Get-Mailbox -Database “<DatabaseName>”

This command lists all mailboxes in the specified database.

2. Rename the Database (Optional)

For ease of management, you might want to rename the database. This can be done through the Exchange Admin Center (EAC) under the ‘Servers’ and ‘Databases’ tabs or via PowerShell:

Set-MailboxDatabase “<OldDatabaseName>” -Name “<NewDatabaseName>”

3. Move System and User Mailboxes

If any mailboxes are still in the database, they must be moved to another database. This includes user mailboxes, system mailboxes, and arbitration mailboxes. Use the `New-MoveRequest` command to move each mailbox:

New-MoveRequest -Identity “<MailboxName>” -TargetDatabase “<TargetDatabaseName>”

Monitor the move request status with:

Get-MoveRequest
Get-MoveRequest | Get-MoveRequestStatistics

 

4. Delete the Database

Once all mailboxes have been moved, you can delete the database from the EAC by selecting the database and clicking the ‘Delete’ icon. Remember, this action only removes the database from Exchange Server; it does not delete the physical EDB file.

5. Remove Physical Database Files

After removing the database from the Exchange setup, manually delete the physical EDB file and its associated log files from the server’s file system.

6. Post-Removal Checks

After deletion, ensure that the database is no longer listed in the EMS and that all services are running correctly.

It’s important to note that these steps are a general guide and may vary slightly depending on the version of Exchange Server you are using. Always ensure that you have a complete backup before making any changes to the server.

Remember, removing the default Exchange Server database should be done with caution and thorough understanding of the process to maintain the integrity and smooth operation of your server.

For more detailed instructions and visual guides, you can refer to video tutorial uploaded on my YouTube channel.

Download the commands used in the video from Here.

 

Distribute Exchange Mailbox

In the dynamic world of IT management, the ability to efficiently manage mailboxes in an Exchange Server is a valuable skill. This may require IT Administrators to occasionally move the mailboxes from one database to another. This process, known as mailbox migration, is essential for various scenarios such as load balancing, server decommissioning, or simply organizational restructuring.

By default, Exchange Server will create a single default database and stores all the user mailbox, shared mailbox and other types of special mailboxes which are used by Exchange services.

Having all the mailboxes stored on a single database can lead to issues like,

  • Oversized database
  • Database exceeding the space on the physical HDD.
  • if the database is failed or corrupted, all the users on the organization will be affected and may not be able to use Exchange services.

This may cause a huge downtime for all the users on the organization.

However, if you plan and distribute the mailboxes across multiple Exchange databases and Multiple Exchange servers, it will drastically reduce the downtime and the impact.

Moving Mailboxes in Exchange Server:

Before initiating the migration, it’s crucial to ensure that the Exchange environment is healthy and that all prerequisites are met. This includes checking database integrity, ensuring sufficient storage space, and verifying that the target database is properly configured and operational.

Using Exchange Admin Center (EAC):

1. Log in to the EAC and navigate to the ‘Recipients’ section, followed by the ‘Migration’ tab.
2. Click on the ‘+’ icon and select ‘Move to a different database’.
3. Choose the mailboxes you wish to move and specify the target database.
4. Configure the move request settings, such as the number of bad items to ignore and the recipient of the completion report.
5. Initiate the migration either immediately or schedule it for a later time.

Using Exchange Management Shell (EMS):

For those who prefer using PowerShell, the Exchange Management Shell provides a powerful way to move mailboxes.

1. Use the `Get-Mailbox` cmdlet to list all mailboxes in the source database.
2. Create a new move request with the `New-MoveRequest` cmdlet, specifying the target database.
3. Monitor the move request with the `Get-MoveRequest` and `Get-MoveRequestStatistics` cmdlets.
4. Upon completion, verify the move by checking the mailboxes in the target database.

To Distribute multiple mailboxes using PowerShell and Balance them across all the database automatically, please watch may YouTube video below.

 

Download the Commands used on this video Here.

Post-Migration Tasks:

After the migration, it’s important to confirm that all mailboxes are functioning correctly in the new database. This includes testing mail flow, accessing mailboxes, and ensuring client connectivity.

Best Practices:

– Always have a rollback plan in case the migration encounters issues.
– Perform migrations during off-peak hours to minimize impact on users.
– Consider moving mailboxes in batches to reduce the load on the server.

Conclusion:

Mailbox migration is a critical task that can be executed smoothly with proper planning and execution. By following the steps outlined above, administrators can ensure a seamless transition from one database to another, maintaining the integrity and availability of user data throughout the process.

Create Exchange Mailbox Databases on Exchange Server

Exchange Server is a powerful mail server system used by organizations worldwide to ensure efficient email communication. One of the key components of setting up an Exchange Server is creating mailbox databases, which store users’ mailboxes and related data. Here’s a professional guide on how to create Exchange mailbox databases on Exchange Server.

Step 1: Prepare Your Environment

Before you begin, ensure that your Exchange Server is properly installed and configured. Check that the system requirements are met, including hardware, software, and network configurations. Also, make sure you have administrative rights to carry out the database creation process.

Step 2: Open Exchange Admin Center (EAC)

Access the Exchange Admin Center by opening a web browser and navigating to the URL of your Exchange Server’s EAC. This is typically in the format `https://<YourExchangeServer>/ecp`. Log in using your administrator credentials.

Step 3: Navigate to Databases

In the EAC, go to the “servers” section and then click on “databases”. This will take you to the area where you can manage your mailbox databases.

Step 4: Add a New Mailbox Database

Click on the “+” sign to add a new mailbox database. You will be prompted to enter various details such as the database name, the server where it will be hosted, and the file path where the database and log files will be stored.

Step 5: Configure Database Settings

After providing the necessary information, you can configure additional settings for the database. This includes setting limits on mailbox sizes, retention policies, and maintenance schedules.

Step 6: Save and Mount the Database

Once you’ve configured the settings to your preference, save the new database. After saving, the database will be created but not yet mounted. To mount the database, select it from the list and click on the “mount” option. This will make the database active and ready to host mailboxes.

Step 7: Create Mailboxes

With the database mounted, you can now create mailboxes. Go to the “recipients” section in the EAC, click on “mailboxes”, and then use the “+” sign to add new user mailboxes to your newly created database.

Step 8: Verify the Setup

After creating the mailboxes, it’s important to verify that they are working correctly. Send test emails to ensure that the mail flow is functioning and that users can access their mailboxes.

Creating mailbox databases is a fundamental task for managing an Exchange Server environment. By following these steps, you can ensure that your organization’s email system is robust, scalable, and ready for operation. Remember to regularly back up your databases and monitor their performance to maintain a healthy Exchange environment.

You can also use PowerShell to Create Exchange Databases. For more detailed information, please watch the below YouTube video on the same.

Download all the commands used on this Video Here.

 

#iguru_soc_icon_wrap_688ae2431e298 a{ background: transparent; }#iguru_soc_icon_wrap_688ae2431e298 a:hover{ background: transparent; border-color: #661D92; }#iguru_soc_icon_wrap_688ae2431e298 a{ color: #F8F3D9; }#iguru_soc_icon_wrap_688ae2431e298 a:hover{ color: #F8F3D9; }.iguru_module_social #soc_icon_688ae2431e2be1{ color: #FF005D; }.iguru_module_social #soc_icon_688ae2431e2be1:hover{ color: #FF005D; }.iguru_module_social #soc_icon_688ae2431e2be1{ background: #661D92; }.iguru_module_social #soc_icon_688ae2431e2be1:hover{ background: #661D92; }.iguru_module_social #soc_icon_688ae2431e2cd2{ color: #FF005D; }.iguru_module_social #soc_icon_688ae2431e2cd2:hover{ color: #FF005D; }.iguru_module_social #soc_icon_688ae2431e2cd2{ background: #661D92; }.iguru_module_social #soc_icon_688ae2431e2cd2:hover{ background: #661D92; }#wgl-menu-module_688ae2431e490 a.wgl-menu-module_link { color: #FFFFFF; font-size: 14px; }#wgl-menu-module_688ae2431e490 a.wgl-menu-module_link:hover { color: #FAF4D3; }#wgl-menu-module_688ae2431e490 a:before { background-color: #FAF4D3; }#wgl-menu-module_688ae2431e4d2 a.wgl-menu-module_link { color: #FFFFFF; font-size: 14px; }#wgl-menu-module_688ae2431e4d2 a.wgl-menu-module_link:hover { color: #FAF4D3; }#wgl-menu-module_688ae2431e4d2 a:before { background-color: #FAF4D3; }#wgl-menu-module_688ae2431e514 a.wgl-menu-module_link { color: #FFFFFF; font-size: 14px; }#wgl-menu-module_688ae2431e514 a.wgl-menu-module_link:hover { color: #FAF4D3; }#wgl-menu-module_688ae2431e514 a:before { background-color: #FAF4D3; }#wgl-menu-module_688ae2431e546 a.wgl-menu-module_link { color: #FFFFFF; font-size: 14px; }#wgl-menu-module_688ae2431e546 a.wgl-menu-module_link:hover { color: #FAF4D3; }#wgl-menu-module_688ae2431e546 a:before { background-color: #FAF4D3; }