Windows Server - tutorial.wmlcloud.com

Change page: < 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ... > | Displaying page 2 of 59, items 51 to 100 of 2916.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 4) - Setting storage restrictions on mailbox and archives

In a standard configuration of Exchange Online, each licensed user gets 25 GB of mailbox storage, and a storage warning is issued when the mailbox reaches 22.5 GB.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 3) - Permitting others to access a mailbox

Occasionally, users need to access someone else’s mailbox, and in certain situations, you should allow this. For example, if John is Susan’s manager and Susan is going on vacation, John might need access to her mailbox while she’s away.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 2) - Setting message send and receive restrictions on individual mailboxes

You can select multiple recipients at the same time. To select multiple recipients individually, hold down the Ctrl key and then tap or click each recipient that you want to select. To select a sequence of recipients, select the first recipient, hold down the Shift key, and then tap or click the last recipient.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 1) - Setting message size restrictions on delivery to and from individual mailboxes

Message size restrictions control the maximum size of messages that can be sent or received in the Exchange organization. With Exchange Online, the maximum size of messages that users can send is 35,840 KB and the maximum size of messages that users can receive is 36,864 KB by default.

Microsoft Exchange Server 2013: Moving mailboxes (part 3) - Performing on-premises mailbox moves

With online moves and batch migrations, you can move mailboxes between databases on the same server. You also can move mailboxes from a database on one server to a database on another server regardless of whether the servers are in a different Active Directory site or in another Active Directory forest.

Microsoft Exchange Server 2013: Moving mailboxes (part 2) - Performing on-premises mailbox moves and migrations

The destination database for an on-premises mailbox move can be on the same server, on a different server, in a different domain, or in a different Active Directory site.

Microsoft Exchange Server 2013: Moving mailboxes (part 1) - Importing and exporting mail data

You must have the Mailbox Import Export role to be able to import or export mailbox data. Because this role isn’t assigned to any role group, you must be explicitly assigned this role.

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 4) - Restoring online users and mailboxes, Repairing mailboxes

If you remove the Exchange Online license for an online user account, the user’s account is marked as an unlicensed account. Exchange Online deletes mailboxes from unlicensed accounts automatically after the grace period expires.

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 3) - Restoring on-premises users and mailboxes

When you disable or delete a mailbox, on-premises Exchange retains the deleted mailbox in the mailbox database and puts the mailbox in a disabled state. There is, however, an important distinction between disabling and deleting a mailbox, and this difference affects recovery.

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 2) - Configuring apps for mailboxes

With both on-premises Exchange and Exchange Online, you can add apps to the Outlook Web App interface to add functionality. Several apps are installed and made available to users by default, including the following apps created by Microsoft

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 1) - Viewing current mailbox size, message count, and last logon

You often need to manage user mailboxes the way you do user accounts. Some of the management tasks are intuitive and others aren’t. If you have questions, be sure to read the sections that follow.

Managing Windows Server 2012 Systems : Managing the Registry (part 8) - Securing the registry - Auditing registry access

Access to the registry can be audited, as can access to files and other areas of the operating system. Auditing allows you to track which users access the registry and what they’re doing

Managing Windows Server 2012 Systems : Managing the Registry (part 7) - Securing the registry - Preventing access to the registry utilities, Applying permissions to registry keys

The registry is a critical area of the operating system. It has some limited built-in security to reduce the risk of settings being inadvertently changed or deleted.

Managing Windows Server 2012 Systems : Managing the Registry (part 6) - Backing up and restoring the registry, Maintaining the registry

Backing up and restoring the registry normally isn’t done from within Registry Editor, however. It is handled through the Windows Server Backup utility or through your preferred third-party backup software.

Managing Windows Server 2012 Systems : Managing the Registry (part 5) - Registry administration - Importing and exporting registry data

Sometimes you might find that it is necessary or useful to copy all or part of the registry to a file. For example, if you’ve installed a service or component that requires extensive configuration, you might want to use it on another computer without having to go through the whole configuration process again

Managing Windows Server 2012 Systems : Managing the Registry (part 4) - Registry administration - Modifying the registry

When you want to work with keys and values in the registry, you typically are working with subkeys of a particular key. This allows you to add a subkey and define its values and to remove subkeys and their values.

Managing Windows Server 2012 Systems : Managing the Registry (part 3) - Registry data: How it is stored and used

Now that you know more about the registry’s structure, let’s take a look at the actual data within the registry. Understanding how registry data is stored and used is just as important as understanding the registry structure.

Managing Windows Server 2012 Systems : Managing the Registry (part 2) - Registry root keys

The registry is organized into a hierarchy of keys, subkeys, and value entries. The root keys are at the top of the hierarchy and form the primary branches, or subtrees, of registry information.

Managing Windows Server 2012 Systems : Managing the Registry (part 1) - Introducing the registry, Understanding the registry structure

Many administrative tools are little more than friendly user interfaces for managing the registry, especially when it comes to Control Panel.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 11)

The most recent versions of Exchange Server, as well as Active Directory, were designed to break through the constraints that had limited previous Exchange implementations.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 10)

To determine the default configuration domain controller, view the Event Viewer application log and search for Event ID 2081. The results of the Microsoft Exchange Active Directory Topology service query are listed here as well, as shown in Figure 8.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 9)

When a domain controller receives the orders to become a global catalog server, there is a period of time when the GC information replicates to that domain controller.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 8)

To understand how Exchange manages security, an analysis of Active Directory authentication is required. This information aids in troubleshooting the environment, as well as in gaining a better understanding of Exchange Server 2013 as a whole.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 7)

DNSLINT is a Microsoft Windows utility that helps administrators diagnose common DNS name resolution issues. The utility is not installed by default on Windows servers and has to be downloaded from Microsoft.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 6)

Troubleshooting is part of everyday life for administrators. DNS is no exception to this rule. Therefore, understanding how to use the following tools to troubleshoot DNS not only helps avoid mistakes when configuring DNS-related services, but also provides administrators with a useful toolbox to resolve issues.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 5)

This configuration is also helpful in stopping dangerous viruses from being spread through email. For example, dangerous scripts could potentially be attached to email, which could execute as soon as the user opens the mail.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 4)

Though DNS entries for MX records can be pointed to CNAME host records, doing so is not advised and is not a Microsoft recommended best practice. Increased administrative overhead and the possibility of misrouted messages can result.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 3)

Copying the DNS database from one server to another is accomplished through a process known as a zone transfer. Zone transfers are required for any zone that has more than one name server responsible for the contents of that zone.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 2)

A Windows Server 2008 or Windows 2012 DNS server can store zone information in two distinct formats: Active Directory–integrated or standard text file.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 1)

With Microsoft Exchange relying on Active Directory and domain name system (DNS) to function, it is important for an organization to make sure that critical networking services are configured and operating properly and that domain controllers have been deployed and configured to adequately support the environment.

Windows Server 2012 : Enhancing DHCP Reliability - Windows Server 2012 DHCP Failover

Windows Server 2012 DHCP includes a failover scope feature. The benefit of this feature is that leases and reservations are synchronized across the DHCP server and a failover cluster is not required.

Windows Server 2012 : Enhancing DHCP Reliability - Implementing Redundant DHCP Services

DHCP is a critical network service and should be treated as such. Building redundancy into DHCP services has been a challenge for years, and with each release of Windows Server, DHCP redundancy options get better.

Windows Server 2012 : Enhancing DHCP Reliability - DHCP Network Access Protection Integration

The Windows Server 2012 DHCP server service can interact with the Network Access Protection (NAP) service. NAP consists of administrator-defined policies that include specific criteria to be met before a system is allowed to communicate on the network

Windows Server 2012 : Enhancing DHCP Reliability - DHCP Name Protection, DHCP and Dynamic DNS Configuration

If you want to avoid DNS registration issues, you can configure this account to have the password never expire. As a best practice, however, you should change the service account password in Active Directory and in the DHCP server settings as frequently as defined in the standard user password policy.

Windows Server 2012 : Enhancing DHCP Reliability - Link-Layer Filtering, DHCP Reservations

Link-layer filtering or MAC address filtering is a feature of the Windows Server 2012 DHCP service that can be enabled to provide a higher level of security to DHCP leases.

Exploring DHCP Changes in Windows Server 2012 : Migrating DHCP Services from 2008 R2 to Windows Server 2012, derstanding DHCP Client Alternate Network Capability

Aside from the export and import process, after the export is completed on the source server, the source server IP address must be changed, and the original source server IP address must be added to the destination server for the import and DHCP operation to be seamless.

Exploring DHCP Changes in Windows Server 2012 : Migrating DHCP Servers Using Windows Server Migration Tools

The Windows Server 2012 Window Server Migration Tools are a set of tools designed to aid administrators with the migration of not only DHCP scope information, but also the current leases, reservations, and scope options.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Preparing the Server and Installing OWA via the GUI

As noted earlier, the evolution and expansion of OWA has changed the installation procedures greatly from the previous version. The first step to any OWA install is to prepare and configure the server.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Topology

Office Web Apps has moved from an exclusive SharePoint service onto its own standalone server. This change is critical to how you configure and architect Office Web Apps to service the SharePoint 2013 farm.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Mobile Device Support

Just as the nature of how SharePoint information is accessed has evolved, so has its delivery method. The previous model, which offered a rather static view that lacked graphics suited for small, low-resolution displays, has been radically updated for use as an appropriate communications platform.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Desktop Enhancements

A primary concern for Microsoft following the release of Office Web Apps 2010 was the varying user experience between different operating systems. For example, users of Office Web Apps on a Mac had only some functions available.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Licensing and Versions

Office Web Apps offers some significant changes from the previous version in the licensing arena. There are two licenses in Office Web Apps this time around. The default Office Web Apps mode is view-only, and it is provided free.

Microsoft Lync Server 2013 : Persistent Chat Administration (part 2) - Chat Room Management by End Users , Persistent Chat Troubleshooting

As noted previously, chat room management can be handled not only by Lync administrators, but also by end users who are delegated low-level administrative permissions to the chat room configuration.

Microsoft Lync Server 2013 : Persistent Chat Administration (part 1) - Chat Room Management by Administrators

The message history initially presented to the user when viewing a chat room is based on the Default Chat History setting configured by the administrator. However, this does not prevent a user from searching the chat room for additional messages that are maintained within the chat history for the room.

Microsoft Lync Server 2013 : Configuring Persistent Chat (part 4) - Creating a Chat Room Using the Lync Server Management Shell , Creating a Chat Room Using the Lync 2013 Client

Chat room add-ins are used to extend the Persistent Chat user experience by associating customized websites with chat rooms. When add-ins are registered by the Lync administrator and associated with chat rooms, the content of the specified websites is embedded in the conversation extensibility pane of the Lync 2013 client.

Microsoft Lync Server 2013 : Configuring Persistent Chat (part 3) - Chat Room Categories

Chat room categories are used to develop a logical structure for the organization of chat rooms, and also serve as a mechanism for controlling which users and groups are permitted to create or join the chat rooms within those categories.

Microsoft Lync Server 2013 : Configuring Persistent Chat (part 2) - Persistent Chat Server Options

Lync Server 2013 provides the capability to create a set of server options that can be applied globally to all Persistent Chat pools, or alternatively these same server options can be applied to a specific site or pool

Microsoft Lync Server 2013 : Configuring Persistent Chat (part 1) - Administrative Access, Persistent Chat Policies

Persistent Chat policies are used to determine which Lync users are enabled for Persistent Chat. There are four levels of policies that can be used: global, pool, site, and user.

Microsoft Lync Server 2013 : Persistent Chat Deployment (part 3) - Installing the Persistent Chat Server Role

After the Lync topology has been updated to include the Persistent Chat pool, the Lync Server role installation can be run on each Persistent Chat server that has been added to the topology.

Microsoft Lync Server 2013 : Persistent Chat Deployment (part 2) - Topology Update

Although a new FQDN is created in the topology for Persistent Chat pools that are deployed on separate hardware, it is not necessary to enter the FQDN of the Persistent Chat pool as an internal DNS record. The Front End Server handles all the routing for Persistent Chat without requiring DNS queries.