Telling them that emailing a link is just as easy as sending the attachment only goes so far - most L-users are so used to sending attachments form their personal email activity they just can't break the habit plus not everyone that they communicate with can access that cute wmv file stored in the root of their departments critical apps folder, YMMV ;->
John W. Cook Systems Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Office (352) 393-2741 x320 Cell (352) 215-6944 Fax (352) 393-2746 MCSE, MCTS, MCP+I, A+, N+, VSP -----Original Message----- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Friday, May 29, 2009 7:59 AM To: NT System Admin Issues Subject: RE: Amusing Hi, Deploy Sharepoint, and email links instead. :-) But as Brian has mentioned - it's working checking your actual SIS stats. I agree with what he has said - many places get a lot less out of SIS than they think they are. Cheers Ken ________________________________________ From: John Hornbuckle [john.hornbuc...@taylor.k12.fl.us] Sent: Friday, 29 May 2009 8:15 PM To: NT System Admin Issues Subject: RE: Amusing I don't think anyone thinks Ex 2010 sucks; it has a number of exciting new features. I just think that for some (many?) shops, the SIS issue could have a significant negative impact. As I mentioned before, we're a 500-mailbox organization. Moving to Ex 2010 would require 500x the storage currently required every time an attachment is sent out organization-wide. Suddenly that 1 MB newsletter requires half a gig of storage. The 3 MB set of pictures requires 1.5 gigs. The 5 MB video clip requires 2.5 gigs. A few gigs here, a few gigs there--it starts to add up in a hurry. I can easily see our database size increasing dramatically from where it currently is, although this should be mitigated by compression (hopefully SIGNIFICANTLY mitigated). John -----Original Message----- From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Thursday, May 28, 2009 9:46 PM To: NT System Admin Issues Subject: RE: Amusing OK so before we go down the Exchange 2010 sucks because I think I need single instance [attachment] storage route, let's look at some other new stuff: --> Threaded conversation view (ala GMAIL) in Outlook Web Access --> Substantial filtering choices in Outlook Web Access --> Conversation "muting" in Outlook Web Access (ignores a thread and put it out of view) --> Mail Tips in Outlook Web Access - tells you prior to sending a mail things like the destination mailbox is over quota, you don't have permission to mail a mailbox, a recipient is OOF, a DL has more than K recipients, an external recipient is on a To list with all internal recipients, etc --> Favorite folders in OWA --> Delegate mailbox access in OWA --> Side by Side calendaring in OWA --> Full Outlook Web Access "Premium" feature parity across IE7+/FF3/Safari --> Note S/MIME is only supported in IE --> Voicemail preview transcribes voicemails delivered to Exchange. This lets you preview the message without listening and search. --> You also can do things like my cell phone (T-Mobile) voicemail goes to my Exchange Inbox with this --> Voicemail allows you to create rules based messages and auto attendants (e.g. if Brian calls, tell him I'm away and transfer him to Carrie, or IVR menus e.g. Press 1 to X, press 2 to Y, etc) --> Instant messaging (MSN or OCS) is integrated into OWA for text, SMS, and voice --> Presence information is integrated into OWA --> Calendar federation lets you see free/busy data for business partners --> E-Mail archiving lets users have two mailboxes (in Outlook and OWA) and lets you store archive data in the separate mailbox --> Retention policies can move that data to the archive automatically --> Users can drag and drop PSTs into the archive --> Legal holds can be placed on messages --> Compliance people (your legal folks, etc) can be delegated rights to do eDiscovery searches across the organization via Outlook Web Access. --> Transport rules can apply permissions and rights management to messages as they pass through the system --> You can integrate and manage Exchange Online (off-prem) and your own Exchange (on-premise) through one console --> Distribution Lists can be self service managed (created, member managed, moderated) by users in Outlook Web Access --> Users can add external recipients to these DLs --> Windows Mobile will be able to update certain components over the air from Exchange --> Text Message (SMS) sync/integration between phone and mailbox --> Text messaging rules that allow Exchange to SMS your phone when events happen --> End user message tracking interface in OWA --> End user delivery confirmation/reporting interface in OWA Thanks, Brian Desmond br...@briandesmond.com c - 312.731.3132 -----Original Message----- From: John Hornbuckle [mailto:john.hornbuc...@taylor.k12.fl.us] Sent: Thursday, May 28, 2009 8:26 PM To: NT System Admin Issues Subject: RE: Amusing I agree with Ben's sentiment; these changes sound more beneficial to very large organizations. For those of us who are small shops, we might come out ahead keeping SIS. We have 500 mailboxes running on Exchange 2007 in a Hyper-V VM. Performance isn't an issue for us; e-mail is processed very quickly here. Storage, however, is another story; it always seems to be at a limited resource. John Hornbuckle MIS Department Taylor County School District www.taylor.k12.fl.us -----Original Message----- From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Thursday, May 28, 2009 6:35 PM To: NT System Admin Issues Subject: RE: Amusing The reason for this is that the design of the databases in Exchange 2010 has been changed very much so from prior releases. In prior releases you had a single table for messages, a single table for attachments, and so forth. This leads to A LOT of random I/O which is very expensive, especially on slower drives. In Exchange 2010, you have one table _per mailbox_ for folders, one per mailbox for message headers, and one per mailbox for bodies and so forth. What you get from this is huge gains in large sequential I/O because you have contiguous data. The page size has also been increased to 32KB (4-fold increase) which gets you a substantial reduction in I/O operations. Say you have a 26KB message. That's 4 reads in 2007, 1 read in 2010. If you're running in a scenario where you have high availability (the new DAG [Distributed Availability Group] design), the checkpoint depth has been increased substantially which gets a huge reduction in write operations. The build of Exchange 2010 that's available to the public now has a roughly 70% reduction in total IOPS per second. The numbers I'm looking at are for a scenario with 3000x250MB mailboxes with a very heavy user profile and 3MB of cache (RAM) allocated per user. That is a /huge/ performance gain. The net result here is that you can buy fewer cheaper disks, put substantially more users on them (think potential factor of 3-4), and deliver larger mailbox quotas. That's a win. Thanks, Brian Desmond br...@briandesmond.com c - 312.731.3132 -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Thursday, May 28, 2009 5:13 PM To: NT System Admin Issues Subject: Re: Amusing On Thu, May 28, 2009 at 5:50 PM, Brian Desmond <br...@briandesmond.com> wrote: > If 3,000 users all come after the same data in a short time window it's going > to be > in the cache which means it's served out of memory (not disk). RAM is way > faster than disk. Except that, from what you're saying, in Exchange 2010, there's no SIS, so there will be no benefit from caching stuff in RAM, because everybody has a unique copy of everything. Tell me again how this is an improvement? -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
