Allen, If the client is running a domain then the machines must be members of the domain to get full access rights to the server obviously.
If the Win 10 has been set up with a Microsoft account as login then this must be added into the domain as opposed to using the default machine name (or whatever they used on Windows 7). We discovered a similar problem when we had to default Win 8/8.1 login as it isn't or wasn't obvious then that you could use a non Microsoft login account!!!
The Microsoft seems to cause too many problems especially seeing as how we restrict all machines on internet access which the Microsoft login sometimes doesn't like. I guess it is all to do with the ET 'Phone Home' syndrome.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Allen Pollard Sent: 16 August 2016 10:39 To: profox@leafe.com Subject: RE: [NF] windows server 2007
Ah ok so 2008 is not a problem with win 10? So it has to be setup of win 10? I see that there is, on the accounts setup, a choice of logging in as Microsoft account or other. I wonder if other will solve the problems. The problems being unable to connect to server drives and outlook to exchange server. Al
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Alan Bourke Sent: 16 August 2016 11:17 To: profoxtech@leafe.com Subject: Re: [NF] windows server 2007
On Tue, 16 Aug 2016, at 10:08 AM, Allen Pollard wrote:
It would explain why the bad take-up of windows 10 if it costs 120,000 AUD for a relatively small company.
We have plenty of companies on Server 2008 and earlier who are starting to introduce Windows 10 clients, either by upgrade or as old machines get replaced. It would be crazy for Microsoft to restrict it's rollout wholesale like this. If corporate uptake is slow it's because Windows 7 is still supported, updated and plenty good enough for many IT departments.
[excessive quoting removed by server]