Jump to content
Covecube Inc.

TAdams

Members
  • Content Count

    6
  • Joined

  • Last visited

Reputation Activity

  1. Like
    TAdams reacted to Christopher (Drashna) in File System damaged - NO errors in chkdsk or windows chkdsk   
    Have you tried resetting the status in StableBit Scanner?
     
    To do so, open the UI, double click on the drive in question, click on the ">" button next to "File system health" at the bottom, and click on the button with the green circle, and select "mark as unchecked" (or to that affect). 
     
    If it continues to come up as "damaged", enable logging, and reset the status:
    Click on the Settings button in the toolbar and select Scanner Settings. Enable the Show advanced settings and information option, and hit "OK". You will only need to do this once, from now on, it will always display this option. Click on Settings, and select the new Advanced Settings and information option. This will open to the logging tab, by deafult. Find the "Chkdsk" option, click on it and select "Verbose".   Once you've done this, let it rescan the disk, and if continues to error out, grab the contents of "C:\ProgramData\StableBit Scanner", right click on the "Service" folder and select "Send To" > "Compressed Folder".   Then upload the compressed folder to us at https://stablebit.com/Contact
  2. Like
    TAdams got a reaction from Jaga in Moving from WHS V1   
    First of all, I would like to say thank you all for taking the time to reply and or answer. I currently have an SSD which Windows Server 2016 Standard which has my shares as well as drive pool installed and I have gotten pretty far along in the setup and is pretty close to how I want it. Again, I realized I was missing the "sever essentials" backup system and I installed that. I believe the issues I was seeing is from the way the two flavors deal with file permissions. I initially had them set with Standard and when I added Essentials it added many permissions (per user and or group) to each file. Each mechanism allowing/disallowing rights based on that systems scheme. Which meant I had some doubled up and files that I shouldn't have access to - I did and vice versa for others. In short it seems like the most practical way is to perform a clean install and use which ever system to create and administer the shares - not both or a mix and match of both. I don't think this was a Drive Pool issue at all, simply put it was my lack of understanding of how the two systems apply user permissions.
     In my first install, I tried Windows Server Essentials and had backups running but did not like the strange folder structure, which is why I tried downloading and installing Standard and added the server role. I believe I could live with it, but the current look is so clean and that of course leaves me without the previously mentioned backup solution. I have checked out Veeam which looks VERY promising I appreciate the suggestion Jaga!
    I hadn't realized MS had planned on removing the ability to add Essentials Role in the future Umfriend, is there anything in particular you are looking for in WSE 2019?
     
    Thank you for the links Christopher, those are put together better than the tidbits I located in my searches. Currently I am trying to decide what I want to purchase, Windows Server 2016 Standard, WSE 2016...They are roughly the same price on Amazon and it seems like the Standard with provide greater flexibility for the future.  I am most certainly getting drivepool!
     
    Thank you all again! Regards,
    Tom
  3. Like
    TAdams reacted to Jaga in Moving from WHS V1   
    The only tidbit of wisdom that I can offer is what I've been told before about how Drivepool "talks" to the pool drives.  It merely passes commands to them like Windows would to any NTFS drive (although there are some "wonky" things NTFS does that Alex had to work around).  I wouldn't think this would interfere with regular copy/move/delete commands, even on system folders.  @Christopher (Drashna) is the real WHS/WSE/Drivepool guru however, so it'd be best to wait and hear what he has to say.
    As for the rest of your criteria - even Windows 7 Pro + Drivepool can handle them, with the exception of WHS V1 style client backups.  The W7 Ultimate server I'm running on now (which I'm going to be upgrading to WSE 2016 soon) does all of them except the backup (currently using Macrium Reflect).  After I migrate to WSE, I *think* I'll be using Veeam for backups based on the research I've done so far.  If you haven't looked at it, it may be worth the time.
    And while WSE might seem to be overkill in a lot of circumstances, I value it highly for the learning experience it provides.  Some of what it does is "next level" stuff, which you don't get to see in a standard desktop operating system.  That comes in handy for me since I'm in the IT field professionally, though it may not for a lot of people.  Because of that, I feel it's worth the extra effort.  I'm going to be installing it on top of a Hyper-V on bare metal...   just for the experience.  If you're into server based installations for any reason, it's good to keep up on the current popular platforms.
  4. Like
    TAdams reacted to Umfriend in Moving from WHS V1   
    For me, the client backups are what makes Windows Server worthwhile. File sharing, running a certain downloading client (that we'll not discuss) and media server etc. are nice extras (although that can be done on a W10 machine as well of course). I am currently at WHS 2011 and intend to go WSE 2019 (which as it turns out will be a SKU, but WS Standard won't offer the Essentials role anymore). It'll be a steep learning curve for me as well, which is a shame. But that is the one reason I am waiting a bit still and go WSE2019: It'll be longer before I have to go through that experience again. My main issue is that with WHS v1 (and 2011 somewhat) there were online resources aimed at, well, SOHO. With WSE2016 en higher that is far less the case. If you find one, pls let me know.
  5. Like
    TAdams reacted to Christopher (Drashna) in Moving from WHS V1   
    Windows Server 2016 Essentials is a very good choice, actually!  It's the direct successor to Windows Home Server, actually.  The caveat here is that it does want to be a domain controller (but that's 100% optional). 
    Yeah, the Essentials Experience won't really let you delete the Users folder. There is some hard coded functionality here, which ... is annoying. 
    Depending on how you move the folders, "yes".  Eg, it will keep the permissions from the old folder, and not use the ones from the new folder. It's quite annoying, and why some of my automation stuff uses a temp drive and then moves stuff to the pool. 
    If you're using the Essentials stuff, you should be good.  
    But you should check out this: https://tinkertry.com/ws2012e-connector
    https://tinkertry.com/how-to-make-windows-server-2012-r2-essentials-client-connector-install-behave-just-like-windows-home-server
     
×
×
  • Create New...