So I've just physically inserted 4 brand new disks into a Dell server. I can see them as ready in Dell OpenManage, but when I got to create a storage pool its not picking up my primordial disks.

Do I need to go into the hardware SATA/RAID controller and configure them maybe? Just as a 1 disk RAID1 for each disk or something?

Hello!

We have server based on Windows Server 2012. It has FileServer role installed. 

We have shared folder, where are many other folders. Users see only those folders, that are available for them, because of setting. (File and Storage Sevices -> Shares -> Settings -> Enable access-baces enumeration)

So when I give permission to user for some folder in this share, after log off / log on or reboot he starts to see this folder.

So I want to do this without log off or reboot. How I can do this faster, without user interruption? 

Thank you!

Hi

I have a storage pool containing 2x physical disks. I have created a mirrored virtual disk on top of those physical disks, occupying all the space.

I would like to split this pool/mirror back into 2 separate disks, but retain the data. So basically end up with 2 separate disks each containing a copy of the data.

Is this possible?

Thanks

Hi,

we do have an rds farm with roaming profiles (not profile disks) consisting of 6 terminal servers ("srvts001" to "srv006" 2012 R2), 2 domain controllers ("srvdc01", "srvdc02" 2012 R2), 1 SQL/Fileserver ("srvsql01" 2012 R2).

Roaming profiles are stored on srvsql01 in share RDS. Oplocks are disabled, directory caching is disabled.

Everything was running without problems for 1 or 2 years. Recently (about 2 weeks ago) users began complaining about being logged on with a temporary profile. Investigation showed a lot of open file handles from previous (no longer existing) sessions on the file server.

E.g. user1 had logged on to rds one day and logged off in the evening (not just disconnected, really logged off) and when he logs in the other day on the rds farm he is logged on with a temporary profile due to the profile service being unable to access the roaming profile as it is (event log) "in use by another process".

Looking at the fileserver's open files we can see that a lot of files of that user profile (and of other users, too!) are shown as open - all with read option and no apparent locks.

When user1 loggs off these locks stay! Manually closing the open files on the file server allows the user to log on to the rds servers normally. Subsequent logging off may or may not create those stale open file handles.

We have no clue as to when these enormous amount of open file handles (we talk about 100s of files per user) happen. It seems to be at random and not hitting every user.

Has anyone ever met a similar problem? Or at least an idea on how to prevent logged off users to still have open files on the file server?

Any answer pointing in the direction of a possible solution or source of this problem is greatly appreciated!

This is a brand new 2012R2 AD environment and I have a test user that is only a member of domain users.  The folder structure I will use for an example is \\server\data-share\accounting.  Domain users have NTFS read-only permissions to the data-share folder so that they can list the contents, however, this is applied to the data-share folder only, not sub-folders/files so if you look at the permissions on the accounting folder, you will see no ACL entries for domain users.

So here is the issue, when I look at effective access on the accounting folder for the test user, they have 'read permissions' and 'change permissions' rights (see pic).  I cannot figure out where this is coming from.  Any ideas?

Image may be NSFW.
Clik here to view.

So, we're a bit stumped on something.  We have a fileserver on 2012R2 and a 2008 AD.  We have users who map to a home network drive.  We set the users up the same way every time.  Sharing is Everyone - Full Control, but then it's locked down by security.  We make the folder, then use the server manager to share it.  (That is if it's a new user, if it's a re-used folder we just change the permission.)

Users have modify rights to their home folder and any sub folders and files.  System, domain admins and local admin group have full control.  Usually the owner is the local admin group.

We've got one user who is having an issue creating new folders or saving to those folders.  Says access denied.  We blew out the folder, recreated it, then shared it.  It still marks any folder any user creates as having Special Permissions and then doesn't allow them to save things to it.  We gave the user Ownership and it still won't allow anything.  We almost have to break the inheritance to get it to work.

What's different on this user?  Are we missing something in their user attributes maybe?

Ben Rollman

We had a replication group between 2 servers offline for more than 60 days. These are the steps I've taken to bring it back online:

1. Made a backup of data on both file servers

2. Marked server 1 as primary member because it has the most up to date data. (Server 2 essentially functions as a backup in a hub and spoke configuration.)

3. Disabled server 2 in the replication group, and enabled it again.

Server 2 is now showing events stating it's ready to begin initial synchronization. However, Server 2 is showing events stating that it needs to be disabled in the RG, and when it is enabled, it will pull fresh data from the other RG members.

What is the correct way to restart replication from Server 1 to Server 2 at this point? My concern is that disabling/enabling Server 1 in the RG group will pull stale data.

We have a network share.  It uses Distributed File System (DFS).  When a user opens a file, it does not get marked as "open" and another user can open file normally instead of getting the Read Only notification.  Both users can even write to the file, overwriting the work of the other.

I've tried web searches, various troubleshooting, etc.  I can't find a solution to this problem.  Can anyone point me in a direction to start checking?  Thank you!

Hi,

Below PowerShell command shows number of users currently accessing a share.  Similarly, on Windows Server,  is there a way to find list of shares being accessed by a given user. 

PS C:\> Get-SmbShare | Select Name, Path, CurrentUsers

Name                                    Path                                                               CurrentUsers
----                                       ----                                                                 ------------
ADMIN$                              C:\Windows                                                              0
C$                                      C:\                                                                           0
D$                                      D:\                                                                           0
IPC$                                                                                                                  1
rmc                                     D:\rmc                                                                     2

PS C:\>

Regards/Susanta

We recently moved a large group of files from a Windows 2003 server to a Windows 2008 server.  These files are accessed by many users constantly throughout the day, so they are almost always considered open.  When those files were residing on the Windows 2003 server, any user or server could access those files even though they were open and make changes to them.

Since we moved the files from the 2003 server to the 2008 server the only users/servers that can still access and change those files while they are open are:

Windows 7 users
Windows Server 2008 server
Windows Server 2012 server

The servers that cannot access/change those files are:

Windows 2000 server
Windows 2003 server

Every time one of those servers try to access the file (or even just change the name of an open file for testing purposes) we get the following error:

Cannot rename <file name>:  There has been a sharing violation.  The Source or destination file may be in use.

We have tried the following to resolve it:

Verified all the permissions/shares are identical for the files on the Server 2003 and the Server 2008.

Changed the NTLM acceptance level on the Windows 2008 server by:  Go to: Local Policies > Security OptionsFind "Network Security: LAN Manager authentication level" Change Setting from "Send NTLMv2 response only" to "Send LM & NTLM - use NTLMv2 session security if negotiated"

Verified the times are identical on all servers.

Removed one Windows 2003 server from the domain and re-joined it again after the NTLM change.

The problem still exists.  Can anyone recommend a solution?

All

A colleague of mine accidentally deleted a DFSR namespace on our W2K3 r2 domain yesterday when meaning to delete a target(!), we've followed KB969382 to restore the DFS configuration blob back into AD from a recent backup and the namespace configuration has returned and DFS is functional from a connectivity point of view, but the namespace appears to have lost it's link to the Replication Groups we set up for the folders within the namespace.

Replication itself still works but if we go into DFS Management - Namespaces - <Our Namespace>, select one of the replicated folders then select the "Replication" tab it says "Replication Status: Not Configured", so the link between the namespace and the replication group seems to have been lost and replication is now running as standalone effectively. If we try to set p replication from the wizard here it fails with "The following folder targets cannot be added as DFS Replication members.... because the shared folder path (path) is already replicated on the server using replication group (\\domain\namespace\folder)", so it appears to know something about the replication groups but just not the link between the two but because of this broken link I assume if we add a new server to the namespace it wouldnt automatically get added to the replication group?

We have a lot of data in our DFS with relatively slow links so we need to avoid replicating from scratch so would like some advice on how to fix the issue, is it as simple as deleting the replication groups and recreating them or will this cause a complete replication to each target from scratch?

thanks

Hi,

Our company is an audiovisual company mainly doing editing and visual effects. We have a windows 2012 server and its configured to do mainly data hosting for 10 workstations and a hp serverblade with 16 blades in. Its set-upped to use a NIC team of 4 NICs to the switch.

When hosting large files like quicktimes of 4GB to several workstations I get a nice maximum of 4Gb/s through the network. But when we are hosting large numbers of image sequences (dpx and openEXR files) the speed drops to 220Mb/s. I also have to disconnect several machines to maintain this speed. (otherwise to much calls and the server slows down even more)

Any thoughts on this problem?

Best,

Fabian

hi,

we have dfs root or namespace hosted on 22 server but it is showing empty in one region that is sydney region.

I ran the diagnostics check with dfsdiag but couldn't find error.

It is intermittent which is going to resolve after sometime.

even \\dc\namespace and \\dfsserver\namespace is also showing empty.

any comments to resolve this is always welcome

I am looking at setting up DFS in our domain and hope to use an existing File server which hosts Homefolders as a DFS server.

I have set up 2 test File servers called Testserver1 and Testserver2. Both these servers are running Server 2012 R2. I have set up test accounts testuser1 and testuser2.

On the test servers and using the test accounts, I have set up test Homefolders on a share "\\ Testserver1\testhomefolder", so that the Homefolders are "\\ Testserver1\testhomefolder\testuser"1 and "\\ Testserver1\testhomefolder\testuser2".

On File servers Testserver1 and Testserver2 I have set up DFS and set up a Namespace "\\ domain\testhomefolder" and a Replication to replicate between the 2 servers. This Namespace seems to function fine and is tolerant to one of the servers being offline, where connecting to "\\ domain\testhomefolder" and any of its child items works as normal.

The issue happens when I change the AD accounts Homefolder field for either testuser1 or testuser2 from "\\ Testserver1\testhomefolder\testuser1" and "\\ Testserver1\testhomefolder\testuser2" to "\\ domain\testhomefolder\testuser1" and "\\ domain\testhomefolder\testuser2" respectively, and then log on as either testuser1 or testuser2.

At the point of logging on as either testuser1 or testuser2 after the Homefolder field has been changed, the old Homefolder is deleted. A log off and logon creates a new Homefolder, but it is empty and all contents of the original folder is lost.

Can anyone please advise as to what I need to do to ensure that the original Homefolders are not wiped when changing the Homefolders for each account from a Servername to a Namespace?

NB - the UNC paths don't actually have a space after the "\\". I added in a space so that IE did nothelpfully turn them into links which stopped me submitting this question.

I have a thin provisioned virtual disk comprising of three physical disks that is showing as degraded:

PS C:\> Get-VirtualDisk "Data" | fl FriendlyName,*Status

FriendlyName      : Data
OperationalStatus : Degraded
HealthStatus      : Warning

PS C:\> Get-PhysicalDisk

FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                              Size
------------        -------             -----------------   ------------        -----                              ----
Disk 1              False               OK                  Healthy             Auto-Select                     2.73 TB
Disk 2              False               OK                  Healthy             Auto-Select                     2.73 TB
PhysicalDisk0       False               OK                  Healthy             Auto-Select                       40 GB
Disk 3              False               OK                  Healthy             Auto-Select                     2.73 TB

When attempting to repair the disk with "Repair-VirtualDisk" the process errors out at 0%:

PS C:\> Repair-VirtualDisk "Data" -Verbose
Repair-VirtualDisk : Failed
At line:1 char:1+ Repair-VirtualDisk "Data" -Verbose+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/...SFT_VirtualDisk) [Repair-VirtualDisk], CimEx
   ception+ FullyQualifiedErrorId : StorageWMI 4,Repair-VirtualDisk

I can create a new virtual disk in addition to the existing one on the same three disks and no health warnings occur. I have installed KB3000123 and KB 2914743 which have been recommended elsewhere but saw no improvement.

I'm keen to avoid having to move the data to a new virtual disk, or backup and restore. 

How does quota management that is set on a volume track files owned by a group?  We would like to set ownership for a folder to domain group "File Administrators" but keep getting "out of disk space".  As we can only get a list of users, not groups when looking at the quota list, I can't figure out how to fix this problem.  Even turning off quota management so that everyone is no limit results is the same problem because the entry for the "File Administrators" group has already been set even though we cannot see it.  I'm willing to bet that temporarily unchecking "Enable quota management" would fix it, but I'd like to avoid doing that.  

More background: In server 2012 with the default permissions of "administrators" having full control, it adds the user account of the tech who tries to access the folder to the NTFS permissions for the entire share, wasting several minutes and cluttering up the ACL entries.  Our techs have personal AD accounts which they use for their work and server accounts which are only for server changes.  The solution was to make all the server accounts part of the File Administrators group and grant that group full control of all shares.  The first part of that process is to take ownership and assign it to "File Administrators".  This is being blocked by volume quota management which does throw an error in the event log saying it is the culprit.  There are no folder quotas set in FSRM. 

Hello,

Hello,  (Was looking for a migration forum so please move if this is not in the correct place)

We have a large 2003 file server that we need to migrate to Server 2012R2

We'd like to avoid having to copy any data and make this a simple procedure with little downtime.

Both the old and the new Server are running as VM's within VMware ESXi 5.1 

The 2003 file server has nothing special running, no DFS etc. Just a plain old fileserver.

It has a C,D, and E drive (3 virtual disks)   D and E contain the file shares.

I'd like to detach D and E (virtual disks) from the old 2003 Server and attach it to the new 2012 Server.

Then we'd export the "Shares" registry key from the 2003 box and import on the 2012 box.

(and handle renaming the new server to the same name as the old server via AD)

Has anyone done this without any major issues?   I've read about possible 8 dot 3 naming issues and partition alignment.

I'm not sure if we'd have any issues with 8 dot 3.  I'm not concerned about partition alignment as this server is not High I/O at all.

I understand that this is not the cleanest way to to this, but this will get us off of the unsupported 2003 platform. 

I'm prepping a lab now to test, but I wanted to see if anyone had run into any issues if they tried this. 

NTFS issues, etc.

Thanks for any input.

Hi

having some problem setting up a net share, I would like to setup a net share and set the permissions at the same time

This is what i run in a powershell windows

PS D:\dfsshares> net share dfs_company=d:\dfsshares\company /GRANT:EVERYONE,READ

The syntax of this command is:

NET SHARE

sharename

          sharename=drive:path [/GRANT:user,[READ | CHANGE | FULL]]

                               [/USERS:number | /UNLIMITED]

                               [/REMARK:"text"]

                               [/CACHE:Manual | Documents| Programs | BranchCache | None]

          sharename [/USERS:number | /UNLIMITED]

                    [/REMARK:"text"]

                    [/CACHE:Manual | Documents | Programs | BranchCache | None]

          {sharename | devicename | drive:path} /DELETE

          sharename \\computername /DELETE

Syntax looks okay to me

Alex

So I performed a replication of IIS from an old server to a new server (IIS 6.0 to IIS 7.5 being the current new server). I've copied over all of the sites and virtual directories. I can FTP and DIR on all of the newly copied virtual directories and sites except for one, however it works perfectly fine on the old server.

New server

230 User logged in.

Remote system type is Windows_NT.

ftp> dir

200 PORT command successful.

550 Keyset does not exist

ftp> cd xxxxxdir

550 The system cannot find the file specified.

ftp>

Old server

Remote system type is Windows_NT.

ftp> dir

200 PORT command successful.

150 Opening ASCII mode data connection for /bin/ls.

02-16-11  08:42AM       <DIR>          xxxxdir

09-16-13  07:48AM       <DIR>          xxxxdir

09-16-13  07:51AM       <DIR>          xxxxdir

09-16-13  07:50AM       <DIR>          xxxxdir

226 Transfer complete.

202 bytes received in 0.0013 seconds (153.98 Kbytes/s)

ftp>

I've read around that it was a permissions issue with a file in C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\xxxxxx but it didn't seem to fix the problem.

All permissions and authorizations are exactly alike between the old and new servers.