• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry

Drashna Jaelre (WGS)

Lead Moderator
  • Content count

  • Joined

  • Last visited

  • Days Won


Drashna Jaelre (WGS) last won the day on September 28 2016

Drashna Jaelre (WGS) had the most liked content!

Community Reputation

314 Excellent

About Drashna Jaelre (WGS)

  • Rank
  • Birthday 06/25/83

Contact Methods

  • AIM
  • MSN
  • Website URL
  • ICQ
  • Skype

Profile Information

  • Gender
  • Location
    San Diego, CA, USA
  • Interests
    Computers, Home Server (obviously), math, science, good books, friends

Recent Profile Visitors

14200 profile views
  1. Well, that you've said that, I think that was the issue. There are ways "around" it, but to be blunt, the Core 2 Duo line is 8 generations behind now? While the MediaSmart Servers were awesome little systems, building something newer would get you better performance with less energy consumption.
  2. IIRC, there were issues with installing Windows 10 on these systems, so you may not have a lot of luck But I haven't tried, so I couldn't personally verify this one way or another. If you're interested in building a new system, there are a number of Mini-ITX systems that may fit the similar form factor.
  3. VyOS is based on linux, and pretty much every linux distro has support for HyperV anymore. As for updates, that entirely depends on your setup. But Microsoft has changed the updating schedule even for older OS's. So you likely won't see many reboots.... and you should be able to schedule them for times that won't impact your network.
  4. https://support.plex.tv/hc/en-us/articles/201774043-What-kind-of-CPU-do-I-need-for-my-Server- And while the guide mentions Core 2 Duo CPUs, it doesn't even follow it's own guidelines (2000 score for each 1080p stream). And as the page mentions, this is a VERY minimum guideline, assuming the system is not doing ANYTHING else. The more you are doing, the more CPU you need to throw at it. And while in most cases a "big" CPU isn't necessary, when you start dealing with media streaming, you really should. Even if you feel it's overkill.
  5. Then that's the problem here. Transcoding/re-encoding is a very, very CPU intensive process. And if you have a few small number of CPU cores available, then it's going to use more CPU time and cause performance issues. If you plan on transcoding a lot, then you'd want a quad core or better CPU, IMO.
  6. Set it to use 4 cores, and see if that helps. And make sure you have at least 4GB of ram.
  7. Well, what are you using to stream? Also, how is the storage presented to the VM (a virtual hard drive, pass through, etc). Also, how much memory did you allocate and how many CPU cores did you assign to the VM?
  8. Well, given what you're planning on doing, that is probably still pretty overkill for what you need. Specifically the CPUs. Virtualization is going to be much more memory intensive as opposed to CPU intensive, and that's where your money may be better spent. That said, for the hyperVisor, I'd recommend VMWare ESX or HyperV Server 2016. Both of which are free, and both are good solutions. As for the OS, honestly, go with whatever is most comfortable for you to use. When things go wrong, YOU will be the one fixing this. That said, Windows Server 2016 Essentials supports local backup, server shares, Active Directory (domains), if you go with exchange for email... there is integration there. It features a remote access website, that includes VPN service and remote desktop gateway. And if you go this way, it may be worth checking out StableBit DrivePool, a pooling software, as it doesn't require additional hardware to created mirrored spanned disk array (it's file based, so any system that can read NTFS disks will be able to access the content). There is also FreeNAS and NAS4Free if you prefer linux type solutions. And speaking of which, you may want to look into ZFS, if you're using a Linux based OS. It's also a great pooling solution that doesn't require hardware support.
  9. "wherever you want". basically. If you're using the same pool from WHS, then using "\ServerFolders\ShareName" works well, and keeps things very organized.
  10. Run "FSMGMT.MSC" on the system. This will bring up the File Share Manager. From there, you can create shared folders. If you want to set it up like WHS, then set the share permissions to give "Everyone" full control, and then set the NTFS (securities) to be what you want
  11. How is the RAID setup? Software, hardware, etc? Without this info, it's really hard to help. I'm guessing hardware RAID, but it's best to not assume. As for not updating, this may fix that issue: https://support.microsoft.com/en-us/kb/3102810 As for the rest, run "chkdsk c: /r" and then "sfc /scannow" on the server, and this may help. Otherwise, download and run NirSoft's BlueScreenView, or "WhoCrashed" to see if you can pinpoint why the crashes occurred.
  12. Well, it's the non-rackmount box that I'd buy, if I was looking for a synology box. That said, I am not familar enough with the product to give you a good answer here. I *beleive* the USB ports can be used to backup/import data, as well. But I'm not sure. Contacting Synology would be your best bet. As for the RAM, that entirely depends on what you plan on doing with the box. Personally, more is always better, IMO. That said, I'm a glutton for punishment, and I'm running server hardware (supermicro 36 bay case, supermicro motherboard, Windows Server 2012R2 Essentials), and am mostly happy with it (now that I identified the crashing issue to the system SSD which gives CRC errors and locks everything up). But then again, I enjoy troubleshooting, apparently.
  13. Definitely sounds like you're having a hardware issue, here. And I'm sorry to hear that. And yes, the Essentials Dashboard leaves a lot to be desired. It's slow, it's buggy, and nothing has been done to fix it. It's part of why Covecube (StableBit) created stand alone UI's for their software... I'd be more than willing to try and help you with the hardware issue, but in some cases, yes, it is much, much easier to just replace it than it is to spend weeks troubleshooting (I've been there, and recently even). That said, Synology does have a "selector" page to help with this: https://www.synology.com/en-us/support/nas_selector This will probably help you out more so than anything I could say. Select your needs, and it will narrow down the list of hardware based on those options Though, my recommendation woudl be the DS1815+. Plenty of room, decent hardware, ~$900.
  14. Have you set up Anywhere Access on the server, via the dashboard? It should configure this automatically. Aside from that, it appears that you have to configure this from the ServerManager app on the server first. then you can use RRAS to modify the settings.
  15. No, this is a bug. Specifically, the main site should be using "C:\Program Files\Windows Server\Bin\WebApps\Site" (or similar) as the base URL for the website. For whatever reason, it's using the default "c:\inetpub\wwwroot" path instead. This appears to be a known issue, but one that hasn't been addressed yet.