On 4/22/2010 9:59 PM, Jason D. McCormick wrote: > Jeff, > >> There is no work around. Microsoft has known about this bug since >> September 2009. More sites need to file bug reports on this issue with >> Microsoft. Until Microsoft is convinced that this is a serious problem >> they are not going to make it a priority. SP1 betas have already been >> cut and if this bug is going to be fixed and added to SP1, they need to >> hear from a broad range of OpenAFS using sites. >> >> There really is nothing more that I can do until Microsoft decides the >> problem is a serious problem for *their* customers. > > Can you point me to the bug report reference, number, whatever within > Microsoft to the issue? > We'll file a support request with MS Premier Support, we just need to now > want to send our TAM after.
Unfortunately, I can't provide one. I'm not allowed to disclose it. The best thing for you to do is to file a new report describing the symptoms as your site is experiencing them. You can provide [email protected] as a contact with the software vendor for the Microsoft support engineer to provide follow up. When a Microsoft support engineer initiates contact I can put them in touch with the developers that have been looking into the case. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
