Good afternoon Indianapolis!

Thank you for such a great day! Thank you for all coming to my event, I had a great time and I hope everyone else did! Before I get to the great questions that you asked, I do have some resources to share with everyone. I mentioned a few things, where can you get presentation slides; my web cast series on group policy...etc.

As promised here are the questions from the event.

If I missed any question please comment to this blog and let me know what I can do to help.

Q: What are the requirements for secure messaging for Microsoft Exchange 2007?
A:
This is referred to as Edge-to-Edge mail flow. Edge-to-edge mail flow refers to mail that is sent between two different Exchange 2007 organizations that have deployed message security features, and established a trust relationship between their organizations. This relationship is managed by a single Hub Transport server in the Exchange 2007 organization, called the Message Security Manager. Edge-to-edge mail flow affects mail flow primarily by changing the characteristics of inbound mail flow and outbound mail flow. The Message Security Manager manages the certificates, encryption, and decryption policies and distributes the latest certificates, encryption, and decryption policies to all Edge Transport servers. After a trusted connection is established, inbound and outbound mail flow do not significantly change in terms of how mail is sent and received by an organization. However, some characteristics of inbound and outbound mail flow change, depending on how an organization has configured Message Security features.

Q: Where can I find more information on Microsoft Exchange 2007 Roles, specifically the Edge Services and the Unified messaging roles?
A:
There is an excellent role guide here: http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/de468880-4a6b-42dd-837c-64b974d7da59.mspx?mfr=true .

Specifically here are the overview pages for the roles you asked about:

Q: What version of Windows do you need to manage Windows Vista group policies from Group Policy Management Console GPMC?
A:
To manage the new Windows Vista–based or Windows Server "Longhorn"–based policy settings you need Windows Vista–based or Windows Server "Longhorn"–based administrative machines running Group Policy Object Editor or Group Policy Management Console. Such policy settings are defined only in ADMX files and, as such, are not exposed on the Windows Server 2003, Windows® XP, or Windows 2000 versions of these tools. An Administrator will need to use the Group Policy Object Editor from a Windows Vista–based or Windows Server "Longhorn"–based administrative machine to configure a new Windows Vista–based Group Policy settings. There is some good information here: http://www.microsoft.com/technet/WindowsVista/library/ops/ca393b34-2afa-46ae-bb1d-7fe9409eb360.mspx?mfr=true

Q: Where can I find more information on the Windows Vista Activation program?
A:
There is a good FAQ here: http://windowshelp.microsoft.com/Windows/en-US/Help/62088be6-3538-46a6-99fb-05e74aeb48b51033.mspx
this is straight from the FAQ, and I remember this question coming up:

  • How many times can I install Windows on my computer before I have to activate Windows again?
    You can reinstall Windows on the same computer as many times as you want because activation pairs the Windows product key with information about your computer's hardware. If you make a significant hardware change, you might have to activate Windows again.

Q: What is the scope of email Life Cycle management i.e. is the settings per-server or organization wide?
A:
You can actually set it all levels from Organization, to server, to mailbox. Here is the documentation from the help file for Microsoft Exchange 2007. It is still in writing so when the product releases this may change:

Turning Off E-Mail Lifecycle Management for Individual Mailboxes

In later releases of Exchange 2007, there will be additional functionality to suspend message expiration for individual mailboxes. Until then, you can stop e-mail lifecycle management for a mailbox by using the Exchange Management Shell to set the value of the ElcMailboxPolicy parameter for the mailbox to $null. This turns off e-mail lifecycle management for all the Default Folders in the mailbox. However, it does not turn off e-mail lifecycle management for the Organizational Folders in the mailbox. In the M4 DF2 release of Exchange 2007, e-mail lifecycle management for Organizational Folders must be turned off at the user level.

Important Note:
After the ElcMailboxPolicy parameter for the mailbox is set to $null, e-mail lifecycle management (that is, expiration and AutoCopy policies) continue to be enforced on any Organizational Folders in the mailbox. This is because those folders may still contain content for which retention policies apply. However, after the ElcMailboxPolicy parameter for the mailbox is set to $null, the user can delete all the Organizational Folders in the mailbox. Organizational Folders are never deleted automatically because they may contain content, or because the user may want to continue to use them.

Turning Off ELC Management Temporarily for Individual Servers

There are two ways in which you can stop the ELC Assistant from running on a server:

  • Clear its schedule in the Exchange Management Console.
  • Set the -ElcSchedule parameter of the Set-MailboxServer command to $null in the Exchange Management Shell.

When you stop the server's ELC Assistant, ELC Content Settings are no longer applied to mailbox folders on that server. No new Organizational Folders are created, and expiration and AutoCopy policies are not enforced. However, folder quotas continue to be enforced.

Turning Off ELC Management Permanently for an Entire Organization

To eliminate e-mail lifecycle management for an organization, delete all its ELC Folder objects. After this has been completed, folder quotas, expiration, and AutoCopy policies are not enforced, and the ELC root folder and all the Organizational Folders are converted into normal folders that can be moved, renamed, or deleted by the user.