SMB 3.0 Over Hyper-V

Hai,
In my Data center , I have to Hyper-V host Installed with Windows 2012 R2 ,with below details
Server Name : ASPHYP01 ; ASPHYP02
IP : 192.168. 0.1 ; 192.168.0.2
Disk : C: 300 GB D: 1 TB in each server , now i need to Configure fail-over cluster for Hyper -V , storage (SAN ) is not Available , so i try to Use SMB3.0 file share , please let know if any one familiar with this concept , if possiable please
share some configuration documents to create Cluster sharded volume , and how to proceed with SMB 3.0 Configuration .
Reagrds
Pandu.J
You don't create Cluster Shared Volume with SMB 3.0 access which is file (CSV is block). So it's all as simple as putting your VM image on SMB 3.0 share and you can go. See:
Assign SMB 3.0 Share to Hyper-V
http://technet.microsoft.com/en-us/library/jj614620.aspx
Deploy SMB 3.0 for Hyper-V (Step-by-Step)
http://blogs.technet.com/b/canitpro/archive/2013/12/18/step-by-step-deploy-hyper-v-on-smb-3-0.aspx
However you need to understand just one share is not a reliable destination and you really need a clustered or CA (Contagiously Available) SMB 3.0 share that's part of a Scale-Out File Server. See:
Scale-Out File Server (Overview)
http://technet.microsoft.com/en-us/library/hh831349.aspx
Scale-Out File Server and Hyper-V (Guide)
With SoFS approach your share is protected as if one host will die silently actual share content would be moved to another available live SoFS node and Hyper-V will continue with your VMs with no downtime.
Hope this helped :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

Using single SMB share with multiple Hyper-V clusters

Hello,
I'm trying to find out if I can use a single SMB share with multiple Hyper-V Clusters. Looking at:
How to Assign SMB 3.0 File Shares to Hyper-V Hosts and Clusters in VMM
I think it's possible. Since the File Server is going to handle the file locking it shouldn't be a problem.
Has anyone tried that?
Thank you in advance!

Hello,
I'm not sure that's possible, I get this from this statement:"Assign the share—Assign
the share to a virtual machine host or cluster."
Even if it worked I wouldn't do that. Why don't you just create multiple shares?

SMB Extremely Slow over VPN With Windows Server 2003

Hello everyone,
I finally convinced another person at my law firm to switch to a MacBook Pro. In preparation, I am attempting to fix any compatibility problems that would put off this new user. Unfortunately, our IT guy recently switched us to a Sonicwall SSL-VPN 200. I can connect to our server through the VPN client with no problems and I can mount our internal file server, but the connection is incredibly slow. My initial reaction was that it must be a problem with Windows Server 2003 and SMB, but I was previously able to connect to and operate on our VPN through our old Fortinet (ipsec) device with no problems. Simply put, directory switching, file moving, etc. are all now incredibly slow over the VPN. Help!

Full support for SMB signing did not appear until Samba 3.0.2 released in 2004. Mac OS X 10.5 (Leopard) supports SMB signing. Previous versions require either disabling SMB signing server-side, using a third party SMB client, using the command-line smbclient program, or updating samba yourself.

LDAP Query´s Slow on Virtual DC with W2K12 over Hyper-V W2K12 R2

Hello,
We have 2 Virtual Machine DC´s. After upgrade HOSTs from Hyper-V 2012 to Hyper-V 2012 R2, LDAP Query´s are very slow on the 2 Virtual DC´s.
Has anyone ever went through the same problem?
Thanks,
Alexandre Smialoski

No. But what LDAP query are you running?
Do you have any network/connectivity issues?
Santhosh Sivarajan | Houston, TX | www.sivarajan.com
ITIL,MCITP,MCTS,MCSE (W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),Network+,CCNA
Windows Server 2012 Book - Migrating from 2008 to Windows Server 2012
Blogs: Blogs
Twitter: Twitter
LinkedIn: LinkedIn
Facebook: Facebook
Microsoft Virtual Academy:
Microsoft Virtual Academy
This posting is provided AS IS with no warranties, and confers no rights.

3 Node hyper-V 2012 R2 Failover Clustering with Storage spaces on one of the Hyper-V hosts

Hi,
We have 3x Dell R720s with 5x 600GB 3.5 15K SAS and 128 GB RAM each. Was wondering if I could setup a Fail-over Hyper-V 2012 R2 Clustering with these 3 with the shared storage for the CSV being provided by one of the Hyper-V hosts with storage spaces installed
(Is storage spaces supported on Hyper-V?) Or I can use a 2-Node Failover clustering and the third one as a standalone Hyper-V or Server 2012 R2 with Hyper-V and storage spaces.
Each Server comes with QP 1G and a DP10G nics so that I can dedicate the 10G nics for iSCSI
Dont have a SAN or a 10G switch so it would be a crossover cable connection between the servers.
Most of the VMs would be Non-HA. Exchange 2010, Sharepoint 2010 and SQL Server 2008 R2 would be the only VMS running as HA-VMs. CSV for the Hyper-V Failover cluster would be provided by the storage spaces.

I thought I was tying to do just that with 8x600 GB RAID-10 using the H/W RAID controller (on the 3rd Server) and creating CSVs out of that space so as to provide better storage performance for the HA-VMs.
1. Storage Server : 8x 600GB RAID-10 (For CSVs to house all HA-VMs running on the other 2 Servers) It may also run some local VMs that have very little disk I/O
2. Hyper-V-1 : Will act has primary HYPER-V hopst for 2x Exchange and Database Server HA-VMs (the VMDXs would be stored on the Storage Servers CSVs on top of the 8x600GB RAID-10). May also run some non-HA VMs using the local 2x600 GB in RAID-1
3. Hyper-V-2 : Will act as a Hyper-V host when the above HA-VMs fail-over to this one (when HYPER-V-1 is down for any reason). May also run some non-HA VMs using the local 2x600 GB in RAID-1
The single point of failure for the HA-VMs (non HA-VMs are non-HA so its OK if they are down for some time) is the Storage Server. The Exchange servers here are DAG peers to the Exchange Servers at the head office so in case the storage server mainboard
goes down (disk failure is mitigated using RAID, other components such as RAM, mainboard may still go but their % failure is relatively low) the local exchange servers would be down but exchange clients will still be able to do their email related tasks using
the HO Exchange servers.
Also they are under 4hr mission critical support including entire server replacement within the 4 hour period.
If you're OK with your shared storage being a single point of failure then sure you can proceed the way you've listed. However you'll still route all VM-related I/O over Ethernet which is obviously slower then running VMs from DAS (with or without virtual SAN
LUN-to-LUN replication layer) as DAS has higher bandwidth and smaller latency. Also with your scenario you exclude one host from your hypervisor cluster so running VMs on a pair of hosts instead of three would give you much worse performance and resilience:
with 1 from 3 physical hosts lost cluster would be still operable and with 1 from 2 lost all VMs booted on a single node could give you inadequate performance. So make sure your hosts would be insanely underprovisioned as every single node should be able to
handle ALL workload in case of disaster. Good luck and happy clustering :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

CIFS/SMB difference

If I try to access my windows share on my network using smb://servername/sharename - it cannot find the box.
If I use CIFS://servername/sharename it works like a charm.
What is the difference between CIFS and SMB?
[the above holds true for accessing only some of the windows machines on the network... but is consistent... same servers never can be see, other can always be seen]

CIFS (Common Internet File System) is a refinement of SMB (Server Message Blocks). SMB is the term for Microsoft's file sharing technology as used in Windows. CIFS was proposed by them as an "open" version of SMB for filesharing over the Internet and is used by other platforms such as Unix.
If you're having trouble with SMB then something in your setup related to Windows file sharing, perhaps WINS server settings or authentication, is not quite right, whereas the more generic CIFS is able to connect.

[Forum FAQ] Troubleshooting Network File Copy Slowness

1. Introduction
The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common
Internet File System (CIFS) Protocol is a dialect of SMB. Both SMB and CIFS are also available on VMS, several versions of Unix, and other operating systems.
Microsoft SMB Protocol and CIFS Protocol Overview
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365233(v=vs.85).aspx
Server Message Block overview
http://technet.microsoft.com/en-us/library/hh831795.aspx
1.1
SMB Versions and Negotiated Versions
- Thanks for the
Jose Barreto's Blog
There are several different versions of SMB used by Windows operating systems:
CIFS – The ancient version of SMB that was part of Microsoft Windows NT 4.0 in 1996. SMB1 supersedes this version.
SMB 1.0 (or SMB1) – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2
SMB 2.0 (technically SMB2 version 2.002) – The version used in Windows Vista (SP1 or later) and Windows Server 2008 (or any SP)
SMB 2.1 ((technically SMB2 version 2.1) – The version used in Windows 7 (or any SP) and Windows Server 2008 R2 (or any SP)
SMB 3.0 (or SMB3) – The version used in Windows 8 and Windows Server 2012
SMB 3.02 (or SMB3) – The version used in Windows 8.1 and Windows Server 2012 R2
Windows NT is no longer supported, so CIFS is definitely out. Windows Server 2003 R2 with a current service pack is under Extended Support, so SMB1 is still around for a little while. SMB 2.x in Windows Server 2008 and Windows Server 2008
R2 are under Mainstream Support until 2015. You can find the most current information on the
support lifecycle page for Windows Server. The information is subject to the
Microsoft Policy Disclaimer and Change Notice. You can use the support pages to also find support policy information for Windows
XP, Windows Vista, Windows 7 and Windows 8.
In Windows 8.1 and Windows Server 2012 R2, we introduced the option to completely disable CIFS/SMB1 support, including the actual removal of the related binaries. While this is not the default configuration, we recommend disabling this older
version of the protocol in scenarios where it’s not useful, like Hyper-V over SMB. You can find details about this new option in item 7 of this blog post:
What’s new in SMB PowerShell in Windows Server 2012 R2.
Negotiated Versions
Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server:
OS
Windows 8.1 WS 2012 R2
Windows 8 WS 2012
Windows 7 WS 2008 R2
Windows Vista WS 2008
Previous versions
Windows 8.1 WS 2012 R2
SMB 3.02
SMB 3.0
SMB 2.1
SMB 2.0
SMB 1.0
Windows 8 WS 2012
SMB 3.0
SMB 3.0
SMB 2.1
SMB 2.0
SMB 1.0
Windows 7 WS 2008 R2
SMB 2.1
SMB 2.1
SMB 2.1
SMB 2.0
SMB 1.0
Windows Vista WS 2008
SMB 2.0
SMB 2.0
SMB 2.0
SMB 2.0
SMB 1.0
Previous versions
SMB 1.0
SMB 1.0
SMB 1.0
SMB 1.0
SMB 1.0
* WS = Windows Server
1.2 Check, Enable and Disable SMB Versions in Windows operating systems
In Windows 8 or Windows Server 2012 and later, there is a new PowerShell cmdlet that can easily tell you what version of SMB the client has negotiated with the File Server. You simply access a remote file server (or create a new mapping to it) and use Get-SmbConnection.
To enable and disable SMBv1, SMBv2, and SMBv3 in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012, please follow the steps in the article below.
Warning: We do not recommend that you disable SMBv2 or SMBv3. Disable SMBv2 or SMBv3 only as a temporary troubleshooting measure. Do not leave SMBv2 or SMBv3 disabled.
http://support.microsoft.com/kb/2696547
1.3 Features and Capabilities
- Thanks for the
Jose Barreto's Blog
Here’s a very short summary of what changed with each version of SMB:
From SMB 1.0 to SMB 2.0 - The first major redesign of SMB
Increased file sharing scalability
Improved performance
Request compounding
Asynchronous operations
Larger reads/writes
More secure and robust
Small command set
Signing now uses HMAC SHA-256 instead of MD5
SMB2 durability
From SMB 2.0 to SMB 2.1
File leasing improvements
Large MTU support
BranchCache
From SMB 2.1 to SMB 3.0
Availability
SMB Transparent Failover
SMB Witness
SMB Multichannel
Performance
SMB Scale-Out
SMB Direct (SMB 3.0 over RDMA)
SMB Multichannel
Directory Leasing
BranchCache V2
Backup
VSS for Remote File Shares
Security
SMB Encryption using AES-CCM (Optional)
Signing now uses AES-CMAC
Management
SMB PowerShell
Improved Performance Counters
Improved Eventing
From SMB 3.0 to SMB 3.02
Automatic rebalancing of Scale-Out File Server clients
Improved performance of SMB Direct (SMB over RDMA)
Support for multiple SMB instances on a Scale-Out File Server
You can get additional details on the SMB 2.0 improvements listed above at
http://blogs.technet.com/b/josebda/archive/2008/12/09/smb2-a-complete-redesign-of-the-main-remote-file-protocol-for-windows.aspx
You can get additional details on the SMB 3.0 improvements listed above at
http://blogs.technet.com/b/josebda/archive/2012/05/03/updated-links-on-windows-server-2012-file-server-and-smb-3-0.aspx
You can get additional details on the SMB 3.02 improvements in Windows Server 2012 R2 at
http://technet.microsoft.com/en-us/library/hh831474.aspx
1.4 Related Registry Keys
HKLM\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters\
DeferredOpensEnabled – Indicates whether the Redirector can defer opens for certain cases where the file does not really need to be opened, such as for certain delete requests and adjusting file attributes.
This defaults to true and is stored in the Redirector variable MRxSmbDeferredOpensEnabled.
OplocksDisabled – Whether the Redirector should not request oplocks, this defaults to false (the Redirector will request oplocks) and is stored in the variable MrxSmbOplocksDisabled.
CscEnabled – Whether Client Side Caching is enabled. This value defaults to true and stored in MRxSmbIsCscEnabled. It is used to determine whether to execute CSC operations when called. If CSC is enabled,
several other parameters controlling CSC behavior are checked, such as CscEnabledDCON, CscEnableTransitionByDefault, and CscEnableAutoDial. CSC will be discussed in depth in its own module, so will be only mentioned in this module when it is necessary to understanding
the operation of the Redirector.
DisableShadowLoopback – Whether to disable the behavior of the Redirector getting a handle to loopback opens (opens on the same machine) so that it can shortcut the network path to the resource and
just access local files locally. Shadow opens are enabled by default, and this registry value can be used to turn them off. It is stored in the global Redirector variable RxSmbDisableShadowLoopback.
IgnoreBindingOrder – Controls whether the Redirector should use the binding order specified in the registry and controlled by the Network Connections UI, or ignore this order when choosing a transport
provider to provide a connection to the server. By default the Redirector will ignore the binding order and can use any transport. The results of this setting are stored in the variable MRxSmbObeyBindingOrder.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Security Signature settings – The RequireSecuritySignature setting is stored in MRxSmbSecuritySignaturesRequired, EnableSecuritySignature in MRxSmbSecuritySignaturesEnabled, RequireExtendedSignature
in MRxSmbExtendedSignaturesRequired, and EnableExtendedSignature in MRxSmbExtendedSignaturesEnabled. Note that the Extended Security Signatures assume the regular security signatures are enabled, so those settings are adjusted if necessary based on the extended
settings. If extended signatures are required, regular signatures have to be required.
EnablePlainTextPassword – Support for using plain text passwords can be turned on using this key. They are disabled by default.
OffLineFileTimeoutIntervalInSeconds – Used to set the expiration time for timing out an Exchange (discussed later) when the exchange is accessing an offline file. This value defaults to 1000 seconds,
but can be changed in the registry and is stored in the global Redirector variable OffLineFileTimeoutInterval
SessTimeout – This is the amount of time the client waits for the server to respond to an outstanding request. The default value is 60 seconds (Windows Vista). When the client does not receive the
response to a request before the Request Expiration Timer expires, it will reset the connection because the operation is considered blocked. In Windows 8, the request expiration timer for the SMB 2 Negotiate is set to a smaller value, typically under 20 seconds,
so that if a node of a continuously available (CA) cluster server is not responding, the SMB 3.0 client can expedite failover to the other node.
ExtendedSessTimeout – Stored in the ExtendedSessTimeoutInterval variable, this value is used to extend the timeout on exchanges for servers that require an extended session timeout as listed in the
ServersWithExtendedSessTimeout key. These are third party servers that handle SMB sessions with different processes and vary dramatically on the time required to process SMB requests. The default value is 1000 seconds. If the client is running at least Windows
7 and ExtendedSessTimeout is not configured (By Default), the timeout is extended to four times the value of SessTimeout (4 * SessTimeout).
MaxNumOfExchangesForPipelineReadWrite – This value is used to determine the maximum number of write exchanges that can be pipelined to a server. The default is 8 and the value is stored in the variable
MaxNumOfExchangesForPipelineReadWrite.
Win9xSessionRestriction – This value defaults to false, but is used to impose a restriction on Windows 9x clients that they can only have one active non-NULL session with the server at a time. Also,
existing session based connections (VNETROOTS) are scavenged immediately, without a timeout to allow them to be reused.
EnableCachingOnWriteOnlyOpens – This value can cause the Redirector to attempt to open a file that is being opened for write only access in a manner that will enable the Redirector to cache the file
data. If the open fails, the request will revert back to the original requested access. The value of this parameter defaults to false and is stored in the MRxSmbEnableCachingOnWriteOnlyOpens variable.
DisableByteRangeLockingOnReadOnlyFiles – This parameter defaults to false, but if set to true will cause level II oplocks to automatically be upgraded to batch oplocks on read-only files opened for
read only access. It is stored in the variable DisableByteRangeLockingOnReadOnlyFiles.
EnableDownLevelLogOff – False by default, this value controls whether a Logoff SMB will be sent to down-level servers when a session is being closed. If this is false, and the server has not negotiated
to the NT SMB dialect or does not support NT Status codes, the logoff will not be sent because we aren’t sure that server will understand the request. The value is stored in MrxSmbEnableDownLevelLogOff.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\
ResilientTimeout – This timer is started when the transport connection associated with a resilient handle is lost. It controls the amount of time the server keeps a resilient handle active after the
transport connection to the client is lost. The default value is 300 seconds (Windows 7, Server 2008 R2, 8, Server 2012).
DurableHandleV2TimeoutInSecond – This timer is started when the transport connection associated with a durable handle is lost. It controls the amount of time the server keeps a durable handle active
after the transport connection to the client is lost. The default value is 60 seconds (Windows 8, Windows Server 2012). The maximum value is 300 seconds.
HKLM\SYSTEM\CurrentControlSet\Services\SMBWitness\Parameters\
KeepAliveInterval – This functionality was introduced for SMB 3.0 in Windows 8 and Windows Server 2012. The witness protocol is used to explicitly notify a client of resource changes that have occurred
on a highly available cluster server. This enables faster recovery from unplanned failures, so that the client does not need to wait for TCP timeouts. The default value is 20 minutes (Windows 8, Windows Server 2012).
HKLM\System\CurrentControlSet\Services\SmbDirect\Parameters\
ConnectTimeoutInMs – Establish a connection and complete negotiation. ConnectTimeoutInMs is the deadline for the remote peer to accept the connection request and complete SMB Direct negotiation. Default
is 120 seconds (Windows 8).
AcceptTimeoutInMs – Accept negotiation: The SMB Direct Negotiate request should be received before AcceptTimeoutInMs expires. The servers starts this timer as soon as it accepted the connection. Default
is 5 seconds (Windows 8).
IdleConnectionTimeoutInMs – This timer is per-connection. It is the amount of time the connection can be idle without receiving a message from the remote peer. Before the local peer terminates the
connection, it sends a keep alive request to the remote peer and applies a keep alive timer. Default is Default: 120 seconds (Windows 8).
KeepaliveResponseTimeoutInMs – This attribute is per-connection. It defines the timeout to wait for the peer response for a keep-alive message on an idle RDMA connection. Default is 5 seconds (Windows
8).
CreditGrantTimeoutInMs – This timer is per-connection. It regulates the amount of time that the local peer waits for the remote peer to grant Send credits before disconnecting the connection.
This timer is started when the local peer runs out of Send credits. Default is 5 seconds (Windows 8).
References:
[MS-SMB]: Server Message Block (SMB) Protocol
http://msdn.microsoft.com/en-us/library/cc246231.aspx
[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3
http://msdn.microsoft.com/en-us/library/cc246482.aspx
SMB 2.x and SMB 3.0 Timeouts in Windows
http://blogs.msdn.com/b/openspecification/archive/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows.aspx

3. How to Troubleshoot
3.1 Troubleshooting Decision Tree
1
Is the slowness occurring in browsing a network shared folder or copying a file, or both?
Browsing, go to 1.1.
Copying, go to 1.2.
Both, go to 1.3.
1.1
Is the target a DFS path or not?
Yes, go to 1.1.1.
No, go to 1.1.2.
1.1.1
Is the client visiting the nearest DFS root server and file server?
Yes, go to 1.1.1.1.
No, go to 1.1.1.2.
1.1.1.1
Browse the corresponding (Non-DFS) UNC path directly. Do you still experience the slowness?
Yes, go to 1.1.1.1.1.
No,
go to 1.1.1.1.2.
1.1.1.1.1
Issue is the particular file server responds to the share folder enumeration requests slowly. Most probably it’s
unrelated to DFS. Follow 1.1.2.
1.1.1.1.2
Issue is that client experiences delay when browsing the DFS path, but no delay is visiting the target file server
directly. Capture Network Monitor trace from the client and study if the DFS path is cracked down.
1.1.1.2
Use dfsutil.exe to clear local domain and referral cache. Then visit the DFS path again and capture Network Monitor
trace from the client to study why the client goes to a wrong file server or DFS root server.
1.1.2
Not a DFS issue. Issue is the particular file server responds to the share folder enumeration requests slowly. “Dir”
the same share folder from Command Prompt. Is it slow?
Yes, go to 1.1.2.1
No, go to 1.1.2.2
1.1.2.1
Check the number of subfolders and files in that share folder. Is the number large?
Yes, go to 1.1.2.1.1
No, go to 1.1.2.1.2
1.1.2.1.1
Try to “dir” a different share folder on the same file server, but with less items. Is it still slow or not?
Yes, go to 1.1.2.1.1.1
No, go to 1.1.2.1.1.2
1.1.2.1.1.1
Probably to be performance issue of the file server. Capture Network Monitor trace from both sides, plus Performance
Monitor on the file server.
1.1.2.1.1.2
Probably to be performance issue of the file server, particularly, of the disk. Capture Network Monitor trace from
both sides, plus Performance Monitor on the file server.
1.1.2.1.2
Same as 1.1.2.1.1.1. Probably to be performance issue of the file server. Capture Network Monitor trace from both
sides, plus Performance Monitor on the file server.
1.1.2.2
Explorer.exe browses the share folder slowly while “dir” does fast. The issue should lie in the particular SMB traffic
incurred by explorer.exe. It's a Shell issue.
1.2
Is the target a DFS path or not?
Yes, go to 1.2.1
No, go to 1.2.2
1.2.1
Is the client downloading/uploading against the nearest file server?
Yes, go to 1.2.1.1
No, go to 1.2.1.2
1.2.1.1
Try to download/upload against that file server using the Non-DFS share path. Still slow?
Yes, go to 1.2.1.1.1
No, go to 1.2.1.1.2
1.2.1.1.1
Not a DFS issue. Capture Network Monitor trace from both sides to identify the pattern of the slowness.
1.2.1.1.2
This is unlikely to occur because the conclusion is contradictory to itself. Start from the beginning to double
check.
1.2.1.2
Same situation as 1.1.1.2. Use dfsutil.exe to clear local domain and referral cache. Then visit the DFS path again
and capture Network Monitor trace from the client to study why the client goes to a wrong file server or DFS root server.
1.2.2
Same as 1.2.1.1.1. It's not a DFS issue. Capture Network Monitor trace from both sides to identify the pattern of
the slowness.
1.3
Follow 1.1 and then 1.2.
3.2 Troubleshooting Tools
Network Monitor or Message Analyzer
Download
http://www.microsoft.com/en-us/download/details.aspx?id=40308
Blog
http://blogs.technet.com/b/messageanalyzer/
Microsoft Message Analyzer Operating Guide
http://technet.microsoft.com/en-us/library/jj649776.aspx
Performance Monitor
http://technet.microsoft.com/en-us/library/cc749249.aspx
DiskMon
http://technet.microsoft.com/en-us/sysinternals/bb896646.aspx
Process Monitor
http://technet.microsoft.com/en-us/sysinternals/bb896645

Windows 2008 Server Co-residency BE6000/BE7000/TRCs/Specs-Based.

Hey,
I'm trying to figure out where I can run a Windows 2008 R2 server:
BE6000: seems like no based on http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/BE6000/Coresidency/9_x/BE6K_coRes.html
BE7000: the data sheet has a "Co-residency Policy" link that provides no information on co-residency. I'm assuming yes and that there is no similar list as for the BE6000.
TRCs: I assume yes
Specs-based: I assume yes.
It would be nice if this was corralled into a single location.
Thanks for any answers.

If you run 6K/7k over HYP or FND license, then yes, the above link applies to both. Not sure if you can also buy either license with TRC or spec-based TRC, if so, then they also fall under the guidelines from the link.
If you run any of the above options over VMware std, ent, or ent+ license, general co-res guidelines from virtualization wiki apply.

Avi codec pack for mac??

Hi,
We have recently switched over a few mac machines and are slowly getting the hang of them. After having issues playing back avi's on the machine i have downloaded the Perian codec pack for mac which allows me to play the files in quicktime etc and get audio output. I still have the problem however that when imported into Premiere/Encore etc i get video but no audio??? I dont want to have to convert all the files into compatible mac files as i just want a codec to install which will play them and solve the problem. The files are DivX codec built.
I find it odd that files will play with audio in quicktime on the machine but not in the adobe software. Tried reading around this on the web but have turned up nothing after Perian that helps. Any help would be greatly appreciated.
Thanks,
Ian

Thanks Hunt,
You seem to reply to most of these posts, so thank you very much for giving up your time to help others, much appreciated.
I have both converted the files - in a rather drawn out way through a couple of freeware programs to give me an mp3 audio file macs don't seem to mind - and and burnt DVD's on mac and PC to check for quality on both machines.
We have to work with DivX a bit for clients to create conference openers etc and if they specify footage from the web etc its generally the only format we can get it in on short notice. Horrible but the way of the world it seems.
Currently running mac book pro's for on site edit machines on the highest specs available for purchase i.e. i7 processor 7200rpm internal hard drive etc and Adobe CS5 and have to say that the 'macs never fall over' hype isn't true. Apart from having their file preferences for use which is a pain when crossing projects over from both platforms i have found both new macs crash when worked hard using premiere, after effects and photoshop/illustrator. We find CS5 has far fewer bugs and is more stable than CS4 mind you.
I'm sure that may queue mac lovers to put me straight on the much fabled shiny machines however.
Cheers, Ian

Upgradebootstrap has failed with unknown exception

I'm stumped. Running SharePoint 2013 over Hyper-V with the following topology:
1 Database server
3 Application/WFE servers (1 for Central Admin, some BI stuff, 1 for Search, 1 for Project Server)
It's a very basic test farm, running 2013 with SP1, only one site collection on port 80. Trying to set up Project Server on a separate server from the rest of my test farm. Installed Project Server, no problems. Got the "Failed to
initiate the upgrade sequence" error. Discovered I needed to install Project Server SP1 so did that, no problems. Still getting the error. The logs give me nothing to do on, other that there's an SPUpgradeException error thrown, that's
all.
Anybody know what to do next? Thanks
Kevin McCarty

Tried that. Now the upgrade wizard won't run at all. It says that the other two servers are missing the Microsoft Project Server 2013 installs altogether. I tried reinstalling them without success (because they are already there, according
to the installer). I then uninstalled Project Server on the Search and Project server boxes and ran the upgrade on the Central Admin box, which then surprisingly worked - except it left Central Admin off so I restarted that. Somehow, along the
way, both of the other boxes were removed from the farm. Then I tried reinstalling Project Server on the Project Server box along with SP1 and reran the wizard but the wizard acted as if the box had never been on the farm so it did a complete "Add
me to the farm" configuration but it DID work. Next I added the Search server and the same thing happened, had to re-add it to the farm but it worked too. I'll have to tweak my search service to get it running on the search server again, but
otherwise everything looks as it should, including, shockingly enough, Project Server.
(Here's an interesting error - at one point I ran the wizard, got a "can't locate master database error", clicked on Advanced Settings button and got an unhandled exception crash - I think it might have been a timeout error originally).
The key takeaway for me is you have to use all the exact same components (OS, installs and patches) when adding servers AND always apply in the order you added them or you are just asking for a resume-updating moment. Just glad I got to learn this
on a test platform. SharePoint is the "SharePointiest" piece of software I have ever run across.
Kevin McCarty

Windows 7 Offline Files Enhancements - SMB2 Required?

I have used Windows 2000/XP Offline Files functionanlity before, and it was pretty much useless. Too many issues to make it a reliable solution.
Moving foward to Windows 7 now, and I've been reading on the many enhancements that Offline Files has now, and in my initial testing it seems 1000X better than previous versions.
My problem is... We have a NetApp device in place that currently has SMB2 disabled on all shares. We needed to do this some time ago for some reason, but now that we have 7500 users accessing the shares, we need to test thoroughly in order to re-enable SMB2.
Basically, my question is: Do we need to enable SMB2 to take advantage of the Bitmap Differential Transfer feature of Windows 7 Offline Files? I can't seem to find any solid information, and don't know how to test it on my Windows 7 test machines.

Hi,
Sorry for my dilatory reply. In my opinion, I would like to suggest you enable SMB2 to use Windows 7 feature-Offline Files.
Here contents is a explain come from Technet Blog.
SMB (Server Message Block) is a remote file protocol commonly used by Microsoft Windows clients and servers that dates back to 1980’s. Back when it was first used, LANs speeds were typically
10Mbps or less, WAN use was very limited and there were no Wireless LANs. Network security concerns like preventing man-in-the-middle attacks were non-existent at that time. Obviously, things have changed a lot since then. SMB did evolve over time, but it
did so incrementally and with great care for keeping backward compatibility. It was only with SMB2 in 2007 that we had the first major redesign.
SMB2 has a numeber of performance improvements over the former SMB1 implementation.
You can access to the link to check more description:
http://blogs.technet.com/b/josebda/archive/2008/12/05/smb2-a-complete-redesign-of-the-main-remote-file-protocol-for-windows.aspx
Roger Lu
TechNet Community Support

TMG Stops responding every 4 days / many connection drops with idle vpn connections

Hi everyone!
I am running a TMG Firewall with about 200 users connected on Server 2008 R2 - patch level 7.0.9193.601.
It is virtualized on a Hyper-V 2008 R2. Additionally we have 4 IPsec Site2Site VPNs configured in Windows Advanced Firewall - as TMG doesn't provide such a comfortable way to configure them directly in TMG.
About 3 Months ago that TMG started to lose connectivity from time to time. At first we were not monitoring that problem precisely as we thought it was an isp issue but some days before christmas that tmg server just dropepd every outgoing connection
and stopped listening!
I was able to control the server over hyper-v directly but no connection in or outbound could be established. (no VPN inc or surf outgoing)
I checked the event logs and there was NO other error than the errors from TMG connection verifiers...
As far as I was able to tell tmg still worked as far as logs and engine was conserned but no routing was done at all!
The last resort was to reboot the TMG then everything worked as before...
This behavior then appeard every 4 days... - simple workaround scheduled reboot every 3 days!
But that is no statisfying solution.... additionally some vpn users reported that their connections has quite annoying drops from time to time, unfortunately I was not able to trace the error.
Possible sources that I can exclude:
-Backup (online snapshot with ArcServe - the server was NOT saved)
-AV (Symantec Endpoint protection 12.1 - was uninstalled nothing changed)
Any ideas??
Best regards

Hi,
opening a MS case seems not to be so easy...
As long as I have no clue whats going on exactly there is no ms case.
Any other suggestions??
I started collecting Perfmon data: everything seems to be OK.
- hardly any backlogged packets
- during working hours about 10 pages / sec (memory)
Some Values:
Free System Page Table Entries: 33.555
Pool Nonpaged Bytes: 88.646.372 Bytes = 84,53 MB
Pool Paged Bytes: 266.842.112 Bytes = 254,48 MB
System Driver Total Bytes: 4.812.800 Bytes = 4,5MB
Handle Count (wspsrv): 11.338Private Bytes (wspsrv): 821.944.320 Bytes = 783,86 MB
Working Set (wspsrv): 609.697.792 Bytes = 581,4 MB
Virtual Bytes (wspsrv): 1.747.615.744 Bytes = 1,666 GBThread Count (wspsrv): 69
I'll keep collecting data for two days because my last reboot was 2 days ago - if my observations were correct TMG will stop responding monday morning or during lunchtime at latest.

Importing MPEG 4 Movie into Keynote 2

After spending 5 days trying to import MPEG 4 video from a Canon Optura 500 videocam, I have learned:
Can't be done. Calling Apple help today, confirmed no possible solution to get the movies into Keynote. I tried everything and read all help information in Keynote and imovie.
What I did for a do or die presentation: Import clip from camera (no editing allowed, as your edits will be lost on transfer) into imovie, copy and paste from imovie to keynote 2, copy and paste from Keynote 2 to POWERPOINT!
click on movie on a powerpoint slide and click view, click custom animation, click on your clip and click extras, pick play on click, and you can now play your MPEG4 movie in a slide show.
An apple rep once told me, in an Apple store, that "Keynote was Powerpoint on steroids". See how bad steroids are for you.

sigh...while Keynote is an amazing product, the Apple store workers tend to over hype it, to the point of making it sound like it has EVERy feature of PPT, when it's really missing a ton of stuff still. Visually though, I have to agree, it makes PPT look like a toy.
That said, I'm trying to figure out what exactly your process was, and what did and didn't work. I looked up the specs on the 500, and it appears that while you can shoot in true DV format onto mini DV tape, it also shoots Mpeg4 onto the photo card. Is this what you shot in (as opposed to DV format onto tape)? If so, I'm trying to figure out how you even got it into iMovie as opposed to iPhoto, which is what you use to import movies from a media card. Also, I don't understand your comment on edits getting lost.
Next, your use of the term slide show is confusing, but I THINK what you'd like is to see the movie sitting there on a poster frame until you want it to play, and then click to make it play. You can do this to an extent, but you have to work around a few missing features in Keynote. Keynote STILL won't let you leave the poster frame showing on the slide and then have the movie play on a click...you'll actually see NOTHING until you trigger the movie as you have to add a build to the movie, and until it builds, you won't see the thing. The work around is to grab a frame of the movie and paste it onto the slide, then build the movie in right on top of it.
I hope that helps. If you can give more details on what you did and what you TRIED to do, and what you want to end up with, I can try to help you figure it out.
EDIT: ah, I see this in a review "Playback of media from the card and the tape is available in playback mode, as is recording to a VCR or a digital video (DV) device using a FireWire cable." which means you "should" be able to import into iMovie. The real draw back is you're working with mpeg4 and not DV...and Mpeg4 is REALLY compressed, not a good format to use if you plan to edit it as you'll have to decompress and recompress, losing quality (DV is also compressed, but not nearly as much).

2012 R2 Generation 2 VM Boot Failure after Migration

I have encountered an issue after migrating virtual machines to a new host. It happens whether the VM has been moved with live migration or though a shutdown, export, import process.
The hosts are both 2012 R2 Datacenter. The virtual machines are Generation 2 and also have 2012 R2 Datacenter. All the systems where installed with the April ISO. The only difference between the hosts is that one only has no other updates. The other has
all recommended and optional updates as off 2014-10-10.
Once the machine has migrated to the updated host the next time it attempts to boot up (after a restart, ect.) it will fail with one of these two messages.
This happens whether the virtual machine has updates or is a fresh install from the April ISO. Once the machine is migrated back to the host that does not have any updates it will boot back up without any issues.
Notes:
The virtual machines where created on the host without any updates.
When creating a new virtual machine on the host with updates the 2012 R2 ISO bluescreens.
I setup another host machine without updates, tested migration to it and then ran updates. Same issue occurs.
I have tried boot with and without secure boot enabled also tries it with drive signature enforcement disabled. No change either.
This does not happen with generation 1 machines.
What I am trying to figure out is, if it truly is an update issue which update might it be so that it can be avoided? It would also be interesting to figure out if there is a workaround to get affect virtual machines to boot back up.
Let me know what your ideas are or if there are any other tests you would like me to provide.

I would like to thank you for your suggestions. It wasn't the updates that where causing the problem, it is actually a side effect of them requiring a restart. In addition to running updates on the new host servers, I also added a second network card.
The virtual machines are stored on an SMB 3.0 file share. When the server gets restarted SMB 3.0 finds and starts using that second network card in a multichannel configuration. (There are two physical cards / 3 ports / 3 vlans).
I found this out when I looked at the multichannel configuration on the server without updates, but had this network card installed. It wasn't using it at all. After a restart of that server the VM's where exhibiting the same broken behavior. Simply disabling
that network card on the machine got them to work again. The server with updates, because it had been restarted already, was trying to use this network card in SMB 3.0 multichannel.
It just happened to be a coincidence of timing. On the other hand the issue moves to why this second NIC would be causing these issues. I am not entirely sure if it actually has to do with SMB verses something with Hyper-V and the network card. After the
restart the saved state of VM's on it failed to start. Removing the saved state and trying to boot them resulted in the same digital signature error. However, like I mentioned, disabling the network card worked. Virtual machines with
save states restored themselves and those without them also would boot. Again, I will post what I figure out.
Thanks again,
Kevin

SMB1/2 transfering extremely slow for small files. Sends file 6 times.

Having an issue with transferring small files using SMB1 or SMB2. 100MBs will transfer faster than 100 files totaling 10kb.
Doing a packet capture on the source computer will show a file being sent to the destination 6 times before completing. Each upload will have a different FID but file path and name are the same. A large file does not do this.

Hi,
Please capture packets between source computer and destination and upload the two packets.
You could use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the files and then give us the download address.
In the meantime, please refer to the article below to see if it related to SMB performance:
SMB/CIFS Performance Over WAN Links
http://blogs.technet.com/b/neilcar/archive/2004/10/26/247903.aspx
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SMB 3.0 Over Hyper-V

Similar Messages

Maybe you are looking for