*a manual disaster recovery process used to recover from a complete site failure
*not automatic but can be automated.
*goal: make sure you have a copy of data and someone can bring it up
*not just technology: people, process, and the procedures... these along with the technology will allow for successful site resilience
*what is the cost of losing your HA solution? make sure this out weighs the the cost for putting in SR. You can also do SR for dedicated DBs.
*IE has 20 min cache for address, you can set your DNS TTL for OWA down to 5 sec, but you won't get a redirect unless you close out IE and reOpen
*The failback URL, make sure to include failback URL.
Thursday, May 19, 2011
Microsoft Exchange Online in Microsoft Office 365: Migration Case Study
*860K mailboxes moved from on prem to o365.
*interesting strategy: user's online accounts were created, dial tone mailboxes were created, user data was imported in separately. this strategy allowed the migration to happen very fast. the school/districts involved had tools to migrate exchange data to online solution - 180 schools/entities were uploading data concurrently. early on during the pilot test, full armor (vendor) noticed that the data export was failing - b/c so much data was coming into online service, the hosted system saw this as DOA and closed down the connection. the lesson learned here is to work with the migration specialist from MS prior to migrating your data
*full armor wrote up a tool that aids in migration, Quest now owns it and it's downloadable
*interesting strategy: user's online accounts were created, dial tone mailboxes were created, user data was imported in separately. this strategy allowed the migration to happen very fast. the school/districts involved had tools to migrate exchange data to online solution - 180 schools/entities were uploading data concurrently. early on during the pilot test, full armor (vendor) noticed that the data export was failing - b/c so much data was coming into online service, the hosted system saw this as DOA and closed down the connection. the lesson learned here is to work with the migration specialist from MS prior to migrating your data
*full armor wrote up a tool that aids in migration, Quest now owns it and it's downloadable
Microsoft Lync 2010: Core Voice Planning and Deployment
New features:
*CAll Park
*Unassigned numbers
-handles numbers that are valid for your org but not assigned t0 a user phone
-you can transfer these calls to a predetermined destination
-create and manage an unassigned number
*location and enhanced 911
-now includes a location information server (LIS) for clients that require locations
-populate LIS DB with (in order of preference): wireless access point (BSSID), LLDP orot, LLDP switch, subnet, MAC
-you can configure LIS with powershell
-LIS is required for 911 enabling and routing
-will need to partner with e911 partner
-will work with IM
-can be used for location based emergency routing outside of US
*Private line:
-not listed on AD
-bypass most inbound call routing rules
-calls will fail if coming from ocs 2007 R2, this feature uses a new attribute
*Caller ID presentation controls
-you can configure caller id mask per trunk
*Monitoring
*Common Area Phone support
-enables low cost iP phones to be placed in common area
*IP Phone Infrastructure requirements
-LLDP-MED supported
-POE supported
-DNS requirement is the same as R2
-DHCP requirements are new:
*Analog Device Management
*Voice Routing - Trunk Translation
*Media Service Colocation
-you can consolidate meditation servers in the central DC
*malicious call trace
*Exchange UM
-only supported UM for lync
-will support exchange 2007 sp1 and beyond
-will support multiple forest: lync can be in one and exchange can be in the other
-hosted EUM as part of O365 is also now supported
-need to configure edge for shared domain when using o365
Routing and setup:
*dial plans:
-require e.164
-lync clients normalized dialed number before the yare sent to the server
-normalization rules are specified using regular expression
*planning for dial plans
-identify all areas within tghe organization that have local dialing requirements
-identify the valid number patterns for each
-try to standardize on an or wide scheme
-determine dial plan scope
-dial plans are obtained by UC clients through the inband provisioning process via the scope of the dial plan policy
*CAll Park
*Unassigned numbers
-handles numbers that are valid for your org but not assigned t0 a user phone
-you can transfer these calls to a predetermined destination
-create and manage an unassigned number
*location and enhanced 911
-now includes a location information server (LIS) for clients that require locations
-populate LIS DB with (in order of preference): wireless access point (BSSID), LLDP orot, LLDP switch, subnet, MAC
-you can configure LIS with powershell
-LIS is required for 911 enabling and routing
-will need to partner with e911 partner
-will work with IM
-can be used for location based emergency routing outside of US
*Private line:
-not listed on AD
-bypass most inbound call routing rules
-calls will fail if coming from ocs 2007 R2, this feature uses a new attribute
*Caller ID presentation controls
-you can configure caller id mask per trunk
*Monitoring
*Common Area Phone support
-enables low cost iP phones to be placed in common area
*IP Phone Infrastructure requirements
-LLDP-MED supported
-POE supported
-DNS requirement is the same as R2
-DHCP requirements are new:
*Analog Device Management
*Voice Routing - Trunk Translation
*Media Service Colocation
-you can consolidate meditation servers in the central DC
*malicious call trace
*Exchange UM
-only supported UM for lync
-will support exchange 2007 sp1 and beyond
-will support multiple forest: lync can be in one and exchange can be in the other
-hosted EUM as part of O365 is also now supported
-need to configure edge for shared domain when using o365
Routing and setup:
*dial plans:
-require e.164
-lync clients normalized dialed number before the yare sent to the server
-normalization rules are specified using regular expression
*planning for dial plans
-identify all areas within tghe organization that have local dialing requirements
-identify the valid number patterns for each
-try to standardize on an or wide scheme
-determine dial plan scope
-dial plans are obtained by UC clients through the inband provisioning process via the scope of the dial plan policy
locking down outlook anywhere by device
look into using ipsec w/certificate:
http://technet.microsoft.com/en-us/network/bb531150a
http://technet.microsoft.com/en-us/network/bb531150a
Microsoft Exchange Online in Microsoft Office 365: Simple Migration Live!
(this lectures applies to more med/small size companies)
*office 365 includes tools for planning
*not interoperable with BES (send as permissions are not migrated over), announcement has been made that BES will be supported in the future
*hybrid/staged mode offers more reach features, with journal rules, transport rules..
*cutover: for migrations with less than 1000 users, require outlook anywhere, public 3rd party cert, identity management in the cloud, review docs from http://help.outlook.com/
*demo:
-the migration tools offer a reporting capability similar to mailbox move reports from on prem version
*staged:
-requirements: require directory sync
-allows for migration in phases
-the planning is different from cutover, you have to specify the users you want to migrate within a CSV file where as in cutover, you discover them.
-when you kick off the sync, the emails are forwared to a migrated user on O.365, no need for final delta sync
-first phase of mailbox copy: copy of all folder structure, start from latest item to the oldest item
-incremental sync phase: copy the delta
*troubleshooting tips:
-performance issue: why is the migration so slow? limiting factors: proc, memory, disk IO and network latency and bandwidth. You can adjust throttle by adjusting concurrent moves. you can load balance your source site,
-connectivity: you can use test exchange connectivity tool. one common error is 'unable to set targetAddress' this is because you are using the wrong migration mode. if you have exchange 2010/2010 sp1 you should use hybrid. User mail not migrated:(1) due to large size (greater than 24mg), (2)due to bad items
-client side requirements: user needs to run connector, once this is installed, it allows the user to connect to o365. the connector tool also will move rules, this tool will try to fix the rules if it's broken and will involve users input
-Not migrate: send as permissions, dumpuster, dynamic DL, public folder, you can't go back - will not migrate back
-hybrid (download EXL311)
*office 365 includes tools for planning
*not interoperable with BES (send as permissions are not migrated over), announcement has been made that BES will be supported in the future
*hybrid/staged mode offers more reach features, with journal rules, transport rules..
*cutover: for migrations with less than 1000 users, require outlook anywhere, public 3rd party cert, identity management in the cloud, review docs from http://help.outlook.com/
*demo:
-the migration tools offer a reporting capability similar to mailbox move reports from on prem version
*staged:
-requirements: require directory sync
-allows for migration in phases
-the planning is different from cutover, you have to specify the users you want to migrate within a CSV file where as in cutover, you discover them.
-when you kick off the sync, the emails are forwared to a migrated user on O.365, no need for final delta sync
-first phase of mailbox copy: copy of all folder structure, start from latest item to the oldest item
-incremental sync phase: copy the delta
*troubleshooting tips:
-performance issue: why is the migration so slow? limiting factors: proc, memory, disk IO and network latency and bandwidth. You can adjust throttle by adjusting concurrent moves. you can load balance your source site,
-connectivity: you can use test exchange connectivity tool. one common error is 'unable to set targetAddress' this is because you are using the wrong migration mode. if you have exchange 2010/2010 sp1 you should use hybrid. User mail not migrated:(1) due to large size (greater than 24mg), (2)due to bad items
-client side requirements: user needs to run connector, once this is installed, it allows the user to connect to o365. the connector tool also will move rules, this tool will try to fix the rules if it's broken and will involve users input
-Not migrate: send as permissions, dumpuster, dynamic DL, public folder, you can't go back - will not migrate back
-hybrid (download EXL311)
Wednesday, May 18, 2011
Lync & Exchange
*it's been announced that a IOS client for Lync will be released before the end of year
BOF12-ITP - Exchange Unified Messaging
*update language packs often for the voice recognition/transcription
*prevent VMs being forwarded by using naming convention of the VMs - use a transport rule
*load testing UM - difficult to do, you must be able to test from the gateway
*top 5 gotchas:
-gateway selection
-know what you are providing to your users
-reverse lookup of the number, related to some translation on the PBX side, you may have a extra digit and the number does not match the number on the directory or the contact
-mis use of sip secure, sip URI, extension... with Lync integration is easy - make sure you have the right certificates
*MWI
-not all versions of cisco has been tested with UM
-make sure you communicate with cisco cm team for any updates
-solid network connection, look for acknowledgement
-UM exchange telephony advisor
*prevent VMs being forwarded by using naming convention of the VMs - use a transport rule
*load testing UM - difficult to do, you must be able to test from the gateway
*top 5 gotchas:
-gateway selection
-know what you are providing to your users
-reverse lookup of the number, related to some translation on the PBX side, you may have a extra digit and the number does not match the number on the directory or the contact
-mis use of sip secure, sip URI, extension... with Lync integration is easy - make sure you have the right certificates
*MWI
-not all versions of cisco has been tested with UM
-make sure you communicate with cisco cm team for any updates
-solid network connection, look for acknowledgement
-UM exchange telephony advisor
Tuesday, May 17, 2011
Best Practices for Virtualization of Microsoft Exchange 2010
key points (full notes are available from slide deck)
*snapshots are NOT supported. exchange is always moving forward in time
*VSS backup of root for pass through disks for iscsi disks connected to initiator in guest
*the new exchange calculator will account for virtualization
*don't forget network needs
*UM and Virtualization
-4 virtual proc is a must, lab tests shows poor voice quality, 40 concurrent connections tested fine with 4 VP/16GB memory
-Exchange is very multi CPU aware, take advantage of using as many vCPUs
-take advantage of HUB/MBX multirole deployment, there's a extra feature you get when you deploy these together (any benefit of combining MBX/CAS?)
*Storage considerations:
-Exchange storage must be fixed VHD
-Exchange storage must be block level, will not support NAS
*take advantage of the DAC mode available with 2010
*clustering the hytper v host:
-make sure to take account of heart beat time out for the DAG
-quick migration is not supported for exchange
-live migration is supported and complete shutdown and bringing it up on another machine is supported
*general guide line, dedicate resource for exchange do not set it for dynamic adjusting resources. the auto tuning adds no value to exchange.
*snapshots are NOT supported. exchange is always moving forward in time
*VSS backup of root for pass through disks for iscsi disks connected to initiator in guest
*the new exchange calculator will account for virtualization
*don't forget network needs
*UM and Virtualization
-4 virtual proc is a must, lab tests shows poor voice quality, 40 concurrent connections tested fine with 4 VP/16GB memory
-Exchange is very multi CPU aware, take advantage of using as many vCPUs
-take advantage of HUB/MBX multirole deployment, there's a extra feature you get when you deploy these together (any benefit of combining MBX/CAS?)
*Storage considerations:
-Exchange storage must be fixed VHD
-Exchange storage must be block level, will not support NAS
*take advantage of the DAC mode available with 2010
*clustering the hytper v host:
-make sure to take account of heart beat time out for the DAG
-quick migration is not supported for exchange
-live migration is supported and complete shutdown and bringing it up on another machine is supported
*general guide line, dedicate resource for exchange do not set it for dynamic adjusting resources. the auto tuning adds no value to exchange.
Monday, May 16, 2011
exchange 2010 UM now supported on hyper V!!
http://blogs.technet.com/b/exchange/archive/2011/05/16/announcing-enhanced-hardware-virtualization-support-for-exchange-2010.aspx
Exchange Server 2010 Tips and Tricks - Scott Schnoll, scott.schnoll@microsoft.com
announcements:
*UM roles are supported on Hyper V.(http://bit.ly/ke0lbw)
*kerberos authentication is recommended over default setting of 'negotiate', NTLM bottleneck (check http://t.co/fpd6sNa)
*SSL offloading updates: http://technet.microsoft.com/en-us/library/ee633481.aspx
*JetStress 1.0.0.11 (4/1/2011)
*IE9 breaks EMC,work around: this is a IE bug, you can use task manager to MMC.exe)
basics
*~70 million mailboxes are being hosted on cloud for this build
*support more languages than ever
*standard ed (up to 5 DBs/server), Enterprise (100 db/server), hybrid edition (only version you can use to connect your 2007 version to office 365, it acts as a gateway to connect to the cloud)
*exchange 2010 SP1 RU 3 has been pulled and updated twice! make sure you have version 3 (14.1.287.1)
planning/deployment tools
http://technet.microsoft.com/en-us/exdeploy2010
*includes tools for deploying to cloud and as well as hybrid mode
*updated mailbox server requirements calculator:14.4
*https://www.testexchangeconnectivity.com
scripts and troubleshooters
*Mailbox assistants troubleshooter (sp1) - repairs mailboxes on the backend (e.g., free busy, resource booking...)
-test-AssistantHealth (run with -ResolveProblems, starts the service or restarts the service if it's hung)
*Troubleshoot-Database.ps1 detects excessive log growth issues and takes actions
-this script will see if it's a user that's causing this problem
-defaults defined in 'storeTSConstants.ps1'
-looks at your top 25 users, you have an option to quarantine the users causing the log growth
-if the log generation is still an issue, the script will remove the database from provisioning
*Troubleshoot-databaseLatency.sp1 - this is being used by SCOM
-this will tell you if you are exceeding the threshold, you know if you are not pushing too much data and you are hitting the threshold, this could be a early sign of disk failure
*TroubleShoot-CI.ps1 - detects problems with content index catalogs
*Move-TransportDatabase.ps1 - useful for moving transport path for transport servers
the powershell (useful one liners)
get-queue | get-message | where {$_.messaegsubject -ewq "subject"} | remove-message
(use withNDR parameter to specify NDR ussage)
get-counter -computerName -counter "\msexchangeReplication (*)\contiunous replication =- block mode active"
0 = file mode
1 = block mode
get-date' get-mailboxserver | for each {$_.get-databasecopystatus -mailboxserver $_.identity - dumpsterstatisticcs | ? {$_.summarycopystatus ne 'mounted"}} | foreach {$_.dumpsterstatistics}
get-whitespace.ps1 - will be posted this later
getting all logon stats from outlook (logon time, last access time, client version, and adapter speed)
get-logonStatistics -server
*by default outlook 2010 doesnt transmit IP address or mac address, you have to create a registry entry - the key will be posted
*UM roles are supported on Hyper V.(http://bit.ly/ke0lbw)
*kerberos authentication is recommended over default setting of 'negotiate', NTLM bottleneck (check http://t.co/fpd6sNa)
*SSL offloading updates: http://technet.microsoft.com/en-us/library/ee633481.aspx
*JetStress 1.0.0.11 (4/1/2011)
*IE9 breaks EMC,work around: this is a IE bug, you can use task manager to MMC.exe)
basics
*~70 million mailboxes are being hosted on cloud for this build
*support more languages than ever
*standard ed (up to 5 DBs/server), Enterprise (100 db/server), hybrid edition (only version you can use to connect your 2007 version to office 365, it acts as a gateway to connect to the cloud)
*exchange 2010 SP1 RU 3 has been pulled and updated twice! make sure you have version 3 (14.1.287.1)
planning/deployment tools
http://technet.microsoft.com/en-us/exdeploy2010
*includes tools for deploying to cloud and as well as hybrid mode
*updated mailbox server requirements calculator:14.4
*https://www.testexchangeconnectivity.com
scripts and troubleshooters
*Mailbox assistants troubleshooter (sp1) - repairs mailboxes on the backend (e.g., free busy, resource booking...)
-test-AssistantHealth (run with -ResolveProblems, starts the service or restarts the service if it's hung)
*Troubleshoot-Database.ps1 detects excessive log growth issues and takes actions
-this script will see if it's a user that's causing this problem
-defaults defined in 'storeTSConstants.ps1'
-looks at your top 25 users, you have an option to quarantine the users causing the log growth
-if the log generation is still an issue, the script will remove the database from provisioning
*Troubleshoot-databaseLatency.sp1 - this is being used by SCOM
-this will tell you if you are exceeding the threshold, you know if you are not pushing too much data and you are hitting the threshold, this could be a early sign of disk failure
*TroubleShoot-CI.ps1 - detects problems with content index catalogs
*Move-TransportDatabase.ps1 - useful for moving transport path for transport servers
the powershell (useful one liners)
get-queue | get-message | where {$_.messaegsubject -ewq "subject"} | remove-message
(use withNDR parameter to specify NDR ussage)
get-counter -computerName
0 = file mode
1 = block mode
get-date' get-mailboxserver | for each {$_.get-databasecopystatus -mailboxserver $_.identity - dumpsterstatisticcs | ? {$_.summarycopystatus ne 'mounted"}} | foreach {$_.dumpsterstatistics}
get-whitespace.ps1
getting all logon stats from outlook (logon time, last access time, client version, and adapter speed)
get-logonStatistics -server
*by default outlook 2010 doesnt transmit IP address or mac address, you have to create a registry entry - the key will be posted
Exchange 2010 SP2: featuring GAL segmentation
four new features so far:
*owa mini
-administered through EMS: set-owamailboxpolicy name-owalightenabled:$true
-completed rewrite from ground up
-alternate version of owa interface
*hybrid configuration wizard: (marrying the on premise exchange w/office 365)
-visit session on Wed for a walk through rm206
-80%reduction work from before
*address book policies/GAL segmentation:
-reasons for using this feature: leagal compliance, optimization, hosting reasons
-the white paper posted for exchange 2007 will not work
-going from allow/deny model to direct assignment to the user
-when a user is connected and is part of the address book policy, the associated GAL will be visible
-no need for a OU hierarchy to manage the users for GAL
-you can create separate OABs based on the policies
-the address book policy assignment is part of the mailbox creation from EMC and EMS
-custom attributes are still the most affective way of setting filters for DLs
*Caveats
-outlook for MAC will not be subject to ABP (Address Book Policy), it accesses AD directly
-you can't put the CAS role on the GC as well
-if you span DLs over ABP, you need to disable group management in ECP as ECP uses get-group which ignores ABP
-ABP are not legal separation
-ABP does not hide lync presence across the org
*Random facts:
-second half of 2011, 20 Million lines of code written in 6-7 languages, more than half are for testing.
-forms based authentication is the key to single sign on when hosting multiple sites of AD
-check: https://blogs.technet.com/b/exchange
-sp2 tap is available
sp2 will involve schema changes
there are about 500 bug fixes for this one
*owa mini
-administered through EMS: set-owamailboxpolicy name-owalightenabled:$true
-completed rewrite from ground up
-alternate version of owa interface
*hybrid configuration wizard: (marrying the on premise exchange w/office 365)
-visit session on Wed for a walk through rm206
-80%reduction work from before
*address book policies/GAL segmentation:
-reasons for using this feature: leagal compliance, optimization, hosting reasons
-the white paper posted for exchange 2007 will not work
-going from allow/deny model to direct assignment to the user
-when a user is connected and is part of the address book policy, the associated GAL will be visible
-no need for a OU hierarchy to manage the users for GAL
-you can create separate OABs based on the policies
-the address book policy assignment is part of the mailbox creation from EMC and EMS
-custom attributes are still the most affective way of setting filters for DLs
*Caveats
-outlook for MAC will not be subject to ABP (Address Book Policy), it accesses AD directly
-you can't put the CAS role on the GC as well
-if you span DLs over ABP, you need to disable group management in ECP as ECP uses get-group which ignores ABP
-ABP are not legal separation
-ABP does not hide lync presence across the org
*Random facts:
-second half of 2011, 20 Million lines of code written in 6-7 languages, more than half are for testing.
-forms based authentication is the key to single sign on when hosting multiple sites of AD
-check: https://blogs.technet.com/b/exchange
-sp2 tap is available
sp2 will involve schema changes
there are about 500 bug fixes for this one
Thursday, June 10, 2010
new phones that will support communicator 14
home screen for one of the 5 phones that will be coming out for Communicator 14: (cx600)
Tuesday, June 8, 2010
finally some great announcements for Exchange 2010 SP1
log replication in sp1 has improved from file level copy to block level cluster replication which increses resilience against data loss in the event of active node failure!!
UNC01-INT - Real-World Database Availability Group (DAG) Design
Microsoft provides a great deal of content covering the theory around designing highly available and site resilient solutions, but there is very little discussion of how to apply that to “non-standard†customer scenarios. Not all customers have 50% of their users in one datacenter and 50% in a second datacenter, or one “hot datacenter†for all user access and one “warm datacenter†for site resilient scenarios. In this session, we apply the theory of DAG design and utilize the tools provided by Microsoft to design some real-world site resilient solutions. [TENA10]
Key points:
1. 250ms for acceptable latency for DAG
- This is important for log replication
- Stretch DAG isn’t meant to handle unreliable link
2. Where should we place fsw?
- If you want primary site to work in the event of outage, you want the FSW to be local
3. If for whatever reason the logs doesn’t play back on the passive nodes, you are better off deleting the copy
- you are better off reseeding it
4. when you take off nodes for 5 days, make sure count into storage for hosting that much logs
- unless, you cause some diversion the log, you shouldn’t have to reseed
- page patching, bad block – these are no longer an issue that requires a reseed
5. 2TB is recommended ceiling for .edb size in replicated environment
6. You can’t stretch DAG to cloud
7. In a odd # of dag you don’t have fsw
8. You can have mbx installed on with hub so you have extra voting members per data center – you don’t have to mount DB
**tomorrow’s dag session for SP1 – attend
Key points:
1. 250ms for acceptable latency for DAG
- This is important for log replication
- Stretch DAG isn’t meant to handle unreliable link
2. Where should we place fsw?
- If you want primary site to work in the event of outage, you want the FSW to be local
3. If for whatever reason the logs doesn’t play back on the passive nodes, you are better off deleting the copy
- you are better off reseeding it
4. when you take off nodes for 5 days, make sure count into storage for hosting that much logs
- unless, you cause some diversion the log, you shouldn’t have to reseed
- page patching, bad block – these are no longer an issue that requires a reseed
5. 2TB is recommended ceiling for .edb size in replicated environment
6. You can’t stretch DAG to cloud
7. In a odd # of dag you don’t have fsw
8. You can have mbx installed on with hub so you have extra voting members per data center – you don’t have to mount DB
**tomorrow’s dag session for SP1 – attend
UNC04-INT - Deploying Windows Rights Management Services (RMS) with Microsoft Exchange Server 2010 SP1, Step-by-Step
Exchange 2010 SP1 features several exciting new capabilities that leverage Rights Management Services (RMS). This interactive session helps you put these features into action. We’re ready to answer all your deployment questions. Using a live demonstration, we provide you with detailed guidance on how configure RMS settings and enable the IRM features in Exchange 2010. We also support the discussion with live demos and helpful troubleshooting tips so you can get up and running right away. [TENA10]
Key points:
1. With high overhead requirement of exchange 2010, RMS, outlook 2010 or Exchange 2010 OWA, this may not be ideal solution for us. We might find some usage for internal users to prevent accidental forwarding of messages unintended recipient but we would have to find out if Source One will work with email protection. Email protection changes the way protected emails are journaled in that it attaches 2 copies of the same message; one decrypted and the other encrypted. Another point to note is that email protection is not intended to protect against malicious user, it’s intended to protect against accidental forwarding of sensitive messages.
Key points:
1. With high overhead requirement of exchange 2010, RMS, outlook 2010 or Exchange 2010 OWA, this may not be ideal solution for us. We might find some usage for internal users to prevent accidental forwarding of messages unintended recipient but we would have to find out if Source One will work with email protection. Email protection changes the way protected emails are journaled in that it attaches 2 copies of the same message; one decrypted and the other encrypted. Another point to note is that email protection is not intended to protect against malicious user, it’s intended to protect against accidental forwarding of sensitive messages.
UNC307 - What's New in Archiving, Retention, and Discovery in Microsoft Exchange Server 2010 SP1
As the volume of email continues to increase, you are likely seeking new and better ways to preserve and discover this critical email data to meet an array of IT governance, legal, and compliance requirements. To help address these needs, Exchange Server 2010 introduced integrated archiving and discovery capabilities. This session offers a technical overview and demonstration of the features and functionality delivered in Exchange 2010 and updates coming in SP1. [TENA10]
Key points:
What’s new with sp1
1. Personal archive:
- Archive on separate db or in the cloud (if in the cloud, just point out the smtp address for it)
- Pst import into archive database
- Outlooks 2007 support for archive database
- Ews support for personal archive
- Admin delegation for personal archive
2. Move and delete policies (mailbox management)
- Managed through emc
- Ews support for archive
- Support for tasks calendar and voicemail
3. Hold policy:
- Managed through ecp
- Hold policy trumps over search and destroy admin tasks (in order to delete message that’s on hold, you would have to unhold)
4. Multi mailbox search:
- Search preview
- De duplication after discover
- Search and destroy
- Annotations
- Cmdlet audit
- Non-owner auditing
Other key points
1. Archive DB is just like any other Mail DB
- You can move archive mailbox to any other db using command lets
- Index for archive mailbox will exist on the new db
2. Pst finder available from ms
3. We have ability to manage retention on archive database.
4. Users can log in add additional retention policy for mailbox management
5. Automatically move content form the primary db to archive dumpster
6. Legal hold
- Doesn’t work on a group level from gui but can be scripted
- All activities done on /within mailbox is audited, even putting the user off hold and back on.
- One a user is on hold, nothing is deleted, and changes are tracked on the messages
7. Litigation search – search isn’t as sophistigated as source one.
- And, or, not queries works, AQS support, regular expressions work,
- Search by date, recipient & sender fields. You can’t specify attachment size and type. You can put extension type in the expression.
8. You can set retention policy per folder level
9. Default dumpster size is 28 days
- You can configure this, you can have separate policy from primary and archive
- The dumpster has its own size and quota, you have mechanism
10. When user gets moved from db another, dumpster follows
- The dumpster today is a indexed it’s a folder
11. “two prong authentication” Two person authorization for certain tasks (brought up, not delivered yet)
12. Demo of hold :
- Users can’t delete, the message. As long as the message is part of the store, you can’t delete it
- And, or, not queries works, AQS support, regular expressions work,
- New in sp1 is estimate of search time
- New in sp1 is dedup of search results
- Folder in the discovery search will have a folder created for the search, and also shows folder structure of where the message is
Questions:
1. When you have a retention policy of 1 year on the primary mailbox with delete nothing the dumpster, does mailbox management move the items in the dumpster older than 1 year to the dumpster on the archive mailbox database, assuming that I have the same policy on the archive database?
- Will the current storage calculator estimate how much storage I will need If I want to keep deleted items for 10 years for archive database?
2. How do you audit dumpster size on exchange 2007 db? Is there a way to breakdown disk utilization for deleted mailbox vs. deleted emails?
Key points:
What’s new with sp1
1. Personal archive:
- Archive on separate db or in the cloud (if in the cloud, just point out the smtp address for it)
- Pst import into archive database
- Outlooks 2007 support for archive database
- Ews support for personal archive
- Admin delegation for personal archive
2. Move and delete policies (mailbox management)
- Managed through emc
- Ews support for archive
- Support for tasks calendar and voicemail
3. Hold policy:
- Managed through ecp
- Hold policy trumps over search and destroy admin tasks (in order to delete message that’s on hold, you would have to unhold)
4. Multi mailbox search:
- Search preview
- De duplication after discover
- Search and destroy
- Annotations
- Cmdlet audit
- Non-owner auditing
Other key points
1. Archive DB is just like any other Mail DB
- You can move archive mailbox to any other db using command lets
- Index for archive mailbox will exist on the new db
2. Pst finder available from ms
3. We have ability to manage retention on archive database.
4. Users can log in add additional retention policy for mailbox management
5. Automatically move content form the primary db to archive dumpster
6. Legal hold
- Doesn’t work on a group level from gui but can be scripted
- All activities done on /within mailbox is audited, even putting the user off hold and back on.
- One a user is on hold, nothing is deleted, and changes are tracked on the messages
7. Litigation search – search isn’t as sophistigated as source one.
- And, or, not queries works, AQS support, regular expressions work,
- Search by date, recipient & sender fields. You can’t specify attachment size and type. You can put extension type in the expression.
8. You can set retention policy per folder level
9. Default dumpster size is 28 days
- You can configure this, you can have separate policy from primary and archive
- The dumpster has its own size and quota, you have mechanism
10. When user gets moved from db another, dumpster follows
- The dumpster today is a indexed it’s a folder
11. “two prong authentication” Two person authorization for certain tasks (brought up, not delivered yet)
12. Demo of hold :
- Users can’t delete, the message. As long as the message is part of the store, you can’t delete it
- And, or, not queries works, AQS support, regular expressions work,
- New in sp1 is estimate of search time
- New in sp1 is dedup of search results
- Folder in the discovery search will have a folder created for the search, and also shows folder structure of where the message is
Questions:
1. When you have a retention policy of 1 year on the primary mailbox with delete nothing the dumpster, does mailbox management move the items in the dumpster older than 1 year to the dumpster on the archive mailbox database, assuming that I have the same policy on the archive database?
- Will the current storage calculator estimate how much storage I will need If I want to keep deleted items for 10 years for archive database?
2. How do you audit dumpster size on exchange 2007 db? Is there a way to breakdown disk utilization for deleted mailbox vs. deleted emails?
Monday, June 7, 2010
UNC303 - Upgrading from Microsoft Exchange Server 2003/2007 to Exchange Server 2010: Tips, Tricks, and Lessons Learned
Rand Morimoto, author of the bestselling book "Exchange 2010 Unleashed" shares over two years of early adopter and real-world experience in upgrading from Exchange 2003 and Exchange 2007 to Exchange 2010. Rand covers strategies in preparing for a successful upgrade as well as common pits and traps to avoid in the process. [TENA10] – being taped
Resource: www.expta.com, www.networkworld.com/community/morimoto
- Search CAS
Key points:
1. Preparation tool:
- Exchange remote connectivity analyzer: test cas, smtp routing
- Exchange server deployment assiantant http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#Home
- Delegate configurations to look out for: CAS naming space and SSL certificates
- Changing out certificate on exchange 2007 for 2010 integration did not require a user to reauthenticate
- In a 2003/2007 environment, 2010 hub relays only with 2007 hub
- Exchange UM - you bring in 2010, you need new dial plan. Mailbox moves from 2007 to 2010 will require reconfiguration of UM for users
- OCS will automatically talk to 2010
- No public folder migration, replication is the way you migrate – this could take few days so plan it out
- PFAdmin is good tool for checking PF replication
- OWA public folder access only works with 2010
- You can move users during the day from 2007 to 2010 but you want to plan out how much (think about log generation and backups...)
- Cas server processes the mailbox moves. Once you submit move request, the cas server handles all move request at which point your machine is out of the loop
Concerns/unknowns:
1. Decomission steps for exchange 2007 in mixed mode
- You want to use setup.exe to properly remove the legacy environment
2. Plan to get mail.outlook.caa.com with ISA. We currently use outlook.caa.com, how will this impact users
- Current SAN used: outlook.caa.com, owa1.caa.com, owa2.caa.com, autodiscovery.caa.com,
- Going to: mail.caa.com, autodiscovery.caa.com, legacy.caa.com
3. Can bes 5.0 MR1 application deliver mail for users on both 2007/2010 env?
Resource: www.expta.com, www.networkworld.com/community/morimoto
- Search CAS
Key points:
1. Preparation tool:
- Exchange remote connectivity analyzer: test cas, smtp routing
- Exchange server deployment assiantant http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#Home
- Delegate configurations to look out for: CAS naming space and SSL certificates
- Changing out certificate on exchange 2007 for 2010 integration did not require a user to reauthenticate
- In a 2003/2007 environment, 2010 hub relays only with 2007 hub
- Exchange UM - you bring in 2010, you need new dial plan. Mailbox moves from 2007 to 2010 will require reconfiguration of UM for users
- OCS will automatically talk to 2010
- No public folder migration, replication is the way you migrate – this could take few days so plan it out
- PFAdmin is good tool for checking PF replication
- OWA public folder access only works with 2010
- You can move users during the day from 2007 to 2010 but you want to plan out how much (think about log generation and backups...)
- Cas server processes the mailbox moves. Once you submit move request, the cas server handles all move request at which point your machine is out of the loop
Concerns/unknowns:
1. Decomission steps for exchange 2007 in mixed mode
- You want to use setup.exe to properly remove the legacy environment
2. Plan to get mail.outlook.caa.com with ISA. We currently use outlook.caa.com, how will this impact users
- Current SAN used: outlook.caa.com, owa1.caa.com, owa2.caa.com, autodiscovery.caa.com,
- Going to: mail.caa.com, autodiscovery.caa.com, legacy.caa.com
3. Can bes 5.0 MR1 application deliver mail for users on both 2007/2010 env?
UNC201 - Microsoft Exchange Server 2010 SP1: An Overview of What's Coming
**class was very disappointing, instructor only mentioned few items about sp1.
General Manager of Exchange Server, Harvinder Bhela, talks about (and demos) key investments in Exchange Server 2010 and SP1 and how Exchange provides unprecedented IT cost savings; the richest user experience across the PC, phone, and browser; and better management of risk through built-in protection and compliance features. This session covers key topics including archiving and tiered storage; low cost disk use and the expansion of mailbox size while reducing costs; Unified Messaging and Voicemail Preview, and much more. Learn more about how Exchange Server 2010 SP1 delivers powerful productivity tools to your users in a way that best fits your business and technology needs. [TENA10]
Key points:
1. ‘Mailbox resiliency’ is the coin term
2. You can have up to 16 replicas
3. One place to manage sms and IM
4. Contact cards on outlook seamless format from OC
5. Option to now store archive mailboxes on separate mail store
6. You can set granular per item retention policies and capture all edits and deletions with legal hold
7. Empower compliance officers to conduct multi mailbox searches with ease
8. Exchange 2010 provides information protection:
- Transport protection rule – this automatically applies to based on senders, expression matching attachments..
- You can temporarily decrypt the message on the server, this way you can journal and archive, message are content indexed on exchange. So there is no compromise with availability and ILM, exchange 2010 solves this issue
- ILM you can protect message from getting forwarded – limitation here is that still users set which message is protected
- There is more support for mobile phones now for ILM
9. You can mix mode for on prem and cloud model
10. Help users manage inbox overloads
11. uM across email, IM, voice mail saves time
12. address book segregation will be available sometime in the second half of year
New in SP1:
1. Ability to estimate search time new in sp1
2. You can dedup results from search
3. You can tweak the search
4. Annotate the results
5. Released date, second half of the year
General Manager of Exchange Server, Harvinder Bhela, talks about (and demos) key investments in Exchange Server 2010 and SP1 and how Exchange provides unprecedented IT cost savings; the richest user experience across the PC, phone, and browser; and better management of risk through built-in protection and compliance features. This session covers key topics including archiving and tiered storage; low cost disk use and the expansion of mailbox size while reducing costs; Unified Messaging and Voicemail Preview, and much more. Learn more about how Exchange Server 2010 SP1 delivers powerful productivity tools to your users in a way that best fits your business and technology needs. [TENA10]
Key points:
1. ‘Mailbox resiliency’ is the coin term
2. You can have up to 16 replicas
3. One place to manage sms and IM
4. Contact cards on outlook seamless format from OC
5. Option to now store archive mailboxes on separate mail store
6. You can set granular per item retention policies and capture all edits and deletions with legal hold
7. Empower compliance officers to conduct multi mailbox searches with ease
8. Exchange 2010 provides information protection:
- Transport protection rule – this automatically applies to based on senders, expression matching attachments..
- You can temporarily decrypt the message on the server, this way you can journal and archive, message are content indexed on exchange. So there is no compromise with availability and ILM, exchange 2010 solves this issue
- ILM you can protect message from getting forwarded – limitation here is that still users set which message is protected
- There is more support for mobile phones now for ILM
9. You can mix mode for on prem and cloud model
10. Help users manage inbox overloads
11. uM across email, IM, voice mail saves time
12. address book segregation will be available sometime in the second half of year
New in SP1:
1. Ability to estimate search time new in sp1
2. You can dedup results from search
3. You can tweak the search
4. Annotate the results
5. Released date, second half of the year
Key Note Session
Key points:
1. .net 4 available as of today
2. RTN application fabric is available as today for download
3. Sql 2008 R2 recently released
4. Win 2008 r2 sp1 & win 7 sp1 to be released sometime july time frame
Shipping dynamic memory and remote FX (HD quality video)
5. Cloud computing and UC
a. Comprising office 2010, sharepoint 2010, exchange 2010
b. Updates with communication 14
- More personal client view
- Improved status, mimicing more social networking tools with photo and status
- Contact card photos will be from share point
- Communicator history enabling user to jump in old threads as needed
- Better interface for soft phone
- Play VM from exchnge UM
- Ability to search for key words that will work with share point to bring up people results that related to the data. Looking up guru for certain topic for instance
- Contact cards, always present when hovering over name
- Presence is right next to photo
- 720p HD video capability for video conferencing: you can policy out IQ mode based on bandwidth availability
- Ability to share and white board docs while in a call
-
6. Windows 7 phone
a. Simple interface with ‘smart cards’
b. Email flagging sync with phone
c. Integration with business systems like share point:
- Demo of pulling up a excel doc from a link, editing it, and saving it on share point
7. IE 9
a. Allows html 5, experiene is faster, and will feature graphic acceleration
8. Windows intune – desktop management tool for cloud services
a. Manage things like inventory, patching and antimalware
9. Bing MAP SDK release today
a. Bing MAP demo of incorporating movie distribution to Bing MAP
10. Business Intelligence and the cloud
a. Much improvements with Excel 2010 that enables ease of bringing data from difference sources together
- Demo: resorting a table with 100 miliion rows in matter of few seconds
- can pull data from SQL Azure and any open source type of db
- can upload and save t share point which will allow use of tools like SQL analysis – users can then quickly and easily pull reports and graphs
11. key take away message for cloud computing – scaling infrastructure based on utilization and not peak capacity. Find out more about Azure
1. .net 4 available as of today
2. RTN application fabric is available as today for download
3. Sql 2008 R2 recently released
4. Win 2008 r2 sp1 & win 7 sp1 to be released sometime july time frame
Shipping dynamic memory and remote FX (HD quality video)
5. Cloud computing and UC
a. Comprising office 2010, sharepoint 2010, exchange 2010
b. Updates with communication 14
- More personal client view
- Improved status, mimicing more social networking tools with photo and status
- Contact card photos will be from share point
- Communicator history enabling user to jump in old threads as needed
- Better interface for soft phone
- Play VM from exchnge UM
- Ability to search for key words that will work with share point to bring up people results that related to the data. Looking up guru for certain topic for instance
- Contact cards, always present when hovering over name
- Presence is right next to photo
- 720p HD video capability for video conferencing: you can policy out IQ mode based on bandwidth availability
- Ability to share and white board docs while in a call
-
6. Windows 7 phone
a. Simple interface with ‘smart cards’
b. Email flagging sync with phone
c. Integration with business systems like share point:
- Demo of pulling up a excel doc from a link, editing it, and saving it on share point
7. IE 9
a. Allows html 5, experiene is faster, and will feature graphic acceleration
8. Windows intune – desktop management tool for cloud services
a. Manage things like inventory, patching and antimalware
9. Bing MAP SDK release today
a. Bing MAP demo of incorporating movie distribution to Bing MAP
10. Business Intelligence and the cloud
a. Much improvements with Excel 2010 that enables ease of bringing data from difference sources together
- Demo: resorting a table with 100 miliion rows in matter of few seconds
- can pull data from SQL Azure and any open source type of db
- can upload and save t share point which will allow use of tools like SQL analysis – users can then quickly and easily pull reports and graphs
11. key take away message for cloud computing – scaling infrastructure based on utilization and not peak capacity. Find out more about Azure
Subscribe to:
Posts (Atom)