Microsoft is changing the update policy for windows 10 per this article on thurrotts website
a couple of years ago, I stopped using a windows 10 homeserver because the update cycles kept breaking things
this new announcement could cause some reconsideration of this.
Don't think I am going to replace my Qnap nas anytime soon -its been rock solid
but if I where building a new server, would consider it.
wouldn't be hard to set up machine with a lot more capability than most NAS's without laying out 400 bucks for a windows server license
and you can use Drivepool, which I miss from my W10 server
I've looked up a lot of topics about this, but i've always find the half of the answers to my questions. I guess it's an unusual situation this time...
I would like to install windows 10 to my server in AHCI mode but without intelligent provisioning (it's died while upgrading it so there is no option to use it, that's another topic).
I'm able to boot the windows installer from iLO remote console but it cannot find the hdd driver. I've tried with few drivers, but no luck.
When the raid controller is the selected controller (the raid would be perfect too), the installer doesn't boot up.
-AHCI mode on( the installer is boots up in this mode only)
- No intelligent provisioning
-HP smart array won't load either
-This concept is possible?
-If yes, the raid is possible without IP and HP smart array?
-Is this will be easier with VMware esxi?
Thanks in advance!
After 2 disk failures … and the W10 April update … and the first patch Tuesday …
… I've been spending a lot of time moving data and testing this past 2 weeks.
I prompted the so called '1803 feature update' immediately it was available via Windows Update, having prepared via Insider test builds.
The process went through slowly but steadily on all my machine types … which you will see from my signature are all pretty old and low powered devices.
There was a vestigial File Explorer item which once closed left everything intact bar the usual window rearrangement/prompts $MSFT likes to make to File Explorer and Edge.
Oh and the usual additional forcing tactics e.g. you see a yellow warning flag on the defender security notification icon if you are logged on to a local account rather than a Microsoft email account.
Only 1 bug to speak of - I have not experienced the problems others have been reporting in the press.
The HOMEGROUP feature has been removed from this release with a likely side effect: other network machines and their shared file systems no longer appear under Network Places.
They are accessible but one has to type the machine name in the File Explorer address bar e.g. \\HPMICROSERVER5 to start any action.
Since I have been moving lots of files around I have also noticed that the network is not as stable as before: a remote shared area can be accessible one minute but not the next.
No showstoppers for me (famous last words).
After 2 days and no problems with the Windows 10 Fall Creators Update I thought I'd report my conversion experiences.
The upgrade was offered immediately on N36, N54 and Gen8 microservers, which in my case are running Windows 10 Pro.
I accepted the 'in place' upgrade on 3 of my 4 machines ... with some trepidation since the last upgrade destroyed my shared folder configurations.
No problems of any sort thus far: only the splash screens for the new features in Edge makes one aware that things have changed.
'In place' with HDD's for the OS drive is .... very slow ... we're talking hours.
The 2nd of my Gen8 machines stalled mid way through upgrade ...but I don't think that was a server or Windows problem: when I reverted to the old OS version disk errors were reported so I suspect the OS disk is on its way out.
After repairing bad blocks I tried a clean reinstall. This is much faster (40 minutes) but one has to reinstall programs and reconfigure. Not a problem since this is only a file server, so only shared folders to reset. I'm glad this happened in one way ... good I think to remind oneself of how to handle a rebuild ... since I could not find the B120i driver file ... or indeed any other HP drivers for the Gen8, which should have been in my machine installation archive. Corrected.
The usual sites were reporting that the new version of Onedrive requires manual installation. Worked fine.
Time to explore the new features then.
I've had it in the back of my mind to try REFS via Storage Spaces for some time. Unfortunately this is another case of NASDAQ:MSFT going backwards for consumers: that option is now removed and only available in the new Windows Pro for Workstations edition. Which I won't be buying.
To be fair though the upgrade has worked without problems on LINX 1010 tablets and my old DELL PC, SAMSUNG laptop, so my initial reaction is to give MSFT the thumbs up.
Hope everyone else has good experiences too!
WARNING - I updated my Windows 10 box to 1709 FCU tonight and it would only recognize one of the two Nvidia GTX 1060s that I had in the box. I have not done any troubleshooting, but when I rolled it back, it worked again. There could be issues with this update.