Looping to Jamie for getting this bug triaged. Please add an RB label with milestone if its critical.

Adding an RB label for tracking purpose. 

RB labels don't generally make sense for Chromoting bugs, as it ships independently of Chrome browser and rarely needs to block it.

I don't think an RB label is needed, this is likely a configuration issue.

maltamirano@, can you capture a host log using the instructions here(under the 'Recording an ETW trace' title):
https://productforums.google.com/d/msg/chrome/RMpoN0WEpzg/0yvbde0ZIFkJ; 

Along with that, it would be useful to know if this is something that was working for you (the original comment says N/A) and broke or if you are setting the machines up for the first time.

a handful of Windows 7 hosts in our organization have this configured. Out of the 2 I tested this morning, 2 could not run curtain mode successfully and I had to turn off curtain mode via registry to get C.R.D. to run for those users. All Windows 7 hosts are running the latest Chrome, and up to date on their Widows update/software. All are running the registry fix for Curtain Mode on.

Windows 10 HOSTS WILL NOT connect whatsoever, even with the TWO require registry fixes mentioned in the Google KB article regarding C.R.D. My work machine HOST is Win 10, and I am connecting with a Win 10 laptop from home. with curtain mode ON, the connection drops immediately after typing the PIN.

I will run the capture sometime tonight, as I am still trying to troubleshoot this.

Just to clarify, these are machines you are attempting to set up, they weren't in a working state and then broken later.  I beleive that is what you are saying but wanted to confirm.

If you send a host log, I can likely root cause it pretty quickly.  A client log for a failed session would also be helpful, here are those instructions:
https://productforums.google.com/forum/#!topic/chrome/_aoxw4Am_RU

Any luck gathering the host logs?  Please let me know if you need help with the instructions.

Got swamped with work, I will try to gather logs by the week’s end

===
Mark Altamirano Systems Administrator Oakwood School Ext.3104

From: joe… via monorail [mailto:monorail+v2.861771509@chromium.org]
Sent: Wednesday, May 31, 2017 8:19 AM
To: Mark Altamirano <maltamirano@oakwoodschool.org>
Subject:  Issue 726388  in chromium: Chrome Remote Desktop: Curtain Mode causing frequest 'disconnect' upon attempting to connect to HOST C.R.D machine

Feel free to reach out if you are having trouble gathering the logs.  I'm closing this bug for now since it has been ~2 weeks.  Please reopen it once you have a host log for me to inspect.