Search results

I guess if you have the knowledge then WSE2016 isn't complex but I don't and I wasn't interested in spending loads of time finding out when Windows10 would do everything I needed and I knew how to set it up.

I managed to setup the WSE server but the ongoing maintenance was to much for me, error messages kept popping up and I didn't have the necessary knowledge to know whatv was relevant or not. There is a 180 day evaluation key that can be re-activated up to 5 times so effectively a 900 day license.

I'm sure you have figured out by now that the cheap keys are not legal. In the end I decided that WSE2016 was too complex for me to manage, and the tiresome hacks needed around domains when, when all I wanted was somewhere to backup my PC's too and use as a file server so I now have a Windows10...

A small issue....... Yesterday I installed a new hdd to the server, I formated it and added it to the shared pool (I'm using Stablebit Drivepool). When I booted the server I had no access to the server via my test pc and when loading the server dashboard there were no users or devices listed...

Not keen on spending nearly £700 for a WSE2019 key! I have an evaluation key that has activated my installation.

Does anyone know a good place to buy an activation key for WSE 2016, I've seen them online but not sure of their authenticity. Thanks

Thanks but thats way to much power for something that will only be a file server and handle client backups. I might just buy an extra 8gb ram to give me 16gb and upgrade the cpu to an i5 or i7, if I can find one secondhand.

Now that I am happy with the evaluation of WSE2016 my thoughts have turned to the server hardware. At the moment my WHS2011 runs on desktop hardware (ASRock H77 Pro4 M mobo, Intel i3-3220 cpu and 8gb ram). I think this hardware should be ok, maybe with a ram upgrade to 16gb, but now is the time...

Same for me plus the server is configured to automatically backup our computers.

Yes, I read that WSE2019 had dropped features that I use in WHS2011 and hence why I went with WSE2016.

Probably a bit far for me at the moment. I'm surprised there have not been more members posting on this thread, is upgrading from WHS to WSE not popular?

My test client PC seems to be working with WSE2016 without being a member of the domain. To get this working I did the regedit "SkipDomainJoin" (only required for W10 Pro clients, W10 Home does not support domains by default), installed the WSE client connector, deleted the domain user account...

Its occurred to me that even with the server managing DNS my other devices won't be affected as they won't have the client connector installed. I can also add an alternative DNS on the client PC, in this case my router provides the alternative DNS

Yes, I see both the user i setup plus the new user that WSE automatically setup. I would have thought that if I logged in with an existing user name that WSE wouldn't create another user with the same name other than the domain name on the end.

Today I installed the WSE connector on the test PC. The install process basically looks like a new Windows10 install process asking lots of very similar questions but when the install completed my test documents in the "documents" folder were gone! Not what I was expecting as they were gone for...

Thanks again. I think I will setup a temporary account on a spare PC and see what happens but I don't want all my files moved to the server as the server will be setup to go to sleep (like my existing server) when I don't want to use it also being the DNS will cause issues for our smartphones...

Thanks for your reply but I don't want anything to interfere with local accounts. We have 4 PC's on the network all with local accounts. I also don't want the WSE server to deal with DNS as my router does that already and I am happy with that arrangement, it just works and if the router goes...

My issue with domains might just be my lack of understanding how they work and what effects they have on my PC's. Same with active directory. I found some info by Microsoft about setting up the server to operate in a workgroup rather than a domain but I needed to make the changes during setup...

I am in the early stages of evaluating Windows Server Essentials 2016. My existing Windows Home Sever 2011 is no longer supported or getting Microsoft updates so a change is required. So far I have installed the OS, setup an admin user, setup a couple of standard users, setup disk pooling, setup...

Deleted.........