Domain Joined Windows 7/8.1 Pro Upgrades to Windows 10?

They will qualify, but you will have to log into a local Administrator account and initiate the upgrade.

Incorrect... the GWX app excludes domain joined PC's ..... 

Will Microsoft provide a way to switch it ON for domain joined PC's or willl we have to remove each computer from the domain to upgrade it first???

I was able to discover this much...

In C:\Windows\System32\GWX ... you will find the files for the upgrade reservation tool.

Running GWX on a domain-joined PC indeed fails to prompt for reservation, however...

There is a config.xml file that contains a <EnableDomainJoined>false</EnableDomainJoined> parameter. Unfortunately, default permissions to folder block simple changes to this file, and I don't feel like mucking about with my work computer at the moment, haha.

Anyway, presumably, that file will need updating... either by MSFT at a later date, or by utility.

Personally, I'd love to have a bulk-registration utility that lets me validate my entire computer list for a MAK so I can build a fresh Windows 10 image and deploy... but maybe that's wishful thinking.

I was able to discover this much...

In C:\Windows\System32\GWX ... you will find the files for the upgrade reservation tool.

Running GWX on a domain-joined PC indeed fails to prompt for reservation, however...

There is a config.xml file that contains a <EnableDomainJoined>false</EnableDomainJoined> parameter. Unfortunately, default permissions to folder block simple changes to this file, and I don't feel like mucking about with my work computer at the moment, haha.

Anyway, presumably, that file will need updating... either by MSFT at a later date, or by utility.

Personally, I'd love to have a bulk-registration utility that lets me validate my entire computer list for a MAK so I can build a fresh Windows 10 image and deploy... but maybe that's wishful thinking.

Yep they the config.xml file there nice and easy to find with a clear option that spells "Change Me ;) " ... but unfortunately the config.xml is digitally signed with the config.cat file and GMX.exe is configured to only validate signatures from Microsoft etc etc.... 

I'm pretty confident the only way to get our domain-joined PC's updated to Windows 8 will be to remove them from the domain :( 

I am more confident that as Windows Server 2016 becomes ready and more of the Enterprise features of Windows 10 are finalized, the story will change.

For now I feel pretty relieved as an IT guy knowing that nobody at work is going to surprise me with an unexpected Windows 10 upgrade.

That config.xml file is owned by TrustedInstaller, so editing it is something of a pain.

I've tried giving ownership to local admins and editing that parameter to "true", so we'll see if that does anything...

Basically all that the gwx app is, is a downloader. The actual update will probably be pushed to the downloaders a week in advance and clients with the app installed and "reserved" will be able to pre-download the update prior to the scheduled release time. I believe the object of this was to relieve the expected stress on the update servers. Once the release time comes they will get a message stating that the update is ready for installation. 

As far as Domain joined systems are concerned users will still have to have administrative privileges in order to install it. The main reason I would like to allow the download at least is due to the state of our internet connection. I have a 75 mega bit connection at the house and only 3 at work which commonly turns in to dialup speeds during the day with almost 1200 tcp connections by lunch time. State of the connection unfortunately is political so nothing I can do about that. My web filter will cache the first download at night and the rest of the systems will get the cache.

I have 146 systems on my network between xp, vista and 7 and would really like to use 10 as a way to get all the systems on the domain on the same operating system. I have been using 10 in the lab and on my workstation for months as well as a test system in the office and surprisingly have had no issues.

  I have tried editing the config file myself, unfortunately every time the gwx process runs it refreshes the config file.