X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C74BA5.8E13E03A@onstor-exch02.onstor.net>; Thu, 8 Feb 2007 09:21:22 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74BA5.8E13E03A"
Content-class: urn:content-classes:message
Subject: CIFS Shares listing
Date: Thu, 8 Feb 2007 09:21:22 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E025BE6A6@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CIFS Shares listing
Thread-Index: AcdLpY4JLKVb29JIQOyYnsNl2niVyw==
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "dl-Filer Manager" <dl-filermanager@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74BA5.8E13E03A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Is it important for NCM to get a list of CIFS shares that include the
auto-create shares?  These are shares that get created on the fly when a
user connects but cannot be managed via the CLI or NCM.

We currently return them and it's messing up the paging logic that was
put in not long ago to handle iterations.

If they can be removed this will allow us to make a much clear
interface.


------_=_NextPart_001_01C74BA5.8E13E03A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.28">
<TITLE>CIFS Shares listing</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">I</FONT><FONT SIZE=3D2 FACE=3D"Arial">s it =
important for NCM to get a list of CIFS shares that include the =
auto-create shares?</FONT>&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"></FONT> =
<FONT SIZE=3D2 FACE=3D"Arial">T</FONT><FONT SIZE=3D2 FACE=3D"Arial">hese =
are shares that get created on the fly when a user connects but cannot =
be managed via the CLI or NCM.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">We =
currently return them and it</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8217;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">s messing up the paging =
logic that was put in not long ago to handle =
iterations.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If they =
can be removed this will</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">allow us to make a much =
clear inter</FONT><FONT SIZE=3D2 FACE=3D"Arial">f</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">ace.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C74BA5.8E13E03A--
