|
Posted by gxdata on December 13, 2005, 3:55 am
Please log in for more thread options
: quoted-printable
I would suggest trying the MSN search weblog at =
http://blogs.msdn.com/msnsearch/default.aspx
and also the "tech" blog at http://spaces.msn.com/members/wdstech/
However, those guys aren't Support - they're developers or project =
managers. You might leave a comment, but it's not their job to provide =
answers or support. =20
There is a Support page where you can post your issues.
https://support.microsoft.com/common/survey.aspx?scid=3Dsw;en;1208&showpa=
ge=3D1&ws=3Dsearch =20
I must say that I have not had any satisfaction there. Just the reverse =
- I don't know how MS puts up with the contracted-out support which has =
no idea, and no interest in responding in a professional way.=20
I posted a remark about the (totally unsatisfactory) integration of the =
user interface for Enterprise version of WDS into the Windows XP SP2 =
search via Windows Explorer. I received a reply which was totally =
unrelated -=20
Thank you for contacting Microsoft Online Customer Service.
From your message and information, I understand you are located in =
Australia. There are significant programming differences between North =
American and localized versions of software. You will be best assisted =
by the subsidiary that specializes in your specific version. If you have =
obtained your Microsoft software in Australia, I suggest you contact =
Microsoft Australia as they are in a better position to assist you.=20
To contact Microsoft Australia, please visit ....=20
I should add that the email respondent's email adress was "Abuse at =
Microsoft" abuse@microsoft.com - obviously, my post was regarded as =
abusive, rather than a legitimate complaint with suggestions for =
remedies.=20
So, I contacted his manager, and received a similarly unhelpful and =
dismissive response:=20
I'm sorry you were not completely satisfied with the technical support =
you received. Our goal is that every customer be completely satisfied =
so we appreciate the feedback that you have offered. =20
Please continue to offer us feedback in the future as it is the only =
way we can know, what we are doing well and the areas in which we may =
need to improve.
Thank you for using Microsoft products and services.
I wish you luck!!=20
--=20
IL Thomas
>I have a small network (10 clients, 1 Windows 2003 File Server).
>=20
> When using the NON-enterprise version of WDS we found a big problem =
when=20
> saving large (and somtimes small) files. All the client machines have =
a=20
> mapped network drive from the server and all the WDS are set to index =
this=20
> drive.
>=20
> Let's say User1 begins to save a 30MB Excel file. The save time is =
about 35=20
> seconds and the whole time a randomly named temp file is being built =
which=20
> is eventually renamed to the original name of the file being saved. =
The=20
> problem we had was that the WDS Indexer on User2, User3, User4, etc... =
would=20
> start to index the TEMP file. The first user to start indexing the =
file=20
> would put a lock on the file and when Excel was done building the temp =
file=20
> and went to rename to the file to it's real name, a "Application =
Sharing=20
> Violation" error would be thrown.
>=20
> The problem would almost always happen with our 30MB file, but would=20
> randomly happen on other occasions with any number of other files in =
the=20
> share. The solution obviously ended up being "Turn off indexing of =
the=20
> network share".
>=20
> With the release of WDS Enterprise edition I expected a way of =
indexing=20
> mapped network drives that solved this problem. However, reading =
through=20
> the Windows Desktop Search Administration Guide gives me little hope.
>=20
> The "don't index these file types", which has always been an available =
> option, might be helpful except for the fact that the Excel temp files =
have=20
> no extension.
>=20
> I thought maybe there would be a multiple index solution involved. =
One=20
> where the server indexes it's own files and sends updates to the user=20
> indexes. Something like this would solve the problem of the over =
zealous=20
> user indexing as the server is the only machine indexing it's files =
and=20
> wouldn't index while there's hard drive activity. I can see where =
this=20
> would be a problem in larger organizations however because maybe hard =
drive=20
> activity never subsides.
>=20
> Anyway, is there any hope to get the mapped network drives indexed or =
am I=20
> out of luck?
> As others might not have run into this problem, and Microsoft Support =
never=20
> even thought to check this with me, I'm not sure the WDS development =
team=20
> knows about this problem. Maybe a [MSFT] person can chime in on that =
one.
>=20
> Thanks for your time,
> Jeremy=20
>=20
>
------=_NextPart_000_0023_01C60006.10AB1890
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>I would suggest trying the MSN =
search weblog=20
at </FONT><A href=3D"http://blogs.msdn.com/msnsearch/default.aspx"><FONT =
face=3DArial=20
size=3D2>http://blogs.msdn.com/msnsearch/default.aspx</FONT></A><BR><FONT=
=20
face=3DArial size=3D2>and also the "tech" blog at </FONT><A=20
href=3D"http://spaces.msn.com/members/wdstech/"><FONT face=3DArial=20
size=3D2>http://spaces.msn.com/members/wdstech/</FONT></A><BR><BR><FONT =
face=3DArial=20
size=3D2>However, those guys aren't Support - they're developers or =
project=20
managers. You might leave a comment, but it's not their job =
to=20
provide answers or support. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>There is a Support page where you can =
post your=20
issues.</FONT></DIV>
<DIV><A=20
href=3D"https://support.microsoft.com/common/survey.aspx?scid=3Dsw;en;120=
8&showpage=3D1&ws=3Dsearch"><FONT=20
face=3DArial=20
size=3D2>https://support.microsoft.com/common/survey.aspx?scid=3Dsw;en;12=
08&showpage=3D1&ws=3Dsearch</FONT></A><FONT=20
face=3DArial size=3D2> </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I must say that I have not had any =
satisfaction=20
there. Just the reverse - I don't know how MS puts up with the =
contracted-out=20
support which has no idea, and no interest in responding in a =
professional way.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I posted a remark about the (totally=20
unsatisfactory) integration of the user interface for Enterprise version =
of WDS=20
into the Windows XP SP2 search via Windows Explorer. I =
received a=20
reply which was totally unrelated - </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2>Thank you for contacting Microsoft =
Online=20
Customer Service.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>From your message and information, I =
understand=20
you are located in Australia. There are significant programming =
differences=20
between North American and localized versions of software. You will be =
best=20
assisted by the subsidiary that specializes in your specific version. =
If you=20
have obtained your Microsoft software in Australia, I =
suggest you=20
contact Microsoft Australia as they are in a better =
position to=20
assist you. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>To contact =
Microsoft Australia, please=20
visit .... </FONT></DIV></BLOCKQUOTE>
<DIV><FONT face=3DArial size=3D2>I should add that the email =
respondent's email=20
adress was "Abuse at Microsoft" <A=20
my post=20
was regarded as abusive, rather than a legitimate complaint with =
suggestions for=20
remedies. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>So, I contacted his manager, and =
received a=20
similarly unhelpful and dismissive response: </FONT></DIV><FONT =
face=3DArial=20
size=3D2>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV>I'm sorry you were not completely satisfied with the technical =
support=20
you received. Our goal is that every customer be completely =
satisfied so=20
we appreciate the feedback that you have offered. </DIV>
<DIV>Please continue to offer us feedback in the future as it is the =
only way=20
we can know, what we are doing well and the areas in which we may need =
to=20
improve.</DIV>
<DIV>Thank you for using Microsoft products and=20
services.</DIV></BLOCKQUOTE></FONT>
<DIV><FONT face=3DArial size=3D2>I wish you luck!! </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>-- <BR>IL Thomas</FONT></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"Jeremy Gollehon" <</FONT><A=20
size=3D2>j_gollehonBLAMSPAM@hotmail.com</FONT></A><FONT face=3DArial =
size=3D2>>=20
wrote in message </FONT><A=20
face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I have a small =
network (10=20
clients, 1 Windows 2003 File Server).<BR>> <BR>> When using the=20
NON-enterprise version of WDS we found a big problem when <BR>> =
saving large=20
(and somtimes small) files. All the client machines have a =
<BR>> mapped=20
network drive from the server and all the WDS are set to index this =
<BR>>=20
drive.<BR>> <BR>> Let's say User1 begins to save a 30MB Excel =
file. =20
The save time is about 35 <BR>> seconds and the whole time a randomly =
named=20
temp file is being built which <BR>> is eventually renamed to the =
original=20
name of the file being saved. The <BR>> problem we had was that =
the WDS=20
Indexer on User2, User3, User4, etc... would <BR>> start to index the =
TEMP=20
file. The first user to start indexing the file <BR>> would put =
a lock=20
on the file and when Excel was done building the temp file <BR>> and =
went to=20
rename to the file to it's real name, a "Application Sharing <BR>> =
Violation"=20
error would be thrown.<BR>> <BR>> The problem would almost always =
happen=20
with our 30MB file, but would <BR>> randomly happen on other =
occasions with=20
any number of other files in the <BR>> share. The solution =
obviously=20
ended up being "Turn off indexing of the <BR>> network =
share".<BR>>=20
<BR>> With the release of WDS Enterprise edition I expected a way of =
indexing=20
<BR>> mapped network drives that solved this problem. However, =
reading=20
through <BR>> the Windows Desktop Search Administration Guide gives =
me little=20
hope.<BR>> <BR>> The "don't index these file types", which has =
always been=20
an available <BR>> option, might be helpful except for the fact that =
the=20
Excel temp files have <BR>> no extension.<BR>> <BR>> I thought =
maybe=20
there would be a multiple index solution involved. One <BR>> =
where the=20
server indexes it's own files and sends updates to the user <BR>>=20
indexes. Something like this would solve the problem of the over =
zealous=20
<BR>> user indexing as the server is the only machine indexing it's =
files and=20
<BR>> wouldn't index while there's hard drive activity. I can =
see where=20
this <BR>> would be a problem in larger organizations however because =
maybe=20
hard drive <BR>> activity never subsides.<BR>> <BR>> Anyway, is =
there=20
any hope to get the mapped network drives indexed or am I <BR>> out =
of=20
luck?<BR>> As others might not have run into this problem, and =
Microsoft=20
Support never <BR>> even thought to check this with me, I'm not sure =
the WDS=20
development team <BR>> knows about this problem. Maybe a [MSFT] =
person=20
can chime in on that one.<BR>> <BR>> Thanks for your time,<BR>> =
Jeremy=20
<BR>> <BR>></FONT></BODY></HTML>
------=
| 
XML Sitemap