OppLocks Settings in SetupBuilder 7

[NewsArchive]

It's for ISAM files of any type, when all users are touching the
datafiles directly. In client-server (i.e. SQL), it's not an issue.

Mike Hanson
www.boxsoft.net

[NewsArchive]

Hi Friedrich,

Please look at this article to disable SMB2 on Vista+:
http://www.petri.co.il/how-to-disabl...erver-2008.htm

You can read the following:

===

To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that
are the “client” systems run the following commands:

sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled

===

So does that mean that the following registry setting won't work on the
CLIENT MACHINE?!:
HKLM\System\CurrentControlSet\Services\LanmanServe r\Parameters
SMB2=0

Best regards,
Jeffrey

[NewsArchive]

Jeffrey,

The oplock.sbi makes use of this method to disable SMB 2.0 on Windows
Vista+:

http://social.msdn.microsoft.com/For...f-6060a2e91ee1

Friedrich

[NewsArchive]

Hi Friedrich,

Yes, I have seen that.

If I understand correctly, to DISABLE SMB2 (so that you CAN disable
opportunistic locking):

Option 1:
You use the SMB2=0 registry setting when the Vista+ machine is acting as
a SERVER.

Opion 2:
Otherwise, when using the Vista+ machine as a CLIENT, you need to use:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled

ONLY after SMB2 is disabled, you CAN disable opportunistic locking.

So my question is:
Will the SMB2=0 registry setting also work when the Vista+ machine is
acting as a CLIENT?

Let me explain further:
My customer has a new Apple OS 10.7.3 Lion Server (before: a Windows
2003 SBS Server).
As of OS 10.7, Apple use *their own* SMB2 protocol and SMB2 can't be
turned off and also opportunistic locking can't be turned off on the
Apple server!
Our TPS files are on a SMB share on the Apple server and the TPS files
are getting corrupted at this moment, because we can't turn off SMB2
(and opportunistic locking) on the Apple server.
This is a big problem!
The clients are Windows 7 machines, so that means that we have to turn
off SMB2 (and opportunistic locking) on the Windows 7 CLIENTS.

So what do we have to use on the Windows 7 clients?
Option 1 or Option 2 (see above)?!

IF we need to use option 2 to turn off SMB2 on the Windows 7 clients,
how can we handle the following with SetupBuilder?:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled

I hope you understand my problem?

Best regards,
Jeffrey

[NewsArchive]

Hi Jeffrey,

The problem is that Microsoft does not provide an official statement. So
you have to find out if "sc config" has negative side effects in your case.

There are quite a few resources available, but no "official" word from
Microsoft.

http://www.axon-it.com/2010/11/16/mi...ows-7-clients/

Yes, you can handle the "sc config" stuff from the include script. Just use
the "Run Command Line..." script function.

Friedrich

[NewsArchive]

Thanks!

Best regards,
Jeffrey

[NewsArchive]

Hi Friedrich,

I found this nice article to disable SMB2 and opportunistic locking on
Windows 7 CLIENTS via the registry:
http://www.tcpj.com/caching.pdf

Best regards,
Jeffrey

[NewsArchive]

Hi Jeffrey,

That looks really good, particularly the Windows 7 and SMB2 stuff.
Thanks for posting.

Graham

[NewsArchive]

SWEET

Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
This post may self-destruct at any moment