Announcing Windows 10 Insider Preview Build 14383 for PC and Mobile Insider

I didn't think it would offer more then the usual Remote connection. In contrast you have Skype to replace WLMessenger offering an improved method for both audio and video with the full features of a chat type engine. TV is an advanced software designed for commercial application mostly while allowing free use by home users. The chat features in that of course would compete with those of other messenger services while companies would tend to expect more out of any remote app for use by their IT and tech dept.s!

I found the QA option was also in the 14379 build as someone mentioned having seen in the previous 372 earlier. At this point if you were compare the TH2 update to the latest you would have a much better total idea of just what the contrasts as far as what is new and changed between the November update and what will be seen in the RS1 at the end of the month.

That is when you will be looking at the full retail RTM for everyone when not only the free upgrade offer is over but a full year of progress for the new Windows has already been seen to for those that now plan to run 10 for the first time. Have a few people at this end that will be.

As for going remote however I would still tend to recommend Team Viewer 11 over the built in option as that hasn't seen much of any change since first introduced in the XP days. It simply gets a new look while still being the same Remote PC option in Windows. TV has been found here to be quite reliable once you have one main if not multiple accounts set up and established as a contact each new pc with the first and others. I worked with on VMs as well as the physical machines for several years now having been able to provide that type of rating.:)

UPDATE on Findings! With the 14361 build still found on one of the two 10 Pro VMs I still have running one now seeing the 366 replace the 361 as this post is updated the Quick Assist was found in the Windows Accessories on that older build as well being the oldest confirmed and may be found on even one or two more but would have expired by now! The 361 perishes on the 15th of this month as the expiration date.

The second remote pc finishing up the 14385 also arrived without any watermark as well. But even this build will have a limited life span to keep in mind for your primary machine that is.

About Quick Assist, first let's correct something told wrong in this conversation: both parties don't have to have or use an MS account. The person offering help yes, but the user receiving help can be using a local account only, No email is asked to receive help, just the six digit code from the user offering help.

When both parties have Windows 10 I actually prefer Quick Assist over TeamViewer. It's far more simpler for me as the user assisting maybe a total newbie user to tell him / her to type Quick in Cortana, hit Enter and type the code I gave, than to give instructions about how to download and install TeamViewer.

In real life situation the fact that Quick Assist does not have voice is not a big deal; the person requesting my help has already (most probably) called me (phone, Skype etc.) and we can just continue the call me giving the code and go from there.

Well first of all I never specified that both but for someone to would be required to sign into an MS account. I would expect a code number of some type would still need to be provided between users. And generally as a rule I wouldn't be providing the keys to anything here out on the web in general but would be working with a system brought to me and by agreement then set up remote monitoring either for on the spot work or for temporarily remotely accessing to help someone debug something.

One of the main advantages for the 3rd party ware is re-establishing a connection immediately if lost due to an interruption or when restarting a machine remotely where you then see the "Wait for partner" option where you are then notified the other machine has signed back in after a restart including an upgrade or when someone not even signed in on that particular signs in. And the unintended access can be set to work both ways if not one way only while the Windows option is one way at a time only.

Another consideration to note is security. Simply handing over the access code won't guaranty access between machines with the Team Viewer program since each new contact has to be validated first. I ran into enough of that between the various VMs over times as well as working with different machines. You will still want to verification as well as being granted access between two parties just the same regardless of the option used.

Now for a rather fast comparison besides the just under 10 minutes you have in order to pass the code along to the next user you will see here the side by side view of both Quick Assist and Team Viewer.



The menu bar full of options and some settings is hidden from view on the TV side in order to show the tiny QA bar. At the left for the QA windows navigating that menu leaves much to be desired on the initial impression with just one look. It takes about a minute or so at first only seeing a black area until the second pc's desktop comes into view. With TV you have the option to hide the other machine's wallpaper if you prefer not to have it in view in the event that is undesirable for some reason?

Night Hawk said:

Well first of all I never specified that both but for someone to would be required to sign into an MS account.

Somebody said, that's why I corrected that.

Night Hawk said:

Teamviewer sees video as well as audio depending on each system's set up while this would simply work by way of the remote desktop functionality likely texting back and forth in text chat box while in progress. That also requires both parties to be signed into MS accounts note! You would be using MS not Teamviewer server based consoles instead.

You won't have to worry any. I provided some very sturdy feedback when getting the new build finally on the other machine earlier. That included the obvious lack of security as well as the awkwardness of the QA option when trying to find out just how much access you do have.

You can draw lines to point to things onscreen and bring up the taskmanager but need a bit more control when trying to run something or browse if not simply move around remotely in order to debug and problem solve. Try locating and viewing a log file for example when the only thing seen when going to click on anything is a red dot?!

As far as the very temporary one session only access code you have a very limited number of minutes to pass that along to the second party in order to hit the allow access button once entered into the box on the second machine. The options for exploring drives, editing log files, making changes other then disabling startup items in the Task manager are none existent.

With TV on the other hand you are able to upgrade the OS as well as see newer Insider builds go on as well as go through everything having full access. Access is only seen from a list of contacts which will be indicated either as not available or signed in when the TV program is active. But you are also dealing with a regular software designed for the purpose.

You first need to find out how much access will be needed before being able to recommend either! since one offers far more then the other. The online management console for TV also logs each session as well as allows for maintaining things. The initial remark about the likelihood of both parties needing an MS account would be if MS had updated things to provide anything similar to what TV offers but was later found not to be the case and the feedback illustrated the too awkward and very limited options in contrast. Hopefully they will rework things a bit to improve this since it didn't look any better then what was seen in XP!

Kari said:

About Quick Assist, first let's correct something told wrong in this conversation: both parties don't have to have or use an MS account. The person offering help yes, but the user receiving help can be using a local account only, No email is asked to receive help, just the six digit code from the user offering help.

Thanks, Kari. I wasn't aware of this, but it really helps to know that.

Kari said:

When both parties have Windows 10 I actually prefer Quick Assist over TeamViewer. It's far more simpler for me as the user assisting maybe a total newbie user to tell him / her to type Quick in Cortana, hit Enter and type the code I gave, than to give instructions about how to download and install TeamViewer.

Right again! However, I should add that when Simrick and I have worked together to solve a problem (mine, of course), she told me to download and install TeamViewer. I must say it was a "piece of cake" that pretty much any newbie could do. She instructed me to give her the numbers and away we went. Yeah, I'm far from being a newbie, but, well . . . as everyone knows, I'm primarily a hardware person, but Simrick's slowly teaching me.

Whether using Quick Assist or TeamViewer, it all hinges on the "helper" having the ability to take over my system and make the necessary changes. That said, either one is a great teaching tool.

Kari said:

In real life situation the fact that Quick Assist does not have voice is not a big deal; the person requesting my help has already (most probably) called me (phone, Skype etc.) and we can just continue the call me giving the code and go from there.

I agree that it doesn't matter if voice is available for the most part because Simrick and I were on Skype. Going back to the newbie, though, I'm not so sure he/she would have the wherewithal to use both QA and Skype. The telephone isn't a great option, simply because of the international nature of things.

All things considered, Quick Assist is headed in the right direction, and I wouldn't be surprised to see it more refined in the future. Probably not in the Anniversary Edition of Windows 10, but . . .

And I gotta say that the combo of Skype and QA, along with Ink (which TeamViewer doesn't have) are great. Not only were we "giving help" to each other, we ended up in a teaching session also. Simrick said, "Click on this," and I said where is it? She then circled it with Ink, and it was, "Oh! There it is." After I'd followed her instructions, she was able to "erase" the circle around whatever.

Bottom line . . . a Quick Assist/Skype combination would be a "marriage made in Heaven!"

Night Hawk said:

Well first of all I never specified that both but for someone to would be required to sign into an MS account. I would expect a code number of some type would still need to be provided between users. And generally as a rule I wouldn't be providing the keys to anything here out on the web in general but would be working with a system brought to me and by agreement then set up remote monitoring either for on the spot work or for temporarily remotely accessing to help someone debug something.

Well, yeah, you did . . .

From Message 259: you said we should both be signed in with our MS accounts.

You will both need to be signed into an MS account and be established as contacts first. The Quick Assist is located right above the Remote Desktop Connection item under the Start>Windows Accessories. Once I get to the other pc being worked on I can run a test between that and the main here.

You said the same in Post 253.