I have much less of an _in_ than you might think, except where Exchange documentation is concerned, and to a lesser degree AD documentation.
As a long term goal, I can tell you that MSFT wants less and less corporate knowledge contained in KB articles, and more and more in online documentation. I can also assure you that if you make comments on online documentation (other than white papers and KB articles), someone in a UE team will definitely read it, regardless of whether your comment is ever acknowledged. All documentation for current releases is on a quarterly web-refresh cycle (which is sometimes a PITA - I hate dead links). So if you can make a specific complaint or specific recommendation for improvement - there is a good chance that it'll show up in 3-6 months. Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Micheal Espinola Jr [mailto:[email protected]] Sent: Tuesday, January 27, 2009 3:22 PM To: NT System Admin Issues Subject: Re: Why is the min. rec. paging file size 1.5x? I know you have an *in* with Microsoft, so I wonder if you could let someone know that there is significant amount of inconsistent information across the multiple articles in the KB, Technet, and even recent How-to Microsoft Press book excerpt articles on the subject that stll won't nail it down for people. Its a bit ridiculous, even for a techie - never mind a uninformed user. I wish I could have got the job in Redmond (almost, but lost out to another Sunbelt list user (I think)), so I could have had access to some of these ppl! Its really not that hard to find the bad material out there. Now, if only someone would fix it to a establish a consistent message. -- ME2 On Tue, Jan 27, 2009 at 3:05 PM, Michael B. Smith <[email protected]> wrote: > The 2mb/10mb addition is to give room to relocate enough memory for the dump > routines to execute. > > The default settings for the current OS's is "system managed". > > Regards, > > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP > My blog: http://TheEssentialExchange.com/blogs/michael > I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php > > > -----Original Message----- > From: Micheal Espinola Jr [mailto:[email protected]] > Sent: Tuesday, January 27, 2009 3:03 PM > To: NT System Admin Issues > Subject: Re: Why is the min. rec. paging file size 1.5x? > > It still exists (the 1.5x recommendation) in the most recent knowledge > base articles, and is the default setting for the current OS's. > > And of course, back in the day, something threw in the +2mb addition, > which I dont think I ever understood. If someone can recall the > reasoning behind that as well, I'd love a reminder! :-) > > -- > ME2 > > > > On Tue, Jan 27, 2009 at 2:54 PM, Kennedy, Jim > <[email protected]> wrote: >> IIRC the 1.5 was back when we had smaller amounts of ram...because the > initial foot print of the OS's in RAM was pretty big in comparison to the > smaller amount of ram of the days. I think that this rule of thumb has just > hung on over the years. >> >> >> >>> -----Original Message----- >>> From: Micheal Espinola Jr [mailto:[email protected]] >>> Sent: Tuesday, January 27, 2009 2:49 PM >>> To: NT System Admin Issues >>> Subject: Why is the min. rec. paging file size 1.5x? >>> >>> My memory is failing me as to why the recommended minimum paging file >>> is 1.5x >>> RAM. Why not 1x or 2x? Why 1.5x specifically? >>> >>> I'm almost positive I used to know why - but my google-fu and personal >>> list archive are also failing me today. >>> >>> I'm interested because I've got a new junior subboardinate whom I'm >>> trying to instill a general understanding of concepts with, along with >>> the benefits of creating and using a personal reference database. >>> Plus, I hate not knowing the "why" for something... :-) >>> >>> Here are my current notes on paging file optimization: >>> >>> http://www.espinola.net/wiki/Paging_file_optimization >>> >>> Not detailed (yet), but they are to the point. Would anyone care to >>> take a peek and tell me if I'm missing something? >>> >>> TIA! >>> >>> -- >>> ME2 >>> >>> ~ 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/> ~
