Hi,

We have got a lab set up in preparation for new equipment arriving.

We have built 2 laptops with Windows Server 2012 std.

On one server we are running the, Active Directory domain services, File server and failover clustering roles/features.

On the second server we have the, File server and failover clustering roles/features.

We have setup a DC and joined our other server to the domain so both servers can talk to each other.

On our second server we have validated and created in failover cluster manager our cluster. But when we try to add a 'disk' we get the following error:

'No disks suitable for cluster disks we found. For diagnostic information about disks available to the cluster, use the validate a configuration wizard to run storage tests'.

Does any one know of a way to get around this?

We have tried with secondary partitions on the laptops HDD but still no success.

 Thanks,

Trying to resolve scan to folder issue on filser server (shared folder)

Scanner Hardware: using Knoica Minolta multifunction biz hub (model C450) and
folder is on Windows Server 2008 Ent with clustered drive. and offcourse folder is shared,

Service account used: svcscan

Folder is configured with svcscan permission (Modify/read/write)
Scanner is configured with svcscan to push scan job to user home drive which is on

but that does not work. Got the error "scan job was done improperly, check the log".
unfortuately log does not give any information ( as usual)
same service account work perfectly fine when sending job to folder on local machine on same domain, that proves scanner is working & configured properly and service account (svcscan) is working.
What you suggest/ recommend and need your help to resolve

Using robocopy with out the /MIR switch.  Approx 6TB, manually recreated shares.  1000s of files are being skipped, assume it it because users are online.  Prior to go live, plan was to close all sessions and files and do one last robocopy. 

What is the easiest way to prevent people from connections be re-established.

robocopy switches are

robocopy "<source>" "<destination>" /E /SEC /COPYALL /V /NP /NFL /NDL /MT:32 /Z /TEE /R:30 /W:10 /LOG:E\log.txt

Hello,

If im implementing a folder redirection at a small office with a single server (no fault tolerance) in order to ease backup and data protection, in case that single server fails, would it still be possible for employees to access theri redirected folders locally if i unchecked the :move the contents of...." option?!,

is synchronization available in that case when that server comes back online?!

is it easy to use folder  redirection with DFS?!

thank you!

I have an Exchange Mailbox Server with 2 NIC, one for the MAPI network and the other is for the SAN Storage network.

The utilization for the SAN Storage Network was being utilized by the Server, but I have noticed recently that the SAN Storage Network is no longer being utilized by the server and I believe that the MAPI network is the one being used for the SAN Traffic as the utilization of the MAPI network goes upto 97%-100%.

How can I force the SAN Traffice to my SAN Storage Network for good?

I have ask this question to the windows server forum because it is most likely to be a server issue.

Someone help.

What are some of the steps to migrate data files from a Windows W2K3 Server to a W2K8 R2 (64-bit) server.

Is this difficult to do?

I have 3 drives in a thin provisioned 2 way mirror storage pool running in Windows Server 2012 Essentials.  The pool has 6.36Tb of capacity and is provisioned for up to 8Tb.  Manage Storage Spaces shows 4.26Tb of used space, yet the Dashboard shows 535Gb of Used Space.  I can confirm the Size on Disk is 535Gb by using Explorer to check properties of the drive.

Screen shots are attached, any ideas?  Should I try an optimize-volume with defrag or retrim or something?

Thanks, Jeff

Jeff

We had setup DFS between a Server 2003 and Serve 2012 server.   The server 2012 was offline was it was moved to a new location.  The server 2003 had an array failure and we did a restore.  Our fiber is not connected and we do not have the bandwidth yet to do a full replication. 

How to we fix the replication without major bandwidth issues?

Dave Mabo, CMC Adaptix Corp.

First time poster, long time lurker, but will appreciate some help here. 

One of our servers that was in a DFSR replication group just experienced a ungraceful shutdown and our primary objective here is to get the DFSR replication going between the two members of the replication group.

The caveat is that the servers were in middle of an initial sync when the authoritative member crashed.

Server A which crashed holds the most recent copy of data, so in an effort to have all this data replicated back to Server B and make sure that it (server A) is the "authoritative" copy, we are planning on disabling Server B in this replication group, resume replication on server A and let it check the DFSR database for consistency and re-initialize if necessary. Since there are no other active members in the replication group, our hope is that Server A will instantly finish it's initialization because it automatically became the authoritative member. Once that finishes, re-enable server B in the replication group.

This is DFSR running on Windows 2012 on both members. 

Do you see any issues with following these steps? Is this how you would recover DFS from a dirty shutdown?

I realize this is a bit complex, do let me know if you need any clarification.

Thanks in advance for your help. 

Hello all thanks for your time and expertise.

I work in a school system with at least 20 buildings in a metropolitan network.  We've recently upgraded the links between our buildings to a GB.   We were looking for a way to simplify management of the student home folders.  Here's a plan I've been thinking about and I would appreciate your input/recommendations:

1 - Centralize home folders for intermediate students through high school in the following format: \\server\home$\students\%username% - All of these students' home folders would be stored on our NAS server utilizing a DFS Namespace.  This way if we needed more space we could add another server to the namespace and just replicate.  Students would all be in one STUDENT home folder.

2 -   Add graduation year to the description property for their user accounts from the general tab so they can be filtered in this manner.  And you can do this by highlighting all the accounts and adding this property because the kids are currently in OUs designating their graduation year. 

3 - Create a Graduated OU.  When the current cycle ends, for example 2013 - you do a filtered search for 2013 students and move them to the Graduated OU.  Then you can delete their accounts from AD.  My issue as I type this is how do I know which folders to delete from the STUDENT folder.

Anyway, your input and recommendations are greatly appreciated.

We are having some issues with VDS and I was hoping to get some ideas.

To recreate the error at will, I open a cmd prompt and go to the root of the drive.  Then I type "dir /s"  Next I start diskmgmt.msc.  It starts and then pauses for a very long time at "Loading Disk Information."  If I look at my command prompt, the directory listing is visibly frozen.  Once Disk Management displays its data, the directory listing continues on.

If I open Resource Monitor, it displays vds.exe accessing a lot of files.  After a few moments vds starts reducing the number of files that it is accessing and then Disk Management displays data.

While vds is accessing the files, our SQL based product has issues because of the latency.

Anyone have any thoughts or solutions?

Hello,

we have set up two servers running windows Server 2008 SP1. The one is a typical fileserver, the other is backup Domain Controller, Backup fileserver, Backup DNS and DHCP server. To set up DFSR between the two systems we used the wizzard. On the fileserver all seems to work fine. The other one however is generating error 9214 (-583), event id 2104 and error 9014, event id 2004. We have tried almost everything i could find on the internet to no avail. The other day we set up replication between the two systems, but used another disk to replicate to on the backup machine. This worked perfectly. I'm starting to think that it has something to do with the harddrive. The drive it works on is a mirrored volume of 365 GB. The harddrive it does not work on is a raid 5 volume of 1.82 TB. At first this was one big volume of 3.63 TB. We have split it into two partitions to make sure that the volume was not to big. Other than tearing down the raid 5 volume I have no other ideas left. Trying to re-install DFSR all together would mean removing the DC from the backup system.

Regards, Frits van den Bergh.

Hi all,

New server and installation of Server 2008 R2, AD and SQL Server running on it.

Whenever i run a Windows Server Backup i get the following series of Errors in the Application Log, in this order:

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   PostSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Name: Shadow Copy Optimization Writer
   Writer Instance ID: {cdef2758-d4d7-4d05-8b99-5f1376e4614c}

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   Gather writers' status
   Executing Asynchronous Operation

Context:
   Current State: GatherWriterStatus

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   Gathering Writer Data
   Executing Asynchronous Operation

Context:
   Execution Context: Requestor
   Current State: GatherWriterMetadata

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   BackupComplete Event
   Executing Asynchronous Operation

Context:
   Current State: BackupComplete

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   Initializing Writer

Context:
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter

Error-specific details:
   Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist.

The Backup runs succesfully however, as does any backup that i run with Backup Exec 2010 on the same server (running these backups also causes these same errors in the Event Log).

The only oher fix i found out in the wild that even remotely gets near these errors is this one:

http://allfaq.org/forums/t/156203.aspx

I tried this but it simply stopped the backups from working at all.

Any ideas anyone?

Many thanks all.

We have a situation were vds.exe is causing a very Long Disk Queue Length (Server 2008 R2) when the service is started.  The problem is relatively easy to reproduce using these steps:

1. Start Resource Monitor and open disk activity.  Also make sure the graphic monitor for Drive C is shown.

2. Open two cmd prompts with the run as administrator option.

3. In one of the cmd prompts, go to the root of drive C: and type "dir /s" to start a directory listing.

4. In the other cmd prompt start diskpart

As diskpart is starting, the directory listing will pause or appear to freeze.  In Resource Monitor you can see the disk queue length increase dramatically.  Once vds.exe gets finished flushing everything that it wants to flush, the disk queue length comes back down to a normal level, diskpart starts, and the directory listing continues.

We have tested this in several forms and it occurs anytime that vds.exe is started.  The queue length issue is causing problems with our SQL applications we are seeking a solution.

Any assistance and suggestions are greatly appreciated.

I have a folder at a drive that was previously read-only in a DFS. The drive went full so I would like to move data to another disk. Now I've stopped the DFS and I've deleted the server as a member in the DFS. Now I have copied the data to another drive and I've started the DFS again, readded the computer with the new folder as member. This is done over 3-4 days as the amount of data is large.

However I cannot delte files in the old drive. It seems somehow marked as read only. I have full access to the files, and I've also tried deleting in admin mode. The error from CMD.EXE when trying del <filename>  is "Access is denied."

I am considering deploying Server 2012 DFS for our two sites to host redirected Home dirs,  TS profiles, and general network shares, ideally in an Active/Active or if I have to an automatic fail over situation. From what I read here:

http://blogs.technet.com/b/askds/archive/2010/09/01/microsoft-s-support-statement-around-replicated-user-profile-data.aspx

I decided not to do it with 2008 R2

I have read there are a lot of improvements with 2012 DFS. Have the concerns about file locking, corruption, and over writes been eliminated for high change risk files been mitigated in the latest DFS version? 

I have not been able to find a blog post regarding this on Bing. 

Thanks.

I have a very small lab environment with a 2012 AD server and two 2012 clients which I am testing DFSR before placing into production.

I can't seem to get a Namespace created.

Regardless if which host I try to create it on, I get the following error:

\\domain\shared: The namespace server \\hostname\shared cannot be added.  The user name or password is incorrect.

The wizard does not ask for a username or password.

I am logged in with the domain\administrator account.

The share does get created.  I have given Everyone and domain\Administrator  full control.

I am stumped and am looking for direction.

techsupport

I have just set up DFS in our environment.  We made a full backup of our existing file server running 2003r2, restored the backup to our new 2012 server and then set all of the shares as individual replicated folder sets between the 2 servers to make sure all changes get replicated.  All users were still pointed to the 2003r2 server, until today when we pointed some users to the namespace as a test, and that really pointed out some issues.

One logs folder that is being replicated has a very large discrepancy, in that the original 2003r2 server has over 10,000 files in it, and the corresponding folder on the 2012 server contains less than 5,000 files.  Then we also noticed that one log file that gets written to multiple times throughout the day exists on both servers, but has completely different data in both servers - almost as if it is alternating which file to write to instead of writing the file and replicating the change as we would expect. 

There are no errors showing in the DFS replication log in event viewer.  I ran a health check, and for the 2003r2 server, for each replicated folder, it says the status is normal, the backlogged sending transactions and backlogged receiving transactions are both just listed as "--".  The # of files received is 0.  On the 2012 server, each replicated folder says the status is Indeterminite.  The staging folders seem to be empty as well.

During our initial testing, the replication appeared to be working as we expected it to work...  I could create a file in the namespace, and it would almost immediately make the change on the server.  Now this is not happening, but the services are running and DFS itself seems to think it is running just fine.

Does anyone have any ideas that would help me figure out how to get this working?