Jason Yoder, MCT

By default, Exchange 2010 sends a warning email to all users every day at 1:00 AM. In the past, I’ve often needed users to be more aware of their utilization. Especially if we were approaching storage capacities. You can create a custom schedule to send more notices throughout the day if needed. · Open the Exchange Management Console. · Expand Organization Configuration . · Click Mailbox . · Right click the database you want to configure and select Properties . · Click the Limits tab · Click Customize · Configure your notification schedule and then click OK . · In the drop down box, click Use Custom Schedule . · Click OK . To configure the notification schedule with PowerShell by using the –QuotaNotificationSchedule switch with the Set-MailboxDatabase cmdlet. Here is an example Set-MailboxDatabase –identity “ ” –QuotaNotificationSchedule “Mon.9:00-Mon.10:00”, “Wed.9:00-Wed

In class is gave the wrong information about how to set your access points up on your clients. The Connection Manager Administration Kit is not the correct answer. There is a GPO setting for this. · Open or create a new GPO. · Expand Computer Configuration à Policies à Windows Settings à Security Settings à Wireless Networks (IEEE 802.11) Policies . · Right click Wireless Networks (IEEE 802.11) Policies and select Create a New Wireless Network Policy for Windows Vista and Later Releases . · Provide a Policy Name and a Description · Click Add à Infrastructure . · You can now add the SSID, Authentication, and Encryption type for each of the wireless access points in your organization.

The connection Manager Administration Kit (CMAK) allows you to send configuration information to your users to set up a VPN connection for them. CMAK will create a profile with all the required settings. The user simples opens the file you send them and all the work is done. Click the following link for more information from Microsoft. http://technet.microsoft.com/en-us/library/cc753977(WS.10).aspx

First off, I recommend against using Local Policies in a domain environment. One of the reasons for using Group Policies is the one-to-many administration that you get. Should you utilize local policies, you will have to visit each client manually. Local Policies should only be used in a work group environment of 10 or less clients. Here is how you manage them. • Click Start • Type MMC and press Enter. • Click File and then Add/Remove Snap-in… • Select Group Policy Object and click Add. At this point, we can decide wheich of the policies we want to configure. • Click Browse. • Click the Users tab. You can now choose to modify the local policy for a specific user, users who have local administrator rights, or users who do not have local administrator rights. • Click OK and then Finish When a user logs on to this client, the appropriate local policy will be applied.

One of the challenges that one of you mentioned was the difficulty in enumerating the settings in a GPO in a convenient way. Below is a procedure to try one your Windows Server 2008 R2 domain controllers. It uses PowerShell to extract the data for you. · Log in to the DC. · Click Start à Windows PowerShell Modules . · Type Get-GPOReport –Name NameOfGPO – ReportType HTML –Path Destination and file name . Open the HTML file that was generated. The only values in the policy that are shown are the values that have been set. Also, if the name of your GPO has a space in it, enclose the name in double quotes. Below is an example of a policy that configured WSUS. Links Location Enforced Link Status Path None This list only includes links in the domain of the GPO. Security Filtering The settings in this GPO can only apply to the following groups, users, and computers: Name NT AUTHORITY\Authenticated Users Delegation

AD RMS (Rights Management Services), allows your users to designate who can do what with the content they create from Rights aware applications. For example, who can read a document and who can print it. This is done without IT staff making any changes to NTFS file permission. AD RMS works with Windows Vista, Windows 7, and Windows Server 2008. You can also utilize AD RMS with Windows XP, 2000, 2003. To do this, you wil need to download a separate version from Microsoft. The following link will direct you to the correct download for your platform: http://technet.microsoft.com/en-us/library/cc731051.aspx .

Supported Server Operating Systems The following server operating systems are supported on Hyper-V: Windows Server 2008 R2 (VM configured with 1, 2, or 4 virtual processors) Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Web Server R2 2008 Windows Server 2008 x64 Edition (VM configured with 1, 2, or 4 virtual processors) Windows Server 2008 Standard x64 Windows Server 2008 Enterprise x64 Windows Server 2008 Datacenter x64 Windows Web Server 2008 x64 Windows Server 2008 HPC Edition x64 Windows Server 2008 Standard without Hyper-V x64 Windows Server 2008 Enterprise without Hyper-V x64 Windows Server 2008 Datacenter without Hyper-V x64 Windows Server 2008 x86 (VM configured with 1, 2, or 4 virtual processors) Windows Server 2008 Standard x86 Windows Server 2008 Enterprise x86 Windows Server 2008 Datacenter x86 Windows Web Server 2008 x86 Windows Server 2008 HPC Edition x86 Windows Server 2008 Standard without Hyper-V x86 Windows