I want to know about active directory database files. Can anyone share the list?
Thanks in Advance
I want to know about active directory database files. Can anyone share the list?
Thanks in Advance
I'm in the process of retiring an older DFS server that's running Windows Server 2008. Currently, I have 2 namespace servers replicating all DFS shares. DFS is setup as AD integrated with 2 sites (site A and site B). Site A is running Windows Serve 2016 and it will remain. Site B is currently running Windows Server 2008 and I have a new server running Windows Server 2016 with the DFS roles installed. Both sites are connected with a VPN tunnel of 5mbps.
My question is when I add the new namespace member, should I add each namespace share with the "Add Folder Target" option and allow the replication to complete for each folder before I add the new server as a namespace server with the "Add Namespace Server" option? I'm trying to reduce the load on the network and I'm not in a hurry. It's my understanding that if I add the new server as a namespace server 1st, it will automatically start to replicate all of my DFS shares and I'd like to do this in stages.
After the setup of the new Windows Server 2016 in site B, I will retire the old Server 2008 box.
Thanks for any input.
Ken
I have a couple file shares on a Server 2016 build, the users are able to access the files no problem, but when reviewing the event viewer I found this error which I am not sure what it is relating too.
Log Name: Microsoft-Windows-SMBServer/SecurityHi,
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!
I have two 2019 servers with groups/partnerships replicating successfully on them.
I want to monitor their ReplicationStatusfrom a 2016 server so I installed the Storage Replica module through Server features. For some reason the get-srgroup command returns nothing when run from a 2016 targeting a 2019 one. Other commands such as get-srpartnership are working as expected in from/to the same servers.
The StorageReplica module version is the same at 1.0 on both servers.
I’m guessing this is a bug though I cannot find anything about it searching. Anyone else experienced this or have info on it?
Hello!
I need to replace our old file server. I also would like to create a domain based DFS namespace.
The old server is running 2008 R2.
The new server will be running 2012 R2.
All server are running in Hyper-V environment.
Summary of requirements:
1. The path to files needs to be intact since we have shortcuts in mail, sharepoint and so on.
2. The permissions must not change.
3. There are too much data to copy. I would have to buy more storage and end up with a lot of unused storage after migration.
I do have access to a NAS for temporary storage if it helps.
I had a plan but it doesn't solve the storage issue?
1. Set up a new file server with DFS.
2. Robocopy a test folder from the old fileserver to the share.
3. Create a DNS alias and test access to the share with it. The DNS alias would be changed to the old fileserver name after full migration and keep the paths intact.
4. After verification of permissions and paths do a full robocopy.
5. Shut down the old server and update the DNS alias.
6. Update linked paths where it is possible and remove alias?
Is there a fancy way of doing this more easily?
'm trying to create a storage space, but receiving the error "The Request is Not Supported." I've tried creating the pool using a different combination of hard drives and on two different computers. I receive the same error with all attempts.
I've have run the command get-physicaldisk in PowerShell and all of the drives have a status of False under CanPool. I followed up with the get-physical | FL command and it shows the "CannotPoolReason" as "Insufficient Capacity" for all of the drives. I found some information that you needed at least 1 GB for each drive. The minimum amount of free space on the 6 drives I'm attempting to add is 1.36 TB. The others are all 4 or 5 TB drives. Does anyone know how I can get these labeled as True for the CanPool status? I feel this is the problem, but I don't know how to change the status.
We are trying to configure new file server mirrors with DFS + DFSR on them and our existing file servers in our three environments. Sandbox-Dev-Live. All are under the same domain. I was able to successfully create a namespace from the "new" sandbox-FS02, \\domain.net\sbox\, and had no issues getting replication up and running and all was looking sunny and easy.
In "dev", however, things are not so easy. When attempting to create the \\domain.net\dev namespace, I receive an error error on both dev-fs01 and dev-fs02. For the sake of simplicity here I'm leaving everything default. Not changing anything with shared folder location, details, or path. The shared folder does not exist before creation. Default path of C:\DFSRRoots\Dev is being used. "All Users have Read-Only Permissions" is checked. Domain based, with 2008 mode checked.
The namespace in question has never been successfully created and there are no associated registry entries for the namespace on any DC.
The error in question is as follows:
"\\domain.net\dev: The namespace server \\dev-fs01 cannot be added. The specified server cannot perform the requested operation".
There is no associated EventViewer Log Error, on either file server or any domain controller within the domain.
I have done a lot of troubleshooting already in terms of network connectivity between the servers and the PDC, permissions, verifying NETLOGON shares, AD replication... out of ideas at this point. I can provide any (sanitized) information that is desired about the environment or the error.
I am migrating DFS shares on old file servers to server 2016. I can add the members based on existing memberships using powershell but when I try to set the membership to read only using powershell I get the following error:
Set-DfsrMembership : The read only property is not supported. The read only property is not supported.As a work around I have been manually setting them to read only using the DFS Management pane. Can anyone explain why I would be getting this error and how to work around it? I have tried setting it to read only when I set the other DFS properties and I've also tried setting it independently in a separate command. I am using the same variables to set the other DFS properties without issue.
Hi,
We have Windows 2012 file server. This is just a windows server and folder are shared with NTFS permissions. Not ftp.
One of the user is not able to access the shared folders. The user is able to access the shares from other pc. Only this pc is having the issue and we cannot format the pc as the pc is working perfectly for other users and their shares.
I have removed the permissions and re added the permissions. Still the user is having the same issue. I have uninstalled antivirus and no firewall is there. I can access from other pc and other users can access their shares from this problematic pc.
Kindly let me know the steps to resolve this issue. The client is using Windows 10.
Hi,
Can I limit shared folder space for each domain user using FSRM?
Thanks
Hello. We have 3 storage, with 3 iscsi disks conect to 2 server with windows server 2019 Datacenter. The disks have each one 512GB. I need to create an pool inside cluster and is ok, but when i try to create Virtual Disk in parity layout, shows me an error.
I copy bellow.
Can you help me please??
"Failed to create virtual disk - Not supported
Extended information: The storage pool does have sufficient eligible resouces for the creation of specified virtual disk.
Recommended Actions:
- Choose a combination of FaultDomainAwareness and NumberOfDataCopies (or physicaldiskredundancy) supported by the storage pool.
- Choose a value for NumberOfColumms that is less than or equal to the number of physical disks in the storage fault domain selected for the virtual disk.
Hi All,
i got win os16 as file server and its working as it shuold
My main issue is that is one spacific server whos in the domain that connected to this files server
I can see him on comp managment----shared folder----sessions----computer name
The thing is that computer name is shows without domain suffix all other servers connected contain the suffix .
Now whan right click on other server and do "close session" that spacific server giving me this error( a sesion do not exist with that computer name)
Although i can see sesion coming and going from him .all other servers in his g AD group are identical and showing suffix and closing sessions right.
Tryed to reset acount resubmit the comp again to the AD atc...nothing works.
your help needed,
regards
EL
We have been running Windows Server 2016 with ReFs for some months now. Its a supermicro server with 5x Seagate 4TB SAS Drives. Storage Spaces is running a mirrored layout and a hot spare. ReFs is the file system on our D:\ drive.
Today windows update restarted our server and the ReFs filsystem was not detected after reboot. The D:\ volume was recognized as RAW!
After some initial investigations we did a full shutdown and cold boot. When the system came online the D:\ volume was recognized as ReFS again.
I looked into the event viewer and saw several entries under \Application and Services Logs\Microsoft\Windows\DataIntegrityScan\Admin and \CrashRecovery. They look like this and entries exist since we took the server into production.
Volume metadata inconsistency was detected and was repaired successfully.
Volume name: D:
Metadata reference: 0x204
Range offset: 0x0
Range length (in bytes): 0x0
Bytes repaired: 0x3000
Status: STATUS_SUCCESS
From within the task scheduler i ran the Data Integrity Scan and a new entry like the above appears.
Questions:
Hello,
I am having a problem with Storage Spaces - it won't start recovering the mirror set.
The mirror set got degraded because one of SATA ports on the controller went bad (I/O errors with any hard drive on that port).
After the hard drive is reconnected to another port, Storage Spaces still shows the drive as 'Retired'.
I can unmark the disk by running Set-PhysicalDisk -UniqueID id -Usage AutoSelect
Then, I can access a Simple (non-mirrored) thin-provisioned virtual disk located on that physical disk, and there are no I/O errors in Event Log, or any other errors.
But after I attempt to initiate Mirror set repair (Repair-VirtualDisk -FriendlyName mirror), the physical disk becomes 'Retired' again, although no I/O errors have occured.
Seems that somewhere in the metadata there is incorrect information about actual disk health state, and I need a way to reset it.
Thank you.
Hi. I have a Windows 2008 R2 Hyper-V server which shows FC SAN disks as SCSI. I have uninstalled/reinstalled MPIO feature but the MPIO tab is missing in the Disk Properties window.
I also see 4 instances of each disk.
Specifically, it shows in the title bar of the Properties window: NETAPP LUN SCSI Disk Device Properties.
All my other hardware-identical servers in this cluster, attached to the same storage, show: NETAPP LUN Multi-Path Disk Device Properties.
I do not know how to find and add the hardware IDs, but not sure that will help. I've got to be missing something obvious but I cannot find it.
Thanks!
Dan
Hello, Expert,
Half year ago, remove printer manager from Domain. because we found plenty of printer as re-direction in Domain PCs.
Recently, we install one big business printer on one workstation(windows server 2008R2). and set up as share printer. Domain users share this printer for their works.
Today found plenty of printers (even Adobe pdf, microsoft XPS etc, and some older printers which already removed long time ago)
deployed to Domain computer.
how can we remove these redirected printers? I can remove from each pc. but I am afraid of they will automatically come again.
how can we stop and clean up the printer deploy server in Domain?
(No printer server in The Domain, How domain deploy these printers(already removed long time ago)
Is there any remaining not clean up completely?)
shall we re-add printer service again and delete the printers from the printer server and remove the printers service from Domain again?
tks n brgds
Liu Wei
Hi Dears
i need your support to modify more than 2000 shares , Remove everyone full access and grant authenticated users full access ,
i got it for Server 2012 , i need it for 2008& 2008R2
Server 2012 Standard
Hosts AD, PDC etc.
Shares access from clients (Win7, Win10) will randomly 'freeze', and will not become available again until a server reboot
SMB client log on the server is showing error 30809 described as <Guidance: The server is responding over TCP but not over SMB. Ensure the Server service is running and responsive, and the disks do not have high per-IO latency, which makes
the disks appear unresponsive to SMB. Also, ensure the server is responsive overall and not paused; for instance, make sure you can log on to it.>
There are no error logged in the applications log or system log.
Any ideas as to cause or remedy?
Thanks, David L.