Windows 10: Windows home server folder mapping fails in Redstone preview

Starting with the Redstone insider previews, my HP mediasmart home server works for automatic backups, and I can open the server console to manage the server.

But it is impossible to map a folder on the WHS to a drive.; none of the shared folders on the WHS are visible, and the homes server is not visible under network.

Troubleshooting indicates a missing protocol, but has no solution. Solutions suggested in other threads in this forum don't work either. Everything works fine on the no-preview PCs on the network. I am concerned that MS is abandoning the WHS and am worried about future official updates.

Has anyone else run into this problem and found a solution?

:)

 

Active Directoy "Home Folder" not mapping consistently Win10 and Server 2012

I'd like to start by pointing out that this issue is specifically with Windows 10 Pro on client machines and Server 2012 on our DCs and File-Print servers.

Users here in my business have been complaining about issues with the Home Folder not consistently mapping. It's affecting several different users.

They have many mapped drives, all of which are mapped via Group Policy but their Home folder "Q:" in this case is implemented through Active Directorys User Home Folder through the path
L:
\\fileprintserver\Personal_Shares\username .

On logging in (usually first thing in the morning) the users Q drive may fail to map, that is to say it's totally missing. Sometimes other drives are marked with the red X and disconnected but you can simply open these and reconnect them but the Q drive
is missing altogether. The users must restart their machine to get the Q drive to then map successfully.

The reason we map users home folder using AD rather than something through a GPO is that we use Citrix for remote users and we found using GPOs to manage their home folders resulted in some strange behaviour.

 

WHS 2011 Connector Fails with Windows 10

I have this problem with the Redstone previews. It looks like MS is abandoning WHS.

Troubleshooting indicates a missing protocol, but has no solution. Homegroups are not a good replacement for this; I've tried, had many problems setting it up; finally got it set up but still have problems. When mapping a drive, it sees the other PC but
then requests a credential that is unknown--MS account and local account credentials fail.

 

The linked article essentially says that MS abandoned WHS and rolled it into Windows Server 2012 Essentials: http://www.zdnet.com/article/microso...s-home-server/

 

Ok, no future development, but why disable it in the next release of Windows 10 (Redstone)? If so, it's an annoying disservice to us home users.

 

It has nothing to do with WHS. It is that Redstone is still in Alpha stage and that there is a lot of stuff that has not been incorporated in it. It explains this in all of the information related to being a part of that program. When it does release, then it will be in Beta, which all of us will get to keep telling Microsoft to fix their OS.

A lot of stuff is getting cut out of Microsoft 10 Redstone, that is right now in the latest rollout. Microsoft cuts features from Windows 10 Redstone update to meet deadline | Tech | Life & Style | Daily Express

Windows 10 Redstone: 1,200 changes between build 11099 and build 11102 WinBeta

Personally everyone would really like Microsoft to quit screwing around with the OS, trying to reinvent the wheel. they need to be concentrating on the problems that currently hound Windows 10.

 

Yes,; I keep hoping they'll get this to work, but after several Redstone updates, it's not looking good.

 

Tell me about it. It is like trying to fit a Big Block into a Pinto.