Increase the size of user profile disk in my remote desktop server
Hi all experts. I have a server for remote desktop services purposes, Windows 2016 standard, and domain joined. It is configured using User Profile Disk, and the maximum limit is set to 5GB. I want to increase the maximum limit but I can't do it under the collection's properties because that field is grayed out. My questions: How to increase the maximum limit? Please guide me and let me know how. Can I increase the maximum limit for 1 single user only? If yes, please let me know how. I found some info from the web that this can be done by the Diskpart command, is it true? If I follow the Diskpart method, do all user profiles encounter data lost? I need your guidance and input, I appreciate it. Here are some images:Write to workgroup fileserver from AzureAD joined device.
Hi, We currently have a situation where we are trying to install a program locally, but we want some of the data files (master data for projects, company settings for the most part) to be stored on a fileserver. The installer allows for this change to set UNC path to the share manually, and in our case recommends doing that. The problem we are facing occurs when trying to go on with the installation, the problem reports back that write-protection is enabled. I have the share mapped as a nettwork station, and can create folders/files through explorer. But I think the issue here is that the share mapped using the "Connect with different credential" option, which is required since the share is on a server in a workgroup and the client I'm using is joined to AzureAD. And when i run the installer for the program it is ofcourse ran with my azure user (local administrator), and I guess it tries to write to the UNC path with that user ofcourse. Is there any way i can let the program write to the share without it being to much of a security risk? The same program also has a nettwork license installed on a different workgroup server. I also had to add local users to that server and do some DCOM permission tweaking for that to work. For the license part i can authenticate with the local server user, but thats not an option when trying to install with UNC path for the file/folder structure.feature Installation Error
I am facing this issue in Windows Server 2019 STD. i am also tried to solve this issue to select sources\sxs path from the OS media but still i am getting the same error. Mistakenly i have removed .Net framework from this server and after that i am facing this issue. please help me to solve this issue.
Possible to recover permanently deleted files windows server 2016?
Hi everyone, I am currently managing a Windows Server 2016 setup and accidentally deleted some important files. Unfortunately, these files are not in the Recycle Bin, which makes me think they’ve been permanently deleted.The server holds critical business data, and recovering these files is a top priority. I have not installed or written any new data to the affected drive to avoid overwriting the lost files. Before diving into third-party tools or professional services, I want to explore any built-in methods or reliable tools recommended by the community for recovering permanently deleted files on Windows Server 2016. If you've encountered a similar issue or know of any solutions, please share your expertise! Looking forward to your advice. Thanks in advance!
Windows Server 2019 grey "X" on folders on LTO
Hi everyone We have just upgraded one of our servers from 2016 to 2019 Std. Since then when I try to copy a file to the LTO, which is directly connected to the server, icons appear with a grey "X" in the bottom left corner. I tried moving the file but the same result appears (when I move it back to the Desktop the "X" disappears). There is no cloud sync of any kind related to this server. Just to be clear, everything worked fine on 2016. Hope someone is able to help. Thank you in advance. Best regardsWindows Storage Spaces with storagebuscache and basic disks
Hi I have a standalone server which has different sized SSD(NVME) drives and HDDs(Jbod, 12TB) drives. 1 x 3.2 TB SSD NVME - a basic disk with a single volume with a couple of shares and data in the drive. Plus new drives designated for a Storage Bus Cache - Storage Pool 4 x 12 TB SSD NVME 32 x 12TB HDD I checked before running the commands and the single 3.2 TV SSD had "can pool" = "False". After following the MS doco to enable-storagebuscache which successfuly created a new Storage pool with the designated 4TB NVME and the 32 HDDs and ignored the 3.2 TB basic disk. However I also lost access to the 3.2TB basic drive. ie its no longer accessible via disk management. https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-storage- bus-cache I executed "disable-storagebuscache" and regained access to the basic disk, the data on the drive was unaffected. The basic disk wasn't added to the storagebuscache storage pool, however I still lose access to it each time I execute "enable-storagebuscache". Does anyone know how I can ensure the basic drive is excluded from "enable-storagebuscache"? Thanks NyobiDrivers to install Windows after wiping out partisions
I have two servers (an old physical server and a VM hosted by VMware Workstation) with 3 iSCSI disks each. A previous Linux installation was wiped out using Gparted from both servers. When I try to install Windows Server 2022 I can't select any drive to install Windows and I am requested to load a driver. Where can I find the driver to recognize the disks? What can I do with Gparted or any other tool to make the disks visible by Windows installer? By the way, I can install Linux on both servers without any problem. Regards
Windows Server 2016 on ESXi, two servers solution in case of failure
Hi, I'm facing a problem I still can't find a solution to. Short description below. ESXi virtualization environment has a Windows Server 2016 Datacenter installed. The Server has AD switched on, for the sake of our discussion I'm naming it "contoso.local". There are shared resources on the virtualized server such as shared folders and files, also there is MS SQL server which receives incoming connections from Windows clients (Win10/11). What do I need to achieve? I need to create another virtualized Windows Server 2016 Datacenter or Standard which will be an alternative server that will start offering its services immediately in case of the another server failure. What do I mean by "immediately" here? I mean, the switching procedure/time must be immediate and all the resources such as shared folders or SQL databases must be up-to-date. So, if at 1:00 PM the first server has a failure (disconnected, shut down by mistake etc), the other server must take control of the client machines at 1:05 PM. And as I mention all shared resources and SQL connections must stay the same but on the second server. The users on client machines can't have their work disrupted (any open Word documents in shared foilders intact or financial software connections kept on). I'm aware of the fact that the second server must be a sort of replica that works all the time and receives data from the server so it must be a 1-1 copy of all data that it constantly updates itself with new data coming from the first server. The question is - how can this be done ? I tried Cluster failover, storage replica already but this mechanism didn't work out. I created two disks (logs, data) according to step-by-step instructions but it is still not a solution to the problem. I'll appreciate any advice to my issue
